Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

ahostmadsen

macrumors 65816
Original poster
Dec 28, 2009
1,107
849
My 2017 15" MBP crashes every night while asleep. It never crashes while I use it. Any ideas how I can solve that?
 

Samuelsan2001

macrumors 604
Oct 24, 2013
7,729
2,153
Well the easiest way would be to turn it off at night. It's not like it takes a long time to boot up.

Other than that find out which process or automatic update is causing the crash and stop it.
 

ahostmadsen

macrumors 65816
Original poster
Dec 28, 2009
1,107
849
Well the easiest way would be to turn it off at night. It's not like it takes a long time to boot up.

Other than that find out which process or automatic update is causing the crash and stop it.
How do I find out about that?
 

ahostmadsen

macrumors 65816
Original poster
Dec 28, 2009
1,107
849
Yes. But until the end of the year I'm working in a country without Apple stores. I also fear they might just ask my to reinstall OS X, so I was trying to see if I could fix it myself.

For the last few nights it did not crash. Crossing fingers that the issue just went away by itself.
 

PBG4 Dude

macrumors 601
Jul 6, 2007
4,357
4,633
How do I find out about that?
In Applications —> Utilities , there is the Consile application. This will let you explore the various logs generated by macOS. You’d probably want to start looking at the system log file.
 

New_Mac_Smell

macrumors 68000
Oct 17, 2016
1,931
1,552
Shanghai
There could be a bigger mystery afoot here, have you considered another entity might be messing with it at night? Check the logs, if it reads "Help, Help! OH GOD PLEASE HELP ME!", then I strongly advise you gather a paranormal activity style setup and further this investigation.
 
  • Like
Reactions: PBG4 Dude

ahostmadsen

macrumors 65816
Original poster
Dec 28, 2009
1,107
849
In Applications —> Utilities , there is the Consile application. This will let you explore the various logs generated by macOS. You’d probably want to start looking at the system log file.
Crashed again last night, even after update to 10.12.6

The system log has a lot of information. Not sure how I can pin it down.
 

JustinRP37

macrumors regular
Jun 14, 2016
217
368
New York, NY
Crashed again last night, even after update to 10.12.6

The system log has a lot of information. Not sure how I can pin it down.
My MacBook Pro 2016 15 inch had this exact problem. They determined it was something with the motherboard and exchanged the whole computer. I’d get it exchanged as it is an issue.
 

PBG4 Dude

macrumors 601
Jul 6, 2007
4,357
4,633
Crashed again last night, even after update to 10.12.6

The system log has a lot of information. Not sure how I can pin it down.
Look at the last few lines before before your restart time. Somewhere around that time could be some kind of failure notification.
 

ahostmadsen

macrumors 65816
Original poster
Dec 28, 2009
1,107
849
Look at the last few lines before before your restart time. Somewhere around that time could be some kind of failure notification.
Another crash. The crash reports starts as follows. I don't think it's very informative:

Date/Time: 2017-09-26 15:38:43 +0900

OS Version: Mac OS X 10.12.6 (Build 16G29)

Architecture: x86_64h

Report Version: 25



Data Source: Stackshots



Event: Sleep Wake Failure

Duration: 0.08s

Steps: 8



Hardware model: MacBookPro14,3

Active cpus: 8









Process: kernel_task [0]

Path: /System/Library/Kernels/kernel

Architecture: x86_64

Version: Darwin Kernel Version 16.7.0: Thu Jun 15 17:36:27 PDT 2017; root:xnu-3789.70.16~2/RELEASE_X86_64

Task size: 3675.36 MB

CPU Time: 1431.751



Thread 0x6b 8 samples (1-8) priority 95 (base 95)

<IO tier 0>

*8 call_continuation + 23 (kernel + 620791) [0xffffff80002978f7] 1-8

*8 ??? (kernel + 1256189) [0xffffff8000332afd] 1-8

*8 thread_block_reason + 222 (kernel + 1057470) [0xffffff80003022be] 1-8

*8 ??? (kernel + 1062043) [0xffffff800030349b] 1-8

*8 machine_switch_context + 206 (kernel + 2070942) [0xffffff80003f999e] 1-8
[doublepost=1506567104][/doublepost]
My MacBook Pro 2016 15 inch had this exact problem. They determined it was something with the motherboard and exchanged the whole computer. I’d get it exchanged as it is an issue.
So, yes definitely I should take it to an Apple store. But the issue is that I'm out of country until January, so that's the earliest I can go. that's why I'm trying to see if it's a software issue, and if I can solve it myself.
 

ahostmadsen

macrumors 65816
Original poster
Dec 28, 2009
1,107
849
I think I figured out the cause (but not necessarily the reason) for the crashes. If I disconnect my external hard drive used for Time Machine, it seems not to crash at night. So, either the hard drive itself, or time machine makes it crash.

In principle I can then solve it by disconnecting my hard drive every night. But that is not really a solution; I like that it backs up all the time.
 

brosenz

macrumors 6502
Apr 26, 2011
342
90
My MacBook Pro 2016 15 inch had this exact problem. They determined it was something with the motherboard and exchanged the whole computer. I’d get it exchanged as it is an issue.
After the motherboard change no more problems?
 

joefoong79

macrumors regular
Jun 23, 2017
178
33
Don’t waste your time travel to Apple store. They can’t do anything at all on sleep wake failure. The reason it happened is because your system malfunction with the new OS. Only solution is just revert back to old OS and wait the next OS. Just avoid this version OS, maybe next will be fine. Nothing much you can do. My old Mac had this symptom on sierra but not at El Capitan. Wasted me a lot of time to find solution until I gave up and reverted.
 

JustinRP37

macrumors regular
Jun 14, 2016
217
368
New York, NY
After the motherboard change no more problems?
Well they swapped me for a new computer, so no issue on the new computer. It no longer has any sleep/wake issues. The only thing I notice is if I close the lid of the computer while still connected to an external monitor, it can fail upon waking up, but if I put the computer to sleep before closing the lid when attached to the external monitor then this isn't a issue. Overall stability is back to being rock steady on macOS 10.13.3.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.