sparksbr87
Level 1 (4 points)

Q: Macbook Pro crashes while charging

I just installed a new SSD in my macbook pro and it now exhibits the strangest behavior. If I leave it charging for more than 4 hours without using it, it crashes. When I return to the device, I'm greeted by a grey screen with a prohibitory sign/apple logo flashing. When I force reboot, I am prompted to send a problem report to Apple. I've reset PRAM and SMC and nothing seems to solve it.

 

Any ideas? Thanks in advance.

MacBook Pro (15-inch Mid 2012), OS X El Capitan (10.11.3)

Posted on Feb 23, 2016 1:35 PM

Close
sparksbr87

Q: Macbook Pro crashes while charging

  • All replies
  • Helpful answers

  • by OGELTHORPE,

    OGELTHORPE OGELTHORPE Feb 23, 2016 1:40 PM in response to sparksbr87
    Level 9 (52,576 points)
    Mac OS X
    Feb 23, 2016 1:40 PM in response to sparksbr87

    Take out you SSD, install it in an enclosure and connect it to your MBP via USB.

     

    Use startup manager to see if you can boot the MBP:

     

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

     

    If successful, the SATA connection cable is probably faulty.  If not, the SSD is suspect.

     

    Ciao.

  • by sparksbr87,

    sparksbr87 sparksbr87 Feb 23, 2016 1:45 PM in response to OGELTHORPE
    Level 1 (4 points)
    Feb 23, 2016 1:45 PM in response to OGELTHORPE

    Thanks for the reply! When I reboot the computer, it boots just fine. It prompts me to send a report to Apple, and then everything works as expected. I can continue using it all day without issue. It's only when I leave it idle for several hours that it crashes again. It also only happens when charging, I can't recreate the problem on battery power.

  • by OGELTHORPE,

    OGELTHORPE OGELTHORPE Feb 23, 2016 1:51 PM in response to sparksbr87
    Level 9 (52,576 points)
    Mac OS X
    Feb 23, 2016 1:51 PM in response to sparksbr87

    Rub an Apple Hardware Test.  That may offer a clue:

     

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

     

    Also reset the SMC:

     

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

     

    Ciao.

  • by sparksbr87,

    sparksbr87 sparksbr87 Feb 23, 2016 1:54 PM in response to OGELTHORPE
    Level 1 (4 points)
    Feb 23, 2016 1:54 PM in response to OGELTHORPE

    Apple Hardware Test freezes about 11 seconds in so I can't use it.. I've used memtest86 to check the RAM and everything passed perfectly.

    SMC has been reset and problem persists.

     

    I've been at it with this thing for a couple of days. I appreciate the help!

  • by my ginger,

    my ginger my ginger Feb 23, 2016 2:02 PM in response to sparksbr87
    Level 4 (2,472 points)
    Feb 23, 2016 2:02 PM in response to sparksbr87

    You may have a hardware problem. When at desktop hold down the option key and click on the battery icon and see if is says normal. You could also go to recovery and run disk utilities on the hard drive.  Try also a pram reset.  https://support.apple.com/kb/PH18761?locale=en_US If by chance you run it in safe boot and the problem does not happen then it could be software . Shift key at startup.

  • by sparksbr87,

    sparksbr87 sparksbr87 Feb 23, 2016 2:10 PM in response to my ginger
    Level 1 (4 points)
    Feb 23, 2016 2:10 PM in response to my ginger

    Yeah I'm trying to eliminate my system being the problem before I decide it's the SSD's problem and try to get my money back.

     

    PRAM reset performed, problem persists.

    Disk utility run both in OS and in recovery and everything checked out fine.

    Haven't tried a safe boot yet but I'll give it  a shot. It's a lengthy diagnosis because the computer needs to be idle for ~4 hours to produce the crash.

    Thanks for the ideas.

  • by OGELTHORPE,

    OGELTHORPE OGELTHORPE Feb 23, 2016 3:20 PM in response to sparksbr87
    Level 9 (52,576 points)
    Mac OS X
    Feb 23, 2016 3:20 PM in response to sparksbr87

    Check to see if you have a kernel panic listed per these instructions.  If so post it:

     

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

     

    Ciao.

  • by sparksbr87,

    sparksbr87 sparksbr87 Feb 23, 2016 3:29 PM in response to OGELTHORPE
    Level 1 (4 points)
    Feb 23, 2016 3:29 PM in response to OGELTHORPE

    Tue Feb 23 13:13:10 2016

     

     

    *** Panic Report ***

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

     

     

    uuid info:

    0x7fff6b54a000 uuid = <9d05fdf4-65ce-3b53-86d4-abe1a5bf35f3>

    0x100204000 uuid = <f9041ce4-2cdc-350f-8a46-6a8d32a51a2b>

     

     

    Thread 4 crashed

     

     

    RAX: 0x0000000000000000, RBX: 0x00007fff6b58a5f8, RCX: 0x0000000100204a00, RDX: 0x000000010024b790

    RSP: 0x000070000021c750, RBP: 0x000070000021c7d0, RSI: 0x00000000000001b1, RDI: 0x00007fff6b58a5f8

    R8:  0x00007fff92370119, R9:  0x000070000021cb40, R10: 0x00000000000c9400, R11: 0x0000000100243170

    R12: 0x0000000000000000, R13: 0x0000000000000000, R14: 0x0000000000000000, R15: 0x0000000100249839

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

     

     

    Thread 0: 0xffffff8015e5f920

       Could not read LR from frame at 0x0000700000080d48

     

     

    Thread 1: 0xffffff801598b920

      0x00007fff949f5d01

      0x0000000000000000

     

     

    Thread 2: 0xffffff8015e60240

      0x00007fff94a047b6

      0x0000000000000000

     

     

    Thread 3: 0xffffff8018e3ab60

      0x00007fff94a00676

      0x00007fff949f49b7

      0x00007fff949f5134

      0x00007fff949fb63b

      0x00007fff949f3c87

      0x00007fff949f3a34

      0x00007fff89a1f68f

      0x00007fff89a1d365

      0x0000000000000000

     

     

    Thread 4: 0xffffff801a9a1b60

      0x00007fff6b54e063

      0x00007fff92370262

      0x0000000100243170

      0x0000000100230c72

      0x00007fff949f033f

      0x00007fff94a00676

      0x00007fff949f49b7

      0x00007fff949f5134

      0x00007fff949fb63b

      0x00007fff949f3c87

      0x00007fff949f3a34

      0x00007fff89a1f68f

      0x00007fff89a1d365

      0x0000000000000000

     

     

    Thread 5: 0xffffff801cf03240

      0x00007fff89a1d365

      0x0000000000000000

     

     

    Mac OS version: 15D21

    Kernel version: Darwin Kernel Version 15.3.0: Thu Dec 10 18:40:58 PST 2015; root:xnu-3248.30.4~1/RELEASE_X86_64

    Kernel UUID: DECC9F02-27D7-31F0-9599-A9EF2873902C

    System model name: MacBookPro9,1 (Mac-4B7AC7E43945597E)

     

     

    System Profile:

    AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xF5), Broadcom BCM43xx 1.0 (7.21.94.136.1a1)

    Bluetooth: Version 4.4.3f4 16616, 3 services, 27 devices, 1 incoming serial ports

    Thunderbolt Bus: MacBook Pro, Apple Inc., 25.1

    Memory Module: BANK 0/DIMM0, 2 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54333235533643465238432D50422020

    Memory Module: BANK 1/DIMM0, 2 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54333235533643465238432D50422020

    USB Device: USB 2.0 Bus

    USB Device: Hub

    USB Device: FaceTime HD Camera (Built-in)

    USB Device: USB 2.0 Bus

    USB Device: Hub

    USB Device: Hub

    USB Device: Apple Internal Keyboard / Trackpad

    USB Device: IR Receiver

    USB Device: BRCM20702 Hub

    USB Device: Bluetooth USB Host Controller

    USB Device: USB 3.0 Bus

    Serial ATA Device: OWC Mercury Electra 6G SSD, 480.1 GB

    Serial ATA Device: TOSHIBA MK5065GSXF, 500.11 GB

    Model: MacBookPro9,1, BootROM MBP91.00D3.B0C, 4 processors, Intel Core i7, 2.3 GHz, 4 GB, SMC 2.1f175

    Network Service: Wi-Fi, AirPort, en1

    Graphics: Intel HD Graphics 4000, Intel HD Graphics 4000, Built-In

    Graphics: NVIDIA GeForce GT 650M, NVIDIA GeForce GT 650M, PCIe, 512 MB

  • by OGELTHORPE,

    OGELTHORPE OGELTHORPE Feb 23, 2016 3:57 PM in response to sparksbr87
    Level 9 (52,576 points)
    Mac OS X
    Feb 23, 2016 3:57 PM in response to sparksbr87

    I highly recommend that you make an appointment at an Apple store genius bar for a thorough evaluation.  It will be done for FREE.

     

    They have better forensic tools that the AHT and they should be able to determine what the issues are.

     

    I will be candid by confessing I do not know the exact reasons for the kernel panic.  I have suspicions but they may not prove to be helpful, however the genius bar technicians can give you some definitive answers.

     

    Ciao.