Sleep/wake crash OSX Mavericks, Macbook Air 2013

Same problem for 4 days now on new 2013 macbook air running mavericks!!

hey andy,

Thanks for posting the suggestion to report Mavericks OS bug to Apple. I have just done that.

Regards

Im having the same issue in my brand new mba. ****** annoying ****!!!!!!!! Just reported this **** bug. Please fix it apple.

Another incident on my 2007 iMac, but more like others have experienced on their laptops. Tapped the keyboard to wake the Mac, clicked to close an open Safari window, and the screen went black and the Mac became unresponsive. I think this might in my case have something to do with Mavericks attempting to update the open windows on wake. This problem is nowhere as common on my iMac as many are reporting on their MBAs, but it does happen. I think this was the third or fourth time for me.

I am also having a sleep wake failure with my new Air (bought 2/2/14). When waking my speakers, microphone and camera are non responsive.

[SOLVED] In my case I have been struggling with it for over two weeks.

The crashes stopped completely after disabling Dropbox (also disabled "Start Dropbox with system startup") and launching it only when in need to sync files with other devices!

Google drive, Dropbox and other file sync utilities are in cause of the sleep-wake failure in my 2013 macbook air 13 inches.

I also did other tests before resolving to try exiting Dropbox (since I need it regylarly and never thought it would be the cause):

Reinstalling Mavericks didn't solve the problem!

Removing Parallels didn't solve the problem.

Removing Kaspersky: crashes became less frequent. (Anti-virus software are also in case of some of the crashes, and I happened to fall within the bad combination of both).

Now the thing is that if every file sync tool causes sleep-wake crashes: is it Mavericks that's not well suited for updated and highly used software?!

The choice of Dropbox, Parallels and Kaspersky was based on the fact that most of crashes reports generated errors from these softs!

I experienced sleep/wake failure problem on iMac late 2010 with 10.9.0, 10.9.1, and 10.9.2 pre-release seed. Here is how I could avoid this problem:

go to: system preferences -> energy saver

then, uncheck all the options:

put hard disks to sleep ...

wake for network access

start up automatically ...

this solved the problem for me.

My guess is the first one may be responsible for black screen, and the second one for system restarting itself.

I tried this earlier and it's not the reason for my MBP crashing when waking up/turning slow as sirap. I have even gone through all my applications and Browser extensions and removed all things there. NOthing solved my problem unfortunately.

Further more I thought maybe it might be the Avira - antivirus program, but i don't think that is it since I turned of real-time-protection and that did not help either.

I don't have any syncing software like Dropbox or Sugarsync.

10.9.2 update is up.

Does somebody know if the 10.9.2 patch fixed the problem?

I might have found a solution to my problem at least. I practically uninstalled all little programs and add-ons I didn't use except my antivirus Avira.com. There was this process Savapi that took a lot of processes, so I tried to turn off the real-time scanning, but it did not solve my problem. So I uninstalled the Avira and installed Avast! instead and it looks like my computer don't crash when waking up now. Or at least not yet.

So have a look at your antivirus programs, might be one solution. 🙂

Well, I don't have any antivirus installed, only the Little Snitch firewall. As the problem started with Mavericks, I think it hasn't anything to do with my installed apps, though.

Same here, it started when upgrading and it might look like it was an app not compatible with Mavericks. Well, at least for me then. But will have to see... I have used Etrecheck and gone through all my browser extensions, 3-party apps and all other things, so if this don't work, then i'm screwed :O

You're right, it has absolutely nothing to do with installed apps, it can be reproduced on a completely fresh install of osx.

Nevertheless, YES, this bug does appear to be fixed in 10.9.2!