NVIDIA Releases 375.86 WHQL Driver Update
by Daniel Williams on November 18, 2016 10:00 PM EST
Two more weeks after NVIDIA’s last hotfix we have another WHQL update to cement those fixes, optimize more games, and prepare for more releases. Releases and updates have been coming swiftly, so let’s see what release 375.89 brings us.
Most of the fixes this week are moving from the 375.76 Hot Fix to this 375.86 WHQL release. Included in the hotfix were fixes for high refresh rate monitors experiencing flickering issues. Specifically, with G-Sync enabled while either running at 144Hz on GTX 1080 or while dragging or resizing windows at 165Hz. There was also an issue with artifacts in GIFs found from the 375.63 update that had been removed as well. Moving on to new fixes, the 375.70 driver caused smearing and ghosting, and the GTX 1080 was unable to enable surround with a SLI HB bridge and the wrong memory usage was being reported while gaming in SLI on Pascal GPUs. Lastly is a smaller fix with the game Battle Carnival being falsely detected as Bionic Commando.
We are receiving some extra optimizations for Tom Clancy’s The Division, Battlefield 1, and Civilization VI. Alongside these updates NVIDIA users are now ready for the Steep open beta which starts this Friday.
One more note before closing is that some issues are being investigated by NVIDIA. NVIDIA reports multi-GPU display issues in Battlefield one with this 375.86 update and GTX 1080/1070/1060 video memory getting stuck at 810MHz. Call of Duty: Infinite Warfare SLI will flicker with render resolution above 100 and there is a problem with incorrect Folding@Home work units after update to release 375. Though we’ve been seeing rather rapid fire releases for drivers from both camps lately, so fixes shouldn’t be far off.
(UPDATE: NVIDIA has a hotfix for the memory clock issue here)
Anyone interested can download the updated drivers through GeForce Experience or on the NVIDIA driver download page. More information on this update and further issues can be found in the 375.86 release notes.
Source: NVIDIA
Facebook
Twitter
RSS
20 Comments
View All Comments
JeffFlanagan - Monday, November 21, 2016 - link
It also seems to have caused problems with your caps-lock key.elevations - Thursday, November 17, 2016 - link
IF YOU HAVE A GTX 1060 DO NOT INSTALL THIS DRIVERAnotherGuy - Saturday, November 19, 2016 - link
WOW nVidia! And I thought AMD was the one known for bad drivers... makes me think going back to AMD after this 1060 I recently purchased! This is the worst experience I have ever had with a videocard, and I replace them every year or two... with last 5 years AMD only and never have a driver issue.... NVidia is releasing a new driver every week it seems...I do not want to hear anyone saying AMD has bad drivers after the recent weeks with nV
nevcairiel - Sunday, November 20, 2016 - link
Frequent releases doesn't necessarily mean bad drivers. Most of the recent releases were just "Game Ready" drivers for various game releases - of which there have been many the last couple weeks.The only really seriously broken driver was this one, and they released a fix within 48 hours (if not sooner).
eyk - Saturday, November 19, 2016 - link
375.95 WHQL is already in their drivers page, this article is outdated.HollyDOL - Sunday, November 20, 2016 - link
my 375.95 was installed Nov 18.... so 375.86 is really yesterday news...yannigr2 - Sunday, November 20, 2016 - link
The last 12-18 months, Nvidia's drivers are a mess. And we are not talking here about gaming performance, but stability and compatibility bugs. Nvidia has become worst in drivers than what ATI was considered in the past.nevcairiel - Sunday, November 20, 2016 - link
Except that AMD has not done great either, if not worse. The drivers for the RX480 (and others in that series) have been a real mess ever since the release of those cards.TheinsanegamerN - Monday, November 21, 2016 - link
AMD's drivers in the last few month have worked pretty well. I've not heard of widespread issues since the launch of the 480.BrokenCrayons - Monday, November 21, 2016 - link
It seems like a lot of driver fixes tend to be focused on multi-GPU configurations. There's rarely something wrong or terminally broken that requires major attention when you're only running one GPU. Its that sort of thing plus diminishing returns and added heat/power demand that makes more than one graphics card continue to seem like a decision lacking sensible thought. Its no wonder they're slowly eroding support for such configurations with this latest generation since they blemish the reputation of the company.