GeForce 516.40 WHQL driver download
Click here to post a comment for GeForce 516.40 WHQL driver download on our message forum
Triklopius
I had multiple freezes in starting and changing missions in Warframe dx11. The prozessor turned up like hell what he does every time with new driver, but more like at other new drivers.
Then freeze at the beginning or short moving forwards while prozessor generates new shaders for dx11.
My card is a gtx 1080. So far no issues in other games. Did clean install with DDU. Nothing changed.
Went back to older 512.95. All good and fine.
iNerd
I had to change my core vid and offset settings including pbo2 per core to avoid cpu to go over 70* while game is loading from lobby into the online match in fortnite. but since that dx11 and dx12 with dlss running just fine. but i feel like this driver is not performing line the last one.
I cannot speak about GFE since i dont use it.
Ps: The dino fan report about missing dino def. wins this round 😎:D:D
Rogerbee
This is the first dud driver I've had since I stopped using GFE and used Guru3D instead.
Undying
This driver works fine here just like the previous one.
OnnA
Yup, for me too.
Also no weird thing in OGL... All good
Note:
This one is slightly better than latter, in BF2042 & Forza H5 (Tested with CapFrameX*).
* It's good to have this one, makes comparison easier.
MMXMMX
Yes same here no problems working fine.
3090
BTW just a clean install with Geaforce experience
mbk1969
Beach valley?
[youtube=GGr50iPkmeM]
cricket bones
It would be the same driver.
Darren Hodgson
So hang on... the release notes specifically state that this is driver with support for Jurassic World Evolution 2's ray-tracing features but yet there are dozens of posts on the Steam and GeForce.com forums from people claiming that this driver causes graphical artefacts and flickering in the game. How on earth did that happen? Do NVIDIA not test their drivers prior to release??? I'm almost embarrassed for them.
I loaded the game up this morning - Windows Store version on GamePass only to check whether it had the RT features added but it seems that version doesn't... yet - but never got as far as actually loading into my save game to test it with this new driver.
-Tj-
Is ok for me, no unusual crashes like with that quadro variant yet.
loracle
Good driver for now, not like the 512.95 garbage.
OnnA
Unigine 😉
BuildeR2
I've got to agree with this and those who are not having issues so far. I was on 511.79 for a while, all was fine. Went to 512.95 for a few weeks and had these annoying semi-frequent stutters in DX12 games, along with slightly lower overall performance. Not a ton, but enough that I noticed Forza Horizon 5 would no longer hold framerates like it had since launch with my carefully chosen settings.
Since clean installing these drivers, I've played about 8 hours between Outriders + Forza Horizon 5 + Mechwarrior 5 + Ryujinx Vulkan and everything seems just like it was in 511.79 or slightly better. I specifically played 3 DX12 games to look for those stutters, but things have been very smooth with expected performance thus far.
Jefry_st
WDDM 3.1 changelog :
Windows for Android subsystem GPU acceleration
Shader Model 6.7 support for upcoming cards
Memory allocation control (GCI interloop)
Pinstripe
"Upcoming cards"
So current cards won't support this anymore?
zheega
IIRC; Turing and RDNA1 cards support SM6.5, Ampere and RDNA2 support SM6.6.
Rogerbee
Well, I stopped using GFE years ago when a driver it told me to install completely borked my system. I've been downloading and installing drivers from Guru3D ever since and 516.40 is the one I've got from there that has broken a game.
lukas_1987_dion
Another driver with random Windows event viewer errors, 512.95 are super stable for me, so will stay with them for a while.
dragonlord
It obviously means that they are adding support for this to upcoming cards.
Jefry_st
Also new CUDA version 11.7 in this driver
Changes:
- Support for using the NVIDIA Open GPU Kernel Modules with CUDA 11.7 and the R515 beta driver.
- Lazy loading of compute kernels for possible "significant" device-side memory savings by deferring from loading at the beginning of a program to instead when the compute kernel is first called. The "CUDA_MODULE_LOADING=LAZY" environment variable controls this CUDA module lazy loading behavior.
- NVCC host compiler support for Clang 13.
- Various new features to Nsight Compute, CUPTI, NVPROF / Visual Profiler, and other CUDA Developer Tools.
- All color formats are now supported for Vulkan-CUDA interop support on Android and Tegra's L4T.
- Deprecating 32-bit compilation by NVCC for all GPUs.
- CentOS Linux 8 has also been removed from the CUDA Toolkit and replaced by Rocky Linux 8 support given the upstream CentOS 8 EOL.
