Apple Event: May 7th at 7 am PT

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

Level 1

7 points

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:

com.LivestreamProcaster.driver.ProcasterAudioRedirector 2.0.0
com.apple.filesystems.smbfs 3.0.0
com.apple.driver.AppleHWSensor 1.9.5d0
com.apple.driver.AGPM 100.14.37
com.apple.filesystems.autofs 3.0
com.apple.iokit.IOBluetoothSerialManager 4.3.0f10
com.apple.driver.AppleOSXWatchdog 1
com.apple.driver.AppleMikeyHIDDriver 124
com.apple.driver.AppleMikeyDriver 266.5
com.apple.driver.AudioAUUC 1.70
com.apple.iokit.IOUserEthernet 1.0.1
com.apple.driver.AppleUpstreamUserClient 3.6.1
com.apple.GeForceTesla 10.0.0
com.apple.Dont_Steal_Mac_OS_X 7.0.0
com.apple.driver.AppleHWAccess 1
com.apple.driver.AppleHV 1
com.apple.driver.AppleHDA 266.5
com.apple.driver.ACPI_SMC_PlatformPlugin 1.0.0
com.apple.driver.AppleIntelHDGraphics 10.0.0
com.apple.driver.AppleIntelHDGraphicsFB 10.0.0
com.apple.driver.AppleSMCLMU 2.0.4d1
com.apple.driver.AppleMuxControl 3.7.21
com.apple.driver.AppleMCCSControl 1.2.10
com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport 4.3.0f10
com.apple.driver.AppleSMCPDRC 1.0.0
com.apple.driver.AppleLPC 1.7.3
com.apple.driver.SMCMotionSensor 3.0.4d1
com.apple.driver.AppleUSBTCButtons 240.2
com.apple.driver.AppleUSBTCKeyboard 240.2
com.apple.driver.AppleUSBCardReader 3.5.0
com.apple.driver.AppleIRController 327.5
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless 1.0.0d1
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1
com.apple.BootCache 35
com.apple.iokit.SCSITaskUserClient 3.7.0
com.apple.driver.XsanFilter 404
com.apple.iokit.IOAHCIBlockStorage 2.6.5
com.apple.driver.AppleUSBHub 705.4.1
com.apple.driver.AppleFWOHCI 5.5.2
com.apple.driver.AppleAHCIPort 3.0.7
com.apple.driver.AirPort.Brcm4331 800.20.24
com.apple.iokit.AppleBCM5701Ethernet 10.1.2b3
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

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

46 replies

Barney-15E

Level 10

112,782 points

Nov 10, 2014 4:56 PM in response to hamo chai

I Completely understand. You just assume I care, which I dont.

Nov 10, 2014 8:34 PM in response to hamo chai

I am considering about the flat rate fix, if it's $300. I searched online about what the flat rate fix is, the reason behind flat rate would be using a refurbished logic board and replacing the old one. Thanks for the reminding about VST, because I know most likely I need to reproduce this issue in the store before getting accepted for this fix. Sometimes it could take more than 30 minutes not crashing, it would be awkward not reproducing this black screen issue in the store.

I hope it could fix this issue.

Nov 11, 2014 5:02 AM in response to dabaipang

Everytime I scroll the page in iMovie's trailer view (selection screen), it will auto restart. You may try.

Jan 8, 2015 1:20 AM in response to LouCasa

I have the exact same problem. I didn't noticed the H/W default until the last quarter of past year, as well as the replacement program, which obviously had expired already. Until I moved to Yosemite I didn't get gpu panics, now I get two or three in the same day. Do you think that reverting to mavericks could help? Has anyone tried already? Thanks.

Barney-15E

Level 10

112,782 points

Jan 8, 2015 4:30 AM in response to curreiros

Previous reports didn't indicate reverting would help.

Jan 8, 2015 4:40 AM in response to Barney-15E

Thanks for the reply. Could that mean that motherboards fail after the yosemite upgrade? The recurrence of kernel panics until then didn't made my computer unusable, I could play games, use photoshop or any other application relying on discrete graphics without a restart, and most failures (one in a month or two) came after waking my computer from sleep.

In other order of things, does this problem also affects when using windows/bootcamp? If reverting don't work, I could rely on this in case I need to work with applications that make use of discrete graphics.

Barney-15E

Level 10

112,782 points

Jan 8, 2015 5:26 PM in response to curreiros

curreiros wrote:

Thanks for the reply. Could that mean that motherboards fail after the yosemite upgrade?

No, and it's not the motherboard. It is the Nvidia GPU that was bad. It is soldered to the Logic Board. Some saw the flaw in Snow Leopard (the OS it shipped with). Others didn't see it until they upgraded beyond Snow Leopard. My daughter's showed up when upgrading to Mountain Lion.

I don't know about Bootcamp.

Take a look at gfxCardStatus. Some have reduced the number of panics by using that to force it into one card. I don't know if it works with Yosemite.

Jan 9, 2015 3:24 AM in response to Barney-15E

Thanks, Barney. I already use gfxcardstatus, it's a good aid. Besides, I think I found a workaround that is working well for me by now. I found the fix in this post:

GPU Panic - OSX 10.9 Mavericks - Macbook PRO 6,2

The fix forces the discrete card to use the system ram instead of video memory. As far as I see this can help if panics are related with memory r/w errors. In my case, every kernel panic description starts with a "read error". I've spent an entire day testing and I've got no panics, even "stressing" the graphics card (running several games at once, as well as every other app that uses discrete graphics). I still haven't tried adding a second monitor. In the same post some people report this gave their system temporary stability, while there're others who say this fix is still working for them. Here are the instructions:

benolerApr 17, 2014 7:29 AM

Re: GPU Panic - OSX 10.9 Mavericks - Macbook PRO 6,2

in response to cfbbaer

Hello guys,

what fixed the issue of "recurring GPU panics at random times" for me was to alter the Configuration.plist file located in "/System/Library/Frameworks/ApplicationServices.framework/Frameworks/CoreGraphi cs.framework/Resources/".

Just copy that file to the Desktop and edit it with XCode.

Where it sais "ForceSessionDrawsVirtualFramebuffer" change "NO" to "YES"

-> This setting will force the GPU to write data only to the main memory instead of using the VRAM.

Note: i assume this fix only works for GPU panics caused by read access failure (see what your panic dump says).

Note: do not use these settings if you're low on memory.

Hope that helps some of you folks 😉

I used textwrangler instead of xcode to edit the file, setting it to "true" instead of "yes". My macbook has 8gb of ram, expect more ram consumption after applying the fix. I think this could be helpful for those who don't want to spend 300$/€ in a motherboard replacement.

Jan 29, 2015 3:05 AM in response to LouCasa

I am using a 15" Mid-2010 and had the same experience. Somehow Yosemite augments the kernel panic. Luckily I tested Yosemite as a fresh install using a new partition. I also found form Activity Monitor, there was background process that heats up the CPU, thus fan noise - not even a single application installed yet. I decided to revert back to Mountain Lion, although kernel panic still occur, since the upgrade is to risky for my portable office. If Apple ignores this issue, then I think the OS development is discriminative to older Macbook.

My current workarounds to avoid kernel panic:

- During non-graphic/casual office tasks (i.e., writing), as advised by Kappy, I make sure the gfxCardStatus 2.3 is on 'integrated only' mode

- During graphical tasks, or when using external display (i.e., photo editing, creating presentation slide), I use NoSleep to allow 'clamshell mode', or having the screen closed and use external monitor only.

I never encounter a kernel panic with this clamshell trick. However, when CPU usage increasing (e.i. fan noise, mac getting warmer) during clamshell) I put two small cubes of pencil erasers, to create a gap between the lid and bottom case, to keep airflow - but not so wide that it wake up the screen.

Please let me know if any of you had tried similar trick. As a non-native speaker, I hope my English makes sense.

Feb 5, 2015 6:51 PM in response to curreiros

After the same problem was found in Mavericks and Yosemite frequently (Before Mavericks, I didn't see this problem) and I tried to revert my OS to mountain lion, same problem was occurred especially you open iMovie or other graphical apps.

Then I reinstall Yosemite again with gfxCardStatus, problem is still existed but not frequently. Now i am waiting to buy next model of MPB..... 😟

Dhadchi

Level 1

0 points

Feb 22, 2015 2:13 AM in response to LouCasa

Hi All,

I have the same big issue. Kernel panics appeared when I upgraded to Yosemite 2 weeks ago. I kept pushing the upgrade back and thought Yosemite worked fine on the mini I own, so I took the plunge. I cannot believe it happens to me after 4 years! I use gfxCardStatus but the problem is still present, especially when I use a software for my research that requires graphics. I thought reverting back to Maverick would solve this issue, but according to this thread it won't help either.

I will take it to an apple store tomorrow and try to get it fixed for free because it should be!

Apple needs to sort this out. Apple cannot forget about our "old" machines that work as well as the new ones if it wasn't for this default. 😐😠

PS: I'll update you guys tomorrow.

Barney-15E

Level 10

112,782 points

Feb 22, 2015 5:32 AM in response to Dhadchi

Dhadchi wrote:

Apple needs to sort this out.

They did have a free replacement program that ran for three years from the date of purchase. That has since expired. I'm pretty certain they consider it sorted.

Dhadchi

Level 1

0 points

Feb 23, 2015 9:51 AM in response to Barney-15E

Thank you, Barney-15E, for your unproductive comment - I have already read this thread.

The following may help UK/Scottish customers:

Read the following: http://www.apple.com/uk/support/macbookpro-videoissues/
Enter your serial number here to check if you are eligible: https://selfsolve.apple.com/agreementWarrantyDynamic.do
I found out, under consumer law in the UK, that I was entitled to a free of charge repair which expires 6 years from purchase http://www.apple.com/uk/legal/statutory-warranty/

Hope it helps.

Best,

Feb 23, 2015 7:29 PM in response to Dhadchi

Hi DJ,

Hope to see Apple finally helped you to fix for free. I am not in UK and no such warranty from my country 😟

Actually I am thinking if I install windows to that macbook, will it have the same problem?

If yes, I just wonder what will be the error message. Will it be "....AppleMuxControl/kext/GPUPanic.cpp:127" again?

If no, what does it mean then ? hardware fault?

Mar 25, 2015 6:06 PM in response to Barney-15E

I have taken my MacBook Pro 15" mid 2010 into Apple twice for this same problem, intermittent black screen/loss of video. They never mentioned anything to me about a "known GPU fault that requires replacing the logic board". Had the problem again today and searched the web and came across this post. Waisted hours and hours of my time trying to figure it out not to mention all the time i spent at the Apple Store and the several weeks waiting for an appointment. Thanks for sharing your knowledge. Wish Apple had done the same.

MacBook Pro Mid-2010 15" Frequent Kernel Panics