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

Oct 19, 2017 3:42 PM in response to mattmadd90

It turned out there was a software issue, as you said, and it was eventually fixed (for me, and many others). I had the exact same problem; everyone said it was just hardware and to stop talking about software drivers, and then one day an OS X update fixed it.


It was hidden in the release notes, something like "Fixes an issue causing system failure in some MacBook Pro models when using discrete graphics" or words to that effect. I can't be bothered to find out which OS X version it was, but it was at least 2 years ago.


There was at least one separate but ultimately unrelated hardware issue with some models around the same time, which caused much of the confusion. So I have no idea which people were impacted by the hardware problem and which people were experiencing the results of the OS X bug.


But for many people who were not using those models listed as being affected by the hardware defect/recall, it wasn't a coincidence that this problem started right after an OS X update. There was a bug in OS X which did cause problems with some discrete graphics-based systems.


I'm still using the same computer which was experiencing multiple daily shutdowns due to this issue, and it has been running fine ever since. No hardware fix required. I wonder how many people paid for expensive logic board replacements they didn't need?

Nov 2, 2014 3:00 PM in response to LouCasa

You have a MacBook Pro with a known GPU fault that requires replacing the logic board. The panic report you posted is indicative of the problem.

The free replacement period has ended. You might be able to get them to replace it for free as the problem didn't occur until you upgraded.

Print out out the following article and take it and your Mac to an Appke Store or certified repair center.

MacBook Pro (15-inch, Mid 2010): Intermittent black screen or loss of video - Apple Support

Nov 4, 2014 7:58 PM in response to Barney-15E

Fixing hardware is NOT a helpful solution because most likely, it will cost people more than $300(I just learned that there is a $300 flat rate for certain kind of repairing) for a 4 and half years old laptop.

My mbp notebook 2010 15'' has the same problem after upgrading to yosemite.

In 2012, I sent it to apple store and had it repaired for free. After that, mountain lion and mavericks are running alright over 95% of the time without sudden black screen and restart, even WITHOUT gfxStatus installed.

Until upgraded to yosemite from mavericks last week, this old nightmare comes back. I have to install gfxStatus and manually make it use 'Integrated Only'. Unfortunately, it does NOT help.

I have enough reasons to believe that the new yosemite does not cover this particular edge case like mavericks did, same machine same hardware but suddenly crashes 10 times a day just after upgrading. It is clear that the new OS and its display driver does not consider this 'delay response'. It is not a hard work for apple os/driver team to fix it in display driver because the error message is so clear, if some pixels are 'stucked', use its 'neighbors', or refresh again using integrated graphic card, or just do something instead of crashing the whole OS. It is reasonable to have some failover protection in the display driver.

I am surprised all the comments online saying it can't be fixed, or go to apple store and replace the hardware. In my example, the replaced hardware is still NOT working. Again, if apple os or driver team can just fix this edge case in the display driver without actually fix the hardware, it will be good enough and very very helpful to the users who own this model.


Currently, my temporary solution is hook up with my dell external monitor, and use gfxStatus, set it to 'Discrete Only', the black screen and sudden restart comes to me once or twice a day at most, it is kinda barely acceptable to me. Of course, it does not mean it fixes the problem, when I disconnect the external monitor and move it to my living room, it crashes.

Nov 9, 2014 8:26 AM in response to dabaipang

I am also using same model (2010-mid 15", i7) and crashed 1-2 times per day after upgraded to Yosemite 10.10.


I brought my macbook to apple store Genius bar, they run VST (video test) for my macbook and confirmed failure. They offered me the price HKD4,xxx for replacing the logic board. I did rejected and downloaded gfxCardStatus app. Only chosen "Integrated" mode every time when I logged in mac os.


Now everytime i started iMovie, it prompted error and i must changed to another display card (Geforce) by gfxcard. But also crashed after I scrolled trailer in iMovie.


I hope Apple will fix this bug ASAP and it will save many macbooks and Apple fans.


I am very disappointed this time about apple products. It is because software affecting hardware? and expensive for replacing logic board but dabaipang also stated that it may have same problem after replaced hardware 😟

Nov 9, 2014 9:12 AM in response to hamo chai

I hope Apple will fix this bug ASAP and it will save many macbooks and Apple fans.

There isn’t a bug to fix. It is a known fault that happened during the manufacture of the GPU.

Generally, the GPU wasn’t taxed as hard with previous OS’s, so many didn’t see the flaw until they upgraded to Lion, Mountain Lion, Mavericks, or Yosemite.

Nov 9, 2014 3:50 PM in response to Barney-15E

So let me get this straight: It was a known manufacturing defect but now is no longer covered? It worked fine until the OS taxed it, and Apple knows what the problem is, so why can't Apple build an exception into the OS? It would certainly be cheaper than replacing all the motherboards. One of the reasons for buying a Mac is the supposedly tight integration between HW and SW, so come on Apple, fix this for us!


By the way, I didn't experience it until updating to 10.9.5 a few months ago. How about taking that into account when offering a replacement program?!

Nov 9, 2014 4:04 PM in response to LouCasa

By the way, I didn't experience it until updating to 10.9.5 a few months ago. How about taking that into account when offering a replacement program?!

I don’t work for Apple, and I’m certainly not going to replace your logic board. You should ask Apple. If you have an Apple Store nearby, then I would try to use that fact.

It worked fine until the OS taxed it, and Apple knows what the problem is, so why can't Apple build an exception into the OS?

It’s not some API call to the GPU that reveals the flaw, so it can’t be “excepted." It is flawed. Just using it could trigger the flaw. Some people actually saw it in 10.6. Others didn’t see it until upgrading past 10.6. As already mentioned, you can avoid using the GPU with gfxCardStatus.

Nov 9, 2014 6:17 PM in response to Barney-15E

Sorry, I didn't mean to imply that you personally were responsible. It was meant as a general plea to the people at Apple monitoring these discussions.


I can't use gfxCardStatus in Integrated Only mode since I need to use Chrome. I also can't afford to be without my laptop for the extended time it would take to fix it, even if they cover it.

Nov 10, 2014 4:07 AM in response to LouCasa

LouCasa wrote:


Sorry, I didn't mean to imply that you personally were responsible. It was meant as a general plea to the people at Apple monitoring these discussions.

There isn’t anyone from Apple that matters monitoring this forum. There are moderators here that work for Apple, but they don’t have anything to do with Apple corporate.

Nov 10, 2014 9:00 AM in response to Barney-15E

Thanks for your reply. But please try to understand why we (affected people) are not happy for this problem.


Actually Apple store's staff also told me that is known "H/W" fault when i brought my macbook to run VST last week.


Apple claimed this is H/W fault and suggested us to change logic board. The interesting thing is, this problem was existed from long time ago. Please check this URL > MacBook Pro (15-inch, Mid 2010): Intermittent black screen or loss of video - Apple Support


After read the page above, you should understand that version 10.8 or before also got this "H/W" problem but Apple tried to fix this for 10.8 or before.


From 10.9, no more support for this problem. Until 10.10 released, you may search "GPUPanic 2010 mid macbook" from google and you will see how many people was affected by this problem.


I also want to classify what is the definition of H/W fault. If apple can isolate the bug of the logic which was burnt on logic board (version 10.8 or before), then this is software fix for H/W fault.


If Apple OS development team can just check our macbook version from OS and escape the "H/W" logic bug, all 2010 mid macbook will not be affected again.


For real H/W fault, I don't think so many people will see same error at same period (after upgraded to 10.10) like this > ... AppleMuxControl/kext/GPUPanic.cpp:127


The important point is, Apple provided OS update for us before 10.8, then we didnt know the actual graphic card's problem.

We trusted Apple and bought macbook. But Apple told us that our graphic card got "H/W" fault and no more support from 10.9.


I like macbook and saved money to buy this in 2010. Using it carefully up to now. Finally Apple told me that my macbook's graphic card got problem and asked me to change(buy) logic board for fixing this problem.


In Sep 2014, I'd just bought new macbook for my girl friend which is new model 2014 15" macbook pro. I told her macbook is very stable and have no problem. What a big joke to me......and to all affected people.

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.