|
|
#1 |
|
Kernel Panic at boot - RAM Issue
I have a 15-inch mid-2010 MBP running Mountain Lion, that I upgraded from 4 to 8 Gb of memory in Sept. 2012. The memory i purchased was a 2x4 gb set of Corsair Value rated at 1333 MHz. The upgrade went smooth, and i did not have any problems for a few months.
Then late in december or early in january, I had a few Kernel Panics. I didn't think too much of it, as I was busy with exams, and thought it might be a software issue or something, maybe related to VMware Fusion. The KP's started getting a bit more frequent, and suddenly one day the machine wouldn't boot at all, it just KP's at the Apple logo and then goes in a loop. I now suspected a memory problem, as my experience tells me that this is a usual cause of KP's. I started fiddling with the memory sticks, and determined that one of the blocks would boot, so i went to the place i bought the set and talked to them. They agreed that the one block was probably faulty, and replaced my memory with a 2x4 Gb set of Corsair Mac Memory. This is 1066 MHz CL7, and should be compatible with MB,MBP and iMac, according to the packaging. The problem is that the machine will not boot with this memory either. It just goes for the same loop and KP's at the Apple logo. I can't even get this to boot with one stick in the machine, so it's arguably worse. The machine works well with the original memory, It's been a rock solid main machine with 4Gb of ram for about a month now. I tried PRAM and SMC reset to no avail. I tried booting into boot camp with the new memory, but it just never seems to load Windows. This also works with the old memory. I've tried the memory in a friends HP PC, where it boots with no problems at all. I've also tried running Rember in Safe Mode overnight, and the machine was still running when I got up in the morning. I've attached the most recent KP log. Can anyone figure out the problem? Edit: Oh, I should add that I have replaced my optical drive with an SSD that i boot OS X from. This was done about two years ago, a has not caused problems. Windows boots from the HDD. Code:
Wed Feb 20 14:35:01 2013 panic(cpu 0 caller 0xffffff8009c43d8e): "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 0xffffff80ec313b20 : 0xffffff8009c1d626 0xffffff80ec313b90 : 0xffffff8009c43d8e 0xffffff80ec313bd0 : 0xffffff8009c435d2 0xffffff80ec313cb0 : 0xffffff8009c663f7 0xffffff80ec313cf0 : 0xffffff8009c67398 0xffffff80ec313e40 : 0xffffff8009c66388 0xffffff80ec313f10 : 0xffffff8009ff3538 0xffffff80ec313f90 : 0xffffff8009c323cc 0xffffff80ec313fb0 : 0xffffff8009cb26b7 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: 0x0000000009a00000 Kernel text base: 0xffffff8009c00000 System model name: MacBookPro6,2 (Mac-F22586C8) System uptime in nanoseconds: 1255606831 last loaded kext at 522264221: com.apple.driver.AppleFileSystemDriver 3.0.1 (addr 0xffffff7f8bf1d000, size 16384) loaded kexts: 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.driver.XsanFilter 404 com.apple.iokit.IOAHCIBlockStorage 2.2.2 com.apple.driver.AppleUSBHub 5.2.5 com.apple.driver.AppleFWOHCI 4.9.6 com.apple.iokit.AppleBCM5701Ethernet 3.2.5b3 com.apple.driver.AirPort.Brcm4331 602.15.22 com.apple.driver.AppleUSBUHCI 5.2.5 com.apple.driver.AppleAHCIPort 2.4.1 com.apple.driver.AppleUSBEHCI 5.4.0 com.apple.driver.AppleSmartBatteryManager 161.0.0 com.apple.driver.AppleEFINVRAM 1.6.1 com.apple.driver.AppleACPIButtons 1.6 com.apple.driver.AppleRTC 1.5 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.AppleUSBMergeNub 5.2.5 com.apple.driver.AppleUSBComposite 5.2.5 com.apple.iokit.IOUSBUserClient 5.2.5 com.apple.iokit.IOFireWireFamily 4.5.5 com.apple.iokit.IOEthernetAVBController 1.0.2b1 com.apple.iokit.IO80211Family 500.15 com.apple.iokit.IONetworkingFamily 3.0 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 |
|
|
|
0
|
|
|
#2 | |
|
Quote:
|
||
|
|
0
|
|
|
#3 | |
|
Quote:
What I don't get is that it used to work, but has now stopped. I would think it's the memory controller, but I don't get how it has problems with 8 gb, but not with 4 gb. I don't get how it has deteriorated like that either. And I don't get how it can work pretty well in Fail Safe mode, but then again, that mode IS Fail Safe, and I don't know what they did to make it so... |
||
|
|
0
|
|
|
#4 | |
|
Quote:
|
||
|
|
0
|
|
|
#5 |
|
|
0
|
|
|
#6 |
|
Bump?
|
|
|
|
0
|
![]() |
|
«
Previous Thread
|
Next Thread
»
| Thread Tools | Search this Thread |
| Display Modes | |
|
|
All times are GMT -5. The time now is 03:07 AM.








Linear Mode
