Currently Being ModeratedNov 21, 2012 4:15 AM (in response to JohnOMalley)
I took the MBP to the Genius Bar because if a service battery message. I showed them a year's worth screen shots depicting graphics issues. They returned it and said, third party ram issues. I cried foul. I only added the 16gb in last two weeks. So, I gave it back to them and asked them to figure it out. So, we will see.
Currently Being ModeratedNov 21, 2012 4:17 AM (in response to sidonsoft)
I could not get it to stop switching graphic modes. I'd change it, then it'd switch back on its own.
Currently Being ModeratedNov 21, 2012 4:20 AM (in response to JohnOMalley)
As if Apple's RAM isn't third party...
Currently Being ModeratedNov 26, 2012 8:37 AM (in response to JohnOMalley)
I received my MBP back from Apple. They replaced the logic board and display. I now have a new issue. When they graphics card uses the Radeon 6750 i get this blue hue to the whole screen. If I use the app you recommended it will allow me to switch to integrated card which removes the blue hue. Anyone have ideas?
Currently Being ModeratedNov 27, 2012 12:40 AM (in response to JohnOMalley)
It's a bug that a handful of us have experienced - and it's not isolated to one model or the other. Whenever the discrete video card kicks in, there's a bluish tint to the screen. I had the problem, used Cody Krieger's gfxCardStatus to isolate the problem, and after a few weeks my problem just 'went away'. Some have reported luck by turning of automatic graphics switching. I don't know what the real solution is, but you shouldn't have to live with it long - I hope: I didn't and I've no idea what 'solved' the problem at all.
Currently Being ModeratedApr 11, 2013 3:33 AM (in response to JohnOMalley)
I have this problem with my MBP's 6750M. It makes the machine unusable because the whole graphics system can freeze and require a restart after only a few minutes of use.
Since this started happening, I have been launching into my Lion partition most of the time. The problem has not shown itself in Lion for me; only in Mountain Lion.
I also suspected the dedicated GPU. Will try it with the GPU disabled. If that works, I would be curious to know the source of the problem -- is there a bad kext in ML? or does Lion just not use the dedicated GPU much?