How to handle a Kernel Panic.

Question

How to handle a Kernel Panic.

So I've been having Kernel Panics and crashes on my 2008 24 inch Desktop recently. So I went into Safe Mode and used my console utility after doing some research and found this:

*** Panic Report ***

panic(cpu 0 caller 0xffffff802019b084): launchd exited (signal 9, exit status 0 CS_KILLED)

uuid info:

0x7fff6eecd000 uuid = <dc81cc9d-651a-3a45-8809-928282052bd3>

0x10e2d4000 uuid = <48362449-4519-317e-9a8b-7524036de5ea>

0x10e325000 uuid = <012548cd-614d-3af0-b3b1-676f427d2cd6>

0x10e331000 uuid = <d55d5807-1fbe-32a5-9105-44d7afe68c27>

0x10e782000 uuid = <82e2270e-4577-3465-8fc3-90e05455237c>

0x10e78a000 uuid = <7e14504c-a8b0-3574-b6eb-5d5fabc72926>

0x10e7a4000 uuid = <9548aae9-2ab7-3525-9ece-a2a7c4688447>

0x10e7b5000 uuid = <93732261-34b4-3914-b7a2-90a81a182dba>

0x10e7d4000 uuid = <a13ecf69-f59f-38ae-8609-7b731450fbcd>

0x10e7f0000 uuid = <a48637bc-f3f2-34f2-bb68-4c65fd012832>

0x10e800000 uuid = <b5c05fd7-a540-345a-87bf-8e41848a3c17>

0x10e895000 uuid = <c7499857-61a5-3d7d-a5ea-65dcc8c3df92>

0x10e8ec000 uuid = <25d28225-99ae-3a04-b98c-acff47d6d9b0>

0x10e8fb000 uuid = <8371ce54-5fdd-3ce9-b3df-e98c761b6fe0>

0x10e905000 uuid = <834ed605-5114-3641-aa4d-ecf31b801c50>

0x10e913000 uuid = <318264fa-58f1-39d8-8285-1f6254ee410e>

0x10e920000 uuid = <0f4169f0-0c84-3a25-b3ae-e47b3586d908>

0x10e929000 uuid = <552ef39e-14d7-363e-9059-4565ac2f894e>

0x10e930000 uuid = <41f8e11f-1bd0-3f1d-ba3a-aa1577ed98a9>

0x10e956000 uuid = <1244d9d5-f6aa-35bb-b307-86851c24b8e5>

0x10e95d000 uuid = <28733d22-553e-3cbc-8d2c-edceb46e46af>

0x10ea18000 uuid = <3deb7df9-6804-37e1-bc83-0166882ff0ff>

0x10ea27000 uuid = <1b3f5afc-ffcd-3ecb-8b9a-5538366fb20d>

0x10ea34000 uuid = <c90dae38-4082-381c-a185-2a6a8b677628>

0x10ea59000 uuid = <80189998-32b0-316c-b5c5-53857486713d>

0x10ea6c000 uuid = <faa9226d-64de-3769-a6d8-6caba4b7ff4d>

0x10eaaf000 uuid = <a3f069ea-6a41-35ca-bdf8-187e0209b3e2>

0x10eae9000 uuid = <08e1a4b2-6448-3dfe-a58c-acc7335be7e4>

0x10eb28000 uuid = <5748e8b2-f81c-34c6-8b13-456213127678>

0x10eb53000 uuid = <b52dab73-92dc-3da7-b9f4-b899d66445c1>

0x10ebf7000 uuid = <66095dc7-6539-38f2-95ee-458f15f6d014>

0x10ec11000 uuid = <d48bde34-0f7e-34ca-a0ff-c578e39987cc>

0x10ec2a000 uuid = <29a905ef-6777-3c33-82b0-6c3a88c4ba15>

0x10ec3e000 uuid = <3dd1ef4c-1d1b-3abf-8cc6-b3b1ceee9559>

0x10ec5c000 uuid = <2a68b39c-b786-3a05-87a2-56e688469fb8>

0x10ec66000 uuid = <32b1a8c6-dc84-3f4f-b8ce-9a52b47c3e6b>

0x10ec72000 uuid = <e9311c03-9e61-3b13-af3f-a64956fff269>

0x10ec93000 uuid = <ddb1e947-c775-33b8-b461-63e5eb698f0e>

0x10ec9e000 uuid = <f6eb48e5-4d12-359a-ab54-c937fbbe9043>

0x10ecad000 uuid = <54d1328e-054e-3daa-89e2-375722f9d18f>

0x10ecf5000 uuid = <999e610f-41fc-32a3-adca-5ec049b65dfb>

0x10ed57000 uuid = <922efb36-0e9e-315b-8270-e81ac43472c0>

0x10ed96000 uuid = <8fc3d139-8055-3498-9ac5-6467cb7f4d14>

0x10ee47000 uuid = <4243b6b4-21e9-355b-9c5a-95a216233b96>

Thread 5 crashed

RAX: 0x0000000000000000, RBX: 0x00007fff6ef0d5f8, RCX: 0x000000010e2d4a00, RDX: 0x000000010e31c7b8

RSP: 0x000070000021c790, RBP: 0x000070000021c810, RSI: 0x00000000000015d3, RDI: 0x00007fff6ef0d5f8

R8: 0x000000010e8ed119, R9: 0x00007fbaf0c03190, R10: 0x0000000004001080, R11: 0x000000010e314170

R12: 0x00007fbaf10e6058, R13: 0x0000000000000000, R14: 0x0000000000000000, R15: 0x000000010e31bc53

RFL: 0x0000000000010246, RIP: 0x00007fff6eee74d0, CS: 0x000000000000002b, SS: 0x0000000000000023

Thread 0: 0xffffff8027d2bb60

Could not read LR from frame at 0x0000700000080d48

Thread 1: 0xffffff8027d2a000

0x000000010e89cdcd

0x0000000000000000

Thread 2: 0xffffff8027dd0db0

0x000000010e8ab7b5

0x0000000000000000

Thread 3: 0xffffff80296cbdb0

0x000000010e8a7675

0x000000010e89ba83

0x000000010e89c200

0x000000010e8a2707

0x000000010e89ad53

0x000000010e89ab00

0x000000010ec414de

0x000000010ec3f341

0x0000000000000000

Thread 4: 0xffffff802a83e920

0x000000010ec3f341

0x0000000000000000

Thread 5: 0xffffff802988b920

0x00007fff6eed1063

0x000000010e8ed262

0x000000010e314170

0x000000010e2e5b57

0x000000010e2e54a0

0x000000010e2e9b95

0x000000010e89740b

0x000000010e8a7675

0x000000010e89ba83

0x000000010e89c200

0x000000010e8a2707

0x000000010e89ad53

0x000000010e89ab00

0x000000010ec414de

0x000000010ec3f341

0x0000000000000000

Mac OS version: 15G1010

Kernel version: Darwin Kernel Version 15.6.0: Mon Aug 29 20:21:34 PDT 2016; root:xnu-3248.60.11~1/RELEASE_X86_64

Kernel UUID: E349749B-3303-3DDF-959C-B5885A0E1F6E

System model name: iMac8,1 (Mac-F227BEC8)

So where do I go from here?

iMac Line (2012 and Later)

Posted on Jan 4, 2019 12:50 AM

Reply

Answer 1

Best reply

SeaPapp

Level 7

26,486 points

Jan 4, 2019 2:46 AM in response to Dreamershearts

Although that says panic report I've never seen a kernel panic that looked like that, I don't know how to read that. Possibly something here will help you http://www.thexlab.com/faqs/kernelpanics.html

Or Apples advice If your Mac spontaneously restarts or displays a message that it restarted or shut down because of a problem - Apple Support

Reply

Answer 2

K Shaffer

Level 8

35,002 points

Jan 5, 2019 2:34 AM in response to Dreamershearts

A more detailed and therefore time consuming troubleshooting effort may be more involved.

These kernel panic issues can be caused by software, hardware ~ or a combination of both.

And to try & decipher the meaning of the details you may see in other system log files can

be a source of additional answers; or a means to determine which way to go next. Also an

older Mac could have hidden issues. A kernel panic could be caused by graphic card, hard

disk drive, memory (RAM) failure, software incompatibility, among other disparate issues.

•Technical Note TN2063: Understanding and Debugging Kernel Panics

https://developer.apple.com/library/archive/technotes/tn2063/_index.html

• Resolving Kernel Panics - troubleshooting - xlabs addendum:

http://www.thexlab.com/faqs/kernelpanics.html#Anchor-Troubleshooting-49575

Although some of these kernel related links may seem outdated (or PPC vs Intel)

their basic construct is helpful if you can understand where they vary or converge.

I've experienced several kinds of kernel panics; some can be worked around with

effort and eventual resolution found. {You could also try 'safe' mode restart as part

of troubleshooting the hardware and software.} Some old early Intel-based iMacs

could have several wear related or time related causes. A read-write error with a

damaged hard drive can also cause odd and problematic panic reports.

• Use 'safe' mode to isolate issues with your Mac - Apple Support:

https://support.apple.com/en-us/HT201262

Reply

Answer 3

Jan 4, 2019 10:44 PM in response to SeaPapp

Okay, I had another panic while troubleshooting my mac and this was the report:

panic(cpu 1 caller 0xffffff800339b084): launchd exited (signal 9, exit status 0 CS_KILLED)

Thread 7 crashed

RAX: 0x0000000000000000, RBX: 0x00007fff6b6445f8, RCX: 0x000000010ea12a00, RDX: 0x000000010ea5a7b8

RSP: 0x00007000003a5790, RBP: 0x00007000003a5810, RSI: 0x00000000000015d3, RDI: 0x00007fff6b6445f8

R8: 0x000000010f038119, R9: 0x00007fb928c04130, R10: 0x0000000004001080, R11: 0x000000010ea52170

R12: 0x00007fb9298bca58, R13: 0x0000000000000000, R14: 0x0000000000000000, R15: 0x000000010ea59c53

RFL: 0x0000000000010246, RIP: 0x00007fff6b61e4d0, CS: 0x000000000000002b, SS: 0x0000000000000023

Thread 0: 0xffffff800a74d920

0x000000010efe6dcd

0x0000000000000000

Thread 1: 0xffffff800a74e240

Could not read LR from frame at 0x0000700000116d48

Thread 2: 0xffffff800a3d36d0

0x000000010eff57b5

0x0000000000000000

Thread 3: 0xffffff800b545db0

0x000000010eff1675

0x000000010efe5a83

0x000000010efe6200

0x000000010efec707

0x000000010efe4d53

0x000000010efe4b00

0x000000010f3834de

0x000000010f381341

0x0000000000000000

Thread 4: 0xffffff800d1276d0

0x000000010f381341

0x0000000000000000

Thread 5: 0xffffff800a74eb60

0x000000010f381341

0x0000000000000000

Thread 6: 0xffffff800a02a6d0

0x000000010f381341

0x0000000000000000

Thread 7: 0xffffff800e46a920

0x00007fff6b608063

0x000000010f038262

0x000000010ea52170

0x000000010ea23b57

0x000000010ea234a0

0x000000010ea27b95

0x000000010efe140b

0x000000010eff1675

0x000000010efe5a83

0x000000010efe6200

0x000000010efec707

0x000000010efe4d53

0x000000010efe4b00

0x000000010f3834de

0x000000010f381341

0x0000000000000000

Mac OS version: 15G1010

Kernel version: Darwin Kernel Version 15.6.0: Mon Aug 29 20:21:34 PDT 2016; root:xnu-3248.60.11~1/RELEASE_X86_64

Kernel UUID: E349749B-3303-3DDF-959C-B5885A0E1F6E

System model name: iMac8,1 (Mac-F227BEC8)

Will this be easier to decipher?

Reply

How to handle a Kernel Panic.

Similar questions