-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Comments
Please run Fyi: the GPU blacklisting system got optimized a few days ago and will become available in the next release. |
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. |
Thanks for looking into this! Here is the output of the above command. Name : Intel(R) UHD Graphics 630 Name : NVIDIA GeForce GTX 1650 |
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. |
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 |
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](https://private-user-images.githubusercontent.com/30079306/344270463-e215964f-1958-4030-8aaa-6aaacd778ed0.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjAxNTE0MjcsIm5iZiI6MTcyMDE1MTEyNywicGF0aCI6Ii8zMDA3OTMwNi8zNDQyNzA0NjMtZTIxNTk2NGYtMTk1OC00MDMwLThhYWEtNmFhYWNkNzc4ZWQwLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA3MDUlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNzA1VDAzNDUyN1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTFhZWQ3ZDkxOGU1MzNlZDFjZGUzOGU1ODM0NDg4Mzc3NTViMjQyMmNiOWMxMmJiZjNkMmQzYTRiMmFmMjY5NGMmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.allLmJ3pfPkkYIBlLOfbGR0lehynlLg0nUFLfVHCcYM)
![image](https://private-user-images.githubusercontent.com/30079306/344270630-639c2014-2fef-412e-9933-de916ff57e63.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjAxNTE0MjcsIm5iZiI6MTcyMDE1MTEyNywicGF0aCI6Ii8zMDA3OTMwNi8zNDQyNzA2MzAtNjM5YzIwMTQtMmZlZi00MTJlLTk5MzMtZGU5MTZmZjU3ZTYzLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA3MDUlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNzA1VDAzNDUyN1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWM5MTU5NWYwZDJjNjU5NWMxMjI1YWFlNzhlOTkwYTIwY2IyZTk0NDgyZjdiZWQ5MzhhMTI0NDAzNzI0NzdkMmMmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.EwPxYEkyUuum789vl6H186q4Q7Q4OkC_XIRDjD_o7ZE)
Additional context
note that the GPU is the intel UHD iGPU, not the Nvidia eGPU.
The text was updated successfully, but these errors were encountered: