Getting Kernel Panics on a fresh Mavericks installation; Can anyone help analyzing the KP logs?

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:

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: [<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.