Graphics corruption issue continues in Mavericks 10.9.1

Having the same issue since Mavericks upgarde.

We, too, are having the same issue with two of our Mid 2010 MacBook Pros with current update to 10.9.1 (MBP 2.53 GHz Intel Core I5 and 4GB 1067 MHz DDR3). Hope that there wil be a fix soon.

Also having this issue sporadically in OS X 10.9.1. I also wanted to ask if anyone has been having graphics crashes in Windows 7 as well? When I use Firefox and there is some kind of animation (like clicking on a download), I usually get a crash that makes the screen goes black and I get a "Graphics driver has recovered" bubble after a few seconds.

I upgraded to 8 GB RAM (Kingston) a while ago, so another theory I have is this might be caused by bad RAM. If you are experiencing this issue, are you using the original RAM sticks from factory, or have you upgraded your RAM? Memtest86 has some glitch that causes it to report all the RAM as bad on our computers.

I think i have a possible solution to this problem, at least for the MacBook Pro 2010.

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 a day or so 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

and then Restart to reenable compressed memory.

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

Hi, guys.

I also would like to add that my MackbookPro still has Windows special effect!

I'm seeing these graphical issues with my computer too. I have a 13" mid-2009 MBP so there's only the integrated graphics chip. The only time I see these colorful graphics glitches is while using Preview. If I expand to full screen they show up and the system studders for a second or two then displays the image.

I'm also having other issues but I've already posted my own thread about that. I believe I have a mix of hardware and software issues.

Pehtis,

Sounds like you may on to something with your solution. I'm always wary of messing with Terminal for fear of screwing something up. I'd like to have some confidence that what I'm doing is a good idea. If you could, please do keep us informed over the next several days and let us know if the fix sticks or if there might be new issues introduced as a result.

If you haven't done so, already, I'd recommend sending your feedback to Apple:

http://www.apple.com/feedback/macosx.html

Anything that can help Apple get an "official" fix out the door as soon as possible can only be benificial to the many of us who have been banging our heads against this problem for several months, now.

Pehtis,

I believe your solution is a good one as the corruption only occurs when the computer has experienced "high memory pressure." Since disabling memory compression have you experienced any further corruption?

I'm hoping Apple will have a fix for this in 10.9.2 but if not I will likely implement your solution. But I'd prefer to be able to take advantage of the memory compression.

Thanks for posting your solution!

Exactly the same thing with me. Mid 2010 15in.

Has this solved your issue?

I want to try it out but memory compression is quite nice..

mainboard = logicboard right? I got mine replaced too but it didn't help. I feel like they don't know which ones have the issue and just put on other faulty ones.

I too am having graffics problem as pictured in this thread. Applecare replaced the logic board about two weeks ago; that seemed to fix the problem until this morning. The same problem is back now. I have a mid 2010 MacBook Pro and upgraded my operating system in mid December 2013. The graffics problem appeared shortly after I completed the upgrade.

I also have seen this issue only after updating to Mavericks and only while using the Integrated GPU and while the machine was under heavy CPU/MEMORY usage. I am able to reliably reproduce the issue quickly using the gfxCardStatus by cody krieger application. If I eliminate applications requiring the discreet gpu and set it to Integrated the issue will be seen shortly after, and will go away immediately once I switch to the discreet gpu.

I have posted this using the apple feedback form, and pointed them to this thread as I noticed someone did a good job listing all the other numerous threads dealing with this issue.

For now rather then trying the memory compression fix I will just stick with using the gfxCardStatus by cody kriegera application and stay using the Discreet GPU since I use my machine for quite a bit of development and use virtual machines for a lot of my testing which wants all the power it can get.

Hopefully they fix this soon 😟

Hardware Configuration:

Model Name: MacBook Pro

Model Identifier: MacBookPro6,2

Processor Name: Intel Core i7

Processor Speed: 2.66 GHz

Number of Processors: 1

Total Number of Cores: 2

L2 Cache (per Core): 256 KB

L3 Cache: 4 MB

Memory: 8 GB

Processor Interconnect Speed: 4.8 GT/s

Boot ROM Version: MBP61.0057.B0F

SMC Version (system): 1.58f17

Serial Number (system): W801**T3AGZ

Hardware UUID: 87C1ECEA-***-54C4-9D33-1C0BB2C0A56C

Sudden Motion Sensor:

State: Enabled

Integrated Problematic GPU:

Chipset Model: Intel HD Graphics

Type: GPU

Bus: Built-In

VRAM (Total): 288 MB

Vendor: Intel (0x8086)

Device ID: 0x0046

Revision ID: 0x0012

gMux Version: 1.9.21

Discreet Works fine GPU :

NVIDIA GeForce GT 330M:

Chipset Model: NVIDIA GeForce GT 330M

Type: GPU

Bus: PCIe

PCIe Lane Width: x16

VRAM (Total): 512 MB

Vendor: NVIDIA (0x10de)

Device ID: 0x0a29

Revision ID: 0x00a2

ROM Revision: 3560

gMux Version: 1.9.21

Displays: