New rMBP sleep/wake failure crashes

@Potatodish you need to be more specific please. what version of mavericks are you using etc.

Regarding my previews post:

1) Can anyone tell me what these diagnostic logs above say?

I mean the computer does not show any error or so. i basically just realized my hard discs starting and shutting down every now and then. it was quite annopying when trying to sleep as on old hdd is really loud.

@Ricc83... I cannot help you, sorry. I don't even know how you made those logs--my computer diagnostics knowlege is nonexistent.

@ricc83 - Please start your own thread. Also generally please don't post logs, stack traces, crash reports, etc directly to forums unless someone asks and offers to specifically look at them (IMHO it's still better to post them to pastebin, gist, etc as those of us that can read them don't want to read them reformatted inside a post)

The new update 10.9.2 appears to have solved my issue as well. My machine is a Macbook Pro, 15-inch Retina, with a 2.6 GHz, Intel Core i7 processor. I have a powered Western Digital 4TB My Book Studio Edition II External HD attached to the USB port permanently now without issue. Before the update, this used to cause a crash within one hour of inactivity. Since the update, I have had zero crashes. Perhaps this is the answer to many of our issues. Best of luck to everyone.

Update 10.9.2 has solved the "Sleep/Wake Failure" in combination with "Power Nap" for me.

For those still experiencing the problem:

I have done the following steps back in november on suggestion of an apple engineer. I'm not sure if it also added to solving the problem:

1. Resetting the System Management Controller (SMC): http://support.apple.com/kb/HT3964
2. OS X Mavericks: Start up in safe mode:http://support.apple.com/kb/PH14204
3. I have also updated the firmware of my external WD HDD which may have helped

I have been scouring discussions all night for this, and haven't found a specific answer to my version of this black screen of death issue.

My mid 2008 MBP with 10.9.1 (I don't think I had gotten to updating to 10.9.2 yet) has gone into a mode of perpetual sleep, where opening the lid causes the sleep light to dim, but not go off, and the fan to spin. When lid is closed, the fan continues to spin, and the sleep light comes on brighter, but doesn't throb like I am used to seeing when it is sleeping.

When I remove the battery and power, it shuts down, but when I plug back in (or battery) and hit the power button it makes the optical drive noise, and goes immediately into sleep/black screen of death. So I basically can't get it out of this mode at all to change any settings so it can even shut down correctly (is power nap to blame for this?)

I have reset the SMC and PRAM and those don't do anything.

I can't power into safe mode because when I power up from what should be a turned off computer, it doesn't make the startup tone, but goes right into the sleep mode.

If anyone has any clue how to get this thing to just shut down completely so I can get it to start up I am welcoming any and all tips.

thanks!

shadrach333 - Please start your own thread. Your issue to totally unrelated to this one.

jb510, please tell me how my sleep wake issue is unrelated to this? The failure I am having is directly related to the sleep wake, issue that this thread, and others across the forum here are reporting.

Shadrach333 - You should read the thread to understand what is covered here before posting.

The issue is summarized several times as "Spontanous Reboot while sleeping w/ powered USB devices attached and an error log message upon reboot coded Sleep/Wake Failure".

That's not at all what you describe.

What you have sounds like a video or logic board failure.

Update 10.9.2 has solved the "Sleep/Wake Failure" for me as well. I did disable "Power Nap" before but that did not help. Macbook Pro 2013 with Anchor 3.0 USB hub and two drives attached would crash if left to sleep over night (or several hours). If I allowed the MBP to sleep for several hours with just the USB hub plugged in, it would notify me that it had crashed overnight. I run Windows 7 in a Fusion VM (latest version) but ruled that out as a cause.

After updating to 10.9.2 the problem may have been resolved. I have left both drives active on the hub and after sleeping overnight the system has not crashed by the next morning. This has been repeated for several days now so looking good. Perhaps Apple engineers got tired of my our relentless bug notifications coming in after each crash. Will post again if the problem comes back but so far so good. Thanks Apple!

I just upgraded to Mavericks on my 2013 Retina Macbook Pro and I have 10.9.2 and the crash persits. Same sleep wake failure crash. It appears to happen overnight without anything plug into the laptop.

Steps to reproduce:

At home I have a 27 inch screen and I connect it through the HDMI port, along with a USB External HDD and a USB Keyboard. Everything works fine. When I am done, I don't close the lid I go to the Apple icon and sleep the computer from there. I unplug everything and close the lid. I can open the lid again and no crash everything continues to work fine.

Next morning, again without having anything connected I open the lid and the laptop crashed overnight.

I have played around with the suggestion in this post disabling power nap, wake for network access, put hard disks to sleep, enable them again, the crash persists overnight.

I am normally patient when it comes to a bug like this when a lot of people has the issue, since normally the next update contains the fix, but in this case its getting very annoying to come back the next day and the laptop crashed.

Any other ideas if someone is still experiencing the issue will be greatly appreciated.

SOLUTION WORKAROUND by preventing MacBook from going into *deeper* Standby

I used the following approach to fix the problem on my mid-2012 Retina MacBook. I have not had a Sleep/Wake failure in over a month:

-------------------

At a Terminal Window, type:

"sudo pmset -a hibernatemode 3 standbydelay 300000 autopoweroffdelay 14400”

-------------------

(The net Solution Effect is: After the lid is closed, my MacBook does not go into deeper standby or write memory to disk for approximately ~3.5days (300,000sec / 60sec / 60min / 24hrs = 3.47days), which prevents a Sleep/Wake crash. I believe either the standbydelay and/or the autopoweroffdelay timeframes/transitions are when the Sleep/Wake crash occurs. Unless I leave my MacBook sleeping with the lid/cover closed & unused for more than 3.5 days, I have not had the Sleep/Wake crash occur.)

OPTIONAL ADDITIONAL DETAILS:

Here's the background detail of my experience. It may not be explicitely/perfectly accurate, but this is what I have researched and what I have observed to work in a repeatable fashion with my Mid-2012 Retina MacBook Pro:

LIFECYCLE of Power Management:

(1) Sleep: After Lid closed it takes about 30-60sec to put system/CPU into sleep mode (RAM/memory is still powered on for quick resume when you open your lid/cover)

(2) Standby: standbydelay measured in seconds is configurable and governs how long until standby happens (standby I think is when RAM/memory is written to disk and powered on or off, depending on hibernatemode)

(2.1) hibernatemode: "hibernatemode 3" leaves RAM powered on and enables using/setting autopoweroffdelay, which is the default for Retina MacBooks. Unless hibernatemode is set to '3', you can not use autopoweroffdelay. I have heard this setting called a 'smart sleep' feature that was introduced with 'newer' MacBooks.

(3) AutoPowerOffDelay: autopoweroffdelay configures how long until RAM/memory is powered off for maximum battery life.

My Recommended pmset Sleep/Wake Sleep/Standby/Hibernate Settings:

(These are the same pmset settings shown at the beginning of this post, just with more description)

- At a Terminal window command prompt:

"sudo pmset -a hibernatemode 3 standbydelay 300000 autopoweroffdelay 14400”

What happens with these settings, based on what I have observed/tested?

(1) Sleep > (2) Standby > (3) Power off Mem for maximum battery life:

1) Sleep: After Lid is closed it takes about 30-60seconds to put system/cpu into Sleep mode.

2) Standby: Then after 300000sec = ~3.5days standbydelay, RAM is written to disk and Mem is still powered on (300,000sec / 60sec / 60min / 24hrs = 3.47days)

3) PowerOffMem: Then after 14400min = 10days autopoweroffdelay, Mem is powered off for maximium battery life

How I came to the above pmset recommended settings:

I believe either the standbydelay and/or the autopoweroffdelay timeframe is when the Memory/Disk transition occurs that causes the Sleep/Wake crash to occur. Unless I leave my MacBook sleeping with the lid/cover closed & unused for more than 3.5 days - 10 days, I have not had the Sleep/Wake crash occur. I have experimented with smaller #s for standbydelay and autopoweroffdelay with some success. Sometimes the Sleep/Wake crash occurs after the standbydelay and other times it seems to occur after the autopoweroffdelay. Therefore, I decided to make my standbydelay longer than a typical long-weekend when I would not be using my laptop, and make the autopoweroffdelay longer than a typical 1 week vacation, so that I could leave my MacBook on *all the time* if I so chose and have a good chance of avoiding Sleep/Wake crashes. It has been working for me almost perfectly for over 6 months. And, I have been Sleep/Wake Crash free completely for the last 1-2 months.

I hope this helps some and works for most.

I think I may have found the reason as to why the screen suddenly goes black...

Its due to the "Hot Corner" functionality. The screen has 4 programable Hot Corners that functions like an additional set of TrackPad gestures. When you move your mouse near one of the four corners the function kicks in. Whether its view Dashboard, Mission Control or PUT DISPLAY TO SLEEP.

The Fix:

In the DESKTOP & SCREENSAVER folder in the system preferences, click to SCREENSAVER page. At the BOTTOM RIGHT corner is the Hot Corner button. Click that then change all of the hot corners to - (null) or whatever function you want it to be.

Hope that helps.

Bro what happened about this issue !!!

Hi All,

I found the issue in my case that was causing this report to appear. Please see thread:

https://communities.vmware.com/thread/467919

Before upgrading to Mavericks I used to kept my Windows VM running and when I close the lid and open it the next day no issues.

Now with Mavericks this appears to be a problem. I have test it already shutting down or suspending the VM and the laptop never chashed.

BillHahn workaround works fine as the crashes only happens when the laptop goes off completely and then you resume work the next day.