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.
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![]()
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...
I've seen the odd black screen and "display driver stopped/recovered" message with 320.00
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?
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
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.
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.
As far as cards dieing is it limlited to 6xx/7xx series or is it effecting previous generations?
As far as cards dieing is it limlited to 6xx/7xx series or is it effecting previous generations?
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!
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.
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...
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/
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?
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: