• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

320.18 Nvidia Drivers - Report your issues here

Any official word from nvidia on these yet Greg?

Not a fan of others having a laugh and finger point about this, really quite gutted for those that may end up with dead cards. Nobody likes to see their £300 investment burn up.

Nothing from Nvidia and anyone who has said their card has died has not had a response. Pretty poor, as I see too many for it to be a coincidence. I do feel gutted for those that have no warranty and the card has failed :(
 
Nothing from Nvidia and anyone who has said their card has died has not had a response. Pretty poor, as I see too many for it to be a coincidence. I do feel gutted for those that have no warranty and the card has failed :(

Do you think that perhaps Nvidia have got just a little to arrogant?

Genuine question :)

Clearly there is something very wrong with these drivers, it must be as obvious to them as it is to us, and yet they maintain complete silence, ignore those with dead GPU's and stubbornly leave the offending drivers up for others to potentially join GPU's murdered queue.

Do the really think by ignoring this history and their users affected will just sweep it under the carpet for them?
 
playing devils advocate for a second; it does appear to be overclocked / last legs cards that are having problems... in nvidia's drive to extract every last ounce of performance from stock cards, these drivers are pushing already on the edge cards over

from nvidia's point of view, they are just trying to give their users the best performance they can... but the road to hell being paved with good intentions as they say...

it would be nice to see nvidia / the AIB's actually step up and do something for those that have been affected, though how to tell the difference between a "stock" factory OC failing, and a card failing because it had spent 3+ years overclocked to within an inch of it's life will be a tricky one, they could be opening the flood gates to claims from people who know full well that they broke their own card long before this issue cropped up

though if it's a 6** series card it is pretty obvious that it should be under warranty

this issue does have the potential to tarnish their brand in the market place
 
playing devils advocate for a second; it does appear to be overclocked / last legs cards that are having problems... in nvidia's drive to extract every last ounce of performance from stock cards, these drivers are pushing already on the edge cards over

from nvidia's point of view, they are just trying to give their users the best performance they can... but the road to hell being paved with good intentions as they say...

Andy, ^^^^^ really?

There being an advocate and then there's recognising what your about to say make one look like one is trying to hard. :)
 
The more I look at this "issue", the more it just seems like coincidence and people putting 2+2 together and ending up with 6. Anyone with card problems will do an internet search and now see one of the many threads on forums such as this, where their are unfounded proclamations of the driver destroying graphics cards. They naturally then assume that their card also suffered the same fate. The driver that Nvidia actually pulled for killing cards had proof that it was indeed killing them. This hasn't been proven and has been going on since the drivers where released. The fact that Nvidia hasn't pulled them yet is good enough for me to say that its not the driver, its just a coincidence.

Its like saying that AMD drivers killed all MSI 7950 cards, even though it was the hardware that was faulty. Before it was proved, everyone just lambasted AMD for their drivers...
 
Do you think that perhaps Nvidia have got just a little to arrogant?

Genuine question :)

Clearly there is something very wrong with these drivers, it must be as obvious to them as it is to us, and yet they maintain complete silence, ignore those with dead GPU's and stubbornly leave the offending drivers up for others to potentially join GPU's murdered queue.

Do the really think by ignoring this history and their users affected will just sweep it under the carpet for them?

In honesty, as far as coding goes, I have no clue as to what goes on in the drivers. I don't think it was arrogance and I certainly don't believe they did it on purpose. Drivers have been terrible since Jan/Feb and that is inexcusable. I have defended Nvidia in the past for producing great drivers (which they have) but the last few releases (WHQL) have left questions over the dev team. I understand Beta's can have issues (hence the term Beta) but to then release a WHQL that is as problematic as these 320.18 on so many different systems, leaves a question mark over their commitment to the end user. I don't want to get into the realms of beating on Nvidia because of my personal history has been a good one. The bad part for Nvidia is other users and if I was one of those who have been bitten, I would be the first to be looking at swapping across.

What I do like about Nvidia is the simplistic set-up. I have 3 screens that all run in 3D and they just work. No fuss, no bother, so from a personal point of view, my lack of major issues keeps me interested. The only real gripe I have is the lack of any form of acknowledgement on the dead cards and feel that loyal fans are being shafted and with AMD doing so well since 12.11, Nvidia could be losing a lot of loyal fans.

I have been accused of being a fanboy on so many occasions (which I guess I am to a degree) but I am the first to criticise Nvidia when they mess up. I have been picking faults and moaning on their forums (and even getting jumped on there by gimps), as well as here when something isn't right. All the issues that were reported in this thread I informed Nvidia on their website, purely because some of us moan here but not at the place where it counts. Unless more people tell them the errors they are getting, they will not do anything about it. They have a driver report thread but sadly that gets abused by certain people or not used correctly.
 
Clearly there is something very wrong with these drivers, it must be as obvious to them as it is to us, and yet they maintain complete silence

Dude do you not remember reading their response? we both posted in the thread.

For users encountering corruption in Battlefield 3 where the objects display the wrong colors with drivers R320.xx but does not appear in driver R314.22 or earlier, could you please do the following?

1) Please if possible email me a copy of your VBIOS to [email protected]. Include your graphics cards make and model (and if possible the in game graphic settings used and any changes in the NVIDIA Control Panel you have used and screen resolution and refresh rate)

2) If you are located in the USA, if you would be willing to mail us your graphics card so that we can try to reproduce this locally, we would pay for shipping both ways and also provide you with a loaner graphics card while we test your issue.

3) If by chance you live close to Santa Clara and would be willing to bring in your system to Santa Clara and show us the corruption reproduce with R320.18 but not with driver R314.22, that would be the best option for us if possible. We would compensate you with a graphics card upgrade.

We are getting a couple of loaner boards from users in next couple of days. Our goal is to address this, Assassin's Creed 3 and the Battlefield 3 issue and then release a driver with these fixes. For more advanced users experiencing system crashes after updating to driver R320.18, especially on desktop or while browsing Firefox, it would be helpful if you could provide us with mini-dmp file from your system. Instructions are available from Microsoft below:

http://msdn.microsoft.com/en-us/libr...8VS.85).aspx

You can email the mini dump files to me at [email protected]

Please include in description what apps you were running when this occurred, OS and graphics card used. Thank you all for your patience and your feedback. We hope to have fixes for these very soon.

I'm not trying to cover for them, I agree they should have pulled the driver until they can figure out what the issue is and whats caused it, but trying to make out their ignoring the issue when that was posted 6 days ago is a bit misleading.
 
Don't help those who don't think to go there are read that ^^^^

In honesty, as far as coding goes, I have no clue as to what goes on in the drivers. I don't think it was arrogance and I certainly don't believe they did it on purpose. Drivers have been terrible since Jan/Feb and that is inexcusable. I have defended Nvidia in the past for producing great drivers (which they have) but the last few releases (WHQL) have left questions over the dev team. I understand Beta's can have issues (hence the term Beta) but to then release a WHQL that is as problematic as these 320.18 on so many different systems, leaves a question mark over their commitment to the end user. I don't want to get into the realms of beating on Nvidia because of my personal history has been a good one. The bad part for Nvidia is other users and if I was one of those who have been bitten, I would be the first to be looking at swapping across.

What I do like about Nvidia is the simplistic set-up. I have 3 screens that all run in 3D and they just work. No fuss, no bother, so from a personal point of view, my lack of major issues keeps me interested. The only real gripe I have is the lack of any form of acknowledgement on the dead cards and feel that loyal fans are being shafted and with AMD doing so well since 12.11, Nvidia could be losing a lot of loyal fans.

I have been accused of being a fanboy on so many occasions (which I guess I am to a degree) but I am the first to criticise Nvidia when they mess up. I have been picking faults and moaning on their forums (and even getting jumped on there by gimps), as well as here when something isn't right. All the issues that were reported in this thread I informed Nvidia on their website, purely because some of us moan here but not at the place where it counts. Unless more people tell them the errors they are getting, they will not do anything about it. They have a driver report thread but sadly that gets abused by certain people or not used correctly.

Bloody hell...

All I asked was if you though Nvidia should accept the overwhelming evidence on the Internet and pull the offending drivers before more people are affected by them.

I have said nothing about any rivalries, I have no idea why you would expend in to all that crap.... I have nothing to say on the matter. off topic!
 
As far as cards dieing is it limlited to 6xx/7xx series or is it effecting previous generations?

Affects anything supposedly, which makes it stand out even more as complete coincidence as the architecture between a 8x00, 2x0, 4x0/5x0/6x0/770 and 780/Titan are completely different. Its not like the driver that specifically killed 590s for example. I still firmly believe this is coincidence.

I've had a brand new gpu a few years back (8800 GT) that lasted an entire week before dying. Its replacement lasted years... Where drivers to blame or poor hardware? Poor hardware ofc.
 
As far as cards dieing is it limlited to 6xx/7xx series or is it effecting previous generations?

people with 4 and 5 series have been reporting similar issues, though as JamesJ points out, it is very hard to separate fact from fiction when it comes to these claims

the one person on this forum that has reported a card outright dieing after installing these drivers, was a factory OC card that was a b-grade, so it's writing may well have been on the wall in any case (hence why b-grade cards only come with 90 days warranty - they are always a risk and not one that even OCUK are prepared to fully back)
 
Don't help those who don't think to go there are read that ^^^^



Bloody hell...

All I asked was if you though Nvidia should accept the overwhelming evidence on the Internet and pull the offending drivers before more people are affected by them.

I have said nothing about any rivalries, I have no idea why you would expend in to all that crap.... I have nothing to say on the matter. off topic!

Unless you actually know RMA return rates on GPUs for the last few years, how could you remotely prove it? More people being vocal about their gpu dying doesn't necessarily mean its the driver, it just means they go to the internet when its happened to complain about it.
 
they are offering to pay shipping and/or free upgrades to people willing to give them their graphics card to test this problem, you really can't say fairer than that at this point

All I asked was if you though Nvidia should accept the overwhelming evidence on the Internet and pull the offending drivers before more people are affected by them.

yours and mine idea of "evidence" is obviously fairly different... if they can't reproduce it in a test rig then all of this "evidence" is anecdotal at best
I could post on every forum and a dozen twitter feeds that EVGA used cheese slices instead of TIM and that it caused my Titan to fail - I could include pictures... it wouldn't make it "evidence"
 
Last edited:
It seems to affect all.

Its like saying that AMD drivers killed all MSI 7950 cards, even though it was the hardware that was faulty. Before it was proved, everyone just lambasted AMD for their drivers...

Except that it's nothing like that, as in that case it only affected one brand, MSI, and they confirmed the problem and were willing to replace all faulty or even potentially (!) faulty cards.

I've uninstalled 320.18 now pending someone actually answering my question about modding the INF file on the 314.22 or responding to whether I can use the ones linked in this post for Windows 8 on my W7 install:
There are none listed for Windows 7, so will the Windows 8 version work? Do i use the Mobile Nvidia OEM 64bit ones? http://forums.laptopvideo2go.com/forum/179-31x-series-geforce-driver-release/
 
Last edited:
Unless you actually know RMA return rates on GPUs for the last few years, how could you remotely prove it? More people being vocal about their gpu dying doesn't necessarily mean its the driver, it just means they go to the internet when its happened to complain about it.

I think with the amount of people now complaing about dead / damaged GPU's after 320.18 and still dead / damaged with rollbacks can no longer be shrugged off as liars and trollers.

Don't you agree?

However as long as Nvidia go on ignoring this then it can always be argued by die hard fans that there is no evidence.
 
Last edited:
I think with the amount of people now complaing about dead / damaged GPU's after 320.18 and still dead / damaged with rollbacks can no longer be shrugged off as liars and trollers.

Don't you agree?

You think that way because you fail to apply logic to anything remotely complicated. There is STILL no proof. Its like having a school child try and describe the different mechanisms of programmed cell death. They see the cell dying, yet don't have a damn clue why, instead just clutch at straws and coincidental factors.

Until its proved, which I highly doubt it will be, the only people trolling are people like you, who insist that theres some massive conspiracy at play.

I'll ask you again, do you know the RMA rates of all major manufacturers in the last 3-5 years? If not, how the hell can you prove that the failure rate on Nvidia GPU's has risen past a point that isn't in the mean scale? Until you get that sort of FACT, you are just talking rubbish.
 
It seems to affect all.



Except that it's nothing like that, as in that case it only affected one brand, MSI, and they confirmed the problem and were willing to replace all faulty or even potentially (!) faulty cards.

I've uninstalled 320.18 now pending someone actually answering my question about modding the INF file on the 314.22 or responding to whether I can use the ones linked in this post for Windows 8 on my W7 install:

Exactly, it was nothing like that, which this could be just another example of. Get it now?
 
Back
Top Bottom