NVIDIA GeForce 496.13 WHQL driver download & Discussion

This driver causes random flickering(fast TDRs) in 2D, random Dots( Red, Black ) ( also under 2D ) in UWP Apps
And sometimes opened Windows are a Pixel mess
While gaming everything is fine but Desktop

I guess the random Driver Resets is causing this graphical mess on the Desktop
Rolling back to 472.12 and the bug is gone

 

sounds similar but different to what @venturi obseved.

 

@ManuelG Open Issue are growing day by day

GeForce 496.13 GRD Feedback Thread ( | NVIDIA GeForce Forums

 

Division 2 will have a driver workaround
Doom BFG is fixed for next driver
Supreme Commander is an accidental regression, the previous fix for R470 was somehow not included in R495
ROTRR's update was pulled and a fix will be provided by the developer
Youtube remains a flaw in chrome/chromium backend

 

Getting random fps slow downs (fps dropped down to 10 for about 5 seconds) in my games with this driver... rolled back to 471.96

 

Okay set of drivers for my system. Saw tons of reports about these exposing system and/or overclock instabilities, so I'm glad my overclock is still running as stable as before.

 

Many ppl think the earth is flat......

your are giving wrong information on Cod Black Ops Cold War, the game has problems like alot of other games...

your inconsistance on this matter is staggering, 1º you say to all ppl when the issue is showed that its hardware related, bla bla bla, then when its a common issue with every body its game related, the issue HAS been detected the only driver by nvidia that brings this error is 496.13 on this game is that, and this driver is cleary halfbaked not for this issue but for alot of other stuff.

cheers

 

I'm seeing a lot of comments on the Shader Cache size, but I'm still confused about some points.

What exactly is the "Default size" for reference? If this is per game, is there a general average anyone's aware of? If I select 10 Gb is that per game or total? I figure I'll go ahead and set it to 10 Gb perhaps, but without a frame of reference for how this really works or what the default size is I worry I'm making an error changing it off the default.

For context, I've got enough space to spare for probably even 100 Gb's but at some point perhaps that'd be wasteful, unsure.

Thanks!

 

Wait, but does selecting "10 Gig's" lets say mean 10 GBs per game or total/for all games? Thanks,

 

All games.

 

@venturi can you supply nvidia with a msinfo32 text output, as well as any modified settings you've made in chrome/edge (experimental stuff especially)

also do you have global vsync set to the default setting?

its sort of looking like the bug is this
1184361 - Black compositing corruption on win 10 - chromium

are you on 19042 or 19043/4)?

 

Its funny how every driver before this one had 3 different versions of it ,but not this one.Its also funny not anyone else is posting this driver except nvidia.

 

@ManuelG

This driver brought back the texture flickering in World of Warcraft Shadowlands that was fixed in previous drivers

You can see the examples here on the wow forums: https://eu.forums.blizzard.com/en/wow/t/nvidia-flickering-is-back/320521/9

Just filed a bug report on the Nvidia website

 

no it did not, this is not a driver regression, its Blizzard poor QA.

the issue was literally reintroduced by blizzard with 9.1 with no coinciding driver release, those ignorant wowzombies on the forum are clueless.

The Driver issue involved background shader optimizations when first released alongside the 430 driver and persisted till 470 with some workarounds employed in between to more or less effect - the issue was worked around by clearing the directx shaders before every game start.


The new issue is not affected by the presence of shaders, happens from first run and has been occuring in every nvidia driver as of the release of 9.1

Take your reports to Blizzard, the actual responsible party.

 

Well you can say what you want, but nothing was patched in Wow Shadowlands in the last 2 weeks what can cause this. I know 9.1 isnt a brilliant job form a technical point of view. It was solved a few driver versions ago at least for and by nvidia. If it was solved with clearing shaders, good to know but appearently that fix is not in this driver. So yes, 496.13 brings back this issue.

 

CoD CW crash is still not listed in open issue on official forum :/
But clearly it s a driver 496.13 problem cos a rollback to 472.12 fix the problem and no crash at all on this game with previous driver.

 

I am not seeing a spike in crashes for COD CW. If you are able to reproduce this pretty easily, could you capture a full crash dmp file as decribed below and send it to me at driverfeedback@nvidia.com.

https://nvidia.custhelp.com/app/answers/detail/a_id/3335

 

Default is 4GB which is a pool for all games. This means that if a new game takes say 1GB and you've hit the 4GB limit, the oldest shader cache files will get deleted. If you re-run that old game, a new shader cache will need to be re-created leading to slower boot times and possibly lower performance until the shader cache creation is completed. So increasing the amount may help if you run a lot of games on your PC.

 

Was this also the case for pre 496.13 drivers?

 

Previous branch yes. Before that it was 1GB.