post #1 of 1
Thread Starter 
I found the 320.49 driver to be VERY stable when I was using windows 7.

When I upgraded to windows 8, I installed the windows 8 version of this driver from nvidia's site but I've been having nothing but issues...

I tried 320.49, 327, and the may whql 320 driver. All of them make BF3 crash with a direct x error:

device hung due to badly formed commands.

Why does it do this?

At stock clocks and volts it crashes.

With my OC profile I can get through valley benchmark just fine... scoring a decent 2030.

3dmark11 is fine.



The confusing part is that when I get this error, my OC profile (if it is running) stays. Usually when the driver crashes, the OC profile resets to stock. However, since it does not reset, I'm assuming the card isn't the problem but rather something is wrong with windows 8... or the windows 8 version of the driver...

can someone shed some light on this?

my 670's highest stable OC is 1215mhz core and 7450mhz memory in valley. highest stable bf3 is 1215/7300 so I run the game at 1215/7204 just to be safe. Never had an issue with those settings... but now when it crashes at stock i'm not sure if its windows 8 being bad or what...
    
CPUMotherboardGraphicsRAM
i7 3770k @ 4.8ghz z77 sabertooth EVGA GTX 980 TI Classified corsair vengeance 16gb 
CoolingCoolingCoolingCooling
corsair h100 2x coolermaster megaflow 200mm 1x coolermaster 140mm 4x cougar vortex 120mm pwm 
OSPowerCase
windows 7 professional corsair tx750 coolermaster haf x 
  hide details  
Reply
    
CPUMotherboardGraphicsRAM
i7 3770k @ 4.8ghz z77 sabertooth EVGA GTX 980 TI Classified corsair vengeance 16gb 
CoolingCoolingCoolingCooling
corsair h100 2x coolermaster megaflow 200mm 1x coolermaster 140mm 4x cougar vortex 120mm pwm 
OSPowerCase
windows 7 professional corsair tx750 coolermaster haf x 
  hide details  
Reply