Nvidia 320.18 WHQL Display Driver is Damaging GPUs

[layte]

Really? you can't set custom refresh rates with CCC , That's RP.

Simple, ergonomic and all of it works perfectly.

No, you cant. Seems you dont understand what those pages on the CCC actually do. Those are for basically tweaking overscan and for very slight adjustments required for HDTV's with strange resolutions. When I wanted to add 2560x1440 to my system (I have a 1600p display) I had to edit the registry, and everytime the drivers were updated I had to re edit the registry.

Oh and as to having to resort to a 3rd party solution, yea it works fine, but all of that should be in the CCC and it all should work.

Edit: And LCD overdrive? Really? ugh.. Whack overdrive up to max and revel in the inverse ghosting. That has nothing to do with refreshrates.

Edit2: This is how its done: http://hardforum.com/showthread.php?t=1605511

 

[Gregster]

Why is it the guys who own AMD GPU's have the biggest voices? I have issues with these drivers and past drivers and have never been shy of letting people know when Nvidia have done wrong but that doesn't detract from the fact that this thread is blown well out of proportion.

Unless someone provides evidence, I am not buying it.

 

[kh85]

i'm going to stick with the 320.11 drivers from the cd for now.

will try bf3 and see if everything ok later (once it's downloaded -_-)

 

[spoffle]

But that's the extent of how much it matters.

But if I were you, I would not be taking any risks.

 

[humbug]

No, you cant. Seems you dont understand what those pages on the CCC actually do. Those are for basically tweaking overscan and for very slight adjustments required for HDTV's with strange resolutions. When I wanted to add 2560x1440 to my system (I have a 1600p display) I had to edit the registry, and everytime the drivers were updated I had to re edit the registry.

Oh and as to having to resort to a 3rd party solution, yea it works fine, but all of that should be in the CCC and it all should work.

Edit: And LCD overdrive? Really? ugh.. Whack overdrive up to max and revel in the inverse ghosting. That has nothing to do with refreshrates.

So what your saying is 1600P is not an option that exists in CCC?

 

[jackle13]

This is a strange one, as I have been worried about it since my first crash in Metro LL due to an Nvidia hang-up error in event manager, but after that nothing since..

Since then, I have been using my GTX 770 with 320.18 drivers without any issues playing long hours of BF3, Crysis 3, FC3 etc.

 

[spoffle]

Most of what Layte is saying is correct, though 2560x1440 should be there if he's got a 2560x1600 monitor. That's a bit odd.

When I had 1920x1200 displays I could easily select 1920x1080 for them, which is the same situation.

 

[layte]

So what your saying is 1600P is not an option that exists in CCC?

No, please re-read what I posted. I am saying because 1440p was not a resolution listed in the EDID of my display (the same thing happened on both my Dell 3008 and 3014), I had to resort to editing the registry (see my second edit). In the NV control panel you click a couple of buttons to do the same thing.

Most of what Layte is saying is correct, though 2560x1440 should be there if he's got a 2560x1600 monitor. That's a bit odd.

When I had 1920x1200 displays I could easily select 1920x1080 for them, which is the same situation.

The same displays had no issue with 1080p. I guess Dell don't like 1440p on their 30" jobbies.

 

[ubersonic]

I've figured it out guys! its all a hoax cleverly orchestrated by AMD to stop people buying the 7xx cards which need 320 drivers and to stop the performance increases in the 320's making it to reviews/benchmarks!

That WAS a joke

 

[Rilot]

This constant bickering stops NOW.

 

[tommybhoy]

Why is it the guys who own AMD GPU's have the biggest voices?

AMD CrossFire Frame Rating latency problem thread resurrection:

Any sign of these prototype drivers yet?

 

[andybird123]

Your 7970M issue is an issue with Clevo/Enduro isn't it? It's just that the issue is affecting the use of your 7970M.

the "enduro problem" related to where the 7970M wouldn't become active due to enduro not switching to it has been "fixed", my problem in an ever increasing number of titles now is that the usage on the 7970M swings wildly from 99% to 10% and back seemingly at random with with no corresponding increase in action on screen or usage of CPU

for every game that gets fixed, there are another 3 new ones that it crops up on, and even a game that is fixed in one update gets re-broken in the next, so I face a constant battle of driver sweeping the machine to find a set of drivers that works with a specific game and having to change every time I fancy playing something else for a couple of hours

it isn't clevo related, or enduro related, it is specific to the 7*** series mobile chips and the lack of corresponding driver support

 

[andybird123]

Only the ones who refuse to hear anything bad about their pet faceless company. There are plenty of Nvidia users in this thread who have clarified they had issues with these drivers and reverting to older drivers fixed the problem.

Though feel free to bring up these kinds of problems a moron declares Nvidia drivers as never causig problems.

no one is refuting that 320.18 are a bad set of drivers... what some of us are refuting is that these drivers are "killing cards" as per the thread title

as you say yourself, people who actually try swapping back to older drivers are finding that the problems are solved, however the claims by spoffle et al are that these drivers are systematically destroying anything older than a 7** series in a deliberate attempt by nvidia to force people to buy newer cards

 

[humbug]

no one is refuting that 320.18 are a bad set of drivers... what some of us are refuting is that these drivers are "killing cards" as per the thread title

as you say yourself, people who actually try swapping back to older drivers are finding that the problems are solved, however the claims by spoffle et al are that these drivers are systematically destroying anything older than a 7** series in a deliberate attempt by nvidia to force people to buy newer cards

There are plenty of users on the internet having gone 320.18: found problems, and then reverted back to 314.22 and found permanent GFX corruption, some saying the GPU no longer works at all.

Employing the Ostrich maneuver and pretending those people don't exists while repeating over and over again that "it can always be fixed by rolling back" will not rewrite history

 

[andybird123]

There are plenty of users on the internet having gone 320.18: found problems, and then reverted back to 314.22 and found permanent GFX corruption, some saying the GPU no longer works at all.

Employing the Ostrich maneuver and pretending those people don't exists while repeating over and over again that it can always be fixed by rolling back will not rewrite history

I have tested these drivers myself and haven't seen any of the increased voltage, heat, BSOD or black screen problems that people are saying have killed their cards... I have also seen a great many people with these issues say that rolling back has fixed all of the problems

when your own experience mirrors someone else's, do you a) tend to think that this is the most likely situation or b) take a couple of people's claims posted on the internet as being more factual

I understand why AMD owners are rubbing their hands with glee at the prospect of some bad press for Nvidia, but that doesn't make it factually correct

everyone is free to make up their own mind, though I would prefer that people who actually have some direct experience of the situation post their experience, rather than pages of "well I read it on the internet so it must be true"

 

[Final8y]

Most of what Layte is saying is correct, though 2560x1440 should be there if he's got a 2560x1600 monitor. That's a bit odd.

When I had 1920x1200 displays I could easily select 1920x1080 for them, which is the same situation.

2560x1440 is not there by default on a 2560x1600 monitor in CCC even though some games will give you the 2560x1440 option.

 

[humbug]

I have tested these drivers myself and haven't seen any of the increased voltage, heat, BSOD or black screen problems that people are saying have killed their cards... I have also seen a great many people with these issues say that rolling back has fixed all of the problems

when your own experience mirrors someone else's, do you a) tend to think that this is the most likely situation or b) take a couple of people's claims posted on the internet as being more factual

I understand why AMD owners are rubbing their hands with glee at the prospect of some bad press for Nvidia, but that doesn't make it factually correct

everyone is free to make up their own mind, though I would prefer that people who actually have some direct experience of the situation post their experience, rather than pages of "well I read it on the internet so it must be true"

I don't know whats going on, I don't have those very GPU's those people have in their rigs claiming they are now busted.
Its far to convenient dismiss them as if they are all liars and go on banging home your own version as if 'that is fact'
its a blatant attempt at writing history.

And you have seen those screen shots, they look pretty serious, something that looks like that cant be doing good things to the GPU for it to look as bad as they do.

You overclock your memory to the point where BF3 looks like that and I will bet you damage is done, if not in the short term perhaps in the longer term. not that i'm saying its a cause.

 

[Stanners]

I don't know whats going on, I don't have those very GPU's those people have in their rigs claiming they are now busted.
Its far to convenient dismiss them as if they are all liars and go on banging home your own version as if 'that is fact'
its a blatant attempt at writing history.

And you have seen those screen shots, they look pretty serious, something that looks like that cant be doing good things to the GPU for it to look as bad as they do.

You overclock your memory to the point where BF3 looks like that and I will bet you damage is done, if not in the short term perhaps in the longer term. not that i'm saying its a cause.

As far as i know Nvidia still have not pulled them(which they did very quickly last time when things blew), So as I see it I am still thinking it is maybe getting blown out of proportion.

The trouble is people like to sensationalise potential issues and seem to get enjoyment from other peoples potential misfortune just to meet there own specific views.

 

[spixelspixel]

I really don't understand how nvidia managed to release a driver in this state :/

 

[andybird123]

I don't know whats going on, I don't have those very GPU's those people have in their rigs claiming they are now busted.
Its far to convenient dismiss them as if they are all liars and go on banging home your own version as if 'that is fact'
its a blatant attempt at writing history.

And you have seen those screen shots, they look pretty serious, something that looks like that cant be doing good things to the GPU for it to look as bad as they do.

You overclock your memory to the point where BF3 looks like that and I will bet you damage is done, if not in the short term perhaps in the longer term. not that i'm saying its a cause.

nope, you are misquoting me, just because I'm not taking one extreme of claims as "fact" does not automatically mean that I am taking the other end of the spectrum as "fact" either

I have in fact said that people should weigh the evidence and make their own decision, I have then stated my OPINION on the subject, but this is not fact

I would like to hear more evidence from people with direct experience, that is difficult when potential evidence is being drowned out by claims of rewriting history, deliberate sabotage by evil nvidia and assumptions based on information that is being whispered from forum to forum so many times that no one knows where it originally came from

my opinion is open to change as more useful information comes to light

all I have said, is that based on the information I currently have available to me, is that there is a very low likelihood that this driver is outright killing cards

I personally have rolled back to an older version, though mainly because of a performance issue with a specific game, rather than through fear of GPU death

I've overclocked memory to the point of on screen corruption plenty of times and repeatedly and never had permanent damage, so I tend to think you are exaggerating a touch

if you have/do use these drivers and get problems, my advice is to try an older driver first (use safe mode if needed), and if this doesn't work then post up in the feedback thread, as well as contact the vendor of your card

the more information we can get together, the better for everyone