Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GHelper causing WMI Provider Host to use alot of CPU Usage #3545

Open
2 tasks done
FarukTTA opened this issue Jan 4, 2025 · 1 comment
Open
2 tasks done

GHelper causing WMI Provider Host to use alot of CPU Usage #3545

FarukTTA opened this issue Jan 4, 2025 · 1 comment
Labels
question Further information is requested

Comments

@FarukTTA
Copy link

FarukTTA commented Jan 4, 2025

Rules

  • I made myself familiar with the Readme, FAQ and Troubleshooting.
  • I understand that, if insufficient information or no app logs will be provided, my issue will be closed without an answer.

What's wrong?

Hi, I don't know wether or not this is by design or not (if it is, my apologies), but for the past couple of days, while using my computer, I've noticed high temperatures and an audible fan, I don't think that this a thermal issue since I regularly check in on it. But in Task Manager there is this application called 'WMI Provider Host' using alot of CPU Usage, it's always using atleast 5% of CPU Usage and often times spikes to 10 or even 20%, when I check Event Viewer and go to WMI Activity. It always reports a PID that matches with the ID of GHelper. GHelper is the only application that calls for WMI, there are sometimes other system applications like svchost or OEM software like AsusSoftwareManagerAgent that call for WMI, but out of all of the errors, 70% stem from GHelper. Is there anyway I can fix this issue?

The description shown in the error(s) in WMI Activity reads this:

  1. Id = {00000000-0000-0000-0000-000000000000}; ClientMachine = LAPTOP-KJNTEGNN; User = LAPTOP-KJNTEGNN\PC; ClientProcessId = 18548; Component = Unknown; Operation = Start IWbemServices::ExecQuery - root\WMI : SELECT * FROM BatteryStatus; ResultCode = 0x80041032; PossibleCause = Throttling Idle Tasks, refer to CIMOM regkey: ArbTaskMaxIdle
  2. Id = {00000000-0000-0000-0000-000000000000}; ClientMachine = LAPTOP-KJNTEGNN; User = LAPTOP-KJNTEGNN\PC; ClientProcessId = 18548; Component = Unknown; Operation = Start IWbemServices::ExecQuery - root\WMI : SELECT * FROM BatteryStaticData; ResultCode = 0x80041032; PossibleCause = Throttling Idle Tasks, refer to CIMOM regkey: ArbTaskMaxIdle

When I "close" GHelper this issue still persists. Because when GHelper is closed WMI-Activity will then read these:

  1. Id = {00000000-0000-0000-0000-000000000000}; ClientMachine = LAPTOP-KJNTEGNN; User = LAPTOP-KJNTEGNN\PC; ClientProcessId = 18548; Component = Core; Operation = Start IWbemServices::ExecNotificationQuery - root\wmi : select * from AsusAtkWmiEvent; ResultCode = 0x800706BA; PossibleCause = Could not send status to client
  2. Id = {00000000-0000-0000-0000-000000000000}; ClientMachine = LAPTOP-KJNTEGNN; User = LAPTOP-KJNTEGNN\PC; ClientProcessId = 18548; Component = Unknown; Operation = Start IWbemServices::ExecNotificationQuery - root\wmi : select * from AsusAtkWmiEvent; ResultCode = 0x80041032; PossibleCause = Unknown

When I open it back, it'll give this:

  • Namespace = root\wmi; NotificationQuery = select * from AsusAtkWmiEvent; UserName = LAPTOP-KJNTEGNN\PC; ClientProcessID = 10592, ClientMachine = LAPTOP-KJNTEGNN; PossibleCause = Temporary

The error codes given here always happen periodically and in sequence, it will happen in 2 to 3 second intervals for a minute or two, then stop, and after a while it'll repeat itself. This has been happening for a week now and the error codes given here are always the same. the ID always matches with the one of GHelper and it always uses 'SYSTEM' as the user.

How to reproduce the bug?

  1. Win + R
  2. Type in 'eventvwr.msc'
  3. Applications And Services>Microsoft>Windows>WMI-Activity>Errors
  4. Check for 'Errors' that correspond with the PID of GHelper

Logs

log.txt

Device and Model

ASUS TUF Dash F15 FX516PR-HN002T

Additional information.

I updated GHelper today to version 0.200.0 from its nearest previous version, after that it deleted all logs before December 26, but even after the update this issue is still happening so I kept it and fused the new log file with it.

Armoury Crate

Uninstalled

Asus Services

6

Version

0.200.0

OS

Windows 11 Home 23H2

@seerge
Copy link
Owner

seerge commented Jan 4, 2025

@FarukTTA hello,

It looks like there is some underlying problem with the system, like something is broken with WMI or so

As G-Helper uses WMI to get laptop model name (only on app start), or check current battery charge level (every few seconds, when main window is open). But that is unavoidable, and it can't cause high load to the device. Otherwise it will be a lot of complains from all 200 000 users who use app here :)

I would suggest to follow Troubleshooting steps, mainly Rebuilding WMI repository , Repair corrupted system files, Reinstalling Asus System Control Interface and Hard reset.

Please do all of them and let me know if it helps :)

Thanks.

@seerge seerge added the question Further information is requested label Jan 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants