Kernel Panics on 27" iMac (Late 2009)

Question

Level 1

4 points

Kernel Panics on 27" iMac (Late 2009)

Hi Community,

my iMac has started Kernel Panicking on me since Thursday. At first, I could barely boot up the machine without a Kernel Panic, after talking to Apple's Phone Support, who told me to delete the Application Caches and re-install Lion (without removing existing files and apps) it has become a lot less rare, but still happens.

Here's the most recent panic log:

Sat Jun 16 12:16:02 2012

panic(cpu 0 caller 0xffffff80002c473a): Kernel trap at 0xffffff8000290560, type 13=general protection, registers:

CR0: 0x0000000080010033, CR2: 0x0000000112026000, CR3: 0x000000002371f000, CR4: 0x0000000000000660

RAX: 0x0000000000000001, RBX: 0x0000000007950000, RCX: 0xffffff8012cffd80, RDX: 0x0000000000080e51

RSP: 0xffffff80f0ca3450, RBP: 0xffffff80f0ca3470, RSI: 0x00000000299e7310, RDI: 0xffffff8004302728

R8: 0xffffff8012221058, R9: 0x0000000000000000, R10: 0xffffff800086f4d0, R11: 0xffffff80006400b4

R12: 0xffffff8004302728, R13: 0x0000000000000100, R14: 0xffffff8018b080e0, R15: 0x0080000000000000

RFL: 0x0000000000010206, RIP: 0xffffff8000290560, CS: 0x0000000000000008, SS: 0x0000000000000010

CR2: 0x0000000112026000, Error code: 0x0000000000000000, Faulting CPU: 0x0

Backtrace (CPU 0), Frame : Return Address

0xffffff80f0ca3100 : 0xffffff8000220792

0xffffff80f0ca3180 : 0xffffff80002c473a

0xffffff80f0ca3330 : 0xffffff80002da0cd

0xffffff80f0ca3350 : 0xffffff8000290560

0xffffff80f0ca3470 : 0xffffff800028c225

0xffffff80f0ca3780 : 0xffffff8000570f6b

0xffffff80f0ca37c0 : 0xffffff80002efefb

0xffffff80f0ca3890 : 0xffffff80002f02c2

0xffffff80f0ca3900 : 0xffffff80002f0fd3

0xffffff80f0ca3a70 : 0xffffff80002f143f

0xffffff80f0ca3ca0 : 0xffffff7f8085bcf5

0xffffff80f0ca3dc0 : 0xffffff800031b54d

0xffffff80f0ca3e10 : 0xffffff8000312d6b

0xffffff80f0ca3e60 : 0xffffff8000564051

0xffffff80f0ca3ef0 : 0xffffff8000564758

0xffffff80f0ca3f50 : 0xffffff80005cd61b

0xffffff80f0ca3fb0 : 0xffffff80002daa13

Kernel Extensions in backtrace:

com.apple.filesystems.ntfs(3.10.1)[13494759-5AEF-34F4-BD38-E47CDA5F2867]@0xffff ff7f80851000->0xffffff7f808a7fff

BSD process name corresponding to current thread: HandBrake

Mac OS version:

11E53

Kernel version:

Darwin Kernel Version 11.4.0: Mon Apr 9 19:32:15 PDT 2012; root:xnu-1699.26.8~1/RELEASE_X86_64

Kernel UUID: *****************

System model name: iMac11,1 (Mac-F2268DAE)

System uptime in nanoseconds: 4331456990878

last loaded kext at 103871244872: com.apple.filesystems.afpfs 9.8.1 (addr 0xffffff7f8182c000, size 356352)

last unloaded kext at 179063722577: com.apple.driver.AppleUSBUHCI 4.4.5 (addr 0xffffff7f80b29000, size 65536)

loaded kexts:

com.apple.filesystems.afpfs 9.8.1

com.apple.nke.asp_tcp 6.0.1

com.apple.driver.AppleBluetoothMultitouch 70.12

com.apple.filesystems.ntfs 3.10.1

com.apple.filesystems.autofs 3.0

com.apple.driver.AppleHWSensor 1.9.5d0

com.apple.driver.AudioAUUC 1.59

com.apple.driver.AppleMikeyHIDDriver 122

com.apple.driver.AppleUpstreamUserClient 3.5.9

com.apple.driver.AppleMCCSControl 1.0.26

com.apple.kext.ATIFramebuffer 7.1.8

com.apple.driver.AppleMikeyDriver 2.2.0f3

com.apple.ATIRadeonX2000 7.1.8

com.apple.driver.AppleHDA 2.2.0f3

com.apple.driver.AGPM 100.12.42

com.apple.iokit.IOUserEthernet 1.0.0d1

com.apple.iokit.IOBluetoothSerialManager 4.0.5f11

com.apple.Dont_Steal_Mac_OS_X 7.0.0

com.apple.driver.AudioIPCDriver 1.2.2

com.apple.driver.ACPI_SMC_PlatformPlugin 5.0.0d0

com.apple.driver.AppleLPC 1.5.8

com.apple.driver.AppleBacklight 170.1.9

com.apple.driver.BroadcomUSBBluetoothHCIController 4.0.5f11

com.apple.driver.AppleIRController 312

com.apple.driver.AppleUSBCardReader 3.0.1

com.apple.iokit.SCSITaskUserClient 3.2.0

com.apple.AppleFSCompression.AppleFSCompressionTypeDataless 1.0.0d1

com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1

com.apple.BootCache 33

com.apple.driver.XsanFilter 404

com.apple.iokit.IOAHCISerialATAPI 2.0.3

com.apple.iokit.IOAHCIBlockStorage 2.0.3

com.apple.driver.AppleFWOHCI 4.8.9

com.apple.driver.AppleUSBHub 4.5.0

com.apple.driver.AirPort.Atheros40 504.64.2

com.apple.driver.AppleEFINVRAM 1.5.0

com.apple.driver.AppleAHCIPort 2.3.0

com.apple.iokit.AppleBCM5701Ethernet 3.1.2b2

com.apple.driver.AppleUSBEHCI 4.5.8

com.apple.driver.AppleACPIButtons 1.5

com.apple.driver.AppleRTC 1.5

com.apple.driver.AppleHPET 1.6

com.apple.driver.AppleSMBIOS 1.8

com.apple.driver.AppleACPIEC 1.5

com.apple.driver.AppleAPIC 1.5

com.apple.driver.AppleIntelCPUPowerManagementClient 193.0.0

com.apple.nke.applicationfirewall 3.2.30

com.apple.security.quarantine 1.3

com.apple.driver.AppleIntelCPUPowerManagement 193.0.0

com.apple.security.SecureRemotePassword 1.0

com.apple.driver.AppleBluetoothHIDKeyboard 160.7

com.apple.driver.AppleHIDKeyboard 160.7

com.apple.driver.AppleMultitouchDriver 231.4

com.apple.driver.IOBluetoothHIDDriver 4.0.5f11

com.apple.kext.triggers 1.0

com.apple.driver.DspFuncLib 2.2.0f3

com.apple.driver.AppleSMBusController 1.0.10d0

com.apple.kext.ATI4800Controller 7.1.8

com.apple.kext.ATISupport 7.1.8

com.apple.iokit.IOSurface 80.0.2

com.apple.iokit.IOSerialFamily 10.0.5

com.apple.iokit.IOFireWireIP 2.2.4

com.apple.iokit.IOAudioFamily 1.8.6fc17

com.apple.kext.OSvKernDSPLib 1.3

com.apple.driver.AppleHDAController 2.2.0f3

com.apple.iokit.IOHDAFamily 2.2.0f3

com.apple.driver.ApplePolicyControl 3.0.16

com.apple.driver.AppleSMC 3.1.3d8

com.apple.driver.IOPlatformPluginLegacy 5.0.0d0

com.apple.driver.AppleSMBusPCI 1.0.10d0

com.apple.driver.AppleGraphicsControl 3.0.16

com.apple.driver.IOPlatformPluginFamily 5.1.0d17

com.apple.driver.AppleBacklightExpert 1.0.3

com.apple.iokit.IONDRVSupport 2.3.2

com.apple.iokit.IOGraphicsFamily 2.3.2

com.apple.driver.AppleUSBBluetoothHCIController 4.0.5f11

com.apple.iokit.IOBluetoothFamily 4.0.5f11

com.apple.iokit.IOUSBHIDDriver 4.4.5

com.apple.iokit.IOUSBMassStorageClass 3.0.1

com.apple.iokit.IOSCSIBlockCommandsDevice 3.2.0

com.apple.iokit.IOFireWireSerialBusProtocolTransport 2.1.0

com.apple.iokit.IOFireWireSBP2 4.2.0

com.apple.driver.AppleUSBMergeNub 4.5.3

com.apple.driver.AppleUSBComposite 4.5.8

com.apple.iokit.IOSCSIMultimediaCommandsDevice 3.2.0

com.apple.iokit.IOBDStorageFamily 1.6

com.apple.iokit.IODVDStorageFamily 1.7

com.apple.iokit.IOCDStorageFamily 1.7

com.apple.iokit.IOSCSIArchitectureModelFamily 3.2.0

com.apple.iokit.IOFireWireFamily 4.4.5

com.apple.iokit.IOUSBUserClient 4.5.8

com.apple.iokit.IO80211Family 420.3

com.apple.iokit.IOAHCIFamily 2.0.8

com.apple.iokit.IOEthernetAVBController 1.0.1b1

com.apple.iokit.IONetworkingFamily 2.1

com.apple.iokit.IOUSBFamily 4.5.8

com.apple.driver.AppleEFIRuntime 1.5.0

com.apple.iokit.IOHIDFamily 1.7.1

com.apple.iokit.IOSMBusFamily 1.1

com.apple.security.sandbox 177.5

com.apple.kext.AppleMatch 1.0.0d1

com.apple.security.TMSafetyNet 7

com.apple.driver.DiskImages 331.6

com.apple.iokit.IOStorageFamily 1.7.1

com.apple.driver.AppleKeyStore 28.18

com.apple.driver.AppleACPIPlatform 1.5

com.apple.iokit.IOPCIFamily 2.6.8

com.apple.iokit.IOACPIFamily 1.4

I also ran Apple Hardware Test, because I suspected something might be up hardware wise, and indeed, when I first ran it I got this message:

It says: "Apple Hardware Test found an error: 4MEM/4/40000000: 0xb78dd418"

At this point I figured one of my RAM chips was broken, but when I went and tested them the next day (by running AHT with only one module at a time and then both together again) AHT didn't find any errors anymore.

Apple says my next move is to wipe the hard drive clean and reinstall Lion. Before I do that, I'd like to be sure it's not actually a hardware problem. Can anybody make sense of what's going on here? I'd greatly appreciate any help I can get.

Thanks in advance!

iMac (27-inch Late 2009), Mac OS X (10.7.4)

Posted on Jun 16, 2012 9:05 AM

Reply

Answer 1

Best reply

den.thed

Level 9

77,134 points

Jun 16, 2012 9:32 AM in response to andrekn

Sounds like you have either a faulty module or one that might be loose and needs to be reseated.

Try reseating your RAM as per > iMac (Late 2009) and later: Installing or replacing memory pushing firmly on each module with both thumbs to ensure that they are fully seated.

Then re-run the Extended Apple Hardware Test.

Reply

Answer 2

andrekn Author

Level 1

4 points

Jun 16, 2012 10:07 AM in response to den.thed

Thanks, I'll try that!

The document says you should hear a click when the module is firmly in place. I pressed as hard as seemed sensible to me, but couldn't make out a click. Am I deaf or is this click really not as audible?

Reply

Answer 3

den.thed

Level 9

77,134 points

Jun 16, 2012 10:41 AM in response to andrekn

It's more a feel than an audible click.

Sometimes it helps if someone else steadies the iMac while your seating the modules.

Reply

Answer 4

andrekn Author

Level 1

4 points

Jun 16, 2012 12:16 PM in response to den.thed

There is no way the modules can sit any tighter in their slots than I've got them now. I ran the extended AHT and it came back with no errors. I guess I'll keep an eye on it and if there are any more panics I'll have to wipe my hard drive

Reply

Answer 5

den.thed

Level 9

77,134 points

Jun 16, 2012 12:27 PM in response to andrekn

If it act's up again, see > Resolving Kernel Panics

Reply

Answer 6

andrekn Author

Level 1

4 points

Jun 16, 2012 12:33 PM in response to den.thed

Thanks again for the suggestion. Think I'll let run AHT in Loop Mode over night to see what it comes up with. Any way to deactivate the screen while running AHT?

Reply

Answer 7

rkaufmann87

Level 10

140,478 points

Jun 16, 2012 12:34 PM in response to andrekn

Dennis is absolutely correct, if the KP's continue then it's time to start eliminating which DIMM is failing. Unfortunately AHT is not the most reliable test and failing or failed RAM DIMMs can be a little tricky to locate. A system process of complete elimination (all new RAM) or testing DIMM by DIMM are the only reliable methods.

Reply

Answer 8

andrekn Author

Level 1

4 points

Jun 16, 2012 12:48 PM in response to rkaufmann87

I've tested the DIMMs individually, neither of them reported an error then. And after testing them individually showed no errors, I tested them both together again and there weren't any errors then either. This is what has me so baffled too. Is there an alternative to AHT I could use to "get a second opinion"?

Reply

Answer 9

rkaufmann87

Level 10

140,478 points

Jun 16, 2012 12:49 PM in response to andrekn

Replace all the RAM.

Reply

Answer 10

TildeBee

Level 7

31,917 points

Jun 16, 2012 1:05 PM in response to andrekn

Are the kps still happening?

Reply

Answer 11

den.thed

Level 9

77,134 points

Jun 16, 2012 1:17 PM in response to andrekn

No, at this point I think I would just run it and if the problem reoccurs, then replace the RAM as Roger suggests.

Besides that, if it was just a lose module or a week connection, then there is a pretty good chance that the problem will not return.

Reply

Answer 12

andrekn Author

Level 1

4 points

Jun 16, 2012 1:12 PM in response to TildeBee

I had one this morning, but not since. Before the one this morning I hadn't seen one in 1.5 days though, so I'm reluctant to call the problem solved. I found Rember, which is a GUI for memtest and it reported this error:

FAILURE! Data mismatch at local address 0x000000014ff76ed8

Expected Data: 0xb608bba064e507cd, Actual Data: 0xb600bba064e507cd

which makes me think I need to replace at least one DIMM... Since I bought them in March, I'm still covered by warranty though...

Reply

Answer 13

andrekn Author

Level 1

4 points

Jun 19, 2012 11:48 AM in response to andrekn

For everyone who helped me on this: After the iMac froze up Sunday evening, I swapped the DIMMS for the old ones and it's been running fine since.

Reply

Answer 14

den.thed

Level 9

77,134 points

Jun 19, 2012 4:03 PM in response to andrekn

What RAM did you use when you upgraded, suppliers like OWC, Crucial and others have lifetime warranties.

Upgrade Apple iMac Memory & more – Easy Guide, Free Installation Videos.

Crucial Memory Upgrades for Macs - Apple Memory

Reply

Answer 15

rkaufmann87

Level 10

140,478 points

Jun 19, 2012 4:51 PM in response to andrekn

Dennis is exactly right. The RAM you bought is defective. Check to see what the warranty is, if you purchased from a reputable vendor it probably has a lifetime warranty.

Reply