mattbram

Q: 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

Close

Q: Crashing

  • All replies
  • Helpful answers