Getting Kernel Panics on a fresh Mavericks installation; Can anyone help analyzing the KP logs? 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:


http://pastebin.com/3CsCHRsg (KP log 24-dec-2013) 
http://pastebin.com/jVmEQsJG (KP log 20-dec-2013)
Your particular MacBook Pro (6,2) has documented GPU problems for some units:

https://support.apple.com/kb/TS4088

http://reviews.cnet.com/8301-13727_7-57577329-263/os-x-10.8.3-forces-discrete-gpu-use-in-2010-macbook-pros/

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: [&lt;None&gt;] 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.