Kernel Panics on Boot after RAM Upgrade

Question

Level 1

0 points

Kernel Panics on Boot after RAM Upgrade

Hi,

I bought a used 2010 21.5" iMac. It only came with 4 GB of memory, so I decided to order this: http://www.amazon.com/gp/product/B002YUF8ZG/ref=oh_details_o01_s00_i00

I saw that they were DDR3, 1333MHz so they were compatible. Some of the reviews also said it was compatible with this iMac.

It did not work. As the title says, I get a kernel panic on boot. It does not even show the pinwheel when booting up normally. Just the apple logo and some details. My windows partition and recovery do not work either. I am currently writing this from Safe Mode, where it manages to start and recognize the RAM, somehow. Here are the crash details:

Interval Since Last Panic Report: 245846 sec

Panics Since Last Report: 1

Anonymous UUID: C3DFEF06-D5FE-6E98-3C7F-DC1C18E37B78

Fri Jan 18 13:33:08 2013

panic(cpu 0 caller 0xffffff800a443d8e): "a freed zone element has been modified in zone: maps"@/SourceCache/xnu/xnu-2050.18.24/osfmk/kern/zalloc.c:219

Backtrace (CPU 0), Frame : Return Address

0xffffff80ec0c3b20 : 0xffffff800a41d626

0xffffff80ec0c3b90 : 0xffffff800a443d8e

0xffffff80ec0c3bd0 : 0xffffff800a4435d2

0xffffff80ec0c3cb0 : 0xffffff800a4663f7

0xffffff80ec0c3cf0 : 0xffffff800a467398

0xffffff80ec0c3e40 : 0xffffff800a466388

0xffffff80ec0c3f10 : 0xffffff800a7f3538

0xffffff80ec0c3f90 : 0xffffff800a4323cc

0xffffff80ec0c3fb0 : 0xffffff800a4b26b7

BSD process name corresponding to current thread: kernel_task

Boot args: rp=file:///com.apple.recovery.boot/BaseSystem.dmg

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: 0x000000000a200000

Kernel text base: 0xffffff800a400000

System model name: iMac11,2 (Mac-F2238AC8)

System uptime in nanoseconds: 821585069

last loaded kext at 559223612: com.apple.driver.DiskImages.ReadWriteDiskImage 344 (addr 0xffffff7f8afe1000, size 16384)

loaded kexts:

com.apple.driver.DiskImages.ReadWriteDiskImage 344

com.apple.driver.DiskImages.SparseDiskImage 344

com.apple.driver.DiskImages.UDIFDiskImage 344

com.apple.driver.DiskImages.FileBackingStore 344

com.apple.driver.DiskImages.HTTPBackingStore 344

com.apple.driver.DiskImages.RAMBackingStore 344

com.apple.driver.AppleFileSystemDriver 3.0.1

com.apple.AppleFSCompression.AppleFSCompressionTypeDataless 1.0.0d1

com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1

com.apple.BootCache 34

com.apple.iokit.SCSITaskUserClient 3.5.1

com.apple.driver.XsanFilter 404

com.apple.iokit.IOAHCIBlockStorage 2.2.2

com.apple.driver.AirPort.Atheros40 600.70.23

com.apple.iokit.AppleBCM5701Ethernet 3.2.5b3

com.apple.driver.AppleFWOHCI 4.9.6

com.apple.driver.AppleUSBHub 5.2.5

com.apple.driver.AppleUSBUHCI 5.2.5

com.apple.driver.AppleAHCIPort 2.4.1

com.apple.driver.AppleUSBEHCI 5.4.0

com.apple.driver.AppleEFINVRAM 1.6.1

com.apple.driver.AppleRTC 1.5

com.apple.driver.AppleACPIButtons 1.6

com.apple.driver.AppleHPET 1.7

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.39

com.apple.security.quarantine 2

com.apple.driver.AppleIntelCPUPowerManagement 196.0.0

com.apple.driver.DiskImages.KernelBacked 344

com.apple.driver.AppleUSBMergeNub 5.2.5

com.apple.driver.AppleUSBComposite 5.2.5

com.apple.iokit.IOSCSIMultimediaCommandsDevice 3.5.1

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.1

com.apple.iokit.IO80211Family 500.15

com.apple.iokit.IOEthernetAVBController 1.0.2b1

com.apple.iokit.IONetworkingFamily 3.0

com.apple.iokit.IOFireWireFamily 4.5.5

com.apple.iokit.IOUSBUserClient 5.2.5

com.apple.iokit.IOAHCIFamily 2.2.1

com.apple.iokit.IOUSBFamily 5.4.0

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

Model: iMac11,2, BootROM IM112.0057.B01, 2 processors, Intel Core i3, 3.06 GHz, 8 GB, SMC 1.64f5

Graphics: ATI Radeon HD 4670, ATI Radeon HD 4670, PCIe, 256 MB

Memory Module: BANK 0/DIMM1, 4 GB, DDR3, 1333 MHz, 0x029E, 0x434D534F344758334D314131333333433920

Memory Module: BANK 1/DIMM1, 4 GB, DDR3, 1333 MHz, 0x029E, 0x434D534F344758334D314131333333433920

AirPort: spairport_wireless_card_type_airport_extreme (0x168C, 0x8F), Atheros 9280: 4.0.70.23-P2P

Bluetooth: Version 4.0.9f33 10885, 2 service, 18 devices, 0 incoming serial ports

Network Service: Wi-Fi, AirPort, en1

Serial ATA Device: ST3500418AS, 500.11 GB

Serial ATA Device: HL-DT-STDVDRW GA32N, 3.58 GB

USB Device: hub_device, 0x0424 (SMSC), 0x2514, 0xfd100000 / 2

USB Device: HP USB Multimedia Keyboard, 0x0461 (Primax Electronics), 0x4d8a, 0xfd130000 / 5

USB Device: IR Receiver, apple_vendor_id, 0x8242, 0xfd120000 / 4

USB Device: Built-in iSight, apple_vendor_id, 0x8502, 0xfd110000 / 3

USB Device: hub_device, 0x0424 (SMSC), 0x2514, 0xfa100000 / 2

USB Device: Internal Memory Card Reader, apple_vendor_id, 0x8403, 0xfa120000 / 4

USB Device: BRCM2046 Hub, 0x0a5c (Broadcom Corp.), 0x4500, 0xfa110000 / 3

USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x8215, 0xfa111000 / 6

Please help!

iMac, OS X Mountain Lion (10.8.2)

Posted on Jan 18, 2013 5:53 PM

Reply

Answer 1

rkaufmann87

Level 10

140,478 points

Jan 18, 2013 5:55 PM in response to The Doolster

Then you have one of three problems:

Incorrect RAM
Unseated RAM
Failed RAM

If the only thing that changed was adding the RAM then troubleshoot until you figure out which of the three is the issue.

Reply

Answer 2

The Doolster Author

Level 1

0 points

Jan 18, 2013 6:00 PM in response to rkaufmann87

Thanks for the quick reply, but I do not think the issue is with the RAM since I can boot it in safe mode and it can recognise and use the RAM. If the memory was bad could the system still use it? I do not think that would be possible.

Reply

Answer 3

Jan 18, 2013 6:15 PM in response to The Doolster

You might want to check the reviews on Amazon at the link you supplied. Looking at the one star reviews are a buch of complaints about this ram amd mac's and this replie from Cosair

Reply

Answer 4

SeaPapp

Level 7

26,486 points

Jan 18, 2013 6:32 PM in response to The Doolster

The issue is most definately with the ram. Looking at the log I'm wondering Where are the original two 2GB chips? If you leave them in their original slots and put the new ram in the emp slots you *might* have a snowballs chance in hades of getting your Mac to boot properly. You need to return that ram for either a refund or exchange for the Crucial ram that Amazon also sells. Just scan this and any other Mac board and you're going to find that almost everyone will recommend one of two places for Mac ram, Crucial or OWC. I've just become aware of a third vendor that supposedly uses the same brands as Apple and that's MemoryTen but I haven't dealt with them yet.

Reply

Answer 5

Jan 18, 2013 6:37 PM in response to The Doolster

Looking st the iMac ram specs at iMac (Mid 2010): Memory specifications shows PC3-10600. Looking at the Amazon page you linked to shows what you have as PC3-10666.

Macs are really picky abiut their memory, return what you have and get the right ram.

regards

Reply

Answer 6

The Doolster Author

Level 1

0 points

Jan 18, 2013 7:36 PM in response to The Doolster

Thanks for the answers, I will exchange it for some Crucial ram next week. I did not see the reply from Corsair on the review page.

Reply

Answer 7

Jan 18, 2013 7:51 PM in response to The Doolster

Look here at the one star ratings about halfway down the page.

You might want to check out OWC also. They are very good at making sure you get the correct ram.

regards

Message was edited by: Frank Caggiano

Reply

Answer 8

rkaufmann87

Level 10

140,478 points

Jan 18, 2013 8:09 PM in response to The Doolster

The Doolster wrote:

Thanks for the quick reply, but I do not think the issue is with the RAM since I can boot it in safe mode and it can recognise and use the RAM. If the memory was bad could the system still use it? I do not think that would be possible.

Well I see others concur with my assessment and I'm glad they did because it's obvious your issue is RAM related. Glad you're on the right track now though and getting the correct RAM, btw Crucial is a good brand and vendor. Once you have the right stuff in there make sure it's installed (seated) well and your KP's should vanish. Until you have the correct RAM I'd remove the problem RAM because KP's can damage the OS and it would be foolish to leave something installed that you know is creating such an issue.

Reply