Sleep Wake Failure with High Sierra 10.13.2

One thing I did that stopped the problem for a little bit was to turn off the setting "Put hard disks to sleep whenever possible." I'm not sure if it fixed it or if my computer just started working again, but it did solve the problem for a few weeks. However the problem did reoccur later. Hope this might be helpful.

So I can really recommend the method I described in my previous comment, since I haven't had anymore crashes in over a week now.

Create a new user on your computer. Log into this user. Restart the computer from this new user. Log in to your original user. Put your macbook to sleep and pray. 😝

This seems to reconfigure some settings that might solve the problem. Tell me if it works for you!

this makes sense. basically you reduce the workload to the minimum before entering the sleep mode. So that when wake up, it recovers to the minimum workload state so that it doesn't cause high electrical current demand that cause vmin issue. Other than wifi, turn off everything that can be turned off before enter sleep mode would help a better chance to wake up successfully.

My iMac has been having the Sleep Wake failure and restarting itself since I installed HS in November. I installed the 10.13.3 Supplemental update on 02/22 and it did not help at all. I tried the new update for 3 days and had multiple gray screen wake ups and restarts. The only thing that will keep my iMac from restarting once or twice a day is to Enable Power nap. I turned PN back on 36 hours ago and have not had a gray screen or SW failure, or restart (yet). If anyone else has a positive result by enabling PN please let me know. I am working with my 6th or 7th advisor now and he supposedly is passing on this information to the engineering department. Yesterday he told me that the engineers are aware of the problem and are trying to fix it thru an OS update. Unfortunately I have been told that by other advisors since December. I just hope they get it figured out soon this failure has wasted a lot of time for all of us.

I forgot to mention that if you have not called tech support about have a Sleep Wake Failure please do so. Even though they can not fix it Apple will not make it a high priority until enough people let them know it is a problem. Thanks.

Hello brummmmme. This is worth framing!

brummmmme wrote:

I did a pretty extreme test. I erased my disk, installed a fresh copy of High Sierra without importing any user or data, without installing any program, just High Sierra. And I still had the Sleep Wake Failure!

I erased my disk again and installed Sierra and no more Sleep Wake Failure. Then I contacted Apple about these tests and Senior Advisor was helpless. She told me I have to go to High Sierra again to see if the problem happens again... Pffff I just know this will happen again! I told her to read this forum. It did not seam like a knowed issue for her. Since I don't have High Sierra anymore, she told me she could not help me.

By far the most revealing test and confirmation of the nature of Apple's Sleep Wake Failure calamity.

You could have recommended reading Joseph Heller to your Senior Adviser.

I've been testing solutions since yesterday. Disabled pmset autopoweroff, didn't work. Changed hibernatemode to "0", didn't work. I increased the standby time to 24 hours, and autopoweroff as well. Didn't work.o

So I decided to test the apps I used to let opened while sleep. Usually, I let several Chrome tabs for the Google Apps I use, and the TeamViwer to get instant acces to other computers. Since yesterday, I started to close TeamViwer and no issues until now.

I will set the autopoweroff and standby time to it's default and see what happens.

Just saying, by now, maybe the issue happens because some apps. It's not an excuse to Apple ignore this problem. But can be a solution. Opening an app every time you open the lid can be less painful than restarting the whole system.

It does on an iMac - mine has been fine for weeks with computer sleep set to 'never' in energy saver preferences.

Our MacBook Air is unaffected by the problem, which is fortunate as I don't see how it can actually be managed on a laptop.

Just thought I'd provide a status update based on my experience. Since I've installed 10.13.4 Developer Beta 4 going on about 9 days now, I have not encountered the sleep wake failure (with all Energy Saver settings set to default). I have also updated to Developer Beta 5 yesterday and the issue still has not occurred. From my experience, it appears that Apple has resolved this issue starting with the 10.13.4 Developer Beta 4 update.

I'm having this problem too. The workaround - on a desktop machine - is to leave the thing on all the time by disabling sleep, rather than turning it off.

I have MacBook Pro (Retina, 13-inch, Early 2015) with the same problem. I went back to Sierra for a while (did that at the genius bar) and that fixed it. Then I assumed after some updates that it was safe to update to High Sierra again - and the problem is back once again with a vengeance!

My advice don't update to HS if you can avoid it.

I have a temporary solution which is to use an app called "InsomniaX" which prevents sleep on lid closure (although it has been known to create overheating problems so you have to watch that closely. I use this when I carry my laptop from one room to another (it the lid closed). Otherwise when I move around it pretty much aways crashes. For longer journeys the computer has to be completely switched off now.

I have found that it is better to shut down my iMac rather than let it go to sleep mode and have a sleep wake issue restart.

It takes about 2 minutes to boot up from a shut down vs 4 minutes for a sleep wake restart

Still a major inconvenience I wish I did not have to deal with!

Here is my story. It started about a week ago. I found my supposed-to-be-sleeping MacBook Air (HS 12.3.3) awake in the middle of the night, green screen with a folder with a flashing question mark. Hard reboot, everything back to normal. From time to time, I started to have wake-from-sleep issues (ie, open the lid, black screen, nothing happens, hard reboot using the power button).


The flashing question mark folder re-appeared almost every night, or in the morning when opening the laptop lid.


Tried everything I found in internet, including PRAM, SMC, safeboot, recoverymode and diskutility, reisntalled combo 10.13.3, installed the recent 10.13.3 supplemental. Nothing works.


Going through console system.log, I found a weird "5 [RE] Reachability changed" as the last entry before the freeze. See these examples:


Feb 21 00:27:35 DZ-MacBookProi5 uc[67]: 5 [UP] Transitioning from 3 to 1


Feb 21 00:27:38 DZ-MacBookProi5 com.apple.xpc.launchd[1] (com.apple.preference.displays.MirrorDisplays): Service only ran for 0 seconds. Pushing respawn out by 10 seconds.

Feb 21 00:27:41 DZ-MacBookProi5 uc[67]: 5 [RE] Reachability changed

Feb 21 08:27:38 localhost bootlog[0]: BOOT_TIME 1519198058 0

Feb 21 10:55:45 DZ-MacBookProi5 CheckmateIdleDaemon[117]: The system WILL go to sleep...


Feb 21 10:55:45 DZ-MacBookProi5 loginwindow[122]: magsafeStateChanged state changed old 1 new 2

Feb 21 10:55:46 DZ-MacBookProi5 fud[30895]: objc[30895]: Class MobileAssetUpdater is implemented in both /System/Library/PrivateFrameworks/MobileAccessoryUpdater.framework/Support/fud (0x102ec4e10) and /System/Library/AccessoryUpdaterBundles/ApplePowerAccessoryUpdater.bundle/Conte nts/MacOS/ApplePowerAccessoryUpdater (0x102fd28f8). One of the two will be used. Which one is undefined.

Feb 21 10:55:46 DZ-MacBookProi5 uc[64]: 5 [RE] Reachability changed

Feb 21 11:18:41 localhost bootlog[0]: BOOT_TIME 1519208321 0

Isthat "Reachability changed" entry involved with the freeze? this is the last entry in system.log before the freeze. Anybody seeing the same entry?


As last resort, I tried to disable safesleep.

In /private/var/vm i found a sleepimage file, created on February 15 (when I started to have the issue, but it might be a coincidence).


I disabled safesleep (pmset -a hybernatemode 0), rebooted in recovery mode (CMD+R), disabled SIP (csrutil disable), rebooted, deleted the safesleep file, rebooted in recovery mode, enabled SIP (csrutil enable) and re-booted normally.


System has created a new sleepimage file.


In summary, I removed the old sleepimage, I left hibernatemode on 0. Let's see what happens.


ghogoh wrote:

Whichever the case may be, hundreds of Apple users, at least those showing on this and the thread I mentioned above, quite likely many more, have been affected over an extended period of time and this forum becomes as good as any for them to express their expectations from Apple to help resolve the issue.

It is, however, pointless to do so. If you want to express something to Apple, contact them directly. Use the Contact Support button at the top right of every page. Use the feedback page. Or, make an appointment at the Genius Bar at your local Apple Store. If you contact Apple in any of those ways, they track the issues. That's how they learn the scope of a particular problem.

I had a senior advisor tell me that those "anonymous" error reports to Apple are evaluated to discover error trends, but who knows? I guess only Apple knows and they won't say. Apple has really been tight lipped and non-responsive on most of the problems that the crappy High Sierra has caused. Very few of the 9 different advisors that I have contacted knew anything about the sleep wake failure before I talked to them and many tried to get me to wipe my drive and start over which fortunately I didn't do since no one on this discussion had any good results from doing that. I am afraid it could be months or longer before they come out with a solution. My iMac had not been restarting as often since I turned on Power Nap. Apple didn't even know that was a temporary work around.