Since upgrading to the driver for DLSS4 572.16 nv display container is doing heavy writes to a log file.

[chrcoluk]

Attaching a screenshot, I wonder if anyone has any insight on this.

I did install via nvcleanstall, but I cant remember If I disabled all the usual components I normally do, this didnt happen on the 551.86 drivers.

Probably will downgrade if I dont learn of a solution for it. Restarting the nvidia display container LS service seems to stop it temporarily.

Some more info, I think it doesnt stop, but rather restarting the service resets the file, so as the file grows the writes become heavier and heavier as its overwritten every few seconds with new data.

 

[R0H1T]

Well try "freezing" or suspending the process to see if there's any issues. I usually disable it completely.

 

[DarkDreams]

Have you tried opening the file with a text editor to see what it is logging? I checked and that folder is empty for me, but I'm on an older driver (551.86).

 

[R0H1T]

I'm guessing more telemetry or whatever JHH's up to these days with our data.

 

[chrcoluk]

@R0H1T sadly if the process/service is stopped, I cant open the nvidia control panel, looks like its a required dependency. It does stop the logging when stopped.

@DarkDreams yep, its in binary format.

 

[chrcoluk]

I have more info.

It seems to be triggered by certain things, it doesnt like a idle netflix window in the browser.

Also have tested 551.86 stops the problem, so I am back on that for now.

 

[chrcoluk]

I have a script that can be pinned to start menu as a way to launch the control panel, and will share if anyone is interested, it will start the service, open the control panel, when control panel is closed then end the ls display container service. You will have a command prompt window open whilst the control panel is open, I dont know if its possible to auto hide it as the script has to stay pending as it waits for it to be closed before stopping the service.

 

[DarkDreams]

If you are using a batch file, starting a program by simply putting in the address will make the batch file pause execution until that program is closed. If you want the batch file to continue running (and eventually close) after it launches a program you need to use:

start "" "address"

The first airquotes are the window title and can be left empty.

 

[tugrul_LordOfDrinks]

The nvidia is watching you. Are you AMD? Are you Intel?

 

[chrcoluk]

If you are using a batch file, starting a program by simply putting in the address will make the batch file pause execution until that program is closed. If you want the batch file to continue running (and eventually close) after it launches a program you need to use:

start "" "address"

The first airquotes are the window title and can be left empty.

Sadly if I remember right was some complications, as the command to open the control panel in itself is kind of a launcher, so the script at first was ending before the control panel would load, and it would then fail as the service was already killed.

This is the script I ended up using.

@echo off

sc config NVDisplay.ContainerLocalSystem start=demand
sc start NVDisplay.ContainerLocalSystem >nul
start /B /WAIT powershell.exe -File "%UserProfile%\launch.ps1" "NVIDIA Control Panel"
sc stop NVDisplay.ContainerLocalSystem >nul
sc config NVDisplay.ContainerLocalSystem start= disabled

launch1.ps1, got from github, although I think I edited it for my own purposes somewhat. Note the start-sleep, and wait I added.

param (
    [switch]$list = $false
)

if ($args[0] -ne $null) {
    $appId = get-StartApps -Name $args[0] | Select AppID -ExpandProperty AppID

    if ($appId -eq $null) {
        Write-Host "Application not found"
        exit
    }

    if ($args[1] -eq $null) {
        Start-Process -FilePath "shell:AppsFolder\$appId"
        if ($args[0] -eq "NVIDIA Control Panel") {
            Start-Sleep -Seconds 5
            Wait-Process -Name "nvcplui"
            Write-Output "nvcplui has closed."
        }
    } else {
        Start-Process -FilePath "shell:AppsFolder\$appId" $args[1..$args.Length] | Out-Null
    }

    exit
}

if ($list) {
    get-StartApps | select Name -ExpandProperty Name
    exit
}

Write-Host "Usage: launch.ps1 ApplicationName|[-list]"
Write-Host ""
Write-Host "  -list     List all applications found in shell:appsFolder"
Write-Host "  ApplicationName     Launch the application"
Write-Host ""

Remember its using a modern app format now, and I used shell:appsfolder method so the syntax should work across driver upgrades, otherwise raw path to binary change every driver update.