Ouch. I have the same mac (mid 2010) and have experienced the same error two times now.
I had a lot of panics earlier and Apple changed my motherboard. This was back in april or may this year.
After that all problemes was gone until now. First panic was aug 26 and one more today aug 29. This is not good.
What our it-maintenence guy said to me after reciving the mac back from when they changed the motherboard was that it will happen again after some time (I think both he and me thought it would be at least two more problem free years). As in the problems will come back because it is still the same motherboard (just a replacement but same model). He also said the second time they will not change it as a warranty. I do not know way and I do not know if this is actually the case.
Anyway...seems I am back to where I was. This is just not cool.
I got the exact same problem on the same Macbook Pro, Mid 2010, OS 10.8.5
panic(cpu 0 caller 0xffffff7f92896f1a): "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 0xffffff809d0e9000 0x0a5480a2, D0, P3/4\n"@/SourceCache/AppleGraphicsControl/AppleGraphicsControl-3.4.5/src/AppleM uxControl/kext/GPUPanic.cpp:127
I brought my Macbook to Apple store, they checked HW, memory, etc. no problem found. They re-installed the OS, etc.
Brought it home, the problem is still there.
I will have to come back again. Thanks for the posting.
This really, really, really stinks. And what's worse, it's the second time I literally have a major malfunction 1-2 months out of warranty.
My MB Pro was purchased on 8/22/10. With the extended warranty my device would've been covered until 8/22/13. Over the past month I've encountered this same exact issue. Started small and did it a couple times over 2 weeks. This past week it's reset itself 6 times, twice today.
Why if they had a known issue that they were extending warranties for wouldn't they contact people with affective devices.
I looked up that part number that another user had replaced, 661-6362, the best I can find it for is $926. This is crap. I had a full logic board failure on my mac mini at 13 months. It's now a paperweight. I can't afford to keep paying the Apple premium for this stuff that is junk. Never had these problems on Windows devices.
I bought my machine back to the Apple store and brought along: i) the error report, ii) the forum discussion.
After a few days, I was informed that the logic board will be replaced free of charge.
After another week or so, I was called to pick up my MBP.
Apple handled this problem professionally. I just wished that the staff was more knowledgeable so that I did not waste my time going back and forth.
Mavericks doesn't fix it. Things seemed fine for a couple hours after installation, but issues surfaced after that and I've had 4 kernel panics with Mavericks so far in just a few hours of use. I went back to 10.6.8 to get work done during the day.
As my machine is 3.6 years old and I'm the third owner, Apple doesn't seem overly interested in paying for the repair. I'm still trying.
I would happily accept a software fix. If this machine can work perfectly well with 10.6.8, I don't see how that knowledge can't be used to fix this issue in software. This would save a lot of time for customers and potentially a lot of money for Apple (who is still doing free repairs for quite a few customers).
BTW, Nvidia just released a new CUDA installation package yesterday. Doesn't help at all. One of the known issues with that library sounds awfully lot like the issue we are having: if the GPU goes to sleep for any reason at all, it will cause a kernel panic later on.
I did some heavy graphics testing right after installing Mavericks. The GPU didn't have a chance to sleep (I was playing Quicktime & Youtube videos + some screen savers non-stop) and things seemed fine. When I let the computer just sit there for a while, I think it powers down the GPU to save energy (even if the GPU switching is turned off) and the machine will usually panic a few minutes later.
I've been using 10.6.8 partly because I didn't get good results with Lion & Mountain Lion. I seem to remember having the kernel panics then and I figured it was just a bad OS version, so I went back to what I knew worked well. Now I'm miffed because when I was forced to abandon Snow Leopard (software compatibility), I found that it was too late to qualify for Apple's repair program.
Apple: put some good low level software engineers on this and issue a patch that fixes the problem.
This is my second MacBook Pro in a row with a failing nVidia GPU. The previous one was the Santa Rosa (8600M) - the internal display has completely failed, so instead of even trying to get it repaired, I'm just using it as a multimedia player in my bedroom (even though a certified Mac service provider told me that the GPU is failing). I do my work on MacBooks, but these repeated issues make me extremely wary about trusting yet another MacBook with an nVidia GPU (and I think I want more than integrated Intel graphics).
Just keeps getting better. Gotta fortune invested in this Mac 15 and this happens. Yep, I am on maverick too. Like Maverick. But this started with Mountain lion, I do wonder because on the original snow leopard I had no issue with graphic problems. I'm having a bad month people, bleeding money... don't need this too. AARRgh!
I just got mine back from the Apple service provider. No crashes yet, but I've only had the machine for an hour or so. Take your machine to an Apple Store (genius) or Apple Service Provider and ask them to test for TS4088:
You might still be able to qualify for a free or reduced cost repair. For Apple's sake, I hope they figure out a software work-around for this problem - replacing logic boards can not be cheap.
Pretty much everyone has the same symptoms: Snow Leopard is 100% fine, but anything after that will cause Kernel Panics. As a technically savvy person, I'm really curious to know why Snow Leopard doesn't trigger the issue.
A clean system installation would of course be a good idea to try. The same panic has been found on a lot of 2010 MacBook Pros and it happens even on a cleanly installed system. It's theoretically possible that some malware might be infecting MacBook Pro firmware and causing the issues, which would also explain why a log board swap could fix it.
Third party kernel extensions can cause serious problems. Badly installed Apple kernel extensions can cause problems too. A lot of really experienced Mac users have tried to fix this problem and so far the only solutions I have seen are:
1) Use Snow Leopard and don't upgrade.
2) Get the hardware repaired.
3) Use the MacBook with the discrete GPU disabled - easier said than done. gfxCardStatus can be used to switch between the discrete and integrated graphics...the setting just doesn't stick very well and prevents you from using external monitors.