196.21 WHQL Breaks AB and Precision...

[burebista]

Originally Posted by theGryphon

Oh boy, who's been writing Nvidia drivers recently???

Maybe they borrowed some ATI programmers?

[Hog54]

Well these drivers dont work with thier own utility that came out a couple days ago,so I guess the jokes on them.

[kENSHu]

what program is that Hog54, looks like ntune?

[Hog54]

Its nvidia system tools utilty.http://www.nvidia.com/object/nvidia_...ools_6.05.html

[xSLIX]

even control panel sys info theres no clocks lol

NVIDIA System Information report created on: 01/19/2010 22:18:11
System name: xx

[Display]
Processor: Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz (3000 MHz)
Operating System: Microsoft Windows XP, 32-bit (Service Pack 3)
DirectX version: 9.0
GPU processor: GeForce GTX 280
Driver version: 196.21
CUDA Cores: 240
Memory interface: 512-bit
Memory: 1024 MB
Video BIOS version: 62.00.0E.00.0F
IRQ: 16
Bus: PCI Express x16 Gen2
GPU processor: GeForce GTX 280
Driver version: 196.21
CUDA Cores: 240
Memory interface: 512-bit
Memory: 1024 MB
Video BIOS version: 62.00.1C.00.10
IRQ: 16
Bus: PCI Express x16 Gen2
[Components]

nvCplUI.exe 2.8.290.13 NVIDIA Control Panel
nvWSS.dll 6.14.11.9621 NVIDIA Workstation Server
nvViTvS.dll 6.14.11.9621 NVIDIA Video Server
nvMoblS.dll 6.14.11.9621 NVIDIA Mobile Server
NVMCTRAY.DLL 6.14.11.9621 NVIDIA Media Center Library
NVOGLNT.DLL 6.14.11.9621 NVIDIA Compatible OpenGL ICD
nvDispS.dll 6.14.11.9621 NVIDIA Display Server
NVCPL.DLL 6.14.11.9621 NVIDIA Compatible Windows 2000 Display driver, Version 196.21
NV4_MINI.SYS 6.14.11.9621 NVIDIA Compatible Windows 2000 Miniport Driver, Version 196.21
NV4_DISP.DLL 6.14.11.9621 NVIDIA Compatible Windows 2000 Display driver, Version 196.21
PhysX 09.09.1112 NVIDIA PhysX
NVCUDA.DLL 6.14.11.9621 NVIDIA CUDA 3.0.1 driver
nvGameS.dll 6.14.11.9621 NVIDIA 3D Settings Server

[Unwinder]

Good news, I've implemented a workaround allowing to restore overclocking for 196.21 by means of using bugged IDs used in this version as well as provide the compatibility containing the fix from NVIDIA side in future NVIDIA drivers. Quote from the changes list:


- Added workaround for overclocking bug of ForceWare 196.21. Please take a note
that the workaround is applied only to 196.00 - 196.21 driver versions range
in order to ensure compatibility with future fixed NVIDIA drivers.
That is wny you may need to force the workaround via ClockDomainIdWorkaround
configuration file entry if NVIDIA release a few more versions affected by
this problem prior to fixing it
- Added workaround for overclocking bug of ForceWare 196.21. Please take a note
that the workaround is applied only to 196.00 - 196.21 driver versions range
in order to ensure compatibility with future fixed NVIDIA drivers.
That is wny you may need to force the workaround via ClockDomainIdWorkaround
configuration file entry if NVIDIA release a few more versions affected by
this problem prior to fixing it


I guess we'll upload beta 5 tomorrow (probably even today), allow you to test it a bit then incorporate the same workaround into EVGA Precision (unfortunately we don't use public beta releases approach with Precision like we do with Afterburner)

[upurz2]

Originally Posted by Unwinder

Good news, I've implemented a workaround allowing to restore overclocking for 196.21 by means of using bugged IDs used in this version as well as provide the compatibility containing the fix from NVIDIA side in future NVIDIA drivers. Quote from the changes list:

It was very nice of you to do this with your busy schedule. Much appreciated.

[v4npro]

Originally Posted by Unwinder

Good news, I've implemented a workaround allowing to restore overclocking for 196.21 by means of using bugged IDs used in this version as well as provide the compatibility containing the fix from NVIDIA side in future NVIDIA drivers. Quote from the changes list:


- Added workaround for overclocking bug of ForceWare 196.21. Please take a note
that the workaround is applied only to 196.00 - 196.21 driver versions range
in order to ensure compatibility with future fixed NVIDIA drivers.
That is wny you may need to force the workaround via ClockDomainIdWorkaround
configuration file entry if NVIDIA release a few more versions affected by
this problem prior to fixing it
- Added workaround for overclocking bug of ForceWare 196.21. Please take a note
that the workaround is applied only to 196.00 - 196.21 driver versions range
in order to ensure compatibility with future fixed NVIDIA drivers.
That is wny you may need to force the workaround via ClockDomainIdWorkaround
configuration file entry if NVIDIA release a few more versions affected by
this problem prior to fixing it


I guess we'll upload beta 5 tomorrow (probably even today), allow you to test it a bit then incorporate the same workaround into EVGA Precision (unfortunately we don't use public beta releases approach with Precision like we do with Afterburner)

Your the man!

[TFL Replica]

Thank you Unwinder.

[Unwinder]

Updated builds have been sent to both MSI and EVGA. So we'll release new MSI Afterburner beta 5 with it soon to allow public beta testing and EVGA will update Precision couple days later too after testing the build internally.

[dack1]

Thank you for all that work sir.

[Unwinder]

http://www.tomshardware.com/news/nvi...-bug,9489.html

NVIDIA confirmed that the fix is coming in future drivers, so other applications which don't include the workaround like recently released MSI Afterburner 1.5.0b5 and EVGA Precision 1.9.1 (e.g. NVIDIA System Tools, Gainward ExpertTool etc) will start working again.
Great thanks to people from NV for feedback, for paying attention to issue and for working on a fix. That's what I call proper developer relations. Totally beyond of my understanding why ATI devrel cannot be the same and why they almost never do the same and tend to leave issues undocumented and unresolved for ages.

[Blaise]

One of the members of nVidia's technical support just wrote:

Originally Posted by ManuelG

I wanted to mention we are aware of the compatibility issue with the latest NVIDIA Forceware display driver version 196.21 and overclocking utilities. We will be releasing a driver with a fix for this bug shortly.

on their nVidia forum.

[Wanny]

Originally Posted by Unwinder

http://www.tomshardware.com/news/nvi...-bug,9489.html

NVIDIA confirmed that the fix is coming in future drivers, so other applications which don't include the workaround like recently released MSI Afterburner 1.5.0b5 and EVGA Precision 1.9.1 (e.g. NVIDIA System Tools, Gainward ExpertTool etc) will start working again.
Great thanks to people from NV for feedback, for paying attention to issue and for working on a fix. That's what I call proper developer relations. Totally beyond of my understanding why ATI devrel cannot be the same and why they almost never do the same and tend to leave issues undocumented and unresolved for ages.

Good to hear

[Unwinder]

New beta NVIDIA drivers are available. The beta is supposed to fix the problem with overclocking:

http://www.nvidia.com/object/win7_wi...6.34_beta.html
http://www.nvidia.com/object/win7_wi...6.34_beta.html
http://www.nvidia.com/object/winxp64_196.34_beta.html
http://www.nvidia.com/object/winxp_196.34_beta.html