IProSetMonitor creates a lot of WMI Errors

[Hen]

Hello,

on my system the IProSetMonitor (30.0.0.2) creates every 10 seconds an error in WMI-Activity:

SELECT * FROM __InstanceOperationEvent WITHIN 10 WHERE (TargetInstance ISA 'Msvm_ExternalEthernetPort') OR (TargetInstance ISA 'Msvm_VLANEndpoint') OR (TargetInstance ISA 'Msvm_SyntheticEthernetPort') OR (TargetInstance ISA 'Msvm_ComputerSystem') OR (TargetInstance ISA 'Msvm_EthernetSwitchPortVlanSettingData'); UserName = NT-AUTORITÄT\SYSTEM; ClientProcessID = 3912

The used memory of the Winmgmt process is increasing by that by 12 MB per hour until the hole memory is used and the system crashes. I read in anothor thread, that this monitor is nessassary when hyper-v is used. Unfortunatly i use hyper-v on this system. Is there a way to solve this problem?

Regards,

Hen

[Sachinks]

Hello Hen,

Thank you for posting in the Intel Community. We sincerely apologize for the delay in our response. We have received your concern and would like to assure you that assisting you is our top priority.

We understand that you are experiencing issues related to IProSetMonitor (30.0.0.2). Kindly provide us the below details so that we can check this further.

1) The system details that you are using ( motherboard model details ).

2) A screenshot of the error message.

3) Any recent changes/updates you have done.

4) Also, as you have mentioned that the product is ethernet, kindly let us know the nic card/controller you are using.

We appreciate your patience and understanding, and we look forward to hearing from you soon.

Regards,

Sachin KS

Intel Customer Support Technician

[Hen]

Hello Sachin,

thanks for your answer. I think all of your requested informations are inside the SSU.txt from my first post. If you need additional information please let me know. Attached you can find a screenshot of the error message.

The last days I deaktivated Hyper-V and let the system run. The error did not occure.

The only update I've done before was IProSetMonitor. From 26.0.3 to current version, to check if the problem was solved in latest version. But it wasn't.

Regards,

Hen

[Akshaya1]

Hello Hen,

Thank you for sharing the details.

Upon reviewing, I found that the issue is related to the Ethernet controller. I suggest reaching out to the board manufacturer for further assistance in resolving this.

Please let me know if you need any additional information.

Regards,

Akshaya 

Intel Customer Support Technician