Since a couple of weeks, my MacBook Pro has been experiencing random kernel panics. I believe these kps started after installing Mavericks (although I am not completely sure). I decided to do a complete fresh install of Mavericks, without restoring it using TimeMachine. All went well for a while, until last week, in which I had two KPs again.

The crashes seem completely random and are pretty rare. I think I had a little less than 10 KPs in two months time. So the fact that all went well for a while lately doesn't mean much I think; probably pure coincidence... I have a MacBook Pro late 2010 15 inch, 2.53 GHz Intel Core i5 and I run OS X 10.9.1. The kp logs always report about a GPU panic in the beginning.

I have quite some stuff running on my mac, including stuff that interacts pretty directly with the core of the OS. This includes NoSleep (which is practically never running, but I know it installs some kexts which I can imagine being loaded even if the actual NoSleep program itself is not running), Tuxera NTFS, RightZoom, TotalFinder, Parallels 8 and iStat Menus. All run on the latest updates. Maybe I should make the upgrade to Parallels 9, as it is currently my main suspect. I have been running a lot of VMs lately, and it is very well possibly that it had been running every time a kp occured. However, I rather not make the paid upgrade as I am Dutch ;)

Could anyone help analyze the KP logs? I am clueless...

I posted the last two here:

  • I would be more interested in seeing the dates / times of all crashes. If you can start to identify patterns when they arrive, it might be easier than going down Apple's support page in how to isolate the cause of panics on Mavericks. However the two you posted look like GPU hardware issues and the answer below makes a call to Apple Support my first recommendation to see if they will fix things on their dime.
    – bmike
    Dec 24, 2013 at 14:16
  • It turned out I had a faulty GPU. This was indeed a common problem of the 15inch mid 2010 Macbook Pro. It had an extended warranty of 3 years because of this problem. Unfortunately it is already 3.5 years old, so I had to pay for replacing the motherboard. They detected and fixed it within a day at the apple store, but it cost me nearly 500 euros: a lot of money!
    – koenlek
    Dec 30, 2013 at 14:00
  • Ouch and glad it's sorted with a replacement CPU/GPU.
    – bmike
    Dec 30, 2013 at 14:59

2 Answers 2


My mid 2010 15 inch Mac Book Pro is in for a logic board replacement right now for what looks like the same issue. At least the first line of the log you posted is identical to the ones I was having. Apparently a run of nVidia graphics chips used in that vintage of 15 inch MBPs had a "latent defect". The bug can be tickled or not depending on the applications you are running and also the OS revision -- different releases of OS/X use the graphics hardware in different ways. My panics really got bad after upgrading to Mavericks, like yours -- though I had a few, very few and far between (<< 10 in all) before the upgrade.

When you take it in to Apple, be sure that they run what is called the VST test. The Apple stores do NOT run this test routinely even though it only takes a few minutes. Even after telling the Genius who took my machine in that I wanted this test run, and even after the test appearing on the work order, they did not run it until I insisted over the phone (their recommendation was to wipe the disk clean and do a fresh OS install). This was after they had run every other diagnostic on it for two days and pronounced the panics software related. Of course, it failed the VST test, and as I said, is now having the logic board replaced.

BTW this is the TS4088 issue, and although you should be within the 3-year window or just barely out of it, many Apple stores will still pick up the tab for this since it is a known problem.

Good luck.


Your particular MacBook Pro (6,2) has documented GPU problems for some units:



Even if you think you are out of warranty coverage, a call to Apple would be a good move. You've done most of the troubleshooting by cleanly installing Mavericks and still see the panics. Also the first line with details sure points at persistent GPU code involvement in the panics:

 panic(cpu 0 caller 0xffffff7f9d838fac): "GPU Panic: [<None>] 3 3 7f 0 0 0 0 3 : NVRM[0/1:0:0]: Read Error 0x00000100: CFG 0x0a2910de 0x00100000 0x00000000, BAR0 0xd2000000 0xffffff812f8cc000 0x0a5480a2, D0, P3/4\n"@/SourceCache/AppleGraphicsControl/AppleGraphicsControl-3.4.12/src/AppleMuxControl/kext/GPUPanic.cpp:127

You could also run sysdiagnose and file a bug report with Apple in case this is software instead of hardware - these repeated panic logs would give the engineers a good idea exactly where the code is getting nonsense values from the hardware and perhaps decide to handle it less harshly as far as the user is concerned.

  • it's in the crash log System model name: MacBookPro6,2 (Mac-F22586C8)
    – l'L'l
    Dec 24, 2013 at 14:00
  • Based on the assumption that you're seeing more than 20 panics a week, hardware is very likely per the link above where Apple has a service repair option and a specific knowledge base article on the exact symptom you report. I've also added my read on the panics above in hopes that @IconDaemon doesn't mind.
    – bmike
    Dec 24, 2013 at 14:18

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .