NVIDIA GeForce Version 430.39 WHQL - Download and Discussion

Seems nvdisplay.container.exe is trying to send data out... my firewall blocked it.

Outbound rule to block (nvdisplay.container.exe)
C:\program files\nvidia corporation\display.nvcontainer\nvdisplay.container.exe

 

Yes I saw that too..

It calls to geforce experience activation something. And I don't have it installed at all..

 

Hello!

I was wondering if those of you who report stuttering, frametime spikes or a avg-fps decrease after updating drivers actually take into account that most games usually behave a bit worse for the first run after you switch because of the shader cache is also rebuilt? I think this occurs with each and every driver change, but correct me if I'm wrong - also especially if using DDU.

As you play the game the shaders will be compiled and cached and the next time you will run it smoothness and performance should be re-gained somewhat.

So, is this usually known and taken into account in the reports that we can read on these forums - or are users just dismissing new drivers because of the above mentioned phenomenon?

 

No love for DX 12 mgpu yet in BF V

The only game that works with DX 12 mgpu with RTX is the new shadow of the Tombraider.

Getting great performance with 2x2080ti nvlink in 3440x1440 ultra with RTX. No need for using DLSS

I want Mgpu to work in BF V now!

 

Well

Down the road for sure, by then I should have my second 1080Ti.

 

I will just say that BFV runs completely fluid after this driver update. Might even consider throwing the second 2080 Ti back in.... Pulled it last week because it just wouldn't work with almost all games...

 

Same issue here what other users are facing - flickering in time spy & some Games (witcher 3). Fps drops in anno 1800 too. I'd suggest reverting or not updating to this one yet.

 

Yeah... like... does it even work in BF1 yet? That game's older than Bf5 and yet doesn't support it... I wouldn't count on mGPU anytime soon friends. Generally.

 

SLI/CF are dead. Anyone who didn't notice that yet during the last five or so years didn't pay any attention.

 

Yes, the more we move to native Dx12 the more that will probably be dropped except for maybe a few engines.
Dev's don't have time to do that for such a small user base.

 

Here's hoping that the rise of RT will reverse this trend. RT is natively parallel.

 

It's not dead for me.

For you, I don't care

 

sGPU = Plug and Play
mGPU/SLI/CF = Plug and Pray

 

Not sure what is going on here but it's 100% reproducible on 1903 (18362.53)



After cold booting (if that term is even applicable to Win 10) NVIDIA Container is using ~15% of CPU as soon as system finishes loading. Restarting fixes this issue but only temporarily - it appears again if you shutdown the system.
Only Driver and PhysX installed with NVSlimmer, DDU'd before installation.

EDIT:
Killing the process seems to restart it and work as intended

 

Respectfully, again, that is just your opinion.

 

Respectfully, not really.

 

Same as mine, which looks normal to me and same behavior as before, so it seems renaming the DLL to something else is a good way to stop the telemetry. Just deleting the folder and you won't get the Control Panel and said log files will constantly spam/refresh with error messages like "could not initiate RSS blah blah" or some such message.

Yes that's the new telemetry they added, "C:\Program Files\NVIDIA Corporation\DisplayDriverRAS" it then creates a Telemetry folder in your "C:\ProgramData\NVIDIA Corporation" folder and I would assume it's trying to send those things to NVIDIA. It'll happen exactly at 2 hours from when you turned your computer on, so if you booted at lets say 1:00pm, you firewall will "alert" you at 3:00pm about this connection.

 

I have fast boot completely disabled on my system and I have never seen this behavior, same OS version 18362.53.

 

I'll try disabling it and report back

EDIT:
Yep that "fixed" it. Still, I kinda got used to fast startup so I hope nvidia looks into this bug.