You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

10.8.4 External Display Problem

Updated my rMBP to 10.8.4. The laptop rebooted, and the external display is not displaying correctly. How can I fix this?


The monitor has never had problems until immediatly after the update. The monitor attempts to display 1920x1080, but is offset. Part of it is off the screen, and is not horizantally long enough to fill the screen anyway. (Black bar on left side).


Bootcamp Trial

Booted into Windows 7 64bit

Monitor works fine, highest available resolution is 1280 x 1024.


Tried to set Mac resolution to 1280x 1024, works, but this is noticably less resolution than I had originally, before the update.


Specs

Retina Macbook Pro

LG external monitor: FLATRON W2343T

Thunderbolt to VGA adaptor


Thanks for any help you can provide.

OS X Mountain Lion (10.8.4)

Posted on Jun 4, 2013 8:05 PM

Reply
177 replies

Aug 15, 2013 11:51 AM in response to khroy

SOLVED!!!! External monitor missing after sleep or shutdown.


I have a Mid-2009 17" MacBook Pro and use it in a Henge-Dock with a Samsung 27" external HDMI monitor with a Mini-display to HDMI adapter and upon upgrading to 10.8.4 the only way I could get the connection to the external Samsung to work again was to restart and before login, when the restart was complete unplug the monitor for 5 seconds and plug it back in and all was well until sleep or shutdown. I have been repeating this procedure since the 10.8.4 upgrade.


The soluution was triggered by reading an earlier post when in the Display Preferences "Color" to uncheck "Show Profiles" then to hold down the "Option Key" so the "Detect Profiles" button appears. In doing this I rembered the "Apple Profile First Aid" Which is part of the "Color Sync Utility" tahat you can find under the "Go" menu in the Finder and pull down to "Utilities".


I started up "Profile First Aid" and first chose "verify" and it reported two profiles had "Bad Header" should of taken better notes. Then I clicked the "Repair" button and it indicated the bad files could not be repaired. I noted the name and the location of the problem files and found them here: "System/Library/CoreServices/Resources/Profiles"


Now having found the subject files I clicked once on them to select them and then right-click to "Get Info" and discovered these files were locked. I clicked the padalock in the lower left of the info window and then set all of the priviledges to "Read-Write" for every user which includes System.


At this point I closed all the windows open in the Finder and when back to "Profile First Aid" and selected repair and the problem files were repaired and "Profile First Aid" reported the details of the repair. Also when inspecting the now accessable profiles I was able to see the color map and lot's of information on my Samsung 27" HDMI monitor.


I have been testing the repairs now for more then an hour and all is well. When my MacBook Pro wakes up from sleep while it is in the HengeDock the good old 27" HDMI is there at full 1920 x 1080 resolution and the login screen just perfect. I can sleep it and unplug from the dock and open the MBP and the Apple razor sharp 17" display is perfect. I can close the lid on the MBP and put it back in the dock, wiggle the mouse and the 27" Samsung HDMI is perfect. I can sleed the MBP in the dock and it is waking up perfect to the login screen or the window of the last app I was in. My system is back to Apple Awesome.


Prior to this since 10.8.3 with big hopes in 10.8.4 to fix and up to now doing the start my MBP, wait for startup (not long thank God) unplug the HDMI cable at the monitor, wait 5-10 seconds and plug it back in.


A corrupted monitor profile is I bet at the root of these problems. In all my Mac Years since March of 1984 this is the second external monitor problem I have had and there have been hundreds of mac's and monitors and projectors.


I bet dollars to donuts this gets 95% of you back to WORK!!!!

Aug 16, 2013 11:45 AM in response to khroy

More than two months have gone by since this issue was originally reported. So far, we haven't seen any action taken by Apple. I thought this was the right communication channel to report and share issues with Apple products. Two months of TOTAL silence and indifference from Apple is really unprofessional. One of the most recent mottos from Apple is that "It just works"; well in this case the latest update to OSX, for MANY users doesn't work well. It is broken.

As users of Apple products we expect better service and communication from Apple.

Apple get your act together, read this chain of post messages and solve this bad issue that is impacting your customers productivity and product satisfaction.

Aug 21, 2013 8:55 AM in response to khroy

EXTERNAL DISPLAY PROBLEM: SOLUTION??? NO !!!!! WORKAROUND???? MAY BE !!!!


My last post propose a reset to solve the external display issue. This really work, but why?

Today, I just had another "external display issue" and attempted to see what happen without a reset. So this is what I did (The Experiment):


(1) Awake the laptop

(2) Login as usual without any external display connection. I have seen that login in sometimes helps in the external display problem.

(3) Connected the external display using the mini-port.

(4) PROBLEM ARISED. Laptop went blue then white and stuck there.

(5) Unplugged the miniport.

(6) After a while (20 seconds) the laptop went back to normal.

(7) Did the same again as (3), (4) came in, then I did (5) and (6) again

(8) I opened the "console" app, see the system log, I saw errors but hard to find out a clear answer.

(9) Start working reading mail as usual without the external display (I blaming apple as usual) for about 10 minutes.

(10) As a desesperated action, I tried again plugin the external miniport adapter again..... and GUESS, it worked.

(11) I compared the system log with the problem and without the problem, I observed differences in the log from applications not responding to the resolution change in messages like:


Aug 21 09:42:58 <computer> WindowServer[79]: CGXDisableUpdate: UI updates were forcibly disabled by application "Eclipse" for over 1.00 seconds. Server has re-enabled them.

Aug 21 09:42:58 <computer> WindowServer[79]: CGXDisableUpdate: UI updates were forcibly disabled by application "SystemUIServer" for over 1.00 seconds. Server has re-enabled them.

Aug 21 09:42:58 <computer> WindowServer[79]: CGXDisableUpdate: UI updates were forcibly disabled by application "Notification Center" for over 1.00 seconds. Server has re-enabled them.



THEN many more message below ....


Aug 21 09:43:12 <computer>.local WindowServer[79]: disable_update_likely_unbalanced: UI updates still disabled by application "Eclipse" after 15.00 seconds (server forcibly re-enabled them after 1.00 seconds). Likely an unbalanced disableUpdate call.

Aug 21 09:43:12 <computer>.local WindowServer[79]: disable_update_likely_unbalanced: UI updates still disabled by application "SystemUIServer" after 15.00 seconds (server forcibly re-enabled them after 1.00 seconds). Likely an unbalanced disableUpdate call.

Aug 21 09:43:12 <computer>.local WindowServer[79]: disable_update_likely_unbalanced: UI updates still disabled by application "Notification Center" after 15.00 seconds (server forcibly re-enabled them after 1.00 seconds). Likely an unbalanced disableUpdate call.

Aug 21 09:43:32 <computer> kernel[0]: stampWait: Overflowed checking for stamp 0x98282a9 on MAIN ring: called from sleepForTimeStamp

Aug 21 09:43:32 <computer> kernel[0]: timestamp = 0x98282a1

Aug 21 09:43:32 <computer> kernel[0]: GPU hang:

Aug 21 09:43:32 <computer> kernel[0]: Trying restart GPU ...

Aug 21 09:43:32 <computer> kernel[0]: MAIN ring is stuck waiting on an event

Aug 21 09:43:32 <computer> kernel[0]: After attempt to clear wait condition = 0x0000f001 no longer waiting

Aug 21 09:43:33 <computer> com.apple.launchd[1] (com.apple.DumpGPURestart): Throttling respawn: Will start in 9 seconds

Aug 21 09:43:37 <computer> com.apple.launchd[1] (com.apple.DumpGPURestart): Throttling respawn: Will start in 5 seconds

Aug 21 09:43:37 <computer> kernel[0]: stampWait: Overflowed checking for stamp 0x98282a9 on MAIN ring: called from sleepForTimeStamp

Aug 21 09:43:37 <computer> kernel[0]: timestamp = 0x98282a8

Aug 21 09:43:37 <computer> kernel[0]: GPU hang:

Aug 21 09:43:37 <computer> kernel[0]: Trying restart GPU ...

Aug 21 09:43:37 <computer> kernel[0]: MAIN ring is NOT waiting on an event



================================================

DISCUSSION

================================================

To me, the first and second failures were due to applications not responding to change then the OS seems to restart GPU and that caused a problem. When I used the computer for about 10 minutes, all applications, cache, and everything went back to run as usual, that is, they went "ready", then the third connection was successfull because the applications responded "quickly" to resolution change.


CONCLUSION: It seems that the OS needs to be "stable" after an awake in order to apps respond quickly to resolution change and avoid problems. This is in agreement with the "reset" procedure since a reset make everything clean and the OS has no load for previous sessions and windows. Therefore the workaround for this will be (1) Awake, (2) Login, (3) "Awake" applications by just clicking their icons to force refresh cache and that stuffs, (4) Wait for 1 minute or so, and (5) Connect the miniport....... for a better SOLUTION: APPLE MAKE BETTER SOFTWARE.

Aug 21, 2013 10:58 AM in response to victor.trevino

Hi @victor.trevino. Thanks for the info, but the problem you described seems to be a different one as what the OP described. The OP suggested a problem where the display area on the external monitor is horizontally offset/shifted, leaving a black strip on the left.


Regardless, I tried your method but to no avail -- the screen is still offset on the external monitor.

Aug 31, 2013 12:48 AM in response to khroy

Hi,


I found the solution and i post it


First solution is to use time machine to restore an old version 10.8.3 but you can fix this problem with a 10.8.4 OSX:



Read the tutorial i made to view how to repair this problem.


It's not an hardware problem but a bug after this update.


You need repair the permission to fix the problem.



My tutorial:


http://www.shareannonce.com/david/tutorial/275


🙂

10.8.4 External Display Problem

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.