You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

MacBook Pro Mid-2010 15" Frequent Kernel Panics

Hello all,


I have been experiencing frequent kernel panic shutdowns (2-3 a day) since upgrading to Yosemite. To compound matters, after each panic is an additional restart as my computer is already in the process of restarting, so I never get the crash log or option to send it, and I can't decipher the logs in Console to find them--if they exist.


This is also happening to my daughter's identical model, and was happening after updating to 10.9.5 a while ago. I took my laptop to the Genius bar and they tried to tell me there was an issue with my video card (GPU) and that it would need replacing. I was doubtful about that diagnosis and opted not to repair (no time to give up my computer for the time needed anyway), and with my daughter's problem I seem to be vindicated. Prior to installing Yosemite I reinstalled 10.9.5 and was crash-free for a week before upgrading to Yosemite. Now the problem is getting worse, and reinstalling did not fix it.


I am attaching my daughter's recent crash log with the same GPU incident that the Genius showed me.


Any ideas or inspiration would be welcome.


Thanks,

Lou


Anonymous UUID: 334DFA24-A3CB-CD55-BD16-9309B1CFCCD1


Thu Oct 30 11:50:09 2014


*** Panic Report ***

panic(cpu 1 caller 0xffffff7f8dfcff63): "GPU Panic: [<None>] 5 3 7f 0 0 0 0 3 : NVRM[0/1:0:0]: Read Error 0x00000100: CFG 0xffffffff 0xffffffff 0xffffffff, BAR0 0xd2000000 0xffffff80b36ba000 0x0a5480a2, D0, P2/4\n"@/SourceCache/AppleGraphicsControl/AppleGraphicsControl-3.7.21/src/Apple MuxControl/kext/GPUPanic.cpp:127

Backtrace (CPU 1), Frame : Return Address

0xffffff80a2ab31f0 : 0xffffff800b33a811

0xffffff80a2ab3270 : 0xffffff7f8dfcff63

0xffffff80a2ab3350 : 0xffffff7f8c11bb9f

0xffffff80a2ab3410 : 0xffffff7f8c1e518e

0xffffff80a2ab3450 : 0xffffff7f8c1e51fe

0xffffff80a2ab34c0 : 0xffffff7f8c464056

0xffffff80a2ab35f0 : 0xffffff7f8c20882d

0xffffff80a2ab3610 : 0xffffff7f8c1225f1

0xffffff80a2ab36c0 : 0xffffff7f8c1200fc

0xffffff80a2ab38c0 : 0xffffff7f8c122225

0xffffff80a2ab39b0 : 0xffffff7f8d68c925

0xffffff80a2ab3a10 : 0xffffff7f8d6895ef

0xffffff80a2ab3a90 : 0xffffff7f8d6737fb

0xffffff80a2ab3ad0 : 0xffffff7f8d66a7dd

0xffffff80a2ab3b30 : 0xffffff800b901156

0xffffff80a2ab3b60 : 0xffffff800b90283b

0xffffff80a2ab3bc0 : 0xffffff800b900003

0xffffff80a2ab3d00 : 0xffffff800b3ea517

0xffffff80a2ab3e10 : 0xffffff800b33e91c

0xffffff80a2ab3e40 : 0xffffff800b3235a3

0xffffff80a2ab3e90 : 0xffffff800b333e8d

0xffffff80a2ab3f10 : 0xffffff800b40a142

0xffffff80a2ab3fb0 : 0xffffff800b43ac66

Kernel Extensions in backtrace:

com.apple.driver.AppleMuxControl(3.7.21)[32B7E2DE-1F9D-3555-B687-7A76A62B81D2]@0 xffffff7f8dfc1000->0xffffff7f8dfd4fff

dependency: com.apple.driver.AppleGraphicsControl(3.7.21)[62689710-EEA7-307A-AC83-B8F25DA88 A6A]@0xffffff7f8dfb9000

dependency: com.apple.iokit.IOACPIFamily(1.4)[70E2B65E-A91A-3522-A1A0-79FD63EABB4C]@0xfffff f7f8bda9000

dependency: com.apple.iokit.IOPCIFamily(2.9)[766FC23F-452C-3B74-951C-598BB17BCF06]@0xffffff 7f8bb24000

dependency: com.apple.iokit.IOGraphicsFamily(2.4.1)[6D99A3BE-D531-3780-880B-13F2FC894A4A]@0 xffffff7f8c074000

dependency: com.apple.driver.AppleBacklightExpert(1.1.0)[0183904C-6A16-32C4-9405-EEFD7F820B 02]@0xffffff7f8dfbc000

com.apple.nvidia.classic.NVDAResmanTesla(10.0)[796AE430-39FB-3255-8161-D52AFA28E E2B]@0xffffff7f8c0cb000->0xffffff7f8c334fff

dependency: com.apple.iokit.IOPCIFamily(2.9)[766FC23F-452C-3B74-951C-598BB17BCF06]@0xffffff 7f8bb24000

dependency: com.apple.iokit.IONDRVSupport(2.4.1)[F4738C55-B507-3627-A9CA-3D29A5230A03]@0xff ffff7f8c0bb000

dependency: com.apple.iokit.IOGraphicsFamily(2.4.1)[6D99A3BE-D531-3780-880B-13F2FC894A4A]@0 xffffff7f8c074000

com.apple.nvidia.classic.NVDANV50HalTesla(10.0)[7FE40648-F15F-3E18-91E2-FDDDF4CD A355]@0xffffff7f8c33f000->0xffffff7f8c5e8fff

dependency: com.apple.nvidia.classic.NVDAResmanTesla(10.0.0)[796AE430-39FB-3255-8161-D52AFA 28EE2B]@0xffffff7f8c0cb000

dependency: com.apple.iokit.IOPCIFamily(2.9)[766FC23F-452C-3B74-951C-598BB17BCF06]@0xffffff 7f8bb24000

com.apple.GeForceTesla(10.0)[67CD214F-0F26-3BEF-BAD0-CF0F83C2616D]@0xffffff7f8d6 26000->0xffffff7f8d6f3fff

dependency: com.apple.iokit.IOPCIFamily(2.9)[766FC23F-452C-3B74-951C-598BB17BCF06]@0xffffff 7f8bb24000

dependency: com.apple.iokit.IONDRVSupport(2.4.1)[F4738C55-B507-3627-A9CA-3D29A5230A03]@0xff ffff7f8c0bb000

dependency: com.apple.iokit.IOGraphicsFamily(2.4.1)[6D99A3BE-D531-3780-880B-13F2FC894A4A]@0 xffffff7f8c074000

dependency: com.apple.nvidia.classic.NVDAResmanTesla(10.0.0)[796AE430-39FB-3255-8161-D52AFA 28EE2B]@0xffffff7f8c0cb000


BSD process name corresponding to current thread: WindowServer


Mac OS version:

14A389


Kernel version:

Darwin Kernel Version 14.0.0: Fri Sep 19 00:26:44 PDT 2014; root:xnu-2782.1.97~2/RELEASE_X86_64

Kernel UUID: 89E10306-BC78-3A3B-955C-7C4922577E61

Kernel slide: 0x000000000b000000

Kernel text base: 0xffffff800b200000

__HIB text base: 0xffffff800b100000

System model name: MacBookPro6,2 (Mac-F22586C8)


System uptime in nanoseconds: 7944503916275

last loaded kext at 375968224482: com.apple.filesystems.smbfs 3.0.0 (addr 0xffffff7f8be79000, size 393216)

last unloaded kext at 493559229555: com.apple.driver.AppleUSBUHCI 656.4.1 (addr 0xffffff7f8c82e000, size 65536)

loaded kexts:

  1. com.LivestreamProcaster.driver.ProcasterAudioRedirector 2.0.0
  2. com.apple.filesystems.smbfs 3.0.0
  3. com.apple.driver.AppleHWSensor 1.9.5d0
  4. com.apple.driver.AGPM 100.14.37
  5. com.apple.filesystems.autofs 3.0
  6. com.apple.iokit.IOBluetoothSerialManager 4.3.0f10
  7. com.apple.driver.AppleOSXWatchdog 1
  8. com.apple.driver.AppleMikeyHIDDriver 124
  9. com.apple.driver.AppleMikeyDriver 266.5
  10. com.apple.driver.AudioAUUC 1.70
  11. com.apple.iokit.IOUserEthernet 1.0.1
  12. com.apple.driver.AppleUpstreamUserClient 3.6.1
  13. com.apple.GeForceTesla 10.0.0
  14. com.apple.Dont_Steal_Mac_OS_X 7.0.0
  15. com.apple.driver.AppleHWAccess 1
  16. com.apple.driver.AppleHV 1
  17. com.apple.driver.AppleHDA 266.5
  18. com.apple.driver.ACPI_SMC_PlatformPlugin 1.0.0
  19. com.apple.driver.AppleIntelHDGraphics 10.0.0
  20. com.apple.driver.AppleIntelHDGraphicsFB 10.0.0
  21. com.apple.driver.AppleSMCLMU 2.0.4d1
  22. com.apple.driver.AppleMuxControl 3.7.21
  23. com.apple.driver.AppleMCCSControl 1.2.10
  24. com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport 4.3.0f10
  25. com.apple.driver.AppleSMCPDRC 1.0.0
  26. com.apple.driver.AppleLPC 1.7.3
  27. com.apple.driver.SMCMotionSensor 3.0.4d1
  28. com.apple.driver.AppleUSBTCButtons 240.2
  29. com.apple.driver.AppleUSBTCKeyboard 240.2
  30. com.apple.driver.AppleUSBCardReader 3.5.0
  31. com.apple.driver.AppleIRController 327.5
  32. com.apple.AppleFSCompression.AppleFSCompressionTypeDataless 1.0.0d1
  33. com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1
  34. com.apple.BootCache 35
  35. com.apple.iokit.SCSITaskUserClient 3.7.0
  36. com.apple.driver.XsanFilter 404
  37. com.apple.iokit.IOAHCIBlockStorage 2.6.5
  38. com.apple.driver.AppleUSBHub 705.4.1
  39. com.apple.driver.AppleFWOHCI 5.5.2
  40. com.apple.driver.AppleAHCIPort 3.0.7
  41. com.apple.driver.AirPort.Brcm4331 800.20.24
  42. com.apple.iokit.AppleBCM5701Ethernet 10.1.2b3
  43. com.apple.driver.AppleUSBEHCI 705.4.14
  44. com.apple.driver.AppleSmartBatteryManager 161.0.0
  45. com.apple.driver.AppleACPIButtons 3.1
  46. com.apple.driver.AppleRTC 2.0
  47. com.apple.driver.AppleHPET 1.8
  48. com.apple.driver.AppleSMBIOS



Model: MacBookPro6,2, BootROM MBP61.0057.B0F, 2 processors, Intel Core i5, 2.4 GHz, 4 GB, SMC 1.58f17

Graphics: Intel HD Graphics, Intel HD Graphics, Built-In, 288 MB

Graphics: NVIDIA GeForce GT 330M, NVIDIA GeForce GT 330M, PCIe, 256 MB

Memory Module: BANK 0/DIMM0, 2 GB, DDR3, 1067 MHz, 0x802C, 0x31364A53463235363634485A2D3147314631

Memory Module: BANK 1/DIMM0, 2 GB, DDR3, 1067 MHz, 0x802C, 0x31364A53463235363634485A2D3147314631

AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x93), Broadcom BCM43xx 1.0 (5.106.98.100.24)

Bluetooth: Version 4.3.0f10 14890, 3 services, 27 devices, 1 incoming serial ports

Serial ATA Device: WDC WD7500BPKT-22PK4T0, 750.16 GB

Serial ATA Device: MATSHITADVD-R UJ-898

USB Device: Hub

USB Device: BRCM2070 Hub

USB Device: Bluetooth USB Host Controller

USB Device: Internal Memory Card Reader

USB Device: Apple Internal Keyboard / Trackpad

USB Device: Hub

USB Device: Built-in iSight

USB Device: IR Receiver

Thunderbolt Bus:

MacBook Pro, OS X Yosemite (10.10), 15" (Mid-2010) 2.4 GHz i5/8 GM RAM

Posted on Nov 2, 2014 2:47 PM

Reply
46 replies

Jul 19, 2015 7:54 PM in response to LouCasa

Same issue here. Mid-2010, Model 6,2. System crashes and reboots, or screen just goes black. Panic Report says GPU issue. Apple says motherboard failure and offered to sell me a refurbished motherboard for $310. It seems that Yosemite requires more resources than the GPU can deliver, and the crash is triggered when the system tries autoswitching between the motherboard processor and the graphics processor. One fix is to go into EnergySaver and disable automatic graphics switching (which consumes more battery power, unfortunately). I plan to also wipe the hard disk, reinstall Mavericks, and not upgrade to Yosemite. If that works, I'll just stick with Mavericks until the time comes to buy a new laptop. (Alternatively, the OS after Yosemite is supposed to be more efficient, so it may make this problem go away; i.e., it may be possible to upgrade immediately to Yosemite, then upgrade to the next OS.)


I think we should all push for Apple to extend their board replacement program to include mid-2010 systems — the graphics problem seems to have been caused by Yosemite bloat.

Jul 29, 2015 7:47 PM in response to LouCasa

I completely agree with you LouCasa. I am having the exact same issue here with my mid-2010 Macbook Pro...GPU panics constantly now, at least 2-3 times a day, and it started after upgrading to 10.10 (Yosemite). I just recently downgraded to 10.6.8 (Snow Leopard) as a test, and it's been running fine for several weeks now, no crashes at all. I can't believe that most immediate responses are to replace the motherboard. Yes this model and pretty much any model from 2010 - 2014 has been reported to have GPU hardware problems, big fail...but I believe mine to be fine, at least for now. I hope apple fixes this issue, predicting a video driver problem. For now Snow Leopard is solid. I'm going to upgrade to Mountain Lion soon and see how it performs. I will report back if I get any GPU panic shut downs.


I also noticed that in Yosemite, my fan speeds would stay at the constant minimum 2000 rpm, and when the computer heats up, and I am running more video intense applications, the fans speeds stay the same and do not increase. This leads me to believe there is clearly a driver problem with Yosemite and this model. The fan speeds should increase along with the increased temperatures, but they do not. Now while running Snow Leopard, my fan speeds are automatically adjusting themselves again, and having no problems at all.


Also note that I clean out my fans regularly, and have even repasted my the CPU and GPU with good quality thermal paste.


Most times I see GPU's fail is that a person has never cleaned out their laptop and there is a huge build-up of dust in the fans, causing overheating.


If somehow I were to now have a GPU hardware problem then I blame Yosemite for sure, maybe the new OS stressed my video card so hard that it is now beginning to fail. I am not sure...who knows.


I really hope Apple receives a lot of complaints about this. I'm just going to stick with an older OS for now, and also I won't be buying another mac in the future, for several reasons:


1) My previous Macbook Pro (2008) I had to bring in for service 6 times for motherboard / gpu / fan / heat issues.


2) With the newer models today, you cannot upgrade hardware, everything is now built-in to the motherboard, including hard drive, ram, etc. So if you run into any hardware problems at all, your looking at replacing the motherboard. This should not be legal, we should be aloud to upgrade our ram and hard drive. Why does a laptop have to keep getting slimmer (runs hotter, and less ports) and have less hardware that can actually be replaced. People are going to be getting into serious costs on repairs when they have a minor hardware issue and they're warranty has expired.


3) Just to contact them for any phone support once your warranty is up, it costs $35. Not worth it for me, absolutely ridiculous! All other computer companies I have dealt with at least I will be able to get through to someone over the phone who can assist me with my issues or complaints.


4) Their MagSafe adapters are faulty, I have had to buy a few, and I handle mine very carefully. Just look at the horrible rating on the website for the adapters, its horrible. Very poor design flaw. I do like the magnetic port, but the construction of the adapter at the tip is poorly done. There should be a small tab built in so that you can pull it off without pulling at the cord which bends it overtime.

Aug 20, 2015 12:46 AM in response to hamo chai

Apple needs to stop being lazy by blaming the hardware... This is a driver issue and Apple just don't want to code a fix...

You've all been asking "what about Windows?"...


When running Windows 8.1 the gpu will encounter the error but the whole OS doesn't shut down, the screen just goes blank for a few seconds and then comes back just fine followed by a balloon notification stating that the nvidia graphics driver has crashed and recovered from the error.

The fact that this gpu error is not a fatal error in Windows just proves that it's a driver issue and not hardware, or at the very least, it can be fixed with a driver update instead of an entire hardware replacement.

It seems that Apple is just taking the easy way out by blaming the hardware and saying replacements are needed instead of actually looking into the error and coding a fix for it.

Sep 10, 2015 2:53 PM in response to Barney-15E

You sound like you work for apple my friend. A GPU problem that appears on everyone's (including my machine) machines after a Yosemite's upgrade, does look like a very clear, obvious apple software ****-up.


Just disable that GPU (Most likely the discrete one), with the use of a utility out there, and your problem will be solved...

At least until apple will decide to fix this.

However, I'm 100% sure they won't ever fix this with their software updates.


I mean think about it:

Apple has this AWESOME hardware.

They have you HOOKED on their iCloud and i-What-Not. Right ?

Now you HAVE to go Apple.

If they have a new product, that they want more money for, you won't expect then to fix your OLD product so that you end up paying.. probably NOTHING instead of paying another $1k for an upgrade or ever $3k at least for their new product ? Right ? That drives than right out of business.


So... why not get $300 per each 2010 mid MBP owner.. Right ? I mean... if you had a choice as a business owner, what would you do?


I'm typing this from my Mid 2010 Mac Book Pro, with Ubuntu installed on it.

It's working GREAT ! Even with some neat Steam games on too!


Perhaps you should do the same 😉

Sep 10, 2015 5:43 PM in response to gwwknaqu

The problem is a documented flaw in the Nvidia GPU. You can continue hoping for a software update, but there won't be one as you don't fix a hardware flaw with software, especially on 5-year old hardware.

Perhaps you should do the same 😉

No need. I replaced mine under the extended repair program and it runs Yosemite flawlessly. It demonstrated the problem only after upgrading to Lion.


<Edited by Host>

Oct 23, 2015 11:21 AM in response to LouCasa

I have just taken my 2010 MacBook Pro with the bad GPU into an Apple Store and they agreed to fix it, even though the repair program ended in March this year. I would urge anyone with the same issue to at least ask Apple if they will still fix it, they might not, but there's no harm in trying!


Update: someone has pointed out that under UK consumer law you are entitled to a repair up to 6 years from the original purchase date, I believe this is why I was offered a free repair.

Oct 23, 2015 12:20 PM in response to LouCasa

Just went in to the store. 2010 15" MBP same thing flat rate $310.00

You don't have a cutoff on a device that's defective because of your coding negligence.

Thats like having a cutoff on a car with a safety issue.

Sorry Apple I'm out ... your loss. Very nice products but there are too many nice alternatives to Apple at almost half the cost.

I refuse to spend $300.00 on a duct tape repair of a 5 year old laptop.

You should be ashamed. your coding has exposed its own flaws and you wont help your customers out.

My wife wanted a new MBP for her birthday and we were looking at an I Pad mini for my son. Walked right out of the store!

Samsung will do just fine in my house.

Cancelling I cloud as well. I'll buy a NAS instead.

Dec 26, 2015 12:02 AM in response to LouCasa

OK, ladies and germs, I have had the same problem.


Until recently, I never knew this MBP 6,2 mid-2010 would be a clunker, but it had shown problems before, but not like this. I too, have had the GPU panic, the screen just goes blank, it gives me the grey screen message that the computer has problems and restarts.

It had been doing it for a while now, ever since I upgraded to El Capitan, but not before.

Before, it used to slow down and freeze and not much more, but definitely would be slow in running a few things. Now it would just go blank. I used to have to run Permissions repair all the time as the same problem kept coming up - but never a mention of the GPU panic in any of the messages. But obviously there's something there, and since I upgraded to El Capitan, it got worse, to this point of going blank and restarting all the time.


The other day I decided to try the various methods mentioned here, but I'm not a programmer nor am I technical enough to start messing with Xcode and such, but I decided to just run ONYX and see if that would help. http://www.titanium.free.fr/onyx.html

Instead of just running the Automation, I decided to carefully run each segment one by one, making sure I cleaned everything including the Error logs and so on.

I then ran Automation again to make sure, and then let it restart.


Voila. So far, I have had no problems for an entire day. Strange, isn't it? And for two days now it's been quite stable and behaving. I haven't had to be really careful and jumpy that it might go blank while I was doing something important. I guess the new Disk Utility doesn't do enough.


I thought I would contribute my 2cents.

Dec 28, 2015 10:29 AM in response to LouCasa

OK. I spoke too soon.


But I think I found a glitch.


It happens only when I have STICKIES open. I use Stickies down the left side of the screen, I have several stickies with some notes, and when I have them open and then I try to use the notes while I am also on Safari, it crashes. But when I have Stickies off, as I am on Safari like I am now, the computer works like normal. Weird, isn't it? I had noticed it before, while I would be looking at some notes it would crash, but I clearly noticed it this time for sure, as I had not opened Stickies since I last wrote on here about what I thought I was experiencing.


So there must be something wrong here with El Capitan, Stickies and the GPU glitch.

MacBook Pro Mid-2010 15" Frequent Kernel Panics

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.