Very high CPU usage with GUI

[mistamal]

Describe the bug Very high GPU usage when using the GUI utility launched from powershell

To Reproduce run iwr -useb https://christitus.com/win | iex on powershell as admin

Expected behavior low GPU usage.

Screenshots

Additional context note that the GPU is the intel UHD iGPU, not the Nvidia eGPU.

[Marterich]

Please run Get-CimInstance Win32_VideoController | fl Name In an administrative Powershell and post the results here so we can check if your GPU needs to be added to the blacklist for gpus that struggle with the matrix theme.

Fyi: the GPU blacklisting system got optimized a few days ago and will become available in the next release.

[MyDrift-user]

What I think happened is WinUtil detected the NGIDIA GPU and therefore used a ressource demanding UI, but that GPU is not the one used, so the integraded Graphics are way overloaded.

If you are using a PC, you should plug in your Monitor to the GPU, that are usually the horizontal video ports. If you plug it in to the Mainboard (vertical ones) it always uses the Intel UHD Graphics.

A way to fix that issue in general is to change the way WinUtil detects the GPU, I will look into it that weekend if noone already did.

[mistamal]

Please run Get-CimInstance Win32_VideoController | fl Name In an administrative Powershell and post the results here so we can check if your GPU needs to be added to the blacklist for gpus that struggle with the matrix theme.

Fyi: the GPU blacklisting system got optimized a few days ago and will become available in the next release.

Thanks for looking into this! Here is the output of the above command.

Name : Intel(R) UHD Graphics 630

Name : NVIDIA GeForce GTX 1650

[mistamal]

What I think happened is WinUtil detected the NGIDIA GPU and therefore used a ressource demanding UI, but that GPU is not the one used, so the integraded Graphics are way overloaded.

If you are using a PC, you should plug in your Monitor to the GPU, that are usually the horizontal video ports. If you plug it in to the Mainboard (vertical ones) it always uses the Intel UHD Graphics.

A way to fix that issue in general is to change the way WinUtil detects the GPU, I will look into it that weekend if noone already did.

Actually I am on a Dell XPS 7590 laptop which has a single HDMI output, so I assume the system determines automatically which GPU to use based on the application.

[Marterich]

Please run Get-CimInstance Win32_VideoController | fl Name In an administrative Powershell and post the results here so we can check if your GPU needs to be added to the blacklist for gpus that struggle with the matrix theme.

Fyi: the GPU blacklisting system got optimized a few days ago and will become available in the next release.

Thanks for looking into this! Here is the output of the above command.

Name : Intel(R) UHD Graphics 630

Name : NVIDIA GeForce GTX 1650

All Right, this problem was already fixed in #2178 and will be resolved for you once the new winutil release is published :) so there's nothing more to do

[og-mrk]

Hello @mistamal Just checking if the problem is fixed in the latest WinUtil release? If it's fixed, then please consider closing this issue as complete, and if not (the issue still present) then I recommend keeping this issue open & If possible, provide any additional info which might help in further debugging of issue. Thanks in advance 😄

[github-actions[bot]]

This issue was marked as stale because it has been inactive for 7 days

[mistamal]

Hello! sorry for the delayed response...

I can confirm that the iGPU is not being taxed abnormally. Thank you for resolving this issue and maintaining this project!

[Marterich]

@mistamal great to hear your issue is resolved. Could you mark the issue as resolved/closed please :)

[og-mrk]

Hello! sorry for the delayed response...

I can confirm that the iGPU is not being taxed abnormally. Thank you for resolving this issue and maintaining this project!

Happy to hear that, and no problem on the late reply. Considering that the issue you're facing is resolved, I'll be closing this Issue Ticket, Thanks for reporting this problem @mistamal 😄

/close