Q: Anyone getting graphics corruption in OSX Mavericks?

Heinz1970: The problem solved by 10.9.2 is the graphics corruption bug some users were having with the integrated graphics card.

The bug you have is this one and it can't be solved by software updates: http://support.apple.com/kb/ts4088

If you bought your computer in less than 3 years ago, you can take it to an authorized service provider. They will run a test and replace your logic board for free.

I'm also having this problem with my mid 2010 MBP and as a temporary workaround, I'm running gfxCardStatus to disable the automatic graphics switching and force the integrated graphics mode.

I still have a few months to complete 3 years since my purchase, so and I'm taking it to fix next week.

I bought it used last June via ebay and don’t have the original invoice to know when it was purchased the first time.
I can not use gfxCardStatus because than I can not use the Creative Cloud anymore.

I followed this thread and had the graphics corruptions like described in the beginning even before Mavericks. But it was gone after installing the system new by a Genius.
The crashes kept.

I can not afford a new Mac and this is my most important working tool!

Definitely agree with weslly...bring it in with that notice printed out.  They should be able to run a special test in store.  Even if it is a bit outside that realm, you have documentation the issue occurred earlier (at an Apple Store).  They will be able to check the serial number and get the machine's history.

umparrothead: which notice you mean to print out?

The one mentioned earlier (http://support.apple.com/kb/ts4088), just so that they know exactly what you're referencing and that there is a coverage extension as well.  Good luck!

Thank you! I will make another apointment and try to get that fixed

I was just about to report two graphic corruption free weeks, when my mpb suddenly went black during some editing in Garage Band. Anyone else gotten their problems back?

i had a full screen of GUI garbage, when i recently launched the revamped Diablo 3 (after patch 2.03) - it happened twice - but disappears after a few seconds, when you get to The Reaper Of Souls promo

- it looks like the graphics problem hasn't been fully sorted - or else there's still a glitch when switching from the Intel to nVidia cards.

I only had one incident.  A few days ago, I was watching a very large video file with VLC.  VLC forces discrete graphics, so no issues while in that mode.  Immediately upon quitting VLC, the GPU switched back to integrated and I, immediately, saw some corruption in my dashboard widgets.  I used the old trick of toggling the GPUs with gfxCardStatus to clear the artifacts (only one toggle needed; previously, I'd sometimes need multiple toggles depending on how "sticky" the corruption was at a given moment).  I guess I hit that sensitive "sweet spot" level of activity required to push the graphics memory and the compression into the "problem zone".  Other than that one time, 10.9.2 has been smooth sailing.  Prior to the update, I was getting corruption on a daily basis doing more mundane tasks, which was much more infuriating.  If the frequency has been whittled down from "daily" to "every once in a while", I supposed I can't really complain.

Yes, here we go again.  The colors are pretty this time.  I installed Mav 10.9.2 from the "Combo" update, not the 10.9.2-only update.  Before installing it, I returned Pehtis' compressed memory fix back to the default setting.  I'm posting this also to the Apple Feedback board http://www.apple.com/feedback/macbookpro.html

Hi Cerebro - Interesting that you were using VLC when this happened.  I happened to be using VLC (v2.1.4) and HandBrake (v.096) earlier this week.  I don't think I turned the machine off that evening, so perhaps that's a clue.  I had 'undone' Pehtis' graphics fix but i'm putting it back on now.  Here is that fix (quote from Pehtis' January posting here)

"To fix it you have to disable compressed memory by typing the following command in the terminal:

sudo nvram boot-args="vm_compressor=1"

and then Restarting your Mac.

I'm guessing that its a bug in the driver of the Intel HD Graphics integrated GPU used in the 2010 MacBook Pro and somehow a part of the graphics RAM is accidentally compressed. I've been testing for approx. 8 hours and so far no graphics corruption at all.

If it gets fixed in an OSX update or it doesn't work for you you can use:

sudo nvram -d boot-args

to reenable compressed memory."

I got my Logic Board replaced for free. Thank you Apple, my MBP works fine now.

I think I might have the same problem, i.e. black screens etc. My mpb is 3+, anyone with experience of getting the logic replaced for free even though it's too old? Read somewhere that Apple sometimes did this as goodwill.

Just for clarification, for anyone who might be stumbling on to this thread late in the game, we seem to, once again, be crossing our wires and talking about two different problems in this thread.  Granted, both of them are graphics related which, no doubt, continues to lead to the overlap.

Problem #1:  Is this:  http://support.apple.com/kb/TS4088.  Intermittent black screen or loss of video, or similar such symptoms.  This has, largely, been identified by Apple as a hardware issue, specifically with the Nvidia GPU.  Apple are, on their own dime, replacing logic boards on affected models as a last-ditch solution.

Problem #2:  Graphics corruption (what this thread was, initially, intended to address).  Symptoms have, typically, manifested as graphical artifacts appearing on screen to varying degrees and blocky drop shadow rendering around windows.  The symptoms have, usually, occured when the Intel GPU is active.  Toggling over to the discrete GPU clears the artifacts.  This has been show to be a software issue.  For many of us, the problem was nonexistent until we upgraded to Mavericks.  Has Pehtis's solution has proved, the problem is directly related to the memory compression feature introduced with Mavericks.  10.9.2 has, largely, solved this problem.  Though it isn't 100% there, yet.

both problems on mbpro mid 2010, with more than 3 years