Random sleep mode after Mountain Lion install

MBA 13 i5 8gb 128gb 2013, just purchased a few days ago, same problem.

MacBookAir6,2 i7 1.7ghz 8gb, same problem. Migrated my profile from a 15" MBP retina that was not experiencing this problem.

I find that this often happens right after I wake my display. I'll wiggle the pointer, the display will wake and then the system will sleep.

Wow, Apple. A year- old thread with tons of users reporting the same problem. I hope you are reading this. If not to resolve the issue at hand, perhaps your support extends far enough to help us turn this thread into a petition. Would that get your attention?

No need to describe what I am experiencing. 100 users before me have reported the same problem.

Add me to the list.

MacBook Air 11"

Less than a month old

13" MBA mid-2013, same problem here. Wonder if it's hardware related, dont really want to go through the trouble of taking it for warranty service if its an unaddressed software problem.

Exact same issue here- 13" MBA mid-2013, 1.7GHz i7 running 10.8.4. From time to time when I wake it from sleep and start doing something, it abruptly goes back to sleep after a short time (typically between 5 secs and a minute, maybe?)

It happened the first time within a half hour of getting the machine in June, practically before I'd even installed anything at all on it, and still happens. Plugged in, on battery, iPhone in my pocket, no iPhones in sight, doesn't matter— can't seem to find any triggers that would explain it. I keep hoping for a 'narcolepsy patch', but I'm worried that there's a hardware issue instead!

Same Problem. THIS MAKING ME HATE MY MBA. Cannot use with others looking on…

Here I got some logs from the moment that I wake up the laptop till it randomly sleep crashes or however you want to call it:

8/21/13 3:13:04.799 PM WindowServer[88]: CGXSetWindowBackgroundBlurRadius: Invalid window 0xffffffff

8/21/13 3:13:04.802 PM loginwindow[65]: find_shared_window: WID -1

8/21/13 3:13:04.802 PM loginwindow[65]: CGSGetWindowTags: Invalid window 0xffffffff

8/21/13 3:13:04.802 PM loginwindow[65]: find_shared_window: WID -1

8/21/13 3:13:04.802 PM loginwindow[65]: CGSSetWindowTags: Invalid window 0xffffffff

8/21/13 3:13:05.118 PM WindowServer[88]: Created shield window 0x646 for display 0x042737c0

8/21/13 3:13:05.118 PM WindowServer[88]: device_generate_desktop_screenshot: authw 0x7f96ca942190(2000), shield 0x7f96cab1aa40(2001)

8/21/13 3:13:05.135 PM WindowServer[88]: device_generate_lock_screen_screenshot: authw 0x7f96ca942190(2000), shield 0x7f96cab1aa40(2001)

8/21/13 3:13:09.582 PM WindowServer[88]: handle_will_sleep_auth_and_shield_windows: releasing authw 0x7f96ca942190(2000), shield 0x7f96cab1aa40(2001), lock state 3

8/21/13 3:13:09.582 PM WindowServer[88]: handle_will_sleep_auth_and_shield_windows: err 0x0

8/21/13 3:13:09.584 PM WindowServer[88]: Created shield window 0x647 for display 0x003f003d

8/21/13 3:13:09.584 PM WindowServer[88]: handle_will_sleep_auth_and_shield_windows: releasing authw 0x7f96ca942190(2002), shield 0x7f96cab1aa40(2001), lock state 3

8/21/13 3:13:09.584 PM WindowServer[88]: handle_will_sleep_auth_and_shield_windows: err 0x0

8/21/13 3:13:09.610 PM WindowServer[88]: Created shield window 0x648 for display 0x003f003e

8/21/13 3:13:09.610 PM WindowServer[88]: handle_will_sleep_auth_and_shield_windows: releasing authw 0x7f96ca942190(2002), shield 0x7f96cab1aa40(2001), lock state 3

8/21/13 3:13:09.610 PM WindowServer[88]: handle_will_sleep_auth_and_shield_windows: err 0x0

8/21/13 3:13:13.934 PM WindowServer[88]: CGXGetWindowInfo: Invalid window 1617

8/21/13 3:13:13.935 PM Dock[150]: CGSBindWindow: Unable to obtain window information

8/21/13 3:13:13.936 PM Dock[150]: CGSGetWindowTags: Invalid window 0x651

8/21/13 3:13:13.936 PM Dock[150]: find_shared_window: WID 1616

8/21/13 3:13:13.936 PM Dock[150]: CGSGetWindowTags: Invalid window 0x650

8/21/13 3:13:13.936 PM Dock[150]: find_shared_window: WID 1615

8/21/13 3:13:13.936 PM Dock[150]: CGSGetWindowTags: Invalid window 0x64f

8/21/13 3:13:13.937 PM Dock[150]: find_shared_window: WID 1614

8/21/13 3:13:13.937 PM Dock[150]: CGSGetWindowTags: Invalid window 0x64e

8/21/13 3:13:14.705 PM WindowServer[88]: CGXRegisterWindowWithSystemStatusBar: window f already registered

8/21/13 3:13:34.788 PM WindowServer[88]: CGXSetWindowBackgroundBlurRadius: Invalid window 0xffffffff

8/21/13 3:13:34.790 PM loginwindow[65]: find_shared_window: WID -1

8/21/13 3:13:34.790 PM loginwindow[65]: CGSGetWindowTags: Invalid window 0xffffffff

8/21/13 3:13:34.790 PM loginwindow[65]: find_shared_window: WID -1

8/21/13 3:13:34.791 PM loginwindow[65]: CGSSetWindowTags: Invalid window 0xffffffff

8/21/13 3:13:34.000 PM kernel[0]: PM notification timeout (pid 181, Google Chrome)

8/21/13 3:13:34.000 PM kernel[0]: PM notification timeout (pid 214, Google Chrome He)

8/21/13 3:13:34.000 PM kernel[0]: PM notification timeout (pid 215, Google Chrome He)

8/21/13 3:13:34.000 PM kernel[0]: PM notification timeout (pid 217, Google Chrome He)

8/21/13 3:13:34.000 PM kernel[0]: PM notification timeout (pid 228, Google Chrome He)

8/21/13 3:13:34.000 PM kernel[0]: PM notification timeout (pid 229, Google Chrome He)

8/21/13 3:13:34.000 PM kernel[0]: PM notification timeout (pid 232, Google Chrome He)

8/21/13 3:13:34.000 PM kernel[0]: PM notification timeout (pid 1318, Google Chrome He)

8/21/13 3:13:34.000 PM kernel[0]: PM notification timeout (pid 1848, Google Chrome He)

8/21/13 3:13:34.000 PM kernel[0]: PM notification timeout (pid 1853, Google Chrome He)

8/21/13 3:13:34.000 PM kernel[0]: PM notification timeout (pid 1857, Google Chrome He)

8/21/13 3:13:35.077 PM com.apple.time[11]: Next maintenance wake [Backup Interval]: <date: 0x7fd2c8e0cc50> Wed Aug 21 15:58:28 2013 CEST (approx)

8/21/13 3:13:35.077 PM com.apple.time[11]: Requesting maintenance wake [Backup Interval]: <date: 0x7fd2c8e0cc50> Wed Aug 21 15:58:28 2013 CEST (approx)

8/21/13 3:13:35.089 PM WindowServer[88]: Created shield window 0x65b for display 0x042737c0

8/21/13 3:13:35.095 PM WindowServer[88]: device_generate_desktop_screenshot: authw 0x7f96c9466500(2000), shield 0x7f96cab1aa40(2001)

8/21/13 3:13:35.108 PM WindowServer[88]: device_generate_lock_screen_screenshot: authw 0x7f96c9466500(2000), shield 0x7f96cab1aa40(2001)

8/21/13 3:13:35.000 PM kernel[0]: 27608.199194: AirPort_Brcm43xx::powerChange: System Sleep

8/21/13 3:13:35.000 PM kernel[0]: AppleCamIn::powerStateWillChangeTo - root-domain power state = 0x00000002 (flags=0x00000004)

8/21/13 3:13:35.000 PM kernel[0]: en0: BSSID changed to 50:46:5d:cc:d4:f4

8/21/13 3:13:35.000 PM kernel[0]: wlEvent: en0 en0 Link DOWN virtIf = 0

8/21/13 3:13:35.000 PM kernel[0]: AirPort: Link Down on en0. Reason 8 (Disassociated because station leaving).

8/21/13 3:13:35.000 PM kernel[0]: en0::IO80211Interface::postMessage bssid changed

8/21/13 3:13:36.000 PM kernel[0]: IOThunderboltSwitch<0xffffff8017aeb000>(0x0)::listenerCallback - Thunderbolt HPD packet for route = 0x0 port = 11 unplug = 0

8/21/13 3:13:36.000 PM kernel[0]: IOThunderboltSwitch<0xffffff8017aeb000>(0x0)::listenerCallback - Thunderbolt HPD packet for route = 0x0 port = 12 unplug = 0

Same problem. MBA 13" 2013

latest mba 13, same problem.

some more clues (sorry if this has been covered, i may have missed it earlier in the thread): for me, seems to happen when i unplug from ac power. it often happens despite plugging right back into ac power.

basically what seems to be happening is this: unplug the computer. the os will start the countdown to sleep (in my case 1 minute). no matter what you do, you cannot stop the countdown. so now, whenever i unplug my mbp to move it, i have to move it, wait a minute for it to sleep, wait another minute or two to actually go all the way to sleep, wake it again, then i can start working.

(this is speculation - i haven't precisely timed it to see if it's 1 minute, haven't changed that to 5 minutes and tried again, etc. - there's really only so much time in my life i can dedicate to everything that goes wrong with my mac, i'll do this stuff when i can and post my results!)

i suspect this is somehow related to new power management in mountain lion, which requires apps to explicitly and constantly tell the os not to sleep while they are active, as opposed to the old method in which app activity was enough to keep your mac "awake". while this doesn't seem to be directly related, i'm guessing this came with other changes to power management that are less well documented (or at least less well known by me).

my next steps: test the timing to see if it actually matches my "energy saver" settings. next, reset smc. i'll report back anything interesting.

EDIT: forgot to mention: mbp 15" 2.53ghz mid-2009

Hey playerzero - while you're experimenting try logging in before disconnecting from the power source... that does the trick for me everytime... if I ever forget, and unplug before waking and signing in, she goes to sleep in less than a minute...

I just found out how to make this repeatable it seems. Try this:

Don't completely sleep your computer. Try this to only sleep the display. Do ctrl+shift+eject (or ctrl+shift+power on MBA) and wait for the display to sleep. Then move your mouse or something to wake it up and log back in. Wait about 30 seconds ... does it die/sleep itself? For me it happens everytime I sleep this way. Try it a few times, is it repeatable? It was for me. Try sleeping with cmd+opt+eject (or cmd+opt+power for MBA). Does the bug happen? Not for me.

So, conclusion? This bug is triggered when the computer tries to sleep in a weird scenario, maybe it tries to sleep itself but sets the display to sleep first ... blah blah, who knows. I did some supersleuthing to try to probe the matter and found something that seems to work for me. It uses a command line program called pmset, a power management tool.

Try this:

Open a Terminal window (Apps->Terminal)

In the command prompt, enter this:

sudo pmset -b sleep 20

sudo pmset -b displaysleep 10

sudo pmset -c sleep 0

sudo pmset -c displaysleep 15

The first two lines change settings to use while on battery (this is why there is a -b). They will set your Time-Til-Computer-Sleep to 20 minutes, your Time-Til-Display-Sleep to 10 minutes while on battery. (If you get errors about some time being longer than another, try to set the times/run the commands in a different order).

The next two lines do the same (change settings) but for while you are plugged into a charger (that is what the option -c is for). The 0 for pmset -c sleep is to set it to never sleep while plugged in.

Feel free to change those numbers around to whatever you want to use for your machine.

If you do these settings but hate them/want to get rid of them, you can delete these files (/Library/Preferences/SystemConfiguration/com.apple.PowerManagement.plist, /Library/Preferences/SystemConfiguration/com.apple.AutoWake.plist) apparently. I haven't tried deleting them but others report it will in fact turn of the settings you have invoked ith pmset.

This seemes to have worked for me. Good luck in trying. I will report if it comes back again.

Oh wow! that reproduced it for me! Now I have something to show the guys at the apple store! Thanks!

Same problem. 2013mba. 2nd apple I've had this problem on. Shocking to keep coming back to this thread for over a year and seeing not a single idea from Apple. Itunes has gotten pretty buggy too in the last few months. Slopes for the slope throne?

MBA 2013. Same problem.

Can reproduce it using isospin instructions.