Wednesday, November 16th 2016

Users report multiple issues with GeForce 375.86 WHQL Drivers

If you have installed the GeForce 375.86 WHQL drivers you may experience a variety of issues. According to users on Guru3D forums, and indeed users here on our very own forums, the drivers released just yesterday have had reports where certain games frame rates are cut in half, however more alarmingly many users also report memory clock speed drops resulting in on-screen flickering and instability.

The memory speed and flickering issues appear to be limited to cards using the "Pascal" architecture, NVIDIA have acknowledged that the issues are widespread and work is already underway to remedy them. We expect either that a hotfix or new WHQL driver set will follow shortly, depending on their release cycle.
Add your own comment

61 Comments on Users report multiple issues with GeForce 375.86 WHQL Drivers

#51
cadaveca
My name is Dave
FluffmeisterQuick support as always.

First world problems and another bowl of corn flakes to try.
To be fair, many people are using "game-ready" drivers or hotfix drivers, which aren't WHQL. They are beta, and are really only tuned for the specific apps mentioned, IMHO. So, when doing beta, unexpected things can happen, and that's that. This new release is not WHQL, so anyone with problems should probably stick to WHQL releases, and have a bit of patience for those releases. I think both NV and AMD have issues at times, and it sucks, but it doesn't really bother me at all. I had a PCIe slot die while using the 375.86 driver, as well as some stability issues (ASUS "surge protect" kept triggering), and while I might like to blame driver, the issues I had were probably an indicator of my board starting to give up. My CPU and mem is OC'ed, which means that I took a chance that things might happen, and they did unexpectedly. I've been running this rig since before Skylake's official launch, so it served me well enough; I am expecting a barebones PC from MSI in the near future that I'll be taking these parts out of anyway, and then I'll get my new bowl to eat out of. :P
Posted on Reply
#52
jigar2speed
FluffmeisterHow about: nVidia's driver issues spawn shit metaphors.
How about we stop advertising people that Nvidia has superior drivers ?
Posted on Reply
#53
Caring1
FluffmeisterWe all eat shit, and die...
Fixed that for you :laugh:
Posted on Reply
#54
Prima.Vera
After nVidia goes fully into autonomous drive for automobiles market, how do you think people will react after a car's accident because of a driver (the software one) bug?? :) :)
This is indeed now a minor annoying issue, nothing more, but when shmit will start to get serious for nVidia, you cannot play with people's life.
Posted on Reply
#55
EarthDog
jigar2speedHow about we stop advertising people that Nvidia has superior drivers ?
:roll:


Who gives a shit...really.
Posted on Reply
#56
jigar2speed
EarthDog:roll:


Who gives a shit...really.
You are telling me all this time i was talking to sheeps ? Sorry my bad, carry on with your line. ;)
Posted on Reply
#58
EarthDog
jigar2speedYou are telling me all this time i was talking to sheeps ? Sorry my bad, carry on with your line. ;)
Sheep...naaa, just not a drama filled nut job about driver issues as some can be. ;)

(Not saying you)
Posted on Reply
#59
TheOne
NVIDIA pulled 375.86 and now 375.95 is WHQL and listed on their driver page.
Posted on Reply
#60
SilveradoCyn
I have made 3 driver updates in 2 days and still have CUDA broken!
I understand this issue was forced by a Win10 Preview version upgrade, but any idea when it might be resolved?
- - SilveradoCyn
Posted on Reply
#61
SilveradoCyn
cadavecaSecond slot doesn't work at all any more. Swapped CPUs, and everything else, same problem. Both cards work individually.
I have two systems where the second card quit working on .86. Today's driver may have fixed it, but now I can't get CUDA to run at all.
Everyone should understand Microsoft had dropped a new preview version of Windows 10 that broke the drivers (as usual) and NVidia had to respond quickly.
Unfortunately the response seems to have broken more stuff than it was designed to fix.
There is no joy in that driver group right now...
Posted on Reply
Add your own comment
Apr 23rd, 2024 12:04 EDT change timezone

New Forum Posts

Popular Reviews

Controversial News Posts