Need help with RivaTuner or ATItool

brysig228

Gawd
Joined
Feb 27, 2007
Messages
573
i just installed vista 64-bit installed riva and ati, riva sees my card 8800gts 512m but it don't give me the option of over clocking it and same as the temp. ati tool dont see the clock of the card. anyone have any idea what i'm doing wrong? thanks for your help.
 
Did you install the available updates in rivatuner? if not just go to the setup folder and double click RivaTuner209Drv.rtu

If you only need to OC and check fan/temp, EVGA precision is the best alternative for 64bit users
 
Which Riva version and where are you clicking to attemp the overclock???:D
 
This guide is very good:http://www.vaguesoft.com/index.php?pageid=rt207

what nvidia driver version????

To overclock:
click on customize to the right of the "driver settings"
then click on the little graphics card icon, first one on the left.
It will take you to the overclocking selections.
 
I had a similar problem, started about weekend previous... I was playing Crysis, just before the mine level, and gotten sudden choppiness and massive audio "corruptions"/looping (best I could term it)... Well, push comes to shove, I decide to futz around in RT, the NV CP, and so on. Nothing could see anything but what card I had, the temp and the fan speeds. No overclocking, no reading of either stock (except in GPUZ) or current speeds.. Small caveat: RT monitoring showed 400 core/memory, 810 shaders, but that obviously was totally off.. I tried reverting to older drivers, 169.25, 169,32, latest as noted @ EVGA (169.44), 175.12 (?) betas, and as of this morning the (edit: 175.63's) (from G3D; rel. 05/03 I think). Didn't work, uninstalling the drivers + reinstall didn't work..

Long story (a bit) short(er), it took rebooting in safe mode, running Driver Cleaner, rebooting again and reinstalling (latest betas ATM) for everything to be back to normal. Well - normal as can be - RT & others can now see current/stock speeds, and the EVGA tool can see/alter fan speeds/clocks now (RT can't overclock though, but I attribute that to non support of the latest betas). As if Crysis can be blamed after it's mini meltdown, I don't know, it's just after that when I noticed the issue.


Just thought I'd throw in my $.02, may not help the OP since it sounds like it's fixed there too, but hopefully can help someone else (should they think of searching first ;).
 
Back
Top