Written by me@grafxflow
If you are suffering from the infamous blue lines on the black screen on startup or random reboots then you maybe suffering from an AMD graphics card hardware issue with your later 2011 Macbook Pro laptop.
Now there are several solutions on the web but this is the only one that worked for me running macOS High Sierra (10.13.6+) and what was worst for me is that the MacBook Pro was stuck in looping reboot... I wanted to use the Time machine backup... if I could ever get it to bootup!
NOTE: One known issue to this solution (and maybe others) is that when the screen goes to sleep/black it no longer wakes up, therefore needing a forced reboot. The solution is to change your energy settings and make sure the screen saver animation options are always active.
Now there are other solutions that say at first boot into Recovery Single User Mode - CMD + R + S. But I had two problems - I had no permissions when trying to disable the csrutil and when trying the same with Recovery Mode - CMD + R I had the blue lines on black screen appearing, but the below sorted it for me.
So first reboot your Macbook Pro into single user mode by holding down the CMD + S keys. The terminal will now be on the screen.
First input.
sudo nvram fa4ce28d-b62f-4c99-9cc3-6815686e30f9:gpu-power-prefs=%01%00%00%00
Then.
reboot
Now reboot into Recovery mode using CMD + R. On the screen that loads choose a language then on the screen which appears next choose the following options in the menu Utilities -> Terminal - see below.

In the terminal add the following.
csrutil disable
When csrutil is disabled we can now move kexts and delete system folders.
Then.
reboot
On reboot go back into single user mode by holding down the CMD + S keys. Now in the terminal add the following, which will fix any disk permissions before we do anything.
fsck -fy
Once done mount the MacBook Pro hard drive by adding.
mount -uw /
Try using /sbin/mount if you get mount command not found
Now we are going to move all the AMD graphics card drivers, so best to make a copy of them rather than deleting them all. So first make a backup directory to copy them into.
sudo mkdir /amd-backup-kexts/
Then move all of the drivers with a wildcard naming.
sudo mv /System/Library/Extensions/AMD*.* /amd-backup-kexts/
Now once done lets delete the kext drivers cache.
sudo rm -rf /System/Library/Caches/com.apple.kext.caches/
To be safe create it again.
sudo mkdir /System/Library/Caches/com.apple.kext.caches/
Now update the timestamps of the driver cache without the AMD drivers.
sudo touch /System/Library/Extensions/
Now we are more or less repeating the same as Step 1.
sudo nvram fa4ce28d-b62f-4c99-9cc3-6815686e30f9:gpu-power-prefs=%01%00%00%00
Then.
reboot
Now reboot into Recovery mode using CMD + R. On the screen that loads choose the following in the menu Utilities -> Terminal.

In the terminal add the following.
csrutil enable
Then.
reboot
Now your mac should be booting normally without any issues, if not then there really is more than a graphics card issue.
Important! This is up to you but I would suggest doing a Time Machine backup just to be safe.
Hope this helps anybody else with the same problem.
Note: You will probably have to do this all again when doing any system updates and from my experience even security updates.
Founder, Grafxflow
I am a Full-stack Developer who also started delving into the world of UX/UI Design a few years back. I blog and tweet to hopefully share a little bit of knowledge that can help others around the web. I build lighting-fast dynamic content engines with Laravel, Winter CMS and Tailwind CSS. Thanks for stopping by!
Josemi
04 Jun 2020
Thank you very much, you are god! If you come to Spain I will invite you a beer!! hahahahaha
Damon
28 Jun 2020
Does this leave the thunderbolt port useless ?
caterina
18 Aug 2020
You are the best!!!!Thank you so much for sharing. Also beer in Vienna
Macaroni
22 Aug 2020
Damon, did you manage to change the hdd after doing the GPU fix? I myself tried to change my hdd to an ssd and now I cant get OSX installed on the new SSD even trying to install from an external drive. Did you have any luck? My solution now is to get a hard drive adapter and install OSX to an externally connected SSD through another computer then put it back in my MBP2011 and see if that works, not sure if it will though. Any advice would be awesome!!!
Numbiano
23 Aug 2020
Hi. I’m running a late 2011 MBP with High Siera. I can’t access recovery mode or single user mode so there is no way for me to access terminal to remove the GPU Kexts. I read somewhere that I can take out my SDD, boot it from another machine, remove the GPU kexts then replace the SDD into the machine with the failed GPU. Could you share some light on the process for doing this? Would it need to be done on a similar aged machine? Is their a risk of messing up the host machine? Thanks in advance!
Damon
20 Sep 2020
Macaroni
My ssd was already installed so I never tried anything after fixing the gpu issue.
TAG
25 Sep 2020
If you have trouble getting to recovery mode using command R try resetting smc and pram then holding it for like 5 minutes while it reboots or until the recovery mode screen pops up. I was having trouble until I did this.
Brian Paxton
29 Sep 2020
Before I embark on what appears to be a super great fix, let me state that:
1) My MBP runs OS X El Capital 10.11.6 and I'm unable to update.
2) I had a guy "heatgun" the GPU and it worked for a week or two, then the problems started to occur again. I let it sit for a week and after cooling it is rebooted now. Is there a better way to approach this fix and GPU switch if mine is able to boot for the moment?
Thanks for sharing this excellent information.
Cheers!
me@grafxflow
29 Sep 2020
Hi Brian,
I had a similar issue with an ibook back in the day with its graphics card, due to heat would start to separate from the motherboard therefore causing a major issue with the startup screen. It was fixed by adding pressure but eventually came back again. So you may have had the GPU welded back to the motherboard, I sadly still think it will keep coming back. It's a simple case of a badly built laptop that was done for this model proven by the amount of people with the same problem.
Eric Aguilera
08 Oct 2020
Thanks for this but every time I restart my 15” Late 2011 the process reverts. I’m running High Sierra. Any thoughts
me@grafxflow
08 Oct 2020
Hi Eric Aguilera,
Are you making sure to delete the ' /System/Library/Extensions/AMD*.*' ?
sudo mv /System/Library/Extensions/AMD*.* /amd-backup-kexts/
If these are still in the '/System/Library/Extensions' then it will keep crashing.
If need be try the following and see if the AMD extensions are still listed.
ls -a /System/Library/Extensions/
Eric Aguilera
08 Oct 2020
Hello Again
Thanks for the fast reply.
So im not that good with single user mode so I did the entire process again and im up and running in the os.
I navigated to /System/library/Extensions and I do see lists of files in there that start with AMD so im guessing I didnt delete them correctly.
Can I delete within the OS?
Thanks for your support
me@grafxflow
08 Oct 2020
Hi Eric Aguilera,
I don't think you will be able to delete them via the desktop, because they will be loaded and in use once it starts up. But if you follow the tutorial then it should work fine.
The really important part is the csrutil disable since without this disabled you won't be able delete the files either way.
AJ
28 Oct 2020
Hi,
Many thanks, it worked really well.
My sound is not working correctly, have a no entry sign at bottom when clicking the volume up and down key and other times it works fine?
Has anybody else have this issue? Do you have any possible solution