GeForce 546.17 WHQL driver download

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

Click here to post a comment for GeForce 546.17 WHQL driver download on our message forum
data/avatar/default/avatar12.webp
Driver installed fine and running well here.
https://forums.guru3d.com/data/avatars/m/227/227503.jpg
PC freezes when booting up to Lock Screen. For 5-7 seconds not reacting to keypress or mouse movement, then logs in normally.
https://forums.guru3d.com/data/avatars/m/88/88194.jpg
This observation is not limited to this driver but I think something changed not very long ago regarding the general "GSync+VSync+limiter" recommendation. I think either nVidia or Microsoft changed something and GSync now seems to provide tear-free moving image without explicitly setting VSync to ON. I recently had a conversation about this on another forum. The other party objected, so I fired up CS2 to record a 960fps video for him exposing the tear-line I used to see with GSync on but VSync off. It wasn't there in windowed-fullscreen mode. So I fired up old Half-Life 2 in fullscreen mode (but Windows 11's "fullscreen optimizations" and similar "optimize for VRR" settings enabled) and the tear-line still wasn't present (the one that used to be really close to the bottom of the screen, easy to spot with HL2's HUD around that area and by moving parallel to the fairly low-detail wall textures of this game). I wonder which one of the 2 below happened (if not a third one): 1: nVidia realized that ~99% of people are severely misinterpreting the role of enabling VSync on top of GSync and decided to make GSync tear-free regardless of the state of the "VSync" switch. 2: Microsoft's "fullscreen optimizations" (that translates fullscreen to windowed-fullscreen regardless of GSync) paired with the VRR-optimization features (hidden deep inside the advanced Windows graphics settings, next to HAGS) "force" the kind of VSync required for tear-free GSync (effectively preventing tearing with VRR regardless of fullscreen/windowed_fullscreen and/or generic VSync toogles).
https://forums.guru3d.com/data/avatars/m/258/258465.jpg
FatBoyNL:

So I just tried out RTX Super Resolution on my new 4080, but the vid still looks like sh!t. Is it supposed to do that?
Nee toch?! Whoops.. Nah, don't think so. But I've tried it with a streaming service and it looks way better with level 4 of the rtx super resolution thing. I'm gonna try it again with some different levels to see the difference or without.
https://forums.guru3d.com/data/avatars/m/84/84948.jpg
janos666:

This observation is not limited to this driver but I think something changed not very long ago regarding the general "GSync+VSync+limiter" recommendation. I think either nVidia or Microsoft changed something and GSync now seems to provide tear-free moving image without explicitly setting VSync to ON. I recently had a conversation about this on another forum. The other party objected, so I fired up CS2 to record a 960fps video for him exposing the tear-line I used to see with GSync on but VSync off. It wasn't there in windowed-fullscreen mode. So I fired up old Half-Life 2 in fullscreen mode (but Windows 11's "fullscreen optimizations" and similar "optimize for VRR" settings enabled) and the tear-line still wasn't present (the one that used to be really close to the bottom of the screen, easy to spot with HL2's HUD around that area and by moving parallel to the fairly low-detail wall textures of this game). I wonder which one of the 2 below happened (if not a third one): 1: nVidia realized that ~99% of people are severely misinterpreting the role of enabling VSync on top of GSync and decided to make GSync tear-free regardless of the state of the "VSync" switch. 2: Microsoft's "fullscreen optimizations" (that translates fullscreen to windowed-fullscreen regardless of GSync) paired with the VRR-optimization features (hidden deep inside the advanced Windows graphics settings, next to HAGS) "force" the kind of VSync required for tear-free GSync (effectively preventing tearing with VRR regardless of fullscreen/windowed_fullscreen and/or generic VSync toogles).
This is just an unordered wall of text, but I seem to recognize some details 😉
data/avatar/default/avatar11.webp
These drivers cured my [insert something you aren't offended by here], but my 3dmark score went down 200 points so I uninstalled. (edited for those who can't take a joke)
https://forums.guru3d.com/data/avatars/m/259/259956.jpg
Forza Horizon stutters fixed?
data/avatar/default/avatar09.webp
TheDeeGee:

I got 1000 Hz more polling rate installing this driver, keeper!
My mouse feel smooth now on desktop 😀 ..... Ohh wait... It was the new ROG Swift Pro 540Hz PG248QP 😀
https://forums.guru3d.com/data/avatars/m/263/263271.jpg
Gazebo:

PC freezes when booting up to Lock Screen. For 5-7 seconds not reacting to keypress or mouse movement, then logs in normally.
Can confirm as well. Boots fine till login screen, after login loads way longer than I'm used to — screen turns black and remains for around 10 seconds. Then logs in as usual. Installed win11 fresh last week. Hotfix driver went fine, just installed this one over. Either win11 issue or driver issue. Can reproduce upon every login.
https://forums.guru3d.com/data/avatars/m/88/88194.jpg
FatBoyNL:

This is just an unordered wall of text, but I seem to recognize some details 😉
English is not my native language, so please forgive me for some mistakes here and there (we usually order the words and use commas differently in complex sentences). 🙁 Otherwise, I mostly try to order sentences/thoughts in long texts in a way I got used to during my years at the university (although that was a long time ago and I am somewhat more socialized to dumb internet culture style style writing, but not enough to please the TickTok+ONlyFans+amphetamine/opiate addled readers :P).
https://forums.guru3d.com/data/avatars/m/72/72794.jpg
TheDeeGee:

Lot of tweakers on this forum who have modified their Windows installation beyond repair. No doubt there where all the issues come from. And then there are those using the snake oil "clean" driver packages. Apart from the known issues listed (Win 10 transparency recently), i have no problems msyelf either.
I'm a bit confused here as I keep on seeing people refer to the clean drivers as snake oil drivers which makes no sense to me. The aim of clean drivers is to not install stuff that you'll never use and to get rid of telemetry - I don't think anyone expects better performance out of them. I ran clean drivers for, iirc, four years on my GTX 1080 -> GTX 1080 Ti -> RTX 2080 and now I am on them with my RTX 4090 and I have had significantly less problems than the vast majority of people on multiple forums. The only problems I have had were widely acknowledged ones which clearly didn't stem from the clean drivers. What is the snake oil of clean drivers? They provide a debloated driver devoid of telemetry and work perfectly for me so what they claim to do they do which is the opposite of what snake oil means. For those of us that like to run a tight ship the clean drivers are the only way to go as why load up a bunch of stuff that you'll never use? Again, I have to stress that I never expected better performance out of clean drivers and I don't think that was ever claimed.I am not saying that everyone should use clean drivers. I just don't understand the snake oil label being thrown around. I installed the Clean RTX version of this driver (as I always do) and everything seems to be running perfectly. At least the install went without a hitch just installing right over 546.08 and Windows seems to be fine - I will play some games and report back.
https://forums.guru3d.com/data/avatars/m/88/88194.jpg
1: So-called "clean" drivers are not as clean as they claim to be (not all telemetry and/or unused parts are removed, only a few). 2: Removing anything not officially omittable may cause unexpected results (even the removal of "forced" telemetry or effectively unused parts).
https://forums.guru3d.com/data/avatars/m/174/174022.jpg
janos666:

This observation is not limited to this driver but I think something changed not very long ago regarding the general "GSync+VSync+limiter" recommendation. I think either nVidia or Microsoft changed something and GSync now seems to provide tear-free moving image without explicitly setting VSync to ON. I recently had a conversation about this on another forum. The other party objected, so I fired up CS2 to record a 960fps video for him exposing the tear-line I used to see with GSync on but VSync off. It wasn't there in windowed-fullscreen mode. So I fired up old Half-Life 2 in fullscreen mode (but Windows 11's "fullscreen optimizations" and similar "optimize for VRR" settings enabled) and the tear-line still wasn't present (the one that used to be really close to the bottom of the screen, easy to spot with HL2's HUD around that area and by moving parallel to the fairly low-detail wall textures of this game). I wonder which one of the 2 below happened (if not a third one): 1: nVidia realized that ~99% of people are severely misinterpreting the role of enabling VSync on top of GSync and decided to make GSync tear-free regardless of the state of the "VSync" switch. 2: Microsoft's "fullscreen optimizations" (that translates fullscreen to windowed-fullscreen regardless of GSync) paired with the VRR-optimization features (hidden deep inside the advanced Windows graphics settings, next to HAGS) "force" the kind of VSync required for tear-free GSync (effectively preventing tearing with VRR regardless of fullscreen/windowed_fullscreen and/or generic VSync toogles).
Seem to be working just as it did here. But then I never use borderless and honestly can't even remember if tearing was ever a thing in it?
https://forums.guru3d.com/data/avatars/m/279/279272.jpg
janos666:

1: So-called "clean" drivers are not as clean as they claim to be (not all telemetry and/or unused parts are removed, only a few). 2: Removing anything not officially omittable may cause unexpected results (even the removal of "forced" telemetry or effectively unused parts).
Eh, I personally would actively want them to collect telemetry at this point, considering how unstable all software is at this point. I actually do enjoy that there are some driver teams that constantly got spammed by VRAM related crashes in Cyberpunk I've gotten over the recent months. 🙂
https://forums.guru3d.com/data/avatars/m/65/65484.jpg
FatBoyNL:

So I just tried out RTX Super Resolution on my new 4080, but the vid still looks like sh!t. Is it supposed to do that?
No it's not. I'm using it on my 1080p Plasma with Youtube TV and it look fantastic for me especially where certain channel are only available at 720p.
https://forums.guru3d.com/data/avatars/m/72/72794.jpg
janos666:

1: So-called "clean" drivers are not as clean as they claim to be (not all telemetry and/or unused parts are removed, only a few). 2: Removing anything not officially omittable may cause unexpected results (even the removal of "forced" telemetry or effectively unused parts).
The fact remains that clean drivers remove all the bloat which the vast majority of people will never use and most of the telemetry. I have been using them for years without a single issue attributed to the clean driver package because what is removed is simply not used which is why it is termed bloat. My experience, and the experience of a lot of others, has shown that you can remove all this bloat without incident. You don't have to use them but saying they are snake oil is not true because they do what they claim to do - debloat and remove most telemetry. There wouldn't be an entire community dedicated to apps that debloat and a massive thread dedicated to clean drivers if the the removal of bloat and telemetry caused issues.
oneoulker:

Eh, I personally would actively want them to collect telemetry at this point, considering how unstable all software is at this point. I actually do enjoy that there are some driver teams that constantly got spammed by VRAM related crashes in Cyberpunk I've gotten over the recent months. 🙂
This is a valid argument. I have thought about it a lot but I have come to the conclusion that millions of others have telemetry so not having it on my machine will likely not change anything. Although, I may be wrong on that. I wish that nVidia had the same feature as AMD with the bug report tool built into the control panel so any issue could be easily and accurately reported to them. I found AMD was much quicker to fix issues than nVidia because of this. I really miss the impeccable driver experience that I had with my 6800 XT.
https://forums.guru3d.com/data/avatars/m/88/88194.jpg
Snake oils are usually decent-quality oils that won't break your car. It's just that it won't be able to reach 2x speed and time-travel when you hit that 2x speed.
https://forums.guru3d.com/data/avatars/m/269/269781.jpg
jarablue:

What is funny is that I have had 0 issues with nv drivers since forever. But coming to guru3d forums, you would think that they are unusable completely. I wonder if the people who complain about the drivers are using speak and spell computers from the 80s. Crazy that I have yet to see 1 issue pop up in any games. In like 20 years. Ah well. Speak and spell computers need love too.
Some drivers were really shit !!
data/avatar/default/avatar15.webp
Hapatingjaky:

https://imgur.com/Ev9nS3Q Worls Great, no issues on an old 1070 and a 3080ti. Will hold out for everyone complaining about DPC Latency. Tested for 2 hours on the 1070. https://i.imgur.com/Ev9nS3Q.png
These latency issues got out of control with the arrival of the 30xx series and continued with the 40xx series. They are not present with as much intensity with the previous series. It would therefore be more judicious to test 2 hours with your 3080ti than with your 1070 for optimal results and less confusion.
https://forums.guru3d.com/data/avatars/m/258/258465.jpg
stryfe2010:

No it's not. I'm using it on my 1080p Plasma with Youtube TV and it look fantastic for me especially where certain channel are only available at 720p.
Idk what it says at your settings, but for me it's only working/activated while using 1440p screen or higher res: https://i.imgur.com/foPp6JI.png