Unhandled exception error when trying to make any changes

[durrburger93]

This error started happening since earlier today, and it happens every time I try to make any changes in the inspector. The only thing that (visibly) changed on my PC since yesterday is that Microsoft installed some LG monitor control software bs, which also updated C++ and some other libraries. I uninstalled the software with Revo and also tried uninstalling these most recent updates, then updating everything to the latest with powershell, but it still doesn't help as the inspector isn't working.

I'm not sure if this is what caused the issue, but I don't see what else could be the cause since nothing else changed on the PC. How could I go about fixing this without a clean windows resintall since I just did that a month ago?

Here's the error:

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
nspector.Common.NvapiException: DRS_SaveSettings failed: NVAPI_ERROR
at nspector.Common.DrsSettingsServiceBase.SaveSettings(IntPtr hSession)
at nspector.Common.DrsSettingsService.<>c__DisplayClass16_0.b__0(IntPtr hSession)
at nspector.Common.DrsSettingsServiceBase.<>c__DisplayClass5_0.b__0(IntPtr hSession)
at nspector.Common.DrsSessionScope.DrsSession[T](Func2 action, Boolean forceNonGlobalSession, Boolean preventLoadSettings) at nspector.Common.DrsSettingsServiceBase.DrsSession(Action1 action, Boolean forceNonGlobalSession, Boolean preventLoadSettings)
at nspector.Common.DrsSettingsService.StoreSettingsToProfile(String profileName, List`1 settings)
at nspector.frmDrvSettings.StoreChangesOfProfileToDriver()
at nspector.frmDrvSettings.tsbApplyProfile_Click(Object sender, EventArgs e)
at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
at System.Windows.Forms.ToolStripButton.OnClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ToolStrip.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9290.0 built by: NET481REL1LAST_C
CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll

nvidiaProfileInspector
Assembly Version: 2.4.0.18
Win32 Version: 2.4.0.18
CodeBase: file:///C:/Apps/nvidiaProfileInspector/nvidiaProfileInspector.exe

System
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9282.0 built by: NET481REL1LAST_C
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll

System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9256.0 built by: NET481REL1LAST_B
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll

System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9032.0 built by: NET481REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll

System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9032.0 built by: NET481REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll

System.Configuration
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9032.0 built by: NET481REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll

System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9297.0 built by: NET481REL1LAST_C
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll

Microsoft.GeneratedCode
Assembly Version: 1.0.0.0
Win32 Version: 4.8.9032.0 built by: NET481REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll

Microsoft.GeneratedCode
Assembly Version: 1.0.0.0
Win32 Version: 4.8.9032.0 built by: NET481REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll

Accessibility
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9032.0 built by: NET481REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Accessibility/v4.0_4.0.0.0__b03f5f7f11d50a3a/Accessibility.dll

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

[Zero-X141]

I also encountered the same problem, after uninstalling the graphics card driver using DDU and reinstalling it, I couldn't use it anymore.

[durrburger93]

I also encountered the same problem, after uninstalling the graphics card driver using DDU and reinstalling it, I couldn't use it anymore.

Damn thanks for the heads up. I was about to do that to try and fix this but I'm gonna hold off for now if this only started happening for you after the reinstall.

[dobova86]

I'm getting problems saving changes on DLSS (FG) settings, but inspector this morning was working fine! No driver reinstall at all (572.70) ! What damned story is this ?
PS: Also NVIDIA Control Panel has issue to save parameters with access denied. Nvidia App is making lot of damages!!

[durrburger93]

I don't even have the Nv app installed for the sole purpose of not interfering with Inspector since I'm using it to globally replace both SR and FG. Are you having the same error but only when trying to make changes to the FG model?

[malotur]

I had the same problem with the 572.70 driver, I installed the hotfix 572.75 (both driver and app) and the inspector is working again

[ghyujkilop]

I had the same problem with the 572.70 driver, I installed the hotfix 572.75 (both driver and app) and the inspector is working again

Just tested this, didn't work.

[Dutchman101]

This is because Nvidia App has been making hidden changes to the following file:
NVDisplay.Container.exe

(Possibly also in the background through auto-update, as multiple of the above comments are from users that are adamant they hadn't updated any drivers or apps when it began)

If you stop this process in Task manager, and quickly click "Apply Changes" in Nvidia Profile Inspector, it will work without error. However, it will get fast overwritten again as Nvidia's controlware resumes. Your window to be quick is also just 1 or 2 seconds.

The new file has been signed (built by Nvidia) a few days ago. However, they keep it hidden by not changing the binary's version number ( 1.39.3323.1171 ) which it has used for at least 6 months by now.

MD5: FD7CB60784CCE6923B823E96EDB563AF (Not seen until a few days ago)
Description:
NVIDIA Container

Original Name:
NvContainer.exe

Internal Name:
NvContainer

Date signed:
2025-03-07 23:47:00 UTC

This file is blocking access to write the profile. It seems Nvidia took notice of NvidiaProfileInspector and wants to block it. Why?

[Dutchman101]

cc Maintainer @Orbmu2k @emoose as this needs a solution and affects everyone.
See the above comment by me for issue cause.

[ghyujkilop]

This is because Nvidia App has been making hidden changes to the following file: NVDisplay.Container.exe

(Possibly also in the background through auto-update, as multiple of the above comments are from users that are adamant they hadn't updated any drivers or apps when it began)

If you stop this process in Task manager, and quickly click "Apply Changes" in Nvidia Profile Inspector, it will work without error. However, it will get fast overwritten again as Nvidia's controlware resumes. Your window to be quick is also just 1 or 2 seconds.

The new file has been signed (built by Nvidia) a few days ago. However, they keep it hidden by not changing the binary's version number ( 1.39.3323.1171 ) which it has used for at least 6 months by now.

MD5: FD7CB60784CCE6923B823E96EDB563AF (Not seen until a few days ago) Description: NVIDIA Container

Original Name: NvContainer.exe

Internal Name: NvContainer

Date signed: 2025-03-07 23:47:00 UTC

This file is blocking access to write the profile. It seems Nvidia took notice of NvidiaProfileInspector and wants to block it. Why?

Attempted above solution of closing in task manager, and this didn't work. I even did it when there were no more processes of NVDisplay.Container.exe running. But I'll probably just wait until the maintainer arrives. Thanks for trying man. Great work hunting the changes btw!

[Dutchman101]

@ghyujkilop
Well, maybe i made a wrong analysis - turns out that file is part of nvami (the Nvidia graphics driver itself, not neccesarily app), as it is located in:

C:\Windows\System32\DriverStore\FileRepository\nvami.inf_amd64_[unique hash per driver version]\Display.NvContainer

Idk how it coincides with the people saying they hadn't updated anything, but so it appears suspending the driver's EXE files is the only way for a moentarily apply before that thing reverts it again. In fact, this proves that the Nvidia graphics driver is guarding these values (the profile), which is new, restrictive, anti-user choice, and anti-NvidiaProfileInspector behavior.

I actually installed driver updates, but that's my case. I am currently running Hotfix driver 572.75

Either way, we are close to finding out what exactly happened, and now it's up to the maintainer to make a full assessment.

[mtlvape]

Currently getting same error on 572.75 hotfix

[facboy]

On my machine it was blocking the nvidia app from working too.

[other2w]

This is because Nvidia App has been making hidden changes to the following file: NVDisplay.Container.exe

(Possibly also in the background through auto-update, as multiple of the above comments are from users that are adamant they hadn't updated any drivers or apps when it began)

If you stop this process in Task manager, and quickly click "Apply Changes" in Nvidia Profile Inspector, it will work without error. However, it will get fast overwritten again as Nvidia's controlware resumes. Your window to be quick is also just 1 or 2 seconds.

The new file has been signed (built by Nvidia) a few days ago. However, they keep it hidden by not changing the binary's version number ( 1.39.3323.1171 ) which it has used for at least 6 months by now.

MD5: FD7CB60784CCE6923B823E96EDB563AF (Not seen until a few days ago) Description: NVIDIA Container

Original Name: NvContainer.exe

Internal Name: NvContainer

Date signed: 2025-03-07 23:47:00 UTC

This file is blocking access to write the profile. It seems Nvidia took notice of NvidiaProfileInspector and wants to block it. Why?

I've seen some people (not only here) saying that the NVIDIA app has stopped changing settings. An OTA update may have broken the driver structure, and a clean reinstall seems to fix it. Until now, there's no evidence that it's related to nvidiaProfileInspector, as it's affecting other NVIDIA tools.