Nvidia Geforce 8800GT - no performance tab?

[importedforyou]

I have the
Nvidia 8800GT Gainward 512mb gold sample BLISS
Driver Version: 196.21
Windows 7 64bit 7600
ExperTool v7.6

Recently I think after i upgraded to the new drivers for the gpu the performance tab which i usually use when i right click ExperTool (comes with Gainward GPU) is missing and i cannot overclock my gpu anymore.
i checked my clocks with gpuz and they are all defaults.
I have tried using Rivatuner but dont think it is as good as the Expertool is more simpler, line the clocks, and can overclock the core, memory and shader which rivatuner cannot do shader? Which i like it even.

Has anyone else got this problem, or is there a way to get my "performance" button back when i right click on expertool?

Thanks

 

[invisible69]

I think newer drivers were released that will re-enable overclocking, since the previous ones seemed to contain a bug. Make sure you are running the latest drivers, use the automatic driver detection tool from nvidia's website

 

[importedforyou]

I was running the latest one and found the fix by going to nvdias beta drivers which currently contains the fix for the lastest driver.

http://www.nvidia.co.uk/object/win7_winvista_64bit_196.34_beta_uk.html

New in Version 196.34

* Fixed a bug with v196.21 that prohibited GPU overclocking

New in Version 196.21

* Adds SLI and multi-GPU support for many top new gaming titles including Avatar Demo, Battlefield: Bad Company 2, City Bus Simulator, Dirt 2, Ferrari Virtual Race, GREED: Black Border, Mass Effect 2, Mortal Online, Ninja Blade, Operation Flashpoint: Dragon Rising Demo, Planet 51, RUSE, Serious Sam HD, and Wings of Prey.
* Upgrades PhysX System Software to version 9.09.1112.
* Includes numerous bug fixes. Refer to the release notes on the documentation tab for information about the key bug fixes in this release.

 

[mame]

You need to install nvidia system tools. This will add the performance tab in the drivers just like it used to be.

 

[importedforyou]

the newer drivers fixed this problem, probably a bug previously