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

groverb · Jun 6, 2015

Over the past several months I've been getting kernel panics due to the graphics card, resulting in my mid-2010 MBP crashing. It's been getting progressively worse, something several times a day. (I missed the recall/repair program by a week because the d*cks at Apple never notified me that such a program existed, and the Apple service rep wouldn't make an exception).

So, what can I do to stop this? I think I read somewhere that the dGPU can be disabled, but there is so much information out there that I don't want to try 20 different things before something works.

Here is the KP info:
*** Panic Report ***
panic(cpu 2 caller 0xffffff7f9386dbdb): "GPU Panic: [<None>] 5 3 7f 0 0 0 0 3 : NVRM[0/1:0:0]: Read Error 0x0061002c: CFG 0xffffffff 0xffffffff 0xffffffff, BAR0 0xd2000000 0xffffff812c90b000 0x0a5480a2, D0, P2/4\n"@/SourceCache/AppleGraphicsControl/AppleGraphicsControl-3.10.22/src/AppleMuxControl/kext/GPUPanic.cpp:127
Backtrace (CPU 2), Frame : Return Address
0xffffff811b92bae0 : 0xffffff8010b2bda1
0xffffff811b92bb60 : 0xffffff7f9386dbdb
0xffffff811b92bc40 : 0xffffff7f91787b9f
0xffffff811b92bd00 : 0xffffff7f9185118e
0xffffff811b92bd40 : 0xffffff7f91a2891c
0xffffff811b92bd60 : 0xffffff7f9182554b
0xffffff811b92bd80 : 0xffffff7f918c8a43
0xffffff811b92be00 : 0xffffff7f9176fc4e
0xffffff811b92bec0 : 0xffffff7f9173d845
0xffffff811b92bf00 : 0xffffff8010b5e759
0xffffff811b92bfb0 : 0xffffff8010c125b7
Kernel Extensions in backtrace:
com.apple.driver.AppleMuxControl(3.10.22)[xxxx]@0xffffff7f9385f000->0xffffff7f93872fff
dependency: com.apple.driver.AppleGraphicsControl(3.10.22)[xxxx]@0xffffff7f93857000
dependency: com.apple.iokit.IOACPIFamily(1.4)[70E2B65E-A91A-3522-A1A0-79FD63EABB4C]@0xffffff7f915a9000
dependency: com.apple.iokit.IOPCIFamily(2.9)[52E715FC-521D-3869-B2EA-5228FA4BEA34]@0xffffff7f91324000
dependency: com.apple.iokit.IOGraphicsFamily(2.4.1)[82EAD591-67E3-39CB-A232-A8095CA30E92]@0xffffff7f916e0000
dependency: com.apple.driver.AppleBacklightExpert(1.1.0)[65E3187E-949B-36E9-BA33-1B13ABB0581A]@0xffffff7f9385a000
com.apple.nvidia.classic.NVDAResmanTesla(10.0)[796AE430-39FB-3255-8161-D52AFA28EE2B]@0xffffff7f91737000->0xffffff7f919a0fff
dependency: com.apple.iokit.IOPCIFamily(2.9)[52E715FC-521D-3869-B2EA-5228FA4BEA34]@0xffffff7f91324000
dependency: com.apple.iokit.IONDRVSupport(2.4.1)[C0B8A85D-B32A-3F24-B4FC-B62B3BBF9E57]@0xffffff7f91727000
dependency: com.apple.iokit.IOGraphicsFamily(2.4.1)[82EAD591-67E3-39CB-A232-A8095CA30E92]@0xffffff7f916e0000
com.apple.nvidia.classic.NVDANV50HalTesla(10.0)[7FE40648-F15F-3E18-91E2-FDDDF4CDA355]@0xffffff7f919ab000->0xffffff7f91c54fff
dependency: com.apple.nvidia.classic.NVDAResmanTesla(10.0.0)[796AE430-39FB-3255-8161-D52AFA28EE2B]@0xffffff7f91737000
dependency: com.apple.iokit.IOPCIFamily(2.9)[52E715FC-521D-3869-B2EA-5228FA4BEA34]@0xffffff7f91324000

BSD process name corresponding to current thread: kernel_task
Boot args: kext-dev-mode=1 arch=x86_64

Mac OS version:
14D136

Kernel version:
Darwin Kernel Version 14.3.0: Mon Mar 23 11:59:05 PDT 2015; root:xnu-2782.20.48~5/RELEASE_X86_64
Kernel UUID: xxxxx
Kernel slide: 0x0000000010800000
Kernel text base: 0xffffff8010a00000
__HIB text base: 0xffffff8010900000
System model name: MacBookPro6,2 (Mac-F22586C8)

System uptime in nanoseconds: 23186455755273
last loaded kext at 23159494478675: com.apple.filesystems.msdosfs 1.10 (addr 0xffffff7f939c1000, size 69632)
last unloaded kext at 123634334859: com.apple.driver.AppleUSBUHCI 656.4.1 (addr 0xffffff7f91fe6000, size 65536)
loaded kexts:
org.virtualbox.kext.VBoxNetAdp 4.3.28
org.virtualbox.kext.VBoxNetFlt 4.3.28
org.virtualbox.kext.VBoxUSB 4.3.28
org.virtualbox.kext.VBoxDrv 4.3.28
com.LivestreamProcaster.driver.ProcasterAudioRedirector 2.0.0
com.apple.filesystems.msdosfs 1.10
com.apple.filesystems.autofs 3.0
com.apple.driver.AppleHWSensor 1.9.5d0
com.apple.driver.AGPM 110.19.5
com.apple.iokit.IOBluetoothSerialManager 4.3.4f4
com.apple.driver.AppleOSXWatchdog 1
com.apple.driver.AppleMikeyHIDDriver 124
com.apple.driver.AppleMikeyDriver 272.18
com.apple.driver.AppleHDA 272.18
com.apple.driver.AppleUpstreamUserClient 3.6.1
com.apple.GeForceTesla 10.0.0
com.apple.driver.AppleIntelHDGraphics 10.0.0
com.apple.driver.AppleIntelHDGraphicsFB 10.0.0
com.apple.driver.AppleLPC 1.7.3
com.apple.driver.AudioAUUC 1.70
com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport 4.3.4f4
com.apple.driver.AppleSMCPDRC 1.0.0
com.apple.driver.ACPI_SMC_PlatformPlugin 1.0.0
com.apple.driver.AppleMCCSControl 1.2.11
com.apple.driver.AppleSMCLMU 2.0.7d0
com.apple.driver.AppleMuxControl 3.10.22
com.apple.iokit.IOUserEthernet 1.0.1
com.apple.Dont_Steal_Mac_OS_X 7.0.0
com.apple.driver.AppleHWAccess 1
com.apple.driver.AppleHV 1
com.apple.driver.AppleIntelSlowAdaptiveClocking 4.0.0
com.apple.driver.SMCMotionSensor 3.0.4d1
com.apple.driver.AppleUSBTCButtons 240.2
com.apple.driver.AppleUSBTCKeyboard 240.2
com.apple.driver.AppleIRController 327.5
com.apple.driver.AppleUSBCardReader 3.5.5
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless 1.0.0d1
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1
com.apple.BootCache 36
com.apple.iokit.SCSITaskUserClient 3.7.5
com.apple.driver.XsanFilter 404
com.apple.iokit.IOAHCIBlockStorage 2.7.1
com.apple.driver.AirPort.Brcm4331 800.20.24
com.apple.driver.AppleFWOHCI 5.5.2
com.apple.driver.AppleUSBHub 705.4.2
com.apple.driver.AppleAHCIPort 3.1.2
com.apple.iokit.AppleBCM5701Ethernet 10.1.3
com.apple.driver.AppleUSBEHCI 705.4.14
com.apple.driver.AppleSmartBatteryManager 161.0.0
com.apple.driver.AppleACPIButtons 3.1
com.apple.driver.AppleRTC 2.0
com.apple.driver.AppleHPET 1.8
com.apple.driver.AppleSMBIOS 2.1
com.apple.driver.AppleACPIEC 3.1
com.apple.driver.AppleAPIC 1.7
com.apple.driver.AppleIntelCPUPowerManagementClient 218.0.0
com.apple.nke.applicationfirewall 161
com.apple.security.quarantine 3
com.apple.security.TMSafetyNet 8
com.apple.driver.AppleIntelCPUPowerManagement 218.0.0
com.apple.kext.triggers 1.0
com.apple.AppleGraphicsDeviceControl 3.10.22
com.apple.iokit.IOSerialFamily 11
com.apple.driver.DspFuncLib 272.18
com.apple.kext.OSvKernDSPLib 1.15
com.apple.nvidia.classic.NVDANV50HalTesla 10.0.0
com.apple.nvidia.classic.NVDAResmanTesla 10.0.0
com.apple.driver.AppleSMBusPCI 1.0.12d1
com.apple.iokit.IOBluetoothHostControllerUSBTransport 4.3.4f4
com.apple.iokit.IOUSBUserClient 705.4.0
com.apple.driver.IOPlatformPluginLegacy 1.0.0
com.apple.driver.IOPlatformPluginFamily 5.9.1d7
com.apple.driver.AppleSMBusController 1.0.13d1
com.apple.iokit.IOFireWireIP 2.2.6
com.apple.driver.AppleHDAController 272.18
com.apple.iokit.IOHDAFamily 272.18
com.apple.driver.AppleBacklightExpert 1.1.0
com.apple.iokit.IONDRVSupport 2.4.1
com.apple.driver.AppleGraphicsControl 3.10.22
com.apple.iokit.IOAudioFamily 203.3
com.apple.vecLib.kext 1.2.0
com.apple.iokit.IOSurface 97.4
com.apple.iokit.IOGraphicsFamily 2.4.1
com.apple.iokit.IOBluetoothFamily 4.3.4f4
com.apple.iokit.IOSlowAdaptiveClockingFamily 1.0.0
com.apple.driver.AppleSMC 3.1.9
com.apple.driver.AppleUSBMultitouch 245.2
com.apple.iokit.IOUSBHIDDriver 705.4.0
com.apple.iokit.IOSCSIBlockCommandsDevice 3.7.5
com.apple.iokit.IOUSBMassStorageClass 3.7.2
com.apple.driver.CoreStorage 471.20.7
com.apple.driver.AppleUSBMergeNub 705.4.0
com.apple.driver.AppleUSBComposite 705.4.9
com.apple.iokit.IOSCSIMultimediaCommandsDevice 3.7.5
com.apple.iokit.IOBDStorageFamily 1.7
com.apple.iokit.IODVDStorageFamily 1.7.1
com.apple.iokit.IOCDStorageFamily 1.7.1
com.apple.iokit.IOAHCISerialATAPI 2.6.1
com.apple.iokit.IOSCSIArchitectureModelFamily 3.7.5
com.apple.iokit.IO80211Family 730.60
com.apple.iokit.IOFireWireFamily 4.5.6
com.apple.iokit.IOAHCIFamily 2.7.5
com.apple.iokit.IOEthernetAVBController 1.0.3b3
com.apple.driver.mDNSOffloadUserClient 1.0.1b8
com.apple.iokit.IONetworkingFamily 3.2
com.apple.iokit.IOUSBFamily 720.4.4
com.apple.driver.AppleEFINVRAM 2.0
com.apple.driver.AppleEFIRuntime 2.0
com.apple.iokit.IOHIDFamily 2.0.0
com.apple.iokit.IOSMBusFamily 1.1
com.apple.security.sandbox 300.0
com.apple.kext.AppleMatch 1.0.0d1
com.apple.driver.AppleKeyStore 2
com.apple.driver.AppleMobileFileIntegrity 1.0.5
com.apple.driver.AppleCredentialManager 1.0
com.apple.driver.DiskImages 396
com.apple.iokit.IOStorageFamily 2.0
com.apple.iokit.IOReportFamily 31
com.apple.driver.AppleFDEKeyStore 28.30
com.apple.driver.AppleACPIPlatform 3.1
com.apple.iokit.IOPCIFamily 2.9
com.apple.iokit.IOACPIFamily 1.4
com.apple.kec.corecrypto 1.0
com.apple.kec.Libm 1
com.apple.kec.pthread 1
Model: MacBookPro6,2, BootROM MBP61.0057.B0F, 2 processors, Intel Core i7, 2.66 GHz, 8 GB, SMC 1.58f17
Graphics: Intel HD Graphics, Intel HD Graphics, Built-In
Graphics: NVIDIA GeForce GT 330M, NVIDIA GeForce GT 330M, PCIe, 512 MB
Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1067 MHz, 0x859B, 0x435435313236344243313036372E4D313646
Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1067 MHz, 0x859B, 0x435435313236344243313036372E4D313646
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x93), Broadcom BCM43xx 1.0 (5.106.98.100.24)
Bluetooth: Version 4.3.4f4 15601, 3 services, 18 devices, 1 incoming serial ports
Network Service: Ethernet, Ethernet, en0
Serial ATA Device: xxxx
Serial ATA Device: HL-DT-ST DVDRW GS23N
USB Device: Hub
USB Device: Apple Internal Keyboard / Trackpad
USB Device: Internal Memory Card Reader
USB Device: BRCM2070 Hub
USB Device: Bluetooth USB Host Controller
USB Device: Hub
USB Device: USB Receiver
USB Device: Built-in iSight
USB Device: IR Receiver
Thunderbolt Bus:

wnorris · Jun 7, 2015

groverb said:
Over the past several months I've been getting kernel panics due to the graphics card, resulting in my mid-2010 MBP crashing. It's been getting progressively worse, something several times a day. (I missed the recall/repair program by a week because the d*cks at Apple never notified me that such a program existed, and the Apple service rep wouldn't make an exception).

So, what can I do to stop this? I think I read somewhere that the dGPU can be disabled, but there is so much information out there that I don't want to try 20 different things before something works.

I have this system and the same problem. The only thing that has worked is to download the gfxCardStatus app at the link below.

https://gfx.io/

When you reboot your system select 'Integrated Only' to ensure that your discrete (Nvidia) graphics card does not get used. This should resolve the panics.

Note that you may need to adjust the settings in apps like your browser to ensure they don't have an option selected to use your discrete graphics (hardware acceleration or something similarly titled). If the option is selected it can override the gfxCardStatus setting.

This could slow down applications that are graphics intensive, but it is better than having the frequent reboots.

groverb · Jun 7, 2015

wnorris said:
I have this system and the same problem. The only thing that has worked is to download the gfxCardStatus app at the link below.

https://gfx.io/

Which version? I read that the only version to properly disable the GPU is 2.2.1. The current version 2.3.

wnorris · Jun 7, 2015

I am using v2.3 and have not noticed anything different over the last year.

As noted initially, you may need to disable hardware acceleration in apps like Google Chrome.

gordian · Jun 7, 2015

I had this same problem since back in 2011 and was able to get my logic board (and battery) completely replaced outside of the replacement program's eligibility period—literally two weeks ago.

My best advice is to call Apple and ask to speak with Customer Relations. Be courteous but persistent and you might be able to convince them to replace your logic board. Call them first and describe the issue. Mention that the discrete graphics chip is something you paid for and you just want the machine to work the way it was intended to work.

They may ask you to head to a Genius Bar to confirm that your machine would have been eligible for logic board replacement which I highly recommend you do, but make sure your Customer Relations rep will be available by phone during your Genius Bar appointment. You will want to ensure that the Genius runs a VST (Video Switching Test) to confirm the defect.

When I did this there were some other complications with my machine, but the Genius offered me Apple's flat rate repair option, which I believe is $310. That would basically involve sending it to the repair depot and they will fix any non-accidental issues they find, even if they're related to wear and tear (e.g., logic board, keyboard issues, battery, etc.).

I brought my machine in some time in 2012 about a battery malfunction and had mentioned the kernel panic issue back then, but the Genius never did anything about it. Luckily he noted it down so there was a record of the problem, which may have been my saving grace. Armed with that I actually managed to negotiate the flat rate repair directly with the store manager and he agreed to give me $150 off. I was about to send it off when my Customer Relations rep called me back. I told her what happened and she asked to speak with the Genius that was assisting me. When he gave me back the phone he just said, "Dude you're lucky, she's going to cover the repair." I ended up sending it out myself the next day (a Friday) in a box they overnighted to me and I received it back on a Wednesday. As I said, they replaced the logic board and the battery!

In the meantime you might try running the Cinebench diagnostic. I've heard that it should crash your machine if it is indeed one of those affected. I also definitely ran it when I received my repaired machine and it did not crash it!

Also check out this Apple Support Community thread: https://discussions.apple.com/thread/5311933

Best of luck!

nperei · Jun 20, 2015

hi
I had same issue on MBP Mid-2010. I just learned there was warranty expired that i didn't know. I took it Apple Store genius and I told them had MBP had been shutdown issue with GPU panic. He decided to take test graphic test and you can see big red label "Failed" He said that issue cover their warranty about discrete graphic for mid-2010. They going to replace whole board thank you I must had bad luck
first it was MBP 2007 graphic card then this MBP mid-2010 (kind threw me off I love Apple products)
I won't get them in next few days.
I'm wondering anyone who had their MBP mid 2010 logic board replaced by apple store. I'm wondering if your Mid-2010 persist the problem ? I'm little skeptical if the problem will repeat again after board replaced? it already happen to MBP 2007 (about (1 1/2 later)

gordian · Jun 20, 2015

gordian said:
In the meantime you might try running the Cinebench diagnostic. I've heard that it should crash your machine if it is indeed one of those affected. I also definitely ran it when I received my repaired machine and it did not crash it!

I had mine replaced and I ran the test mentioned above. It ran fine and it has not crashed after receiving it from the repair depot.

nperei · Jun 21, 2015

gordian said:
I had mine replaced and I ran the test mentioned above. It ran fine and it has not crashed after receiving it from the repair depot.

nperei · Jun 21, 2015

thks i got your msg above. I see you had almost nearly month now. that sound good but I'm wondering in long term ?? Good thing you brought up about Cinebench i did test before i brought to Genusis Bar.

Hope we can heard from other user who had their logic board replaced

Eithanius · Jun 22, 2015

Mid 2010 MBP 15" here... Had that problem last year, and AppleCare expired in 2013... Made some noise about the issue highlighted below, and they were quite reluctant but finally relented to replace it for free.

https://support.apple.com/en-us/HT203554

Unfortunately that program ended just 3 months ago...

gordian · Jun 22, 2015

nperei said:
thks i got your msg above. I see you had almost nearly month now. that sound good but I'm wondering in long term ??

No problems after a month. The defective logic board caused crashes multiple times daily.

Eithanius said:
Unfortunately that program ended just 3 months ago...

If you're courteous, persistent, and thorough like I was with Apple Customer Relations then you have a good chance of getting an extension on the eligibility period for a replacement as I mentioned above.

nperei · Jul 8, 2015

Got the Macbook pro back form Genesis Bar. it work well for 1 week 1/2 I ran Cinebench to test graphic open gl
it did not crash anymore. Guess it all good and hope it work well down the road

NHArq · Mar 4, 2016

Only way to fix Mac Book Pro 15 Mid 2010 by software is older

gfxCardStatus1.8.1(download site: https://software.com/mac/apps/gfxcardstatus/1.8.1 or whenever you find it)
don't try newer versions !!!! it will no work. Then install gfxCardStatus1.8.1. in menu check mark: Intel Only. in preferences, check mark:Load gfx.. at startup. and. Restore last used mode at startup
It will never shutdown but it will never use nvidia graphic card

nperei · Mar 25, 2016

NHArq have you bring MBP to Genesis Bar ? if you have not then it is worth try and let them do diagnostic. if GPU fail in the test Apple may be nice to extended old program to repair MBP 2010 for free. If they have part in their lab. My niece is happy Macbook pro working fine since last summer that Apple replaced board.

ron1004 · Mar 25, 2016

NHArq said:
Only way to fix Mac Book Pro 15 Mid 2010 by software is older

gfxCardStatus1.8.1(download site: https://software.com/mac/apps/gfxcardstatus/1.8.1 or whenever you find it)
don't try newer versions !!!! it will no work. Then install gfxCardStatus1.8.1. in menu check mark: Intel Only. in preferences, check mark:Load gfx.. at startup. and. Restore last used mode at startup
It will never shutdown but it will never use nvidia graphic card

Thanks for that.

I've been using gfxCardStatus for a long time, and all the time wanting the feature to always use Integrated GPU but couldn't find a fix.
Quite surprised that the developer removed this option from later versions.

Edit: Seems to be a bug with that version - when I close an app that would normally have switched graphics, as it closes the GPU status switches to "n".

chrfr · Mar 25, 2016

nperei said:
NHArq have you bring MBP to Genesis Bar ? if you have not then it is worth try and let them do diagnostic. if GPU fail in the test Apple may be nice to extended old program to repair MBP 2010 for free. If they have part in their lab. My niece is happy Macbook pro working fine since last summer that Apple replaced board.

Apple is no longer servicing the 2010 MacBook Pros at all, outside of California, as these computers are now considered "vintage".

AlainD. · May 25, 2016

chrfr said:
Apple is no longer servicing the 2010 MacBook Pros at all, outside of California, as these computers are now considered "vintage".

Hi I went to Genius Bar last week, and the assistant said that Apple does not provide any material for this model any more! :-( So even if they want to replace it for free, there will be no replacement piece available! The only solution which seems to be left with is to find 2nd hand logic boards (and checks with its serial number if it is defectuous or not), or live with it, or buy a newer MBP! :-/

japasetelagoas · Jul 14, 2016

NHArq said:
Only way to fix Mac Book Pro 15 Mid 2010 by software is older

gfxCardStatus1.8.1(download site: https://software.com/mac/apps/gfxcardstatus/1.8.1 or whenever you find it)
don't try newer versions !!!! it will no work. Then install gfxCardStatus1.8.1. in menu check mark: Intel Only. in preferences, check mark:Load gfx.. at startup. and. Restore last used mode at startup
It will never shutdown but it will never use nvidia graphic card

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:

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.

duervo · Jul 14, 2016

japasetelagoas said:
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.

*snipped*

I watch Louis' videos regularly. Subbed to his channel 3 years ago. They make me laugh (in a good way, not as an insult to him.) I just can't watch them when my little boy is awake, as he uses some pretty bad language in his videos, and I won't use a headset with a 4 year-old around (in case he needs me for anything ... ie: he hurts himself.)

Regarding your experience ... if your original issue was due to the crappy hardware/GPU, then I suspect that you're just lucky and it will fail again eventually.

fabioroberto · Sep 1, 2016

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 five methods to apply this fix:
1º Editing kext file and install manually;
2º Using my app MBP-2010-GPU-Panic-fix to apply the kext patch or remove it;
3º 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);
4º Using the bash script written by user btmm (credits below).
5º 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º Using my app MBP-2010-GPU-Panic-fix to apply the kext patch or remove it:
Project: https://github.com/fabioiop/MBP-2010-GPU-Panic-fix
Download it here: https://github.com/fabioiop/MBP-2010-GPU-Panic-fix/releases
Run.

(System Preferences and go to “Security & Privacy” and the “General” tab and allow it to run)
(Mac OSX 10.10 or later)

3º 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 - 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.

2 - 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

3 - Run fix.

4º Bash script:

The friend btmm, wrote a bash script to edits the AppleGraphicsPowerManagement.kext using the parameters above described. Simply, run the .sh at the terminal.

The link to project is here : https://gist.github.com/btmm/ede414c971aac71b78ff2c33f2dedbc1

1 - 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.

2 - 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

3 - Run bash script fix.

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

AlainD. · Sep 2, 2016

fabioroberto said:
(...)

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.
(...)

Hi, what happens if then in the future, you turn off automatic graphics switch ? What are the consequences on the system? (crash?, kernel error, gpu error?...?)
Thanks.

fabioroberto · Sep 2, 2016

AlainD. said:
Hi, what happens if then in the future, you turn off automatic graphics switch ? What are the consequences on the system? (crash?, kernel error, gpu error?...?)
Thanks.

Here nothing abnormal. Only, it is important to start with it in auto mode. Here is working well.

AlainD. · Sep 2, 2016

fabioroberto said:
Here nothing abnormal. Only, it is important to start with it in auto mode. Here is working well.

(ping-pong)

Yes but what happens if not?! You said it's important to keep the option checked, but you did not explain what happens if the option is not checked (temporary, or when reboot, long term, etc...). What happens if the option remains unchecked ? Is it important to just not experience the issue again? Or is it important because of a bigger failure?

Thank you in advance.

fabioroberto · Sep 2, 2016

AlainD. said:
(ping-pong)

Yes but what happens if not?! You said it's important to keep the option checked, but you did not explain what happens if the option is not checked (temporary, or when reboot, long term, etc...). What happens if the option remains unchecked ? Is it important to just not experience the issue again? Or is it important because of a bigger failure?

Thank you in advance.

Sorry, I did not make myself understood.
Are two different things:
First:
here, in my tests is important every boot must be in automatic mode. Discrete gpu only (automatic graphics switching unselected) not working properly, and, i don't know why. Maybe smc is responsible.

Second:
after osx loading i can change to discrete cpu only or in automatic graphics switching. No problem.
without crash or failure.

I think the problem may be in pgood signal. Maybe.

I'm weeks without problem using in this mode.

Thank you for your attention.

iMacC2D · Sep 2, 2016

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.

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

macrumors member

macrumors member

macrumors member

macrumors member

macrumors member

macrumors member

macrumors member

macrumors member

macrumors member

macrumors 68000

macrumors member

macrumors member

macrumors newbie

macrumors member

macrumors 6502

macrumors G5

macrumors newbie

macrumors newbie

macrumors 68020

macrumors regular

macrumors newbie

macrumors regular

macrumors newbie

macrumors regular

macrumors 6502a

Our Staff