Download: NVIDIA GeForce 461.72 WHQL drivers

Published by

Click here to post a comment for Download: NVIDIA GeForce 461.72 WHQL drivers on our message forum
https://forums.guru3d.com/data/avatars/m/273/273678.jpg
SyntaX:

Rocket League runs rubbish with this driver. Starts with long black screen, Sometimes massive Stutters and short freezes. Back to 461.51 and fine again now.
Nothing to do with this driver, its an issue that has been reported since mid 2020 and hasn't got widespread reproducibility. https://steamcommunity.com/app/252950/discussions/3/2962769352283340171/?ctp=2#c3105766250708668033 Manuel is looking into it, but He can't reproduce it. I can't reproduce it. Most people just don't experience it. The issue seems inherent to systems that are still performing post-startup procedures and drive/file access times high enough to block shader cache creation. you weren't one of the folks that made the shader cache folder read/write(no delete) only are you?
Ancymon:

System is updated, no problems with previous 461.40.
whats the latest KB installed?
https://forums.guru3d.com/data/avatars/m/250/250200.jpg
Astyanax:

whats the latest KB installed?
Its a nonsense question.
https://forums.guru3d.com/data/avatars/m/241/241460.jpg
endbase:

Same motherboard and on bios version 1802 but no support yet
Thank you
https://forums.guru3d.com/data/avatars/m/222/222821.jpg
Astyanax:

Nothing to do with this driver, its an issue that has been reported since mid 2020 and hasn't got widespread reproducibility. https://steamcommunity.com/app/252950/discussions/3/2962769352283340171/?ctp=2#c3105766250708668033 Manuel is looking into it, but He can't reproduce it. I can't reproduce it. Most people just don't experience it. The issue seems inherent to systems that are still performing post-startup procedures and drive/file access times high enough to block shader cache creation. you weren't one of the folks that made the shader cache folder read/write(no delete) only are you?
i take it all back Epic Server are rubbish, was only lucky that after driver reinstall they got better. My first thought was that the old shadercache is not compatible anymore, felt like shader creation on cemu 🙂 Used DDU, now also flicker after windows login disappeared, that was introduced with first 460.xx.
https://forums.guru3d.com/data/avatars/m/273/273678.jpg
Ancymon:

Its a nonsense question.
So you're just here to complain about user error.
https://forums.guru3d.com/data/avatars/m/250/250200.jpg
Astyanax:

So you're just here to complain about user error.
You r talking to yourself.
https://forums.guru3d.com/data/avatars/m/273/273678.jpg
Ancymon:

You r talking to yourself.
The driver works for me in 7 with security updates to atleast november of last year. The only reports i've seen of the driver not starting on w7 are from out of date systems. It's your error if you aren't on top of windows updates. Edit: I have confirmed that the driver requires PCA certificates provided in the October or November 2020 ESU update to function on Windows 7. Edit2: My system is also set for unsigned drivers presently but the certificate chain is reporting everything as ok. I have seen another more verbose reasoning for the problem and have passed it on to ManuelG
Code integrity determined that the image hash of a file is not valid. The file could be corrupt due to unauthorized modification or the invalid hash could indicate a potential disk device error. File Name: \Device\HarddiskVolume3\Windows\System32\drivers\nvlddmkm.sys
I have verified that the nvklddm file matches the contents of the catalog and the signatures are all valid. Nvidia has reproduced the the Code 52 and are investigating.
https://forums.guru3d.com/data/avatars/m/273/273678.jpg
This Windows 7 version of this driver is going to be removed or replaced, whilst all the digital signatures have valid chains for some reason in a normal configuration Windows 7 environment the following occurs. CODE 52: "Windows cannot verify the digital signature for the drivers required for this device." in Device manager Code integrity determined that the image hash of a file is not valid. The file could be corrupt due to unauthorized modification or the invalid hash could indicate a potential disk device error. File Name: \Device\HarddiskVolume1\Windows\System32\drivers\nvlddmkm.sys in Windows Security Audit Log Code Integrity is unable to verify the image integrity of the file \Device\HarddiskVolume1\Windows\System32\drivers\nvlddmkm.sys because the set of per-page image hashes could not be found on the system. in Code Integrity operational Log The driver works with DSEO enabled, so its not corrupt.
data/avatar/default/avatar24.webp
Hitman1985:

Hey guys i have a question, i'm still sitting on GTX 1080 Ti, What is the best driver so far for GTX 1080 Ti?
Probably 442.59 but it's quite old at this point so I wouldn't bother unless you actually have some issues with the newer drivers.
https://forums.guru3d.com/data/avatars/m/263/263739.jpg
SyntaX:

i take it all back Epic Server are rubbish, was only lucky that after driver reinstall they got better. My first thought was that the old shadercache is not compatible anymore, felt like shader creation on cemu 🙂 Used DDU, now also flicker after windows login disappeared, that was introduced with first 460.xx.
Had some freezes in Fortnite epic games it happens every new driver from the last 4 DDU does fix it dunno what is going on with that
https://forums.guru3d.com/data/avatars/m/226/226864.jpg
endbase:

Had some freezes in Fortnite epic games it happens every new driver from the last 4 DDU does fix it dunno what is going on with that
Maybe it has something to do with shader caching.
https://forums.guru3d.com/data/avatars/m/250/250200.jpg
Astyanax:

The driver works for me in 7 with security updates to atleast november of last year. The only reports i've seen of the driver not starting on w7 are from out of date systems. It's your error if you aren't on top of windows updates. Edit: I have confirmed that the driver requires PCA certificates provided in the October or November 2020 ESU update to function on Windows 7. Edit2: My system is also set for unsigned drivers presently but the certificate chain is reporting everything as ok. I have seen another more verbose reasoning for the problem and have passed it on to ManuelG I have verified that the nvklddm file matches the contents of the catalog and the signatures are all valid. Nvidia has reproduced the the Code 52 and are investigating.
Astyanax:

This Windows 7 version of this driver is going to be removed or replaced, whilst all the digital signatures have valid chains for some reason in a normal configuration Windows 7 environment the following occurs. CODE 52: "Windows cannot verify the digital signature for the drivers required for this device." in Device manager Code integrity determined that the image hash of a file is not valid. The file could be corrupt due to unauthorized modification or the invalid hash could indicate a potential disk device error. File Name: \Device\HarddiskVolume1\Windows\System32\drivers\nvlddmkm.sys in Windows Security Audit Log Code Integrity is unable to verify the image integrity of the file \Device\HarddiskVolume1\Windows\System32\drivers\nvlddmkm.sys because the set of per-page image hashes could not be found on the system. in Code Integrity operational Log The driver works with DSEO enabled, so its not corrupt.
Probably the latest vulkan dev beta driver 457.96 for win 7 is affected by the same problem.
data/avatar/default/avatar29.webp
windrunnerxj:

Probably 442.59 but it's quite old at this point so I wouldn't bother unless you actually have some issues with the newer drivers.
442.59 is also one of the last drivers where the Nvidia fps limiter is working properly with some games like Apex and I don't know if there's more games that are effected by such a wierd issue. (frametime wise) Heard one of the 451.XX is also ok but I only tested up to 442.59 and jumped straight to 456+ [youtube=WlUkkmHulkU] Here is the issue.Video starts with the game just using the nvidia fps limiter.The frametime is erratic which shouldn't be and it isn't on driver 442.59.Using the RTSS fps limiter fixes the issue as you can see.Frametime gets controlled to a 7ms and the camera ingame becomes smooth when looking around. This is just 1 quick example for the sake of showing the issue super fast but the issue also doesn't go away if you disable reflex ingame either.The issue it tied to the driver. https://www.nvidia.com/en-us/geforce/forums/game-ready-drivers/13/435761/geforce-46172-game-ready-driver-feedback-thread-re/ few ppl mentioned it too.The nvidia fps limiter from what I can tell can't control the frametimes on Apex even if the fps is stuck at 140fps while RTSS can and this issue started somewhere around the 442.59 drivers.
https://forums.guru3d.com/data/avatars/m/265/265898.jpg
Astyanax:

This Windows 7 version of this driver is going to be removed or replaced, whilst all the digital signatures have valid chains for some reason in a normal configuration Windows 7 environment the following occurs. CODE 52: "Windows cannot verify the digital signature for the drivers required for this device." in Device manager Code integrity determined that the image hash of a file is not valid. The file could be corrupt due to unauthorized modification or the invalid hash could indicate a potential disk device error. File Name: \Device\HarddiskVolume1\Windows\System32\drivers\nvlddmkm.sys in Windows Security Audit Log Code Integrity is unable to verify the image integrity of the file \Device\HarddiskVolume1\Windows\System32\drivers\nvlddmkm.sys because the set of per-page image hashes could not be found on the system. in Code Integrity operational Log The driver works with DSEO enabled, so its not corrupt.
Thanks for the useful info! 461.72 weren’t working properly with my GTX 1660 Ti. My system runs on Windows 7 Ultimate SP1 fully updated and set for unsigned drivers. Latest update was KB4601347 from February 9, 2021 (Monthly Rollup). It has been working as a fully stable piece of software, with ZERO Critical, Error or Warning Events. I’ve never, ever, run into this issue. Now, back to 461.40 and everything’s fine again – will wait for the next proper signed drivers for 7. Take care.
data/avatar/default/avatar04.webp
LOVEandROCKETS:

Thanks for the useful info! 461.72 weren’t working properly with my GTX 1660 Ti. My system runs on Windows 7 Ultimate SP1 fully updated and set for unsigned drivers. Latest update was KB4601347 from February 9, 2021 (Monthly Rollup). It has been working as a fully stable piece of software, with ZERO Critical, Error or Warning Events. I’ve never, ever, run into this issue. Now, back to 461.40 and everything’s fine again – will wait for the next proper signed drivers for 7. Take care.
Same ...