Apple Event: May 7th at 7 am PT

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

Please help me understand this kernel panic report

My macbook pro restarts multple times in a row every since this guy upgraded me to osx 10.8. I keep getting the below error message. please explain and suggest any fix: Thanks in advance:


Interval Since Last Panic Report: 71557 sec
Panics Since Last Report: 3
Anonymous UUID: D75B923F-A8D3-427E-A0D9-BB842B814C6E


Thu Aug 15 23:08:36 2013
panic(cpu 0 caller 0xffffff8007eb7075): Kernel trap at 0xffffff7f898f0db1, type 14=page fault, registers:
CR0: 0x0000000080010033, CR2: 0xffffff80d402200c, CR3: 0x0000000025850000, CR4: 0x0000000000000660
RAX: 0xffffff801c1f9848, RBX: 0x0000000000000000, RCX: 0xffffff801c1f9848, RDX: 0x00000000caf01e98
RSP: 0xffffff80f007b2f0, RBP: 0xffffff80f007b470, RSI: 0xffffff80d4022000, RDI: 0xffffff802802a320
R8: 0x0000000000000000, R9: 0xffffff80f007ad18, R10: 0x0000000000004078, R11: 0x000000000000407c
R12: 0xffffff8028a0f808, R13: 0xffffff8028984380, R14: 0xffffff8027b4d988, R15: 0x00000000caf01e98
RFL: 0x0000000000010282, RIP: 0xffffff7f898f0db1, CS: 0x0000000000000008, SS: 0x0000000000000010
Fault CR2: 0xffffff80d402200c, Error code: 0x0000000000000000, Fault CPU: 0x0


Backtrace (CPU 0), Frame : Return Address
0xffffff80f007af90 : 0xffffff8007e1d636
0xffffff80f007b000 : 0xffffff8007eb7075
0xffffff80f007b1d0 : 0xffffff8007ecd60d
0xffffff80f007b1f0 : 0xffffff7f898f0db1
0xffffff80f007b470 : 0xffffff7f898f1e58
0xffffff80f007b5c0 : 0xffffff7f8990bb13
0xffffff80f007b5d0 : 0xffffff7f8991eb28
0xffffff80f007b600 : 0xffffff7f89920282
0xffffff80f007b680 : 0xffffff7f899207c2
0xffffff80f007b700 : 0xffffff7f89907254
0xffffff80f007b760 : 0xffffff7f89907b02
0xffffff80f007b7b0 : 0xffffff7f89907eb9
0xffffff80f007b850 : 0xffffff7f899087c1
0xffffff80f007b890 : 0xffffff7f898c51a5
0xffffff80f007ba10 : 0xffffff7f89904f56
0xffffff80f007bad0 : 0xffffff7f898c3cae
0xffffff80f007bb30 : 0xffffff8008271bd9
0xffffff80f007bb50 : 0xffffff8008273180
0xffffff80f007bbb0 : 0xffffff8008270b9f
0xffffff80f007bd00 : 0xffffff8007e979e1
0xffffff80f007be10 : 0xffffff8007e20afd
0xffffff80f007be40 : 0xffffff8007e10448
0xffffff80f007be90 : 0xffffff8007e195fb
0xffffff80f007bf00 : 0xffffff8007ea50ae
0xffffff80f007bfb0 : 0xffffff8007ecdc1e
Kernel Extensions in backtrace:
com.apple.GeForce(8.0)[9D30C66C-CA86-3540-A070-395C1BCB7F82]@0xffffff7f898b7000 ->0xffffff7f89975fff
dependency: com.apple.NVDAResman(8.0.0)[A268310F-5D51-3D05-8FB0-D91FB73690BA]@0xffffff7f885 a9000
dependency: com.apple.iokit.IONDRVSupport(2.3.4)[1EBB4A44-AD92-398A-99F0-2D0EA0D0BE11]@0xff ffff7f88595000
dependency: com.apple.iokit.IOPCIFamily(2.7)[C1E9C4AD-003A-3794-95D0-5FC1817E35D8]@0xffffff 7f88421000
dependency: com.apple.iokit.IOGraphicsFamily(2.3.4)[9A99C5C3-64E1-3596-B630-DFC16F499E1A]@0 xffffff7f88552000


BSD process name corresponding to current thread: plugin-container


Mac OS version:
12A178q


Kernel version:
Darwin Kernel Version 12.0.0: Sun Apr 8 21:22:58 PDT 2012; root:xnu-2050.3.19~1/RELEASE_X86_64
Kernel UUID: FED644F0-FA16-3ED9-996D-88DF52600E9A
Kernel slide: 0x0000000007c00000
Kernel text base: 0xffffff8007e00000
System model name: MacBookPro5,5 (Mac-F2268AC8)


System uptime in nanoseconds: 1463617280830
last loaded kext at 35817297174: com.apple.driver.AppleHWSensor 1.9.5d0 (addr 0xffffff7f89ff2000, size 36864)
last unloaded kext at 192614138289: com.apple.driver.AppleFileSystemDriver 3.0.1 (addr 0xffffff7f8a23d000, size 8192)
loaded kexts:
com.apple.driver.AppleHWSensor 1.9.5d0
com.apple.driver.AudioAUUC 1.60
com.apple.iokit.IOBluetoothSerialManager 4.0.8b13
com.apple.driver.AGPM 100.12.67
com.apple.filesystems.autofs 3.0
com.apple.driver.AppleMikeyHIDDriver 122
com.apple.driver.AppleHDA 2.3.0a22
com.apple.driver.SMCMotionSensor 3.0.2d6
com.apple.iokit.BroadcomBluetoothHCIControllerUSBTransport 4.0.8b13
com.apple.driver.AppleSMCLMU 2.0.2d0
com.apple.iokit.IOUserEthernet 1.0.0d1
com.apple.Dont_Steal_Mac_OS_X 7.0.0
com.apple.driver.ACPI_SMC_PlatformPlugin 1.0.0
com.apple.driver.AppleMikeyDriver 2.3.0a22
com.apple.driver.AppleLPC 1.6.0
com.apple.driver.AppleBacklight 170.2.1
com.apple.driver.AppleUpstreamUserClient 3.5.10
com.apple.driver.AppleMCCSControl 1.0.28
com.apple.GeForce 8.0.0
com.apple.driver.AppleUSBTCButtons 235.3
com.apple.driver.AppleUSBTCKeyboard 235.3
com.apple.driver.AppleIRController 320.9
com.apple.driver.AppleUSBCardReader 3.0.2
com.apple.iokit.SCSITaskUserClient 3.5.0
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless 1.0.0d1
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1
com.apple.BootCache 34
com.apple.driver.XsanFilter 404
com.apple.iokit.IOAHCIBlockStorage 2.2.0
com.apple.driver.AppleUSBOHCI 5.0.0a30
com.apple.driver.AppleFWOHCI 4.8.9
com.apple.driver.AirPort.Brcm4331 600.13.9
com.apple.driver.AppleUSBHub 5.0.0a30
com.apple.driver.AppleAHCIPort 2.4.0
com.apple.nvenet 2.0.17
com.apple.driver.AppleEFINVRAM 1.6.0
com.apple.driver.AppleUSBEHCI 5.0.0a30
com.apple.driver.AppleSmartBatteryManager 161.0.0
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.driver.AppleIntelCPUPowerManagementClient 196.0.0
com.apple.nke.applicationfirewall 4.0.38
com.apple.security.quarantine 2
com.apple.driver.AppleIntelCPUPowerManagement 196.0.0
com.apple.iokit.IOSerialFamily 10.0.6
com.apple.kext.triggers 1.0
com.apple.driver.DspFuncLib 2.3.0a22
com.apple.iokit.IOAudioFamily 1.8.9fc5
com.apple.kext.OSvKernDSPLib 1.6
com.apple.driver.CoreStorage 230.3
com.apple.iokit.IOFireWireIP 2.2.4
com.apple.iokit.AppleBluetoothHCIControllerUSBTransport 4.0.8b13
com.apple.iokit.IOSurface 85.0
com.apple.iokit.IOBluetoothFamily 4.0.8b13
com.apple.driver.ApplePolicyControl 3.0.19
com.apple.driver.IOPlatformPluginLegacy 1.0.0
com.apple.driver.AppleSMBusPCI 1.0.10d0
com.apple.driver.IOPlatformPluginFamily 5.2.0d0
com.apple.driver.AppleGraphicsControl 3.0.19
com.apple.driver.AppleBacklightExpert 1.0.4
com.apple.driver.AppleHDAController 2.3.0a22
com.apple.iokit.IOHDAFamily 2.3.0a22
com.apple.driver.AppleSMC 3.1.3d7
com.apple.driver.AppleSMBusController 1.0.10d0
com.apple.nvidia.nv50hal 8.0.0
com.apple.NVDAResman 8.0.0
com.apple.iokit.IONDRVSupport 2.3.4
com.apple.iokit.IOGraphicsFamily 2.3.4
com.apple.driver.AppleUSBMultitouch 235.5
com.apple.iokit.IOUSBHIDDriver 5.0.0a30
com.apple.iokit.IOSCSIBlockCommandsDevice 3.5.0
com.apple.iokit.IOUSBMassStorageClass 3.5.0
com.apple.driver.AppleUSBMergeNub 5.0.0a30
com.apple.driver.AppleUSBComposite 5.0.0a30
com.apple.iokit.IOSCSIMultimediaCommandsDevice 3.5.0
com.apple.iokit.IOBDStorageFamily 1.7
com.apple.iokit.IODVDStorageFamily 1.7.1
com.apple.iokit.IOCDStorageFamily 1.7.1
com.apple.iokit.IOAHCISerialATAPI 2.5.0
com.apple.iokit.IOSCSIArchitectureModelFamily 3.5.0
com.apple.iokit.IOFireWireFamily 4.4.6
com.apple.iokit.IO80211Family 500.8.4
com.apple.iokit.IOUSBUserClient 5.0.0a30
com.apple.iokit.IOAHCIFamily 2.2.0
com.apple.iokit.IONetworkingFamily 3.0
com.apple.iokit.IOUSBFamily 5.0.0a30
com.apple.driver.NVSMU 2.2.9
com.apple.driver.AppleEFIRuntime 1.6.0
com.apple.iokit.IOHIDFamily 1.8.0
com.apple.iokit.IOSMBusFamily 1.1
com.apple.security.sandbox 212
com.apple.kext.AppleMatch 1.0.0d1
com.apple.security.TMSafetyNet 7
com.apple.driver.DiskImages 342
com.apple.iokit.IOStorageFamily 1.8
com.apple.driver.AppleKeyStore 28.18
com.apple.driver.AppleACPIPlatform 1.6
com.apple.iokit.IOPCIFamily 2.7
com.apple.iokit.IOACPIFamily 1.4
com.apple.kec.corecrypto 1.0
Model: MacBookPro5,5, BootROM MBP55.00AC.B03, 2 processors, Intel Core 2 Duo, 2.26 GHz, 8 GB, SMC 1.47f2
Graphics: NVIDIA GeForce 9400M, NVIDIA GeForce 9400M, PCI, 256 MB
Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1067 MHz, 0x859B, 0x435434473353313036374D2E4D3136464D44
Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1067 MHz, 0x859B, 0x435434473353313036374D2E4D3136464D44
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x8D), Broadcom BCM43xx 1.0 (5.106.98.75.9)
Bluetooth: Version 4.0.8b13, 2 service, 18 devices, 1 incoming serial ports
Network Service: AirPort, AirPort, en1
Serial ATA Device: FUJITSU MJA2160BH FFS G1, 160.04 GB
Serial ATA Device: MATSHITADVD-R UJ-868
USB Device: Internal Memory Card Reader, apple_vendor_id, 0x8403, 0x26500000 / 2
USB Device: Built-in iSight, apple_vendor_id, 0x8507, 0x24400000 / 2
USB Device: BRCM2046 Hub, 0x0a5c (Broadcom Corp.), 0x4500, 0x06100000 / 2
USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x8213, 0x06110000 / 4
USB Device: Apple Internal Keyboard / Trackpad, apple_vendor_id, 0x0236, 0x04600000 / 3
USB Device: IR Receiver, apple_vendor_id, 0x8242, 0x04500000 / 2

MacBook Pro, 13-inch, Mid 2009 8 GB 1067 MHz DDR

Posted on Aug 15, 2013 8:45 PM

Reply
Question marked as Best reply

Posted on Aug 15, 2013 10:26 PM

That panic was not caused by third-party software. If the problem is recurrent, the possibilities are:


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


You may already have ruled out some of these.

Rule out #1 by booting in safe mode and then rebooting as usual. Note: If FileVault is enabled on some models, or if a firmware password is set, or if the boot volume is a software RAID, you can’t do this. Post for further instructions.

You can rule out #2 and #3 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.


If your model has user-replaceable memory, and you've upgraded the memory modules, reinstall the original memory and see whether there's any improvement. Be careful not to touch the gold contacts. Clean them with a mild solvent such as rubbing alcohol. Aftermarket memory must exactly match the technical specifications for your model. Memory that is either slower or faster than specified may be incompatible.


The Apple Hardware Test or Apple Diagnostics, 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.

Connecting more than one display is another reported trigger for OS X bugs.

If your system is not fully up to date, running Software Update might get you a bug fix.


In rare cases, a malformed network packet from a defective router or other network device can cause panics. Such packets could also be sent deliberately by a skillful attacker. This possibility is something to consider if you run a public server that might be the target of such an attack.


If none of the above applies, 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.

1 reply
Question marked as Best reply

Aug 15, 2013 10:26 PM in response to vonkaiser3

That panic was not caused by third-party software. If the problem is recurrent, the possibilities are:


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


You may already have ruled out some of these.

Rule out #1 by booting in safe mode and then rebooting as usual. Note: If FileVault is enabled on some models, or if a firmware password is set, or if the boot volume is a software RAID, you can’t do this. Post for further instructions.

You can rule out #2 and #3 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.


If your model has user-replaceable memory, and you've upgraded the memory modules, reinstall the original memory and see whether there's any improvement. Be careful not to touch the gold contacts. Clean them with a mild solvent such as rubbing alcohol. Aftermarket memory must exactly match the technical specifications for your model. Memory that is either slower or faster than specified may be incompatible.


The Apple Hardware Test or Apple Diagnostics, 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.

Connecting more than one display is another reported trigger for OS X bugs.

If your system is not fully up to date, running Software Update might get you a bug fix.


In rare cases, a malformed network packet from a defective router or other network device can cause panics. Such packets could also be sent deliberately by a skillful attacker. This possibility is something to consider if you run a public server that might be the target of such an attack.


If none of the above applies, 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.

Please help me understand this kernel panic report

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