Sleep Wake Failure: Reboots only after upgrading to High Sierra

FYI sudo pmset -a hibernatemode 3 standbydelay 10800 standby 0 helps with the Sleep/wake issue but your battery will drain fast.

Hi all -- I have had this problem too for months. Don't want to raise false hope, but I upgraded to 10.13.3 yesterday and it hasn't happened since. Based on my past experience, I would have expected to see it by now. Anyway -- may be worth giving the update a try. May the force be with us!

This seems to work with my early 2014 mac book air with a 3rd party owc 1tb aura pro x ssd drive.

My guess, as has been espoused in this forum, is that if the machine sleeps, when it wakes back up, it takes too long for the 3rd party drive to initialize, and a watchdog goes ahead and reboots the machine - twice!

It is restarting because the 1tb is NOT plugged in. I believe it is the time of the night that it backs everything up and if it is not plugged in it searches for it and then does the reboots. I am going to leave it plugged in this evening and see if that solves the problem.

This is only a quick response to pcpclafferty, ahead of a more detailed update on my observations since going to 10.13.5 Beta. My guess is that yours is a portable, for which the default power management settings are different from those for desktops (in my case an iMac, 21.5, late 2012). In particular your standby = 1 and hibernate = 3 are both 0 on the iMac. It is my suspicion that these settings are involved in the whole messy saga, but I have no definite understanding how.

As a working hypothesis, it seems that the actual(!) effect of the parameter 'sleep' (presumably corresponding to computer/system sleep) might be related to the problem. It appears that before my updating to the Beta the effect of 'sleep' involved going into a state similar to 'hibernate', even when my hibernate setting was 0. Now this does not seem to happen, which probably means that my iMac does not effectively 'sleep' (although I have no way of establishing this).

Since upgrading to 10.13.5 Beta, more than 2 weeks ago, remarkably, I have not had a single SWF event!! With great trepidation a couple of days back I turned on the disksleep, which initially was not ticked, so that I only have display and system sleep, in order to have the minimum of parameters active. The computer was going to auto-power-off at night, as before, mostly at night, and waking up normally. I am not confident enough to attempt changing standby = 0 and hibernate = 0, as months of SWF experience, daily!, has still not healed the scars.

In short it is my guess that your, possibly, default standby=1 and hibernate=3 may be causing the same issue as the sleep before the Beta presumably changed the effect of the latter.

Many people on this discussion have mentioned that preventing the computer from sleeping somehow removed the SWF problem, so you might try to set standby and hibernate to 0, if you are inclined to verify that hypothesis. However, this can only be a temporary cure and certainly not a professional solution to a problem of such proportions.

Apologies if the writing above is not sufficiently clearly structured. Hope to write an improved update before long.

Since Apple does not care about the problem and I need a system that works, I decided to downgrade to Sierra. Thanks Apple! 😠

Try turning off time machine and see if it still happens. If it doesn't then you know your SSD is creating some problem, maybe draws more current then allowed?

Not that this is the best solution, nor for planet earth, but for me turning off anything that would cause the computer to sleep/hibernate got rid of the problem. Haven't had the issue since.

I have this problem on MacBook Pro Retina 13 Mid 2014. I found, that when I simply close the lid for a couple of hours system restarts (in a strange way, with 2 boot sounds). But when I log out and then close the lid for the night, then system wakes up OK.

Until you get it resolved, I'd log out on extended times away as in overnight.

Does it also do the rebooting if you force it to sleep?

Update to 10.13.3 solved the problem on my late 2013 iMac.

Here is my tale.

I have MacBook Pro (13-inch, 2016, Four Thunderbolt 3 Ports) purchased in early February 2017.

After multiple failures to wake which was at the end not helped by NVRAM or SMC resets I took the computer to my local Apple Store. They were unable to get the computer to function and they accepted it for repair under warranty. When I got it back they had replaced the main board, the battery and the display; basically everything. The computer came back with MacOS 10.12.6 installed. Before I reinstalled ANY of my software the computer began to show Sleep Wake Failure. I now have turned off sleep and that is how I will continue to operate so that I can salvage some of my investment in this machine.

My first Mac was a 128K Macintosh. This MacBook Pro will be my last Apple computer. As demonstrated by this support thread and my own experience, Apple has multiple software and hardware problems with its current generation Macs and it is clear that they are both unwilling and more importantly UNABLE to fix these problems.

Adding on so that maybe Apple notices how many people are having this issue and does something about it...

Mid 2015 MacBook Pro on 10.11.6.

I don't think it's an OS issue, necessarily, but a hardware one as I have a Mid 2011 MacBook Pro that has been on everything from 10.7 up to 10.12 and it does NOT have this issue. It seems to be common to 2015 models as I have googled this issue and that one seems to show up the most.

This happens about once a week fairly reliably on the same day. Why the same day? Because that's the only day I remove it from being plugged in and take it elsewhere with me. It goes from a desk where it is attached to 2 external monitors and uses a USB Ethernet adapter for internet and then to another desk where it uses the wireless (the WiFi is turned OFF when it's at the first desk and is only turned ON after I log in at the second) and does not connect to any external monitors. In transport from one desk to the other, it is asleep. It does not reboot right away. Rather, it seems to reboot randomly anywhere from a couple hours after being moved to 12 or so. Usually this happens without my having interacted with it at all during this time. Just now, after not having touched the computer since I moved it at around 4:30PM today, it rebooted itself while sitting here with the lid closed and (supposedly) asleep.

This is a continued annoyance. I would also like to note that the rest of the week, as the computer sits in the same spot and is put to sleep rather than shut down every day, it doesn't reboot.

The reasons given for the reboots each time is sleep/wake failure. The usual fixes of resetting things doesn't do it. As it's happening on different versions of macOS, I don't think it's necessarily an OS issue, especially given that my 2011 MacBook Pro is not having this problem (it has other issues which I think I can attribute to the OS that amount to the Mac version of blue screening (something it never did pre-10.10), but that's neither here nor there since it's not a "sleep/wake failure" error...)

iMac (21.5 in, Late 2012) - Sleep Wake Failure after updating to High Sierra, currently Version 10.13.3

There are 560 responses to this comment, that is since mid December 2017, reporting the same issue. I have been reporting to Apple on an almost daily basis for about a month now. There is at least one other thread, discussing the same problem. All respondents are suffering persistent, disruptive and recurrent difficulties with their apple computers rebooting unexpectedly in sleep mode.

It is disgraceful that Apple would not even acknowledge the issue. This is an appalling attitude to mostly faithful and devoted customers.

So very disappointing!

G

I just recently started having this issue a couple days ago. The only change that has been done to my imac is I finally purchased a 1tb ssd. This is on time machine and I wonder if its a glitch that when I do not have my ssd plugged into a usb it restarts. It keeps happening close to the same time every evening.