Ask Different is a question and answer site for power users of Apple hardware and software. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Hardware is a mid 2010 MAcBook Pro 15", i7 2,66ghz, 8 GB RAM, 512 MB Video RAM.

I encounter regular kernel panics for a while now, I think since upgrading to Mavericks. Usually it used to happen every now and then, between once a week and once a month. So I did not really worry in the beginning. As it started getting on my nerves and neither volume repair nor hard ware test did indicate anything wrong, I decided to do a clean install of the latest Mavericks version a few days ago to see if that helps. kernel panics are still there and with the update to 10.9.3. today it seems even worse. I already had two kernel panics today, which make it four this week.

Attached is the latest kernel panic log:

Anonymous UUID:       2BA5E44A-7200-45C0-F925-7A3107857DDC

Fri May 16 14:19:00 2014
panic(cpu 3 caller 0xffffff7f8b041f7c): "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 0xffffff8124ee6000 0x0a5480a2, D0, P2/4\n"@/SourceCache/AppleGraphicsControl/AppleGraphicsControl-3.5.26/src/AppleMuxControl/kext/GPUPanic.cpp:127
Backtrace (CPU 3), Frame : Return Address
0xffffff8113f4b140 : 0xffffff8008c22fa9 
0xffffff8113f4b1c0 : 0xffffff7f8b041f7c 
0xffffff8113f4b290 : 0xffffff7f89672e7b 
0xffffff8113f4b350 : 0xffffff7f8973c46a 
0xffffff8113f4b390 : 0xffffff7f8973c4da 
0xffffff8113f4b400 : 0xffffff7f899bb056 
0xffffff8113f4b530 : 0xffffff7f8975fb09 
0xffffff8113f4b550 : 0xffffff7f896798cd 
0xffffff8113f4b600 : 0xffffff7f896773d8 
0xffffff8113f4b800 : 0xffffff7f89678356 
0xffffff8113f4b8e0 : 0xffffff7f8a6699c2 
0xffffff8113f4b920 : 0xffffff7f8a67937f 
0xffffff8113f4b940 : 0xffffff7f8a6a733b 
0xffffff8113f4b980 : 0xffffff7f8a6a739b 
0xffffff8113f4b9c0 : 0xffffff7f8a67ee15 
0xffffff8113f4ba10 : 0xffffff7f8a64ab5e 
0xffffff8113f4baa0 : 0xffffff7f8a646ae7 
0xffffff8113f4bad0 : 0xffffff7f8a644636 
0xffffff8113f4bb00 : 0xffffff80090ce0a3 
0xffffff8113f4bb90 : 0xffffff80090cff9f 
0xffffff8113f4bbf0 : 0xffffff80090cdabf 
0xffffff8113f4bd40 : 0xffffff8008cb66a8 
0xffffff8113f4be50 : 0xffffff8008c26bf1 
0xffffff8113f4be80 : 0xffffff8008c139f5 
0xffffff8113f4bef0 : 0xffffff8008c1e043 
0xffffff8113f4bf70 : 0xffffff8008cc989d 
0xffffff8113f4bfb0 : 0xffffff8008cf3c76 
      Kernel Extensions in backtrace:[6EB3FF52-A4F6-3496-AE9C-D89B00FDE504]@0xffffff7f89623000->0xffffff7f8988bfff

BSD process name corresponding to current thread: WindowServer

Mac OS version:

Kernel version:
Darwin Kernel Version 13.2.0: Thu Apr 17 23:03:13 PDT 2014; root:xnu-2422.100.13~1/RELEASE_X86_64
Kernel UUID: ADD73AE6-88B0-32FB-A8BB-4F7C8BE4092E
Kernel slide:     0x0000000008a00000
Kernel text base: 0xffffff8008c00000
System model name: MacBookPro6,2 (Mac-F22586C8)

System uptime in nanoseconds: 4401259546857
last loaded kext at 3670375376124:   104 (addr 0xffffff7f8b144000, size 49152)
last unloaded kext at 3786700867221: 104 (addr 0xffffff7f8b144000, size 32768)
loaded kexts:
at.obdev.nke.LittleSnitch   4092  1.9.5d0   80.14  1.60   100.14.15    4.2.4f1    3.0    124   2.6.1f2  1.0.0d1   7.0.0  1   2.6.1f2    2.0.4d1    3.5.26    1.0.0  8.2.4    3.5.13   1.1.12   8.2.4 8.2.4 4.2.4f1   1.0.0   1.7.0    3.0.4d1  240.2  325.7 240.2 1.0.0d1 1.0.0d1 35 3.4.1  3.6.6 404  2.5.1    666.4.0   700.20.22    3.8.1b2    5.0.2  3.0.0   660.4.0   161.0.0   2.0   2.0  1.8    2.1    2.0  1.7 217.92.1   153   3   217.92.1   4.2.4f1  245.13    3.5.26  10.0.7 1.0   91.1   4.2.4f1 2.6.1f2   1.0.0   1.9.7fc2    1.14   3.5.26 1.0.0  1.0.12d1   1.0.4    2.2.6   1.0.11d1   8.2.4    8.2.4   2.4.1   4.2.4f1 2.6.1f2    2.4.1 2.6.1f2 5.7.0d11   3.1.8    2.5.1  4.2.6 240.9  660.4.0   3.6.6   3.6.0   650.4.0  656.4.1  3.6.6   1.7  1.7.1   1.7.1   2.6.1   3.6.6 660.4.2   630.35 1.0.3b4  1.0.1b5  3.2    4.5.5    2.6.5 677.4.0  2.0    2.0 2.0.0   1.1  278.11   1.0.0d1  7  2 371.1 1.9  23   28.30  2.0 2.9    1.4    1.0   1

Does anyone have any idea what the problem might be or how to track it down? Might the video card or kernel extension be the problem? Any help would be highly appreciated.

share|improve this question
Hey Ben, did apple repair you Macbook with a new Logic Board for free? – bMalum Aug 27 '15 at 6:22
Yes, they did. Though it took a few phone calls and several days from confirmation of the known GPU error before they finally agreed to replace for free. – Ben Aug 30 '15 at 21:24
up vote 6 down vote accepted

Yes the GPU panics are almost certainly due to a defective discrete GPU card. I have the same 2010 MBP and have noticed 10.9.3 has increased the frequency of these fatal crashes significantly.

I'm using the gfxCardStatus utility to turn off this discrete card whenever possible but many apps force it on.

share|improve this answer
I use the same program, but unfortunately can't disable discrete with an external monitor.. – Jacksonkr Jul 14 '14 at 16:57
This series of laptops (2010-2011) with the discrete GPU have a known issue with the GPU that Apple seems perfectly happy not to do anything about - like a recall, or similar. There are many of them in the wild with defective GPU cards, but Apple is treating each occurrence as if they have never seen the problem before. I had a 2011 17" MBP that thankfully did NOT have the problem, but selling it second hand was surprisingly difficult, as the local shops all said they won't touch those models with a ten-foot pole. I guess the discrete GPU is just a case of "another thing to go wrong" ... – Scott Earle Oct 10 '14 at 10:28

Repeated kernel panics occurring without third party drivers can only be caused by a few things:

1) A peripheral device

2) A bad OSX image or bug in OSX itself

3) A hardware problem

In your case, it is unfortunately (3):

System model name: MacBookPro6,2

The kernel panic indicates that your GPU is failing. This is a known issue for your machine. Your model is subject to a replacement program for the logicboard due to a defective GPU. It lasts 3 years from the date of purchase. If this is already expired, Apple may or may not still replace your logicboard. It is ultimately at the discretion of the store manager. If you don't qualify, your other option would be a flat rate repair, for ~$300, which Apple will repair anything wrong with the machine for this fee. Best of luck.

share|improve this answer
+1 I also suffer because of this for about half year now. Unfortunatelly It has begun after 3 years of purchase. – Mateusz Szlosek May 16 '14 at 13:37
Thanks for your reply. I am just out of the 3 year since purchase... – Ben May 16 '14 at 13:39
I have had good luck with getting Apple to do the right thing on hardware a little past warranty expiry. – Andrew Lazarus May 22 '14 at 19:22
Both the Apple Store and Apple Support told me to shell out the cash because my 4 yr applecare warranty had just lapsed. I fear Apple has become the new Microsoft.. – Jacksonkr Jul 14 '14 at 16:59

After a few arguments with a local Apple Store I contacted national Apple management and argued that the problems only started after upgrading to Maverick, which happened three years after purchase. Since they never mentioned Maverick would cause problems on a 2010 MacBook Pro the replacement program should still be applied. They finally agreed.

share|improve this answer

Apple has issued a recall for Macbook Pros Mid 2012. Others may be in the recall. I took it to a store and they had to replace the Logic board ($1000). Thankfully I did not have to pay a cent due to the recall. If you have "GPU Panic" based screen blanks, take it to Mac Shop/Repair shop and they will take care of it. They will run a diagnostic and in 20 mins you will know if it is eligible.

This is not a software issue. Apple would have taken care of it that way. Reinstalling the OS is not an option.

This is a hardware issue. Logic board needs to be removed. Go to a mac store.

Read about the recall here:

share|improve this answer

Seems like using the Kext Utility to clear and repair my kext permissions and doing a clean boot fixed this issue for me. Only tested for a few hours now but so far so good. Many people get a logic board replacement but I think it may have been a kext issue as every time I upgrade I run into kernel panics at some point. I push my machines to the limit and run into panics every 10 or so minutes when running on "Discrete GPU" only.

Now I can enable automatic switching without any problems. Hope this helps someone.

share|improve this answer

Im surprised that nobody on any forums has even touched on this answer i'm about to give and i HAD the exact same issues with mine that most ppl have been having.. So heres what ive found is the root of mine and a few ppls computers ive fixed due to gpu panics.. If you have corrupt or unsupported .jpeg, .mpeg, .mp4, PDF, or any related formats on your hd, it will cause GPU panics to happen.. So the best way to figure it out before thinking that your GPU is fried is get Tech Tool Pro or a similar app and do a file optimization test. On TTP it will tell u which ones and exactly where they r located.. I made the mistake of "upgrading" from Mavericks to Yosemite, and it messed everything up.. I ended up with over 1000 unsupported or corrupt files in those formats because of the "upgrade". It took a couple of painstaking hours to remove the files manually, but the panics have virtually stopped.. And my panics where absolutely infuriating.. I would turn my computer on and if i ran more than 1 or 2 apps at once, it would double panic, then 10 minutes later, it would do it again out of nowhere.. So a simple thing like taking all of those corrupt files fixed it.. Im amazed that all those "support techs" or "gurus" that work for mac havent shed any light on this, because its kinda common sense that would be one of the first things they should be thinking of when troubleshooting this VERY common issue! Hope this helps! If it did, please leave a like or comment, so i can keep personal track myself of how many headaches this might help be avoiding! ;)

Use Tech Tool Pro or related software that has a file optimization feature and remove all corrupt or unsupported files that I listed above.

share|improve this answer
As written it's hard to understand what your actual answer is here. Future visitors probably are more interested in the steps you recommend to analyze/fix this than in your overall experience analyzing this. Could you try to turn your answer into more of a list of instructions on how to proceed? – patrix Oct 24 '15 at 13:49
Sorry, i thought it was clear... Use Tech Tool Pro or RELATED software that has a FILE OPTIMIZATION feature and REMOVE all CORRUPT or UNSUPPORTED files that i listed above. Does that clear things up? – Stevie James Oct 25 '15 at 18:42

protected by Community Oct 25 '15 at 19:43

Thank you for your interest in this question. Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site.

Would you like to answer one of these unanswered questions instead?

Not the answer you're looking for? Browse other questions tagged or ask your own question.