Maverick freezes

I haven't yet determined what the cause is, but I'm experiencing the exact same issue described here. I have a late 2012 13 inch retina MBP, MacBookPro10,2 to be precise, and a fully updated Mavericks. I switch the machine between a triple-screen setup (including the built-in) and just using the built-in screen on a daily basis -- the timing of these errors and pauses somewhat makes me wonder if this may be of importance.

Try turning off "Displays have separate Spaces" in System Preferences -> Mission Control. Restart instead of logging out as it suggests, otherwise the setting may turn itself back on.

That got rid of the invalid display errors for me.

Thank you so much, sickmate. This worked. How on earth did you figure it out?

I was having an issue with a brand new late 2013 Macbook Air failing to resume from sleep with an external monitor attached. The monitor is a cheap Asus I grabbed off Amazon based on popularity, connected to the Macbook via thunderbolt -> HDMI. About 50% of the time it would wake to either no output on the HDMI, or a signal but a black screen. The built-in display was also stuck black, and the keyboard lights did not come on. In both scenarios the system was totally unresponsive and require a power button hold down to recover. No amount of plugging/unplugging and opening/closing the lid had any effect. I later turned on ssh and was able to avoid hard cycling the system by sudo reboot 'ing. I also tailed the log and found the UUID errors that led me to this post.

The system is pretty much stock, plus MS Office 2011 and Chrome. The setup is not mine and I'm uncomfortable leaving it in a state where some magic option prevents the whole thing from crashing constantly, but it's better than shipping it back to Apple (no store in the vicinity).

One other thing: though the crash no longer occurs (I've been neurotically cycling the thing on and off), the errors still show in the log. Not sure if important or not.

No problem, glad it helped you.

I often connect my MBP to my TV, and ever since I upgraded to Mavericks I noticed that it switched the TV display to a separate space when previously I had it mirrored. After disconnecting my laptop, it wasn't recognising that the display was disconnected either (if I opened up System Preferences -> Displays then the display preferences for the now disconnected external display would still open).

After a bit of digging I managed to find that setting in Mission Control. It looks like it's a setting that is new in Mavericks as well.

However I don't get any further display errors after disabling the setting - do you get any other errors along with it? In System Preferences, is there only a single display detected when your laptop isn't connected to an external display?

I am having the same issue with a MacMini connected to an HDTV. I tried to reboot from ssh and it was not effective. I will disable the "displays have seperate spaces" since it's only one "monitor" then it won't really change how I use the computer. However, is this something that would be resolved by using the gefen HDMI detective?

I have the same issue and it seems to be caused by a program called PyCharm.

Ever since upgrading to Mavericks it's been happening. It never happend before. I have an eternal 27" Dell monitor that causes this issue when plugged in to Thunderbolt. I'll try sickmate's suggestion and post my findings here.

Thank you sickmate, works for me too!

I struggled for a long time with this. Combination of factors that replicated the problem in my case was:

use of external monitor/power adapter plugged in/case lid closed

followed by:

no external monitor/battery power/case lid open.

MBP would work fine in scenario 1 but freeze in scenario 2. Would also work fine with no external monitor/power adpter plugged in/case lid open.

My obvious inclination was to blame power management: battery vs power adapter. Turns out that if displays are "mirrored" and Mission Control option for separate spaces is unchecked, the MBP works fine in all scenarios.

BTW Apple Genius Bar totally unable to solve this. Thanks to all assembled here!

Just a heads up: when upgrading Mavericks to 10.9.2, "Displays have separate Spaces" may become re-enabled.

Same issue here. Same sequence of events precedes freeze -- sometimes weeks pass before freeze, though. Same console messages as above, as well ("CGSCopyDisplayUUID: Invalid display").

This may well be the best post on the internet. Nothing is more infuriating than intermittent pauses for totally obscure reasons on a machine with max specs. Thank you!

This totally fixes the issue. And also @sickmate is correct in saying that "when upgrading Mavericks to 10.9.2, "Displays have separate Spaces" may become re-enabled". This happened to me and the MBP started crashing again when the external monitor is plugged in.

I'm experiencing frequent system freezes using a

MacBookPro11,3 with 2 external monitors + built-in retina display on Apple Thunderbolt-DVI & Apple HDMI->DVI adapters.

Same error in my system.log file: "CGSCopyDisplayUUID: Invalid display" right before everything hangs. (Although not everything, my mouse works until I try to force-quit something, and even after my mouse locks, my keyboard works fine until I Command+Opt+Esc & try to force-quit from there.)

I can usually sense the problem coming because whatever active application I have open becomes unresponsive, and this machine is lightning-fast, every other application works, and from then it goes haywire quickly. I can let it run its course, and after several minutes (5-10) it will recover on its own.

I'll try disabling separate spaces for separate monitors and see how it goes. Looks optimistic, based on the feedback here!

Just adding in my info so Apple knows that many people are experiencing this same issue. Not having displays with seperate spaces is quite annoying after using the feature (when it works).

What's interesting for me is that WindowServer finds 3 displays, even though I'm only using the internal and a single external monitor:

5/2/14 10:03:29.354 AM WindowServer[107]: Found 29 modes for display 0x04280600 [18, 11]

5/2/14 10:03:29.371 AM WindowServer[107]: Found 1 modes for display 0x003f003d [1, 0]

5/2/14 10:03:29.374 AM WindowServer[107]: Found 54 modes for display 0x003f003e [32, 16]

This occurs for me when plugging back into my external monitor after having my MBP disconnected from it.