How do you refresh the true clock reading display? I cannot find a registry key for "AllowPLLaccess" either. When I first installed the new version of RivaTuner, It appeared the clocks were reading at my overclocked settings. I reset to defaults and rebooted. Now all they read are the default values.<br> <br> UPDATE: I figured out where the registry entry goes and entered the key for it. It still does not appear that my card has new, overclocked settings, but is still at the default according to the "real" clock readings. How do I know the true settings of my core and memory clocks?<br><br><i>This message was edited by carterpa on 01 Oct 2001 02:56 PM</i>
> When I first installed the new version of RivaTuner, It appeared the clocks were reading at my overclocked settings.<br> <br> It must be so.<br> <br> > I reset to defaults and rebooted. Now all they read are the default values.<br> <br> It must be so too <IMG SRC="smileys/wink.gif"><br> <br> I'm afraid that I don't understand what's a problem.<br> <br> > How do I know the true settings of my core and memory clocks?<br> <br> They are displayed in RT. You may check it up with PowerStrip or any other utility, which reads PLL directly.<br> <br> <br> <br>
I'm sorry. I did not explain myself adequately. Let me take you through these steps.<br> <br> Driver settings were 220/515. Real clock settings were 220/515.<br> <br> I changed memory to 520.<br> <br> Driver settings were 220/520. Real clock settings were 220/515.<br> <br> Real settings did not change to reflect new overclocking values.<br> <br> I changed to default. I rebooted.<br> <br> Driver settings were 200/460. Real clock settings now 199/458.<br> <br> Applied new overlocking values through RivaTuner. Tested, applied and saved.<br> <br> Driver settings now 220/520. Real clock settings still 199/458.<br> <br> What is correct? Why isn't the real clock reflecting the new settings even after a reboot?<br> <br> DetXP, Win98SE
Not being funny here but have you checked the "Apply Overclocking at Windows startup" button:<br> <br> <IMG SRC="http://www.btinternet.com/~neeyik/images/rtoverclock.jpg"><br> <br>
Yes, I have that box checked. It appears as yours does, but with the overclocked settings of 220/520.<br> <br> <IMG SRC="http://home.att.net/~pecarter/RivaTuner.jpg"><br><br><i>This message was edited by carterpa on 02 Oct 2001 03:50 PM</i>
Through no further action of my own, no reboots, etc., I checked RivaTuner later and found the real clocks had changed. Alex, how does the program refresh the real clock values?<br> <br> <IMG SRC="http://home.att.net/~pecarter/RivaTuner2.jpg"> <IMG SRC="smileys/smile.gif">
> Driver settings were 220/520. Real clock settings were 220/515.<br> <br> The driver can report wrong frequencies. It can report double clock freuqency on some SDR boards. I can report wrong frequencies after stanby mode. That's why I've added low level clock frequency monitor - now it allows to control the driver's report. Just try to make an experiment - try to model the situation which u've described and check the clock frequencies with PowerStrip if you don't beleive RivaTuner's report.<br> <br> > Through no further action of my own, no reboots, etc., I checked RivaTuner later and found the real clocks had changed. Alex, how does the program refresh the real clock values?<br> <br> The program refreshes the real clock frequencies each time you are activating Overclocking dialog. It is also refreshed each time when RivaTuner is changing the clock frequencies via the driver (i.e. before/after clock frequency testing and after Apply button).<br><br><i>This message was edited by Unwinder on 02 Oct 2001 10:38 PM</i>
What about this picture? Why do the real clocks show the original defaults of 199/458 when the drivers are at 220/520?<br> <br> <IMG SRC="http://home.att.net/~pecarter/RivaTuner.jpg"><br> <br> By the way, in this example NVturbo from the makers of Powerstrip, reported the frequency shown by the drivers, 220/520, not what the real frequency clocks displayed.
AFAIK NVTurbo is DRIVER LEVEL tweaker. And it reports the clock freuencies requested via the Detonator. It looks like in your case the driver just doesn't really set the clock frequency you are asking.<br> You may find this thread useful: <A HREF="http://pub28.ezboard.com/fentechfrm1.showMessage?topicID=334.topic" TARGET=_blank>http://pub28.ezboard.com/fentechfrm1.showMessage?topicID=334.topic</A> <br> <br> Alshley Saldanha (the author of PowerStrip) answers similar question here.<br> <br> BTW I can assume that I've done some bugs, which prevent the driver from setting clock frequencies (RT uses nvqtwk.dll independent driver calls under w2k/xp). What OS are you running?
