NVIDIA Releases GeForce 471.96 Game Ready Drivers

[btarunr]

NVIDIA today released the latest GeForce Game Ready drivers. Version 471.96 WHQL doesn't come with any new game optimizations tied to a game launch, but adds support for 6 new G-SYNC compatible displays, and adds 24 new titles to the GeForce Experience "Optimal" settings. The drivers also update scaling resolution in NVIDIA Image Sharpening feature. A handful bugs were also fixed. DPC latency being higher on 8 bpc color than 10 bpc color has been fixed. A problem detecting supported resolutions on Samsung Odyssey G9 has been fixed. A BSOD noticed when two of these displays are connected at 240 Hz, has also been fixed. NVDisplay.Container.exe constantly writing data to a ProgramData location has been fixed. Discrete NVIDIA GPUs frequently waiting up on notebooks with Windows 11, has been fixed. Topaz Denoise stability issues on "Turing" and "Volta" GPUs has been fixed. Grab the drivers from the link below.

DOWNLOAD: NVIDIA GeForce 471.96 WHQL



New Features and Other Changes

Updated scaling resolution in NVIDIA Image Sharpening.

GeForce Experience Settings Support

• Aliens: Fireteam Elite
• Bless Unleashed
• Blood of Heroes
• Car Mechanic Simulator 2021
• Doki Doki Literature Club Plus!
• Draw & Guess
• Faraday Protocol
• Final Fantasy
• Final Fantasy III
• Ghost Hunters Corp
• Golf With Your Friends
• GrandChase
• Humankind
• King's Bounty II
• Madden NFL 22
• Mini Motorways
• Psychonauts 2
• Quake Remastered
• SAMURAI WARRIORS 5
• Supraland
• The Great Ace Attorney Chronicles
• The Walking Dead: Onslaught
• Yakuza 4 Remastered
• Yakuza 5 Remastered

G-SYNC Support

• EVE Spectrum ES07D03
• Lenovo G27Q-20
• MSI MAG321QR
• Philips OLED806
• ViewSonic XG250
• Xiaomi O77M8-MAS

Fixed Issues in this Release

• DPC latency is higher when color mode is set to 8-bit color compared to 10-bit color.[3316424]
• Unable to detect supported display modes for the Samsung Odyssey G9 display [3332327]
• Blue-screen crash/reboot loop occurs when two Samsung Odyssey G9 displays @ 240 Hz are connected. [3256732]
• NVDisplay.Container.exe constantly writes data to C:\ProgramData\NVIDIA Corporation\nvtopps\nvtopps.db3. [3350171]
• [Windows 11][Notebook]: With the graphics mode set to Hybrid, the GPU frequently wakes up while idle. [3345922]
• [CUDA][Turing/Volta GPUs]: Stability issues with Topaz Denoise AI. [200755368]

View at TechPowerUp Main Site

 

[P4-630]

Known Issues​

• [Deathloop][HDR]:TDR/corruption occurs in the game with Windows HDR enabled. If this issue occurs, toggle the Windows HDR setting.
• [NVIDIA Control Panel]: After overinstalling the driver using express install when GPU scaling is enabled, the 0.59x upscaling factor is missing from the NVIDIA Control Panel scaling resolution list (Display > Change Resolution page).
  To work around, disable and then re-enable GPU scaling. Alternatively, perform a clean driver installation.
• [Battlefield V][DirectX 12]: The game may crash with HDR enabled. [3353767]
  To work around, enable HDR from the Windows display settings before launching the game.
• [YouTube]: Video playback stutters while scrolling down the YouTube page. [3129705]
• Tom Clancy’s The Division 2 may display graphical artifacts. [200754013]
• Sonic & All-Stars Racing Transformed may crash on courses where players drive through water. [3338967]

 

[Ferrum Master]

• [YouTube]: Video playback stutters while scrolling down the YouTube page. [3129705]

Rolfcopter

 

[ThrashZone]

Hi,
Yeah this driver is terrible tried it yesterday after using vnclean on it lol

 

[FierceRed]

Hi,
Yeah this driver is terrible tried it yesterday after using vnclean on it lol

Do you mind elaborating? What exactly made it terrible?

Not asking for full benchmarks, just your overall impressions.

Fixed Issues in this Release

• NVDisplay.Container.exe constantly writes data to C:\ProgramData\NVIDIA Corporation\nvtopps\nvtopps.db3. [3350171]

Wait, wtf? I tried googling that Bug number but couldn't find a detailed bounty/dossier on it.

I wonder how long that has been happening? While it probably wasn't at a volume that would affect SSD I/O or MTBF, I'm curious about the frequency of this activity.

 

[ThrashZone]

Do you mind elaborating? What exactly made it terrible?

Not asking for full benchmarks, just your overall impressions.



Wait, wtf? I tried googling that Bug number but couldn't find a detailed bounty/dossier on it.

I wonder how long that has been happening? While it probably wasn't at a volume that would affect SSD I/O or MTBF, I'm curious about the frequency of this activity.

Hi,
benchmark wouldn't even run kept dying back to 461.. and all was well again.
So yeah is not worth messing with maybe one before never got around to any between 461 and newest 471 to see if they were as bad.

 

[c2DDragon]

No issue so far for me.
Safe mode -> DDU -> everything seems fine.
I don't have any youtube video stutter while scrolling on Firefox neither on Edge.
I don't use a HDR screen.
I didn't try The Division 2 but it's not a problem since I don't play this game anymore these days.
I cannot notice the change about their DPC latency fix because I didn't even notice the bug.

 

[Easo]

• [YouTube]: Video playback stutters while scrolling down the YouTube page. [3129705]

Rolfcopter

Has been what, 1.5 years at this point?

 

[Mussels]

Oh good, the DPC latency bug has finally been fixed!

Edit: i thought this was why i had micro stutter, but then my SSD corrupted itself...

 

[YOUDIEMOFO]

Hi,
benchmark wouldn't even run kept dying back to 461.. and all was well again.
So yeah is not worth messing with maybe one before never got around to any between 461 and newest 471 to see if they were as bad.

If you've got issues with Amy driver from 471 anything I'd say you might need to check something else out in/on your system...

One should have zero issues unless they're ones mentioned in in the release notes.

That is unless it's a reproducible issue you could submit and help the world out...?

Just saying it won't run a particular benchmark and that it's garbage for your setup and you're done can't be it. Then maybe I'd want to fix something for my own sake?

 

[user50758]

Wait, wtf? I tried googling that Bug number but couldn't find a detailed bounty/dossier on it.

I wonder how long that has been happening? While it probably wasn't at a volume that would affect SSD I/O or MTBF, I'm curious about the frequency of this activity.

I've been running 471.68 and noticed this happening.
Applied an acceptable workaround found here and also linked to here.

 

[dcf-joe]

• [YouTube]: Video playback stutters while scrolling down the YouTube page. [3129705]

Yeah, this one has been on their bug list for quite a while. However, in my own personal experience, I have never actually experienced this issue.

 

[Legacy-ZA]

Aha, finally fixed the DPC latency issue, well well, how many years is this now? I thought it was just us nVidia? lol

 

[Ferrum Master]

Yeah, this one has been on their bug list for quite a while. However, in my own personal experience, I have never actually experienced this issue.

That's why I laugh...

I have actually... not that it causes the end of the world for me...

But kinda sad if you think about it deeper.

 

[P4-630]

Yeah, this one has been on their bug list for quite a while. However, in my own personal experience, I have never actually experienced this issue.

Can confirm, I never experienced this issue either, not on this driver nor the previous drivers.

What I did experience quite sometime was webpages flickering in google chrome, that luckily has been fixed 2- 3 drivers ago.

 

[5 o'clock Charlie]

Tom Clancy’s The Division 2 may display graphical artifacts. [200754013]

This is the first time I have seen this logged as a known issue, but I am curious when this was first declared in their release notes? I am currently running driver version 461.09 and started seeing this type of issue during gameplay about 2-3 weeks ago. From a quick search online, first mention of it was with driver version 471.68.

 

[P4-630]

This is the first time I have seen this logged as a known issue, but I am curious when this was first declared in their release notes? I am currently running driver version 461.09 and started seeing this type of issue during gameplay about 2-3 weeks ago. From a quick search online, first mention of it was with driver version 471.68.

I wouldn't know, also I don't have that game.