Want to highlight a helpful answer? Upvote!

Did someone help you, or did an answer or User Tip resolve your issue? Upvote by selecting the upvote arrow. Your feedback helps others! Learn more about when to upvote >

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

User profile for user: ponderingz
ponderingz Author
User level: Level 1
0 points

Macbook Air Kernal Panic?

Hello Everyone,


This morning I had my first kernal panic. A bit frightening as I've owned Macs for many years and never had one. The log seems pretty short compared to others I've seen online. Does anyone see what might be happening here?


Thank you!

Here's my specs: Macbook Air 13", Late 2010

MacBookAir3,2

Processor 2.13 GHz Intel Core 2 Duo

Memory 4 GB 1067 MHz DDR3

Graphics NVIDIA GeForce 320M 256 MB

Software OS X 10.8.2 (12C60)



Here's the log:

Fri Feb 1 07:35:27 2013

panic(cpu 0 caller 0xffffff800c0b7bd5): Kernel trap at 0xffffff800c02e906, type 12=stack bounds, registers:

CR0: 0x000000008001003b, CR2: 0xffffff807eadd000, CR3: 0x000000000ed1a000, CR4: 0x0000000000000660

RAX: 0x909520efd4c60090, RBX: 0xffffff8017091000, RCX: 0x0000000009000000, RDX: 0xffffff8078a6a078

RSP: 0xffffff8084283e40, RBP: 0x01ffff8084283eb0, RSI: 0xffffff8078a6a068, RDI: 0x0000000000000000

R8: 0xffffff800c6bec60, R9: 0xffffffffffffffff, R10: 0x00000000ffffffff, R11: 0x00000000ffffff80

R12: 0x0000000000000001, R13: 0x0000000000000000, R14: 0xffffff8017122aa0, R15: 0x0000000000000000

RFL: 0x0000000000010046, RIP: 0xffffff800c02e906, CS: 0x0000000000000008, SS: 0x0000000000000000

Fault CR2: 0xffffff807eadd000, Error code: 0x0000000000000000, Fault CPU: 0x0



Backtrace (CPU 0), Frame : Return Address

0xffffff8084283ae0 : 0xffffff800c01d626

0xffffff8084283b50 : 0xffffff800c0b7bd5

0xffffff8084283d20 : 0xffffff800c0ce4ed

0xffffff8084283d40 : 0xffffff800c02e906

No mapping exists for frame pointer

Backtrace terminated-invalid frame pointer 0x1ffff8084283eb0



BSD process name corresponding to current thread: kernel_task



Mac OS version:

Not yet set



Kernel version:

Darwin Kernel Version 12.2.0: Sat Aug 25 00:48:52 PDT 2012; root:xnu-2050.18.24~1/RELEASE_X86_64

Kernel UUID: 69A5853F-375A-3EF4-9247-478FD0247333

Kernel slide: 0x000000000be00000

Kernel text base: 0xffffff800c000000

System model name: MacBookAir3,2 (Mac-942C5DF58193131B)



System uptime in nanoseconds: 1398584534

last loaded kext at 336372302: com.apple.driver.XsanFilter 404 (addr 0xffffff7f8dcf9000, size 20480)

loaded kexts:

com.apple.driver.XsanFilter 404

com.apple.iokit.IOAHCIBlockStorage 2.2.2

com.apple.driver.AppleIntelCPUPowerManagementClient 196.0.0

com.apple.driver.AppleUSBHub 5.2.5

com.apple.driver.AirPort.Brcm4331 602.15.22

com.apple.driver.AppleEFINVRAM 1.6.1

com.apple.driver.AppleSmartBatteryManager 161.0.0

com.apple.driver.AppleAHCIPort 2.4.1

com.apple.driver.AppleUSBEHCI 5.4.0

com.apple.driver.AppleUSBOHCI 5.2.5

com.apple.driver.AppleRTC 1.5

com.apple.driver.AppleHPET 1.7

com.apple.driver.AppleACPIButtons 1.6

com.apple.driver.AppleSMBIOS 1.9

com.apple.driver.AppleACPIEC 1.6

com.apple.driver.AppleAPIC 1.6

com.apple.nke.applicationfirewall 4.0.39

com.apple.security.quarantine 2

com.apple.driver.AppleIntelCPUPowerManagement 196.0.0

com.apple.iokit.IOUSBUserClient 5.2.5

com.apple.iokit.IO80211Family 500.15

com.apple.iokit.IONetworkingFamily 3.0

com.apple.driver.AppleMCP89RootPortPM 1.11

com.apple.iokit.IOAHCIFamily 2.2.1

com.apple.iokit.IOUSBFamily 5.4.0

com.apple.driver.NVSMU 2.2.9

com.apple.driver.AppleEFIRuntime 1.6.1

com.apple.iokit.IOHIDFamily 1.8.0

com.apple.iokit.IOSMBusFamily 1.1

com.apple.security.sandbox 220

com.apple.kext.AppleMatch 1.0.0d1

com.apple.security.TMSafetyNet 7

com.apple.driver.DiskImages 344

com.apple.iokit.IOStorageFamily 1.8

com.apple.driver.AppleKeyStore 28.21

com.apple.driver.AppleACPIPlatform 1.6

com.apple.iokit.IOPCIFamily 2.7.2

com.apple.iokit.IOACPIFamily 1.4

com.apple.kec.corecrypto 1.0

MacBook Air (13-inch Late 2010), OS X Mountain Lion (10.8.2)

Posted on Feb 1, 2013 4:57 AM

Reply
Question marked as Best reply
User profile for user: Linc Davis
Linc Davis
User level: Level 10
209,547 points

Posted on Feb 1, 2013 11:35 AM

That panic was not caused by third-party software. If it's happened only once, and is not repeated in at least a few thousand hours of use, a reasonable choice would be to ignore it. Machines don't work perfectly. They never will.


If the problem is recurrent, the possibilities are:


  1. A damaged OS X installation
  2. A fault in a peripheral device, if any
  3. Corrupt non-volatile memory (NVRAM)
  4. An internal hardware fault
  5. An obscure bug in OS X


You can rule out the first two possibilities by reinstalling the OS and testing with non-essential peripherals disconnected and aftermarket expansion cards removed, if applicable. Sometimes a clean reinstallation (after erasing the startup volume) may solve a problem that isn't solved by reinstalling in place, without erasing.


Corrupt NVRAM, which rarely causes panics, can be ruled out by resetting it as directed in this support article.


If you've recently upgraded the memory, reinstall the original memory and see whether there's any improvement. Be careful not to touch the gold contacts on the memory modules when handling them. If necessary, clean them with a mild solvent such as rubbing alcohol.


The Apple Hardware Test, though generally unreliable, will sometimes detect a fault. A negative test can't be depended on. Run the extended version of the test.


In the category of obscure bugs, reports suggest that FileVault may trigger kernel traps under some unknown conditions. Most, though not all, of these reports seem to involve booting from an aftermarket SSD. If those conditions apply to you, try deactivating FileVault.


Otherwise, make a "Genius" appointment at an Apple Store to have the machine tested. You may have to leave it there for several days. There isn't much point in doing this unless you can reproduce the panic, or if you can't, it happens often enough that it's likely to be repeated at the store. Otherwise you may be told that nothing is wrong.


Print the first page of the panic report and bring it with you.


Back up all data on the internal drive(s) before you hand over your computer to anyone. If privacy is a concern, erase the data partition(s) with the option to write zeros* (do this only if you know how to restore, and you have at least two independent backups.) Don’t erase the recovery partition, if present.


Keeping your confidential data secure during hardware repair


*An SSD doesn't need to be zeroed.

View in context
3 replies
Question marked as Best reply
User profile for user: Linc Davis
Linc Davis
User level: Level 10
209,547 points

Feb 1, 2013 11:35 AM in response to ponderingz

That panic was not caused by third-party software. If it's happened only once, and is not repeated in at least a few thousand hours of use, a reasonable choice would be to ignore it. Machines don't work perfectly. They never will.


If the problem is recurrent, the possibilities are:


  1. A damaged OS X installation
  2. A fault in a peripheral device, if any
  3. Corrupt non-volatile memory (NVRAM)
  4. An internal hardware fault
  5. An obscure bug in OS X


You can rule out the first two possibilities by reinstalling the OS and testing with non-essential peripherals disconnected and aftermarket expansion cards removed, if applicable. Sometimes a clean reinstallation (after erasing the startup volume) may solve a problem that isn't solved by reinstalling in place, without erasing.


Corrupt NVRAM, which rarely causes panics, can be ruled out by resetting it as directed in this support article.


If you've recently upgraded the memory, reinstall the original memory and see whether there's any improvement. Be careful not to touch the gold contacts on the memory modules when handling them. If necessary, clean them with a mild solvent such as rubbing alcohol.


The Apple Hardware Test, though generally unreliable, will sometimes detect a fault. A negative test can't be depended on. Run the extended version of the test.


In the category of obscure bugs, reports suggest that FileVault may trigger kernel traps under some unknown conditions. Most, though not all, of these reports seem to involve booting from an aftermarket SSD. If those conditions apply to you, try deactivating FileVault.


Otherwise, make a "Genius" appointment at an Apple Store to have the machine tested. You may have to leave it there for several days. There isn't much point in doing this unless you can reproduce the panic, or if you can't, it happens often enough that it's likely to be repeated at the store. Otherwise you may be told that nothing is wrong.


Print the first page of the panic report and bring it with you.


Back up all data on the internal drive(s) before you hand over your computer to anyone. If privacy is a concern, erase the data partition(s) with the option to write zeros* (do this only if you know how to restore, and you have at least two independent backups.) Don’t erase the recovery partition, if present.


Keeping your confidential data secure during hardware repair


*An SSD doesn't need to be zeroed.

Reply

Macbook Air Kernal Panic?

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.
Learn more Sign up