9

My 15-inch 2016 MacBook Pro is now experiencing shutdowns when the lid is closed. Though it is not a crash because I don't get a crash report when I turn the computer back on (unlike the problem I had earlier). I used the following Terminal command to obtain the Previous Shutdown Cause (as the console app can't do it anymore in Sierra):

log show --style syslog --last 48h | egrep shutdown\ cause | awk -F')' '{print substr($0,1,19), $NF}'

The code for the shutdown is 0. From this question I found that 0 triggers when you unplugged the battery, or the power cable on desktop Macs. But the battery on the 2016 MacBook Pro is non-removable (obviously). Even more strangely, when this happens, my laptop is plugged into the power adapter and for sure it is charging. This doesn't happen when I am using the computer both on battery and power adapter, it only happens when the lid is closed for a while.

I have tried to reset SMC and NVRAM with no luck. Anyone know how to solve this problem?

  • This and your other question points to a logic board failure. To get a 0 shutdown cause you have disconnect all power and on a laptop that's pretty hard to do. I suspect there's something wrong with the SMC or related components and not enough power is getting to critical systems like memory so you are seeing the shutdowns/crashes. – Allan Mar 4 '17 at 15:22
  • @Allan yeah, thought of that. Going to get it fixed. – Tom Shen Mar 4 '17 at 15:22
  • Let us know what happens. – Allan Mar 4 '17 at 15:23
  • the same has happened to me. Very disappointed. – ashoor Feb 18 '18 at 3:56
0

Possible hardware issues aside, check what is your setting on what the computer wants to do when you close the lid and the behaviour afterwards. You can see the settings with the:

pmset -g

Look for the hibernatemode, autopoweroffdelay and standbydelay settings.

See a blog post describing the pmset settings here

On the hardware problems side I've read reports that a faulty charger might cause the MacBook to shutdown. As you report that the problem does not occur when on battery life, this may be the culprit and I'd suggest you try a different charger.

Is the time you mention "for a while" three hours or more? Then the problem occurs when your MacBook tries to enter the standby (see standbydelay setting above).

0

It had been close to year after posting this original question. The MacBook is completely fine now. It has to be some bugs that Apple had in the 2016 revision of the MBP. I’ve been running for a close to half a year without any problem now (it hadn’t even crashed once after 10.13). If you still had the same question you might want to get the machine serviced as I’m pretty sure if it’s that then it’s a logic board problem.

You must log in to answer this question.

protected by Community Feb 18 '18 at 4:49

Thank you for your interest in this question. Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).

Would you like to answer one of these unanswered questions instead?

Not the answer you're looking for? Browse other questions tagged .