Crashing

Question

Level 1

4 points

Crashing

Hey Everyone,

First, thanks for your help. I have a 15" MBP mid 2014 that I purchased in January of '15. I use my machine for dev/ops and it has worked flawlessly up until about 3-months ago. I had several applications running including postgres, node, scala, ect. My machine started crashing and I lived with it as I thought it may have been one of my apps that had corrupted. It got so bad with so many KPs that last weekend, I did a clean install after flashing the drive. When I reinstalled, I selected the file vault feature, which seemed like an immediate mistake. Yesterday, I reflashed the drive again and did another clean install of 10.11.5. The OS is fully updated with all patches. I have installed a single app, google chrome, and it is still throwing KPs. It seems that the KPs are happening after the machine comes out of sleep. I have also reset SCM and PRAM. I have also performed apple diagnostics with no errors and no errors after running firstaid on the ssd. Any help you can provide would be greatly appreciated. Please find below the KP:

Anonymous UUID: 62268A9F-8E5C-D156-B9A5-0EAB170F6F1A

Mon May 30 07:57:02 2016

*** Panic Report ***

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

uuid info:

0x7fff67d11000 uuid = <a468d85e-d8d6-3461-8c99-49d3b9acfc63>

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

Thread 4 crashed

RAX: 0x0000000108e0a000, RBX: 0x00007fff67d515f8, RCX: 0x00007fff8d6c30e8, RDX: 0x00007fff67d4a568

RSP: 0x000070000021c740, RBP: 0x000070000021c740, RSI: 0x00000000000001b1, RDI: 0x00007fff67d515f8

R8: 0x00007fff8d6c3119, R9: 0x000070000021cb40, R10: 0x0000000000013a00, R11: 0x0000000108e4a170

R12: 0x0000000000000000, R13: 0x0000000109801980, R14: 0x00000000000001b1, R15: 0x00007fff8d6c30e8

RFL: 0x0000000000010206, RIP: 0x00007fff67d22882, CS: 0x000000000000002b, SS: 0x0000000000000023

Thread 0: 0xffffff803be92920

Could not read LR from frame at 0x0000700000080d48

Thread 1: 0xffffff803be936d0

0x00007fff91149dcd

0x0000000000000000

Thread 2: 0xffffff803be92490

0x00007fff911587b5

0x0000000000000000

Thread 3: 0xffffff8050176000

0x00007fff91154675

0x00007fff91148a83

0x00007fff91149200

0x00007fff9114f707

0x00007fff91147d53

0x00007fff91147b00

0x00007fff8657f4de

0x00007fff8657d341

0x0000000000000000

Thread 4: 0xffffff80526cd920

0x00007fff67d2b28b

0x00007fff67d15063

0x00007fff8d6c3262

0x0000000108e4a170

0x0000000108e37c28

0x00007fff9114440b

0x00007fff91154675

0x00007fff91148a83

0x00007fff91149200

0x00007fff9114f707

0x00007fff91147d53

0x00007fff91147b00

0x00007fff8657f4de

0x00007fff8657d341

0x0000000000000000

Thread 5: 0xffffff804fcc06d0

Mac OS version: 15F34

Kernel version: Darwin Kernel Version 15.5.0: Tue Apr 19 18:36:36 PDT 2016; root:xnu-3248.50.21~8/RELEASE_X86_64

Kernel UUID: 7E7B0822-D2DE-3B39-A7A5-77B40A668BC6

System model name: MacBookPro11,2 (Mac-3CBD00234E554E41)

MacBook Pro (Retina, 15-inch, Mid 2014), OS X El Capitan (10.11.5)

Posted on May 30, 2016 8:21 AM

Reply

Answer 1

Linc Davis

Level 10

209,739 points

May 30, 2016 11:41 AM in response to mattbram

That kind of panic is caused by a drive failure or perhaps by some other hardware fault.

Reply

Answer 2

OGELTHORPE

Level 9

57,329 points

May 30, 2016 1:00 PM in response to mattbram

Perhaps an Etrecheck report will provide a clue. Download and post one:

http://www.etresoft.com/etrecheck

Ciao.

Reply

Answer 3

mattbram Author

Level 1

4 points

May 30, 2016 1:08 PM in response to mattbram

*** Update

The machine froze again without throwing a KP. Screen froze and no UI, mouse still worked (scrolling) but no interactions. No keyboard function. The clock also stopped when it froze. Leading me to believe that either the video card (onboard) is failing, RAM is damaged, or kernel driver for 10.11.5 is not working on my hardware.

Reply

Answer 4

mattbram Author

Level 1

4 points

May 30, 2016 1:10 PM in response to OGELTHORPE

Thanks for the comment/suggestion. Etrecheck shows no anomalies. Latest freeze did not throw an exception and no error log was written. Just the emptiness of space...

Reply

Answer 5

Linc Davis

Level 10

209,739 points

May 30, 2016 1:11 PM in response to mattbram

Make a "Genius" appointment at an Apple Store, or go to another authorized service provider. You may have to leave the machine there for several days.

Back up all data on the internal drive(s) before you hand over your computer to anyone. There are ways to back up a computer that isn't fully functional—ask if you need guidance.

If privacy is a concern, erase the data partition(s) with the option to write zeros* (do this only if you have at least two complete, independent backups, and you know how to restore to an empty drive from any of them.) Don’t erase the recovery partition, if present.

Keep your confidential data secure during hardware repair.

Apple recommends that you deauthorize a device in the iTunes Store before having it serviced.

*An SSD doesn't need to be zeroed.

Reply

Answer 6

mattbram Author

Level 1

4 points

May 30, 2016 1:13 PM in response to Linc Davis

Heard of any GPU issues causing this. Also, there is some buzz on other boards about WebGL being the culprit. Any experience with this?

Thanks...Matt

Reply

Answer 7

Linc Davis

Level 10

209,739 points

May 30, 2016 1:17 PM in response to mattbram

Many people are running the same version of OS X as you on the same hardware and not having the same problem. Something is wrong with your unit. Good luck.

Reply