twztid13

The 310.33 made my card downclock somehow. It lowered the kepler boost by 5 to 1241, and the only change was the new driver (it was still 1246 after the Precision X update earlier in the week). I have the same issues as others where my Precision X v3.0.4 offset can no longer be changed in 1 point increments (it just ignores them until you get to a number that makes the clock go up by 11 - 13). Formerly, I had +70 to get a 1246 kepler boost clock. Now, with the 1241 at +70, it changed nothing from +71 to +75, but +76 to +80 gives me a 1254 kepler boost clock (adding 13 for anywhere from +6 to +10 offset increase). Same issue on the memory clock. Mine was 3375 with a +272. When I went up +5 to +277, it raised the clock by 11 to 3386, which isn't accurate, but only 1 point off. When I lowered the offset just 1 point to +276, it goes back to 3375...down 11 clocks. WHY, Nvidia??

Oddly, my GPU-Z reading says I lose 0.3 GPixel Fillrate with the higher clock (I stuck with the 1254 clock, with a +79 to try & keep it like it was in case they fix this, and it's not an intentional direction) & new drivers (37.7 to 37.4 GPixel/s)... This SUCKS!! Anyone else have similar situation?

Also, I just played BF3 for a couple of hours, and it played great. No crashes on this driver (just info for the peeps that were having issues).

MitchB84

BF3 freezes with these drivers. Ctrl-alt-del gets me back to the desktop where I see the "battlefield 3 has stopped responding" error message. I reverted back to 306.97 and it has not happened thus far.

twztid13...my Precision X v3.0.4 offset can no longer be changed in 1 point increments (it just ignores them until you get to a number that makes the clock go up by 11 - 13). Formerly, I had +70 to get a 1246 kepler boost clock. Now, with the 1241 at +70, it changed nothing from +71 to +75, but +76 to +80 gives me a 1254 kepler boost clock (adding 13 for anywhere from +6 to +10 offset increase). Same issue on the memory clock. Mine was 3375 with a +272. When I went up +5 to +277, it raised the clock by 11 to 3386, which isn't accurate, but only 1 point off. When I lowered the offset just 1 point to +276, it goes back to 3375...down 11 clocks. WHY, Nvidia??...

rjohnson11

I couldn't get these drivers to work on Windows 8 even though they are for Windows 7 and 8. All I got was a black screen. 

zerox3

uploaded 2 things i noticed with the stuttering  on the 306.97 i noticed when i was using abilitys and monitoring evga precision my GPU usage was fluxing like a crazy mofo, and on the 310.33 beta my gpu power was fluxing when the stuttering was going on ( k boost enabled ).

HAZMAN_THE_GREAT

tarpon31

Overall great driver's for me.

The physx driver for me did not work though. The first test I used was the metro benchmark and it black screened on me and would not run so I uninstalled the physx driver and went back to physx driver 9.12.0613 and everything works fine.

From experience in the past with corrupted physx driver's the metro benchmark has always shown me right away wether they are corrupt or not.

Ya dude for some reason my PhysX driver did not install right. I installed these drivers three times and I still come up with the same corrupted icon in for the PhysX down in the pic below. I ran Batman Arkaham City with the games PhysX all the way turned up and the game has not crashed on me. BUT I remember this happening before and Batman crashed on my like every time because the PhysX driver got corrupted when I was installing my drivers for some reason. I wonder if anyone else is seeing what I am seeing.

Warboy

manuelg_nvidia

tarpon31

Overall great driver's for me.

The physx driver for me did not work though. The first test I used was the metro benchmark and it black screened on me and would not run so I uninstalled the physx driver and went back to physx driver 9.12.0613 and everything works fine.

From experience in the past with corrupted physx driver's the metro benchmark has always shown me right away wether they are corrupt or not.

We had an installer bug which causes the Physx processor to be set to CPU.  Check if it is set to CPU, AUTO or your GPU in the NVIDIA Control Panel.  If you still have problems, please try to manually uninstall your drivers and then re-install driver R310.33 and let me know if you still encounter Physx issues with Metro 2033.

I just wanna mention that I have confirmed in a test that FPS thing I said earlier in NFS Most wanted [2012]
FPS in 310.33 is lower then in 306.xx
I don't know if it's the AO feature quality or another graphical thing causing it.  But it effects performance on 310.33 by 20-30%, I'm able to run 2560x1440 at 55fps on 306.xx, But unplayable on 310.33, 306.xx solid 60 at 1080p, 310.33 weak 40-50fps at 1080p.

manuelg_nvidia
Can you give me more details?  What map?  What graphic settings are you using?

[Display]
SSAOLevel=2
LockTo30=false
HiResTextures=true
FitToVertical=true
ParticleShadows=true
HeadlightShadows=true
Scattering=true
FrameLatency=0
MotionBlurLevel=3
ReflectionDetailLevel=2
LodScaling=3
VfxDetail=3
ScreenScale=0
Brightness=0
Contrast=0
Width=2560
Height=1440
GammaRamp=1.000
[Hardware]
AdapterNumber=0
OutputNumber=0
[Settings]
ShadowMapLevel=3
Webcam=true
[Sound]
MusicVolume=0
SfxVolume=10
SpeechVolume=10
SpeakerSetup=1
Reverb=1
[Gameplay]
EnableVibration=true