GeForce 471.22 Hotfix driver download

Videocards - NVIDIA GeForce Windows 10 | 11 683 Updated by Hilbert Hagedoorn

Click here to post a comment for GeForce 471.22 Hotfix driver download on our message forum
#5926682
https://forums.guru3d.com/data/avatars/m/270/270091.jpg
Does this fix the issue where turning on RT and DLSS on Doom Eternal causes the framerate to be stuck around 37 to 40FPS? Basically the GPU is being underutilized
#5926684
https://forums.guru3d.com/data/avatars/m/166/166060.jpg
DonMigs85:

Does this fix the issue where turning on RT and DLSS on Doom Eternal causes the framerate to be stuck around 37 to 40FPS? Basically the GPU is being underutilized
The hotfix addresses the following issue: Doom Eternal may crash to desktop during gameplay [3331270] League of Legends [Tencent] may fail to launch [200744747] Mouse cursor color may shift when connected to certain DSC monitors in HDR mode [200741796] [HDMI 2.1][8K] HDMI audio playback may become distorted after changing display modes [3268312] Some displays screen resolution limited to 640x480 after driver update [3330750]
#5926817
https://forums.guru3d.com/data/avatars/m/273/273678.jpg
rosp:

Just installed this (custom install, deselected HD audio and USC drivers). Installation completed successfully, but now my system says I have 456.71 installed! Had the exact same thing happen a few drivers before. Previous driver was 471.11, RTX 2060 card
you have 456.71 installed, blame windows update.
DonMigs85:

Does this fix the issue where turning on RT and DLSS on Doom Eternal causes the framerate to be stuck around 37 to 40FPS? Basically the GPU is being underutilized
you can fix this yourself, its not a driver issue.
#5926857
data/avatar/default/avatar11.webp
rosp:

Just installed this (custom install, deselected HD audio and USC drivers). Installation completed successfully, but now my system says I have 456.71 installed! Had the exact same thing happen a few drivers before. Previous driver was 471.11, RTX 2060 card
Astyanax:

you have 456.71 installed, blame windows update.
Same thing happened to me, previous driver 471.11. Went into device manager, update driver and manually selected the driver that was listed in there (471.22). Not sure why this happens but yeah, it can be quite annoying!