Issues with the AMD Radeon HD 6750M graphics card on MBP 15" Early 2011

I am having the same exact issue. My discreet 6750 is the culprit. The computer works ok with the integrated HD3000. I am going to the apple store today to see about getting it fixed. I have AppleCare so it shouldn't cost me anything. These things happen from time to time.

The NVIDIA problem was extremely widespread. Just about every manufacturer was affected, including Apple, Dell, HP, and others.

What you're experiencing is a more isolated case, and $300 is probably about right to replace the logic board. Nothing you can do except pay to fix it or sell it for parts and buy something else.

Update,

After having to get my MBP tested several time at the local Apple Store (Honolulu, Hawaii), they finally sent it off and I got a new logic board. Total time was about 1.5 weeks. They hassled me about having 3rd party ram. I literally had to drive back home and return another day (royally ******* me off) because they refused to send it with my OWC ram. Which, ironically enough is the same exact Samsung modules. The genius bar folks who handle these "complex" troubleshooting jobs are pretty dim. I have yet to meet a "genius" who was able to talk to me about things in appropriate computer vernacular. Anyway, it was fixed so it worked out in the end. I am just starting to really hate going to Apple Stores. I already know what is wrong, but they rarely believe me. Sigh. Still the best laptops in the world.

I got the same problem, I got a MBP 15¨, 2011. no warranty and I can not afford the cost. Failures seemed to occur anywhere from soon after purchase to over two years after purchase.

same problem here.

MBP 15" Early 2011

Seems that problem comes when switching do descrete graphics.

Stripes across the screen or blue screen requiring reboot.

Probably will have to go to Apple Service. Warranty finished

I have an early 2011 MacBook Pro 17" with an AMD6750 GPU that has failed.

I just dropped it at the Apple Store to be sent to the depot for repair - $310.

I think it is time for Apple to accept that these AMD GPUs are as poor and unreliable as the NVIDIA GPUs in the 2008 line of laptops. Apple needs to own up to these subpar GPUs and start covering the repairs for those affected and reimburse those that have already paid for a repair - just like they did with the 2008 models.

For a GPU to go bad in under two years is Windows PC-type reliability - not the comparison Apple wants.

I got the same problem from Spain.

Macbook Pro 15´ late 2011,

Warranty Finished

From the Apple service repair tell me that I can hardly 600€ (About $ 796).

Same problem here. MacBook Pro early 2011 AMD6750 GPU.

I will try to reball the graphic chip and post the results after.

Reballing will only prolong the inevitable. It's the type of solder they used and the gpu chip is faulty. There are currently other threads opened about this exact model. Here's hoping for a recall!!! The 2011 iMac with the amd is suffering the same issues. Only difference is that apple is fixing\replacing the free.

Did you have any luck with reballing the chip?

Yes, it's working perfectly now. The guy that did the repair said that had many with this problem and all got fixed.

Same what happen to my 2yrs old MBP 2011 model A1826 15" 2.2 corei7 with AMD Radeon HD 6750m GPU 1GB of DDR5.. really disapointed for this investment, i was expecting that Apple product will commit to what i invested. i suffer from Freezing all the time, and lead to damage and now unable to boot, with horizontal stripes in restart, and hang to a grey display. safe mode is turning into blue vertical lines.

Apple should recall all units with thesame GPU's.

Same as they did with Nvidia 2010, they recall all units.

Hey APPLE! as you will know many Guys here are suffering from your product, and investing for this product is not a joke!

Appreciated your kind concern...

I agree with you. I have similar problems with my Mac and I hope that Apple quickly fixes the error free!!!

Start to fail again. Reballing the GPU is just a temporary fix. Now it's working after restart and it's working as long as you don't use any intense graphic application.