This fix for sure uses the dedicated graphics and stops the laptop from using integrated graphics. You can use the Activity Monitor app to see which graphics card is being used, in the "Energy" tab selected at the top, and at the middle bottom, a box shows "Graphics Card" and states either High Perf. or integrated (high perf being the Nvidia Graphics). This laptop also almost always (i've never seen otherwise) uses the dedicated graphics in newer OS'es. Softwares like iMovie and Logic Pro X (which I too personally have seen far too much graphics usage from) will want to use the dedicated graphics.
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
This fix for sure uses the dedicated graphics and stops the laptop from using integrated graphics. You can use the Activity Monitor app to see which graphics card is being used, in the "Energy" tab selected at the top, and at the middle bottom, a box shows "Graphics Card" and states either High Perf. or integrated (high perf being the Nvidia Graphics). This laptop also almost always (i've never seen otherwise) uses the dedicated graphics in newer OS'es. Softwares like iMovie and Logic Pro X (which I too personally have seen far too much graphics usage from) will want to use the dedicated graphics.
Hi all,
Running 10.13.4 and had a few freezes/restarts recently. I've run the app a few times, to no avail. The app has been saving the day for a long time, but I seem to have lost some stability, and can't think of any major changes i've made to my MBP.
There is not even a crash log/report in the console, but I'm sure I saw one or two - they were incomplete.
Anyone else?
MBP 2010 15" Dual 2.53GHz i5 with the GT330M
Cheers!
Ed
Running 10.13.4 and had a few freezes/restarts recently. I've run the app a few times, to no avail. The app has been saving the day for a long time, but I seem to have lost some stability, and can't think of any major changes i've made to my MBP.
There is not even a crash log/report in the console, but I'm sure I saw one or two - they were incomplete.
Anyone else?
MBP 2010 15" Dual 2.53GHz i5 with the GT330M
Cheers!
Ed
Had the capacitor replaced around 1 year ago but after last OSX update the freezes are happening again. Any updates on this subject?
Before I had restarts and a crash message; now machine simply freezes and has to be manually rebooted.
Before I had restarts and a crash message; now machine simply freezes and has to be manually rebooted.
I think I have the same problem and feel like Apple crippled the machine on purpose. It apparently is not related to the capacitor since it's a complete freeze and was working properly on previous OSX.
Awaiting for some wise advice.
Hey there,
I have the same issue with an Macbook Pro 2k10 i5 and the Gt... .
I ve used a lot of methodes to bypass this.
But the best way that i figured out is to go back on Os El Capitan and installing the gfxCardStatus tool on the Version 1.8.1 <--- this is the only Version that really works.
But becareful some Programms need a newer Os like Sierra or High Sierra!!
I hope that this Post can help new Users.
Have any Problems ?
Just Dm me or send me an email to : germanjailbreakgroup@gmail.com
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):
2 - Run fix.
- ACPI_SMC_PlatformPlugin.kext (IOPlatformPluginFamily.kext)
- AppleGraphicsPowerManagement.kext
Good luck. I hope this helps you
(sorry my bad english)
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.
Hi
Thank for solution!
is work!, but
can i enable SIP later?
That's a NO! You can only enable SIP again after replacing the cap and eliminating the problem with GPU power management.
@julian-poidevin I disabled SIP and have been using your tool to a great success. Thank you and @fabioroberto for that.
Some questions:
- Does it work perfectly on the last OSX (High Sierra)? I just have to re-run the app after upgrade?
- If I'm using an external monitor, it will work but the possibility of crash just comes back as before, right?
Thanks again.
Some questions:
- Does it work perfectly on the last OSX (High Sierra)? I just have to re-run the app after upgrade?
- If I'm using an external monitor, it will work but the possibility of crash just comes back as before, right?
Thanks again.
Last edited:
- It's working for me. Yep, disable SIP again and run the app.
- Yep, external monitor + fix will probably crash as many have experienced. For an external monitor to work fine you should go with the cap replacement.
Bye!
Hello fabioroberto,
actually crashes appear even without the external monitor plugged in and even after some hours of usage (so, not only after a machine sleep). A couple of days ago i mounted the old HD again on my machine (my crashes started as soon i replaced the old HD with a new SSD one), worked for a couple of hours with no crashes. It's really sure there isn't any connection between the SSD and the GPU Kernel Panic or it's only a 'random' machine behavior?. Thanks again for all.
Hello,
The SSD or HDD is irrelevant. This is not the problem.
Is the SIP disabled and AGPM kext loaded?
Try to do all process again.
Good luck.
Hi, I'm trying to understand whether the problem I'm experiencing is the same...
I have a mid 2010 MacBook Pro 15", i7 8GB (A1286).
A couple of years ago it started crashing randomly: not the kernel panic screen, but just a black screen with three beeps. Sometimes after one week or more, other times just after few hours, with no special usage pattern.
After many attempts I discovered that the issue did NOT happen if I run my MacBook with only one RAM module (4GB) inside the slot which is farther from the keyboard (the upper slot, when you look at the MacBook opened upside down).
It does not matter which RAM module I use, so it's not a problem with RAM modules.
But all memory tests complete successfully even when I install both modules in both slots so the hardware seems to be fine.
I took it to repair (not at Apple, being now vintage), and the guys to my great surprise identified an issue with the video chip and - they say - they repaired it; indeed, the problem disappeared.
But after more or less one year the problem came back, exactly the same as the first time.
I took it to the same guys but they were clueless this time. They talked about EFI corruption due to communication issues between components but I ended up taking back my Mac without any fix.
Do you think my MacBook is affected by the issue described in this thread?
I tried running the small app by Julian but the issue was still there. I also inspected the modified plist file but as far as I could see the inserted values where somewhat different from the ones suggested by fabioroberto here.
Is the patch still working on High Sierra 10.13.4?
Thanks for any info.
Marco
I have a mid 2010 MacBook Pro 15", i7 8GB (A1286).
A couple of years ago it started crashing randomly: not the kernel panic screen, but just a black screen with three beeps. Sometimes after one week or more, other times just after few hours, with no special usage pattern.
After many attempts I discovered that the issue did NOT happen if I run my MacBook with only one RAM module (4GB) inside the slot which is farther from the keyboard (the upper slot, when you look at the MacBook opened upside down).
It does not matter which RAM module I use, so it's not a problem with RAM modules.
But all memory tests complete successfully even when I install both modules in both slots so the hardware seems to be fine.
I took it to repair (not at Apple, being now vintage), and the guys to my great surprise identified an issue with the video chip and - they say - they repaired it; indeed, the problem disappeared.
But after more or less one year the problem came back, exactly the same as the first time.
I took it to the same guys but they were clueless this time. They talked about EFI corruption due to communication issues between components but I ended up taking back my Mac without any fix.
Do you think my MacBook is affected by the issue described in this thread?
I tried running the small app by Julian but the issue was still there. I also inspected the modified plist file but as far as I could see the inserted values where somewhat different from the ones suggested by fabioroberto here.
Is the patch still working on High Sierra 10.13.4?
Thanks for any info.
Marco
So, if this fix is really useless in my case... what is the original plist file for 10.13.4? I launched the app more times so the first backup got lost
Thanks.
Maybe you have to install your High Sierra again to get the original plist file.So, if this fix is really useless in my case... what is the original plist file for 10.13.4? I launched the app more times so the first backup got lost
Thanks.
It would be enough if anyone running unpatched 10.13.4 sends me the file...Maybe you have to install your High Sierra again to get the original plist file.
Problem solved: High Sierra update 10.13.5 came out and replaced my patched file with a brand new unpatched one
Hi,
Thanks in advanced for your replies.
I have a MacBook Pro 2010 15" with the GPU kernel panic....
I also have a MacBook Pro 2007 15" motherboard 820-2101-A that I can use to harvest a cap.
Will any of these caps work to replace the faulty one on my 2010?
Thanks in advanced for your replies.
I have a MacBook Pro 2010 15" with the GPU kernel panic....
I also have a MacBook Pro 2007 15" motherboard 820-2101-A that I can use to harvest a cap.
Will any of these caps work to replace the faulty one on my 2010?
Last edited:
first pic, 330 e75, works but is tantalum model, in the future the problem will return.
Thank for your response. I went ahead and purchased the caps that you suggested. So far so good after I replaced them!
So I just was gifted a 2.8 2010 model with a 512 ssd and 8 gigs. Upgraded to HS. My question is, what do I need to do to make sure it doesn’t have this issue. I’m only using it for coffee shop writing, but I want it to be stable for that.
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.