Beware of new NVIDIA driver, it might burn your card

[xXlAinXx]

Well, so rumors without source and real proof is all we got? nice direction.

[BababooeyHTJ]

Well, so rumors without source and real proof is all we got? nice direction.

SO, Nvidia pulling the drivers isn't proof enough? Stop trolling, seriously.

[xXlAinXx]

SO, Nvidia pulling the drivers isn't proof enough? Stop trolling, seriously.

Lemme think about it for ten second.

EDIT:
nope



--
EDIT2:

Something is wrong with those driver? perhaps.. I'm not suggesting to keep em and/or installing em over an less problematic revision and.. I'm not going to denying the fact that nvidia, months after months are releasing bad driver.
I just dont buy the story where the pig's fly.

[BababooeyHTJ]

I have experienced this first had not the burnt gpu, but woke up the other morning of using the new drivers. I've been running gpugrid manually set fans to 100% before I went to bed. Came downstairs and no fan noise but computer was on I figured it restarted in the middle of the night and back to default. Go over to computer gpugrid still running, computer did not restart, and gpu fans were completely off on both my gtx295's. Go to check temp cores were sitting at 120C. Way to fail nvidia Went back into precision and cranked the fans back to 100% and they worked.

I have seen posts like this at several different forums, there clearly is a problem with the driver.

Software can do weird stuff, like I said GPU-z 3.8 was causing a pretty serious bump in my GPU core voltage accompanied by increased temps and rivatuner reporting a higher load than normal.

[Coldon]

Software can do weird stuff, like I said GPU-z 3.8 was causing a pretty serious bump in my GPU core voltage accompanied by increased temps and rivatuner reporting a higher load than normal.

Any chance the software wasn't reading the sensors properly due to a new driver version, I'm very skeptical that GPUz could modify the voltage regulation in the card.

I've had driver versions where precision could not read the card temps, does that mean that my card had no temperature after I installed the driver.

What nvidia has done is PR damage control, they had two choices either ignore the issue and get flame for that, or recall a driver just in case there was a problem and look like they are being proactive.

there were issues with the 191 drivers that were proven, and yet nvidia didnt do a recall, why? Probably cause the interwebs didn't explode in SC2 fueled nerd rage.

and honestly fan control is a bit of a screw up but its no where closed to the monumental screw up that ATI did with the drivers for the 5 series where my nice new $400 card cant run dual screens without flashing and which STILL hasn't been corrected. On the plus side for these drivers, BFBC2 is running smoother for me compared to the last official 196 version.

[BababooeyHTJ]

Any chance the software wasn't reading the sensors properly due to a new driver version, I'm very skeptical that GPUz could modify the voltage regulation in the card.

I've had driver versions where precision could not read the card temps, does that mean that my card had no temperature after I installed the driver.

What nvidia has done is PR damage control, they had two choices either ignore the issue and get flame for that, or recall a driver just in case there was a problem and look like they are being proactive.

there were issues with the 191 drivers that were proven, and yet nvidia didnt do a recall, why? Probably cause the interwebs didn't explode in SC2 fueled nerd rage.

and honestly fan control is a bit of a screw up but its no where closed to the monumental screw up that ATI did with the drivers for the 5 series where my nice new $400 card cant run dual screens without flashing and which STILL hasn't been corrected. On the plus side for these drivers, BFBC2 is running smoother for me compared to the last official 196 version.

I had that problem with GPU-Z under 196.21 and noticed under Rivatuner that my card was drawing more than normal while idle and beforehand Sirius Sam HD made the card run quite a bit hotter than normal so I doubt that it was just readings. I rebooted and just ran GPU-Z without starting any other monitoring software to be sure that was the cause. I also saw a few people reporting GPU-Z 3.8 causing the same thing with ATI cards running the same volterra chips as well. Remember it's not hard to adjust the core voltage via software on these cards there are quite a few programs that do this.

I the fact that this was backed up with higher temps, higher current draw, other software and others reporting the same thing makes me doubt that it was just an issue with readings.

[xXlAinXx]

I have seen posts like this at several different forums, there clearly is a problem with the driver.

Software can do weird stuff, like I said GPU-z 3.8 was causing a pretty serious bump in my GPU core voltage accompanied by increased temps and rivatuner reporting a higher load than normal.

FAN cannot goes OFF without some explict modification on the windows registry or some kind of catastrophic hardware failure, even if you fry the card the fan shall still spin on.
On the other hand: to be politically correct, only till the trehsold value is meet, the driver could indeed keep the fan to the initial spin value.

Source: