Currently Being ModeratedAug 23, 2012 9:56 AM (in response to StevenLu)
It didn't fix it =(
But it's not too bad. Mountain Lion is still pretty great. Also, don't forget that I'm using an external monitor (olf Apple cinema display) connected via a Mini displayport to DVI adapter. The issue doesn't seem to manifest itself without the external monitor hooked up.
Currently Being ModeratedAug 23, 2012 9:58 AM (in response to mc.escher)
I haven't tried it because I have a different video card (I'm using a mid-2011 Macbook Pro) and I think the fix involves replacing your driver or something. I'm sure Apple will fix it eventually. It only seems to happen occasionally now and only with my external monitor hooked up.
Currently Being ModeratedOct 1, 2012 2:26 PM (in response to gfelipe)
any new experiences with 10.8.2?
If there is still the bug, you should fill a bug report ( bugreport.apple.com ). I think this is the best chance to get this problem fixed.
Currently Being ModeratedOct 1, 2012 3:42 PM (in response to StevenLu)
Actually, I had the same problem until I switched monitors. I was using an old Apple Cinema Display (circa 2004). I'm not using a generic monitor from Best Buy and I haven't seen the problem anymore. I also switched my mini displayport to DVI adapter to a Monoprice one for $6.65. So it could be either one that fixed the problem.
All I know is before Mountain Lion, I never had the issue using the old adapter and Apple Cinema Display. It's a shame. Considering it's an Apple monitor, it should just work.I believe it's a model A1081.
Currently Being ModeratedOct 1, 2012 7:52 PM (in response to ricardofromzoetermeer)
I have had this problem on all version of Lion, and now experience a version of it on Mountain Lion 10.8.2
Whereas I used to see transient display corruption artefacts, the new failure mode is an unrecoverable display corruption where the display fails to update and the console log fills up with NVDA(OpenGL): Channel exception! exception type = 0xd = GR: SW Notify Error messages.
This error requires a hard power-down to recover.
There are other threads that describe the NVDA channel exception errors on these forums, particularly with ML.
Currently Being ModeratedOct 2, 2012 8:30 AM (in response to dsdreamer)
I would first try the Combo updater: http://support.apple.com/kb/DL1581
Then, try restarting using the Recovery mode (hold R at startup) but obviously not reinstall OSX (althought you can try that without losing your data). One you're in, go to Utilities up top and run Disk Utility. Check or Repair disk, and repair permissions. Restart.
Then try resetting the PRAM
or maybe if you have the nvidia card, you can udpate the driver. That seems to be the solution for many, depending on what model they have. What year/model is you Mac?
You can also try booting up with only one stick of RAM in (if you have two) and no other devices connected, just power. If nothing happens, try using the other RAM stick and take out the one that's in there. Also try switching the one that's in to the other slot. Could be that the RAM went bad.
There's also Apple's built-in hardware test. http://support.apple.com/kb/HT1509
Make sure you do the full scan. It could take a while, but it'll scan everything, including your RAM for failures.
If nothing else, schedule an appointment at the Genius Bar, and they'll check it out even if it's no longer under warranty. It could be defective or a recall issue and you might get it fixed quickly!
Currently Being ModeratedDec 27, 2012 11:57 AM (in response to gfelipe)
In the end, after a year of hoping the the next OS X update will fix it, and trying all the usual remedies (safeboot, repair permissions, SMC reset, PRAM reset, avoiding Flash content, changing my browser) nothing was working in ML 10.8.2 to prevent NVDA channel exception graphics crashes. I decided it was high time to let Apple have a go, even if it cost me. The Genius Bar was able to reproduce the fault and they sent it for a depot repair where they changed the logic board and replaced my installed 3rd party (Crucial) 8GB of RAM back to 4GB of their own preferred RAM.
The final result is a fully working Macbook Pro with no graphics issues whatsoever.
I am left with the question as to whether the RAM was really implicated in the problem, or whether they changed it out just for safety.
Nevertheless, it is really nice to have a fully reliable Macbook back in my hands.