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.
From this dump it looks looks like NV changed clock domain IDs due to some odd reason (most likely there are more different clock domains coming in GF100 chips?). So it should be rather easy to fix.
Under such conditions only shader clock control should be disabled in current Precision/Afterburner (I use domain ID checking for shader clock only and always treat the first two domains as core/memory clock domians). Is shader clock control slider the only clock slider disabled now?
Nvidia je zvanično predstavila "nove" grafičke karte GeForce 300 serije, koje će biti dostupne isključivo OEM tržištu, odnosno velikim proizvođačima PC računara. Radi se o GeForce GT 340, GT 330 i GT 320 modelima. Ipak, ne radi se o suštinski novim modelima, pošto se sve ove karte baziraju na 40-nanometarskih GT21x čipovima
Btw jel rade drajveri sa evga precision.
Recently, nVidia posted a WHQL driver "Release 196.75". The driver brought WHQL-certified support for nVidia ION, recently renamed 300-series cards, Optimus-enabled GPUs and many more. However, the driver was quickly found to prevent the fan from spinning and caused a death of multiple graphics cards around the world.
Yes, you've read that correctly - the drivers had an extreme version of issue nVidia already experienced last year with one of past WHQL-certified drives, when the drivers broke fan control on custom-built GeForce cards. Unfortunately for a lot of customers, Release 196.75 brought nothing else but tears, as Internet Forums started filling with complaints about graphics cards that started to die out, most notably during Blizzard's StarCraft II beta test. Activision Blizzard was also first to react and made an official comment on the state of the drivers, advising its customers and testers to immediately go back to previous driver revision, i.e. Release 196.21.
We contacted Bryan Del Rizzo, nVidia's PR Manager for GeForce for comment:
"We are aware that some customers have reported fan speed issues with the latest 196.75 WHQL drivers on NVIDIA.com. Until we can verify and root cause this issue, we recommend that customers stay with, or return to 196.21 WHQL drivers. Release 196.75 drivers have been temporarily removed from our Web site in the meantime."
Given that the most users that reported their graphics cards have died were using a custom-built boards featuring nVidia's favorite renaming chip of all times, G92 GPU [8800GT, 8800GTS, 9800GT, 9800GTX and the subsequent 55nm die-shrink: 9800GTX+, GTS 250]: GeForce 9800GT, 9800GTX and GTS 250 were particular victims of this issue.
The biggest question that now remains is how fast nVidia will handle this situation with the physically damaged users, as it is clear that board vendors will have to accept RMAs for the cards, and if there's one thing that we heard from nVidia partners here at CeBIT, that was a collective opinion that they've lost faith in the company. This driver situation certainly didn't help the situation and we see no other but to address those concerns in a separate article.
open regedit then search and delete all instances of RmThermalProviderInfo and RmThermalProviderNum entries in the registry. Then reboot. This causes the driver to redetect the thermal info. The is just a worse variant of the No GPU temp issue. Bad thermal info during the driver install.
To all users reporting fan issues. We will be posting a newer driver shortly with a fix.
Follow along with the video below to see how to install our site as a web app on your home screen.
Napomena: this_feature_currently_requires_accessing_site_using_safari