Discussion in 'Videocards - NVIDIA GeForce Drivers Section' started by kx11, May 27, 2020.
f1 2019 crashing now, never happened before, back to 445.98 and working fine again
Quake Champions CTD and lockups :/
i just played for a hour, (deathmatch and instagib) with no lockups with latest drivers and recent windows 10 2004 update
Curious. Engineers were also those that coded a totally different intended and custom behaviour during years of drivers iterations. Imo, it seems really inefficient to purge the NV_Cache folder (all content? never seen that) each time an app is launched.
@ManuelG please, could you clarify or confirm us if purging the NV_Cache folder on each application launch is now the intended behaviour? If so, could you share why that wasn't the intended behaviour in each and every version I used and tested since the summer 2016 days and up to version 442.59, included? Purging the NV_Cache folder every time an app or game is launched seems an inneficient behaviour.
excelent, minecraft rtx is not crashing with these, i had problems with the 450.xx insider drivers but these are fine, no problems for me.
What monitor are you using?
Hey Manual, are you guys aware of the Windows 10 start menu being slow/laggy upon launch?
For those with idle clock speed issues, can you do one of the following please?
1. Fill out the driver feedback form so I have a system config to ask QA to test with and see if we can reproduce the issue
2. List the following info in this post:
GPU make and mode:
GPU VBIOS version (you can look this up in the NVIDIA Control Panel)
Windows 10 version (You can view the following FAQ for info on how to look up the version http://nvidia.custhelp.com/app/answers/detail/a_id/3831/ )
Monitor(s) make and model and how each of them are attached (DP/HDMI/etc.)
Did you have hardware scheduling enabled in the Windows 10 display settings before installing driver 446.14?
Need more info
It is a bit complicated. It is not designed to purge the shader cache folder for every game launch but it is possible some games may exceed one of the two shader cache maximum size limit thus triggering the cleanup. We do have some changes planned for a future driver branch including increasing the maximum size for each of the shader caches.
@ManuelG just read this in the 'Fixed Issues' section of the 446.14 release notes:
So, I think my question is already answered.
Good to know, increasing such max size limit is a good idea. Thanks for your explanation. The quoted fix description and your answer clarify all the situation. Regards!
I haven't see this. Is this only with driver 446.14?
Maybe, I also updated to the Windows 10 May update, so I'm not sure if that also has something to do with it.
I'm seeing this with 446.14 on Windows 10 2004 as well. I didn't have such issues in 1909 with these drivers yesterday.
Update: I used DDU and installed 450.99 drivers in 2004 instead and the lag in the start menu is gone for me.
Just curious. How long did you check your GPU monitoring utility? I noticed at log in of Windows 10 2004, the GPU clock speed was stuck at 1350Mhz for about a minute on my PC but then returned to its normal idle clock speed.
No problem with clock speeds on my end, down clocks when it's idling. Using a i7 3770k and RTX 2070 Super.
Played some Valorant and Overwatch, and these feel pretty good so far.
Nvidia FE 2080ti (EK waterblock)
GPU VBIOS : 90.02.0B.00.A9 (KFA2 RTX 2080 Ti 11 GB BIOS to get 380W limit)
Windows10 Pro x64 2004 (OS Build 19631.1) Insider Fast ring
LG38gl950g DP cabel (only uses 1 monitor)
Thanks again. Are other users who are seeing this issue modding their card with a different VBIOS? Just trying to give our QA team the best information to reproduce this.