Freeze when screen saver active or display asleep

[Flash SWT]

I've suddenly started getting freezes on my Mid 2012 MacBook Pro Retina. Running 10.8.5 these crashes started immediately after installing the Digital Camera Raw Compatibility Update 5.01 a few days ago. Not sure if that is related at all though.

I can reproduce it consistently by putting the display to sleep or starting the screen saver. When trying to rewake the display I'll get a beach-ball and the only solution is to hold down the power button.

Interestingly this only happens when "Require password after screen saver begins" is turned on. So the resulting password dialog when trying to wake seems to be the issue.

I'm using the Apple default "Message" screensaver with a clock. It also happens with two other standard Apple screen savers I tried. The screen saver keeps running so the machine isn't totally "frozen" but there is no way out of the situation besides powering off.

Has anyone else seen anything like this? Any thoughts?

Related console messages appear to be:

11/14/13 2:23:56.333 PM WindowServer[95]: Created shield window 0x76 for display 0x04280380
11/14/13 2:23:56.362 PM WindowServer[95]: device_generate_desktop_screenshot: authw 0x0(0), shield 0x0(0)
11/14/13 2:23:56.382 PM WindowServer[95]: device_generate_lock_screen_screenshot: authw 0x0(0), shield 0x0(0)
11/14/13 2:24:20.044 PM WindowServer[95]: handle_will_sleep_auth_and_shield_windows: no lock state data
11/14/13 2:24:20.046 PM WindowServer[95]: Created shield window 0x77 for display 0x003f003d
11/14/13 2:24:20.046 PM WindowServer[95]: handle_will_sleep_auth_and_shield_windows: no lock state data
11/14/13 2:24:20.046 PM WindowServer[95]: Created shield window 0x78 for display 0x003f003e
11/14/13 2:24:20.046 PM WindowServer[95]: handle_will_sleep_auth_and_shield_windows: no lock state data
11/14/13 2:24:20.047 PM WindowServer[95]: Created shield window 0x79 for display 0x003f003f
11/14/13 2:24:20.047 PM WindowServer[95]: handle_will_sleep_auth_and_shield_windows: no lock state data
11/14/13 2:24:20.210 PM WindowServer[95]: Received display connect changed for display 0x4280380
11/14/13 2:24:20.276 PM WindowServer[95]: CGXMuxAcknowledge: Posting glitchless acknowledge
11/14/13 2:24:20.284 PM WindowServer[95]: MPAccessSurfaceForDisplayDevice: Set up page flip mode on display 0x04280380 device: 0x103403a10  isBackBuffered: 1 numComp: 3 numDisp: 3
11/14/13 2:24:20.332 PM WindowServer[95]: Received display connect changed for display 0x4280380
11/14/13 2:24:20.345 PM WindowServer[95]: Received display connect changed for display 0x3f003d
11/14/13 2:24:20.345 PM WindowServer[95]: Received display connect changed for display 0x3f003e
11/14/13 2:24:20.346 PM WindowServer[95]: Received display connect changed for display 0x3f003f
11/14/13 2:24:37.449 PM ScreenSaverEngine[288]: *** WARNING: -[NSImage compositeToPoint:operation:] is deprecated in MacOSX 10.8 and later. Please use -[NSImage drawAtPoint:fromRect:operation:fraction:] instead.
11/14/13 2:24:37.450 PM ScreenSaverEngine[288]: *** WARNING: -[NSImage compositeToPoint:fromRect:operation:] is deprecated in MacOSX 10.8 and later. Please use -[NSImage drawAtPoint:fromRect:operation:fraction:] instead.
11/14/13 2:25:53.960 PM coreservicesd[31]: Application App:"Finder" [ 0x0/0xc00c]  @ 0x0x7f96932099d0 tried to be brought forward, but isn't in fPermittedFrontASNs ( ( ASN:0x0-0x2c02c:) ), so denying.
11/14/13 2:25:53.961 PM WindowServer[95]: [cps/setfront] Failed setting the front application to Finder, psn 0x0-0xc00c, securitySessionID=0x186a5, err=-13066
11/14/13 2:25:54.560 PM coreservicesd[31]: Application App:"Finder" [ 0x0/0xc00c]  @ 0x0x7f96932099d0 tried to be brought forward, but isn't in fPermittedFrontASNs ( ( ASN:0x0-0x2c02c:) ), so denying.
11/14/13 2:25:54.560 PM WindowServer[95]: [cps/setfront] Failed setting the front application to Finder, psn 0x0-0xc00c, securitySessionID=0x186a5, err=-13066
11/14/13 2:25:54.937 PM coreservicesd[31]: Application App:"Finder" [ 0x0/0xc00c]  @ 0x0x7f96932099d0 tried to be brought forward, but isn't in fPermittedFrontASNs ( ( ASN:0x0-0x2c02c:) ), so denying.
11/14/13 2:25:54.938 PM WindowServer[95]: [cps/setfront] Failed setting the front application to Finder, psn 0x0-0xc00c, securitySessionID=0x186a5, err=-13066
11/14/13 2:25:55.317 PM coreservicesd[31]: Application App:"Finder" [ 0x0/0xc00c]  @ 0x0x7f96932099d0 tried to be brought forward, but isn't in fPermittedFrontASNs ( ( ASN:0x0-0x2c02c:) ), so denying.
11/14/13 2:25:55.317 PM WindowServer[95]: [cps/setfront] Failed setting the front application to Finder, psn 0x0-0xc00c, securitySessionID=0x186a5, err=-13066
11/14/13 2:26:09.254 PM WindowServer[95]: Received display connect changed for display 0x4280380
11/14/13 2:26:09.319 PM WindowServer[95]: Received display connect changed for display 0x3f003d
11/14/13 2:26:09.319 PM WindowServer[95]: Received display connect changed for display 0x3f003e
11/14/13 2:26:09.320 PM WindowServer[95]: Received display connect changed for display 0x3f003f
11/14/13 2:26:09.321 PM WindowServer[95]: CGXMuxAcknowledge: Posting glitchless acknowledge
11/14/13 2:26:09.341 PM WindowServer[95]: MPAccessSurfaceForDisplayDevice: Set up page flip mode on display 0x04280380 device: 0x103403a10  isBackBuffered: 1 numComp: 3 numDisp: 3
11/14/13 2:26:09.354 PM WindowServer[95]: Received display connect changed for display 0x4280380
11/14/13 2:26:21.515 PM WindowServer[95]: Created shield window 0x86 for display 0x04280380
11/14/13 2:26:21.539 PM WindowServer[95]: device_generate_desktop_screenshot: authw 0x0(0), shield 0x0(0)
11/14/13 2:26:21.558 PM WindowServer[95]: device_generate_lock_screen_screenshot: authw 0x0(0), shield 0x0(0)
11/14/13 2:26:26.294 PM WindowServer[95]: handle_will_sleep_auth_and_shield_windows: no lock state data
11/14/13 2:26:26.295 PM WindowServer[95]: Created shield window 0x87 for display 0x003f003d
11/14/13 2:26:26.295 PM WindowServer[95]: handle_will_sleep_auth_and_shield_windows: no lock state data
11/14/13 2:26:26.319 PM WindowServer[95]: Created shield window 0x88 for display 0x003f003e
11/14/13 2:26:26.319 PM WindowServer[95]: handle_will_sleep_auth_and_shield_windows: no lock state data
11/14/13 2:26:26.320 PM WindowServer[95]: Created shield window 0x89 for display 0x003f003f
11/14/13 2:26:26.320 PM WindowServer[95]: handle_will_sleep_auth_and_shield_windows: no lock state data

 

[philamonster]

Sorry for the bump...

Joined just to state that I am having the exact same issue though on a Late 2011 MBP. I was actually just finishing reading this a couple weeks ago: http://arstechnica.com/apple/2014/0...with-amd-gpus-experiencing-hardware-failures/ when I accidentally rebooted my MBP with keyboard shortcut instead of putting it to sleep and ended up with Apple logo and spinning beach ball just as login window was supposed to appear. I let it sit for a few minutes and nothing so I did a hard reset and same thing. I immediately blamed recent application installs of Cisco's VPN client and/or gfxCardStatus and removed both after I eventually got to login window with PRAM reset. Rebooted a dozen times to be sure and seemed good.

Then I started getting the same thing when resuming from sleep; black back-lit screen and spinning beach ball....hard reset. Seems to come back after PRAM reset but that wasn't always the case. Tonight was the first time I had the issue trying to clear screensaver and happened just as you described, which lead me to this thread though I am seeing something slightly different in logs and not as often as you. I too have removed the requirement for password after waking/screensaver and am brought back to desktop on resume from sleep.

I know this is months old but were you ever able to find a solution?

 

[Flash SWT]

Since I got no replies and couldn't find any suggestions elsewhere online I gave up and just formatted and reinstalled from scratch over the holiday break.

My MPB-R is work issued so I didn't have any personal data on it and everything on it was backed up multiple places. I made sure I had Time Machine and Carbon Copy Cloner copies up to date.

I just selectively restored data from the CCC backup and reinstalled all programs manually. I didn't want to risk migrating over whatever was causing the problem.

It has been running just fine since then leading me to believe it was a software issue and nothing wrong with the hardware. Good luck getting everything sorted out on your end and definitely let me know if you find an easier way to fix it.