Multiple WMI Errors pointing Nvidia Display Driver since 20H2 update!

Hello,

I don't know if anyone can shed some daylight into this. I never had these errors when I was in 1903. But since upgrading to 20H2 these are the multiple WMI Activity errors that trigger at startup and then a few hours later.
The first error is this one here as indicated in my printscreen.

Id = {00000000-0000-0000-0000-000000000000}; ClientMachine = DESKTOP-XXXXXX; User = NT AUTHORITY\SYSTEM; ClientProcessId = 1452; Component = Unknown; Operation = Start IWbemServices::ExecQuery - root\wmi : Select * from NvWmiBrightness; ResultCode = 0x80041032; PossibleCause = Throttling Idle Tasks, refer to CIMOM regkey: ArbTaskMaxIdle



And the second one is this.

Id = {00000000-0000-0000-0000-000000000000}; ClientMachine = DESKTOP-XXXXXX; User = NT AUTHORITY\SYSTEM; ClientProcessId = 2084; Component = Unknown; Operation = Start IWbemServices::ExecQuery - ROOT\CIMV2 : SELECT SystemSKUNumber FROM Win32_ComputerSystem ; ResultCode = 0x80041032; PossibleCause = Unknown

Both of these errors are pointing the Nvidia Display Containers. I have installed latest Nvidia graphics card drivers and removed the first one that was automatically installed with Windows Update. In both cases these errors come up.

Never in 1903 did I witness these errors.

I have a Gigabyte GTX 960 4GB OC Graphics Card. Temps are normal to me. Everything seems fine except for these 2 errors that I believe trigger WMI always at system startup. I haven't tested yet to run Windows with the Nvidia Container disabled.

Do all of you with an Nvidia graphics card with Windows 10 20H2 see these errors?!?! Please answer me this, even if you don't know the solution to this problem!

@steve108 Mine doesn't show as Win32_DiskPartition. It simply logs the error as SystemSKUNumber, that's it.

I made an experiment yesterday to start msconfig as a system start up with Nvidia Display Driver Container disabled! Now I no longer get the WMI Errors associated with the Nvidia Control Panel.

I haven't tested yet uninstalling and reinstalling the graphics card drivers. But if indeed this fixes it then that will be great. If it is a fault specifically with 20H2 then that's disappointing. I don't want to return back to older version of Windows...

selden said:

@BLaZiNgSPEED

Do you really mean 20H2 or do you mean the current release, which is 21H2 ?

If you aren't already running it, you might consider updating to 21H2.

Yes, I mean 20H2 that was the update offered on Windows Update. It upgraded me from 1903 to 20H2 (OS Build 19042.1348).

Windows Update says device is fully up to date with an optional feature upgrade, which I haven't done yet.

Without Nvidia Control Panel no errors show as of last night for 13 hours system up time.

I have no idea why these errors are getting triggered. I will test after uninstalling the drivers. But for now I want to verify for the next couple of days whether further errors are getting triggered before I go on to uninstall and reinstall the GPU drivers.

Last night I reinstalled Windows 10 with an older version of Windows 10 1909 and latest Nvidia drivers. The exact same issue is occurring. At this stage I can't tell if it is latest Nvidia drivers or Windows 1909 also being the culprit.

The problem is when I had 1903 I did not try the latest nvidia drivers. So I can't determine if the latest Nvidia drivers are the cause of these WMI Errors. I don't remember, which old drivers I used. But I had been using them for 2 years.

Now maybe this is related to latest drivers. But the only way I can determine this is if I install an older Windows 10 1903 version and then check whether latest Nvidia drivers cause this.

But I feel like this is too much of a hassle to do just to experiment. If the issue is benign then I may just ignore the errors and use the system as it is.

BLaZiNgSPEED said:

Last night I reinstalled Windows 10 with an older version of Windows 10 1909 and latest Nvidia drivers. The exact same issue is occurring. At this stage I can't tell if it is latest Nvidia drivers or Windows 1909 also being the culprit.

The problem is when I had 1903 I did not try the latest nvidia drivers. So I can't determine if the latest Nvidia drivers are the cause of these WMI Errors. I don't remember, which old drivers I used. But I had been using them for 2 years.

Now maybe this is related to latest drivers. But the only way I can determine this is if I install an older Windows 10 1903 version and then check whether latest Nvidia drivers cause this.

But I feel like this is too much of a hassle to do just to experiment. If the issue is benign then I may just ignore the errors and use the system as it is.

Sorry for late participation , basically I have had your issue about a year ago and it was really annoying partly because it was not only about generating an error entry in the event viewer but also a sudden half second pause in whichever app/game I am using accompanied by that error record , this felt ridiculous .

When all fixes failed I decided to rather downgrade the driver , several trials and errors lead me to realize that driver 425.31 and bellow do not generate such error nor do that mild pause .

I am personally using driver 399.24 basically because several Youtubes illustrated that drivers breed 3xx perform around 10% faster than the 4xx breed for same GPU and they could prove it by benchmarks , so I decided to pick the last of that breed .


Cheers!

nIGHTmAYOR said:

Sorry for late participation , basically I have had your issue about a year ago and it was really annoying partly because it was not only about generating an error entry in the event viewer but also a sudden half second pause in whichever app/game I am using accompanied by that error record , this felt ridiculous .

When all fixes failed I decided to rather downgrade the driver , several trials and errors lead me to realize that driver 425.31 and bellow do not generate such error nor do that mild pause .

I am personally using driver 399.24 basically because several Youtubes illustrated that drivers breed 3xx perform around 10% faster than the 4xx breed for same GPU and they could prove it by benchmarks , so I decided to pick the last of that breed .


Cheers!

Hello, many thanks for your response! So indeed I'm not alone.

I returned back to Windows 10 1903. The Driver version that was auto-installed with Windows update is Nvidia 432.00 and in my case it is no longer triggering these WMI Errors. I can actually now recall this is the exact same Nvidia driver I had with 1903 prior to the fresh re-installation 2 years ago.

I have no idea if updating to the latest drivers under 1903 will trigger the errors again. I have no guts to try this..

But one thing I can tell you is that disabling NVDisplay.Container and just running with the latest drivers doesn't trigger this error at all. I was wondering whether updating to the latest Nvidia drivers without updating the Control Panel will stop the error?

I don't know if it is the control panel or the driver responsible for the errors. Display Driver Uninstaller, I do not think will work as when I updated to 1909 from a clean install I made sure to disable automatic driver update by Windows Update and tried latest drivers and the errors were triggered regardless..

But 1903 with old Nvidia 432 drivers are not causing these errors. I also noticed these errors were triggered when monitor will wake up from sleep, something that never happens under the older drivers unless NVDisplay.Container is disabled at windows startup.