Should have no effect as the MPB requires a "Magic Packet" which is a specific address & instruction to wake up for access, equally if not using the feature, no harm to turn it off.
Q-6
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
MacBook Pro restarts during sleep
- Thread starter aevan
- Start date
- Sort by reaction score
Should have no effect as the MPB requires a "Magic Packet" which is a specific address & instruction to wake up for access, equally if not using the feature, no harm to turn it off.
Q-6
Thanks for the clarification.
I think the wake-ups are just macOS bugs. I'll wait for it to get sorted out, the restart issue was problematic, this - not so much.
I can confirm that the wakeup issue is due to the "Wake for Wi-Fi network access" I don't know why, but when I did deactivated it in Energy Saver my MBP did not wake up anymore.
Good to hear that your reboot aka. Sleep Wake Failure was solved.
I'll try to turn of the Wake for Wi-Fi then and see what happens. As I understand, it shouldn't influence sleep, but maybe it's some bug connected to it. Thanks!
Since you're trying things, I'd deselect anything you're not using that may relate to waking. I think Wake for Wi-Fi network access is supposed to only work with certain software on a local network, but over the years people have found/thought it to be implicated in buggy wake-sleep issues beyond that.
Edit: Ha, should have read page two of the comments first!
Edit: Ha, should have read page two of the comments first!
Well if you have done smc / nvram reset and then delted the hibrination file then the only thing left is to try to reinstall macOS.
Also try to do hardware diagnostic and see if it's say something.
Boot the mbp same time as you pushing the D key.
Or, post the error file here so we can read it you can find it in Console.
If you post the error log file, also download etrcheck and run that program and post the log file of it here also.
If nothing helps then take it to Apple Store so they can run there test program on it.
All I've done was deleting the file. Haven't tried SMC/NVRAM reset yet. I guess that is my next step.
Incredible, but it happened to me, also. The sleep file helped for a few days, but it happened again.
I will do a clean macOS install over the weekend and report my findings.
I just found this thread. I seem to be having the same issue, or at least it's similar: for me, this only happened once (the crash upon resume from sleep), but I see the screen turning on every now and then when a notification arrives. It's especially annoying because it's an external screen and it's pretty bright.
More details here: 2016 MBP TB: kernel panic - sleep wake failure
More details here: 2016 MBP TB: kernel panic - sleep wake failure
I did get replay from bug report;
They told me that they can't reproduce it etc.
So indricet if it's nothing wrong with the software it's hardware related.
They told me that they can't reproduce it etc.
So indricet if it's nothing wrong with the software it's hardware related.
Those having repeating issues, are your MBP's connected to an external display when entering Deep Sleep? If so you will likely be stuck with the issue until Apple decide to resolve. Might be worth testing with & without being connected to an external display.
Q-6
Q-6
Mine is not. For some reason, I believe some of the 3rd party apps are messing up sleep. I quit most of the apps running in background, and I am testing. And I'll probably do a full reinstall of macOS for the weekend.
I'm no expert, but this really seems like a software issue to me.
Well your definitely better to exclude any potential for software issue, as dealing with a repair at this stage will be painful.
Better to try and nail it down now, prior to a reinstall and or clean reinstall of the OS, may well save you time in the long run.
- DL and update with latest OS combo point release from Apple I have experience of this alone fixing OS related problems in the past.
- Try booting to Safemode and see if the problem persists, as this will exclude all 3rd party applications on start up.
- Try creating a new user account and see if the issue replicates.
Code:
cat /var/log/system.log | grep -i "wake reason"Q-6
A quick scan with Malwarebyres for Mac and or Bitdefender (free from App Store) will reveal if any malicious code is present on the system.
Q-6
Update. I figured the reason MBP was restarting during sleep.... and, this may come as a surprise. It's - Wunderlist.
Ok, so if I leave the Wunderlist running in the menu bar, the MBP will crash when going to deep sleep. I tested for a few days and can verify this. I have no idea why this is happening. If I quit Wunderlist - no issues.
Don't know if this helps anyone, but if your MBP is crashing, try to quit all apps before going to sleep and see if it restarts. Then turn them on one by one and test.
Ok, so if I leave the Wunderlist running in the menu bar, the MBP will crash when going to deep sleep. I tested for a few days and can verify this. I have no idea why this is happening. If I quit Wunderlist - no issues.
Don't know if this helps anyone, but if your MBP is crashing, try to quit all apps before going to sleep and see if it restarts. Then turn them on one by one and test.
Yet another update - the problem persists. It's hard to test because sometimes it takes days for the problem to manifest, so I think I solved it, when in fact I didn't.
I tried deleting the sleep image, resetting the SMC, PRAM, I even wiped my drive and installed a fresh Sierra.
It still happens. Could it be a hardware defect? Not sure how this is possible, because everything else works fine.
My current plan is to try and test without 3rd party apps (for example, turning off BTT before putting it to sleep)
Also, disabling hybernation in the Terminal
I could take it to service however, I don't have Apple Stores in my country, only authorised service providers, and my friend recenltly had quite a bad experience with them (they actually managed to make things worse and were unable to fix a problem, he ended up contacting Apple and after three (!) months of hassle and without a computer, Apple sent him a replacement). I am reluctant to risk being without my computer for months because of this, especially since it only happens in 'deep sleep' and does not affect my work. Still, it's annoying.
I may wait for the next major macOS update and hope it, somehow, fixes itself. Not sure what else to do, really.
I tried deleting the sleep image, resetting the SMC, PRAM, I even wiped my drive and installed a fresh Sierra.
It still happens. Could it be a hardware defect? Not sure how this is possible, because everything else works fine.
My current plan is to try and test without 3rd party apps (for example, turning off BTT before putting it to sleep)
Also, disabling hybernation in the Terminal
I could take it to service however, I don't have Apple Stores in my country, only authorised service providers, and my friend recenltly had quite a bad experience with them (they actually managed to make things worse and were unable to fix a problem, he ended up contacting Apple and after three (!) months of hassle and without a computer, Apple sent him a replacement). I am reluctant to risk being without my computer for months because of this, especially since it only happens in 'deep sleep' and does not affect my work. Still, it's annoying.
I may wait for the next major macOS update and hope it, somehow, fixes itself. Not sure what else to do, really.
I'm in the same boat, AppleCare was really unable to help me since I can't extensively test using my computer without my external monitor (I do scientific research and need to open tons of windows). There are definitely issues related to the monitor, but I've gotten random restarts without it plugged in too.
I've also had it happen a lot if I unplug my monitor, then close my laptop and re-open it. It'll usually just restart itself. Sometimes it will also happen when I'm actively using it, screen will just go black and there will be no message of any kind. I feel like it happens more often when I have a lot of usb-c devices plugged in (2 external hard drives, Logitech wireless USB adapter, monitor, power cable). It could be so many things I depend on - usb-c hub, hard drives, monitor cable, monitor itself, computer. Feels impossible to troubleshoot without taking a huge productivity hit.
No idea if its related but I also get red bars (always a different pattern) in finder when I unplug or plug in my monitor (usb-C to DisplayPort cable with an LG curved 32" monitor). If I relaunch finder these go away.
Guess I'll have to do a reinstall, what a huge pain. I have so many compiled programs I need to install one by one....
I also had a weird touchbar issue the other day where it only displayed function keys until I restarted.
This is my second 15" MBP TB, the first one was replaced because of restart issues and extremely bad battery life.
Edited: Its not the monitor specifically, its happened with multiple monitors (all 32", HP, LG, and Asus). I also tried deleting sleepimage a few months back and had the same experience.
Last edited:
I'm pretty sure I had this problem since Sierra. Maybe with El Capitan too, I'm not sure. I connect to external monitor through HDMI. Usually keep it plugged in, power plugged in, screen open position. I got tired of the random crashing so I did a clean install of 10.13.1 just couple days ago. Major software that I installed are xcode, ms office 2016, Parallels 12.2.1(41615), MacPorts, TunnelBlick VPN, Teamviewer, and some more. It stayed standby fine for 3 days, then it crashed yesterday around 5pm. It sucks to have to be greeted with "unexpected shutdown" message. I always click on the "report to apple" button, but I don't think they even care.
Even after a clean install, and trying disabling wifi wake stuff, same thing happened. Unexpected shutdown. Well, it was more like an "expected" unexpected shutdown.
I got so pissed, I went back to El Capitan. It's been about a week without any crash. I think that problem started since Sierra, and continues in High Sierra. I'm just going to use El Capitan unless it's really confirmed to be fixed.
i have had this issue. i have a 2017 TB-MBP. I rarely put it to sleep.
Occasionally, when I do wake it from sleep, it has to boot the system from scratch. There is no message about improper shutdown and in the logs there is just this kind of thing:
I can see from log in /var/log/powermanagement that there is a `Sleep Failure [code:0x04000013]:` when I open the clamshell.
Can't find any other information in logs...
Occasionally, when I do wake it from sleep, it has to boot the system from scratch. There is no message about improper shutdown and in the logs there is just this kind of thing:
I can see from log in /var/log/powermanagement that there is a `Sleep Failure [code:0x04000013]:` when I open the clamshell.
Can't find any other information in logs...