Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

MBP 1,1-10,2 GPU Kernel Panic in mid-2010; what's the best fix?

Elia68 said:
I used my 2010 model for a very long time without any issue. The panic came out really from nothing. The best that you can do is running a 'Cinebench' test. With high probabilities the issue may occur during the test. Here what you need
https://www.maxon.net/en/products/cinebench/. Best regards.
Click to expand...
It looks like there's a tool in this thread and the other one to stop the graphic card from being used. I think I'll just throw on that, since I really will be using this laptop more or less as a chromebook (with mac only applications like Scrivener and Vellum).

just did the software fix, and then ran the cinebench test. It crashed it. Oh well, I was excited to have this as a laptop but I can't trust it if it's acting like this. :(
 
Last edited:
[doublepost=1532224360][/doublepost]
iMacC2D said:
Had the same issues with my 15-inch Mid 2010 machine. The repair extension program had since expired and because the machine had entered vintage status, replacement parts were no longer available.

I'd already bought soldering tools to repair a Mid 2009 MacBook Pro, so I decided to have a shot at changing the troubled capacitor. Problem solved. Not the easiest repair in the world but it would be a straightforward job for an electronics repairer or anyone skilled with a soldering iron.

This would be the better solution for anyone that isn't content with a temporary software fix, boots between multiple operating systems or needs the use of the higher powered graphics hardware.

View attachment 759608
Click to expand...

Did you use another poly tantalum cap?
 
Last edited:
Oh crap, I applied the patch to my mbp several months ago and it was working like a charm then i updated to high sierra 10.13.6 today and now it's buggered up again!! keeps kernel panicking. Is there another working solution - reapplying the patch didn't work.
 
It is possible to find
AppleGraphicsPowerManagement.kext 10.13.5
for Mac OS Sierra 10.13.5


fabioroberto said:
Hi,

Well, after years i found a solution. I have the famous MacBook Pro 6,2 with GT330m (
0x0a29 model).

I discovered that this problem happens every time that g-state change between 2 to 0.

G-States go from 0 to 3, are related to the thresholds inside AppleGraphicsPowerManagement.kext, like this:

G-state 0 (maximum speed) and G-state 3 (lowest speed).

I solved the problem by keeping it always at G-State 2 (medium speed).

And the performance? Exemple: Cinebench, default (G-state 0) i've about 15fps, with g-state 2 (medium speed): 10fps.). Not bad.


If you want to try, these are the values changed in the info.plist:



<key>MacBookPro6,2</key>

<dict>

<key>LogControl</key>

<integer>1</integer>

<key>Vendor10deDevice0a29</key>

<dict>

<key>BoostPState</key>

<array>

<integer>2</integer>

<integer>2</integer>

<integer>2</integer>

<integer>2</integer>

</array>

<key>BoostTime</key>

<array>

<integer>2</integer>

<integer>2</integer>

<integer>2</integer>

<integer>2</integer>

</array>

<key>Heuristic</key>

<dict>

<key>ID</key>

<integer>0</integer>

<key>IdleInterval</key>

<integer>10</integer>

<key>SensorOption</key>

<integer>1</integer>

<key>SensorSampleRate</key>

<integer>10000</integer>

<key>TargetCount</key>

<integer>1</integer>

<key>Threshold_High</key>

<array>

<integer>0</integer>

<integer>0</integer>

<integer>100</integer>

<integer>200</integer>

</array>

<key>Threshold_High_v</key>

<array>

<integer>0</integer>

<integer>0</integer>

<integer>98</integer>

<integer>200</integer>

</array>

<key>Threshold_Low</key>

<array>

<integer>0</integer>

<integer>0</integer>

<integer>0</integer>

<integer>200</integer>

</array>

<key>Threshold_Low_v</key>

<array>

<integer>0</integer>

<integer>0</integer>

<integer>4</integer>

<integer>200</integer>

</array>

</dict>

<key>control-id</key>

<integer>17</integer>

</dict>



Perfect values? I do not know, but it is working for me.


Now, we have three methods to apply this fix:
1º Editing kext file and install manually;
2º Using the utility program called MBP Mid 2010 GPU Fix, that allows to fix the kext, using the parameters above described, automatically (credits [below] to julian-poidevin);
3º Hardware fix. Read the next posts pages to know about that. Credits to l.a.rossmann


1º Editing kext file and install manually:

Step by step:

1 - Make sure these .kext are original (unmodified), and loaded (About this Mac -> System Report -> Software -> Extensions):
  • ACPI_SMC_PlatformPlugin.kext (IOPlatformPluginFamily.kext)
  • AppleGraphicsPowerManagement.kext

2 - Disable SIP (boot into recovery mode, terminal: csrutil disable)
Avaliable only in OS X El Capitan or later. Previous OS X versions, jump to next step.

3 - Open Extensions folder (System/Library/Extensions), copy AppleGraphicsPowerManagement.kext to desktop (or other folder), open the info.plist into editor (I used the PlistEdit Pro.app), and change the values like writing up.

Attention: verify if your model is 0x0a29 really.

4 - Save info.plist, quit editor.

5 - Use Kext Drop.app to instal this kext, but before, delete the AppleGraphicsPowerManagement.kext into extensions folder.

6 - (This is important step) Leave the automatic graphics switching select (System Preferences - Energy Saver), if you are using gfxCardStatus.app, same thing!.

After, reboot normally.

Remember, the option automatic graphics switching selected always.

7 - Open Console.app, type into search: gfx0 and check if g-state changes if working!


(or you can to download the kext already edited, below)



2º MBP Mid 2010 GPU Fix, utility program:

The friend julian-poidevin, created an utility program called MBPMid2010_GPUFix, that allows to fix the kext, using the parameters above described.
The link to project is here : https://github.com/julian-poidevin/MBPMid2010_GPUFix
You can download it here : https://github.com/julian-poidevin/MBPMid2010_GPUFix/releases/latest

1 - Before, make sure these .kext are original (unmodified), and loaded (About this Mac -> System Report -> Software -> Extensions):
  • ACPI_SMC_PlatformPlugin.kext (IOPlatformPluginFamily.kext)
  • AppleGraphicsPowerManagement.kext
2 - Run fix.




Good luck. I hope this helps you
(sorry my bad english)



console.png


AppleGraphicsPowerManagement.kext 10.6.8
https://www.dropbox.com/s/cm12m6bww3rkbcm/10.6.8 AppleGraphicsPowerManagement.kext.zip?dl=0

AppleGraphicsPowerManagement.kext 10.9.5 (Thanks @user1690)
https://forums.macrumors.com/thread...ts-the-best-fix.1890097/page-10#post-24062932

https://www.dropbox.com/s/po0255ci7dax98o/10.9.5 AppleGraphicsPowerManagement.kext.zip?dl=0

AppleGraphicsPowerManagement.kext 10.10.5
https://www.dropbox.com/s/zvhluh27qcaqww6/10.10.5 AppleGraphicsPowerManagement.kext.zip?dl=0

AppleGraphicsPowerManagement.kext 10.11.6
https://www.dropbox.com/s/4er2qo84zu6lffd/AppleGraphicsPowerManagement.kext.zip?dl=0

AppleGraphicsPowerManagement.kext 10.12
https://www.dropbox.com/s/7esidh70l31h9i3/10.12.AppleGraphicsPowerManagement.kext.zip?dl=0

AppleGraphicsPowerManagement.kext 10.12.1
https://www.dropbox.com/s/mwu4fi84hl0h24l/10.12.1 AppleGraphicsPowerManagement.kext.zip?dl=0

AppleGraphicsPowerManagement.kext 10.12.2
https://www.dropbox.com/s/2k3kkdths8g928j/10.12.2 AppleGraphicsPowerManagement.kext.zip?dl=0

AppleGraphicsPowerManagement.kext 10.12.3
https://www.dropbox.com/s/32gub73afj4oaz2/10.12.3 AppleGraphicsPowerManagement.kext.zip?dl=0

AppleGraphicsPowerManagement.kext 10.12.4
https://www.dropbox.com/s/i50rvpbwqofpojh/10.12.4 AppleGraphicsPowerManagement.kext.zip?dl=0

AppleGraphicsPowerManagement.kext 10.12.5
https://www.dropbox.com/s/8ngc0c6d350u26a/10.12.5 AppleGraphicsPowerManagement.kext.zip?dl=0

AppleGraphicsPowerManagement.kext 10.12.6
https://www.dropbox.com/s/e9ed23z0eqyyci9/10.12.6 AppleGraphicsPowerManagement.kext.zip?dl=0

AppleGraphicsPowerManagement.kext 10.13 GM
https://www.dropbox.com/s/beoloqn8mx3elmt/10.13GM_ AppleGraphicsPowerManagement.kext.zip?dl=0

AppleGraphicsPowerManagement.kext 10.13
https://www.dropbox.com/s/l4zcbkfizabyqn5/10.13.AppleGraphicsPowerManagement.kext.zip?dl=0

AppleGraphicsPowerManagement.kext 10.13.2
https://www.dropbox.com/s/ay0wnnnzz1u5yzc/10.13.2 AppleGraphicsPowerManagement.kext.zip?dl=0


Bonus - Enable Night Shift:
https://www.dropbox.com/s/18kq9q8o55p0o1r/NightShift.rtf?dl=0


---------
Credits:
Special thanks for julian-poidevin for your work, really, this application was a good idea! We all appreciate it.
Click to expand...
 
OutSpoken said:
Oh crap, I applied the patch to my mbp several months ago and it was working like a charm then i updated to high sierra 10.13.6 today and now it's buggered up again!! keeps kernel panicking. Is there another working solution - reapplying the patch didn't work.
Click to expand...

Disable SIP.
Run the MBP Mid 2010 GPU Fix utility program;

Open terminal and type:
sudo bash
<enter password>
chown -R root:wheel /S*/L*/E*
chmod -R 755 /S*/L*/E*
kextcache -system-caches
kextcache -system-prelinked-kernel

Reboot
 
  • Like
Reactions: OutSpoken, Manu_5555 and Audit13
Hello Mac !

with my mid 2010

I've wrote all the scripts and patched the kernel, but when the mac is connected in HDMI with a external monitor, it still crashes.
 
Last edited:
fabioroberto said:
Disable SIP.
Run the MBP Mid 2010 GPU Fix utility program;

Open terminal and type:
sudo bash
<enter password>
chown -R root:wheel /S*/L*/E*
chmod -R 755 /S*/L*/E*
kextcache -system-caches
kextcache -system-prelinked-kernel

Reboot
Click to expand...
it doesn't work very greatfully, in a hdmi external monitoring mode the crash comes back.
 
fabioroberto said:
Disable SIP.
Run the MBP Mid 2010 GPU Fix utility program;

Open terminal and type:
sudo bash
<enter password>
chown -R root:wheel /S*/L*/E*
chmod -R 755 /S*/L*/E*
kextcache -system-caches
kextcache -system-prelinked-kernel

Reboot
Click to expand...
Hello!
First sorry for my bad english and thank you to your nice job.

I run he patch (SIP disabled) but it seems that not apply because the macbook crash and reboot.
I try the method of terminal but it says an error
'kext with invalid signature (-67030) allowed'

Any idea?

Thank you very much.

Edit: I try it again and not have error but when I reboot the screen have distorsions, pink lines, etc and loops rebooting... :(. This error is common on my macbook pro mid 2010.
I will try if rebooting a lot of times i can start the system and not crash.
 
Last edited:
EDESEC said:
Hello!
First sorry for my bad english and thank you to your nice job.

I run he patch (SIP disabled) but it seems that not apply because the macbook crash and reboot.
I try the method of terminal but it says an error
'kext with invalid signature (-67030) allowed'

Any idea?

Thank you very much.

Edit: I try it again and not have error but when I reboot the screen have distorsions, pink lines, etc and loops rebooting... :(. This error is common on my macbook pro mid 2010.
I will try if rebooting a lot of times i can start the system and not crash.
Click to expand...

For my part, I going to change the capacitor. Actually, it very simple to do. Problem : I do not know the name of the capacitor.
But for 40 $ it can be changed by a pro. I will change the HHD by SSD too, and this mac will be graduate!

Total= 100 $
 
  • Like
Reactions: EDESEC
jeremymacrumors said:
For my part, I going to change the capacitor. Actually, it very simple to do. Problem : I do not know the name of the capacitor.
But for 40 $ it can be changed by a pro. I will change the HHD by SSD too, and this mac will be graduate!

Total= 100 $
Click to expand...
Aluminum Polymer Capacitor: 330µF 2.5V, 20% tolerance, -55°C ~ 105°C, ESR
Do not use tantalum (the problem will return) or Ceramic MLCC. The correct is Aluminum Polymer Capacitor SMD
 
  • Like
Reactions: EDESEC
fabioroberto said:
Aluminum Polymer Capacitor: 330µF 2.5V, 20% tolerance, -55°C ~ 105°C, ESR
Do not use tantalum (the problem will return) or Ceramic MLCC. The correct is Aluminum Polymer Capacitor SMD
Click to expand...

Thank you for taking time out of your personal time to help us.
[doublepost=1533652836][/doublepost]
fabioroberto said:
Aluminum Polymer Capacitor: 330µF 2.5V, 20% tolerance, -55°C ~ 105°C, ESR
Do not use tantalum (the problem will return) or Ceramic MLCC. The correct is Aluminum Polymer Capacitor SMD
Click to expand...

Does this one work CAP ALU ELEC 330UF 2V SMD ?
 
  • Like
Reactions: Audit13 and fabioroberto
fabioroberto said:
Hi,

Well, after years i found a solution. I have the famous MacBook Pro 6,2 with GT330m (
0x0a29 model).

I discovered that this problem happens every time that g-state change between 2 to 0.

G-States go from 0 to 3, are related to the thresholds inside AppleGraphicsPowerManagement.kext, like this:

G-state 0 (maximum speed) and G-state 3 (lowest speed).

I solved the problem by keeping it always at G-State 2 (medium speed).

And the performance? Exemple: Cinebench, default (G-state 0) i've about 15fps, with g-state 2 (medium speed): 10fps.). Not bad.


If you want to try, these are the values changed in the info.plist:



<key>MacBookPro6,2</key>

<dict>

<key>LogControl</key>

<integer>1</integer>

<key>Vendor10deDevice0a29</key>

<dict>

<key>BoostPState</key>

<array>

<integer>2</integer>

<integer>2</integer>

<integer>2</integer>

<integer>2</integer>

</array>

<key>BoostTime</key>

<array>

<integer>2</integer>

<integer>2</integer>

<integer>2</integer>

<integer>2</integer>

</array>

<key>Heuristic</key>

<dict>

<key>ID</key>

<integer>0</integer>

<key>IdleInterval</key>

<integer>10</integer>

<key>SensorOption</key>

<integer>1</integer>

<key>SensorSampleRate</key>

<integer>10000</integer>

<key>TargetCount</key>

<integer>1</integer>

<key>Threshold_High</key>

<array>

<integer>0</integer>

<integer>0</integer>

<integer>100</integer>

<integer>200</integer>

</array>

<key>Threshold_High_v</key>

<array>

<integer>0</integer>

<integer>0</integer>

<integer>98</integer>

<integer>200</integer>

</array>

<key>Threshold_Low</key>

<array>

<integer>0</integer>

<integer>0</integer>

<integer>0</integer>

<integer>200</integer>

</array>

<key>Threshold_Low_v</key>

<array>

<integer>0</integer>

<integer>0</integer>

<integer>4</integer>

<integer>200</integer>

</array>

</dict>

<key>control-id</key>

<integer>17</integer>

</dict>



Perfect values? I do not know, but it is working for me.


Now, we have three methods to apply this fix:
1º Editing kext file and install manually;
2º Using the utility program called MBP Mid 2010 GPU Fix, that allows to fix the kext, using the parameters above described, automatically (credits [below] to julian-poidevin);
3º Hardware fix. Read the next posts pages to know about that. Credits to l.a.rossmann


1º Editing kext file and install manually:

Step by step:

1 - Make sure these .kext are original (unmodified), and loaded (About this Mac -> System Report -> Software -> Extensions):
  • ACPI_SMC_PlatformPlugin.kext (IOPlatformPluginFamily.kext)
  • AppleGraphicsPowerManagement.kext

2 - Disable SIP (boot into recovery mode, terminal: csrutil disable)
Avaliable only in OS X El Capitan or later. Previous OS X versions, jump to next step.

3 - Open Extensions folder (System/Library/Extensions), copy AppleGraphicsPowerManagement.kext to desktop (or other folder), open the info.plist into editor (I used the PlistEdit Pro.app), and change the values like writing up.

Attention: verify if your model is 0x0a29 really.

4 - Save info.plist, quit editor.

5 - Use Kext Drop.app to instal this kext, but before, delete the AppleGraphicsPowerManagement.kext into extensions folder.

6 - (This is important step) Leave the automatic graphics switching select (System Preferences - Energy Saver), if you are using gfxCardStatus.app, same thing!.

After, reboot normally.

Remember, the option automatic graphics switching selected always.

7 - Open Console.app, type into search: gfx0 and check if g-state changes if working!


(or you can to download the kext already edited, below)



2º MBP Mid 2010 GPU Fix, utility program:

The friend julian-poidevin, created an utility program called MBPMid2010_GPUFix, that allows to fix the kext, using the parameters above described.
The link to project is here : https://github.com/julian-poidevin/MBPMid2010_GPUFix
You can download it here : https://github.com/julian-poidevin/MBPMid2010_GPUFix/releases/latest

1 - Before, make sure these .kext are original (unmodified), and loaded (About this Mac -> System Report -> Software -> Extensions):
  • ACPI_SMC_PlatformPlugin.kext (IOPlatformPluginFamily.kext)
  • AppleGraphicsPowerManagement.kext
2 - Run fix.




Good luck. I hope this helps you
(sorry my bad english)



console.png


AppleGraphicsPowerManagement.kext 10.6.8
https://www.dropbox.com/s/cm12m6bww3rkbcm/10.6.8 AppleGraphicsPowerManagement.kext.zip?dl=0

AppleGraphicsPowerManagement.kext 10.9.5 (Thanks @user1690)
https://forums.macrumors.com/thread...ts-the-best-fix.1890097/page-10#post-24062932

https://www.dropbox.com/s/po0255ci7dax98o/10.9.5 AppleGraphicsPowerManagement.kext.zip?dl=0

AppleGraphicsPowerManagement.kext 10.10.5
https://www.dropbox.com/s/zvhluh27qcaqww6/10.10.5 AppleGraphicsPowerManagement.kext.zip?dl=0

AppleGraphicsPowerManagement.kext 10.11.6
https://www.dropbox.com/s/4er2qo84zu6lffd/AppleGraphicsPowerManagement.kext.zip?dl=0

AppleGraphicsPowerManagement.kext 10.12
https://www.dropbox.com/s/7esidh70l31h9i3/10.12.AppleGraphicsPowerManagement.kext.zip?dl=0

AppleGraphicsPowerManagement.kext 10.12.1
https://www.dropbox.com/s/mwu4fi84hl0h24l/10.12.1 AppleGraphicsPowerManagement.kext.zip?dl=0

AppleGraphicsPowerManagement.kext 10.12.2
https://www.dropbox.com/s/2k3kkdths8g928j/10.12.2 AppleGraphicsPowerManagement.kext.zip?dl=0

AppleGraphicsPowerManagement.kext 10.12.3
https://www.dropbox.com/s/32gub73afj4oaz2/10.12.3 AppleGraphicsPowerManagement.kext.zip?dl=0

AppleGraphicsPowerManagement.kext 10.12.4
https://www.dropbox.com/s/i50rvpbwqofpojh/10.12.4 AppleGraphicsPowerManagement.kext.zip?dl=0

AppleGraphicsPowerManagement.kext 10.12.5
https://www.dropbox.com/s/8ngc0c6d350u26a/10.12.5 AppleGraphicsPowerManagement.kext.zip?dl=0

AppleGraphicsPowerManagement.kext 10.12.6
https://www.dropbox.com/s/e9ed23z0eqyyci9/10.12.6 AppleGraphicsPowerManagement.kext.zip?dl=0

AppleGraphicsPowerManagement.kext 10.13 GM
https://www.dropbox.com/s/beoloqn8mx3elmt/10.13GM_ AppleGraphicsPowerManagement.kext.zip?dl=0

AppleGraphicsPowerManagement.kext 10.13
https://www.dropbox.com/s/l4zcbkfizabyqn5/10.13.AppleGraphicsPowerManagement.kext.zip?dl=0

AppleGraphicsPowerManagement.kext 10.13.2
https://www.dropbox.com/s/ay0wnnnzz1u5yzc/10.13.2 AppleGraphicsPowerManagement.kext.zip?dl=0


Bonus - Enable Night Shift:
https://www.dropbox.com/s/18kq9q8o55p0o1r/NightShift.rtf?dl=0


---------
Credits:
Special thanks for julian-poidevin for your work, really, this application was a good idea! We all appreciate it.
Click to expand...

I launched the MBP Mid 2010 GPU Fix program. I do not have a user password in my mac. The message I get is "Wrong password Try again". How can I solve this problem?
 

Attachments

  • upload_2018-8-27_16-2-12.png
    upload_2018-8-27_16-2-12.png
    520 KB · Views: 212
  • upload_2018-8-27_16-7-16.png
    upload_2018-8-27_16-7-16.png
    520 KB · Views: 225
Can anyone link to where the best kext fix is in this thread?

I looked around a bit but couldn't find it.

years ago I done the kext fix temporarily, until I replaced the capacitor but the replacement was also tantalum, so the problem is returning now.
 
Hi,

has anyone tested the MBPMid2010_GPUFix from julian-poidevin on macOS Mojave 10.14? Does it work?

thx
 
I have just stumbled upon this very useful thread, and I have an URGET issue....
My mid 2010 MacBook is sufffering the GPU reboot issue, so I have tried installing the gfxCardStatus app. Once installed, I mistakenly set it for GFX Only and now I am not able to boot in the Mac anymore! Anyone could pls help me in fixing this stupid thing I made? It should be enough to just enter in the desktop and change that setting! I have also tried in Safe mode, but it doesn't work: boot sequence just arrive to 50%, then I have the kernel panic.
Thank you for any suggestion, I am really in trouble.
 
fabioroberto said:
Hi,

...
1º Editing kext file and install manually:

Step by step:

1 - Make sure these .kext are original (unmodified), and loaded (About this Mac -> System Report -> Software -> Extensions):
  • ACPI_SMC_PlatformPlugin.kext (IOPlatformPluginFamily.kext)
  • AppleGraphicsPowerManagement.kext
...
Click to expand...

I have used this kext fix for almost a year now, and I barely have panic attacks anymore. Sometimes after an upgrade it happens again, because the kext file was brought back to original form. I have been able to replace it successfully again in the past.

But now the last few days I again have a lot of panic attacks. I thought, maybe the kext file has been replaced by the original; but no, I still have the modified kext file. BUT it is not loaded. I can't remember if this is normal or not. And I have no idea how to load it (so it says 'yes' loaded). And I can't do the whole process over, because (see above) I have the wrong kext file in place.

What can I do to solve my problem?
Also, I use gfx card status v1.8.1, "intel only" status, because it seemed to be helpful for the graphics card not to panic (until now recently). I'm not sure anymore whether to still use gfx or a specific version, or to just remove it all (and why). Only thing I know is that my macbook pro certainly still has a few years left of good use! ;D

Thanks in advance!
 
@lumineritiena
Don't user gfsxCardStatus WITH the kext fix. Remove gfxCardStatus.

For the kext not loading, open a terminal and type:

sudo chown -R root:wheel /S*/L*/E*;
sudo chmod -R 755 /S*/L*/E*;
sudo kextcache -i /

then reboot
 
  • Like
Reactions: fabioroberto
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back