Sleep/wake crash OSX Mavericks, Macbook Air 2013

Just happened again - so obviously not fixed in 10.9.1 :-(

It's also happening on my 2013 MBPr. I open my macbook after a couple of hours to find that the computer has crashed and restarted itself. Not impressed. What ever happened to quality control and it just works at Apple?

A friend of mine had the same issue and figured out that it happens only when mac is going to sleep. During next circa 3 seconds after the screen goes black you should not press any key or touch pad, because then it'll crash. The probable reason is that when mac is going to sleep it starts saving data on disk and the bug is that it can't be disturbed during this 3 seconds period. If so, it'll crash immediately. Obviously it's a bug that is rooted deep inside OS and hope they'll fix it in 10.9.2. For now, I recommend you to be careful and when screen starts getting black, don't touch impulsively keyboard, just wait a few seconds. Moreover I believe it occurs on other macs as well, MBA is not awarded:)

Do your macs crash even when you don't press any key?

Something similar has happened at least twice on my mid-2007 iMac since upgrading to Mavericks. I don't get the black screen that others have reported. The screen wakes, but I don't have control of anything. The cursor can be moved with the mouse, but that's all. I can see when OSX crashed because the clock is stuck on that time. I have to hard-restart the Mac with the power button.

In another thread, Plotinus mentions following should help:

"Go to system preferences > energy settings > UNcheck "put hard disks to sleep" on both tabs for charge and battery."

Does this resolve the issue for anybody else?

the other thread: https://discussions.apple.com/thread/5537842?answerId=23919123022#23919123022

this def. does not work. did this weeks ago when the first crashes appeared …

Update

After visiting the Genius Bar a 2nd time (same rep), they decided to send it to a repair shop for further diagnosis. The repair shop replaced the Logic Board and the I/O Flex Cable and declared the issue resolved. I picked up my repaired MBA today, and, while still in the store, tried to recreate the issue. I got it to crash following the exact steps I've outlined previously in this thread.

They sent me back to the genius bar to show the problem to yet another rep. Fortunately, the original rep was working today and could confirm I wasn't crazy. I reproduced the problem for the new rep. Given all the diagnosis and work done on this machine, they gave me a brand new MBA and sent me on my way. They were quite busy, so I didn't bother sticking around long enough to test the new MBA. (Plus, if the same problem existed on the new machine, I would be pretty sure it was an OS or systemic MBA issue).

I am at home now and... drum-roll please... the new MBA crashes as well! I think all the apple support experts lurking this thread can now have some confidence that this is indeed an OS software problem (or a systemic problem with MBA hardware). They need to get their hands on a newish MBA, and follow my steps to look for this issue (many times, guys, once is not good enough to say the problem doesn't exist. You have to try waiting 0.25s, 0.5s, 0.75s, 1s, etc after the screen goes dark. Pls see my previous step-by-step in this thread).

At this point. I am going to deal with it. I now have a brand new MBA, and hopefully, this issue will be resolved via an OS update.

If you'd like to get a new MBA, I suggest honing your ability to reproduce the problem, visiting your local Apple Store (possibly 3 times), and demonstrating it for them. If Apple notices enough new MBAs being handed out on warranty, they'll do something...

Cheers everyone, signing off...

Carl

I haven't tried your steps to lead to a crash, but I can attest that the issue is not limited to the MBA, since I have seen it at least twice on a late-2007 iMac, and it always comes when waking from sleep.

Interesting. Can you reproduce the crash consistently on your iMac? If not, you'll encounter much skepticism (from me, too 🙂).

It's happened twice at least. Wake the iMac from sleep, and it's frozen. The cursor can be moved, but everything else is stuck. The clock on the menu bar indicates that the freeze occurred when sleep was envoked. Since I've been using this iMac for over five years now and it has never mishaved in any way before Mavericks then I think this is about as convincing as it needs to be. The symptoms are also close enough to what you have reported on your two MBAs to have the same likely source at the OS level. I wonder if OSX even generates a crash report in this case, since the Mac has to be restarted with the power button.

I can confirm that this is not a hardware problem. I have experienced the same issue on iMac late 2010 ever since I upgraded from Mountain lion to Mavericks. The only thing that could help me was to disable screen sleep.

The same thing happens to me. Hopefully it will resolve with an OS update.

I would question if this is related to MacBooks at all. It seems purely a general issue of 10.9 (and 10.9.1). The fact that it fails by going to sleep is the common factor. My 2010 MacPro can't sleep now without being powered off and on to bring it back. The machine was bulletproof on 10.6.8. It shows the same symptom of turning the monitors back on but not actually bringing video up.

I know it's inconvenient (not to mention one reason I don't run Windows), but my plan is to turn off all sleep/hibernation and using only screen saver (which doesn't have any problems) and shut down the machine nightly (back to the 1990s). I have always loved that with OSX, you could leave the machine in a steady state and only reboot when there is an update, with no updates, you could run for months. This is sad that Apple is not responding to this and WiFi problems of Mavericks.

I also manage many Macs of which two are on 10.9.1. They are servers so I don't sleep them, but when I inadvertently left power saving on on one of them, a 2012 Mini-server, it had to be powered off and on to bring it back.

Apple, please respond to people on this issues.

My problem isn't as severe as this, at least in terms of frequency, but it does happen. Thinking about the occurrences, I have an idea it has to do with apps that aren't behaving properly with versioning. I'm pretty sure I've always had a Pages document open when it happened. This is the old version of Pages, the new one being quite useless to me. Just a guess.

I have the same issue. Has anyone found a resolution yet?

Mine occurs on my 2013 MacBook Air 13" with Mavericks that is less than a week old. The computer will enter sleep mode and I will try to quickly wake it from sleep causing it to crash. The only way to remedy this crash is for me to do a hard resert by holding down the power button cusing me to loose all of my work that I had open. Really annoying...