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

Very high CPU usage with GUI #2208

Open
mistamal opened this issue Jun 28, 2024 · 5 comments
Open

Very high CPU usage with GUI #2208

mistamal opened this issue Jun 28, 2024 · 5 comments

Comments

@mistamal
Copy link

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
image
image

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

@Marterich
Copy link
Contributor

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
Copy link
Contributor

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
Copy link
Author

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
Copy link
Author

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
Copy link
Contributor

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants