NVIDIA GeForce 496.13 WHQL driver download & Discussion

I have moved to .49 and the GPU is not pulling near 200w in the game nor is it crashing anymore. So they might be linked by hey its sort for me at least.

I agree with you a card is a card though. Should of gone RTX 3080 Laptop which is 165w but i cheaped out and a RTX 3080 is Overkill for 1080p.

 

Hi Manuel

thank you very much for your answer.
Actually , I m not at home but perhaps someone could upload a crashdup when CoD War crashes as more and more people report crash on CoD Cw and Warzone since 476.13.
for information , there is no spike when the game crash and we have no message display driver in windows event log ; it s very strange but I can confirm the problem happens since 476.13 in CoD CW for me.

 

its mainly a game bug, but for some it was provoked by .13 hitting unusual power draw with their chip, try 496.49

 

The 496.13s have been doing well for me. I`ll stick with them for awhile.

 

when a comment is positive about NaughtyVidia responds like this "xD" other than that
“nothing is true, everything is permitted.”

 

This still isn't as cool as you think it is.

 

Profile fix for Doom 3 (Windows store BFG version)

Import with Nvidia Profile Inspector https://github.com/Orbmu2k/nvidiaProfileInspector/releases

https://cdn.discordapp.com/attachments/247515315825672203/903400606906077225/Doom_3_BFG.nip

This adds the PackageFamilyName to the Doom BFG profile, even though the store version is called Doom3.exe and both doom 3 and doom3 bfg have the profile setting update, neither will apply to it without this.

 

It can't be disabled in Nvidia inspector And I'm not the only one with this issue. No config For NvCamera and Nvidia Profile Inspector can't disable it.


https://github.com/Orbmu2k/nvidiaProfileInspector/issues/87

 

it can be disabled by importing a small profile that has it off, the setting itself has been broken for awhile.

 

Now where are we supposed to get this file from? People that have never used DCH drivers have never had to deal with this issue till now.