Download: GeForce 471.41 WHQL drivers

#5930482

kx11

2021-07-19 19:22

Older driver DLSS becnhmark RDR2 [youtube=VP6nLZxY14Q] Latest driver [youtube=JfgslAD900U]

#5930485

Neo Cyrus

2021-07-19 19:38

ReShade still fails to compile CAS on this driver, in certain games/programs. I'm not even sure how far back I'd have to go in drivers to fix it, but it was broken on the last hotfix as well.

#5930488

aufkrawall2

2021-07-19 19:49

Neo Cyrus:

ReShade still fails to compile CAS on this driver, in certain games/programs. I'm not even sure how far back I'd have to go in drivers to fix it, but it was broken on the last hotfix as well.

Can you list all affected games? So far it has been working everywhere for me.

#5930490

Falkentyne

2021-07-19 19:57

tty8k:

I will test this release today but in beta testing version the MPO 8bit latency issue was fixed with no need to disable MPO with registry key anymore. Unless this is a different branch or changes reverted. I'll be back with confirmation.

Any way to get this test driver?

#5930496

JamesSneed

2021-07-19 20:35

Reddoguk:

I'll do some RDR2 benches later to see if there is any improvement but for now it's just too freakin hot here in the UK, i'm afraid my system might start to throttle because my house feels like it's 40C.

Good time to do stress tests for any OC's though. Worst case testing.

#5930498

Neo Cyrus

2021-07-19 20:50

aufkrawall2:

Can you list all affected games? So far it has been working everywhere for me.

I've only tested 2 things so far because those were what I was playing when I first noticed a driver update broke them: Tekken 7, and more importantly Ryujinx since that means it's broken for all Switch games for me.

#5930500

Jen1

2021-07-19 21:14

I will pass this driver as someone has reported BSOD on the geforce forum, although I am already on Windows 11. I really that NVIDIA will start making stable and beta drivers, Stable for those who work on their PC and can't afford BSOD, Beta for gamers and new features enthusiasts, until then I will stick to the studio drivers. Still using 471.22 as it is a hotfix for 471.11 which was a studio driver.

#5930502

cricket bones

2021-07-19 21:20

Jen1:

I will pass this driver as someone has reported BSOD on the geforce forum, although I am already on Windows 11. I really that NVIDIA will start making stable and beta drivers, Stable for those who work on their PC and can't afford BSOD, Beta for gamers and new features enthusiasts, until then I will stick to the studio drivers. Still using 471.22 as it is a hotfix for 471.11 which was a studio driver.

ohh noooeeess! One person on the internet had a problem?

#5930503

Astyanax

2021-07-19 21:21

Jen1:

I will pass this driver as someone has reported BSOD on the geforce forum, although I am already on Windows 11. I really that NVIDIA will start making stable and beta drivers, Stable for those who work on their PC and can't afford BSOD, Beta for gamers and new features enthusiasts, until then I will stick to the studio drivers. Still using 471.22 as it is a hotfix for 471.11 which was a studio driver.

There are thousands of people with broken and misconfigured systems on the geforce forum and not enough qualified folk on there to take the time to teach them how to thoroughly identify the source part. Someone will always report bsods on there. Someone will always report fps drops on there. very few of them are legitimate driver caused issues.

#5930506

Bedouille69

2021-07-19 21:34

ManuelG:

I may have asked this before but do you get this when you connect your GPU directly to the TV and run the audio from the TV speakers?

Hello ManuelG, No, I didn't test because I have an "all clean install" and no hdmi 2.1 cable long enough. My 3080 is connected to https://www.denon.com/en-gb/hdmiadapter (for Denon 4700H) All fine with no audio cuts and HDR movies in 10 bits with 466.27 driver but this driver becames old 🙁 but the driver is OK for F1 2021. Thanks

#5930517

kman

2021-07-19 22:38

Astyanax:

you have to name the games and list settings and you have to provide traces for each of them, you know the drill. https://nvidia.custhelp.com/app/answers/detail/a_id/3507/~/how-to-generating-an-event-trace-log-for-gpuview-to-troubleshoot-performance

Wasn't there a simpler gpu trace programm where you just ran it and logged instead of using the CMD window? It was an official nvidia link too from what I remember and pretty much had the same explanation and you needed the windows performance kit but there was also a gpu trace logger you could download instead of using the CMD window.I think it was you who gave me the link for it at some point.

#5930520

janos666

2021-07-19 22:50

The annoying HDMI 2.1 display flickerings after reboots are finally gone. Thank you!

#5930522

Jen1

2021-07-19 22:53

Astyanax:

There are thousands of people with broken and misconfigured systems on the geforce forum and not enough qualified folk on there to take the time to teach them how to thoroughly identify the source part. Someone will always report bsods on there. Someone will always report fps drops on there. very few of them are legitimate driver caused issues.

When someone claims BSOD in a new driver, or the 7th driver in a row, and rolling back will fix the issue, I would believe that it is the drivers and not the system configuration. It could be specific to his model, but surely not the system configuration. I had my share of BSODs and sudden restarts, updating drivers fixed my issues at some point. So it is NVIDIA drivers and not system configurations. An no, I will not test the so called WHQL drivers from NVIDIA while in fact they are beta releases, as always a hotfix will be releases a few days later. I will stick to the studio drivers, although I doubt that they are tested, as the studio drivers usually released at the same time with the same version as GRD. What I would like to see, that a stable release from the same branch of a previous so called GRD release has been tested and no one has reported BSODs. I don't mind old dated drivers as long they are stable. I don't mind minor bugs, for example nvcpl.dll is not being updated although I have reported it, it is ok, I can replace the old nvcpl.dll myself each driver update. But BSODs will cost me a lot, and some people in here are still making fun of it, it is really weird.

#5930531

Nastya

2021-07-19 23:32

Jen1:

When someone claims BSOD in a new driver, or the 7th driver in a row, and rolling back will fix the issue, I would believe that it is the drivers and not the system configuration. It could be specific to his model, but surely not the system configuration.

As someone who's very cautious as well, just a single or two reports of BSODs isn't something I'm too concerned with. I recently came across a thread for 471.11 where one or two BSOD were reported, and at that point I had been running the driver without problems for weeks. There was only one driver in recent months that I skipped because more than an overwhelming number of users reported BSODs and various other problems; that's when it's worth taking a second look or just skipping entirely.

#5930532

Jen1

2021-07-19 23:53

tty8k:

Ok so you trust some random guy on geforce forums with an unknown setup rather than people here who test more extensively every driver release. BSODS are usually hardware malfunction or incorrect setups. Gaming and app performance is a different story for which we share our findings here in order to identify and report them faster to nvidia. What I can tell you already is that on a 1650ti mobile, gtx 1650ti, gtx 1080, rtx 2070 and rtx 3070 this driver causes no such severe issues. Two of the systems are hooked up directly via HDMI and the other 2 are dual displays on DP. All driver installations are done using DDU (clean) on Windows 10 and 11. Windows HAGS is disabled on all. Bottom line is (and you're not doing me or anyone else any favor but yourself) if you install a driver and encounter issues posting it here it might help you find what is wrong or even fix it.

Nastya:

As someone who's very cautious as well, just a single or two reports of BSODs isn't something I'm too concerned with. I recently came across a thread for 471.11 where one or two BSOD were reported, and at that point I had been running the driver without problems for weeks. There was only one driver in recent months that I skipped because more than an overwhelming number of users reported BSODs and various other problems; that's when it's worth taking a second look or just skipping entirely.

This what you got from what I said. NVIDIA drivers are beta and not well tested drivers, they use us as a laboratory mouse. I don't just trust some random guy, it is just I don't trust NVIDIA, they don't test their drivers, they post Beta release and wait for the feedback. that is why I always read the comments before I test a driver now. And now, I will not test NVIDIA drivers anymore, I used to be the first the test a new driver, not anymore ... I will stick the studio drivers or hotfixes as they have been tested by users ..

#5930535

Mineria

2021-07-20 00:09

Elite Dangerous crashes when I run about on stations, did it two times in a row now, no issue in space, planets nor smaller setlement. Will try to disable MPO again and check if that stops it. Display driver nvlddmkm stopped responding and has successfully recovered. Bit odd that the event claims something is missing? Did a clean install via GFE which actually was quite fast and smooth...

The description for Event ID 14 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

\Device\000000c3
CMDre 00000003 000005c0 60000fff 00000004 00800000

The system cannot find message text for message number 0x%1 in the message file for %2

#5930539

Jen1

2021-07-20 00:20

tty8k:

Well I do agree with you but this is how it works. Nvidia, AMD, Microsoft, Apple, Google all release updates etc and they're all in fact beta until they iron out all the custom issues. Considering the number of different system configurations, settings and software it would take them years to release a stable update, IF. There is also a number or apps/games/OS that run in parallel so they need to somehow sync with those releases too. What it pisses me off sometimes and trust me I do show it even on this forum, is when common or easy to spot issues (by my judgement) are included in stable releases. But if you don't want the trouble and hassle to "test" new driver then it's smart to wait for a few releases or even use an older stable version. Otherwise these kind posts here have no meaning, the very purpose of this thread is to test and share finding on this "beta" or not release 🙂

It is not meaningless, I am righting hopefully @ManuelG will read this and NVIDIA will start making Beta and Stable releases. AMD does have beta releases, Microsoft does too, even Microsoft has beta and release preview before they release the final release. NVIDIA should start making beta releases, lots of gamers will be very delighted to test them in their games. But for me I use my Laptop for work, I need to see a stable release, not a beta release each time ....

#5930541

pseudodeed

2021-07-20 00:25

Hello i have a white secree in windows and on windows logon after install this driver. If i install my old driver 466.77 i dont have any problems and i dont have the white screen problem. Have anyone similar problems? How can i fix this problem or is it a bug? Can anybody help me please? I have an dell notebook and have started the build in self test. That is testing all the hardeare and i dont have any hardware problems. I have with 471.XX many many many windows system errors in the windows log form system. I have this problem with all 471.XX drives. All drives befor and 466.XX are working without errors. My System: Windows 10 64 Bit GPU Nvidia Quadro M4000M (NVIDIA 970M) 32 GB Ram CPU I7-4810MQ

#5930543

Mineria

2021-07-20 00:36

tty8k:

I had something similar in Warcraft, froze and recovered. Turned out to be card boosting to 1950MHz instead of 1935MHz on a lower supplied voltage. Looks like whatever I set in afterburner the card almost always goes +15MHz higher (lower doesn't matter) and if I don't set a voltage stable for that frequency most likely results in a crash/recovery. I just gave it a bit more voltage to avoid the situation, all stable since.

Just tested it with the MPO disabled, no crash and fps was also slightly higher.

#5930544

Mineria

2021-07-20 00:43

pseudodeed:

Hello i have a whit secree in windows and on windows logon after install this driver. If i install my old driver 466.77 i dont have any problems and i dint have a whit screen. Have anyone similar problems? How can i fix this problem or is it a bug? Can anybody help me please? I have an dell notebook and have started the build in self test. That is testing all the hardeare and i dont have any hardware problems. My System: Windows 10 64 Bit GPU Nvidia Quadro M4000M 32 GB Ram CPU I7-4810MQ

Did you download the one posted here on Guru3D? Think this is the one you should have downloaded instead: Graphics Driver - NVIDIA RTX / Quadro Desktop and Notebook Driver Release 470 | NVIDIA