• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.
  • The forums have been upgraded with support for dark mode. By default it will follow the setting on your system/browser. You may override it by scrolling to the end of the page and clicking the gears icon.

nVidia 320.18 drivers killing GPUs?

ViperXTR

ViperXTR

Joined
Jan 31, 2011
Messages
2,236 (0.42/day)
System Specs
System Name Ultima
Processor AMD Ryzen 7 5800X
Motherboard MSI Mag B550M Mortar
Cooling Arctic Liquid Freezer II 240 rev4 w/ Ryzen offset mount
Memory G.SKill Ripjaws V 2x16GB DDR4 3600
Video Card(s) Palit GeForce RTX 4070 12GB Dual
Storage WD Black SN850X 2TB Gen4, Samsung 970 Evo Plus 500GB , 1TB Crucial MX500 SSD sata,
Display(s) ASUS TUF VG249Q3A 24" 1080p 165-180Hz VRR
Case DarkFlash DLM21 Mesh
Audio Device(s) Onboard Realtek ALC1200 Audio/Nvidia HD Audio
Power Supply Corsair RM650
Mouse Rog Strix Impact 3 Wireless | Wacom Intuos CTH-480
Keyboard A4Tech B314 Keyboard
Software Windows 10 Pro
Ive only seen this issue on first gen Fermi cards, and good riddance, those cards are junk anyways.
 
Been using 320.18 drivers for days, no issues whatsoever tho :confused:

Running overclocked cards also.

1202 MHz Core and 7 GHz memory.
 
I have been using 320.18 about 1 day after it was released. I have used my Desktop with GTX 670/660 for about 3 hours total with no problems, but no gaming. I mostly use my laptop. I'm not going to uninstall, yet.
 
Doesn't this come up every few driver releases? I keep seeing this complaint but never see anything concrete or scientific come out of it, probably why it's never a big news story.
 
I had strange 'barcoding' of textures in some games with 320.18. Had to rollback to 314.22.
 
I'm glad I haven't gotten round to installing it yet. As I've got a GTX 590 which can be easily damaged through overstress, it might be extra prudent to leave it out.

In fact, I don't overclock any of my graphics cards to avoid potentially damaging them.
 
qubit said:
I'm glad I haven't gotten round to installing it yet. As I've got a GTX 590 which can be easily damaged through overstress, it might be extra prudent to leave it out.

In fact, I don't overclock any of my graphics cards to avoid potentially damaging them.
Click to expand...

I over clock the heck out of my cards. When I spend 2 grand on new cards I want them to run as fast as possible. I do have water blocks on both so they can take it. Spending money like I did for two GTX 690s and not water cooling them and then not over clocking them should be against the law....lol that is like haveing a Porsche 911 turbo with a VW engine in it. O wait it does... VW owns Porsche.. Still you get my point.....;)
 
Are my two GTX 550 Ti's in SLI safe?
 
Knight091 said:
I over clock the heck out of my cards. When I spend 2 grand on new cards I want them to run as fast as possible. I do have water blocks on both so they can take it. Spending money like I did for two GTX 690s and not water cooling them and then not over clocking them should be against the law....lol that is like haveing a Porsche 911 turbo with a VW engine in it. O wait it does... VW owns Porsche.. Still you get my point.....;)
Click to expand...

Whether you overclock them like that or not really boils down to money and how much you can afford to replace a destroyed card. Most of us are not as rich as you and have to take care of our stuff.

Those waterblocks will keep the temperatures down, but the VRMs, GPU and other components are still getting massively stressed out from the out of spec extra voltage and clock speed and will die a lot sooner than stock speeds. Don't kid yourself that they "can take it" forever.
 
after installing this shitty driver. i had an unexpected experience with "no display" after bios booting for around 10 - 15 secs also image corruption on GRID 2, it looks like my card got an artifact.
 
Last edited:
I've had no problem with my GTX 670. I'm not to worries about it.
 
I lost over 1k score in FFXIV ARR benchmark, because of this shite driver.
 
It makes you wonder how crap like this gets WHQL certified, doesn't it? What does it say about Microsoft's driver quality testing? Can't be too hot, can it?
 
No issues here. Had one single gfx glitch in BF3 but it wasn't repeated. If anything, my set up seems more stable now from the previous ones.
 
Been running it on the 780 since I got the card, no complaints, although me and UnholyWar crash in League of Legends at the start of every single match due to incompatibilities with 320.18. Everything else has run perfectly. Done a lot of gaming, seems solid. PLEASE FIX THE LoL ISSUE!
 
I've had twice the problem that happens with bf3, other games work fine though. and if I rma it(if the problem stays) will they accept it?
 
Black.Raven said:
I've had twice the problem that happens with bf3, other games work fine though. and if I rma it(if the problem stays) will they accept it?
Click to expand...

You can't RMA it if it's a driver problem (normally). Just roll back to previous drivers.

It's a pain in the ass when a driver releases that should be stable but the problem is normally incompatibility with something else (which i guess is what the WHQL is meant to sort out).

I prefer these to the previous beta's and the previous WHQL. Doesn't mean they're not 'faulty' though - just means it's luck of the draw which is kind of run of the mill for driver releases.
 
Battlefield 3 can't have problems because Battlefield 3 itself is a problem.
 
qubit said:
It makes you wonder how crap like this gets WHQL certified, doesn't it? What does it say about Microsoft's driver quality testing? Can't be too hot, can it?
Click to expand...

Microsoft doesn't test the drivers with cards if that's what you're thinking, they just look at the code to see if it conforms to WDM.
 
TRWOV said:
Microsoft doesn't test the drivers with cards if that's what you're thinking, they just look at the code to see if it conforms to WDM.
Click to expand...

Yes, I was thinking that they actually tested it with sample hardware. Clearly WHQL certification has its limits and a junky driver can still sail through.
 
Since when software damages hardware like this is intended to show... in a driver update?

I have 318.20 with different sli with a 560TI+560 no problems at all.
 
I don't have any issues but I do extremely clean installs, deleting every folder, file, and registry entry made by nvidia before updating. That helps with some issues.
 
You must log in or register to reply here.
Back
Top