• Notice regarding image hosts and attachments. See here.

  • Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

**THE NVIDIA DRIVERS THREAD**

I am on 617.42 but its a good reminder to check this type of behaviour especially when storage is through the roof compared to just over a year ago.
 
Rolling back to 621.01 completely sorted it, nvdisplaycontainer doesn't even register in the top 15 high i/o write items in task manager any more and it's basically a background footprint again.

This has restored years of service life to my SSD, and would have not been any wiser otherwise had the issue not been brought up!

I've done the same... ffs :mad:

Nice one @Purgatory for bringing it to our attention
 
Last edited:
This is precisely what a dev at I believe Microsoft was talking about, Due to AI a massive chunk of time is needed to fix issues that would've been caught by humans.

I don't think it's impacting everyone though, On my system over the last 5 hours it's written a total of 6 Megabytes so it has to be something only impacting a certain hardware config or Windows Update install maybe ?
 
Last edited:
  • Like
Reactions: mrk
This isn't the first time they've had issues with nvcontainer nomming through ssds like cookie monster with...well cookies...
 
I think it's not affecting me. Don't know why.
It amplifies based on display usage, so if you are moving around windows, alt tabbing, playing videos etc, stuff that uses DWM and so on, it will call up more polls to the logfile.
 
Hey guys, I'm on 617.14, not doing too much gaming on this second PC (RTX 5060) but use it a lot for work, office based things. Is this driver good to go?
 
After seeing this problem on here, checked my PC, and sure enough, there were around 2.5Gb of data being written to and read in just an hour or so.

Reverted back to 621.01 and all OK.

What is MSA doing, cheaping out on the AI?

What a crock, bring back human Devs.
 
Last edited:
I've been using NVcleanstall for the last few months and only install the basic driver, PhysX and the legacy CP.
Checking with Win resource monitor, there's no activity from NV container at all.
 
It's nvdisplaycontainer and it may not show until a display activity calls for it. You cannot disable or remove it as it is needed for nvapp and nv control panels, well you can but those things will no longer load if you do so you cannot set DLSS presets and so on via them and will need to use NVPI/DLSS Swapper etc instead.
 
Hmmm. I'm on the latest Nvidia drivers and don't have "NVDisplayContainer.exe" listed in resource monitor. I'm on a normal full driver game ready install and have NVidia app installed too. For what it's worth I'm still on Win 11 24H2.

What 'display activity' makes nvdisplaycontainer kick in?

EDIT - ran a game and quit. Now I can see "NVContainer.exe" and sometimes "Nvidia Overlay.exe" showing but they keep coming and going. I don't have that specific "NVDisplayContainer.exe" showing at all though. Is that normal?
 
Last edited:
Just finished playing several games of MW4 and using Resource Monitor saw no disk activity from "NVDisplayContainer at all.

It is listed in Task Manager as (2) processes, so what would trigger read/write activity if I had installed the driver without NVcleanstall?
 
Just finished playing several games of MW4 and using Resource Monitor saw no disk activity from "NVDisplayContainer at all.

It is listed in Task Manager as (2) processes, so what would trigger read/write activity if I had installed the driver without NVcleanstall?

Look at it via resource monitor under disk, see what it looks like.
 
Look at it via resource monitor under disk, see what it looks like.
That's what I mean - I've seen no activity at all from anything Nvidia related in resource monitor - just cod.exe (obv), system, Registry, svchost.exe, MsMpEng.exe plus a couple of others, but nothing from Nvidia.
 
Last edited:
Back
Top Bottom