Got a tip for us?
Let us know
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?
- Thread starter groverb
- Start date
- Sort by reaction score
Try creating a bootable USB installer for macOS Sierra. Not for installing all system again but only to get run the terminal.
try reset NVRAM (Command+Option+P+R), boot immediately into usb flash drive with macOS Sierra installer, disable SIP, reboot.
If this not working, really, I dont know why. Maybe, reinstall last combo can help.
I've been searching about this MBP mid 2010 problem for years. I have kind of control via gfx but it's very annoying because of the impossibility to use an external monitor. I tried to follow your instructions and had no success. I ended up reinstalling El Capitán. Now I'm trying to understand if your magnificent found can work with my MBP.
I have a 0x0a29 GT 330M and did not find AppleGraphicsPowerManagement.kext inside the extensions folder!
Besides that, I had a system extension warning when I rebooted saying:
"the system extension "/System/Library/Extensions/ATTOExpressRAID_Enabler.kext" was installed improperly and cannot be used. Please try reinstalling it, or contacted the product's vendor for an update."
Any ideas? Thanks so much!
guys..
i' m using el capitan, few days ago i updated something from App Store now the crash are back! why?? what can i do??
i' m using el capitan, few days ago i updated something from App Store now the crash are back! why?? what can i do??
check if SIP is disabled yet. Terminal: csrutil status
[doublepost=1485007145][/doublepost]
Something is wrong in your system. Consider install again the 10.11.6 combo.
Now, for the external monitor to work properly, it is required replace the capacitor c9560.
SIP is disabled. I don t know why but sometime happens that something goes wrong.. iTunes quit by itself or i ve got an heavy PDF(200mb), when i try to open it the machine fails and i ve got to reboot.. everything After that update..
Strange
. Try install the latest combo again and repeat all process to install de edited kext.Thanks..but, what do you mean with: latest combo??Strange
sorry, my fingers and iphone keyboard...is a disaster. The last combo, like the 10.12.3 (sierra) or 10.11.6(el capitan)
Last edited:
AppleGraphicsPowerManagement.kext 10.12.3 is available.
https://forums.macrumors.com/thread...010-whats-the-best-fix.1890097/#post-23312990
https://forums.macrumors.com/thread...010-whats-the-best-fix.1890097/#post-23312990
update: there was a system security update that was installed automatically on my 10.10.5, it must of replaced the kext.. after reboot, old problem back.. same kext replacement process done again, and voila, all works again with no reboots still waiting for my replacement capacitor "in postal transit"..
ohh.. and P.S. external monitor does NOT work, forces kernel panic and restart
still waiting for my replacement capacitor "in postal transit"..ohh.. and P.S. external monitor does NOT work, forces kernel panic and restart
Last edited:
Hi, Fabioroberto. i checked my files (info.plist) under mac os 10.6.8 and it is very different. Have you got the file for my system ? : ) Sorry for my english...i'm french.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.
Step by step:
1 - Verify that the file is the original and this loaded:
- 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!
Good luck. I hope this helps you
(sorry my bad english)
AppleGraphicsPowerManagement.kext 10.9.5 (Thanks @user1690)
https://forums.macrumors.com/thread...ts-the-best-fix.1890097/page-10#post-24062932
AppleGraphicsPowerManagement.kext 10.10.5
https://dl.dropboxusercontent.com/u/35721057/10.10.5 AppleGraphicsPowerManagement.kext.zip
AppleGraphicsPowerManagement.kext 10.11.6
https://dl.dropboxusercontent.com/u/35721057/AppleGraphicsPowerManagement.kext.zip
AppleGraphicsPowerManagement.kext 10.12
https://dl.dropboxusercontent.com/u/35721057/10.12.AppleGraphicsPowerManagement.kext.zip
AppleGraphicsPowerManagement.kext 10.12.1
https://dl.dropboxusercontent.com/u/35721057/10.12.1 AppleGraphicsPowerManagement.kext.zip
AppleGraphicsPowerManagement.kext 10.12.2
https://dl.dropboxusercontent.com/u/35721057/10.12.2 AppleGraphicsPowerManagement.kext.zip
AppleGraphicsPowerManagement.kext 10.12.3
https://dl.dropboxusercontent.com/u/35721057/10.12.3 AppleGraphicsPowerManagement.kext.zip
Thank you very much. I did what you say (Actually, i found the good lines to edit in infoplist) but when i use kext drop, the process was very long (you know, with the wheel). I get this in console :
24/01/2017 21:12:46 kernel AGPM: GPU = GFX0 Initialized, Control ID 17
24/01/2017 21:12:47 kernel AGPM: GPU = GFX0 G-state set to 3 from 3, ControlID = 17
24/01/2017 21:12:47 kernel AGPM: GPU = GFX0 G-state set to 2 from 3, ControlID = 17
24/01/2017 21:17:38 kernel AGPM: GPU = GFX0 Initialized, Control ID 17
24/01/2017 21:17:42 kernel AGPM: GPU = GFX0 G-state set to 3 from 3, ControlID = 17
24/01/2017 21:17:42 kernel AGPM: GPU = GFX0 G-state set to 2 from 3, ControlID = 17
24/01/2017 21:36:07 kernel AGPM: GPU = GFX0 Initialized, Control ID 17
24/01/2017 21:36:18 kernel AGPM: GPU = GFX0 G-state set to 3 from 3, ControlID = 17
24/01/2017 21:36:18 kernel AGPM: GPU = GFX0 G-state set to 2 from 3, ControlID = 17
24/01/2017 22:25:40 kernel AGPM: GPU = GFX0 Initialized, Control ID 17
24/01/2017 22:25:51 kernel AGPM: GPU = GFX0 G-state set to 3 from 3, ControlID = 17
24/01/2017 22:25:51 kernel AGPM: GPU = GFX0 G-state set to 2 from 3, ControlID = 17
24/01/2017 23:01:39 kernel AGPM: GPU = GFX0 Initialized, Control ID 17
24/01/2017 23:01:51 kernel AGPM: GPU = GFX0 G-state set to 3 from 3, ControlID = 17
24/01/2017 23:01:51 kernel AGPM: GPU = GFX0 G-state set to 2 from 3, ControlID = 17
24/01/2017 23:14:24 kernel AGPM: GPU = GFX0 Initialized, Control ID 17
24/01/2017 23:14:36 kernel AGPM: GPU = GFX0 G-state set to 3 from 3, ControlID = 17
24/01/2017 23:14:36 kernel AGPM: GPU = GFX0 G-state set to 2 from 3, ControlID = 17
I think it's okay, do you ?
Anyway i think my problem is different i crash only using Pro Tools with an external Display
and when i move windows in this display during audio playback....
24/01/2017 21:12:46 kernel AGPM: GPU = GFX0 Initialized, Control ID 17
24/01/2017 21:12:47 kernel AGPM: GPU = GFX0 G-state set to 3 from 3, ControlID = 17
24/01/2017 21:12:47 kernel AGPM: GPU = GFX0 G-state set to 2 from 3, ControlID = 17
24/01/2017 21:17:38 kernel AGPM: GPU = GFX0 Initialized, Control ID 17
24/01/2017 21:17:42 kernel AGPM: GPU = GFX0 G-state set to 3 from 3, ControlID = 17
24/01/2017 21:17:42 kernel AGPM: GPU = GFX0 G-state set to 2 from 3, ControlID = 17
24/01/2017 21:36:07 kernel AGPM: GPU = GFX0 Initialized, Control ID 17
24/01/2017 21:36:18 kernel AGPM: GPU = GFX0 G-state set to 3 from 3, ControlID = 17
24/01/2017 21:36:18 kernel AGPM: GPU = GFX0 G-state set to 2 from 3, ControlID = 17
24/01/2017 22:25:40 kernel AGPM: GPU = GFX0 Initialized, Control ID 17
24/01/2017 22:25:51 kernel AGPM: GPU = GFX0 G-state set to 3 from 3, ControlID = 17
24/01/2017 22:25:51 kernel AGPM: GPU = GFX0 G-state set to 2 from 3, ControlID = 17
24/01/2017 23:01:39 kernel AGPM: GPU = GFX0 Initialized, Control ID 17
24/01/2017 23:01:51 kernel AGPM: GPU = GFX0 G-state set to 3 from 3, ControlID = 17
24/01/2017 23:01:51 kernel AGPM: GPU = GFX0 G-state set to 2 from 3, ControlID = 17
24/01/2017 23:14:24 kernel AGPM: GPU = GFX0 Initialized, Control ID 17
24/01/2017 23:14:36 kernel AGPM: GPU = GFX0 G-state set to 3 from 3, ControlID = 17
24/01/2017 23:14:36 kernel AGPM: GPU = GFX0 G-state set to 2 from 3, ControlID = 17
I think it's okay, do you ?
Anyway i think my problem is different i crash only using Pro Tools with an external Display
and when i move windows in this display during audio playback....
Expected. For the external monitor to work properly, it is required replace the capacitor c9560.
Test using Cinebench app (disconnect external monitor). The gpu test should end successfully, and fps around 9 - 11.
If the KP happen into gpu test, try a PRAM reset and test again.
Hi Fabioroberto,
first of all, thanx for your great job solving the gfx-problem.
It has worked for me under 10.11.6… now I'm struggling. may you find time to help me?
I tried your method with the instruction you gave to lapinus POST #45.
This instruction was very easy since I just needed to install your hacked KEXT.
Sadly 10.11.6 was slowing down my machine a lot, so I switched back to 10.10.5 (14F2109).
I thought I use your KEXT-Mod for 10.10.5 in the same was as in Post #45 for El Captain and it should work – but it doesn't.
After the “fix“ Systeminfo/Extensions says now, that AppleGraphicPowerManagement is not loaded.
> Kext signature validation error code -67030
I do think apple changes something with a late security update. What do you think?
To solve the gfx-problem anyway, I would love to try a plist edit for my current OS X, if you can't offer a KEXT for the latest 10.10.5.
MY PROBLEM: I'm a absolute beginner in editing plist files.
1. I don't even get it straight, which file you are editing.A copy of the original AppleGraphicsPowerManagement.kext from the system, right?
2. If I'm right how to do that. I downloaded the plistEditPro, but the app is not able to open up the AppleGraphicsPowerManagement.kext , so something I do really wrong.
Could you explain the steps of modify the plist in a more simple way?
Cheers Ruwen
P.S: I also uploaded a copy of my original AppleGraphicsPowerManagement.kext ,may you can check if theres a difference to your posted file for 10.10.5
Okay Fabioroberto,
seems I'm not so much of an idiot. I found out, how to edit the .kext
(> just use the context menu on the kext and click > show content)
I put your values into the right spot of the info.plist – I think – but if I install the modified .kext and reboot, the system will not load the AppleGraphicsPowerManagement.kext
and still says > Kext signature validation error code -67030
How can I trick the system to sign up on the edited .kext?
Can someone help me? Does the newer version of 10.10.5 has SIP?
Cheers,
rubi
first of all, thanx for your great job solving the gfx-problem.
It has worked for me under 10.11.6… now I'm struggling. may you find time to help me?
I tried your method with the instruction you gave to lapinus POST #45.
This instruction was very easy since I just needed to install your hacked KEXT.
Sadly 10.11.6 was slowing down my machine a lot, so I switched back to 10.10.5 (14F2109).
I thought I use your KEXT-Mod for 10.10.5 in the same was as in Post #45 for El Captain and it should work – but it doesn't.
After the “fix“ Systeminfo/Extensions says now, that AppleGraphicPowerManagement is not loaded.
> Kext signature validation error code -67030
I do think apple changes something with a late security update. What do you think?
To solve the gfx-problem anyway, I would love to try a plist edit for my current OS X, if you can't offer a KEXT for the latest 10.10.5.
MY PROBLEM: I'm a absolute beginner in editing plist files.
1. I don't even get it straight, which file you are editing.A copy of the original AppleGraphicsPowerManagement.kext from the system, right?
2. If I'm right how to do that. I downloaded the plistEditPro, but the app is not able to open up the AppleGraphicsPowerManagement.kext , so something I do really wrong.
Could you explain the steps of modify the plist in a more simple way?
Cheers Ruwen
P.S: I also uploaded a copy of my original AppleGraphicsPowerManagement.kext ,may you can check if theres a difference to your posted file for 10.10.5
[doublepost=1485351642][/doublepost]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.
Step by step:
1 - Verify that the file is the original and this loaded:
- 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!
Good luck. I hope this helps you
(sorry my bad english)
AppleGraphicsPowerManagement.kext 10.6.8
https://dl.dropboxusercontent.com/u/35721057/10.6.8 AppleGraphicsPowerManagement.kext.zip
AppleGraphicsPowerManagement.kext 10.9.5 (Thanks @user1690)
https://forums.macrumors.com/thread...ts-the-best-fix.1890097/page-10#post-24062932
AppleGraphicsPowerManagement.kext 10.10.5
https://dl.dropboxusercontent.com/u/35721057/10.10.5 AppleGraphicsPowerManagement.kext.zip
AppleGraphicsPowerManagement.kext 10.11.6
https://dl.dropboxusercontent.com/u/35721057/AppleGraphicsPowerManagement.kext.zip
AppleGraphicsPowerManagement.kext 10.12
https://dl.dropboxusercontent.com/u/35721057/10.12.AppleGraphicsPowerManagement.kext.zip
AppleGraphicsPowerManagement.kext 10.12.1
https://dl.dropboxusercontent.com/u/35721057/10.12.1 AppleGraphicsPowerManagement.kext.zip
AppleGraphicsPowerManagement.kext 10.12.2
https://dl.dropboxusercontent.com/u/35721057/10.12.2 AppleGraphicsPowerManagement.kext.zip
AppleGraphicsPowerManagement.kext 10.12.3
https://dl.dropboxusercontent.com/u/35721057/10.12.3 AppleGraphicsPowerManagement.kext.zip
Okay Fabioroberto,
seems I'm not so much of an idiot. I found out, how to edit the .kext
(> just use the context menu on the kext and click > show content)
I put your values into the right spot of the info.plist – I think – but if I install the modified .kext and reboot, the system will not load the AppleGraphicsPowerManagement.kext
and still says > Kext signature validation error code -67030
How can I trick the system to sign up on the edited .kext?
Can someone help me? Does the newer version of 10.10.5 has SIP?
Cheers,
rubi
Okay, this is going to be a self teaching post.
I found out that Yosemite 10.10.5 got a kext signing that I have to switch of by typing
„sudo nvram boot-args=kext-dev-mode=1“ into the terminal.
Now the OS X Systeminfo > Software/Extension/ApplePowerManagement says:
loaded: YES and gives out a load adresse:18446743521858300000
but under loadable: it says NO
and under validation, it still says: Kext signature validation error code -67030
I think I have to try, if my system works now. I hope so.
I wanted to check it under the console-app but if I type in „gfx0“ nothing shows up. Why?
Cheers Rubi.
The test give me 10,36 fps.Expected. For the external monitor to work properly, it is required replace the capacitor c9560.
Test using Cinebench app (disconnect external monitor). The gpu test should end successfully, and fps around 9 - 11.
If the KP happen into gpu test, try a PRAM reset and test again.
I tried also WITH the external = Crash exactly expected.
So, i have to find somebody able to change my capacitor....
In Marseille France i think is difficult.
If someone know someone...
Thank you very very much for this admirable work.
Hi rubi,
Okay, I'll try help you.
Loaded: Yes
Loadable: No
Obtained from: Unknown
Signature Validation Errors: Kext signature validation error code -67030
is expected, no problem.
https://dl.dropboxusercontent.com/u/35721057/loaded.png
Well, how you posted that kext is loaded, test the system running Cinebench. If was succesfull the test will show fps around 9 - 11.
If fail happen, try this:
Download this edited kext (https://dl.dropboxusercontent.com/u/35721057/10.10.5(14F2109) AppleGraphicsPowerManagement.kext.zip)
Delete old kext from Extensions folder;
Using app like Kext Drop, install new edited kext;
Reboot;
Load into Safe Mode, log in into your account, wait the system to be loaded completely and turn off the macbook.
Turn on macbook, reset PRAM and SMC, load the OS X normally. This part is important.
After, check if loaded.
GFX0 into console, only if the LogControl key is changed to 1 in the .plist.
I hope I´ve helped
[doublepost=1485371733][/doublepost]
Great, working
.Sorry, really for use external monitor (100% working) only replacing the capacitor.
Last edited:
MacBook Pro 2010 here. Struggled with this for about a year using gfxcardstatus 1.8.1 which worked ok, but obviously only with the internal graphics card. Installed your kext and voila - everything works fine! Thank you very much. Apple should state this fix on their website if they would care about their customers. I missed the old replacement program for the GPU problem, because I as many others was not informed about it in the first place. I also wonder why a faulty component can not be repaired by Apple, even after this amount of time. This is not a normal failure because of advanced age, this is a design failure, so they should offer a fix for this for all these models and not for just two years. This would provide a lot of work for a lot of tech centers and would be an easy fix as well, if the parts just cost 2 dollars (in bulk probably more like 50 cents each).
At the very least they should have done the work that Fabio put in themselves or at least ackknowledge this on the page that states now, that the repair program is not available anymore.
At the very least they should have done the work that Fabio put in themselves or at least ackknowledge this on the page that states now, that the repair program is not available anymore.
fabioroberto, greetings from Russia!
Here's one more happy MacBookPro 2010 user thanks to you!
I appreciate so much the job you have done and still doing for all of us!
You saved me from spending EUR 4K+ for new MBP!
The way is really simple. I used Kext Utility App to update .kext
Thank you once again!
Here's one more happy MacBookPro 2010 user thanks to you!
I appreciate so much the job you have done and still doing for all of us!
You saved me from spending EUR 4K+ for new MBP!
The way is really simple. I used Kext Utility App to update .kext
Thank you once again!