iMac kernel panic

Rud3Bwoy

Suspended
Original poster
Oct 9, 2011
433
11
so new imac i restarted today and got a kernel panic had this mac for 2 weeks changed ram to 32 gb and only today got this also here is report

Anonymous UUID: 5BFF8AB9-3190-ED24-6C1D-FED602761069

Sat Aug 9 03:45:08 2014
panic(cpu 0 caller 0xffffff80127dc38d): "ubc_destroy_named: memory_object_destroy failed"@/SourceCache/xnu/xnu-2422.110.17/bsd/kern/ubc_subr.c:1808
Backtrace (CPU 0), Frame : Return Address
0xffffff83b9e6bc10 : 0xffffff8012622f79
0xffffff83b9e6bc90 : 0xffffff80127dc38d
0xffffff83b9e6bce0 : 0xffffff80127dba00
0xffffff83b9e6bd20 : 0xffffff80127dbf60
0xffffff83b9e6bdb0 : 0xffffff80127e4da7
0xffffff83b9e6be10 : 0xffffff80127dd38a
0xffffff83b9e6be50 : 0xffffff80129de59a
0xffffff83b9e6bec0 : 0xffffff80129ece98
0xffffff83b9e6bf50 : 0xffffff8012a40a33
0xffffff83b9e6bfb0 : 0xffffff80126f3f46

BSD process name corresponding to current thread: launchd

Mac OS version:
13E28

Kernel version:
Darwin Kernel Version 13.3.0: Tue Jun 3 21:27:35 PDT 2014; root:xnu-2422.110.17~1/RELEASE_X86_64
Kernel UUID: BBFADD17-672B-35A2-9B7F-E4B12213E4B8
Kernel slide: 0x0000000012400000
Kernel text base: 0xffffff8012600000
System model name: iMac14,2 (Mac-27ADBB7B4CEE8E61)

System uptime in nanoseconds: 18128860669174
last loaded kext at 15669469935353: com.apple.driver.AppleIntelMCEReporter 104 (addr 0xffffff7f94c23000, size 49152)
last unloaded kext at 15765045481295: com.apple.driver.AppleIntelMCEReporter 104 (addr 0xffffff7f94c23000, size 32768)
loaded kexts:
com.apple.driver.AppleBluetoothMultitouch 80.14
com.apple.driver.AudioAUUC 1.60
com.apple.driver.AppleHWSensor 1.9.5d0
com.apple.filesystems.autofs 3.0
com.apple.iokit.IOBluetoothSerialManager 4.2.6f1
com.apple.driver.AppleMikeyHIDDriver 124
com.apple.driver.AGPM 100.14.28
com.apple.driver.ApplePlatformEnabler 2.0.9d6
com.apple.driver.X86PlatformShim 1.0.0
com.apple.driver.AppleMikeyDriver 2.6.3f4
com.apple.driver.AppleHDA 2.6.3f4
com.apple.iokit.IOUserEthernet 1.0.0d1
com.apple.Dont_Steal_Mac_OS_X 7.0.0
com.apple.driver.AppleUpstreamUserClient 3.5.13
com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport 4.2.6f1
com.apple.driver.AppleIntelHD5000Graphics 8.2.8
com.apple.driver.AppleHWAccess 1
com.apple.driver.AppleBacklight 170.3.5
com.apple.GeForce 8.2.6
com.apple.driver.AppleSMCLMU 2.0.4d1
com.apple.driver.AppleThunderboltIP 1.1.2
com.apple.driver.AppleLPC 1.7.0
com.apple.driver.AppleMCCSControl 1.2.5
com.apple.driver.AppleIntelFramebufferAzul 8.2.8
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless 1.0.0d1
com.apple.AppleFSCompression.AppleFSCompressionTypeLZVN 1.0.0d1
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1
com.apple.BootCache 35
com.apple.driver.AppleUSBHub 683.4.0
com.apple.driver.XsanFilter 404
com.apple.iokit.IOAHCIBlockStorage 2.6.0
com.apple.driver.AppleSDXC 1.5.2
com.apple.iokit.AppleBCM5701Ethernet 3.8.1b2
com.apple.driver.AirPort.Brcm4360 842.21.65
com.apple.driver.AppleAHCIPort 3.0.5
com.apple.driver.AppleUSBXHCI 683.4.0
com.apple.driver.AppleRTC 2.0
com.apple.driver.AppleACPIButtons 2.0
com.apple.driver.AppleHPET 1.8
com.apple.driver.AppleSMBIOS 2.1
com.apple.driver.AppleACPIEC 2.0
com.apple.driver.AppleAPIC 1.7
com.apple.nke.applicationfirewall 153
com.apple.security.quarantine 3
com.apple.driver.IOBluetoothHIDDriver 4.2.6f1
com.apple.driver.AppleMultitouchDriver 245.13
com.apple.kext.triggers 1.0
com.apple.iokit.IOSCSIArchitectureModelFamily 3.6.6
com.apple.iokit.IOSerialFamily 10.0.7
com.apple.driver.DspFuncLib 2.6.3f4
com.apple.vecLib.kext 1.0.0
com.apple.iokit.IOAudioFamily 1.9.7fc2
com.apple.kext.OSvKernDSPLib 1.14
com.apple.iokit.IOBluetoothFamily 4.2.6f1
com.apple.iokit.IOBluetoothHostControllerUSBTransport 4.2.6f1
com.apple.iokit.IOSurface 91.1
com.apple.driver.AppleBacklightExpert 1.0.4
com.apple.iokit.IOAcceleratorFamily 98.22
com.apple.nvidia.driver.NVDAGK100Hal 8.2.6
com.apple.nvidia.driver.NVDAResman 8.2.6
com.apple.driver.AppleHDAController 2.6.3f4
com.apple.iokit.IOHDAFamily 2.6.3f4
com.apple.driver.AppleThunderboltEDMSink 2.1.3
com.apple.driver.AppleSMBusPCI 1.0.12d1
com.apple.driver.X86PlatformPlugin 1.0.0
com.apple.driver.AppleSMC 3.1.8
com.apple.driver.IOPlatformPluginFamily 5.7.1d6
com.apple.driver.AppleSMBusController 1.0.12d1
com.apple.AppleGraphicsDeviceControl 3.6.22
com.apple.iokit.IOAcceleratorFamily2 98.22
com.apple.iokit.IONDRVSupport 2.4.1
com.apple.iokit.IOGraphicsFamily 2.4.1
com.apple.driver.AppleUSBHIDKeyboard 170.15
com.apple.driver.AppleHIDKeyboard 170.15
com.apple.iokit.IOUSBHIDDriver 660.4.0
com.apple.driver.AppleUSBMergeNub 650.4.0
com.apple.driver.AppleUSBComposite 656.4.1
com.apple.driver.AppleThunderboltDPInAdapter 3.1.7
com.apple.driver.AppleThunderboltDPOutAdapter 3.1.7
com.apple.driver.AppleThunderboltDPAdapterFamily 3.1.7
com.apple.driver.AppleThunderboltPCIDownAdapter 1.4.5
com.apple.iokit.IOUSBUserClient 660.4.2
com.apple.driver.AppleThunderboltNHI 2.0.1
com.apple.iokit.IOThunderboltFamily 3.3.1
com.apple.iokit.IOEthernetAVBController 1.0.3b4
com.apple.iokit.IO80211Family 640.36
com.apple.driver.mDNSOffloadUserClient 1.0.1b5
com.apple.iokit.IONetworkingFamily 3.2
com.apple.iokit.IOAHCIFamily 2.6.5
com.apple.iokit.IOUSBFamily 683.4.0
com.apple.driver.AppleEFINVRAM 2.0
com.apple.driver.AppleEFIRuntime 2.0
com.apple.iokit.IOHIDFamily 2.0.0
com.apple.iokit.IOSMBusFamily 1.1
com.apple.security.sandbox 278.11.1
com.apple.kext.AppleMatch 1.0.0d1
com.apple.security.TMSafetyNet 7
com.apple.driver.AppleKeyStore 2
com.apple.driver.DiskImages 371.1
com.apple.iokit.IOStorageFamily 1.9
com.apple.iokit.IOReportFamily 23
com.apple.driver.AppleFDEKeyStore 28.30
com.apple.driver.AppleACPIPlatform 2.0
com.apple.iokit.IOPCIFamily 2.9
com.apple.iokit.IOACPIFamily 1.4
com.apple.kec.corecrypto 1.0
com.apple.kec.pthread 1
 

Intell

macrumors P6
Jan 24, 2010
18,872
368
Inside
It does appear to be caused by faulty memory. Run the diagnostics as suggested above.
 

Rud3Bwoy

Suspended
Original poster
Oct 9, 2011
433
11
Run Apple Diagnostics on it: http://support.apple.com/kb/PH11342

Hold down D when you restart to get into Diagnostics. The test takes a couple of minutes and if nothing is wrong it will say "No issues found".
no issues found just ran it

----------

It does appear to be caused by faulty memory. Run the diagnostics as suggested above.
what about the kernel points to ram?

----------

I would swap in your old RAM and see if the KP goes away. If it does, you got some bad RAM.
i only had this error one time since owning the imac for 2 weeks now so it's hard for me to say if it's the ram or not,not a constant issue

----------

also running a memtest now just incase
 

Rud3Bwoy

Suspended
Original poster
Oct 9, 2011
433
11
How the memory object failed for launchd.
i'm running memtest now to be sure also where is the log files saved im using memtest 4.22

ill let it run any issues again ill contact crucial
 

SaSaSushi

macrumors 601
Aug 8, 2007
4,079
470
Takamatsu, Japan
just ran memtest from like 12 to 4 pm all test passed =/
Try running Memtest 86 in multi-CPU Parallel mode. I had a rare bad Crucial DIMM on my first delivery and it passed the normal tests with flying colors but failed in Parallel mode.

Also, I'm not sure if it bears any relevance in this situation, but the DIMMs I returned as bad were low density (8 chips on each side, 16 total) and the working ones I received as a replacement were high density (4 chips each side, 8 total). It probably is not relevant because the 16GB of stock Elpida RAM I added the Crucial to is low density. It was just a case of BAD DIMMs. I ran the multi-CPU Parallel mode Memtest86 for a few hours after taking delivery of these. They've been running panic free for about 5 months now.

The Haswell iMacs are notoriously sensitive with RAM upgrades.
 
Last edited:

steve23094

macrumors 68030
Apr 23, 2013
2,612
1,330
i'm running memtest now to be sure also where is the log files saved im using memtest 4.22

ill let it run any issues again ill contact crucial
I thought Crucial had solved this problem. If you check on their message forums you will see a very long thread from other people with the same problem.

Contact Crucial for a replacement.
 

SaSaSushi

macrumors 601
Aug 8, 2007
4,079
470
Takamatsu, Japan
I thought Crucial had solved this problem. If you check on their message forums you will see a very long thread from other people with the same problem.
Do you mean this thread?

No brand of RAM is immune from the occasional bad DIM.

Contact Crucial for a replacement.
I'd seek a replacement from the retailer you purchased it from before resorting to RMAing it with Micron. It would be a lot faster. I had Amazon USA replace my bad sticks. With Amazon they just ship out your replacement immediately and give you a month to return the old ones (on their dime for the shipping).
 

Rud3Bwoy

Suspended
Original poster
Oct 9, 2011
433
11
Try running Memtest 86 in multi-CPU Parallel mode. I had a rare bad Crucial DIMM on my first delivery and it passed the normal tests with flying colors but failed in Parallel mode.

Also, I'm not sure if it bears any relevance in this situation, but the DIMMs I returned as bad were low density (8 chips on each side, 16 total) and the working ones I received as a replacement were high density (4 chips each side, 8 total). It probably is not relevant because the 16GB of stock Elpida RAM I added the Crucial to is low density. It was just a case of BAD DIMMs. I ran the multi-CPU Parallel mode Memtest86 for a few hours after taking delivery of these. They've been running panic free for about 5 months now.

The Haswell iMacs are notoriously sensitive with RAM upgrades.
mind guiding me how to do that ill re test again,i never ram memtest86 on mac did on windows and was pretty easy not sure how to on mac osx btw ill also be using a usb drive if that makes a difference

how is crucial for replacements?

which memtest should i download as well please point me in the right direction thanks
 
Last edited:

rambo47

macrumors 6502a
Oct 3, 2010
589
101
Denville, NJ
I had a similar situation when I upgraded my Mid-2010 iMac to 16GB from the original 4GB. It took a day or so for the kernel panics to start but once they did they came more and more frequently. When I pulled out two of the 4GB modules and replaced them with my original 2GB modules (12GB total) the kernel panics stopped immediately and the iMac runs like a champ.
 

Rud3Bwoy

Suspended
Original poster
Oct 9, 2011
433
11
I had a similar situation when I upgraded my Mid-2010 iMac to 16GB from the original 4GB. It took a day or so for the kernel panics to start but once they did they came more and more frequently. When I pulled out two of the 4GB modules and replaced them with my original 2GB modules (12GB total) the kernel panics stopped immediately and the iMac runs like a champ.
just got another kernel panic how do i find the kernal panic error again?
 

SaSaSushi

macrumors 601
Aug 8, 2007
4,079
470
Takamatsu, Japan
mind guiding me how to do that ill re test again,i never ram memtest86 on mac did on windows and was pretty easy not sure how to on mac osx btw ill also be using a usb drive if that makes a difference

how is crucial for replacements?

which memtest should i download as well please point me in the right direction thanks
Download and burn the Memtest86 ISO for CD or USB thumb drive from here:

http://memtest86.com/download.htm


Hold down the option key at boot and choose the Memtest86 EFI image and after it starts click on Settings and from there choose the Multi-CPU Parallel mode.

Crucial is great with RMA replacements but if you bought it recently it might be quicker to replace it through the retailer.
 
Last edited:

Rud3Bwoy

Suspended
Original poster
Oct 9, 2011
433
11
Download and burn the Memtest86 ISO for CD or USB thumb drive from here:

http://memtest86.com/download.htm


Hold down the option key at boot and choose the Memtest86 EFI image and after it starts click on Settings and from there choose the Multi-CPU Parallel mode.

Crucial is great with RMA replacements but if you bought it recently it might be quicker to replace it through the retailer.
how do one create a bootable usb for this or do i just drop the files in?
 

Rud3Bwoy

Suspended
Original poster
Oct 9, 2011
433
11
also crucial had me do nvram reset so trying that if no go ill send it back for advanced rma
 

Rud3Bwoy

Suspended
Original poster
Oct 9, 2011
433
11
Try running Memtest 86 in multi-CPU Parallel mode. I had a rare bad Crucial DIMM on my first delivery and it passed the normal tests with flying colors but failed in Parallel mode.

Also, I'm not sure if it bears any relevance in this situation, but the DIMMs I returned as bad were low density (8 chips on each side, 16 total) and the working ones I received as a replacement were high density (4 chips each side, 8 total). It probably is not relevant because the 16GB of stock Elpida RAM I added the Crucial to is low density. It was just a case of BAD DIMMs. I ran the multi-CPU Parallel mode Memtest86 for a few hours after taking delivery of these. They've been running panic free for about 5 months now.

The Haswell iMacs are notoriously sensitive with RAM upgrades.

i ran the multi cpu mode passed 3/4 test almost to 4/4 then stopped it cause seemed like no issues also reset pram lets see if that fixes anything
 

jordanm86

macrumors regular
Oct 21, 2011
223
34
OP,

I had this exact same issue when I bought an iMac last Oct/Nov. I bought a BTO iMac with the minimum amount of RAM and upgraded it myself using HyperX RAM (which was made and listed as compatible with macs and this specific machine) - instant kernel panics.

Ran all the tests, all passed - no faults. Returned the RAM and bought crucial RAM, same issues (passed tests, just caused panics etc).

In the end, I wasted so much time on it, I returned the iMac (had a screen colour issue too) and re-ordered it with 32GB straight from Apple. Overpriced but it stopped the kernel panics.
 

SaSaSushi

macrumors 601
Aug 8, 2007
4,079
470
Takamatsu, Japan
In the end, I wasted so much time on it, I returned the iMac (had a screen colour issue too) and re-ordered it with 32GB straight from Apple. Overpriced but it stopped the kernel panics.
You don't need to go to this extent to solve your problems. Even if it is passing all the tests I'd try an exchange of the Crucial you purchased if the kernel panics are not occurring with the Crucial removed.

Did you add the Crucial to Apple stock RAM? The DIMMs should be in alternating slots if so with the stock RAM in 1 and 3 and the new RAM in slots 2 and 4 or vice versa.
 

Rud3Bwoy

Suspended
Original poster
Oct 9, 2011
433
11
You don't need to go to this extent to solve your problems. Even if it is passing all the tests I'd try an exchange of the Crucial you purchased if the kernel panics are not occurring with the Crucial removed.

Did you add the Crucial to Apple stock RAM? The DIMMs should be in alternating slots if so with the stock RAM in 1 and 3 and the new RAM in slots 2 and 4 or vice versa.
nope all crucial right now system up two days with pram reset no kernel panic and reseated all ram so waiting to see what's going on
 

Rud3Bwoy

Suspended
Original poster
Oct 9, 2011
433
11
Anonymous UUID: 5BFF8AB9-3190-ED24-6C1D-FED602761069

Thu Aug 14 10:49:10 2014
panic(cpu 0 caller 0xffffff8006adc24e): Kernel trap at 0xffffff8006dd2183, type 14=page fault, registers:
CR0: 0x0000000080010033, CR2: 0x0000000000040014, CR3: 0x0000000077e71069, CR4: 0x00000000001606e0
RAX: 0x0000000000000000, RBX: 0x0000000000040000, RCX: 0xffffff83b4d1bcd8, RDX: 0x0000000000000001
RSP: 0xffffff83b4d1bc70, RBP: 0xffffff83b4d1bcc0, RSI: 0xffffff805f807308, RDI: 0x0000000000040000
R8: 0xffffff83b4d1bce0, R9: 0xffffff83b4d1be80, R10: 0x0000000000000434, R11: 0x0000000000000444
R12: 0x0000000000000000, R13: 0x0000000000000001, R14: 0x0000000000000000, R15: 0xffffffffffffffff
RFL: 0x0000000000010202, RIP: 0xffffff8006dd2183, CS: 0x0000000000000008, SS: 0x0000000000000010
Fault CR2: 0x0000000000040014, Error code: 0x0000000000000000, Fault CPU: 0x0

Backtrace (CPU 0), Frame : Return Address
0xffffff83b4d1b900 : 0xffffff8006a22f79
0xffffff83b4d1b980 : 0xffffff8006adc24e
0xffffff83b4d1bb50 : 0xffffff8006af3746
0xffffff83b4d1bb70 : 0xffffff8006dd2183
0xffffff83b4d1bcc0 : 0xffffff8006dd1e30
0xffffff83b4d1bd10 : 0xffffff8006dd158f
0xffffff83b4d1bdf0 : 0xffffff8006bfffca
0xffffff83b4d1be60 : 0xffffff8006dc1b4c
0xffffff83b4d1bed0 : 0xffffff8006dbf1de
0xffffff83b4d1bf20 : 0xffffff8006dc195a
0xffffff83b4d1bf60 : 0xffffff8006e40777
0xffffff83b4d1bfb0 : 0xffffff8006af3c38

BSD process name corresponding to current thread: Google Chrome

Mac OS version:
13E28

Kernel version:
Darwin Kernel Version 13.3.0: Tue Jun 3 21:27:35 PDT 2014; root:xnu-2422.110.17~1/RELEASE_X86_64
Kernel UUID: BBFADD17-672B-35A2-9B7F-E4B12213E4B8
Kernel slide: 0x0000000006800000
Kernel text base: 0xffffff8006a00000
System model name: iMac14,2 (Mac-27ADBB7B4CEE8E61)

System uptime in nanoseconds: 77805220292376
last loaded kext at 77736861281713: com.apple.driver.AppleIntelMCEReporter 104 (addr 0xffffff7f89029000, size 49152)
last unloaded kext at 77800094159864: com.apple.driver.AppleIntelMCEReporter 104 (addr 0xffffff7f89029000, size 32768)
loaded kexts:
com.apple.filesystems.smbfs 2.0.2
com.apple.driver.AudioAUUC 1.60
com.apple.driver.AppleBluetoothMultitouch 80.14
com.apple.driver.AppleHWSensor 1.9.5d0
com.apple.filesystems.autofs 3.0
com.apple.iokit.IOBluetoothSerialManager 4.2.6f1
com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport 4.2.6f1
com.apple.driver.AppleMikeyHIDDriver 124
com.apple.driver.AppleMikeyDriver 2.6.3f4
com.apple.driver.AGPM 100.14.28
com.apple.driver.ApplePlatformEnabler 2.0.9d6
com.apple.driver.X86PlatformShim 1.0.0
com.apple.driver.AppleHDA 2.6.3f4
com.apple.driver.AppleUpstreamUserClient 3.5.13
com.apple.iokit.IOUserEthernet 1.0.0d1
com.apple.GeForce 8.2.6
com.apple.Dont_Steal_Mac_OS_X 7.0.0
com.apple.driver.AppleIntelHD5000Graphics 8.2.8
com.apple.driver.AppleHWAccess 1
com.apple.driver.AppleThunderboltIP 1.1.2
com.apple.driver.AppleSMCLMU 2.0.4d1
com.apple.driver.AppleLPC 1.7.0
com.apple.driver.AppleIntelFramebufferAzul 8.2.8
com.apple.driver.AppleBacklight 170.3.5
com.apple.driver.AppleMCCSControl 1.2.5
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless 1.0.0d1
com.apple.AppleFSCompression.AppleFSCompressionTypeLZVN 1.0.0d1
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1
com.apple.BootCache 35
com.apple.driver.AppleUSBHub 683.4.0
com.apple.driver.XsanFilter 404
com.apple.iokit.IOAHCIBlockStorage 2.6.0
com.apple.driver.AppleSDXC 1.5.2
com.apple.iokit.AppleBCM5701Ethernet 3.8.1b2
com.apple.driver.AirPort.Brcm4360 842.21.65
com.apple.driver.AppleAHCIPort 3.0.5
com.apple.driver.AppleUSBXHCI 683.4.0
com.apple.driver.AppleRTC 2.0
com.apple.driver.AppleACPIButtons 2.0
com.apple.driver.AppleHPET 1.8
com.apple.driver.AppleSMBIOS 2.1
com.apple.driver.AppleACPIEC 2.0
com.apple.driver.AppleAPIC 1.7
com.apple.nke.applicationfirewall 153
com.apple.security.quarantine 3
com.apple.driver.IOBluetoothHIDDriver 4.2.6f1
com.apple.driver.AppleMultitouchDriver 245.13
com.apple.kext.triggers 1.0
com.apple.iokit.IOSerialFamily 10.0.7
com.apple.iokit.IOBluetoothHostControllerUSBTransport 4.2.6f1
com.apple.driver.DspFuncLib 2.6.3f4
com.apple.vecLib.kext 1.0.0
com.apple.iokit.IOAudioFamily 1.9.7fc2
com.apple.kext.OSvKernDSPLib 1.14
com.apple.nvidia.driver.NVDAGK100Hal 8.2.6
com.apple.nvidia.driver.NVDAResman 8.2.6
com.apple.iokit.IOAcceleratorFamily 98.22
com.apple.iokit.IOBluetoothFamily 4.2.6f1
com.apple.iokit.IOSurface 91.1
com.apple.driver.AppleHDAController 2.6.3f4
com.apple.iokit.IOHDAFamily 2.6.3f4
com.apple.driver.AppleSMBusPCI 1.0.12d1
com.apple.driver.X86PlatformPlugin 1.0.0
com.apple.driver.AppleSMC 3.1.8
com.apple.driver.IOPlatformPluginFamily 5.7.1d6
com.apple.driver.AppleThunderboltEDMSink 2.1.3
com.apple.AppleGraphicsDeviceControl 3.6.22
com.apple.iokit.IOAcceleratorFamily2 98.22
com.apple.driver.AppleBacklightExpert 1.0.4
com.apple.iokit.IONDRVSupport 2.4.1
com.apple.driver.AppleSMBusController 1.0.12d1
com.apple.iokit.IOGraphicsFamily 2.4.1
com.apple.driver.AppleUSBHIDKeyboard 170.15
com.apple.driver.AppleHIDKeyboard 170.15
com.apple.iokit.IOUSBHIDDriver 660.4.0
com.apple.driver.AppleUSBMergeNub 650.4.0
com.apple.driver.AppleThunderboltDPOutAdapter 3.1.7
com.apple.driver.AppleThunderboltDPInAdapter 3.1.7
com.apple.driver.AppleThunderboltDPAdapterFamily 3.1.7
com.apple.driver.AppleThunderboltPCIDownAdapter 1.4.5
com.apple.iokit.IOSCSIArchitectureModelFamily 3.6.6
com.apple.driver.AppleUSBComposite 656.4.1
com.apple.iokit.IOUSBUserClient 660.4.2
com.apple.driver.AppleThunderboltNHI 2.0.1
com.apple.iokit.IOThunderboltFamily 3.3.1
com.apple.iokit.IOEthernetAVBController 1.0.3b4
com.apple.iokit.IO80211Family 640.36
com.apple.driver.mDNSOffloadUserClient 1.0.1b5
com.apple.iokit.IONetworkingFamily 3.2
com.apple.iokit.IOAHCIFamily 2.6.5
com.apple.iokit.IOUSBFamily 683.4.0
com.apple.driver.AppleEFINVRAM 2.0
com.apple.driver.AppleEFIRuntime 2.0
com.apple.iokit.IOHIDFamily 2.0.0
com.apple.iokit.IOSMBusFamily 1.1
com.apple.security.sandbox 278.11.1
com.apple.kext.AppleMatch 1.0.0d1
com.apple.security.TMSafetyNet 7
com.apple.driver.AppleKeyStore 2
com.apple.driver.DiskImages 371.1
com.apple.iokit.IOStorageFamily 1.9
com.apple.iokit.IOReportFamily 23
com.apple.driver.AppleFDEKeyStore 28.30
com.apple.driver.AppleACPIPlatform 2.0
com.apple.iokit.IOPCIFamily 2.9
com.apple.iokit.IOACPIFamily 1.4
com.apple.kec.corecrypto 1.0
com.apple.kec.pthread 1

another one going to do rma today for
 

SaSaSushi

macrumors 601
Aug 8, 2007
4,079
470
Takamatsu, Japan
nope all crucial
Well then, the key is whether the panics persist with the Crucial out and the Apple stock RAM back in.

Anonymous UUID: 5BFF8AB9-3190-ED24-6C1D-FED602761069

Thu Aug 14 10:49:10 2014
panic(cpu 0 caller 0xffffff8006adc24e): Kernel trap at 0xffffff8006dd2183, type 14=page fault, registers:

another one going to do rma today for
Crucial is pretty good with RMAs (unlike Seagate Singapore, who I've been dealing with for a HDD RMA for a month). You can find out the RMA process in their forums.

A replacement set should resolve things for you but do post back with your results.
 

Rud3Bwoy

Suspended
Original poster
Oct 9, 2011
433
11
Well then, the key is whether the panics persist with the Crucial out and the Apple stock RAM back in.



Crucial is pretty good with RMAs (unlike Seagate Singapore, who I've been dealing with for a HDD RMA for a month). You can find out the RMA process in their forums.

A replacement set should resolve things for you but do post back with your results.
noticed this on all the kernel panics

BSD process name corresponding to current thread: Google Chrome


?

is it from chrome and not the ram?but first kenral said bsd launchd