Macbook Pro screen becomes blue every time a discrete graphics card is used!

The easiest way to deal with this issue, is to log out and log back in everytime you power on. as long you have it in sleep mode, youre fine till next time you do a complete power off.

Turing off automatic graphics switching in energy saver prefs is the only thing that solved this problem for me. It is consistently reproducible with the graphics switching set to "on" so it is not a hardware problem (to my relief). I run 10.6.8 so any ML solutions are not going to help me. I'd wish that Apple would address this and also the problem with invalid file count and needing to repair the disk frequently... A LOT of people I know still run 10.6.8 for professional audio and composition work and are not going to upgrade the OS any time soon. Oh well :s

Well, the problem is back for me. I removed my Intel 320 120GB SATA2 SSD and installed a Crucial M4 SATA3 256GB SSD. I then enabled FileVault. LOTS of blue tint jumpiness happening during the FileVault disk encryption. Now when I open up a large Ps file, the screen turns blue. Logging out/in solved the problem temporarily, but this is getting quite annoying for such a high-end laptop.

http://youtu.be/VdU9FFTlvFs

same problem. "smc reset" fixed it for me, for a time at least:

http://support.apple.com/kb/HT3964?viewlocale=en_US&locale=en_US

greetings michael

there is no mentioned workaround here, which solved the problem, other than using login and password when booting. i never used login and password when booting, but since i use it, i didnt have a blue screen problem anymore. i can provoke it clearly, when i turn on login&password in system settings in 10.8.3 - then i get a bluescreen, when starting adobe photoshop CS6 instantly.

i never had this problem earlier on 10.7 or 10.6 and so on. apple didnt fix it. why?

so, this permanent workaround (which is slightly annoying) solved the problem for 100%: turn on login and password in system settings. (under system>user)

thanks for your help and time!

I have the same problem with OS X 10.8.3 .

Nothing works for longer than 3 restarts.

Reinstalling latest OS X update

Reinstalling Flash

Deleted the ~/Library/ColorSync

Of course deaktivating 'automatic graphics switching' works. But then the battery duration is much lower, the mainboard gpu is then never used.

Happens to me only when I have iPhoto opened. Very annoying when you have to deal with photos professionally.

HELP!

Has anyone taken their MacBook Pro to an Apple Store to get Apple's response to this? There was one post in this thread about someone taking to the store and being told "We're working on it", but that won't cut it for me. I didn't get the top-of-the-line 17" MacBook Pro so that I could log out / log in every time I boot the thing.

If no one else has gone to an Apple Store, I'll probably take mine in this week. It has gotten to the point where without fail, every time I reboot, it will absolutely go back and forth between blue tint and regular color profile when launching graphics-heavy applications.

I'm encountering the same issue with my MPB Early 2011. This issue happens both in OSX and Bootcamp: Windows 7. I suspect what's happening here is the descrete graphics card is fried. I'm looking good on the integrated intel graphics card untill the system makes the switch over. If this is indeed a hardware issue, the whole logicboard will need to be replaced.

Going to reinstall OSX and see how it goes...

I'm almost definitely sure it's a software issue, since I ran FileVault in 10.6.8 with no issues for about a year, then when I upgraded to 10.8 and enabled FV, the blue tint issue presented itself. It's either an encryption issue, or a software issue, in my opinion.

i have found the problem !

after mounth of suffering i made a clean install, few day it was ok, but just now i see it again, so i tought to myself "what did i installed today?" and the answer was Aperture. So i removed aperture witha app for cleaning aditional files like http://www.freemacsoft.net/appcleaner/ (dont just drag Aperture to the trash you need to get everithing related out) and it worked for me ! Tell me if it works for you ! Regards !

thanks for your effort, i dont think our problem belongs to aperture, as a lot of people do have this problem without installed aperture. i have installed aperture, but i did also encounter the problem without aperture, before the install

It is NOT an Aperture issue, infact, it's not associated with any software. It's the OS/firmware thats cauing issue. Any application thats going to use the descrete graphics will trigger the issue.

Temperarly solution: everytime you power up the MBP, you log out immidiately then log back into your account. The issue will dissappear even if you put the macbook pro to sleep, until you power off and power on again.

A goodway to monitor what applications uses the descrete graphics chip or not is to install gfxCardStatus in your menu bar. it has a indicater what chip is being utilized at the moment and what application is using it.

It is NOT an Aperture issue, infact, it's not associated with any software. It's the OSX 10.8/firmware thats cauing issue. Any application thats going to use the descrete graphics will trigger the issue.

Temperarly solution: everytime you power up the MBP, you log out immidiately then log back into your account. The issue will dissappear even if you put the macbook pro to sleep, until you power off and power on again.

A goodway to monitor what applications uses the descrete graphics chip or not is to install gfxCardStatus in your menu bar. it has a indicater what chip is being utilized at the moment and what application is using it.

I solved the problem, but the solution is far from ideal. I erased my SSD and reinstalled 10.8.3 from scratch, and i DID NOT ENABLE FileVault 2. It appeared that the issue stemmed from having FV2 active on an SSD, and since I turned FileVault off, I don't really count this as a solution.

FileVault was causing a lot of other performance issues on my 17" MBP, so I decided that creating individually encrypted volumes for storing important data was a better solution for me than crippling my device on many fronts.

I hope Apple fixes this soon!