• 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

Gregster

Gregster

Gregster

Caporegime
Joined
24 Sep 2008
Posts
38,283
Location
Essex innit!
So after reading that thread LtMatt posted about these drivers are killing cards, I decided to start a thread where we can discuss the issues and hopefully find a fix or just bug report to Nvidia. I found it quite disturbing that these drivers are causing the amount of issues we are seeing reported and I myself have had issues with these.

So far I have found that Trine 2 is far to bright (colours are all messed up) and Grid 2 exits full screen and when I go back to full screen, it is running ~30fps (dropped from 80+).

I will be giving other games a test over the next couple of days to see if there is any other issues.

If you are having hard locks, please report it here:
https://forums.geforce.com/default/...-xx-display-driver-stability-feedback-thread/

Please make sure you add all the required info to help the devs reproduce the issue.
 
Neil79 said:
GTX 560 ti / Windows 7

Every 320.x driver (Beta/Whql) so far, causes the system to freeze up in windows at certain times. I might be browsing in firefox or listening to music and system becomes unresponsive. Unable to move mouse! But within 2mins, system resumes and I can see a driver fault in error logging.

All previous drivers work perfectly!
Click to expand...

It seems quite a few are having issues with FF and the later drivers. I just perused back through the driver feedback thread and seen a few reporting the same issue as you Neil.

Probably a good idea to give your info (if you haven't already) here
https://forums.geforce.com/default/...-xx-display-driver-stability-feedback-thread/

Certainly drivers have gone down hill and seems far more bug reports than there ever was. Nvidia need to sort this out and fast.
 
Neil79 said:
They should recall the drivers, they've done it before with that Fan issue.
Click to expand...

If these are killing GPU's, for sure they should and replace those who have been affected, regardless of warranty. I have always bigged up Nvidia drivers but for the past 6 months, they have gone down hill.

I sure hope that anyone who installed these drivers and their GPU dies, does report it. The more that do, the more chance of Nvidia admitting there is an underlying issue and the users should get some remuneration.
 
DTWD said:
From the other thread:
Click to expand...

Can you send me the minidump files please from your C:\Windows\minidump folder?

My email addy is at the bottom of my signature.

Edit:

Could anyone getting BSOD's send me the memory dump files. I am at work till 10pm tonight but will go through them :)
 
Last edited:
I wonder if the higher temps are anything to do with the weather getting warmer? I noted earlier that my temps were lower than the previous day and I was on 314.22. Today I put the 320.18 back on and temps were cooler (it was quite cold here this morning).
 
kh85 said:
morning guys, i've recieved my 780 today and unsure what to do,
has this driver issue been sorted, or can i use an older version of drivers on the 780 for now? don't wanna install it until i'm sure. it also sounds like pot luck if you get the problems

thanks guys
Click to expand...

I would only have concerns if I was out of warranty in honesty. As yours is new, load them up.
 
pgi947 said:
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.
Click to expand...

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 :(
 
humbug said:
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?
Click to expand...

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.
 
humbug said:
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!
Click to expand...

You obviously didn't bother reading what I typed. Where on earth did I say about rivalries? I was pointing out the errors I have had and feel this is rather relevant to these 320.18 drivers (which I am on).

Please stay out of this thread if you are only wanting people to start hating Nvidia and going by your reaction, that is clearly pointing at that. That will not help any user and like I said, users need to post in the relevant section of the Nvidia forum with their details and what is happening on their system. Don't try and be like Spoffle, as it will only lead to disappointment.

Edit:

As you have no issues to report, I kindly ask you leave this thread :) Everything you have been saying has been done in that other thread which got closed.
 
James J said:
Nvidia have pulled drivers before and said sorry to the community though. Look at the 590 setting on fire debacle a few years back. The drivers where pulled when they could replicate the issue. So far though, there is no proof that this driver is actually killing cards as it doesn't appear to be altering voltages, which was initially thought. Sure the driver is a bit buggy, but not to the point where its damaging hardware. Just coincidence.
Click to expand...

I believe it isn't the GPU being damaged but the memory modules. Most issues being reported are showing corruption. If there is an issue, I would be looking at what is happening with the memory to be honest.
 
James J said:
From what I've seen, its not all memory issues. Numerous people are getting issues associated with core death as well, which also confounds my assumption that this is still coincidental.
Click to expand...

Could be. I have a good understanding of how a GPU works but have no idea on the intricacies of one. I was just going on the basis of the amount who report texture corruption and this normally points to memory being clocked too high. Of course I could be a mile off and it is something completely different.
 
humbug said:
People here aren't going to see that.

It wont be closed as long as it stays civil :)
Click to expand...

But Nvidia will see it and with me linking it, users here can go and have their input. The best way to get heard is to go to the source. I doubt Nvidia are trawling through all the forums looking for petty debates on drivers. Like I said, this thread is for reporting issues and not mud slinging (which is what you seem to be doing).
 
ubersonic said:
Humbug tried to start a thread for that but Rilot closed it and said that's what this thread is for, sorry :(
Click to expand...

I will go and start a thread on the Nvidia forum and ask "Should the 320.18 driver be pulled". I started this thread to get feedback on errors and to then try and help the users. You must have noticed how the other thread went and I don't want this thread going the same way.

Edit:

Done
https://forums.geforce.com/default/topic/547101/geforce-drivers/should-the-320-18-driver-be-pulled-/

Please go there to add your input on whether or not they should be pulled :)
 
Last edited:
You must log in or register to reply here.
Back
Top Bottom