Overclock.net › Forums › Graphics Cards › NVIDIA › NVIDIA Drivers and Overclocking Software › New driver cause previous stable overclock to become unstable?
New Posts  All Forums:Forum Nav:

New driver cause previous stable overclock to become unstable?

post #1 of 4
Thread Starter 
Hey,

My question is whether a new driver (290.53) can cause a previously stable overclock to become unstable? I'm asking this because I have my ASUS Geforce GTX 560 DC II OC OC'ed to 950/1200/1900 on 1.037V (was previously on 1.087V but found this is also stable) from stock 1.025V and it worked great with driver version 275.33. After I updated from 290.53, after 2.5-3 hours of mw3 the screen turned black for a few seconds and the voltage throttled (Assuming OCP) killing GPU Usage and FPS dropped when I went back to game. Can a new driver cause this to happen (Assuming it caused OCP to kick in for some reason)? I've been playing mw3 for 2 hours so far on the above OC with 1.037V with no issues and temps in the mid-high 40's with a max of 50.

Specs:

AMD Phenom II x4 970 BE OC'ed to 3.79Ghz
16gb of G-Skill RAM
ASUS Geforce GTX 560 DC II OC
OCz Modxstream Pro 500W PSU
ASUS Crosshair IV Formula Motherboard

Thanks,

Black_Shark
post #2 of 4
Reset card to stock vales and use my nvidia uninstall guide to reinstall the latest nvidia beta drivers and retest.
X79-GCN
(22 items)
 
  
CPUMotherboardGraphicsRAM
Intel 3930K 4.5GHz HT GIGABYTE GA-X79-UP4 AMD R9-290X GEil Evo Potenza DDR3 2400MHz CL10 (4x4GB) 
Hard DriveCoolingCoolingCooling
Samsung 840 Pro 120GB EK Supremacy (CPU) NF F12's P/P (360 Rad)  NF A14's (420 Rad)  
CoolingCoolingCoolingCooling
XSPC Chrome Compression Fittings EK RES X3 150 Primochill PremoFlex Advanced LRT Clear 1/2 ID EK-FC (R9 290X) 
CoolingCoolingCoolingOS
EK D5 Vario Top-X  Phobya G-Changer V2 360mm Phobya G-Changer V2 420mm Win 10 x64 Pro 
MonitorKeyboardPowerCase
BenQ XR3501 35" Curved Corsair Vengeance K90 Seasonic X-1250 Gold (v2) Corsair 900D 
MouseAudio
Logitech G400s Senn HD 598 
  hide details  
Reply
X79-GCN
(22 items)
 
  
CPUMotherboardGraphicsRAM
Intel 3930K 4.5GHz HT GIGABYTE GA-X79-UP4 AMD R9-290X GEil Evo Potenza DDR3 2400MHz CL10 (4x4GB) 
Hard DriveCoolingCoolingCooling
Samsung 840 Pro 120GB EK Supremacy (CPU) NF F12's P/P (360 Rad)  NF A14's (420 Rad)  
CoolingCoolingCoolingCooling
XSPC Chrome Compression Fittings EK RES X3 150 Primochill PremoFlex Advanced LRT Clear 1/2 ID EK-FC (R9 290X) 
CoolingCoolingCoolingOS
EK D5 Vario Top-X  Phobya G-Changer V2 360mm Phobya G-Changer V2 420mm Win 10 x64 Pro 
MonitorKeyboardPowerCase
BenQ XR3501 35" Curved Corsair Vengeance K90 Seasonic X-1250 Gold (v2) Corsair 900D 
MouseAudio
Logitech G400s Senn HD 598 
  hide details  
Reply
post #3 of 4
Thread Starter 
Already reinstalled 275.33 using clean reinstall guide. After 3 hours of mw3 at OC, no problems whatsoever. Stable as a rock.

** Just followed your uninstall guide and am reinstalling 290.53. Will report back sometime tonight/tomorrow with results. In the meantime, does anyone know the answer to my previous question?
Edited by Black Shark11 - 1/20/12 at 6:22pm
post #4 of 4
Thread Starter 
Maybe my problem was that it was an unstable OC. OCCT found quite a few errors within 10 seconds of the test starting so I kept downing the clocks until I finally got 0 errors during a 15min test.

OC........................Stock............Reference
940Mhz Core vs. 850Mhz Core vs. 810Mhz Core
1100Mhz Memory vs. 1050Mhz Memory vs. 1001Mhz Memory
1880Mhz Shader vs. 1700Mhz Shader vs. 1620 Shader
1.087V vs. 1.025V vs. 1.000V

This OC has 0 errors in 15 min of OCCT 4.0 Beta (Shader complexity= 3 as recommended by OCCT and fullscreen) and no artifacts or issues in COD: MW3 in a 2 hour testing session which had previously revealed unstable OC's. Thats a 16% increase over the reference card, not too shabby since ASUS limits my voltage to 1.087V and its aircooled.
New Posts  All Forums:Forum Nav:
  Return Home
Overclock.net › Forums › Graphics Cards › NVIDIA › NVIDIA Drivers and Overclocking Software › New driver cause previous stable overclock to become unstable?