Q: Anyone getting graphics corruption in OSX Mavericks?

Its kind of comforting to find i'm not the only one with this annoying scrambling!

Anyway, surprise surprise mines also a Mid 2010 15" MBP running OSX Mav. soon as I turned off the Automatic graphics switching as JVinegar suggested it corrected itself immeidately.

Not sure what the graphics switching does or if i'll even notice a difference with it off, but it'll do for me until Apple release

Thanks guys

I started having the issue after restoring my system from a Time Machine backup. It turns out that is a complex thing to do (another story), but I found a solution in a parallel thread.

One was to boot up in Safe Mode, which clears several caches that can cause the problem. I decided to go with Onyx, which cleared my caches and also did some other needed maintenance. So far, no further corruption.

Here's the link: http://www.titanium.free.fr/downloadonyx.php

Hi - Despite Onyx, I'm afraid the problem will return.  Although Onyx is a great utility and highly recommended, it doesn't correct this issue.  In addition to running Onyx, I've erased and re-installed everything (after full backup of course), and had my logic/motherboard replaced (at Apple's expense, an "A" for good intentions).  See my earlier posts to this thread.

The fact remains that most of the people participating in this discussion have the same problem, with the same model of computer (2010 MacBook Pro model ID 6,2, although it appears that some Mac Minis have it too).  We all know what the work-around is (change the setting in Energy Saver - see http://support.apple.com/kb/HT4110), but that runs the battery down more quickly.  In other words, it's a hardware issue outside of the end user's control, which has a tangible negative impact.

Unless I'm missing something, it appears that three outcomes remain:

1) Mavericks 10.9.2 offers a fix (not a work-around)

2) Apple replaces these machines altogether (with a model that has a different hardware design, not subject to this issue)

3) Apple does nothing further, and risks its customer goodwill.

The second item may seem drastic and expensive (to Apple), but we didn't ask for this issue.  It's not our fault.

Since the problem only occurs with Mavericks installed, that makes it a software issue, not a hardware issue.  As you've noted yourself, a logic board replacement didn't fix the problem.  Reverting to Mountain Lion does  fix the problem. 

Apple can fix this with a software update, and I'm a little miffed that the richest company on the planet didn't bother to fix it in the 10.9.1 update.  What exactly is going on at Apple that results in an OS X release breaking an entire year of laptop models?  I can't help but wonder how Steve Jobs would have reacted to such a colossal blunder.

well, there is also option 4, Apple does nothing and burned customers buy a new laptop.  I definitely have Retina Display envy, but at 2k+ a pop, you like to think it will last a while.

yes, me too, the whole story  !!!

switch from windows to mac 3 years ago.

- after update to Mavericks the problem start

- contact a premum support and paid 70€ for a 2 day diagnoses without any result. Hint from the support do a clean installation

- clean install of OSX Mav just the same problem

- 2-3 hours fon call with applecare germany: They never heard about that problem and they can give me support because I am out of Warranty. But, they suggest to install Mountain lion again and check if the problem is also there.

- I installed mountain lion. No Problem anymore. But, I can't use the latest software updates of final cut....

- back to Mavericks. The Problem is back. I have to use the graficcard energy save trick to work with it.

- no reaction to my applecare ticket. Very BAD support !!! I had some kind of simular experiance with Dell.

- I notice, if I use a second monitor the problem is not shown.

I switched from Windows to Apple to have finally a system that is build to work NOT!

Let's see if this will be fixed soon....

sorry, I can't resist

https://www.facebook.com/Mavericksarts

I admit, I haven't read the thread, but I wanted to add, that I had this scrambling already in Lion - this was the whole reason, why I changed to  Mavericks. Now it happens much less frequently, but it still does, from time to time ...

MBP 2011, 10.9.1

Discrockers,

I like your idea about posting our screens. If enough people posted or shared I'm pretty sure it would make enough of a headline that maybe we'd see a response from Apple at some point... although it's likely to be a 'cease and desist'.

I filed a bug report with my Apple dev account and it turns out that Apple engineering is aware of the issue.

 

Engineering has determined that your bug report (15869971) is a duplicate of another issue (15652623) and will be closed.

 

I guess that's a good sign and hopefully it will be fixed in 10.9.2

I would suggest others post a bug report too. Registration is free. https://bugreport.apple.com

It would be good to see what bug report 15869971 actually says. Unfortunately I don't think we get access to that.

I have certainly been working with Apple Senior Analysts who have sent off capture data (along with my screenshot) to Engineering who should be figuring out where the issue is and resolving it (that is after they replaced numerous parts of my Macbook Pro, including the Mainboard).

I have also drawn all their attention to this discussion forum several times, so they are definitely aware of the issue and working towards figuring out what is actually causing it so they can resolve it.

I don't think we can read anything into this.  When I filed a bug a few weeks ago, same response: my bug was the duplicate of another issue (and it's the same one that Freezeman referenced above, 15652623) and was closed. 

As circled on my screenshot, the rank of the bug was "No Value," which has ambiguous meaning!  It's hard to know whether "No Value" means that the bug was not assigned a some kind of a rank, or that Apple decided that the bug could be ignored.   I then searched for #15652623 and the result was "No problems were found that match the search criteria (OK)".

At worst, this is further 'evidence' that can be presented to an Apple Engineer or Sr Analyst.

I think i have a possible solution to this problem.

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.

It might affect other Intel GPUs so its worth a shot if you have a similar problem.

Hello Pehtis,  I've just tried your suggestion.  So far so good (machine didn't explode).  Will report my progress, good or bad.  Thanks - Steve

Thank You Pehtis,

I beleive your solution is working.

Please share this on as many discussions of this issue as possible.

Many MBP users are suffering because of this.

I would like you to take credit of this solution you suggest so i will not be posting it.

Thanks,

Aatit