Q: New rMBP sleep/wake failure crashes

In my case, this happens with NO external drives attached.  The WD issue may exacerbate the problem, but it is not the sole cause.

Unfortunately this is just not true.

My D Link USB Hub also causes the same issue.  Even if there are no USBs attached to the Hub.

Again, this leads me to believe this is universal to powered USB devices (devices that rely on an external power source, not just BUS power)

Nope.  turning off power nap did nothing for me.  I plugged in my HD, did a backup, turned off power nap, and walked away for about 15 minutes.  when I came back, same old thing.  computer had restarted, and I got the sleep/wake crash report.

it works for me !

rMBP 13" haswell. WD (and other) HD connected.

after 10.9.1, unchecking the power nap and all other options for energy saving my book doesn't restart any more since yesterday.

i tried disable power nap before 10.9.1 with no success.. now it works here.

ok an update on my sleep wke failure, Got my macbook pro back they changed the Lgic Board and my problem is gone, I repeat no sleeping problem at least for now that is.

I still think that not is a hardware problem.

This problem are in new late 2013 pro 15 , 13 , air and old MacBook with mavericks

All is very strange ...

Well since deactivating Power Nap I've had no reboots even with my WD drives attached via USB 3.0. So far so good, lets hope this bug gets patched soon.

I started having multiple Sleep Wake Failure experienced a problem issues right after I updated to 10.9.1.  Here is a short history:

Bought a stock rMBP 13" on Nov 29th w/10.9.  Fired it up on Dec 2nd, and did not migrate from previous MBP mid-2009, since that computer was overloaded with migrations from past computers. (Been a Mac user since 1985-512k) 

Immediately had problems with RAM/Virtual RAM not working (w/no apps running, Activity Monitor indicated all 8GB of RAM was being used by system processes, and no Virtual Memory was being used up).  Also had problems with the computer logging me out after a certain time of inactivity.  I would come back after a break, and I would see the log-in screen.   

After two days and many hours on the phone w/Apple, investigating all the usual suspects, ended up erasing the flash drive and re-installing Mavericks.  The RAM problem went away, but still experienced at least 3 FCPX, 2 Evernote, 2 TextEdit, 4 Chrome Crashes in about a two week period.  And still the Log-Outs. 

I spoke to at least 2 Senior Tech Support advisors, and none of them were able to resolve the log-out problem.  I was convinced it was a software problem, since this happened to my mid-2009 MBP as well right after I upgraded to Mavericks.   I did a little digging and found that in System Prefs/Security & Privacy there is a buttom at bottom right: Advanced.... which needs Admin password to get in.  There, the box that said Log out after XX minutes of inactivity was checked as the default.  I unchecked it on both computers, and the problem went away.  Until...

...I Upgraded both computers to 10.9.1, and that night the rMBP re-booted by itself, but the 2009 MBP was just fine.  The rMPB rebooted at least 3 times in a two day period.  So on the phone with Apple Care again.  For about 2 hours.

In 28 years of owning Apple computers and dealing with tech support, I had one of my most unproductive and disturbing conversations with a "Senior Advisor" early this week.  About an hour into our conversation, it became obvious to me that they are covering up for the fact that while 10.9 might be a great OS, it is buggy, and 10.9.1 solved some and introduced others.  I could not get an honest answer, except a lot of runarounds with "do the usual tests..., take the computer in for hardware check... disconnect all your peripherals..."  It almost seemed as though they were trying to keep me busy until they found the answer. 

I told her that running my computer without the peripherals (a Keyboard, Magic Mouse, 2 external monitors, and a 4 TB USB3 drive was not an option, since I bought the computer specifically to edit using FCPX.  She kept coming back to wanting to put the blame on a peripheral.  She suggested that I contact the manufacturers to see if they had new drivers, etc...  And these are peripherals that I've used for over a year with my 2009 MBP with never a problem.

When I asked her point blank what does it mean when the computer generates a crash report that says at the top: Sleep Wake Failure experienced a problem, she could not (or would not) answer me.  

At one point in our conversation, while I was on hold, I came to this thread.  When she came back on the line, I told her that there were 13 pages of posts about this same problem, so how could it be that Apple has not heard anything about  Sleep Wake Failure and why aren't they working on a solution.  Her answer was even more astonishing.  She said that "These are Apple discussion boards, you don't know all the information that's there, you don't know whether it's correct or not...It's not a reliable source of information". 

After a few more totally useless exchanges,  I asked to be transferred to someone else who might have that answer, she said No! She was as high as I could go.  And that if I wanted to talk to another advisor, I'd have to call back Apple Support.  I was flabbergasted. She said "I am not doing this to being spiteful, but it's just our policy.  I am not able to transfer you to someone".  

I don't want to go on and on about this tech support call that left me speechless.  I'll rant about it in another thread. 

What I want to report is that, I read each and every post in this thread, and I noticed that my 2009 MBP SysPref does not have a checkbox for Power Nap and Prevent Computer from sleeping, as is the case with 2013 rMBP.  So I unchecked all the boxes on the Energy Saver Pane, and so far the rMBP has been going to sleep and waking up just fine and not re-booting,  with the following apps open: FCPX, Evernote, Chrome, Preview, Fission, Audio HiJackPro, and a few others.

Permanent Fix?  Maybe not, but it seems to hold for the time being.  Thank you all for posting on this thread. 

I wish Apple would change their opinion of these discussion boards and take their loyal customers a little more seriously. 

I'd like to know if people have Time Machine running (specifically the NEW 2TB TIme Capsule). I have been experiencing this problem (I'm on my second machine LATE 2013 15" Retina MPB) - I have a Powered USB connected with 4 HDD drives.

I TURNED OFF TIme Machine at night - for the last 2 nites - and my machine did not CRASH - 2 nites in a row.

I'm trying to figure out if TM is a contributing factor.

No Time Machine for me and no USB devices at all. I went to the Genius Bar this morning after my MB Pro refused to wake after sleeping. They reset the PRAM to wake it up and ran diagnostics but for ound no hardware problems. They looked at my system logs and found a bunch of Kernel messages relating to an antivirus program I was running. They advised to uninstall the AV and see if it helps. Too soon to tell.

Anyone else running AV and experiencing the non-waking / wake to perpetual gray screen problem?

This is not the same issue. This thread is for machines that automatically reboot after sleep/wake failure. When you come back to your machine after it has been asleep, it has rebooted and asks you to log in. Your problem is failure to wake up after sleep.

Its back :(

Only One Happy Day. Now its the Same Problem again.

10.9.1 and turning off all sleep-Things doesn't help for me.

The question is, how Long to wait until sending it to Apple..

I read this whole thread. Here's what I found:

I am speaking about the issue of crash/reboot while on sleep, not the issue that people are having while waking from sleep or frezees while waking from sleep

5 people in this thread reported that they this issue and Apple exchanged their machine, but the problem persisted. The 5 people are: jb510, Casey Kiernan1, jurdawg (third machine exchanged), pinda18 and Davidmd.

Only 1 person said that they exchanged their macbook and the problem is now fixed. This person is: faslkdjfalskdjfalskdfj (he was a big vague, and I don't know if I can trust what he said)

Sorry. I should have updated.... It stopped for about a week. Then it started again. Totally software

Thanks a lot. So...

6 people in this thread reported that they had this issue and Apple exchanged their machine, but the problem persisted. The 6 people are: jb510, Casey Kiernan1, jurdawg (third machine exchanged), pinda18, Davidmd and faslkdjfalskdjfalskdfj.

0 people said that they exchanged their macbook and the problem is now fixed.