I'm on a separate forum and had a user suggest typing kextstat | grep -v apple into terminal to see what non-Apple kernels were running. I had AirParrot which I no longer use anyway and thought I had deleted.
After following some simple terminal commands detailed on AirParrot's website, I removed all Mavericks-conflicting issues and seem to have my sleep/wake issue on my 2013 MBA fixed. It's only been a few hours, granted...However, having literally tried everything with absolutely nothing working and being able to 100% reproduce the issue on demand...This is very promising.
I might be back on here shortly saying it's reappeared, but wanted to let everyone know ASAP just in case...wish I had known this months ago!
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.
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.
Found this "fix" on another forum and it worked for me... so far, no crashes after my 2009 iMac (w/ Mavericks) sleeps!
Open terminal, and type in the following commands ( without the quotation marks )
"sudo pmset autopoweroff 0" and "sudo pmset standby 0"
Using Sudo will probably prompt you for your password...this is the system password that you use on your Mac
MID-2010 Same problem.
Sleep Wake Failure problem began almost immediately after switching to Mavericks. Mavericks has ruined my computer! Took the computer into the local Apple store and they had no idea what to do. Never had a problem until I began using mavericks, now sleep doesn't work at all. Close the lid and i get a blank white screen and have to do a hard restart every time. Come on apple!
I upgraded to mavericks last week and my up-till-then faultless 2012 Air won't wake from sleep. It really won't wake. All that happens is the fan goes to max. I press and hold the power button to force it to shutdown as it's the only thing that works. Now I have the problem of how to make it start up again. Nothing works and I have to wait hours or even days randomly trying to power it up. Very frustrating. Took it to Genius Bar yesterday and of course it perfomed faultlessly and passed all their tests.
So how can I start it up again?
Well, same here on a new mac pro... First screensaver, then displays go to standby, mac goes to sleep. If i do not wait too long, i'm able to wake it up without an issue, but waiting longer, it just powers off. On restart same sleep wake failure message.
Guys, i tried EVERYTHING mentioned here or somewhere else, from resetting SMC, NVRAM, changed RAM, ... I also played around with pmset... On my mac, autopoweroff was set to 1, and autopoweroffdelay was set to 14400. with a whole bunch of hope i set autopoweroff to 0. that's it, i thought. (Btw, why we can't change this in the system settings?)
No. Same behavior. Uhm, ***?
I do not have this issue on my 27" imac latest model, where autopoweroff is set to 1 too?
Could this really be a problem with specific peripherals and related drivers?
Hey apple, may we have a statement on this?
I have noticed that in the threads associated with this Mavericks bug, when people take their laptops to a "genius bar", it never fails. This suggests to me that aside from 3rd party software and drivers that some found to be a problem, other hardware connected to the system may also be having trouble during the awakening state.
It seems like a great test for those of you who have had the problem disappear when taking it to the genius bar, to just unhook all your thunderbolt, firewire and USB devices and run like a real laptop while testing. If so, we can add third party hardware as another catalyst for making the Mavericks bug appear. Perhaps reporting something like that may make Apple finally realize they have a problem.
My identical problem seems to have been fixed by upgrading drivers to a firewire device, so it seems plausible that the problem could be brought on by hardware, software and drivers that Apple would not have tested. I think it's worth a try to run disconnected and see if the problem goes away (like it always seems to do at a "genius bar").
Hey apple, may we have a statement on this?
Are you expecting to see such a thing here? I can pretty much guarantee it won't appear unless somebody finds it elsewhere and quotes it here. Apple doesn't read most of what we post and rarely answers directly when they do.
You'll have better luck by giving them feedback directly at http://www.apple.com/feedback/macbookair.html
My iMac Mid 2010 has suffered with this issue since I upgraded from Mountain Lion to Mavericks, now running 10.9.2.
I have always used the default Energy Saver settings with it set to sleep at 10:30 PM and Wake at 8:00 AM. Since upgrading to iOS Mavericks I have had daily problems with waking from sleep. Until a week ago, I had to power down and restart. It would power up and after logging in, sometimes, a wake error report displayed and/or there would be no response when I tried to use the mouse. If the mouse did not work I had to power down and restart a second time.
While attempting to wake the iMac from sleep, I observed the activity light on the mouse would not flash until after multiple clicks. Once the activity light flashed my iMac would wake as it should. I now do this if it fails to wake from sleep. So far it has worked every time. This also seems to solved the problem on a new MBPR running Mavericks 10.9.2 except I have to use the track pad.
My problem was solved after removing 3rd party software using too much resources and eventually slowing down my MBP to something stickier than honey.
I would backup my computer and make a clean installation with only Mavericks and see if that helps. After I would install my software and see if there's any issues after.
I have the exact same problem on my brand new MacBook Pro that came with Mavericks.
2.3 GHz Intel Core i7
16 GB 1600MHz DDR3
NVIDIA GeForce GT 750M 2048MB
OS X 10.9.2 (13C64).
I keep my old Macbook Pro running 10.6.8 beside my new laptop for all the things that don't work in Mavericks.
Come on Apple!