320.18 Nvidia Drivers - Report your issues here

goodl · 20 Jun 2013 at 16:55

Rrof, we have a tentative theory its Precision X or MSIAB related, not overclocking needed though. All the systems I have seen with this issue have seen correlate under these conditions.

a. Multiple driver revs one on top of the other via GFE (bet they never thought that TLA through, or maybe they did and thought we wouldnt notice)
b. EVGA Precision installed for temp monitoring
c. Sub GK110 class GPU 2xx,4xx,6xx,770 (sorry, not a dig )
d. Windows 7 & 8 (haven't got any XP systems I support)
e. z68,z77 chipsets
f. Sandy and Ivy CPUS
g. SSD Syetem Drive and Closed Loop Watercooling (clutching at straws again but it's a common factor)

Lets try and narrow it down people, I think G can be safely disregarded but are there for the sake of completeness

humbug · 20 Jun 2013 at 17:10

goodl said:
Rrof, we have a tentative theory its Precision X or MSIAB related, not overclocking needed though. All the systems I have seen with this issue have seen correlate under these conditions.

a. Multiple driver revs one on top of the other via GFE (bet they never thought that TLA through, or maybe they did and thought we wouldnt notice)
b. EVGA Precision installed for temp monitoring
c. Sub GK110 class GPU 2xx,4xx,6xx,770 (sorry, not a dig )
d. Windows 7 & 8 (haven't got any XP systems I support)
e. z68,z77 chipsets
f. Sandy and Ivy CPUS
g. SSD Syetem Drive and Closed Loop Watercooling (clutching at straws again but it's a common factor)

Lets try and narrow it down people, I think G can be safely disregarded but are there for the sake of completeness

Is there any patterns among specific brands? Or ASIC, Memory IC's (Hynix / Elpida) Chokes, Mosfets, VR's, Caps, BIOS.....

Frenzy · 20 Jun 2013 at 17:11

I've tested against MSIAB 2.3.1 on W7 32 and haven't had any issues.

Rroff · 20 Jun 2013 at 17:13

goodl said:
Rrof, we have a tentative theory its Precision X or MSIAB related, not overclocking needed though. All the systems I have seen with this issue have seen correlate under these conditions.

a. Multiple driver revs one on top of the other via GFE (bet they never thought that TLA through, or maybe they did and thought we wouldnt notice)
b. EVGA Precision installed for temp monitoring
c. Sub GK110 class GPU 2xx,4xx,6xx,770 (sorry, not a dig )
d. Windows 7 & 8 (haven't got any XP systems I support)
e. z68,z77 chipsets
f. Sandy and Ivy CPUS
g. SSD Syetem Drive and Closed Loop Watercooling (clutching at straws again but it's a common factor)

Lets try and narrow it down people, I think G can be safely disregarded but are there for the sake of completeness

I surmised in another thread that it sounded like a conflict between a 3rd party tool like MSI AB, evga precision, etc. and the drivers - quite a few people who've reported GPUs dying have mentioned EVGA precision being installed. Most of my machines have MSI AB installed and so far not seen any issues so I'm inclinded to discount that but it could be due to a configuration of hardware or settings that I don't use.

goodl · 20 Jun 2013 at 17:14

humbug said:
Is there any patterns among specific brands? Or ASIC, Memory IC's (Hynix / Elpida) Chokes, Mosfets, VR's, Caps, BIOS.....

All the issues I have seen have been of reference designs, my punters wouldnt know a decent non ref card if it smacked them in the mouth (Not you Roachy, stand down

)

humbug · 20 Jun 2013 at 17:19

goodl said:
All the issues I have seen have been of reference designs, my punters wouldnt know a decent non ref card if it smacked them in the mouth (Not you Roachy, stand down )

Do they all share the same components? I don't want to point any fingers or make anything of it, its just deductive reasoning and we shouldn't rule anything out.

So perhaps a pattern in hardware components should be looked at.

Like anything a GPU is only as strong as its weakest component.

goodl · 20 Jun 2013 at 17:29

I'm a stickler for quality components and wont move on that,im midrange gigabyte for mobos, intel for cpus (no expections, corsair PSUs and branded ram, but to a customer a gpu is a race to the bottom on price. All I can insist on is warranty and even then I cant push that hard, its no skin off my nose if they wont listen.They just have a dead GPU they have to replace at their own cost or get reflowed.

goodl · 20 Jun 2013 at 17:36

plus i only do builds about once every quarter, hardware has always moved on

Frenzy · 20 Jun 2013 at 17:40

Looped GRID 2 benchmark on an MSI 660Ti for 30min with EVGA precision and MSIAB installed. Again no issues.

goodl · 20 Jun 2013 at 17:41

Frenzy stick Precision on as a bg task and see if it makes any diff

Frenzy · 20 Jun 2013 at 17:47

Sorry, what do you mean as a bg task? Background task? Isn't it a background task by default if I have GRID 2 full screen?

GTA767 · 20 Jun 2013 at 19:15

worst driver in the history of nvidia

hope new one will come out soon fixed

Alz_D · 20 Jun 2013 at 20:33

I fixed my bsod problems by uninstalling precision x. All runs perfect -except metro LL (that's just broken) mobo drivers are up to date, 320.18 drivers. While precX is running I get random driver irql not equal bsod regularly. While uninstalled I have had none. Hope next drivers fix it.

goodl · 20 Jun 2013 at 22:14

@Frenzy, sorry I've been testing on two monitors, of course

jimfowler_82 · 21 Jun 2013 at 07:26

IS 320.11 a safe driver to get? I got a 770 coming and i dont want any issues yet!

RetrogamerX · 21 Jun 2013 at 07:28

jimfowler_82 said:
IS 320.11 a safe driver to get? I got a 770 coming and i dont want any issues yet!

I have no issues at all with my 770 lightnings with 320.18 drivers. It a very low number having problems.

jimfowler_82 · 21 Jun 2013 at 07:30

RetrogamerX said:
I have no issues at all with my 770 lightnings with 320.18 drivers. It a very low number having problems.

Thanks mate

MoRT489 · 21 Jun 2013 at 07:59

After 10 pages and many people reporting graphical corruptions I don't think you can say it's a very low number anymore.

Kaapstad · 21 Jun 2013 at 09:27

MoRT489 said:
After 10 pages and many people reporting graphical corruptions I don't think you can say it's a very low number anymore.

When people talk about graphical corruptions it could be from all manner of things.

I play Civ5 a lot and have used AMD and NVidia cards with the game. I often see graphical corruption with both AMD and NVidia using lots of different drivers since the game launched.

The best drivers I have ever used with no corruption is the 320.18 drivers on Civ5.

Now how does that fit or not with what everyone else is posting.

My point is when we talk about corruption we need to be a bit more precise and detailed. It would be easy to talk about any driver AMD/NVidia and find faults/bugs in it.

Edit @MoRT489 perhaps you could compile a list of the most common faults/corruption. This would be helpful for other people to reference.

melmac · 21 Jun 2013 at 12:09

Kaapstad said:
When people talk about graphical corruptions it could be from all manner of things.

I play Civ5 a lot and have used AMD and NVidia cards with the game. I often see graphical corruption with both AMD and NVidia using lots of different drivers since the game launched.

The best drivers I have ever used with no corruption is the 320.18 drivers on Civ5.

Now how does that fit or not with what everyone else is posting.

My point is when we talk about corruption we need to be a bit more precise and detailed. It would be easy to talk about any driver AMD/NVidia and find faults/bugs in it.

Yes, but the problem with this is that most of the people complaining about these drivers have no issues when they roll back to older drivers. Too many people are reporting problems after installing this driver for it not be a driver issue.

Why is everybody not been affected? Don't know but look at the stuttering bug from last year, not everyone was affected with that either.