Nvidia Video Card Wont Store Overclock

**tesco** · 02-07-2004, 04:48 AM

Ive been having a problem with my videocard where i overclock it and apply t and i say to reapply when i restart but after i restart it goes back to normal. ive had this problem for a long time. i reinstalled windows but still have the problems. i used the coolbits registry edit thing and set it to 3 which it said to do.

now after i restart it restest back to the default clock setting.

card is a gefore mx 440 128mb ddr 8x and im using the 53.03 (latest) driver. can anybody help me out?

**atiVidia** · 02-07-2004, 04:50 AM

2 things

1: ur holding ctrl on start...

2: ur overclocking more than the chip can handle

wtf r u overclocking an MX anyway???

**tesco** · 02-07-2004, 04:58 AM

well im having problems with some games (actually only ones i play are combat flight simulator 98 and need for speed underground) and both of them stutter ocasionaly but i have no problems at all if i put up the clock of the core so thats what i do everytime i want to play but my dad doesnt know how to overclock it and he is the one that plays combat flight simulator so he has to overclock it.

and i tried holding ctrl but that resets it...

**_John_Lennon_** · 02-07-2004, 04:59 AM

What makes you think that the card is resetting itself?

Also btw, the MX cards are good overclockers in terms of Mhz, seeing as how they have quite a bit of head room.

**tesco** · 02-07-2004, 05:10 AM

uhh i think its resetting itself because i look back at the overclock and it says 270mhx but im setting it at like 350 lol. and you might think that that isnt affecting it since its such a high voerclock but it is making games run better, and efter i restart it runs crappily until i overclock it again, whether it be by 5 mhz or 100 so can anybody tell me why it is resetting?

**_John_Lennon_** · 02-07-2004, 05:11 AM

So even when you try to overclock it by only 5 Mhz, it gets reset after you restart your computer?

What OS are you running........

**tesco** · 02-07-2004, 05:15 AM

windows xp pro with sp1 and im using the latest drivers...could that be a problem, im thinking the problems started around december (when the 53.03 drivers were released) maybe ill try the 52.16 or 45.23 drivers iunstead see if that fixes it if nobody knows what is wrong, anybody got ideas?