Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

5K iMac kernel panics...

W

WilliamG

macrumors G4
Original poster
Mar 29, 2008
10,011
3,894
Seattle
I can't figure this out. My 5K iMac - which has been without issue since launch in late 2014, has been crashing a lot on me this past week. There's been no changes to devices or peripherals. It crashes on average about once per day now. Running 10.10.3.

The last time it crashed was during the night. I had gone to bed around 1am, putting the display (not the system) to sleep at that point.

At 4:20am, it crashed.

I got to my computer later this morning, and this is the report:

Thu Apr 23 09:49:46 2015

*** Panic Report ***
panic(cpu 4 caller 0xffffff8005bc1cde): "launchd died\nState at Last Exception:\n\n"@/SourceCache/xnu/xnu-2782.20.48/bsd/kern/kern_exit.c:363



Now, I'm usually pretty good at troubleshooting computers, but this one is rather uninformative...

Here's the one it did yesterday:

Wed Apr 22 20:14:09 2015

*** Panic Report ***
panic(cpu 2 caller 0xffffff800a5c1cde): "launchd died\nState at Last Exception:\n\n"@/SourceCache/xnu/xnu-2782.20.48/bsd/kern/kern_exit.c:363
 
Fresh install... went 2.5 days on 24/7 (not ever asleep). Come to it just now after not touching it for about 12 hours and it wakes up - freezes, black screen, kernel panic, shutdown.

Sun Apr 26 13:47:02 2015

*** Panic Report ***
panic(cpu 6 caller 0xffffff801d3c1cde): "launchd died\nState at Last Exception:\n\n"@/SourceCache/xnu/xnu-2782.20.48/bsd/kern/kern_exit.c:363


I've seriously no idea what's going on here...
 
redheeler said:
If you haven't installed anything recently that might be causing this, try an OS reinstall.
Click to expand...

Read the post before you posted. I just did 2 days ago to try and solve it. :)

----------

I just ran a memory test (Rember - which is a GUI for memtest. It threw this up:


Memtest version 4.22 (64-bit)
Copyright (C) 2004 Charles Cazabon
Copyright (C) 2004-2008 Tony Scaminaci (Macintosh port)
Licensed under the GNU General Public License version 2 only

Mac OS X 10.10.3 (14D136) running in multiuser mode
Memory Page Size: 4096
System has 8 Intel core(s) with SSE
Requested memory: 27241MB (28564537344 bytes)
Available memory: 27241MB (28564537344 bytes)
Allocated memory: 27241MB (28564537344 bytes) at local address 0x0000000101000000
Attempting memory lock... locked successfully
Partitioning memory into 2 comparison buffers...
Buffer A: 13620MB (14282268672 bytes) starts at local address 0x0000000101000000
Buffer B: 13620MB (14282268672 bytes) starts at local address 0x00000004544a2000

Running 1 test sequence... (CTRL-C to quit)

Test sequence 1 of 1:

Running tests on full 27241MB region...
Stuck Address : setting 1 of 16 ok
Linear PRN : setting 1 of 16 ok
Running comparison tests using 13620MB buffers...
Random Value : \ ok
Compare XOR :  ok
Compare SUB :  ok
Compare MUL :  ok
Compare DIV :  ok
Compare OR :  ok
Compare AND :  ok
Sequential Increment:  ok
Solid Bits : setting 1 of 64

FAILURE! Data mismatch at local BUFA address 0x00000001d5657670, BUFB address 0x0000000528af9670
BUFA Data: 0x0000000200000000, BUFB Data: 0x0000000000000000

Block Sequential : setting 1 of 256
 
Cape Dave said:
I had similar weird issues at one point. A fresh install and changing energy saver settings to this worked perfectly!

https://www.dropbox.com/s/o177xghyie8gu2v/Screenshot 2015-04-26 20.39.02.png?dl=0
Click to expand...

I would think all that setting is doing is a bandaid to cover up what is wrong rather than fix the issue.

WilliamG: I am going to guess that you have like many here, bought the base 8gb ram and put in/upgrade/changed the memory inside the machine to non OEM ram??

I was told once that the only way to really test memory is to do it one simm at a time as modern cpu's use interleaving the memory and a pair of bad simms can cover up a problem that will show if you test each simm by itself.

I had a similar issue with a windows computer that would die if it ever went into sleep mode. Turned out to be a ram issue that I figured out once I tested each simm individually.
 
DeltaMac said:
Adding to previous post, you can also try reseating your memory sticks.

Do you get any error codes after running your Diagnostic test?
Click to expand...

Diagnostics revealed nothing. I took out two sticks (I have 32GB/4x8GB). I ran Memtest on my iMac on two, and put the other two in my Mac mini 2012 (to save time). Memtest on two sticks revealed no issues on the iMac, and the Mac mini found errors on the other two - likely just one of the sticks. I still need to figure out which one later tonight.

These sticks have worked fine for 2.5 years, since they were in my 2012 iMac before my 5K. They are all Corsair Vengeance.

----------
roadkill401 said:
I would think all that setting is doing is a bandaid to cover up what is wrong rather than fix the issue.

WilliamG: I am going to guess that you have like many here, bought the base 8gb ram and put in/upgrade/changed the memory inside the machine to non OEM ram??

I was told once that the only way to really test memory is to do it one simm at a time as modern cpu's use interleaving the memory and a pair of bad simms can cover up a problem that will show if you test each simm by itself.

I had a similar issue with a windows computer that would die if it ever went into sleep mode. Turned out to be a ram issue that I figured out once I tested each simm individually.
Click to expand...

I think one of the sticks just crapped out, really. I think I'll survive with 24GB RAM while I RMA one of the sticks. :) As my earlier post shows, memtest found issues with all 4 in there. Again, bear in mind I had been using these sticks for 2.5 years prior to these issues. Anyway, I'll know later exactly which stick it is and then I'll smash it with a hammer.

Or RMA it.
 
Boy, it's not easy at times. So the 2012 Mac mini found errors on the 2x8GB I put in it, but not on either stick individually. And now the iMac is not finding errors on any of the sticks now that they've (undoubtedly) been swapped around.

Not sure what to think now...
 
A reseat can be a good fix, particularly with RAM sticks.
It's a troubleshooting tip that I have heard (and used) since I first worked on computers more than 25 years ago.
 
DeltaMac said:
A reseat can be a good fix, particularly with RAM sticks.
It's a troubleshooting tip that I have heard (and used) since I first worked on computers more than 25 years ago.
Click to expand...

Yep, indeed! Still running more tests, but hopefully the reseat really is the issue. Would make life a lot simpler, that's for sure.
 
Computer crashed today after uptime of a hair under three days. All I was doing was trying to open XBMC, and bam, computer froze, beachball, screen black, grey screen of death, auto-reboot.

Same error as is now common on this computer.. :(

Anonymous UUID: 26BCB5D7-B480-DE46-B095-53FAAFC79B19

Sat May 2 13:13:04 2015

*** Panic Report ***
panic(cpu 0 caller 0xffffff8018fc1e8e): "launchd died\nState at Last Exception:\n\n"@/SourceCache/xnu/xnu-2782.30.2/bsd/kern/kern_exit.c:363

uuid info:
0x7fff5ffb4000 uuid = <72a99d0f-0b56-3938-abc5-67a0f33757c4>
0x10d3d6000 uuid = <fa0a4792-3a82-3011-8129-31c1ce69d4c8>
0x10d423000 uuid = <4396b358-725e-3ec0-bcbb-e4bf75fe1fb0>

RAX: 0x0000000002000001, RBX: 0x0000000000000006, RCX: 0x000000010d5760e8, RDX: 0x0000000000000000
RSP: 0x000000010d5760e8, RBP: 0x000000010d576190, RSI: 0x000000010d575f40, RDI: 0x0000000000000001
R8: 0x0000000000000000, R9: 0x000000010d4159f0, R10: 0x00007fff825dcb02, R11: 0x0000000000000206
R12: 0x0000000000000000, R13: 0x00007fff837bb7e0, R14: 0x000000010d5765d0, R15: 0x000000010d576790
RFL: 0x0000000000000206, RIP: 0x00007fff825da95a, CS: 0x0000000000000007, SS: 0x0000000000000023

Thread 0xffffff8056729000
0x00007fff8aed7f4b
0x00007fff8aed8068
0x00007fff8aed1554
0x00007fff8b880a6c
0x000000010d4048f7
0x00007fff8bcbbc13
0x00007fff8bcbe88f
0x00007fff8bcccfe4
0x00007fff8bd3e637
0x00007fff8bd3c40d
0x0000000000000000

Thread 0xffffff8056630970
0x00007fff8bcbea6a
0x0000000000000000

Thread 0xffffff805639a000
0x000000010d3edc81
0x00007fff8bcbbc13
0x00007fff8bcbf365
0x00007fff8bcc0ecc
0x00007fff8bcbe6b7
0x00007fff8bcccfe4
0x00007fff8bd3e637
0x00007fff8bd3c40d
0x0000000000000000

Thread 0xffffff805672a798
0x00007fff8bccc3ad
0x0000000000000000

Thread 0xffffff805cb05970
0x00007fff89f55f1a
0x00007ff993f45170
0x00007fff5ffc0455
0x00007fff8213e7b5
0x00007fff8aea67e8
0x00007fff837bb7e0
0x00007fff837bdddf
0x00007fff8bcbbc13
0x00007fff8bcbce5e
0x00007fff837bc0a7
0x000000010d401383
0x00007fff8bcbbc13
0x00007fff8bcbf365
0x00007fff8bcc0ecc
0x00007fff8bcbf154
0x00007fff8bcc0ecc
0x00007fff8bcbe6b7
0x00007fff8bcccfe4
0x00007fff8bd3e637
0x00007fff8bd3c40d
0x0000000000000000

Thread 0xffffff805da90970
0x00007fff8bd3c40d
0x0000000000000000

Thread 0xffffff805bf45000
0x00007fff8bcbe468
0x00007fff8bd3e268
0x00007fff8bd3e1e5
0x00007fff8bd3c41d
0x0000000000000000

Mac OS version: 14E11f
Kernel version: Darwin Kernel Version 14.4.0: Sun Apr 19 20:30:19 PDT 2015; root:xnu-2782.30.2~2/RELEASE_X86_64
Kernel UUID: 1E1DDCBE-ACFE-3F79-8ECA-183621040C0D
System model name: iMac15,1 (Mac-FA842E06C61E91C5)
Model: iMac15,1, BootROM IM151.0207.B01, 4 processors, Intel Core i7, 4 GHz, 32 GB, SMC 2.23f11
Graphics: AMD Radeon R9 M295X, AMD Radeon R9 M295X, PCIe, 4096 MB
Memory Module: BANK 0/DIMM0, 8 GB, DDR3, 1600 MHz, 0x029E, 0x434D5358384758334D314131363030433130
Memory Module: BANK 1/DIMM0, 8 GB, DDR3, 1600 MHz, 0x029E, 0x434D5358384758334D314131363030433130
Memory Module: BANK 0/DIMM1, 8 GB, DDR3, 1600 MHz, 0x029E, 0x434D5358384758334D314131363030433130
Memory Module: BANK 1/DIMM1, 8 GB, DDR3, 1600 MHz, 0x029E, 0x434D5358384758334D314131363030433130
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x142), Broadcom BCM43xx 1.0 (7.15.166.24.3)
Bluetooth: Version 4.3.5f1 15718, 3 services, 27 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en1
PCI Card: pci1b21,612, AHCI Controller, Thunderbolt@10,0,0
PCI Card: pci1b73,1100, USB eXtensible Host Controller, Thunderbolt@194,0,0
PCI Card: ethernet, Ethernet Controller, Thunderbolt@193,0,0
Serial ATA Device: APPLE SSD SD0128F, 121.33 GB
Serial ATA Device: APPLE HDD ST3000DM001, 3 TB
Serial ATA Device: Samsung SSD 850 EVO 1TB, 1 TB
USB Device: USB3.0 Media Reader
USB Device: Elgato Thunderbolt 2 Dock Audio
USB Device: FaceTime HD Camera (Built-in)
USB Device: BRCM20702 Hub
USB Device: Bluetooth USB Host Controller
USB Device: USB2.0 Hub
USB Device: G700s Rechargeable Gaming Mouse
USB Device: Xbox 360 Wireless Receiver for Windows
Thunderbolt Bus: iMac, Apple Inc., 26.1
Thunderbolt Device: GoFlex Adapter Thunderbolt, Seagate, 1, 9.3
Thunderbolt Device: Thunderbolt 2 Dock, Elgato Systems, 3, 25.1
 
WilliamG said:
Computer crashed today after uptime of a hair under three days. All I was doing was trying to open XBMC, and bam, computer froze, beachball, screen black, grey screen of death, auto-reboot.

Same error as is now common on this computer.. :(
...

Mac OS version: 14E11f
...
Click to expand...

When you upgraded to the 10.10.4 beta, then you also increase your risk that one or another application that you use may be unstable, or problems within the system itself. Running the beta when you are already experiencing some challenges may not be your best course of action.
However, you could also support the beta by providing Apple with your crash report.
 
DeltaMac said:
When you upgraded to the 10.10.4 beta, then you also increase your risk that one or another application that you use may be unstable, or problems within the system itself. Running the beta when you are already experiencing some challenges may not be your best course of action.
However, you could also support the beta by providing Apple with your crash report.
Click to expand...

I should clarify. I upgraded to 10.10.4 beta BECAUSE of the kernel panics. Note, I was using 10.10.3 up until I got sick to death of the same kernel panic over and over. I'm still having the same kernel panic after updating.
 
WilliamG said:
I should clarify. I upgraded to 10.10.4 beta BECAUSE of the kernel panics. Note, I was using 10.10.3 up until I got sick to death of the same kernel panic over and over. I'm still having the same kernel panic after updating.
Click to expand...

I can understand that you can always hope that a system update can fix, or at least help out with your issues. Maybe that can happen.
Did you also use XBMC, without issue, at other times during that 3-day period - or was that the first time since upgrading to the beta (as far as you know)
I guess what I am asking is - do you think that launching XBMC was just a coincidence, or do you think it directly contributed to a quick crash?
 
DeltaMac said:
I can understand that you can always hope that a system update can fix, or at least help out with your issues. Maybe that can happen.
Did you also use XBMC, without issue, at other times during that 3-day period - or was that the first time since upgrading to the beta (as far as you know)
I guess what I am asking is - do you think that launching XBMC was just a coincidence, or do you think it directly contributed to a quick crash?
Click to expand...

It's 100% not related. The crash happens doing anything (just browsing Macrumors in Safari, for example), or even during the night when the screen is off (system never sleeps).

It's annoying that it's so infrequent. Generally happens between once a day and once every three days. Again, system never sleeps. Just the screen turns off.
 
I'm at a loss. Ran memory tests on each stick individually in single user mode. No errors after about 12 hours of testing today.

The only thing else it could be is the Thunderbolt 1TB Samsung 850 Evo that I use as my boot drive, but it's been working fine since January, so I'm not really sure why it would suddenly be an issue (the RAM I've had since late 2012).

Don't suppose anyone has any ideas before I start crying?
 
WilliamG said:
I'm at a loss. Ran memory tests on each stick individually in single user mode. No errors after about 12 hours of testing today.

The only thing else it could be is the Thunderbolt 1TB Samsung 850 Evo that I use as my boot drive, but it's been working fine since January, so I'm not really sure why it would suddenly be an issue (the RAM I've had since late 2012).

Don't suppose anyone has any ideas before I start crying?
Click to expand...

You really should try the original ram just to be sure. Memtest usually turns up something within ~5 cycles per stick. There isn't anything in the core dump to really implicate that drive. Ram is still the most probable cause.
 
thekev said:
You really should try the original ram just to be sure. Memtest usually turns up something within ~5 cycles per stick. There isn't anything in the core dump to really implicate that drive. Ram is still the most probable cause.
Click to expand...

I don't actually have any of the original RAM. Not helpful, right? :)

I've run the memory test 3x loop per stick in single user mode from the command line. No errors at all. I'm right now over night running a 10x loop on all 4 sticks.

If there are no errors at that point, I'm lost. :(
 
Last edited:
WilliamG said:
I don't actually have any of the original RAM. Not helpful, right? :)

I've run the memory test 3x loop per stick in single user mode from the command line. No errors at all. I'm right now over night running a 10x loop on all 4 sticks.

If there are no errors at that point, I'm lost. :(
Click to expand...

Just curious, does this issue happen when booting from the internal Fusion Drive?

Have you tried a clean install as well?
 
yjchua95 said:
Just curious, does this issue happen when booting from the internal Fusion Drive?

Have you tried a clean install as well?
Click to expand...

I'm on a clean install right now. Did a completely fresh install earlier in the week to try and address this issue.

I don't know if fusion drive install will work correctly, either. It didn't use to have this issue until it started about 6 months into ownership, and about 4 months into the install to a Thunderbolt SSD. Nothing changed, and nothing new was installed.
 
WilliamG said:
I'm on a clean install right now. Did a completely fresh install earlier in the week to try and address this issue.

I don't know if fusion drive install will work correctly, either. It didn't use to have this issue until it started about 6 months into ownership, and about 4 months into the install to a Thunderbolt SSD. Nothing changed, and nothing new was installed.
Click to expand...

Hmm. I always experience kernel panics on several of my Macs (always the same errors - freed zone element modified in ... or either invalid allocation).

I did several RAM tests and they all turned out fine. And also perhaps not surprisingly, these Macs all had Norton installed on them (as required by my workplace).

Here's the relevant thread that I started: https://forums.macrumors.com/threads/1869072/
 
yjchua95 said:
Hmm. I always experience kernel panics on several of my Macs (always the same errors - freed zone element modified in ... or either invalid allocation).

I did several RAM tests and they all turned out fine. And also perhaps not surprisingly, these Macs all had Norton installed on them (as required by my workplace).

Here's the relevant thread that I started: https://forums.macrumors.com/threads/1869072/
Click to expand...

Your issue is quite different to mine, though, it appears.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back