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

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

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
Click to expand...

It's clear what the poster is trying to say is: load 1.8 and only 1.8 and your machine will not crash.

Well, I have had a radically different result. I have MacOS 10.11.6 (El Capitan) loaded, and when I tried this,
it rekt my mid-2010 Macbook Pro 15" (6,2) with nVidia GeForce 330M.

Previously, I had had 10.6.8 (Snow Leopard) loaded and religiously used 2.2.1, setting it to Intel Mode first thing upon a reboot. Didn't need to do anything at all if it was waking from Sleep mode. I -never- or -extremely rarely- (say every 6-9 months) had a graphics panic. For good measure, I stayed away from Flash games or anything super graphics intensive (eg VR simulations). Had a stable machine for about 5 years. So much so, that I'd almost forgotten that the machine had a problem at all.

Last week, I upgraded to 10.11.6 (El Capitan) and added a SSD. Love El Capitan. Hate the now-frequent reoccurrence of graphics crashes. 2.2.1 worked with 10.6.8, but does not work seamlessly with 10.11.6. I'm regularly finding things "I must not do" lest I incur a graphics panic (Eg, I just bought Little Snitch and can use it as long as I dont pull up the "network map").

Anyway, per this poster, I tried loading 1.8. ("Maybe 1.8 will be the solution that 2.2.1 was not.") Was a disaster. Initially, it loaded and was innocuous and seemed to work. Then, I thought to reboot it to test whether the graphics mode on shutdown was indeed retained on startup. So, I rebooted it. Without exception, it always crashed right after I hit ENTER upon entering my login information. To try to get back to a machine I could use at all, I rebooted in Safe Mode [hold down Cmd-R] and removed the app completely. It was deleted. And yet-- it still caused the instant crash upon login. 1.8 had altered my setup, for the worse, even though it was no longer on the machine! I was about to wipe the disk and start fresh and then I remembered: Resetting the NVRAM with Option-Cmd-P-R. That did the trick. No more instant crashes, but I was back to Square One.

TL;DR gfxCardStatus 1.8 may NOT be helpful and may be harmful to mid-2010 Macbook Pros loaded with 10.11 (El Capitan) that experience graphics panic. But if it does screw up your machine, removing it from Login Items, and resetting NVRAM will get you back to stability.
 
Hello Everybody.
Sorry for my bed english, i will try to do the best i can :)
I have the same troubles with the mid-2010 Macbook (El Capitan 10.11.6) I read carefully the tips by Fabioroberto and decided for the Polvedin software fix, by changing the .kext file. After a couple of days without noise macbook starts again crashing, in particular when i start use the MB after a quite long time. There are a couple of things I would like to point out: the GPU panics started only few months ago (i could not know how many people had troubles with the Nvidia Ge Force GT 330M) and - even if I'm not sure there is a connection - they started soon after i change the native HD with a new SSD one. First i want to thanks everybody for their efforts in order to solve the problem. On the other side I would like to know if there's something else i can do or if i made any mistake. Here is the last crash report and thanks a lot to everybody.

Anonymous UUID: 3AD4717F-16CA-7C42-55B3-10293BC72596

Thu Mar 15 09:57:23 2018

*** Panic Report ***
panic(cpu 0 caller 0xffffff7f98219bc9): "GPU Panic: [<None>] 3 3 7f 0 0 0 0 3 : NVRM[0/1:0:0]: Read Error 0x00000100: CFG 0xffffffff 0xffffffff 0xffffffff, BAR0 0xd2000000 0xffffff91315e7000 0x0a5480a2, D0, P2/4\n"@/Library/Caches/com.apple.xbs/Sources/AppleGraphicsControl/AppleGraphicsControl-3.12.9.1/src/AppleMuxControl/kext/GPUPanic.cpp:127
Backtrace (CPU 0), Frame : Return Address
0xffffff91206fb630 : 0xffffff80150dab52
0xffffff91206fb6b0 : 0xffffff7f98219bc9
0xffffff91206fb790 : 0xffffff7f95d7fa6a
0xffffff91206fb850 : 0xffffff7f95e4c9e8
0xffffff91206fb890 : 0xffffff7f95e4ca53
0xffffff91206fb910 : 0xffffff7f960cba85
0xffffff91206fba80 : 0xffffff7f95e6e711
0xffffff91206fbaa0 : 0xffffff7f95d867e0
0xffffff91206fbb50 : 0xffffff7f95d84150
0xffffff91206fbd50 : 0xffffff7f95d85382
0xffffff91206fbe30 : 0xffffff7f95d30de2
0xffffff91206fbe90 : 0xffffff7f981e6f91
0xffffff91206fbee0 : 0xffffff7f981e58a2
0xffffff91206fbf00 : 0xffffff801510f2ea
0xffffff91206fbfb0 : 0xffffff80151c95a7
Kernel Extensions in backtrace:
com.apple.driver.AppleMuxControl(3.12.9)[86AD8338-1D9E-397C-B870-C305C7C031FA]@0xffffff7f9820b000->0xffffff7f9821efff
dependency: com.apple.driver.AppleGraphicsControl(3.12.9)[0753AF3D-E850-3698-9F36-B22FDBA84803]@0xffffff7f98203000
dependency: com.apple.iokit.IOACPIFamily(1.4)[5D7574C3-8E90-3873-BAEB-D979FC215A7D]@0xffffff7f95bb3000
dependency: com.apple.iokit.IOPCIFamily(2.9)[6A2F4E4C-6CD1-3CA1-95C1-BB9864AC6D9A]@0xffffff7f9592c000
dependency: com.apple.iokit.IOGraphicsFamily(2.4.1)[A360453D-2050-3C49-A549-AC0DD5E87917]@0xffffff7f95cd7000
dependency: com.apple.driver.AppleBacklightExpert(1.1.0)[1D9D8FAB-EC84-330D-AB65-47DFB6C52A91]@0xffffff7f98206000
com.apple.nvidia.classic.NVDAResmanTesla(10.0)[78C84D68-23A9-3597-9AFC-E91B44E5A5B5]@0xffffff7f95d2e000->0xffffff7f95f99fff
dependency: com.apple.iokit.IOPCIFamily(2.9)[6A2F4E4C-6CD1-3CA1-95C1-BB9864AC6D9A]@0xffffff7f9592c000
dependency: com.apple.iokit.IONDRVSupport(2.4.1)[4EB2843C-C821-3AD0-B333-575FD6ED6FB1]@0xffffff7f95d1e000
dependency: com.apple.iokit.IOGraphicsFamily(2.4.1)[A360453D-2050-3C49-A549-AC0DD5E87917]@0xffffff7f95cd7000
com.apple.nvidia.classic.NVDANV50HalTesla(10.0)[07A95AE2-5869-3389-ACC8-A9675B47ACA4]@0xffffff7f95fa5000->0xffffff7f96250fff
dependency: com.apple.nvidia.classic.NVDAResmanTesla(10.0.0)[78C84D68-23A9-3597-9AFC-E91B44E5A5B5]@0xffffff7f95d2e000
dependency: com.apple.iokit.IOPCIFamily(2.9)[6A2F4E4C-6CD1-3CA1-95C1-BB9864AC6D9A]@0xffffff7f9592c000
com.apple.driver.AGPM(110.22)[D2A6476D-895C-33EE-8A84-7548FA9B5748]@0xffffff7f981e3000->0xffffff7f981f9fff
dependency: com.apple.iokit.IOPCIFamily(2.9)[6A2F4E4C-6CD1-3CA1-95C1-BB9864AC6D9A]@0xffffff7f9592c000
dependency: com.apple.driver.IOPlatformPluginFamily(6.0.0d7)[4BEF649C-7CFD-31CA-8D84-1F0DB25BF60B]@0xffffff7f968e9000
dependency: com.apple.iokit.IONDRVSupport(2.4.1)[4EB2843C-C821-3AD0-B333-575FD6ED6FB1]@0xffffff7f95d1e000
dependency: com.apple.iokit.IOGraphicsFamily(2.4.1)[A360453D-2050-3C49-A549-AC0DD5E87917]@0xffffff7f95cd7000
dependency: com.apple.AppleGraphicsDeviceControl(3.12.9)[21580824-E82E-371E-8FEE-B213B71B5C58]@0xffffff7f981dc000

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

Mac OS version:
15G17023

Kernel version:
Darwin Kernel Version 15.6.0: Mon Oct 2 22:20:08 PDT 2017; root:xnu-3248.71.4~1/RELEASE_X86_64
Kernel UUID: C132D1DA-3C39-3F1F-A265-219352AC3C9D
Kernel slide: 0x0000000014e00000
Kernel text base: 0xffffff8015000000
__HIB text base: 0xffffff8014f00000
System model name: MacBookPro6,2 (Mac-F22586C8)

System uptime in nanoseconds: 1205631531841
last loaded kext at 121349725814: com.apple.filesystems.smbfs 3.0.1 (addr 0xffffff7f9830a000, size 409600)
loaded kexts:
com.apple.filesystems.smbfs 3.0.1
com.apple.driver.AudioAUUC 1.70
com.apple.filesystems.autofs 3.0
com.apple.driver.AppleHWSensor 1.9.5d0
com.apple.driver.AppleTyMCEDriver 1.0.2d2
com.apple.driver.AGPM 110.22.0
com.apple.driver.AppleOSXWatchdog 1
com.apple.driver.AppleMikeyHIDDriver 124
com.apple.driver.AppleMikeyDriver 274.12
com.apple.driver.pmtelemetry 1
com.apple.driver.AppleUpstreamUserClient 3.6.1
com.apple.iokit.IOUserEthernet 1.0.1
com.apple.driver.AppleHDAHardwareConfigDriver 274.12
com.apple.GeForceTesla 10.0.0
com.apple.driver.AppleHDA 274.12
com.apple.driver.AppleIntelHDGraphics 10.0.0
com.apple.iokit.IOBluetoothSerialManager 4.4.6f2
com.apple.driver.AppleBacklight 170.8.9
com.apple.Dont_Steal_Mac_OS_X 7.0.0
com.apple.driver.AppleHV 1
com.apple.driver.AppleMCCSControl 1.2.13
com.apple.driver.AppleMuxControl 3.12.9
com.apple.driver.ACPI_SMC_PlatformPlugin 1.0.0
com.apple.driver.AppleIntelHDGraphicsFB 10.0.0
com.apple.nvidia.NVDAStartup 10.1.0
com.apple.driver.AppleIntelSlowAdaptiveClocking 4.0.0
com.apple.driver.AppleFIVRDriver 4.1.0
com.apple.driver.AppleSMCPDRC 1.0.0
com.apple.driver.AppleLPC 3.1
com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport 4.4.6f2
com.apple.driver.AppleSMCLMU 208
com.apple.driver.SMCMotionSensor 3.0.4d1
com.apple.driver.AppleUSBTCButtons 245.4
com.apple.iokit.IOBluetoothUSBDFU 4.4.6f2
com.apple.driver.AppleUSBDisplays 378
com.apple.driver.AppleUSBStorageCoexistentDriver 3.7.1
com.apple.driver.AppleUSBCardReader 3.7.1
com.apple.driver.AppleIRController 327.6
com.apple.driver.AppleUSBTCKeyEventDriver 245.4
com.apple.driver.AppleUSBTCKeyboard 245.4
com.apple.driver.CoreStorageFsck 517.50.1
com.apple.driver.AppleFileSystemDriver 3.0.1
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless 1.0.0d1
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0
com.apple.BootCache 38
com.apple.iokit.SCSITaskUserClient 3.7.7
com.apple.iokit.IOAHCIBlockStorage 2.8.5
com.apple.driver.AppleFWOHCI 5.5.4
com.apple.driver.AirPort.Brcm4331 800.21.28
com.apple.driver.AirPort.Brcm4360 1041.1.1a2
com.apple.driver.AppleAHCIPort 3.1.8
com.apple.iokit.AppleBCM5701Ethernet 10.2.0
com.apple.driver.usb.AppleUSBEHCIPCI 1.0.1
com.apple.driver.usb.AppleUSBUHCIPCI 1.0.1
com.apple.driver.AppleSmartBatteryManager 161.0.0
com.apple.driver.AppleRTC 2.0
com.apple.driver.AppleACPIButtons 4.0
com.apple.driver.AppleHPET 1.8
com.apple.driver.AppleSMBIOS 2.1
com.apple.driver.AppleACPIEC 4.0
com.apple.driver.AppleAPIC 1.7
com.apple.driver.AppleIntelCPUPowerManagementClient 218.0.0
com.apple.nke.applicationfirewall 163
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.12.9
com.apple.iokit.IOSurface 108.2.4
com.apple.nvidia.classic.NVDANV50HalTesla 10.0.0
com.apple.nvidia.classic.NVDAResmanTesla 10.0.0
com.apple.driver.DspFuncLib 274.12
com.apple.kext.OSvKernDSPLib 525
com.apple.iokit.IOSerialFamily 11
com.apple.driver.CoreCaptureResponder 1
com.apple.driver.AppleSMBusController 1.0.14d1
com.apple.iokit.IOFireWireIP 2.2.6
com.apple.driver.AppleBacklightExpert 1.1.0
com.apple.iokit.IONDRVSupport 2.4.1
com.apple.driver.AppleGraphicsControl 3.12.9
com.apple.driver.IOPlatformPluginLegacy 1.0.0
com.apple.iokit.IOSlowAdaptiveClockingFamily 1.0.0
com.apple.driver.AppleHDAController 274.12
com.apple.iokit.IOHDAFamily 274.12
com.apple.iokit.IOAudioFamily 204.4
com.apple.vecLib.kext 1.2.0
com.apple.driver.AppleSMBusPCI 1.0.14d1
com.apple.driver.IOPlatformPluginFamily 6.0.0d7
com.apple.iokit.IOBluetoothHostControllerUSBTransport 4.4.6f2
com.apple.iokit.IOBluetoothFamily 4.4.6f2
com.apple.iokit.IOGraphicsFamily 2.4.1
com.apple.driver.AppleSMC 3.1.9
com.apple.driver.AppleHIDKeyboard 181
com.apple.driver.usb.IOUSBHostHIDDevice 1.0.1
com.apple.driver.AppleUSBComposite 900.4.1
com.apple.iokit.IOUSBHIDDriverPM 900.4.1
com.apple.iokit.IOUSBMassStorageClass 4.0.2
com.apple.iokit.IOSCSIBlockCommandsDevice 3.7.7
com.apple.iokit.IOUSBMassStorageDriver 1.0.0
com.apple.driver.AppleUSBMultitouch 250.5
com.apple.iokit.IOUSBHIDDriver 900.4.1
com.apple.driver.usb.cdc 5.0.0
com.apple.driver.usb.networking 5.0.0
com.apple.driver.usb.AppleUSBHostCompositeDevice 1.0.1
com.apple.driver.CoreStorage 517.50.1
com.apple.driver.usb.AppleUSBHub 1.0.1
com.apple.iokit.IOSCSIMultimediaCommandsDevice 3.7.7
com.apple.iokit.IOBDStorageFamily 1.8
com.apple.iokit.IODVDStorageFamily 1.8
com.apple.iokit.IOCDStorageFamily 1.8
com.apple.driver.AppleXsanScheme 3
com.apple.iokit.IOAHCISerialATAPI 2.6.2
com.apple.iokit.IOSCSIArchitectureModelFamily 3.7.7
com.apple.driver.AppleUSBMergeNub 900.4.1
com.apple.iokit.IOFireWireFamily 4.6.1
com.apple.iokit.IO80211Family 1110.26
com.apple.driver.corecapture 1.0.4
com.apple.iokit.IOAHCIFamily 2.8.1
com.apple.iokit.IOEthernetAVBController 1.0.3b3
com.apple.driver.mDNSOffloadUserClient 1.0.1b8
com.apple.iokit.IONetworkingFamily 3.2
com.apple.iokit.IOUSBFamily 900.4.1
com.apple.driver.usb.AppleUSBUHCI 1.0.1
com.apple.driver.usb.AppleUSBEHCI 1.0.1
com.apple.iokit.IOUSBHostFamily 1.0.1
com.apple.driver.AppleUSBHostMergeProperties 1.0.1
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 417.4
com.apple.iokit.IOStorageFamily 2.1
com.apple.iokit.IOReportFamily 31
com.apple.driver.AppleFDEKeyStore 28.30
com.apple.driver.AppleACPIPlatform 4.0
com.apple.iokit.IOPCIFamily 2.9
com.apple.iokit.IOACPIFamily 1.4
com.apple.kec.Libm 1
com.apple.kec.pthread 1
com.apple.kec.corecrypto 1.0
Model: MacBookPro6,2, BootROM MBP61.005A.B00, 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, 0x855D, 0xFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1067 MHz, 0x855D, 0xFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x93), Broadcom BCM43xx 1.0 (5.106.98.101.28)
Bluetooth: Version 4.4.6f2, 3 services, 19 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en1
Serial ATA Device: Crucial_CT525MX300SSD1, 525,11 GB
Serial ATA Device: MATSHITADVD-R UJ-898
USB Device: USB 2.0 Bus
USB Device: Hub
USB Device: Hub
USB Device: Keyboard Hub
USB Device: Composite Device
USB Device: Apple Keyboard
USB Device: Apple Cinema Display
USB Device: IR Receiver
USB Device: Built-in iSight
USB Device: USB 2.0 Bus
USB Device: Hub
USB Device: Card Reader
USB Device: Apple Internal Keyboard / Trackpad
USB Device: BRCM2070 Hub
USB Device: Bluetooth USB Host Controller
Thunderbolt Bus:
 
Hi I have the dreaded 2010 MBP restarting issue. This is usually when I’m using iMovie. I bought my MacBook to do videos on!!! I want to try the GPU fix but I need to know if iMovie will still be usable after changing the kext file?? Also I’m finding it hard to understand. Does the GPU fix turn off the integrated graphics or does it just change the “G state” whatever that is? Or are they the same thing?
 
tronlady said:
Hi I have the dreaded 2010 MBP restarting issue. This is usually when I’m using iMovie. I bought my MacBook to do videos on!!! I want to try the GPU fix but I need to know if iMovie will still be usable after changing the kext file?? Also I’m finding it hard to understand. Does the GPU fix turn off the integrated graphics or does it just change the “G state” whatever that is? Or are they the same thing?
Click to expand...
My crashes were specially related to imovie. After the GPU fix I used Imovie for a while without crashes. They appeared without any apparently reason in other circumstances: using Chrome, working on the Finder, etc. On the other question, i think the GPU fix only concern a change in the G state. I hope to receive more details from Senjor User :)
 
Thanks a lot fabioroberto! After the GPU fix i still have crashes. As I told, it happen in vary circumstances without a particular reason. More frequently when i start to work, but i can't be more detailed. Any idea?
 
Elia68 said:
Thanks a lot fabioroberto! After the GPU fix i still have crashes. As I told, it happen in vary circumstances without a particular reason. More frequently when i start to work, but i can't be more detailed. Any idea?
Click to expand...
Check if csrutil is disabled. (Terminal: type -> csrutil status).
Did you test using Cinebench? Completed successfully and with fps around 10?
Are you using external monitor? When one monitor external is connected the KP is expected. Wake up after sleep also (sometimes).

I hope I´ve helped.
 
fabioroberto said:
Check if csrutil is disabled. (Terminal: type -> csrutil status).
Did you test using Cinebench? Completed successfully and with fps around 10?
Are you using external monitor? When one monitor external is connected the KP is expected. Wake up after sleep also (sometimes).

I hope I´ve helped.
Click to expand...
Hello Fabioroberto. Csrutil is actually disabled. I did a Cinebench test with a crash, but i had an external monitor connected. I will do the test without and see.
[doublepost=1521451742][/doublepost]
Elia68 said:
Hello Fabioroberto. Csrutil is actually disabled. I did a Cinebench test with a crash, but i had an external monitor connected. I will do the test without and see.
Click to expand...
The Cinebench test without the external monitor was successfully. The score was 10.55. It means that when I have the external monitor connected I can't avoid the Panic?
 
Elia68 said:
Hello Fabioroberto. Csrutil is actually disabled. I did a Cinebench test with a crash, but i had an external monitor connected. I will do the test without and see.
[doublepost=1521451742][/doublepost]
The Cinebench test without the external monitor was successfully. The score was 10.55. It means that when I have the external monitor connected I can't avoid the Panic?
Click to expand...
Hello
To use the external monitor it is necessary to replace the capacitor.
 
tronlady said:
Hiya newtonuk. Did you find a repairer in Leeds? I am looking for 1 in Yorkshire. Spoken to 3 in South Yorkshire who told me to "get shut of it". It seems 1 of them can do the capacitor repair but says it won't last....thing is I'd rather pay for the repair than £800 plus for another used mbp!!! Also I can't be arsed with all the file transfers or hard drive transfer to another MBP!!!
Click to expand...

Hi, not in Leeds. One in Cambridge seemed quite reasonable, but I haven't taken him up on it as mine is now showing another fault where the white parts of the screen look pink and the black parts green :-(

www.2ndchancepc.co.uk
 
@fabioroberto You say that the secondary display issue is due to the Nvidia EFI Driver, and as I don't know much more, I will take your word for it, but my MacBook does stay reasonably alive whilst running a second display at 1920X1080, but it crashes when I open up things like Ableton Live 10 or Logic Pro X, and also @janbrubel previously mentioned that his cinema display worked, so just to clear my mind please, is there no other way to fix the second display issue without a replacement capacitor and is it just hit and miss with different laptops for second displays? Thank you very much for the fix too, pulled yet another laptop out of the dump as reported in this thread.
 
MyLaptopStoppedWorking said:
@fabioroberto You say that the secondary display issue is due to the Nvidia EFI Driver, and as I don't know much more, I will take your word for it, but my MacBook does stay reasonably alive whilst running a second display at 1920X1080, but it crashes when I open up things like Ableton Live 10 or Logic Pro X, and also @janbrubel previously mentioned that his cinema display worked, so just to clear my mind please, is there no other way to fix the second display issue without a replacement capacitor and is it just hit and miss with different laptops for second displays? Thank you very much for the fix too, pulled yet another laptop out of the dump as reported in this thread.
Click to expand...
Cause the capacitor degradation is relevant. To work correctly, it is necessary to replace the capacitor.
 
fabioroberto said:
Cause the capacitor degradation is relevant. To work correctly, it is necessary to replace the capacitor.
Click to expand...
Ok, that's fine, but I watch the console while I use both displays and what I see is that when I wake the laptop when it is connected this triggers the crash, and sometimes there are no updates on GFX0 but everything runs smoothly, and I've even played CSGO on the 1920X1080 display with both displays on and it works most of the time but has random crashes. Sometimes when I just watch the console GFX0 updates every second for a minute then stops. It is very random to me and I don't know much, so is there a way I can find out or learn how to edit AGPM.kext info.plist to suit my laptop like to change state on wake from sleep?
 
My questions remain unanswered?? Will iMovie will still be usable after changing the kext file?? Also I’m finding it hard to understand. Does the GPU fix turn off the integrated graphics or does it just change the “G state” whatever that is? Or are they the same thing?
[doublepost=1522956128][/doublepost]
Elia68 said:
My crashes were specially related to imovie. After the GPU fix I used Imovie for a while without crashes. They appeared without any apparently reason in other circumstances: using Chrome, working on the Finder, etc. On the other question, i think the GPU fix only concern a change in the G state. I hope to receive more details from Senjor User :)
Click to expand...

Thanks for your reply but I'm not sure what you're saying? Did iMovie start crashing again eventually?
[doublepost=1522956433][/doublepost]
newtonuk said:
Hi, not in Leeds. One in Cambridge seemed quite reasonable, but I haven't taken him up on it as mine is now showing another fault where the white parts of the screen look pink and the black parts green :-(

www.2ndchancepc.co.uk
Click to expand...
Hey thanks for your reply but the link to 2nd chance pc can't be found on the server?? Sorry to hear about your further issues dude...
 
tronlady said:
My questions remain unanswered?? Will iMovie will still be usable after changing the kext file?? Also I’m finding it hard to understand. Does the GPU fix turn off the integrated graphics or does it just change the “G state” whatever that is? Or are they the same thing?
Click to expand...
- iMovie will still work after the fix, hopefully even faster than with the integrated graphics.
- The GPU fix makes the computer use the dedicated graphics over the integrated and does turn off the integrated graphics.
- "G-state" limits the voltage given to the dedicated graphics, and the fix forces a "G-state" of 2 (I think around 1.315V or something until the capacitor breaks) and this stops the kernel panic when using the dedicated graphics.
- You will not be able to use the gfxcardstatus tool to change graphics processor and integrated graphics after the fix, as this breaks it, however, you will not need it anyway.

My 2 Cents:
Unless you really need that little bit more graphics power the handicapped NVidia GPU can give you over the Intel graphics (which iMovie will benefit from), but (I wouldn't) bother if it works with the Intel Graphics.
 
fabioroberto said:
Hi,

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

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

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

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

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

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


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



<key>MacBookPro6,2</key>

<dict>

<key>LogControl</key>

<integer>1</integer>

<key>Vendor10deDevice0a29</key>

<dict>

<key>BoostPState</key>

<array>

<integer>2</integer>

<integer>2</integer>

<integer>2</integer>

<integer>2</integer>

</array>

<key>BoostTime</key>

<array>

<integer>2</integer>

<integer>2</integer>

<integer>2</integer>

<integer>2</integer>

</array>

<key>Heuristic</key>

<dict>

<key>ID</key>

<integer>0</integer>

<key>IdleInterval</key>

<integer>10</integer>

<key>SensorOption</key>

<integer>1</integer>

<key>SensorSampleRate</key>

<integer>10000</integer>

<key>TargetCount</key>

<integer>1</integer>

<key>Threshold_High</key>

<array>

<integer>0</integer>

<integer>0</integer>

<integer>100</integer>

<integer>200</integer>

</array>

<key>Threshold_High_v</key>

<array>

<integer>0</integer>

<integer>0</integer>

<integer>98</integer>

<integer>200</integer>

</array>

<key>Threshold_Low</key>

<array>

<integer>0</integer>

<integer>0</integer>

<integer>0</integer>

<integer>200</integer>

</array>

<key>Threshold_Low_v</key>

<array>

<integer>0</integer>

<integer>0</integer>

<integer>4</integer>

<integer>200</integer>

</array>

</dict>

<key>control-id</key>

<integer>17</integer>

</dict>



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


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


1º Editing kext file and install manually:

Step by step:

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

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

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

Attention: verify if your model is 0x0a29 really.

4 - Save info.plist, quit editor.

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

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

After, reboot normally.

Remember, the option automatic graphics switching selected always.

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


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



2º MBP Mid 2010 GPU Fix, utility program:

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

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




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



console.png


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

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

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

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

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

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

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

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

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

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

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

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

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

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

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


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


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

Hi, In the Third point "Hardware fix", The post that you talk about it doesn't exist, could you please link another article or some information?

Greetings.
 
@fabioroberto Basically all I'm asking is how does this file work, maybe some of us with slightly more/less severity for the health of the capacitor (I'm not sure if all bad capacitors work -or not work in this case- the same way so the fix is 100 universal for everyone) but I just want to know what values do what like the meaning of threshold_high_v or threshold_low_v (I have found out how threshold_high and threshold_low work and what they do on another thread on another forum ( https://www.insanelymac.com/forum/f...-full-power-and-save-energy-at-the-same-time/ ) and also what is TargetCount, or SensorSampleRate, or SensorOption or ID or IdleInterval or BoostTime. If you know what they do please tell me, but threshold_high_v and threshold_low_v are most important as it looks like you changed it. If you don't know that is fine but I want to get the most out of this dying thing. Thanks again so much and please reply ASAP as I don't want to mess it up. (BOLD FOR MOST IMPORTANT POINT)
 
MyLaptopStoppedWorking said:
@fabioroberto Basically all I'm asking is how does this file work, maybe some of us with slightly more/less severity for the health of the capacitor (I'm not sure if all bad capacitors work -or not work in this case- the same way so the fix is 100 universal for everyone) but I just want to know what values do what like the meaning of threshold_high_v or threshold_low_v (I have found out how threshold_high and threshold_low work and what they do on another thread on another forum ( https://www.insanelymac.com/forum/f...-full-power-and-save-energy-at-the-same-time/ ) and also what is TargetCount, or SensorSampleRate, or SensorOption or ID or IdleInterval or BoostTime. If you know what they do please tell me, but threshold_high_v and threshold_low_v are most important as it looks like you changed it. If you don't know that is fine but I want to get the most out of this dying thing. Thanks again so much and please reply ASAP as I don't want to mess it up. (BOLD FOR MOST IMPORTANT POINT)
Click to expand...
I apologize for the delay in answering, i'm traveling.

Yes, I know how this works.
Basically, the IdleInterval and SensorOption are related to the observation cycle of the gpu's state, g-states, and analyzing a possible change in the state (clocks and voltages), trying to predict the next state.
The thresholds are points of graphics, where each g-state works. Just as the X and Y points of a graphic function. The area that corresponds to the graphical coordinates are the intervals of action of each g-state. The gpu do not work with linear changes, but with intervals. Intervals that consider temperature, gpu core utilization, and future prediction.

The problem with this logic board is the capacitor, as Louis Rossmann said for us.
The Panic happen when the voltage change, high to low or low to high, considering thresholds levels.


See you.
 
  • Like
Reactions: rafael.scheid
fabioroberto said:
I apologize for the delay in answering, i'm traveling.

Yes, I know how this works.
Basically, the IdleInterval and SensorOption are related to the observation cycle of the gpu's state, g-states, and analyzing a possible change in the state (clocks and voltages), trying to predict the next state.
The thresholds are points of graphics, where each g-state works. Just as the X and Y points of a graphic function. The area that corresponds to the graphical coordinates are the intervals of action of each g-state. The gpu do not work with linear changes, but with intervals. Intervals that consider temperature, gpu core utilization, and future prediction.

The problem with this logic board is the capacitor, as Louis Rossmann said for us.
The Panic happen when the voltage change, high to low or low to high, considering thresholds levels.


See you.
Click to expand...

Thanks you very much for replying even when busy, this is very useful information and I will try to get slightly changing your values in my own laptop to see if I can get more out of my laptop, thanks for your detailed response! :)

Great work you have done like Rossman and others for this small community of people who will still push and keep an 8 year old laptop working, saving lots of people's time and money left and right! Thanks to you all and keep up the great effort! :)
 
  • Like
Reactions: rafael.scheid
tronlady said:
My questions remain unanswered?? Will iMovie will still be usable after changing the kext file?? Also I’m finding it hard to understand. Does the GPU fix turn off the integrated graphics or does it just change the “G state” whatever that is? Or are they the same thing?
[doublepost=1522956128][/doublepost]

Thanks for your reply but I'm not sure what you're saying? Did iMovie start crashing again eventually?
[doublepost=1522956433][/doublepost]
Hey thanks for your reply but the link to 2nd chance pc can't be found on the server?? Sorry to hear about your further issues dude...
Click to expand...

2nd Chance is back up now, at least it is here.
 
MyLaptopStoppedWorking said:
- iMovie will still work after the fix, hopefully even faster than with the integrated graphics.
- The GPU fix makes the computer use the dedicated graphics over the integrated and does turn off the integrated graphics.
- "G-state" limits the voltage given to the dedicated graphics, and the fix forces a "G-state" of 2 (I think around 1.315V or something until the capacitor breaks) and this stops the kernel panic when using the dedicated graphics.
- You will not be able to use the gfxcardstatus tool to change graphics processor and integrated graphics after the fix, as this breaks it, however, you will not need it anyway.

My 2 Cents:
Unless you really need that little bit more graphics power the handicapped NVidia GPU can give you over the Intel graphics (which iMovie will benefit from), but (I wouldn't) bother if it works with the Intel Graphics.
Click to expand...
Thankyou
[doublepost=1523296931][/doublepost]Thanks for replying but I’m still confused. My understanding was that I needed to find a way to use the integrated graphics rather than the dedicated graphics and that the problem is with the dedicated graphics. Have I got this wrong? The reason that I think this is because lots of people on here have said that if you use the GPU fix you will lose a bit of graphics power? (It switches the dedicated graphics off?). Fron what you are saying, it is the other way round and switches the integrated graphics off!? Also, it is hard to know which graphics card my MBP is using at any given time? I am assuming that because it’s iMovie it will be using the dedicated graphics card?? (As iMovie is graphics intensive). Anyway.....every time I use iMovie, it restarts.....sometimes within 1 minute. I left it recording several audio channels into Logic pro for five hours the other day so this is making me think it is a graphics problem.


MyLaptopStoppedWorking said:
- iMovie will still work after the fix, hopefully even faster than with the integrated graphics.
- The GPU fix makes the computer use the dedicated graphics over the integrated and does turn off the integrated graphics.
- "G-state" limits the voltage given to the dedicated graphics, and the fix forces a "G-state" of 2 (I think around 1.315V or something until the capacitor breaks) and this stops the kernel panic when using the dedicated graphics.
- You will not be able to use the gfxcardstatus tool to change graphics processor and integrated graphics after the fix, as this breaks it, however, you will not need it anyway.

My 2 Cents:
Unless you really need that little bit more graphics power the handicapped NVidia GPU can give you over the Intel graphics (which iMovie will benefit from), but (I wouldn't) bother if it works with the Intel Graphics.
Click to expand...
 
Does the 13" mid 2010 have this issue? Or was it only the GT 330M in the 15" and 17" models. I haven't had any problems with the 13" but it does get quite hot. If it's a ticking time bomb I'd rather get rid of it now.
 
l.a.rossmann said:
13" does not have this issue. Your ticking time bomb will be dead HDD cable.
Click to expand...
If this really is Louis Rossman I have been watching your videos for the past hour while eating my dinner LOL!

Anyway, I appreciate your response. I was gifted this Mac from a job and was going to put Linux on it providing there were no issues with this model. I have dealt with the fail GPU in the MacBook Pro A1260 before and ended up parting out.

This mid 2010 13" unibody is pretty nice minus the low resolution; It's also one of the last you can easily upgrade. Then again, I could sell it on craigslist for a high price and buy something far better like a Thinkpad.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back