Jump to content

Speccy causes WMI errors and high CPU usage


mixvar

Recommended Posts

I discovered that running Speccy on my laptop (Windows 10 Pro 64-bit) causes WMI Provider Host process to constantly use 10-20% CPU (significantly raising temperatures and fan noise). 

I see plenty of errors (one every second) in Event Viewer under Applications and Service Logs => Microsoft => Windows => WMI Activity.

Here is the XML dump of the error (they all look the same):

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-WMI-Activity" Guid="{1418EF04-B0B4-4623-BF7E-D74AB47BBDAA}" />
    <EventID>5858</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x4000000000000000</Keywords>
    <TimeCreated SystemTime="2017-11-01T15:30:37.753924100Z" />
    <EventRecordID>4215</EventRecordID>
    <Correlation />
    <Execution ProcessID="3728" ThreadID="10988" />
    <Channel>Microsoft-Windows-WMI-Activity/Operational</Channel>
    <Computer>DESKTOP-ORHEPT8</Computer>
    <Security UserID="S-1-5-18" />
  </System>
  <UserData>
    <Operation_ClientFailure xmlns="http://manifests.microsoft.com/win/2006/windows/WMI">
      <Id>{00000000-0000-0000-0000-000000000000}</Id>
      <ClientMachine>DESKTOP-ORHEPT8</ClientMachine>
      <User>DESKTOP-ORHEPT8\mixvar</User>
      <ClientProcessId>10480</ClientProcessId>
      <Component>Unknown</Component>
      <Operation>Start IWbemServices::ExecQuery - root\cimv2 : SELECT * FROM Win32_PerfFormattedData_Tcpip_NetworkInterface</Operation>
      <ResultCode>0x80041017</ResultCode>
      <PossibleCause>Unknown</PossibleCause>
    </Operation_ClientFailure>
  </UserData>
</Event>

ClientProcessId points to Speccy.

 

 

Link to comment
Share on other sites

  • 8 months later...
On 11/1/2017 at 10:03, mixvar said:

I discovered that running Speccy on my laptop (Windows 10 Pro 64-bit) causes WMI Provider Host process to constantly use 10-20% CPU (significantly raising temperatures and fan noise). 

I see plenty of errors (one every second) in Event Viewer under Applications and Service Logs => Microsoft => Windows => WMI Activity.

Here is the XML dump of the error (they all look the same):


<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-WMI-Activity" Guid="{1418EF04-B0B4-4623-BF7E-D74AB47BBDAA}" />
    <EventID>5858</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x4000000000000000</Keywords>
    <TimeCreated SystemTime="2017-11-01T15:30:37.753924100Z" />
    <EventRecordID>4215</EventRecordID>
    <Correlation />
    <Execution ProcessID="3728" ThreadID="10988" />
    <Channel>Microsoft-Windows-WMI-Activity/Operational</Channel>
    <Computer>DESKTOP-ORHEPT8</Computer>
    <Security UserID="S-1-5-18" />
  </System>
  <UserData>
    <Operation_ClientFailure xmlns="http://manifests.microsoft.com/win/2006/windows/WMI">
      <Id>{00000000-0000-0000-0000-000000000000}</Id>
      <ClientMachine>DESKTOP-ORHEPT8</ClientMachine>
      <User>DESKTOP-ORHEPT8\mixvar</User>
      <ClientProcessId>10480</ClientProcessId>
      <Component>Unknown</Component>
      <Operation>Start IWbemServices::ExecQuery - root\cimv2 : SELECT * FROM Win32_PerfFormattedData_Tcpip_NetworkInterface</Operation>
      <ResultCode>0x80041017</ResultCode>
      <PossibleCause>Unknown</PossibleCause>
    </Operation_ClientFailure>
  </UserData>
</Event>

ClientProcessId points to Speccy.

 

 

Precisely the same issue. Now using [competition software] instead on my work PC. Definitely not as simple/straightforward as Speccy but locating the relevant temps is easy enough. 

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.