GeForce 451.85 hotfix driver download





Download the Nvidia GeForce 451.85 hotfix driver, as released by NVIDIA. This release fixes issues with Shadow of the Tomb Raider, Death Stranding as well as other issues at hand.
Game Ready Drivers provide the best possible gaming experience for all major new releases, including Virtual Reality games. Prior to a new title launching, our driver team is working up until the last minute to ensure every performance tweak and bug fix is optimized for the best gameplay on day-1. We have a discussion thread open on this driver here in our Nvidia driver discussion forums. For those that wonder, the DCH driver is a Microsoft DCH (Declarative Componentized Hardware supported apps) driver, and refers to a new Windows 10 driver package preinstalled by OEMS implementing the Microsoft Universal Driver paradigm. While the base core component files remain the same, the way DCH drivers are packaged differs from previous Legacy (Standard) drivers.
GeForce Hotfix display driver version 451.85 is based on our latest Game Ready Driver 451.67.
This Hotfix driver resolves the following issues:
- [Shadow of the Tomb Raider][DirectX 12]: The game may crash when launched with Hardware-accelerated GPU scheduling enabled.
- [Death Stranding]: Texture corruption may be observed during gameplay on GeForce GTX 16/RTX 20 series GPUs
- NVIDIA Control Panel does not display the native resolution of some HDTVs with invalid timings
- Some games may exhibit random freezes that lasts for a few seconds during gameplay.
- Some displays may show a green tint when Windows Night Light is enabled
- [Forza Motorsport 7]: Game starts to stutter after racing a few laps
- [G-Sync Compatible] Adds support for the Samsung 27" Odyssey G7 gaming monitor
GeForce RTX 20 Series:
GeForce RTX 2080 Ti, GeForce RTX 2080 (Super), GeForce RTX 2070 (Super), GeForce 2060 (Super), Titan RTX
GeForce 16 Series:
GeForce GTX 1660 SUPER/Ti, GeForce GTX 1660, GeForce GTX 1650, GeForce GTX 1650 Super
NVIDIA TITAN Series
NVIDIA TITAN V, NVIDIA TITAN Xp, NVIDIA TITAN X (Pascal), GeForce GTX TITAN, GeForce GTX TITAN X, GeForce GTX TITAN Black, GeForce GTX TITAN Z
GeForce 10 Series
GeForce GTX 1080 Ti, GeForce GTX 1080, GeForce GTX 1070 Ti, GeForce GTX 1070, GeForce GTX 1660 Ti, GeForce GTX 1060, GeForce GTX 1650, GeForce GTX 1050 Ti, GeForce GTX 1050, GeForce GT 1030
GeForce 900 Series
GeForce GTX 980 Ti, GeForce GTX 980, GeForce GTX 970, GeForce GTX 960, GeForce GTX 950
GeForce 700 Series
GeForce GTX 780 Ti, GeForce GTX 780, GeForce GTX 770, GeForce GTX 760, GeForce GTX 760 Ti (OEM), GeForce GTX 750 Ti, GeForce GTX 750, GeForce GTX 745, GeForce GT 740, GeForce GT 730, GeForce GT 720, GeForce GT 710, GeForce GT 705
GeForce 600 Series
GeForce GTX 690, GeForce GTX 680, GeForce GTX 670, GeForce GTX 660 Ti, GeForce GTX 660, GeForce GTX 650 Ti BOOST, GeForce GTX 650 Ti, GeForce GTX 650, GeForce GTX 645, GeForce GT 645, GeForce GT 640, GeForce GT 635, GeForce GT 630, GeForce GT 620, GeForce GT 610, GeForce 605
Have you read our MSI GeForce GTX 1650 SUPER GAMING X review already?
4 pages 1 2 3 4
Junior Member
Posts: 7
Joined: 2020-03-27
I'm getting kinda tired of nVidia breaking the Forza games over and over and over. Their drivers need a major overhaul and so does their CP. I REALLY hope big Navi is good. I'll sell my 2080ti in a heartbeat... Of course that depends on big navis performance vs the 3080 or 90... Whatever the new "2080ti" is.
Senior Member
Posts: 681
Joined: 2017-02-04
It seems to me that it would be a freeing experience to have separate drivers for each series of releases. Instead of mush moshing every freaking gpu ever released in to one cover all driver, yes I know they have different "driver numbers" but it is still all a hot mess cover all driver, and just release drivers for say 3000 series only and make it policy from now on. Maybe I am ignorant of the way hardware is utilized, but wouldn't it allow them to expand on their choices of hardware utilization knowing that it could have its own driver set?
Senior Member
Posts: 15368
Joined: 2018-03-21
Theres a thing called a support scope, when you do this it increases exponentially until nothing gets fixed and cards are just left unsupported upon the release of your next one.
Aka, Intel.
Senior Member
Posts: 17563
Joined: 2009-02-25
Both NVIDIA and AMD have dropped a few things like the dedicated 32-bit builds and I assume the older GPU's will eventually be phased out of active support when deemed as needed though NVIDIA having a bigger more well funded team here might be less of a issue than AMD although in turn the GCN architecture has been added to and scaled up and supported though RDNA might make for a cut-off point although nowhere near soon.
AMD also had the idea to just outright end Windows 8 support early although I assume NVIDIA and AMD will both eventually reduce Windows 7 support now that it's EOL but again it's a pretty popular OS still so might not happen anytime soon plus different teams and how the code is based and updated.
Control panel is just a shell isn't it exposing a couple of settings, could look better but it works and it's less messy for NVIDIA than AMD's attempt at all the settings and menus within menus and various more hidden sub-menus.
451.85 here sounds like it takes care of several important outstanding issues and with Ampere finalizing and getting supported focus should shift to fixing remaining reported outstanding bugs as I expect there to be a pretty built up and effective bug tracker for this and what gets priority and has to be dealt with immediately like this thing with hardware accelerated GPU scheduling and a assortment of issues now that it's in the public release driver channel.
Can't really jam in some automatic logging and telemetry stuff so also dependent on users actually filling out bug reports or posting about them where community reps can see and submit discussed issues and after that also the importance of detailed reports and replicating the problem so it can be debugged and resolved which I assume at least gets incredibly complex when it wasn't just the driver.

It was this or that hardware with some maybe not 100% bios adjustments and these third party programs on this OS build but maybe it was tweaked in some ways and then software specific bugs and compatibility issues (Call of Duty 2020 whatever it's named seems to be a big one for these currently.) plus you also get D3D12 and Vulkan now and these are even more hardware sensitive like RAM for example.
Plus support from the developers if the game is still in active support and instead of doing some profile tweaking or weird deeper level driver workaround or outright hack or replacing shaders or whatever goes on in here (Some stuff is just really broken, surprised some titles even start at all once you know just how badly some things can get.) although I suppose Microsoft and their studios can put in the resources and have the knowledge to work with the low-level API's a bit better plus involvement from AMD and NVIDIA.
(Well usually, Halo and it's assortment of games had a lot of problems early on but it's still in active support and they are putting in a lot of work to resolve even some of the less pressing issues which is really good to see instead of just demoting it as DNF or Do Not Fix.)
EDIT: Which I suppose is mostly just a longer way of saying that troubleshooting is really complicated and this driver work is probably one of the most difficult things with how massive and complex the actual driver code base itself must be.
Just the actual game profiles alone and title specific tweaks or changes has to be a huge something of code with old and new fixes and how to best go about updating and supporting this.
4 pages 1 2 3 4
Senior Member
Posts: 3343
Joined: 2008-03-08
LOL a bot hating Sora from Nvidia forums,that name is too funny.Thanks for heads up on the driver update