Thursday, November 3rd 2016

NVIDIA Issues the GeForce Hotfix Driver Version 375.76

NVIDIA has issued a Hotfix driver, version number 375.76, which deals with some issues identified in their previous WHQL driver version, 375.70. Namely, the hotfix drivers fix occasional flickers on high refresh-rate monitors, as well as GIF artifacting.

The hotfix also includes all of the previous updates from NVIDIA's WHQL driver release, such as driver optimization, SLI support (provided the game engine supports multi-GPU), and GeForce Experience optimal settings for Call of Duty: Infinite Warfare, Dishonored 2, and Titanfall 2, and include optimization for "The Elder Scrolls V: Skyrim Special Edition" and "Obduction VR." Grab the drivers from the links below.
DOWNLOAD: NVIDIA GeForce 375.76 Hotfix Driver for Windows 10 64-bit | Windows 10 32-bit | Windows 8/7/Vista 64-bit | Windows 8/7/Vista 32-bit
Add your own comment

26 Comments on NVIDIA Issues the GeForce Hotfix Driver Version 375.76

#1
TheLostSwede
Not just GIF's, but also some videos, for example on Facebook.
Posted on Reply
#2
rtwjunkie
PC Gaming Enthusiast
And once again, 3 in a row. Nvidia went through a whole summer last year they couldn't get a driver right. This year has had at least 10 dud drivers. I really do not understand the sentiment so many have that AMD sucks at drivers, and Nvidia is great with them.

Before any non regulars flame me, take a moment to check my system specs and my signature. I'm an equal opportunity GPU player, with a 2:1 Nvidia to AMD ratio.
Posted on Reply
#3
R-T-B
rtwjunkieAnd once again, 3 in a row. Nvidia went through a whole summer last year they couldn't get a driver right. This year has had at least 10 dud drivers. I really do not understand the sentiment so many have that AMD sucks at drivers, and Nvidia is great with them.

Before any non regulars flame me, take a moment to check my system specs and my signature. I'm an equal opportunity GPU player, with a 2:1 Nvidia to AMD ratio.
My main argument is that both drivers suck, but nvidia sucks less.

This comes mainly from the fact that they are better optimized (when they do work with a good release anyways) and use threading better, etc. I'm not saying they don't suck, because they do 90% of the time, but when they get a release right, the model they use for their driver architechture is pretty good.
Posted on Reply
#4
rtwjunkie
PC Gaming Enthusiast
R-T-BMy main argument is that both drivers suck, but nvidia sucks less.

This comes mainly from the fact that they are better optimized (when they do work with a good release anyways) and use threading better, etc. I'm not saying they don't suck, because they do 90% of the time, but when they get a release right, the model they use for their driver architechture is pretty good.
Yeah, I'll give you that, when they get a good one, it stays really good. In fact I've frequently stuck with a good, stable driver on new games that several new drivers may have been optimized for, and still enjoyed a good gaming experience.
Posted on Reply
#5
P4-630
TheLostSwedeNot just GIF's, but also some videos, for example on Facebook.
No problems here with previous driver, also my monitor is just 60Hz.
I'll wait for the next one.
Posted on Reply
#6
Cybrnook2002
rtwjunkieAnd once again, 3 in a row. Nvidia went through a whole summer last year they couldn't get a driver right. This year has had at least 10 dud drivers. I really do not understand the sentiment so many have that AMD sucks at drivers, and Nvidia is great with them.

Before any non regulars flame me, take a moment to check my system specs and my signature. I'm an equal opportunity GPU player, with a 2:1 Nvidia to AMD ratio.
I agree with you!
Posted on Reply
#7
bug
rtwjunkieAnd once again, 3 in a row. Nvidia went through a whole summer last year they couldn't get a driver right. This year has had at least 10 dud drivers. I really do not understand the sentiment so many have that AMD sucks at drivers, and Nvidia is great with them.

Before any non regulars flame me, take a moment to check my system specs and my signature. I'm an equal opportunity GPU player, with a 2:1 Nvidia to AMD ratio.
Probably because AMD has their traditional crappy OpenGL performance (which means their cards are much slower on Linux), whereas in this case, we're talking about some flickering in some select few instances.

But really, when people say "suck", they simply mean that one company is a bit better than the other. I've had "problematic" drivers from Nvidia installed and never saw an issue and I imagine AMD users have had similar experiences. Most of the times the drivers (from either side) work fine, but we tend to disregard those and only concentrate on the few instances where they don't.
Posted on Reply
#8
newtekie1
Semi-Retired Folder
rtwjunkieAnd once again, 3 in a row. Nvidia went through a whole summer last year they couldn't get a driver right. This year has had at least 10 dud drivers. I really do not understand the sentiment so many have that AMD sucks at drivers, and Nvidia is great with them.

Before any non regulars flame me, take a moment to check my system specs and my signature. I'm an equal opportunity GPU player, with a 2:1 Nvidia to AMD ratio.
AMD's driver department went through a really bad spell. To the point that they released buggy drivers for over a year straight. Sure, the drivers were usable and you could correct for the bug, but it was a well documented bug with HDMI that they knew about and just never fixed. NVidia has had some less than perfect drivers from time to time, but they've never gone over a year releasing drivers with the same well known bug. Then they just kind of dropped off the face of the earth and went months between driver releases.

But having said that, I wouldn't say AMD sucks at drivers and nVidia is great. Just that nVidia is better at drivers compared to AMD. When there is a bug, nVidia fixes it pretty quickly. They are also pushing game ready drivers out on pretty much launch day of all the major releases, which AMD still struggles to do.
Posted on Reply
#9
AsRock
TPU addict
newtekie1AMD's driver department went through a really bad spell. To the point that they released buggy drivers for over a year straight. Sure, the drivers were usable and you could correct for the bug, but it was a well documented bug with HDMI that they knew about and just never fixed. NVidia has had some less than perfect drivers from time to time, but they've never gone over a year releasing drivers with the same well known bug. Then they just kind of dropped off the face of the earth and went months between driver releases.

But having said that, I wouldn't say AMD sucks at drivers and nVidia is great. Just that nVidia is better at drivers compared to AMD. When there is a bug, nVidia fixes it pretty quickly. They are also pushing game ready drivers out on pretty much launch day of all the major releases, which AMD still struggles to do.
And yet i never had any issue's with the HDMI or any other in that fact.

Anyways good to see them getting some more fixes out there.
Posted on Reply
#10
MxPhenom 216
ASIC Engineer
Ive only had AMD GPUs twice and not a single problem with the drivers. Ive had had about 4-5 Nvidia GPUs and haven't had any significant problems with those either. Other than the obvious performance issues and DX crashes that seemed to happen with my 780 when the 900 series came out and all driver performance went to shit for Kepler.
Posted on Reply
#11
xorbe
Hotfix tend to be better than their whql branded, heh. HF ftw! Wait wait wait, FTWs are on fire. HF forever!
Posted on Reply
#12
TheOne
Their drivers were better back when they did open betas before WHQL release.
Posted on Reply
#13
avatar_raq
I second what others said, both nVidia and AMD suck when it comes to drivers. I have owned one AMD GPU (5870) and till now I cannot forget how it took AMD over a year just to permanently fix cursor corruption in eyefinity. I did enjoy the card though and it is still functional in a friend's PC 6 years later!
Posted on Reply
#14
newtekie1
Semi-Retired Folder
AsRockAnd yet i never had any issue's with the HDMI or any other in that fact.

Anyways good to see them getting some more fixes out there.
It only happened when connected to an HDTV, it would incorrectly set the overscan to something other than 0 when connected to a HDTV.
Posted on Reply
#15
AsRock
TPU addict
Don't you just use the overscan option to correct that ?, i used to get that with my HDTV WOW a hell long time ago and just had to go in to the options and correct it. For at least a year now i have not even had to touch the option.
Posted on Reply
#16
newtekie1
Semi-Retired Folder
AsRockDon't you just use the overscan option to correct that ?, i used to get that with my HDTV WOW a hell long time ago and just had to go in to the options and correct it. For at least a year now i have not even had to touch the option.
Yes, I said that you could correct the bug. But the fact is that it was a bug that existed in the drivers for well over a year. You shouldn't have to go into the settings to change it, it should default to 0. And it would also revert the setting every time you updated the driver. So every time you installed a new driver, you had to go back in and change the setting again.
Posted on Reply
#17
AsRock
TPU addict
Hardly worth bringing up that bug lol, be a much worse issue today with win10 i guess with windows auto updating drivers and shit, but the bug is squashed now so.

Better have that scaling issue over flicker gif's and flickering screen that's for sure. Which reminds me the 4870\90 i had had that when you messed with the memory clocks.

Nothing compared to the issue's i \ others were having with 7800\7900 back in the day with the stupid hot chip on the back of the cards which hung just over the sough bridge.

Drivers have bugs life goes on with either side, in the end both sides have there fair share but personally have had 0 issue.
Posted on Reply
#18
Fluffmeister
Based on AMD's latest BETA things aren't all rosy in the red camp either, but drivers are complicated with countless apps to support so it's no wonder things go wrong from time to time.

As always I welcome the prompt support.
Posted on Reply
#21
kn00tcn
AsRockDon't you just use the overscan option to correct that ?, i used to get that with my HDTV WOW a hell long time ago and just had to go in to the options and correct it. For at least a year now i have not even had to touch the option.
newtekie1Yes, I said that you could correct the bug. But the fact is that it was a bug that existed in the drivers for well over a year. You shouldn't have to go into the settings to change it, it should default to 0. And it would also revert the setting every time you updated the driver. So every time you installed a new driver, you had to go back in and change the setting again.
it's not a bug, it's a feature, it's the assumption that tv output needs overscan or underscan cuz tv standards suck (as do many tvs that over or underscan themselves)

nvidia has the exact same type of feature-not-bug regarding rgb-limited vs rgb-full, which makes so many people think nvidia is always washed out (the heck is wrong with them thinking washed out is nvidia's official colors)

these companies need to popup an explanation on first boot or have a calibration section that very specifically goes through things that sometimes are required to be tweaked according to the user's monitor

also, sometimes there are bugs that nvidia has ignored for years & it's not a new thing tied to the recent failures either.. back in the dx10 days, an 8800gts had a known bug in unreal engine 2 (or just ut2k4?) that kept being ignored, it had a long thread in the forum that kept going for over a year & so on, i forgot the exact details but it was either about input lag or performance
Posted on Reply
#22
Evo85
THIS is why I wait 2 weeks to D/L a new driver.
Posted on Reply
#23
Prima.Vera
Both companies are delivering crappy drivers sometimes, that's a fact. However nVidia is always bringing fixes fast, compared to AMD, that even after months, they are still not fixing the issues. That's the main difference.

BTW, driver seems to be pulled from the main site.
Is .70 version only
Posted on Reply
#24
lorraine walsh
Does anyone know what the performance is different when compared to 357.63?
Posted on Reply
#25
qubit
Overclocked quantum bit
newtekie1It only happened when connected to an HDTV, it would incorrectly set the overscan to something other than 0 when connected to a HDTV.
That's such a dumb bug. No excuse for it at all and compounded greatly by AMD's refusal to fix it. :shadedshu:

I wouldn't be so scathing if it was something obscure like texture corruption in a particular game when AA is maxed out at 4K resolution on a particular model of card and on a certain OS, for example. I could understand a bug like that and the difficulty of pinning it down, but not this stupidness.
Posted on Reply
Add your own comment
May 22nd, 2022 03:54 EDT change timezone

New Forum Posts

Popular Reviews

Controversial News Posts