[modcrash.com] Nvidia 320.18 WHQL Display Driver is Damaging GPUs

[Vesku]

http://modcrash.com/nvidia-display-driver-damaging-gpus/#.UbS1ePnvtQs

"Fortunately it hasn’t killed every card it’s touched (It’s actually a very low amount), but there is hardly any good news to report about the 320.18 WHQL display drivers."

 

[HurleyBird]

Ironic from a company that supposedly has the best drivers. Didn't something like this happen last year too?

 

[toyota]

lets see how many people here have issues like that? I am guessing no one as that has been over 2 weeks ago and not a single report here or any other forum I am on.

 

[ViRGE]

lets see how many people here have issues like that? I am guessing no one as that has been over 2 weeks ago and not a single report here or any other forum I am on.

There's nothing in 320.18 in particular that would damage cards. It's the 3rd public release from the R319 branch; compared to 320.00 and 310.14, the only thing new in it are optimizations for a couple of games, a handful of bug fixes, and some new profiles. Any changes in hardware management would have come with the new branch itself, and as a result would have showed up in 320.00 and 320.14.

TFA seems to just be based on reading NVIDIA's forums. Which is a dubious source, because these complaints crop up with every new driver release.

 

[Silverforce11]

Notice its hitting the gtx570 and 460... I guess it matters that the 570 reference PCB was rubbish to start with hence people did not recommend it nor did they risk OC, any additional load would send it into a death spiral.

 

[3DVagabond]

lets see how many people here have issues like that? I am guessing no one as that has been over 2 weeks ago and not a single report here or any other forum I am on.

Well, the article does say it only effects a low number of cards. Or, are you doubting the validity of the claim?

 

[notty22]

Notice its hitting the gtx570 and 460... I guess it matters that the 570 reference PCB was rubbish to start with hence people did not recommend it nor did they risk OC, any additional load would send it into a death spiral.

Or it doesn't matter or have anything to do with anything. Just a opportunity to interject fud.

These are a couple recent threads with AMD hardware/software issues. Posted here. Would you like to interject some fairy tales as to why they happened also?

edited: examples removed
http://forums.anandtech.com/showthread.php?t=2323227

 

[toyota]

Well, the article does say it only effects a low number of cards. Or, are you doubting the validity of the claim?

yes I am. as already mentioned, there will always be handful of people that will blame the drivers for whatever happens to their card or system. if this was a legitimate problem then we would have more reports since its been over 2 weeks.

 

[Vesku]

Posted so people can judge for themselves whether to skip 320.18 WHQL.

As for other forums reporting issues:

http://forum.notebookreview.com/gam...nvidia-320-18-whql-update-complete-wreck.html

 

[3DVagabond]

yes I am. as already mentioned, there will always be handful of people that will blame the drivers for whatever happens to their card or system. if this was a legitimate problem then we would have more reports since its been over 2 weeks.

That's how I took what you said, but it wasn't perfectly clear (and your posting style generally leaves very little to interpretation ).

So, made up BS? I do notice that the person writing the article doesn't even use nVidia hardware currently. I always have my doubts to the validity of things said by someone who runs the competing hardware. Why would he have even been reading that forum in the first place? Use Google, get a few hits, write an article (or start a thread) that the sky is falling.

 

[Vesku]

http://www.overclock.net/t/1399104/mc-nvidia-320-18-whql-display-driver-is-damaging-gpus

Plenty of comments in that thread noticing issues with 320.18

 

[BallaTheFeared]

Notice its hitting the gtx570 and 460... I guess it matters that the 570 reference PCB was rubbish to start with hence people did not recommend it nor did they risk OC, any additional load would send it into a death spiral.

Yes that one batch of EVGA cards popping the vrms at 900+ core really defined an era.


These all look like random issues coupled with a few cards that could have died for any number of reasons.


Someone took the page hit bait and linked it here.

 

[toyota]

http://www.overclock.net/t/1399104/mc-nvidia-320-18-whql-display-driver-is-damaging-gpus

Plenty of comments in that thread noticing issues with 320.18

there are issues with every driver. where are the reports of people having their card damaged in that thread though?

and funny how this is being posted around the same time on various forums today even though the original story is over 2 weeks old.

 

[Termie]

320.18 absolutely ruined BF3 on my GTX670, showing the crazy colors shown in that thread, but also almost leading to complete loss of all textures in the game, as shown in the video.

There's no doubt that the driver is busted, as others in the BF3 thread complained of the same issue. As for destroying cards, I assume that was just a freak coincidence. My card worked fine after dropping back to 314.22. BF3 was the only game of five I tested that had any issues with 320.18.

 

[3DVagabond]

there are issues with every driver. where are the reports of people having their card damaged in that thread though?

and funny how this is being posted around the same time on various forums today even though the original story is over 2 weeks old.

The story was originally posted on the 3rd of June, not over 2wks ago. It popping up elsewhere is likely because it's been seen here.

 

[goobee]

I updated my evga GTX 680 SC Signature 2 the first day the new driver was available and have experienced zero problems.

Software damaging hardware seems kind of bahooey if you ask me. Firmware perhaps, software, no. Just saying.

 

[lavaheadache]

I actually had tomb raider act funny 2 days ago with my Titan and these drivers. I can around a corner in a building and every thing had weird pink, green and blue colors to it. Step out of the room and things were fine, back in and funny colors. After restarting the game everything was fine.

 

[HurleyBird]

where are the reports of people having their card damaged

http://forums.guru3d.com/showpost.php?p=4614344&postcount=45

 

[96Firebird]

http://forums.guru3d.com/showpost.php?p=4614344&postcount=45

Did you purposely edit out the part where he said in that thread, meaning the overclock.net thread?

Well done. :thumbsup:

 

[HurleyBird]

Did you purposely edit out the part where he said in that thread, meaning the overclock.net thread?

Well done. :thumbsup:

Yes I did, because it's not relevant. Dead cards are dead cards no matter where they are being reported.

And that same post was linked in the overclock.net thread too, not that it matters.

 

[Vesku]

I guess I should have editorialized the title from the modcrash version to highlight that there were general problems with 320.18 . But I try to preserve the article title when posting a link thread.

I did include in the subject the quote about the reports of damage being small in quantity.

Still 320.18 does seem to be problematic in general, imo avoid.

 

[f1sherman]

http://forums.guru3d.com/showpost.php?p=4614344&postcount=45

oh... the guy who fried 3 cards lately is now blaming the driver.

LOOKS LEGIT :thumbsup:

 

[HurleyBird]

And the other eight?

 

[f1sherman]

I have no clue, he didn't provide the link.

Driver frying 40W DDR3 GT620. Riiiight...

 

[f1sherman]

The amount of BS in article from OP link... staggering.

http://modcrash.com/nvidia-display-driver-damaging-gpus/#.UbUnjj4aRom

What ever you do - don't do that ^^.
Those Unistall methods have been depreciated since last century.
And driver instalation from Safe Mode?! LMAO