Sleep/wake crash OSX Mavericks, Macbook Air 2013

I've got the same problem! I have to hard reset the MBA with the power button. I'm thinking that it's one of Mavericks' new power management "features" like app nap. Also, have you noticed that your Finder has been excruciatingly slow, particularly when trying to open a file in a program? The little spinner just spins for what feels like an eternity until it finally finds the files in the directory, when all you wanted to do was quickly download a picture to your pictures folder instead of downloads?

I didn't have these problems with Mountain Lion, and my MBA was super fast. Now I find my Mac to be less usable, and much less reliable, not to mention that I can't downgrade to a version of OS X that was working very well for me.

Mid 2013 13" MacBook Air, 1.3 GHz Intel Core i5, 4 GB 1600MHz DDR3 RAM.

I was able to make that happen by closing the lid and opening it right away -- on my MacBook Pro running Mountain Lion and earlier versions. May not be a Mavericks issue.

Phil

I have iMac mid 2010. I experienced the same problem since I upgraded my system to Mavericks: when the display goes to sleep it won't wake up again. Mouse click and key press won't wake it up even though the computer itself is on. After turning the computer off and turn it on again I receive a sleep wake failure bug report. I have reported the bug with a system report to Apple through Apple Bug Reporter.

Having similar problem with 2013 MacBook Air. Since installing Mavericks, on at least 3 mornings I have opened it up and found it crashed, either with a black screen or just frozen, requiring a power-switch reboot.

I've got the same problem. It appened twice with my brand new Macbook Air, bought just two weeks ago! It's annoying, Apple please, fix that!

I'm having sometime simular, the screen is going in to power-saving and I'm unable to wake it up. The only thing that seems to work is hard power off.

This is happening to me too. Several times, when I was working on my MBA mid 2013, eg listening to music or talking on skype, the screen went completely black, but the whole computer was working (the keybord was still shining). However I was unable to make it work unless pressing the turn on/off button. There was also some strange sound going from my mac...

Same problem with my mid 2012 Air on maverick!

With 10.8. everything was ok ...

Intel-based Macs: Resetting the System Management Controller (SMC)

http://support.apple.com/kb/HT3964

People all above... Try to reset the SMC for your respective Mac models depending on the kind

I'm getting the same problem on my 11" MBA base model running Maverics. The backlight in the keyboard stays on and the screen is still on just displaying deep black.

Same problem here, MBA 13" 2013, finally annoyed me enough, so with a took a bit of testing, I am able to reproduce the "crash" I think this happed occasionally on a previous MBP 2012 (Mountain Lion), but I'd have to try to reproduce on that machine to know for sure. I am going to try SMC reset later once I have my power supply and I will report back.

SMC reset didn't work for me.

It appears I'm having the identical problem with my four day old late 2013 15" MBP shutting down and restarting with a Sleep Wake Failure. Based on this and related threads I've looked for rascally legacy software:

-Sound Flower

-Norton

-Virtual Box

But none of these usualy suspects are present.

I just turned off "Power Nap" in the "Energy Saver" section of "System Preferences" but won't know the results until tomorrow as it seems to only misbehaves when I'm not paying attention to it.

In the meantime I'll keep looking for info on a fix and I'll post back if I find anything.

Here's the top bit of the VERY long error readout:

Date/Time: 2013-11-18 23:12:47 -0500

OS Version: 10.9 (Build 13A3017)

Architecture: x86_64

Report Version: 18

Event: Sleep Wake Failure

Steps: 51

Hardware model: MacBookPro11,3

Active cpus: 8

I'm also having this difficult on a brand new MacBook Air running Mavericks. It tends to happen in the most inopportune times, and is a real annoyance. Hoping for a rapid response from Apple.