Sleep Wake Failure: Reboots only after upgrading to High Sierra

I started having problems with 10.13.2.

Prior to that, nothing.

Second time in two days.

Not happy. And not sure what to do other than hope they fix it.

Meanwhile I have another problem with Safari. Certain web pages consume 100% of the CPU despite having nothing running on them. The same page works fine in Safari on my wife's laptop and using chrome in my laptop. So another mystery. I might need to do a recovery install.

I am probably going to regret this but I have not had an issue since I did an NVRAM reset.

Therefore, I expect that now that I have said this publicly, it's likely to fail the very next time I wake away from my laptop for more than 20 minutes.

The fact that some people had it on 10.13.1 and others didn't see it until 10.13.2 leads me to believe it's not a simple software issue from a specific release.

So give the NVRAM reset a try. It's easy unless you have a firmware password (like I do). Google NVRAM reset and you'll be good to go.

Good luck!

PS: I'll be back in 30 minutes to say Never mind ;-)

PPS: I only just noticed that the original post includes the fact that the author had already tried an NVRAM reset. Oh well...

So 3 calls with Apple support - clean install - SMC and NVRAM reset (several times) - restore of High Sierra again...

Take a fresh user - NOTHING WORKED! - Still not waking up (have to restart and send reports to apple)

VERY SAD - the worst upgrade ever (and I did all since Mac OS 8.1.....

So apple now offered that I could go to an apple store at the Genius Bar.....Looking forward to the stories they will tell me...

COME ON APPLE - fix this BUG!!!

As much as it might seem like I was being a wiseass, I was in fact not :-)

By you, I meant your computer.

And the reason I asked is that this bug (at the top, anyway) is about laptops that are supposed to go to sleep, but instead, crash and reboot with an error message.

So if you are having trouble getting your laptop to wake up ... you have a different problem.

My laptop has indeed been waking up under High Sierra for several months, including throughout the beta program and now. The only problem was that a few days ago it started crashing when going to sleep (or waking up from sleep - I was never there to see it happen) so that when I returned to the laptop, it had rebooted on me.

Now that I shutdown my computer all the way AND performed an NVRAM reset, I have not seen the problem. But ... I already cannot remember whether that has been one or two days.

So again - if you cannot get your laptop to wake up ... well you have a different problem. Maybe you have a laptop that's going into hibernate mode, which is a much slower sleep AND wake process. So you might think it's failing whereas it's just trying really hard.

So tell us more about your laptop in case we can help you better than Apple Support.

here we go:

System-wide power settings:

Currently in use:

standbydelay 10800

standby 1

womp 0

halfdim 1

hibernatefile /var/vm/sleepimage

powernap 1

gpuswitch 2

networkoversleep 0

disksleep 0

sleep 0

autopoweroffdelay 28800

hibernatemode 3

autopoweroff 1

ttyskeepawake 1

displaysleep 10

tcpkeepalive 1

acwake 0

lidwake 1

no matter - as long it is useful I appreciate your help 😉

here without power cable plugged in:

System-wide power settings:

Currently in use:

standbydelay 10800

standby 1

halfdim 1

hibernatefile /var/vm/sleepimage

powernap 1

gpuswitch 2

disksleep 0

sleep 1

autopoweroffdelay 28800

hibernatemode 3

autopoweroff 1

ttyskeepawake 1

displaysleep 1

tcpkeepalive 1

acwake 0

lidwake 1

So you keep saying, Oli, but what is the point of having a laptop or any computer with wifi capabilities where you don't use the wifi? And I don't know about you, but my computer is nowhere near an ethernet cable.

Meanwhile, like others, I have not had this problem reoccur since the first two times. All I did was a NVRAM reset and I have been fine ever since.

I hope others are as successful as I am.

Hi. Like I said disabling WiFi do not work. I already did that. I disable WiFi at night and in the morning when I wake my iMac same error happens. I can’t find a pattern for this error. For example, after made a fresh install of macOS 10.13.2 this error never happens during one week and with WiFi always enable. After that sometimes I had 2 Wake Sleep Failures in one day! In the past two days I do not have any error and wifi is always enable. In my opinion it is an issue related with kernel and ram! With Sierra this error never happens!

I use Linux and macOS. At this moment I am studying the possibility to buy a Ryzen PC and use Linux as my main operating system. I sold my MacBook Pro late 2013 to buy the 2017 model. Well, even the 13’‘ MacBook Pro has a crazy price for the machine. My iMac late 2012 will be my last Apple Desktop. I will buy the Dell Inspiron 27 7000 as my desktop and a Dell XPS 15’‘ as my laptop. Look, I have iPhones, iPads, MacBook Pro and iMac. I spent lots of money on this machines and these type of errors are not admissible! By the way, I also will sell my iPhone SE and buy one Oneplus one 5T. Goodbye Apple.

Same issue here, tried two fresh installs and NVRAM resets. MacBook Pro 13" late 2013

Please fix it Apple, take care of this bug ASAP, not impressed with High Sierra, looks like some High People worked on it...

The same problem - MacBook Pro 13 Retina Mid 2014 11.1 with Aura Pro X SSD. Never had this problem on Sierra. On High Sierra when computer goes to sleep for more than 3h I have two times boot sound and apple logo and system boots from scratch.

I have a MacBook Pro (Retina, 15-inch, Mid 2014) and after upgraded to High Sierra 10.13.2, I had a similar issue. My MAC do not wake up from sleep 😟 I always need a reboot to open the device and all my works has gone 2-3 times. Apple should not blame third parties or whatever. If 10.12.X has no problems and the same configuration with 10.13.X high sierra has problems, Apple should release an immediate fix. We are not paying these high prices for shine screen and dummy siri, we need a stable operating system. (Clean installation or other re-install options cannot be applied to my system. I have critical software installed and also had a limited time. )

Not sure where I got this idea from, but thinking out of the box, it would be really nice if apple had a place where users can post commonly recurring issues. Then apple could have their real engineers review the issues and post real workarounds or fixes (not reinstall). Even better, apple collects lots of information about user behavior. Maybe they should also collect problem reports about their own o/s when it fails unexpectedly. Sort of like a system"dump". That way, they would have all of the information they need to develop a fix, or they could contact the user directly if they need more information about the reported problem. hmmmm

Maybe the folks at apple are all trapped under a heavy desk or something and haven't been able to get to the phone since the high sierra release. Perhaps they need help. 🙂

Every time this error occurs you can either manually send the log to Apple or it can be automated. I am assuming apple has seen this error many times, at least 8-10 from me alone so now the question is has it showed up often enough to get to the top of their list or are there other more pressing problems. It is also possible that several Apple engineers have tried to fix this but either it is a difficult problem or they haven't found the right engineer to work on it, possibly both. While it is possible they are not aware of the problem or are ignoring it, I find that both of these are unlikely.

I know in this day and age we all think our problems should be solved immediately but often that is not possible.

Just so you understand me, I also wish it were fixed and it ***** that it is not, it appears that the problem has been on going for some time.

I have two MBP latpops. Same model and configuration. Mid 2012 Retina 15". Same processor, same memory, same HD, same everything...you got it right?

What is funny, I installed High Sierra 13.2 on both. One has the issue the other don't. WHAT???????