2011 MBP - Red flickering in black display areas

Recently when I turn on my MBP or wake it from sleep, the black areas on the desktop, in Safari, everywhere, contain red flickering horizontal lines.
I called Apple Support and the best they could do was accuse me of dropping or damaging my computer. This thing is my baby, I take care of it almost too well. Needless to say I was offended but they had no other advice for me (except booting in Safe Boot which did nothing for the problem).
I noticed that if I decrease the angle of the display by moving it towards the keyboard as if I were going to close it, it causes the lines to disappear. This makes me think it is a connection/cable issue but I am wondering if anyone has had this experience and there is an easier fix besides going into an Apple Store...
Also, once the lines disappear they will not reappear until power-on or wake from sleep again...
Any advice out there?

I ran into this probelm, and and it was due to the display cable being slightly disconnected.
The way I fixed it:
Open up the computer to get access to the display cable
Disconnect the cable
Gave the connection a quick blast of air to clean it
Plugged it back in, and ensured it was well seated by applying liberal pressure to the connector
Close up the computer
Problem solved
Hope that helps someone.

Similar Messages

  • Hello, I have a Macbook Pro 17'' 2.4 GHz Intel Core i7 (2011). I dont know what happened but the pixels on black or dark areas on my monitor are displayed in a flickering red color, and on white areas are light blue. Any idea??

    Hello,
    I have a Macbook Pro 17'', 2.4 GHz Intel Core i7 (late 2011). I dont know what happened but the screen shows red flickering pixels everywhere where it should be black, and light blue pixels where it should be gray, I had this problem twice, the first time it just disappeared by itself. Now it's been like this for days, I have really no clue.
    Anyone with the same problem or solution?
    This is how it looks like:
    Thanx

    Is that a camera picture or a screen-shot? Is there any difference? i.e., can you capture the problems in a screen shot, or not?

  • 2011 MBP display went black

    My 15" MBP was bought last month.
    I started up my MBP this morning I heard the machine running sound and saw the power light turned on.
    However, the screen was totally black till loaded to the login page.
    I forced to shut down by pressing the power button.
    The screen didn't show anything for the 2nd and 3rd trial.
    Finally succeeded in 4th time...
    What's wrong with my MBP? is it the display problem?

    Perform a SMC reset
    https://support.apple.com/kb/HT3964
    Did you apply the recent EFI firmware update? See this and hopefully you can restore your firmware back to original conditions.
    https://support.apple.com/kb/HT2213
    With the latest EFI update Apple installed a Lion Internet Recovery,
    Lion boot DVD copies here (option click on Purcahes in MAS to download Lion installer again)
    http://eggfreckles.net/notes/burning-a-lion-boot-disc/

  • I7 MBP 8.2 AMD 6750M 2011 Crashes, Red Horizontal Lines, won't boots

    Crash, horizontal red lines, won't boot, SMC PRAM reset, failed boots, successful boot cycles:
    For about a week, I have been struggling with crashes, followed by red horizontal lines on the screen, and inability to boot into multi-user mode.  It will boot into single user mode, with red stripes on black background.  To get it to boot again I "shutdown -h now" from single user mode, SMC reset, PRAM reset 3 times, and attempt boots with <command> R two to three times unsuccessfully.  Then, if I am lucky, when I do a boot into single-user mode (power, <command> S), it boots into single user mode with a black background and no stripes, then I "exit" to boot.  If I am unlucky, the black screen will have red stripes or red snow in single-user mode.  After several crashes, I also have to remove my hard drive, and do a disk repair and permission repair, while connected to a different mac, or format and restore ML.  (I have two backups of my personal data.)  The failed multi-user boots are terminated by grey or black screens of death, accompanied by heat and the fands running fast.  The fans also run in single user mode without processor load if they red stripes are on the screen.  A successful multi-user boot is cool without fans running.  I didn't have any crashing problems before switching to ML recently.
    Memtest fails in multi-user mode (but not single-user mode):
    Running memtest on 8GB RAM in multi-user mode fails at a single address on the most significant byte (with 1 bit difference).  However, memtest does not show a failure in single-user mode, nor with only a single 4GB module in multi-user mode.
    Increased stability with gfxCardStatus and Flash unininstall:
    Using gfxCardStatus Integrated Only mode, and uninstalling Flash, seems to help.  However, I do get crashes or inability to wake up display which seems to be associated with processes like (google Chrome renderer) which forces gfxCardStatus out of "Integrated Only" mode.  http://gfx.io/switching.html
    Future plans:
    I am in Mexico where RAM is outrageously expensive.  So I will order RAM from the USA and try new 16 GB RAM because it is cheaper part swap than the logic board.  It makes sense to try the cheap stuff first.  I would rather switch to Linux and continue my bioinformatics work than pay and wait to replace the i7 logic board which warranty expired a few months ago.    I refuse to hit it with a heatgun to reflow the BGA solder on the GPU.  I really need the i7 data processing throughput I paid for. 
    Suggestions?
    Does anyone understand the ambiguous memtest results?

    I tested if my computer would hang, if I don't use the Mountain Lion GUI.  I didn't log in on the GUI.  I used ssh from my Mac Mini, to launch scripts while heavily load the i7 CPU while not logged on to the GUI.  I woke up the screen a few time successfully.  However Dec 30, early in the morning, the screen remained black and the login screen would not appear pressing a key.  My ssh sessions were still working and I could continue to run scripts and load all the CPU cores verified by "top" on the command line.  However, I could not ssh to my MacBook Pro! 
         ssh [email protected]
         ssh: Could not resolve hostname hanalei.local: nodename nor servname provided, or not known
    (Previously established SSH sessions continued to work, but new ones could not be started.)
    I ran memtest afteward 4 times without failure while I went to sleep. 
    Looking at the console log, something killed authentication, which I assume disabled the ability to ssh into my MacBook Pro.
         Dec 30 02:26:00 hanalei com.apple.launchd[1] (com.apple.coreservices.appleid.authentication[318]) <Notice>: Exited: Killed: 9
    There were also lots of GPU restarts. 
         Dec 29 22:23:41 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 9 seconds
    syslog -C | grep Killed
    Dec 29 13:48:54 hanalei com.apple.launchd.peruser.503[137] (com.apple.mdworker.shared.04000000-0000-0000-0000-000000000000[295]) <Notice>: Exited: Killed: 9
    Dec 29 15:27:59 hanalei com.apple.launchd.peruser.503[150] (com.apple.talagent[170]) <Notice>: Exited: Killed: 9
    Dec 29 16:58:42 hanalei com.apple.launchd[1] (com.apple.metadata.mds.scan[294]) <Notice>: Exited: Killed: 9
    Dec 30 02:26:00 hanalei com.apple.launchd[1] (com.apple.coreservices.appleid.authentication[318]) <Notice>: Exited: Killed: 9
    Dec 30 02:26:01 hanalei com.apple.launchd[1] (com.apple.audio.SandboxHelper[210]) <Notice>: Exited: Killed: 9
    Dec 30 02:26:01 hanalei com.apple.launchd[1] (com.apple.xpcd.CA000000-0000-0000-0000-000000000000[209]) <Notice>: Exited: Killed: 9
    Dec 30 02:26:02 hanalei com.apple.launchd[1] (com.apple.xpcd.F7010000-0000-0000-0000-000000000000[186]) <Notice>: Exited: Killed: 9
    Dec 30 02:26:02 hanalei com.apple.launchd.peruser.503[140] (com.apple.tccd[153]) <Notice>: Exited: Killed: 9
    Dec 30 02:26:43 hanalei com.apple.launchd.peruser.503[140] (com.apple.cfprefsd.xpc.agent[148]) <Notice>: Exited: Killed: 9
    Dec 30 02:26:44 hanalei com.apple.launchd[1] (com.apple.sleepservicesd[31]) <Notice>: Exited: Killed: 9
    Dec 30 02:29:35 hanalei com.apple.launchd[1] (com.apple.sleepservicesd[14574]) <Notice>: Exited: Killed: 9
    Dec 30 02:29:48 hanalei com.apple.launchd.peruser.503[140] (com.apple.cfprefsd.xpc.agent[14579]) <Notice>: Exited: Killed: 9
    Dec 30 02:29:49 hanalei com.apple.launchd.peruser.503[140] (com.apple.distnoted.xpc.agent[144]) <Notice>: Exited: Killed: 9
    Dec 30 02:29:50 hanalei com.apple.launchd[1] (com.apple.sleepservicesd[14591]) <Notice>: Exited: Killed: 9
    Dec 30 02:29:51 hanalei com.apple.launchd[1] (com.apple.cfprefsd.xpc.daemon[21]) <Notice>: Exited: Killed: 9
    Dec 30 02:30:01 hanalei com.apple.launchd[1] (com.apple.sleepservicesd[14595]) <Notice>: Exited: Killed: 9
    Dec 30 02:30:14 hanalei com.apple.launchd[1] (com.apple.sleepservicesd[14601]) <Notice>: Exited: Killed: 9
    Dec 30 02:30:14 hanalei com.apple.launchd[1] (com.apple.cfprefsd.xpc.daemon[14598]) <Notice>: Exited: Killed: 9
    Dec 30 02:30:38 hanalei com.apple.launchd[1] (com.apple.sleepservicesd[14602]) <Notice>: Exited: Killed: 9
    Dec 30 02:31:27 hanalei com.apple.launchd[1] (com.apple.cfprefsd.xpc.daemon[14611]) <Notice>: Exited: Killed: 9
    Dec 30 03:15:05 hanalei com.apple.launchd.peruser.503[14604] (com.apple.cfprefsd.xpc.agent[14610]) <Notice>: Exited: Killed: 9
    Dec 30 03:26:42 hanalei com.apple.launchd[1] (com.apple.cfprefsd.xpc.daemon[14615]) <Notice>: Exited: Killed: 9
    Dec 30 03:26:43 hanalei com.apple.launchd.peruser.503[14604] (com.apple.distnoted.xpc.agent[14608]) <Notice>: Exited: Killed: 9
    Dec 30 03:26:43 hanalei com.apple.launchd[1] (com.apple.sleepservicesd[14606]) <Notice>: Exited: Killed: 9
    Dec 30 03:46:06 hanalei com.apple.launchd[1] (com.apple.sleepservicesd[14684]) <Notice>: Exited: Killed: 9
    Dec 30 04:26:44 hanalei com.apple.launchd[1] (com.apple.sleepservicesd[14690]) <Notice>: Exited: Killed: 9
    Dec 30 04:26:45 hanalei com.apple.launchd[1] (com.apple.cfprefsd.xpc.daemon[14685]) <Notice>: Exited: Killed: 9
    Dec 30 04:42:03 hanalei com.apple.launchd[1] (com.apple.cfprefsd.xpc.daemon[14699]) <Notice>: Exited: Killed: 9
    Dec 30 04:55:58 hanalei com.apple.launchd[1] (com.apple.sleepservicesd[14698]) <Notice>: Exited: Killed: 9
    syslog -C
    Dec 29 11:05:40 localhost com.apple.launchd[1] <Notice>: *** launchd[1] has started up. ***
    Dec 29 11:05:40 localhost com.apple.launchd[1] <Notice>: *** Shutdown logging is enabled. ***
    Dec 29 11:06:29 localhost com.apple.launchd[1] (com.apple.automountd) <Warning>: Unknown key for boolean: NSSupportsSuddenTermination
    Dec 29 11:06:34 hanalei com.apple.launchd[1] (com.apple.bsd.dirhelper) <Notice>: Throttling respawn: Will start in 10 seconds
    Dec 29 11:07:43 hanalei com.apple.launchd.peruser.503[209] (com.apple.gamed) <Warning>: Ignored this key: UserName
    Dec 29 11:07:43 hanalei com.apple.launchd.peruser.503[209] (com.apple.gamed) <Warning>: Ignored this key: GroupName
    Dec 29 11:07:43 hanalei.local distnoted[213] <Warning>: # distnote server agent  absolute time: 124.947278009   civil time: Sat Dec 29 11:07:43 2012   pid: 213 uid: 503  root: no
    Dec 29 11:08:43 hanalei com.apple.launchd.peruser.503[209] (com.apple.afpstat-qfa[299]) <Notice>: Job failed to exec(3). Setting up event to tell us when to try again: 2: No such file or directory
    Dec 29 11:08:43 hanalei com.apple.launchd.peruser.503[209] (com.apple.afpstat-qfa[299]) <Notice>: Job failed to exec(3) for weird reason: 2
    Dec 29 11:08:43 hanalei com.apple.launchd.peruser.503[209] (com.apple.mrt.uiagent[293]) <Error>: Exited with code: 255
    Dec 29 11:09:03 hanalei com.apple.launchd.peruser.503[209] <Error>: Bug: 12C60: launchd + 112364 [7DCC9489-2DF5-3807-83FA-EF5666EE8078]: 0x1
    --- last message repeated 5 times ---
    Dec 29 13:17:09 localhost com.apple.launchd[1] <Notice>: *** launchd[1] has started up. ***
    Dec 29 13:17:09 localhost com.apple.launchd[1] <Notice>: *** Shutdown logging is enabled. ***
    Dec 29 13:17:38 localhost com.apple.launchd[1] (com.apple.automountd) <Warning>: Unknown key for boolean: NSSupportsSuddenTermination
    Dec 29 13:18:40 hanalei com.apple.launchd.peruser.503[137] (com.apple.gamed) <Warning>: Ignored this key: UserName
    Dec 29 13:18:40 hanalei com.apple.launchd.peruser.503[137] (com.apple.gamed) <Warning>: Ignored this key: GroupName
    Dec 29 13:18:40 hanalei.local distnoted[141] <Warning>: # distnote server agent  absolute time: 95.663712636   civil time: Sat Dec 29 13:18:40 2012   pid: 141 uid: 503  root: no
    Dec 29 13:18:50 hanalei com.apple.launchd.peruser.503[137] <Error>: Bug: 12C60: launchd + 112364 [7DCC9489-2DF5-3807-83FA-EF5666EE8078]: 0x1
    --- last message repeated 5 times ---
    Dec 29 13:18:53 hanalei com.apple.launchd.peruser.503[137] (com.apple.afpstat-qfa[267]) <Notice>: Job failed to exec(3). Setting up event to tell us when to try again: 2: No such file or directory
    Dec 29 13:18:53 hanalei com.apple.launchd.peruser.503[137] (com.apple.afpstat-qfa[267]) <Notice>: Job failed to exec(3) for weird reason: 2
    Dec 29 13:18:53 hanalei com.apple.launchd.peruser.503[137] (com.apple.mrt.uiagent[261]) <Error>: Exited with code: 255
    Dec 29 13:39:25 hanalei com.apple.launchd.peruser.503[137] (com.apple.NetworkDiagnostics[388]) <Warning>: Check-in of Mach service failed. Already active: com.apple.NetworkDiagnostic.agent
    Dec 29 13:42:21 hanalei.local spindump[403] <Notice>: Saved hang report for Mail version 6.2 (1499) to /Library/Logs/DiagnosticReports/Mail_2012-12-29-134221_hanalei.hang
    Dec 29 13:48:54 hanalei com.apple.launchd.peruser.503[137] ([0x0-0x16016].com.apple.AppleSpell[277]) <Notice>: Exited: Terminated: 15
    Dec 29 13:48:54 hanalei com.apple.launchd.peruser.503[137] (com.apple.mdworker.shared.04000000-0000-0000-0000-000000000000[295]) <Notice>: Exited: Killed: 9
    Dec 29 14:29:38 localhost com.apple.launchd[1] <Notice>: *** launchd[1] has started up. ***
    Dec 29 14:29:38 localhost com.apple.launchd[1] <Notice>: *** Shutdown logging is enabled. ***
    Dec 29 14:29:49 localhost com.apple.launchd[1] (com.apple.automountd) <Warning>: Unknown key for boolean: NSSupportsSuddenTermination
    Dec 29 14:32:05 hanalei.local distnoted[118] <Warning>: # distnote server agent  absolute time: 155.593274130   civil time: Sat Dec 29 14:32:05 2012   pid: 118 uid: 503  root: no
    Dec 29 15:21:29 localhost com.apple.launchd[1] <Notice>: *** launchd[1] has started up. ***
    Dec 29 15:21:29 localhost com.apple.launchd[1] <Notice>: *** Shutdown logging is enabled. ***
    Dec 29 15:21:40 localhost com.apple.launchd[1] (com.apple.automountd) <Warning>: Unknown key for boolean: NSSupportsSuddenTermination
    Dec 29 15:22:23 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 9 seconds
    Dec 29 15:22:28 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 4 seconds
    Dec 29 15:22:33 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 9 seconds
    Dec 29 15:22:34 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 8 seconds
    Dec 29 15:22:40 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 2 seconds
    Dec 29 15:22:43 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 9 seconds
    Dec 29 15:22:46 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 6 seconds
    Dec 29 15:22:53 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 9 seconds
    Dec 29 15:22:58 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 4 seconds
    --- last message repeated 6 times ---
    Dec 29 15:23:04 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 9 seconds
    Dec 29 15:23:20 hanalei com.apple.launchd.peruser.503[150] (com.apple.gamed) <Warning>: Ignored this key: UserName
    Dec 29 15:23:20 hanalei com.apple.launchd.peruser.503[150] (com.apple.gamed) <Warning>: Ignored this key: GroupName
    Dec 29 15:23:20 hanalei.local distnoted[154] <Warning>: # distnote server agent  absolute time: 114.027753124   civil time: Sat Dec 29 15:23:20 2012   pid: 154 uid: 503  root: no
    Dec 29 15:23:28 hanalei com.apple.launchd.peruser.503[150] <Error>: Bug: 12C60: launchd + 112364 [7DCC9489-2DF5-3807-83FA-EF5666EE8078]: 0x1
    --- last message repeated 5 times ---
    Dec 29 15:23:33 hanalei com.apple.launchd.peruser.503[150] (com.apple.afpstat-qfa[285]) <Notice>: Job failed to exec(3). Setting up event to tell us when to try again: 2: No such file or directory
    Dec 29 15:23:33 hanalei com.apple.launchd.peruser.503[150] (com.apple.afpstat-qfa[285]) <Notice>: Job failed to exec(3) for weird reason: 2
    Dec 29 15:23:33 hanalei com.apple.launchd.peruser.503[150] (com.apple.mrt.uiagent[278]) <Error>: Exited with code: 255
    Dec 29 15:23:46 hanalei com.apple.launchd.peruser.503[150] (com.apple.NetworkDiagnostics[297]) <Warning>: Check-in of Mach service failed. Already active: com.apple.NetworkDiagnostic.agent
    Dec 29 15:25:53 hanalei com.apple.launchd.peruser.503[150] (com.apple.NetworkDiagnostics[335]) <Warning>: Check-in of Mach service failed. Already active: com.apple.NetworkDiagnostic.agent
    Dec 29 15:27:59 hanalei com.apple.launchd.peruser.503[150] (com.apple.talagent[170]) <Notice>: Exited: Killed: 9
    Dec 29 15:35:00 hanalei com.apple.launchd.peruser.503[150] (com.apple.gamed) <Warning>: Ignored this key: UserName
    Dec 29 15:35:00 hanalei com.apple.launchd.peruser.503[150] (com.apple.gamed) <Warning>: Ignored this key: GroupName
    Dec 29 15:35:27 hanalei com.apple.launchd.peruser.503[150] <Error>: Bug: 12C60: launchd + 112364 [7DCC9489-2DF5-3807-83FA-EF5666EE8078]: 0x1
    --- last message repeated 2 times ---
    Dec 29 15:35:27 hanalei com.apple.launchd.peruser.503[150] (com.apple.afpstat-qfa[482]) <Notice>: Job failed to exec(3). Setting up event to tell us when to try again: 2: No such file or directory
    Dec 29 15:35:27 hanalei com.apple.launchd.peruser.503[150] (com.apple.afpstat-qfa[482]) <Notice>: Job failed to exec(3) for weird reason: 2
    Dec 29 15:35:28 hanalei com.apple.launchd.peruser.503[150] <Error>: Bug: 12C60: launchd + 112364 [7DCC9489-2DF5-3807-83FA-EF5666EE8078]: 0x1
    --- last message repeated 3 times ---
    Dec 29 15:35:28 hanalei com.apple.launchd.peruser.503[150] (com.apple.mrt.uiagent[475]) <Error>: Exited with code: 255
    Dec 29 15:35:46 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 4 seconds
    Dec 29 15:35:51 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 9 seconds
    Dec 29 15:35:52 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 8 seconds
    Dec 29 15:35:58 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 2 seconds
    --- last message repeated 1 time ---
    Dec 29 15:45:55 localhost com.apple.launchd[1] <Notice>: *** launchd[1] has started up. ***
    Dec 29 15:45:55 localhost com.apple.launchd[1] <Notice>: *** Shutdown logging is enabled. ***
    Dec 29 15:46:06 localhost com.apple.launchd[1] (com.apple.automountd) <Warning>: Unknown key for boolean: NSSupportsSuddenTermination
    Dec 29 15:48:21 hanalei.local distnoted[147] <Warning>: # distnote server agent  absolute time: 149.513792853   civil time: Sat Dec 29 15:48:21 2012   pid: 147 uid: 503  root: no
    Dec 29 16:42:52 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 9 seconds
    Dec 29 16:42:57 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 4 seconds
    Dec 29 16:43:02 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 9 seconds
    Dec 29 16:43:03 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 8 seconds
    --- last message repeated 1 time ---
    Dec 29 16:43:09 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 2 seconds
    Dec 29 16:43:12 hanalei com.apple.launchd.peruser.503[144] (com.apple.gamed) <Warning>: Ignored this key: UserName
    Dec 29 16:43:12 hanalei com.apple.launchd.peruser.503[144] (com.apple.gamed) <Warning>: Ignored this key: GroupName
    Dec 29 16:43:24 hanalei com.apple.launchd.peruser.503[144] <Error>: Bug: 12C60: launchd + 112364 [7DCC9489-2DF5-3807-83FA-EF5666EE8078]: 0x1
    --- last message repeated 5 times ---
    Dec 29 16:44:12 hanalei com.apple.launchd.peruser.503[144] (com.apple.afpstat-qfa[311]) <Notice>: Job failed to exec(3). Setting up event to tell us when to try again: 2: No such file or directory
    Dec 29 16:44:12 hanalei com.apple.launchd.peruser.503[144] (com.apple.afpstat-qfa[311]) <Notice>: Job failed to exec(3) for weird reason: 2
    Dec 29 16:44:12 hanalei com.apple.launchd.peruser.503[144] (com.apple.mrt.uiagent[304]) <Error>: Exited with code: 255
    Dec 29 16:44:29 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 4 seconds
    Dec 29 16:44:34 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 9 seconds
    Dec 29 16:44:35 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 8 seconds
    Dec 29 16:44:41 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 2 seconds
    --- last message repeated 1 time ---
    Dec 29 16:55:35 localhost com.apple.launchd[1] <Notice>: *** launchd[1] has started up. ***
    Dec 29 16:55:35 localhost com.apple.launchd[1] <Notice>: *** Shutdown logging is enabled. ***
    Dec 29 16:55:45 localhost com.apple.launchd[1] (com.apple.automountd) <Warning>: Unknown key for boolean: NSSupportsSuddenTermination
    Dec 29 16:56:21 hanalei com.apple.launchd.peruser.503[140] (com.apple.gamed) <Warning>: Ignored this key: UserName
    Dec 29 16:56:21 hanalei com.apple.launchd.peruser.503[140] (com.apple.gamed) <Warning>: Ignored this key: GroupName
    Dec 29 16:56:21 hanalei.local distnoted[144] <Warning>: # distnote server agent  absolute time: 47.520354484   civil time: Sat Dec 29 16:56:21 2012   pid: 144 uid: 503  root: no
    Dec 29 16:57:09 hanalei com.apple.launchd.peruser.503[140] <Error>: Bug: 12C60: launchd + 112364 [7DCC9489-2DF5-3807-83FA-EF5666EE8078]: 0x1
    --- last message repeated 4 times ---
    Dec 29 16:57:14 hanalei com.apple.launchd.peruser.503[140] (com.apple.afpstat-qfa[272]) <Notice>: Job failed to exec(3). Setting up event to tell us when to try again: 2: No such file or directory
    Dec 29 16:57:14 hanalei com.apple.launchd.peruser.503[140] (com.apple.afpstat-qfa[272]) <Notice>: Job failed to exec(3) for weird reason: 2
    Dec 29 16:57:15 hanalei com.apple.launchd.peruser.503[140] <Error>: Bug: 12C60: launchd + 112364 [7DCC9489-2DF5-3807-83FA-EF5666EE8078]: 0x1
    Dec 29 16:57:15 hanalei com.apple.launchd.peruser.503[140] (com.apple.mrt.uiagent[265]) <Error>: Exited with code: 255
    Dec 29 16:58:42 hanalei com.apple.launchd.peruser.503[140] ([0x0-0x19019].com.apple.AppleSpell[289]) <Notice>: Exited: Terminated: 15
    Dec 29 16:58:42 hanalei com.apple.launchd[1] (com.apple.metadata.mds.scan[294]) <Notice>: Exited: Killed: 9
    Dec 29 16:59:35 hanalei com.apple.launchd.peruser.503[140] <Error>: Bug: 12C60: launchd + 112364 [7DCC9489-2DF5-3807-83FA-EF5666EE8078]: 0x1
    --- last message repeated 2 times ---
    Dec 29 19:13:33 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 9 seconds
    Dec 29 19:13:38 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 4 seconds
    Dec 29 19:13:43 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 9 seconds
    Dec 29 19:13:44 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 8 seconds
    --- last message repeated 1 time ---
    Dec 29 19:13:50 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 2 seconds
    Dec 29 20:14:05 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 9 seconds
    Dec 29 20:14:10 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 4 seconds
    Dec 29 20:14:15 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 9 seconds
    Dec 29 20:14:16 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 8 seconds
    --- last message repeated 2 times ---
    Dec 29 20:14:22 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 2 seconds
    Dec 29 21:16:12 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 9 seconds
    Dec 29 21:16:17 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 4 seconds
    Dec 29 21:16:22 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 9 seconds
    Dec 29 21:16:23 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 8 seconds
    --- last message repeated 1 time ---
    Dec 29 21:16:29 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 2 seconds
    Dec 29 22:23:41 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 9 seconds
    Dec 29 22:23:46 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 4 seconds
    Dec 29 22:23:51 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 9 seconds
    Dec 29 22:23:52 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 8 seconds
    --- last message repeated 2 times ---
    Dec 29 22:23:58 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 2 seconds
    Dec 29 22:24:56 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 9 seconds
    Dec 29 22:25:01 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 4 seconds
    Dec 29 22:25:06 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 9 seconds
    Dec 29 22:25:07 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 8 seconds
    --- last message repeated 1 time ---
    Dec 29 22:25:13 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 2 seconds
    Dec 29 22:26:11 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 9 seconds
    Dec 29 22:26:16 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 4 seconds
    Dec 29 22:26:21 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 9 seconds
    Dec 29 22:26:22 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 8 seconds
    --- last message repeated 2 times ---
    Dec 29 22:26:28 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 2 seconds
    Dec 29 22:27:26 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 9 seconds
    Dec 29 22:27:31 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 4 seconds
    Dec 29 22:27:36 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 9 seconds
    Dec 29 22:27:37 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 8 seconds
    --- last message repeated 1 time ---
    Dec 29 22:27:43 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 2 seconds
    Dec 29 22:28:42 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 9 seconds
    Dec 29 22:28:46 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 4 seconds
    Dec 29 22:28:52 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 9 seconds
    Dec 29 22:28:52 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 8 seconds
    --- last message repeated 1 time ---
    Dec 29 22:28:59 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 2 seconds
    Dec 29 22:29:57 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 9 seconds
    Dec 29 22:30:01 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 4 seconds
    Dec 29 22:30:07 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 9 seconds
    Dec 29 22:30:07 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 8 seconds
    --- last message repeated 1 time ---
    Dec 29 22:30:13 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 2 seconds
    Dec 29 22:31:12 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 9 seconds
    Dec 29 22:31:16 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 4 seconds
    Dec 29 22:31:22 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 9 seconds
    Dec 29 22:31:22 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 8 seconds
    --- last message repeated 1 time ---
    Dec 29 22:31:29 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 2 seconds
    Dec 29 22:32:27 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 9 seconds
    Dec 29 22:32:32 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 4 seconds
    Dec 29 22:32:37 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 9 seconds
    Dec 29 22:32:38 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 8 seconds
    --- last message repeated 1 time ---
    Dec 29 22:32:44 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 2 seconds
    Dec 29 22:33:42 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 9 seconds
    Dec 29 22:33:47 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 4 seconds
    Dec 29 22:33:52 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 9 seconds
    Dec 29 22:33:53 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 8 seconds
    --- last message repeated 1 time ---
    Dec 29 22:33:59 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 2 seconds
    Dec 29 23:17:28 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 9 seconds
    Dec 29 23:17:33 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 4 seconds
    Dec 29 23:17:38 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 9 seconds
    Dec 29 23:17:39 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 8 seconds
    --- last message repeated 1 time ---
    Dec 29 23:17:45 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 2 seconds
    Dec 30 02:24:01 hanalei com.apple.launchd.peruser.503[140] <Error>: Bug: 12C60: launchd + 112364 [7DCC9489-2DF5-3807-83FA-EF5666EE8078]: 0x1
    Dec 30 02:26:00 hanalei com.apple.launchd[1] (com.apple.coreservices.appleid.authentication[318]) <Notice>: Exited: Killed: 9
    Dec 30 02:26:01 hanalei com.apple.launchd[1] (com.apple.audio.SandboxHelper[210]) <Notice>: Exited: Killed: 9
    Dec 30 02:26:01 hanalei com.apple.launchd[1] (com.apple.xpcd.CA000000-0000-0000-0000-000000000000[209]) <Notice>: Exited: Killed: 9
    Dec 30 02:26:02 hanalei com.apple.launchd[1] (com.apple.xpcd.F7010000-0000-0000-0000-000000000000[186]) <Notice>: Exited: Killed: 9
    Dec 30 02:26:02 hanalei com.apple.launchd.peruser.503[140] (com.apple.tccd[153]) <Notice>: Exited: Killed: 9
    Dec 30 02:26:43 hanalei com.apple.launchd.peruser.503[140] (com.apple.cfprefsd.xpc.agent[148]) <Notice>: Exited: Killed: 9
    Dec 30 02:26:44 hanalei com.apple.launchd[1] (com.apple.sleepservicesd[31]) <Notice>: Exited: Killed: 9
    Dec 30 02:29:35 hanalei com.apple.launchd[1] (com.apple.sleepservicesd[14574]) <Notice>: Exited: Killed: 9
    Dec 30 02:29:48 hanalei com.apple.launchd.peruser.503[140] (com.apple.cfprefsd.xpc.agent[14579]) <Notice>: Exited: Killed: 9
    Dec 30 02:29:49 hanalei com.apple.launchd.peruser.503[140] (com.apple.distnoted.xpc.agent[144]) <Notice>: Exited: Killed: 9
    Dec 30 02:29:50 hanalei com.apple.launchd[1] (com.apple.sleepservicesd[14591]) <Notice>: Exited: Killed: 9
    Dec 30 02:29:51 hanalei com.apple.launchd[1] (com.apple.cfprefsd.xpc.daemon[21]) <Notice>: Exited: Killed: 9
    Dec 30 02:30:01 hanalei com.apple.launchd[1] (com.apple.sleepservicesd[14595]) <Notice>: Exited: Killed: 9
    Dec 30 02:30:14 hanalei com.apple.launchd[1] (com.apple.sleepservicesd[14601]) <Notice>: Exited: Killed: 9
    Dec 30 02:30:14 hanalei com.apple.launchd[1] (com.apple.cfprefsd.xpc.daemon[14598]) <Notice>: Exited: Killed: 9
    Dec 30 02:30:38 hanalei com.apple.launchd[1] (com.apple.sleepservicesd[14602]) <Notice>: Exited: Killed: 9
    Dec 30 02:30:39 hanalei.local distnoted[14608] <Warning>: # distnote server agent  absolute time: 18252.455382446   civil time: Sun Dec 30 02:30:39 2012   pid: 14608 uid: 503  root: no
    Dec 30 02:31:27 hanalei com.apple.launchd[1] (com.apple.cfprefsd.xpc.daemon[14611]) <Notice>: Exited: Killed: 9
    Dec 30 03:15:05 hanalei com.apple.launchd.peruser.503[14604] (com.apple.cfprefsd.xpc.agent[14610]) <Notice>: Exited: Killed: 9
    Dec 30 03:26:42 hanalei com.apple.launchd[1] (com.apple.cfprefsd.xpc.daemon[14615]) <Notice>: Exited: Killed: 9
    Dec 30 03:26:43 hanalei com.apple.launchd.peruser.503[14604] (com.apple.distnoted.xpc.agent[14608]) <Notice>: Exited: Killed: 9
    Dec 30 03:26:43 hanalei com.apple.launchd[1] (com.apple.sleepservicesd[14606]) <Notice>: Exited: Killed: 9
    Dec 30 03:46:06 hanalei com.apple.launchd[1] (com.apple.sleepservicesd[14684]) <Notice>: Exited: Killed: 9
    Dec 30 04:26:44 hanalei com.apple.launchd[1] (com.apple.sleepservicesd[14690]) <Notice>: Exited: Killed: 9
    Dec 30 04:26:45 hanalei com.apple.launchd[1] (com.apple.cfprefsd.xpc.daemon[14685]) <Notice>: Exited: Killed: 9
    Dec 30 04:42:03 hanalei com.apple.launchd[1] (com.apple.cfprefsd.xpc.daemon[14699]) <Notice>: Exited: Killed: 9
    Dec 30 04:55:58 hanalei com.apple.launchd[1] (com.apple.sleepservicesd[14698]) <Notice>: Exited: Killed: 9
    Dec 30 10:00:37 hanalei.local distnoted[14778] <Warning>: # distnote server agent  absolute time: 45252.245296175   civil time: Sun Dec 30 10:00:37 2012   pid: 14778 uid: 503  root: no

  • Can I place a 13" retina display panel into my 2011 MBP?

    I was wondering (moreso wishing and hoping) if it's possible to have my 2011 MBP display panel replaced with the recent 13" retina display panel. My 2011 MBP is just out of warranty and its display panel has developed a green line issue that seems too common among MBP displays.
    Thanks!

    The best option would be to take this to Apple and pay for it to be fixed. The display will be expensive to fix, so if you feel you can, purchasing a replacement from eBay or somewhere online would be possible. You can not fit a Retina display on as the hings and connectors are different, and even if they were not, the firmware and drivers your Mac will have (and continue to have as the model number tells the system you should have a standard display) can not drive the higher resolution efficiently. This would lead to performance and battery issues.
    Consider buying a desktop stand and display for your Mac as well and use the built in display only when necessary. Small problems with LCDs usually develop into worse situations quickly.
    Good luck!

  • 2011 MBP + Thunderbolt + DVI 30" Display

    Hi,
    Trying to attach one or two monitors to my 2011 MBP but have run up against a wall.
    1) My one Thunderbolt port is attached to a Sonnet Thunderbolt-to-CardBus adapter. The adapter only has one Thunderbolt port, so no possiblilty of daisy-chaining.
    2) I want to hook up a 30" NEC 2560 x 1600 DVI display (and if possible a 23" ACD as well)
    3) There do not seem to be any Thunderbolt Hubs or Splitters available yet. Am I missing something?
    4) The only solution I can see is to use a USB-to-DVI box. Took a look at the StarTech model which supports the high resolution. Is this my only option? What are others doing in this situation?
    Can't wait till Thunderbolt is more widely adopted and the cable/hubs/enclosures/etc finally become more widely available.
    (FYI- The Sonnet Thunderbolt-to-Cardbus adapter is great. I've got a 10-bay eSATA raid hooked up via this and it is WAY faster than FW800)
    Thank you...

    Yes by running a USB cable from the Mac to the HUB input port on the display.
    The product disscription states the cable has connectors on it to connect to USB.
    Connectors and cables
    Apple Display Connector carries digital video, USB, and power
    Two-port, self-powered USB hub

  • My early 2011 MacBook Pro 15" non-glare display has developed a dark band at the edges of the screen approximately the same width as the aluminum surround. This wasn't present when the MBP was new. Am near an Apple Store, but anyone else had this problem

    My early 2011 MacBook Pro 15" non-glare display has developed a dark band at the edges of the screen approximately the same width as the aluminum surround. This wasn't present when the MBP was new. I'm near an Apple Store and can take the laptop in, but has anyone else had this problem?

    Thanks for your input. I didn't completely flesh out what I'm seeing visually. The resolution settings are all correct for my screen. The problem is if, say, looking at the gray startup screens or a completely white full-screen image, there is a perimeter of graying, almost as if the LEDs are somehow not as bright as the rest. It's also curious that the thickness of this phenomenon is almost exactly the same as the metal bezel around the display. I will be taking it to an Apple Store for a look, as I'm also having several minor hardware problems that need to be addressed and remedied.

  • Mac Pro 2008 Apple Cinema Displays are black and there are start up issues

    I have a Mac Pro 2008 Dual quad 2.8 GHz. I have two Apple Cinema Displays (graphics are the standard ATI Radeon HD 2600 – 2 dual link DVI. I have 4 2-GB RAM sticks (8 GB total).
    Neither of my displays are showing anything. Their power lights are on but they are completely black throughout the start up process. In addition when I try to boot up with both graphics cards installed, I get nothing – no beeps no chimes. If just one card is installed (either card in either slot) the computer beeps, chimes and makes the sounds of booting up, but not a flicker on the displays. RAM does not seem to be the issue as I have tried booting with several configurations of RAM sticks with no negative or positive effects. I tried booting up with Hard Drives 1 & 2 removed with no effect.  I have tried several different start up moods and have reset PRAM.
    My guess is that there is something wrong with the motherboard. Or is it possible that both graphics cards are bad?

    The "least intensive" thing you can do is hold down Alt/Option at Startup. Thsi invokes the all-in-ROM Startup Manager, which will light up the screen gray or blue, then attempt to draw an Icon for each potentially-bootable Volume attached (if any). It works as if in slow motion, so you must be patient. If no activity after about two minutes you may count that as a failure.
    The next most intensive is to attempt to boot from an incorruptible source of software, such as an Installer/Utilities DVD. This again uses the "one-size-fits-all" display driver, and attempts to load software off the DVD. The dark colored Apple is loaded off a drive -- it is not present inside your Mac.
    The next most intensive step is to attempt to boot into Safe Mode. This also uses the "one-size-fits-all" display Driver, and does a disk check as it starts up, adding five minutes to the startup time. It then drwas a login screen and deamds your username and password, even if you normally auto-login.

  • External display locked to 640x480 after Windows 8.1 upgrade on 2011 MBP 17 in

    I just upgraded to 8.1 from Windows 8 in Bootcamp on my 2011 MBP 17in. Windows 8 ran fine and I was able to connect my Mac to an external display just fine.
    After the upgrade to 8.1 when I connect my external display it will only support a resolution of 640x480  and only shows a resolution 640x480 as the is the maximum res it can go. I have also loaded the Windows display driver to the Dell E228WFP to no avail. Any external display I try only shows a resolution of 640x480.
    I have removed the AMD Radeon HD7400M from device manager and re-installed the drivers from boot camp 5 but this doesn't resolve the issue.
    Any others havng this issue?
    Thanks.

    Hi,
    I ran into the same problem but I found out a solution for my early 2011 15-inch MBP.
    Basically, with the 8.1 upgrade, the OS mistook my graphics card for another. More specifically, it saw my Radeon HD6490M as one from the 7400M series.
    What I did to solve my problem was go to the Device manager, find my graphics card, right-click to get to the 'Properties' panel, and revert to the previous driver (the option should be available). Thanks to this, it reverted to the driver that was used when I was running Windows 8, and my external monitor is working great now.
    I hope this will help you!

  • My early 2011 MBP 17 started showing a thin vertical red line one inch from the left edge of the screen. Does anyone know what causes this problem?

    Does anyone know what causes a thin vertical red line on the display?

    There is a problem with the display or the connection to the display.  Take it to an Apple store genius bar for a definitive diagnosis.  The diagnosis will be free, any repairs will not be free.
    Ciao.

  • Problems with Late 2011 MBP (catalog corrupt, won't boot from USB/CD)

    Hello,
    I have had some problems with my Late 2011 MBP running OSX 10.8.x (latest update)
    I was using Safari when suddenly my screen froze. It has happened a couple of times before but it usually is either: 1.) a black screen for 5 seconds while nothing works responds and then it continues work like nothing happened, or 2.) just a freeze for a moment which goes away within a few seconds. I have visited the official service and they found nothing wrong with my laptop and said that it may have been just random occurrence. This time it froze and as I waited the fans went crazy and had no other option but to shut down from the power button. Later, when I wanted to boot up, it gets to the Apple logo, the circle spins and the small bar below appears and after a second or two, it disappears and then the computer shuts down. I went to recovery mode and used disk utility to verify and repair the problem (which only works to find out the problem, not to fix it, thanks anyway apple) Heres what it showed:
    Verifying volume “nihil”
    Checking file systemChecking Journaled HFS Plus volume.
    Checking extents overflow file.
    Checking catalog file.
    Keys out of order
    Invalid extent entry
    Incorrect size for file .mdworker_2013-07-21-081г41_эartin-RichaѲds-эacBѯok-ѐro.crash.plist
    (It should be 0 instead of 4398046511104)
    Illegal name
    Invalid extent entry
    Invalid extent entry
    Incorrect size for file .mdworker_2013-07-22-б20303_MartiѮ-RiѣharѤs-MѡcBoѯk-Pro.crash.plist
    (It should be 0 instead of 67108864)
    File has incorrect number of links (id = 60851670)
    (It should be 1 instead of 67108865)
    Invalid extent entry
    Invalid extent entry
    Incorrect block count for file .mdworker_2013-08-04-145002_Martin-Richards-MacBook-Pro.crash.plist
    (It should be 0 instead of 1024)
    Invalid extent entry
    Invalid extent entry
    Incorrect size for file .opendirectoryd_201г-08-04-б516а5_MѡrtiѮ-Riѣhards-MacBook-Pro.crash.plist
    (It should be 0 instead of 67108864)
    File has incorrect number of links (id = 66286495)
    (It should be 1 instead of 67108865)
    Invalid catalog record type
    The volume nihil could not be verified completely.
    Error: This disk needs to be repaired. Click Repair Disk.
    Verify and Repair volume “nihil”
    Checking file systemChecking Journaled HFS Plus volume.
    Checking extents overflow file.
    Checking catalog file.
    Keys out of order
    Invalid extent entry
    Incorrect size for file .mdworker_2013-07-21-081г41_эartin-RichaѲds-эacBѯok-ѐro.crash.plist
    (It should be 0 instead of 4398046511104)
    Illegal name
    Invalid extent entry
    Invalid extent entry
    Incorrect size for file .mdworker_2013-07-22-б20303_MartiѮ-RiѣharѤs-MѡcBoѯk-Pro.crash.plist
    (It should be 0 instead of 67108864)
    File has incorrect number of links (id = 60851670)
    (It should be 1 instead of 67108865)
    Invalid extent entry
    Invalid extent entry
    Incorrect block count for file .mdworker_2013-08-04-145002_Martin-Richards-MacBook-Pro.crash.plist
    (It should be 0 instead of 1024)
    Invalid extent entry
    Invalid extent entry
    Incorrect size for file .opendirectoryd_201г-08-04-б516а5_MѡrtiѮ-Riѣhards-MacBook-Pro.crash.plist
    (It should be 0 instead of 67108864)
    File has incorrect number of links (id = 66286495)
    (It should be 1 instead of 67108865)
    Invalid catalog record type
    The volume nihil could not be verified completely.
    Volume repair complete.Updating boot support partitions for the volume as required.Error: Disk Utility can’t repair this disk. Back up as many of your files as possible, reformat the disk, and restore your backed-up files.
    I tried to boot DiskWarrior from a USB and a CD, after pushing enter in the bootable device's screen, I get a continuous loop of 3 beeps and I can't boot from either of the mediums.
    I also tried the Single-user mode (Command-s when booting) and the /sbin/fsck -fy said that my HD is not completely verifiable. Also, 3/4 of the files mentioned in disk utility are also mentioned in this process, with errors as forrows: keys out of order, invalid index key, invalid extent entries (7 times), incorrect block counts, number of links and incorrect sizes for the foretold files and invalid catalog record type.
    The reason why I'm not doing a clean install is that the last few days I've been in the process of deleting unnecessary items on my laptop so I could make a back-up (as for some reason, Time Machine is awfully slow and a new 600 gb backup would take and enormous amount of time, but that's a problem for another day) and as I had not yet reached the backing up part, my data is locked on this (possibly) corrupt HD. How should I advance and what steps should I take?
    My first and most important mission would be to get back into my OS to make a back-up. Then I'd deal with the "not being able to boot form USB nor CD" and the TM problem.
    Thank you all in advance,
    Martin

    Before you even start, consider that there may be no Windows 7 driver support for some of the hardware in your laptop. You won't know which hardware devices and functions are unsupported until you find out the hard way. In some cases, a driver conflict could cripple your computer.
    Like most OEMS, Toshiba pre-installs Windows 8 to boot with EFI on a GPT hard drive. Your Windows 7 install disc, on the other hand, most likely boots with a BIOS from an MBR. Therefore, your Windows 7 disc will not boot your computer.
    You would need to start by performing a low-level format of your hard drive. This completely erases the disc and its metadata. Then you could boot from your Windows installation disc and try to install Windows 7. How successful you will be depends on driver support.
    All things considered, you should stay with Windows 8. Next time, more research before you buy.

  • 27-30" Monitor to accompany 2011 MBP

    I'm looking to upgrade desk monitor now that I've got the 2011 MBP with the Radeon HD 6750M. Primary use is video editing, with some standard home-office activity. I do have some light coming into my study, so antiglare has become more important to me. Here are the options I've been mulling over...
    1. Dell U3011
    2. 27" iMac (although not antiglare and facing refresh soon)
    3. 27" Apple Cinema Display
    If I have the patience I'm inclined to wait for the iMac refresh to see if they come with antiglare along with the better hardware. But I'm also very interested in the real estate of the U3011.
    Thoughts?
    Thanks.

    I'm using a 2010 15" MBP with apple's 27" cinema display mainly for Final Cut Pro and Aperture / Photoshop works. The experience couldn't be better. This screen is massive, and unless you get a spotlight or a window right behind your shoulders pointing directly to it, it's own brightness would eliminate any other reflections in your room.
    If you find a way to test it in you'll stay with it, I guarantee that.
    regarding the dilemma of buying an iMac or a new MBP, I would buy the latter and here's why:
    an iMac will never come in Matte, so there's no difference between an iMac screen and an apple cinema display.
    an iMac is still limited and not expandable as MacPro is, so choosing between a desktop configuration and a portable-cinema configuration would make sense only if the desktop configuration is a MacPro.
    The latest generation of MBPs is being reported as fast and powerful as today's MacPros model and even better so why limiting yourself to a desktop workstation while you can have the best of both words by opting for a MBP-Cinema display configuration!

  • MBP changing color when thunderbolt display attached

    So I have the last gen 17" mbp running 10.8.2.  the color on the display looks great except when I attach my new thudnerbolt dislpay.  The color temp of the MBP display goes really cool (blue) when the thunderbolt display is attached.  Whenever I unplug the display, it goes back to normal.  Anyone else seen this or have any idea what is going on?
    Thanks,
    Scott

    Bought a TB display to use with my 2011 mbp last night.  Hate that it doesn't have a power button.
    Really hate that the usb implementation seems quite broken.  I spend 95% of my time in Windows, and while the display functions, usb doesn't really.  The apple usb keyboard i bought sticks, and my dell mouse hangs frequently.  both are plugged into the display, but they work fine when plugged into the laptop directly. I also have a jabra usb headset plugged into the display.
    I have noticed I can worsen the situation by actually using the display hardware.  If I start a call using the headset, the keyboard and mouse become even worse.  If I start using the facetime hd camera on the display, they become horribly erratic.
    Apple definitely has some work to do.  They are billing this is a docking solution and it is completely unusable as such right now.

  • AMD Radeon HD 6750M, Early 2011 MBP, 10.9.4 Problems

    Hello,
    Ever since 10.9.3 update I have a serious problem with my Early 2011 MBP with AMD Radeon HD 6750M card.
    First my configuration:
    MBP 2.2 GHz Intel Core i7 (Macbook Pro 8,2)
    16 GB RAM
    512 GB Sandisk SSD and 750 Stock HDD
    AMD Radeon HD 6750M and Intel HD Graphics 3000
    OS X 10.9.4
    I'm usually using my MBP with external display with a resolution of 1920x1080. The display is connected via DVI to Mini Display Port adapter. When I connect the external display, my MBP switches to the AMD card. Here's where the problems begin. If I'm using Davinci Resolve, Capture One Pro or any other software (that I use regularly) that uses the GPU extensively, the cpu usage will rise, the computer will start to feel sluggish and my productivity almost becomes none because even the simplest tasks such as opening another tab in firefox or safari takes anywhere between 1-3 sec. When the computer starts doing that, I cannot play a simple HD video at native fps and the whole machine basically becomes too expensive paper weight. The strange thing is that even after I quit all programs, the system cpu usage continues to be high, around 50% with kernel_task being the star using all this cpu and it keeps using all of this cpu forever, at least until i shut it down or disconnect the external display and manage to make it switch to the internal Intel gpu.
    The problem started after istalling the 10.9.3 update and it's still there with the 10.9.4 update. I even formatted the computer and reinstalled everything but the problem still persists.
    I haven't experienced anything like this on 10.9.2 and the machine was actually quite fast before that. Now, I have too expensive paper weight on my desk.
    Since the problem is very specific, I doubt many users will complain and I doubt Apple will ever do anything to fix it, at least until hopefully the new drivers in 10.10 fix the issue hopefully.
    My question is:
    1. Has anyone else experienced this and managed to solve the problem?
    2. How can I downgrade to 10.9.2? I don't have time machine backup but i have bootable usb with 10.9.2. Will it help?
    All best,
    Goran

    When you have the problem, note the exact time: hour, minute, second.   
    These instructions must be carried out as an administrator. If you have only one user account, you are the administrator.
    ☞ Launch the Console application in any of the following ways:
    ☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
    ☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
    Open LaunchPad. Click Utilities, then Console in the icon grid.
    The title of the Console window should be All Messages. If it isn't, select
              SYSTEM LOG QUERIES ▹ All Messages
    from the log list on the left. If you don't see that list, select
              View ▹ Show Log List
    from the menu bar at the top of the screen.
    Each message in the log begins with the date and time when it was entered. Scroll back to the time you noted above. Select the messages entered from then until the end of the episode, or until they start to repeat, whichever comes first. Copy the messages to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.
    The log contains a vast amount of information, almost all of it useless for solving any particular problem. When posting a log extract, be selective. A few dozen lines are almost always more than enough.
    Please don't indiscriminately dump thousands of lines from the log into this discussion.
    Please don't post screenshots of log messages—post the text.
    Some private information, such as your name, may appear in the log. Anonymize before posting.

  • 2011 MBP 2nd HDD mod with SSD

    I have been trying for days to successfully get Bootcamp 4 +win7 onto my 2011 MBP.
    I have modded my MBP to have a second hard drive (ssd in main bay, original 750gb HDD in sled where optical drive used to be.)
    SSD is in the main HDD slot, and was put there since the main sata bus is native 6gbs (sata3), where the optical drive bus is sata 2.
    So since my ssd is sata3, and the original drive is sata2 it made sense, also it made sense since the main bus is where the computer is designed to boot from.
    Ok, so heres what I have done.
    I have used Bootcamp, with all combinations of the three boxes checked. (after editing files in my mac i was able to use the "create windows 7 USB installer" function)
    I purchased a macbook air super drive (after editing files on my mac, i was able to view and use the drive normally in my OS, but unable to boot from it.) Ended up returning it because an $80 that you can ONLY use on very specific systems is outragous... $25 bucks for a super generic one that has an infinite amount more compatability, or $80 for a locked drive...and here I thought the days of doing stupid proprietary crap to hardware was over
    Gparted, testdisk, pdisk, and other table editors have been no help... (cant even get gparted to boot past video drivers, even in vga mode it errors)
    I can successfully install windows when i replace the original superdrive that shipped with the system, with the original HDD in the main bay. When I install using this method, as soon as I rebuild my system (ssd main bay, hdd in second bay) my mbp fails to see the windows install (blinking ? folder). I think has to do with the drivers for the 2 sata busses are different.
    Holding "alt/option" sees a "Windows" partition that is bootable. when selected, my mbp fails to see the windows install (blinking ? folder)
    Disconnected the drive from MBP, connected it to my desktop, viewed / edited in gparted. Same outcome...my mbp fails to see the windows install.
    When I follow the main bootcamp instructions for a USB install, I can successfully create a bootable USB with windows 7 on it (works great on my PC) when my computer restarts to install... cant boot from usb, i get the blinking folder (in this config, the drives are in my preffered locations: ssd main bay, hdd in second bay)
    Someone said certain USB sticks may not work to boot from... the same USB stick boots up to gparted fine on both my iMac, my PC and this MBP... and the Windows 7 on USB that bootcamp created boots my PC seamlessly. so I doubt its the USB being "unbootable" (just to check this, i erased, reconfigured gparted live USB, and plugged in... not only does it boot, it boots fast, same with a MSDOS recovery USB stick and Unbuntu Live USB)
    I disassembled an External DVD drive, and tried about 8 different drives connected directly to the circut board of the external... Can see whatever disc i put in the drive, but only in the OS, Can not boot from any of them (windows dvd shows up as bootable when that disc is in, but selecting it gives me a blinking "_" on a black screen, a black screen, or the message "no bootable devices found, insert boot disc and press any key" depending on where I am at in my process
    How on earth should I go about completing this bootcamp install... Im beginning to lose my mind about this.
    I have been a computer tech for over 10 years and every logical solution seems to fail for reasons not apparent to me... maybe jobs was in a bad mood when they discussed how my MBP should function.
    Why not let me boot from an $80 superdrive?
    Why not let me boot Windows 7 installer from anything besides the original drive?
    Seriously... Why?
    $2000 dollars for a computer should be more than enough cheddar to get a system that isnt locked to Apples way...
    I was always a PC loyalist, and my MBP started to change that a little. But then the simple things like... booting from a different source, cant use external drives.
    My next best guess on what to do is:
    reconfigure the mac to factory, install bootcamp and configure windows on the main HDD bus.
    Take out that HDD configured the way i want it.
    put in ANOTHER DIFFERENT spare drive.
    rebuild
    install bootcamp again, go through options, partition drive and when it restarts to install, shut it down
    take spare drive
    connect both bootcamp drives to my PC, use GParted to compare the partition tables. Edit one to reflect other
    restart and see if bootcamp is bootable...
    The number one reason i was told i would enjoy my apple...
    "it just works"
    lmao

    SOLVED it for myself like this:
    Moved back the HDD from optibay to main bay. Put back the optical drive in and booted off of a windows 7 DVD and installed it on the HDD. Moved the HDD back to optibay and SSD to the main bay. Booted up and holding option/alt showed both Windows and Lion.
    Hint: I didn't wanted the win to be installed on my SSD, I am so afraid of imagining what win can do to it
    Here is what I experienced:
    SSD in main bay, HDD in optibay:
    * no boot off of a bootable windows setup on a USB made with:
    1- NTFS format (made on mac with Unetbootin)
    2- FAT format (made on windows)
    3- UDF format (made on mac with direction given here : help.ubuntu.com/community/Installation/FromUSBStick )
    * no boot off of an external DVD with original windows setup DVD
    * boots off mac os original DVD supplied
    No SSD, No HDD, No Optical drive:
    * no boot from flash/win cd
    * boots off mac os original CD supplied
    Optical drive in Optibay, SSD or HDD in main bay:
    * boot off win DVD
    * No USB booting!
    * No extrnal DVD booting
    Hope this help someone!

Maybe you are looking for