Download Nvidia GeForce GameReady 372.90 WHQL driver

Published by

Click here to post a comment for Download Nvidia GeForce GameReady 372.90 WHQL driver on our message forum
#5337205
https://forums.guru3d.com/data/avatars/m/268/268673.jpg
Thanks. Trying it now.
#5337214
https://forums.guru3d.com/data/avatars/m/201/201151.jpg
They have updated VulkanRT-Installer to 1.0.26.0 going to test doom..
#5337219
https://forums.guru3d.com/data/avatars/m/218/218363.jpg
OP - Yes, but look at earlier driver posts. Its tradition to keep em clean, informative and helpful 🙂
#5337220
https://forums.guru3d.com/data/avatars/m/201/201151.jpg
Doom opengl first intro scene max FPS around 160 min 96 Vulkan max 200 min 110. Just read the release notes. no major fixes for me except Rise of the tomb raider crashing after a few hours of gameplay Fixed.
#5337227
https://forums.guru3d.com/data/avatars/m/49/49225.jpg
and the Fallout 3, New Vegas, Skyrim crash is still not fixed, and now listed as an app issue. These games will not get patched, so if you want to play these games looks like we are forced to use 368.81 or older. NVidia originally said the next driver after 372.70 would fix this crash. Disappointed.
#5337229
https://forums.guru3d.com/data/avatars/m/174/174022.jpg
They have updated VulkanRT-Installer to 1.0.26.0 going to test doom..
So... they support a higher Vulkan RT now than AMD? This driver must be twice as fast as the previous one in Doom VK according to what I've read here!
and the Fallout 3, New Vegas, Skyrim crash is still not fixed, and now listed as an app issue. These games will not get patched, so if you want to play these games looks like we are forced to use 368.81 or older. NVidia originally said the next driver after 372.70 would fix this crash. Disappointed.
This crash seems to be OS related as it is triggered by WDDM 2.1 on any GPU, including AMD's and Intel's. This is something which should be patched by MS probably.
#5337232
data/avatar/default/avatar13.webp
doom showing vulkan 0.13 now... not a really last updated vulkan... but is better than before 0.8 haha
#5337234
https://forums.guru3d.com/data/avatars/m/174/174022.jpg
- This version of the driver adds security updates for driver components.
Hmm.
Windows 10 Fixed Issues - [SLI, GeForce GTX TITAN] The Mirror's Edge Catalyst Intensity slider is shown as grayed out after filter type is changed to None from Custom. [200231735] - [Start Wars the Old Republic] There is flickering in the game. [1802553] - [Rise of the Tomb Raider] The game crashes after extended gameplay. [1808730] - [NVIDIA G-Sync] Games lag when played in windowed mode with G-Sync enabled. [1803083] - [NVIDIA G-Sync][World of Warcraft] Screen tearing occurs in the game when in-game V-Sync is enabled. [1808054] - [GeForce GTX 1080][HTC Vive] The GPU is not lighting the headset when connected over the DisplayPort. [1785993] - [NVIDIA Ansel] Ansel to be enabled by default in the driver for white-listed games. [1787964] Windows 8.1/Windows 8/Windows 7 Fixed Issues - [SLI, UEFI] Event Viewer error 14 points to nvlddmkm when the system is rebooted. [1309257] - [NVIDIA Ansel] Ansel to be enabled by default in the driver for white-listed games. [1787964]
doom showing vulkan 0.13 now... not a really last updated vulkan... but is better than before 0.8 haha
Ah, so they've updated the API redistributable, not the driver itself. Makes sense /s
#5337237
https://forums.guru3d.com/data/avatars/m/49/49225.jpg
So... they support a higher Vulkan RT now than AMD? This driver must be twice as fast as the previous one in Doom VK according to what I've read here! This crash seems to be OS related as it is triggered by WDDM 2.1 on any GPU, including AMD's and Intel's. This is something which should be patched by MS probably.
Ok, wonder if they are even aware of the issue, irritating to have to keep older drivers, and new games suffer.
#5337239
data/avatar/default/avatar01.webp
Hmm. Ah, so they've updated the API redistributable, not the driver itself. Makes sense /s
i think the api has a little update... no? i remember before show me like 1.0.8... or i´m crazy and always be 1.0.13?
#5337244
https://forums.guru3d.com/data/avatars/m/231/231931.jpg
372.90 WHQL - r370_00-192
Branch regression? from 372.70 372_69-2
#5337255
data/avatar/default/avatar25.webp
Can anyone cure my ocd and tell me how do you install the drivers? 1-Do you use DDU to remove older driver (even if same branch) and install latest ? 2-Uninstall old from control panel and install latest ? 3-Install on top or update from older to newer one ? thanks
#5337259
https://forums.guru3d.com/data/avatars/m/174/174022.jpg
i think the api has a little update... no? i remember before show me like 1.0.8... or i´m crazy and always be 1.0.13?
It was 1.0.13 since the first R370 release I believe.
Branch regression? from 372.70 372_69-2
_00-X means main branch, _XX-X means some other branch afaik. Doesn't mean that XX is newer than 00.
Can anyone cure my ocd and tell me how do you install the drivers? 1-Do you use DDU to remove older driver (even if same branch) and install latest ? 2-Uninstall old from control panel and install latest ? 3-Install on top or update from older to newer one ? thanks
Will install on top of 372.70 with clean install option, as usual. And reboot after install if this should be mentioned.
#5337260
https://forums.guru3d.com/data/avatars/m/242/242471.jpg
Doom @ Vulkan still loads for ever, earlier 368.xx loaded faster. Will see now if vsync slowdown is fixed 🤓
#5337268
https://forums.guru3d.com/data/avatars/m/63/63215.jpg
Doom loads fine here, 42seconds from click to see 1st options screen (full-loading, no intro skipping). Worked fine with last driver too. As for Vulkan, it's the same situation as last driver, 1.0.13. AMD's latest driver runs Doom Vulkan 1.0.25 I believe. Ambient-occlusion setting still doesn't save.
#5337270
https://forums.guru3d.com/data/avatars/m/242/242471.jpg
And it still has this weird slowdown by close encounters and by explosions.. at least in multiplayer, didnt play singleplayer much lately. It says 60fps and 16.67ms all the time, but image isn't smooth and looks laggy (ingame vsync on).
#5337282
data/avatar/default/avatar30.webp
Does this driver fixes the issues that we have at 2 drivers that was released before? MSI Afterburner bug that shows a wrong memory number when sli enabled Lower memory clock comparing the 369 driver, something about 13mhz lower in both 2 drivers released after 368 version... Thanks
#5337284
https://forums.guru3d.com/data/avatars/m/263/263435.jpg
Do these drivers fix the incorrect vram useage while using gtx 1080 in sli with msi afterbuner or gpu z does this bug still exist ? i am not going to instal these if its still not fixed thats not worth it. So if someone here with a gtx 1080 in sli please let me know if its fixed thank u. Edit: what wsarahan said,if someone can test it out
#5337285
data/avatar/default/avatar27.webp
Do these drivers fix the incorrect vram useage while using gtx 1080 in sli with msi afterbuner or gpu z does this bug still exist ? i am not going to instal these if its still not fixed thats not worth it. So if someone here with a gtx 1080 in sli please let me know if its fixed thank u.
Do you also have the clock bug that is lower after 368 release?

Next Page