Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
friend, where can i get information about my model is 0x0a29?
last question, this kext fix working with another graphic issues? like artefacts on this model?
About this mac -> System report->Graphics/display, select nvidia.
Artefacts can be many different things, like temperature or gpu reballing need.. I think that the kext will not fix this
 
Last edited:
  • Like
Reactions: rafarq
Hm what am I doing wrong? I have het macbook pro model with the same issue. I've disabled the security sip. Kext Drop says succesfully installed (AppleGraphicsPowerManagement.kext 10.12.2). After reboot my mac still crashes? Do i have to delete the applegraphicspowermanagement file manually from the extentions folder?
 
Which version? I read that the only version to properly disable the GPU is 2.2.1. The current version 2.3.

Were you able to successfully use this? I downloaded it and whenever it's running I get an alert that it can't switch modes 'with gfxcardstatus running'. That's a problem.
 
friend thanks on sierra OS X second macbook loaded this kext
Great! :)
[doublepost=1483996342][/doublepost]
Hm what am I doing wrong? I have het macbook pro model with the same issue. I've disabled the security sip. Kext Drop says succesfully installed (AppleGraphicsPowerManagement.kext 10.12.2). After reboot my mac still crashes? Do i have to delete the applegraphicspowermanagement file manually from the extentions folder?
Because the .kext was not loaded.
Download the edited .kext from first page (https://forums.macrumors.com/thread...010-whats-the-best-fix.1890097/#post-23312990);
Delete old kext from Extensions folder;
Using app like Kext Drop, install new edited kext;
Reboot;
Reset PRAM;
After, check if loaded (About this mac -> System report -> Software -> Extensions).
If loaded, test it.
 
Great! :)
[doublepost=1483996342][/doublepost]
Because the .kext was not loaded.
Download the edited .kext from first page (https://forums.macrumors.com/thread...010-whats-the-best-fix.1890097/#post-23312990);
Delete old kext from Extensions folder;
Using app like Kext Drop, install new edited kext;
Reboot;
Reset PRAM;
After, check if loaded (About this mac -> System report -> Software -> Extensions).
If loaded, test it.



Fabio u know any software fix about macbooks 2011 with graphic panic?
 
fabioroberto Thanks for your quick reply! And sorry for wasting your time. But I cannot figure out how to remove the current kext from the extensions folder. Do I have to do that in single user mode? Is it after that still possible to boot the mac?
 
fabioroberto Thanks for your quick reply! And sorry for wasting your time. But I cannot figure out how to remove the current kext from the extensions folder. Do I have to do that in single user mode? Is it after that still possible to boot the mac?
(first: have the sure that the SIP is disabled. If you dont know how to do, follow the steps below)

Create one bootable USB installer for macOS Sierra. Not for installing all system again but only to get in macOS Utilities and use the Terminal. (https://macdaddy.io/install-disk-creator/)
In the Terminal window, type in: csrutil disable and press Enter.

Restart your Mac.

Okay, now you are into macOS again.

Please, if possible, search and download a app called: Kext Drop.app or Kext Utility.app (Only to facilitate the process)
Go to Extensions folder, delete AppleGraphicsPowerManagement.kext.
Open Kext Drop (or Kext Utility) and drag .kext inside. Press install.
(download the kext here: https://forums.macrumors.com/thread...010-whats-the-best-fix.1890097/#post-23312990)

Reboot.

Into macOS again, check: About this Mac -> System report -> (Software) Extensions, if AppleGraphicsPowerManagement.kext was loaded. This is very important, just work if is loaded.. If not, check step by step and repeat all process again.
like this: https://dl.dropboxusercontent.com/u/35721057/loaded.png

if loaded, okay! Try your Mac. Cinebench app or normal use if is safe from GPU Panic.

Good luck.
 
Long shot .. but can anyone recommend a repair shop based in UK who would do this for a reasonable price?

Thanks
 
Hey everyone,
I'm not sure if anyone is even going to read this but I felt like I had to post what I did and it seemed to have worked. It does involve downloading the software mentioned above, but not only that. Again, it has been working up to now, a week or so of intense ProTools sessions (music recording) and other multitasking.

This is going to be a long post.

First of all, how it started: After realizing that some of the music production software could not run on Snow Leopard I migrated to Lion. A few weeks went by and then the random shutdowns started to happen. I don't recall doing anything different other than upgrading to Lion. On a desperate move I decided to downgrade back do Snow Leopard but it did nothing to the issue.

After watching some of Louis Rossmann's videos I decided to shoot him a message describing the issue, this was his reply: (it might sound harsh but Louis is actually an amazing dude, who's been assisting a bunch of people with Apple products related issues, look him up on Youtube)

+"japasetelagoas" Reballing is constantly being recommended by the dumbest of our industry, with no brain. Make sure to go back to those places where idiots suggest that and credit me with calling them an idiot. :) Replace C9560 with anything but a tantalum kind. Apple made the same mistake they made with the 820-2610 and 820-2330 where they ran out of space on the motherboard for C7771 so they made it a tantalum one. This is not suitable for a rail that is always on, as C7771 is for an S5 rail - so it dies. Voltage fluctuates, and eventually the machine stops turning on. On the 820-2850, that same 330uf tantalum capacitor re-appears on the framebuffer power supply for the GPU and the VRAM. The reballers without brains are heating this capacitor when they heat the board to remove the chip, so what happens is that they think they fixed it when the capacitor works again post heating! But it dies again when the cap F's up again. The proper repair is to replace C9560 with a non-tantalum one, which won't fit! You will have to scrape the board's ground pad to make this fit. It is doable.

Well, after realizing that I had to do some SMD soldering in order to try to fix it I took the fact that I'm into electronics (have a small lab at home) and decided to buy me a hot air rework station, crucial to swap the super tiny capacitor.

Months went by and I finally came up with enough courage to either ruin my 15 inch mid 2010 MBP or fix it, but before heating up the station I thought about the software mentioned above, the gfxcardstatus, why not give it a try, I'm screwed anyways.

Downloaded exactly as described on the post above, version 1.8.1. Installed it on my MBP running Mountain Lion by the time. After installing the computer failed 2 or 3 times in between both setups, NVIDIA and Intel's GPU. I had lost my faith by the time but after setting it once again to Intel's chipset it sort of stabilized. Three hours went by and no reboots, 5 hours, I then thought to myself, why not downgrade the OS back to Snow Leopard WHILE gfxcardstatus is set to Intel (isolating NVIDIA's chip).

That's exactly what I did, had to format the whole thing, wiped out my HD and after doing that I STILL HAVEN'T HAD ONE SINGLE REBOOT. Almost two weeks went by with constant Protools usage, Adobe Illustrator, Photoshop, not a single hiccup. And before you guys ask, we all know that the gfxcardstatus sort of shuts down NVIDIA's chipset, guess what? My MBP is running exactly on NVIDIA's chipset, the one which was told to be triggering the fault.

The image below points out that the computer is indeed running on it, it even has a Protools session open and the messsage with Louis Rossmann on the background:

31DLvGV.png


This is a message that I've sent to Louis explaining the things that I did:

"Louis, so something weird happened here. I haven't touched the logic board but for some reason my MBP returned to life. A day and a half have passed with extensive Pro Tools 8 sessions and not a single hiccup from the computer. I'm trying to identify any logical reason for it to be working but couldn't think of any, the best thing that I can do is share with you the things that I did prior to realizing that the computer seemed to return to an operational state. It happened on a very short time lapse so I'll just number things out:
1- Finally created the guts to take that cap off after receiving a reply from you 6 months ago.
2- Downloaded the schematic but couldn't find the damn component, sent you a message and received your reply, was confident on doing it.
3- Before actually heating up my hot air station I decided to give the "gfxcardstatus 1.8.1" software a shot, the one that lets you choose between NVIDIA's and Intel's.
4- By the time I had it installed my MBP was still running Mountain Lion (can't recall exactly what version). It did reboot a few times but then after switching back a few times between GPU's I selected the "Intel Only" option and the thing sort of stabilized.
5- A few hours went by and the Mac still hasn't rebooted, which was a relief to say the least. I then decided to downgrade the OS to the one that IMHO is the most stable for music production (Snow Leopard).
6- Did the whole thing, put the Install CD in, erased the hard drive, reformatted the whole thing. Just let me emphasize something, I did all of that whilst the "Intel Only" mode was still selected. I really can't tell you if this has any effect on the final product, if after wiping the HD the command to isolate GPU's simply reset thus ruling out any probability that this is linked to the problem being "solved".
7- Turned the Mac on, now with a fresh Snow Leopard version, installed all of my recording stuff back in, Protools 8, Waves Plugins, a bunch of VST's, still with the uncertainty that it would give me a kernel again.
8- Today 07/06, I decided to give the old Mac a shot on actual recording. Spent 3 hours recording a little project band which I'm in and it worked like a charm. Smooth, 3 different songs with 4 or 5 tracks, nothing major, the bass player didn't show up. But hey, it seems that the thing is back to life.
9- Here comes the intriguing part. I've just checked which processor is being used according to Apple's support website, and apparently, by the time I was writing this email, with a Protools session open, NVIDIA's GPU was running. Should I consider this a fix or should I get some Kleenex to wipe my tears out when this thing fails on me again? Maybe it's just plain luck that it hasn't "decided" to screw me over."

His reply was that he never saw me stating that I've replaced the capacitor, which I didn't.

I apologize for this huge post but I really had to share it, this is something that til now worked for me, I've never seen anyone mentioning that they downgraded their OS while running the gfx software, still I can't guarantee that's going to work considering that I couldn't come up with any logic explanation as to why I still didn't get any reboots, but hey, when I was desperate thinking that I had lost my pricey computer, the first thing that came on Google I was trying it.

Hope this somehow assists people with this particular issue.
[doublepost=1484146143][/doublepost]snow leopard is a stable operating system, my MBP 15 mid 2010 stated its GPU panic since i have upgraded from SL to mavericks. But after upgrading to El Capitan the panic was unbearable, it stats to restart itself in loops, then i decided to downgrade to snow leopard and i've used it for almost a year after that downgrade and the kernel panic disappeared. But this is not a long term solution cuz snow leopard is not supported anymore and lots of new software are not more compatible.
One day I've read about gfxcardstatus, i gave it a try, and it works fine, but sometime the kernel appear when you first restart or turn on the mac because the gfxcardstatus in not loaded yet, but anyway it works perfectly. You just have to uncheck hardware acceleration in the browser like chrome, or other app cuz they overwrite gfxcard.
I've heard about tantalum capacitor thing but i don't have the tools , to i did not try this method
 
Hi, lapinus

i'll try explain just a little bit better


I believe that you are using the latest combo 10.11.6, ok? If not, please install last combo (10.11.6). Why this? Because you said that you do not have good knowledge to edit system files. And.. so we are sure that the system is ok.


After, please, boot into Recovery Mode. How? Simple:

1 Reboot your Mac into Recovery Mode by restarting your computer and holding down Command+R until the Apple logo appears on your screen.

2 Click Utilities > Terminal.

3 In the Terminal window, type in: csrutil disable and press Enter.

4 Restart your Mac.


Ok, now you are into OSX again.

Please, if possible, search and download a app called: Kext Drop. (this is not marketing, okay?) Only to facilitate the process.



Download my AppleGraphicsPowerManagement.kext (already edited) here:
https://dl.dropboxusercontent.com/u/35721057/AppleGraphicsPowerManagement.kext.zip


Open Kext Drop and drag .kext inside. Press install.

Attention, this .kext only works if the system is upgraded to 10.11.6.

(But the “hack” manual in .plist can be done in other versions of OSX)



Reboot.


To check, open Console app (type in the spotlight), and search for: GFX0



Like this:
https://dl.dropboxusercontent.com/u/35721057/console.png




Test if this ok and free GPU Panic.



(Edited)
AppleGraphicsPowerManagement.kext 10.12
https://dl.dropboxusercontent.com/u/35721057/10.12.AppleGraphicsPowerManagement.kext.zip

I follow this instruction and it does SOLVE my problem. I was mad, upset at my macbook for a long time... After I found this post and tried this instruction, my macbook NEVER crash again. Thank you very very much.

Note that after complete this instruction I turn on the security - csrutil enable. Everything seems to be fine.

Thank you
 
  • Like
Reactions: fabioroberto
Just wanted to thank everyone for this thread.
I have a 2010 Mac Pro that had been sitting in a pile for a few years because of the video problem.
Once I saw LR's video showing which cap was at fault I promptly bought a replacement, swapped it out and that is all she wrote.
Great to have the 15 inch paper weight back in use.
DSmaC
 
Hi fabioroberto,

I had ordered this cap : panasonic EEFSX0E331ER

The parcel got lost in post and it's now out of stock, so could you please let me know which one will be ok (or not, and why) among these (spoiler).

Thank you very much.

 
Hi fabioroberto,

I had ordered this cap : panasonic EEFSX0E331ER

The parcel got lost in post and it's now out of stock, so could you please let me know which one will be ok (or not, and why) among these (spoiler).

Thank you very much.


All. :D
All these will work very well.
Personally I prefer EEFSX0E331XE, has a good combination of the voltage, ESR low...
 
I wouldn't remember where I originally heard it, but it was reiterated recently in a video by Louis Rossmann.


I have access to the Apple Video System Test for MacBook Pro (15-inch Mid 2010), so when my machine started to exhibit video issues, I ran the test. It failed within seconds.

I used a replacement 330uF 2.0v non-tantalum poly-film capacitor removed from a 13-inch MacBook Pro (Mid 2012) logic board with water damage. I keep spare boards around for small components and hard to find pieces. That said you can order them new as well from suppliers like RS, Element14 or Mouser, like so:

http://au.element14.com/panasonic-e...cx0d331r/cap-alu-elec-330uf-2v-smd/dp/2358262

After the capacitor was replaced, I re-ran the Apple Video System Test (VST) and it passed. The issue never reoccurred after that.

I did it. It works! Total coasts about $15. But I still have reboot issue when visit this page and wait for a while : https://bjango.com/mac/istatmenus/. But it reboots when I connect external monitor. So this fix is not 100% I guess?
 
  • Like
Reactions: mijail
I did it. It works! Total coasts about $15. But I still have reboot issue when visit this page and wait for a while : https://bjango.com/mac/istatmenus/. But it reboots when I connect external monitor. So this fix is not 100% I guess?
Something is wrong.
Did you test Cinebench? Ran successfully?
If not, or capacitor is not good (or recommended), bad soldering...
Try a SMC and PRAM reset, if not resolve, consider to revise the work.
 
Something is wrong.
Did you test Cinebench? Ran successfully?
If not, or capacitor is not good (or recommended), bad soldering...
Try a SMC and PRAM reset, if not resolve, consider to revise the work.
I ran Cinebench (MAXON Cinebench?) just now and got reboot issue again. The capacitor I used: CAP CER 330UF 2.5V X6S 1210 (https://www.digikey.com/products/en?keywords=587-3976-1-ND) as someone earlier here. I will reset SMC and PRAM hope it will help. Soldering was little bit askew but really little bit, may it be the reason? But funny thing is that I can use external monitor now and in general it works with no problems...
[doublepost=1484717633][/doublepost]Just reseted SMC & PRAM and it helped! Now Cinebench passed successfully! Thank you very much, fabioroberto!
 
I ran Cinebench (MAXON Cinebench?) just now and got reboot issue again. The capacitor I used: CAP CER 330UF 2.5V X6S 1210 (https://www.digikey.com/products/en?keywords=587-3976-1-ND) as someone earlier here. I will reset SMC and PRAM hope it will help. Soldering was little bit askew but really little bit, may it be the reason? But funny thing is that I can use external monitor now and in general it works with no problems...
[doublepost=1484717633][/doublepost]Just reseted SMC & PRAM and it helped! Now Cinebench passed successfully! Thank you very much, fabioroberto!
Yes! Great.:D

(just to clarify, a bad soldering point can be resistive. This happen for many causes, like the wrong temperature, the surface of the soldering iron is not free of contamination and from the oxide film that forms when the metal is exposed to air, although the surfaces to be soldered may look clean, there is always a thin film of oxide covering it. For a good solder bond, surface oxides must be removed during the soldering process using flux. And other things...)
 
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)



console.png


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

Hi there!

Questions...

My system isnt recognizing the revised kext. On a system running Sierra 10.12.2, I turned off SIL, removed the old AppleGraphicsPowerManagement kext. Used Kext Drop to do the install. Rebooted. My machine chimes. Hangs on the black screen with a moveable cursor.

I have to do a force power button restart. My Macbook Pro then restarts again (I assume to shut off the offending Kext file). Any advice?
[doublepost=1484760511][/doublepost]Strange. Just checked my Extensions. The Kext is loaded, but with a verification error. According to the console, the settings are correct. Im surprised because the restart wasn't exactly "clean"


Hi there!

Questions...

My system isnt recognizing the revised kext. On a system running Sierra 10.12.2, I turned off SIL, removed the old AppleGraphicsPowerManagement kext. Used Kext Drop to do the install. Rebooted. My machine chimes. Hangs on the black screen with a moveable cursor.

I have to do a force power button restart. My Macbook Pro then restarts again (I assume to shut off the offending Kext file). Any advice?
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.