Sleep Wake Failure: Reboots only after upgrading to High Sierra

Hello

Exactly the same problem, after I updated to Sierra. That problem was not occurring before.

I went to Genius bar. They checked all hardware configuration. Nothing.

So the only suggestion: reinstall the OS. So , I did !

Problem is still there. Just waisting time !

So , I guess we should wait a patch from Apple.

My first action was : Changing the setting for 'sleep mode', 'energy' , 'screen saver' , all of them to OFF & Never

And the issue was not solved.

Remove ' automatic backup for time machine' has no effect.

Reduce the size of the 'download folder' has no effect 🙂 That was the solution, for 'freezing'...

So, I'm waiting for a patch from Apples's support !

Sorry, I did not realize I needed to take you literally because it seemed so unlikely. So thinking about it another way, it might be possible that if the computer is woken out of sleep often enough i.e. doing backup it will not crash as often. It often took 8 or more hours of sleep for my computer to show the problem.

The computer should be smart enough to realize the backup drive is not available but then anything is possible although not probable.

Hi, I´ve been running High Sierra 10.13.2 for months with no issues. I upgraded to 10.13.4 a couple of days ago and the reboots started (with the log error Sleep Wake Failure).

Something happened during the upgrade, the iMac did a strange noise (the same that when the RAM fails) a couple of times, then it seems like if it entered into save mode for a minute but actually the upgrade ends (successfully?).

It's the first time something like that happens to me during an upgrade or fresh install (iMac mid-2010 with OWD SSD).

Regards

I have a 27” Retina 5K iMac, Late 2015. I wasn’t having this issue until High Sierra 10.13.4 update. I had the reboot, system wake failure problems when running the public betas of 10.13.4, so did a clean install of 10.13.3 and all was fine again. Now stuck with the issue following the 10.13.4 release. It’s really not good enough. Reset the NVRAM, SMC, erase and install, clean install. Nothing worked. Currently waiting on Apple technical.

Just hva eon my Late 2015 27" iMac and so far it seems to have helped. That being said, Time Machine was backing up the update so that might have kept the machine more powered on. Will confirm tomorrow.

If "They said there were no other reports about this.", they have been dishonest, as on this thread and on the following parallel discussion of exactly the same issue,

Sleep Wake Failure with High Sierra 10.13.2

there have been numerous comments by users, who have discussed the problem with Apple Support personnel.

hi everyone. i have the same issue with my MacBook Pro (Retina, Mid 2012).

after i close the display it goes into sleep mode, after some minutes 2 startup sounds and then the error message "sleep wake failure".

the first time this happened at night, i woke up from the gongs and when i tried to start the computer on the next morning the SSD was dead!

In the apple store they told me if they would fix it, they had to change the main board for about 900 bucks or so. so i decided to try my luck with another ssd (Transcend JetDrive 725).

now the mac works again but the "sleep wake failure" is still there. i wonder if the software update caused the death of the original SSD? And after that offered me an insanely expensive repair?

anyways. it would be great if anyone knows how to fix this. i hope the error does not kill my new SSD too.

Hi

Thank you for your time with this issue. According to previous posts Apple are unaware of it. I don’t believe them, it seems they either don’t care or can’t fix it, probably the second. It will soon be time for a new ios so they hope the problem will go away. Meanwhile people all over the world will be getting very frustrated with Apple, will stop buying their expensive products and change to Windows, sad but that’s life. Windows can now do all the things we need that once only Apple could provide.

Think on Apple!

Unfortunately, there is no sign of resolution for this dreadful SWF problem. The saga goes on at the expense of so many users. Looks like it has other manifestations, too:

Apple's magical quality engineering strikes again: You may want to hold off that macOS High Sierra update... • The Regis…

With no disrespect to the enormity of the issues associated with such unimaginably complex things like modern computers, it is the disregard of the difficulties experienced by so many people over such a long time that adds insult to the injury.

In case this comment goes through, just as an update on my experience - while some situations with the iMac crashing on the dreaded Sleep Wake Failure appear similar, there is no clearly identifiable pattern of running applications or connected devices.

I'm having the same trouble everyone here is reporting, but running the latest beta, too.

My report includes other variables yours does not. I wonder why?

standbydelay 10800

standby 1

womp 0

halfdim 1

hibernatefile /var/vm/sleepimage

powernap 1

gpuswitch 2

networkoversleep 0

disksleep 10

sleep 10

autopoweroffdelay 28800

hibernatemode 3

autopoweroff 0

ttyskeepawake 1

displaysleep 10

acwake 0

lidwake 1

I do thank you for your analysis and recommendation.

Per the poster earlier in the thread, I have tried the "sudo pmset -a hibernatemode 3 standbydelay 10800 standby 0" command to see if that helps.

Whatever additional insight you might glean I'd be glad to hear it.

many thanks

The solution you linked is quite interesting, but require a certain skill.

Moreover sounds a little bit risky if you don't know exactly what you're doing.

The author seems to have a proper knowledge of electronics and even found how to modify the cable, mounting an additional resistor.
What I think is that OWC should not declare this device compatible with later 2013+ models, because it is not.

I'm packing the hard drive and sending it back, because for me it's not a replacement to the original.

It seems there's not a solution on the market to make it happen. I mean: should I really send it to Apple or buy a new PoweBook? that's crazy, but absolutely in line with Apple policy.

Amen.

Sorry, I did not realize I needed to take you literally because it seemed so unlikely. So thinking about it another way, it might be possible that if the computer is woken out of sleep often enough i.e. doing backup it will not crash as often. It often took 8 or more hours of sleep for my computer to show the problem.

The computer should be smart enough to realize the backup drive is not available but then anything is possible although not probable.

Sadly for me, I have just been forced to upgrade from El Cap to H Sierra 10.13.6 and now I have all the same sleep/wake problems that you all talk about. Never happened before. Waiting for a call back from the Apple engineer who had told me that they would not be very helpful about troubleshooting various issues if I would not run the latest OS.