RivaTuner 2.05 Released

[helmutcheese]

Minor bugfixes:

- Fixed I2C write routine for ATI R600 graphics processors family, which has been erroneously commented the previous version's source code.
- Minor UI and localization fixes.

What's new:

- Updated databases for Detonator and ForceWare drivers. Added databases for ForceWare 163.69 and 163.71.
- Improved driver-level overclocking module for NVIDIA display adapters:
- Added new user interface for independent G8x GPU family shader clock control interfaces of the ForceWare 163.67 and newer drivers. New UI includes:
- New independent slider for adjusting shader domain clock.
- New "Link clocks" option allows you to use either traditional shader/ROP clock ratio based overclocking or completely asynchronous shader/ROP clock overclocking. Now you may either tick "Link clocks" options and adjust ROP clock only, allowing RivaTuner to overclock shader domain using VGA BIOS default shader/ROP clock ratio similar to pre-163.67 drivers, or untick "Link clocks" options and adjust domain clocks fully independently.
- New overclocking profile format supporting independent shader clocks. Please take a note that old overclocking profiles are not supported by RivaTuner, so you must recreate previously existing overclocking profiles.
- Previously available power user oriented ShaderClockRatio registry entry is now obsolete and it no longer exists in RivaTuner's database. Previously available ratio based shader domain overclocking functionality is now fully covered by new independent shader clock slider and new "Link clocks" option.
- New user interface is provided by default under ForceWare 163.67 and newer drivers under Windows Vista, however Windows XP owners can also force Vista specific overclocking interfaces usage by setting NVAPIUsageBehaviour to 1. If needed, shader clock control can be forcibly disabled and old traditional overclocking module UI appearance can be forced by setting NVAPIShaderClockControl to 0.
- Power user oriented adjustable minimum and maximum clock slider limits have been expanded from 25%-300% to 10%-800%.
- Added experimental SLI overclocking for Vista. Please take a note that I have no SLI rig for testing and development, so this feature has been added blindly and RivaTuner still doesn't provide official SLI support.
- Minor UI changes and improvements.


http://downloads.guru3d.com/downloadget.php?id=163&file=5&evp=2d213e528fb556c354432a3976bff55a

 

[helmutcheese]

The last 3 builds all have MS Driver signing thanks to ATI TOOL maker dude.

 

[helmutcheese]

Ya Unwinder is a good peep but short tempered.

 

[helmutcheese]

You sure as mine shows as not been signed & gets blocked from starting up when vista boots up?

This is with Vista 64.

100%, thats what the little funny Zip icon file is, I also put a copy of it in RivaTuner DIR for good measure.

Try booting with F8, turn on driver signing then install.

 

[helmutcheese]

This build has issues, someone over on their forums has his own issues and wants old build DL link back up.

I run my card at 330mhz Core 2D all the time (as low as Rivatuner lets me without messing about too much), as I do not need its stock 655mhz to surf web etc plus the added heat in a quiet PC as fans are all 50% most times.

Anyhow, I have always set that way and even in the last build with the shader settings through Power User Menu, but this build gives me random Nvidia driver has crashed and recovered MSG's in Vista64, it does this a few times then BSOD, with a MSG about some USB Driver.

It only happens if I use the lower 2D speed and can do it at total idle or playing some mp3 or surfing the WEB.

I think I will go grab 2.04 as there is really no need for the extra slider for me, I simply set previous build to -1 and that keeps my Core/Shader at Nvidias default ratio and then set Clocks to 700/2400 to game.

Now it was fine before I installed this build as I had forgot to slow down my 2D speed till later and thats when issues started

 

[helmutcheese]

NV/MS Vista bug was my issue abover as of running 4GB of Memory

http://www.microsoft.com/whdc/device/display/wddm_timeout.mspx

So Rivatuner was NOT to blame, very weird as I had passed hours of Othos and 3DMark(s) and Memtest For Window with a 1900mhz FSB (475x8=3.8GHZ) with Memory Linked in Sync so running 950mhz be it slacker timings, then back at stock it starts to act up basically at near idle.

Total fluke and now I know there is another Vista 4GB issue thats not about X-FI's lol.

 

[helmutcheese]

He prob has FAN missing from there same as I do last 2 builds, its only in the section above it.

 

[helmutcheese]

No idea, it has been there till last 2 builds for me, I used to have 2 diff fan sections on the 8000 cards but only the one we have now when I has the 7000 series.

 

[helmutcheese]

Just a thought. Have you tried going into power user and go to Nvidia\fan\current device and set in there.

Applyatstartup set to 1

Don;t forget fan speeds are in hex so for 100% fan you need 64

I think its only lets you make profiles for Temp v RPM, not full speed on sensing 3D .