Problem with Forceware going into "safe mode" - Overclock.net

Rayce185 · 08-11-09

So I was tweaking my OC clocks of the GTX 275, and, as what normally happens when I clock too high, the screen flickers for a bit and I get the Forceware baloon message in the tool bar that there was an issue. EVGA Precision shows me that the clocks are crazy low (400/799/297). I would normally just reboot and the clocks would be set back to stock.

Not this time.

Even when setting standard clocks in Precision, they stick at these low values, even after multiple reboots.

a) How can I resolve this?
b) Is this some kind of self-protection mechanism from the driver? How can I deactivate it?

Thanks in advance for any help.

Bazmecc · 08-11-09

might have corrupted the drivers somehow...try a cleanup and reinstall of the drivers

FSF-Foxhound · 08-11-09

I am taking a look in the riva tuner registries, maybe you can force it back to regular 3d performance clocks.

I hate it, too.

I think it might be unchangeable, because it is a protection thing afaik, as when the driver fails it is to protect it..

I would just restart, it isn't that big of a deal once you find the final OC of your card.

I think all 200 series do it.. My 9000 series cards just reset back to stock clocks when it crashes. I wish this did it too!

Bazmecc · 08-11-09

Quote:

Originally Posted by Rayce185

they stick at these low values, even after multiple reboots..

hey Foxhound

FSF-Foxhound · 08-11-09

Quote:

Originally Posted by Bazmecc

hey Foxhound

huh D:

remind me D:

		Overclock.net - Overclocking.net > Graphics Cards > NVIDIA > NVIDIA Drivers and Overclocking Software
Problem with Forceware going into "safe mode"

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)