-
-
Notifications
You must be signed in to change notification settings - Fork 268
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
dGPU cannot turn off while using eco mode. #878
Comments
@123dqwkhjk hello, I see that your BIOS constantly responds with a failure on all attemps to set ECO on
App offers you to restart GPU in device manager, does that help? Does eco work after restarting? Try to do a clean re-install of NVidia drivers, by using DDU or try to do a hardware reset https://github.com/seerge/g-helper#how-do-i-do-a-hardware-reset-on-a-laptop at least. How does Armoury behave in this situation? Does GPU gets disabled via Armoury all the time ? |
After the gpu restart, eco will only work for a short while. |
@123dqwkhjk well, then it's clearly a problem with a system (most probably with BIOS). As command to disable / enable GPU is simple (you can run it by yourself in powershell as admin too) Values: 0 - Enable, 1 - Disable.
So i can't do much here :) On a side not G15 2022 has notoriously bugged bios (based from lots of feedback here). Do you have latest? Mb try to rollback to a bit older version? |
I don't have the older version bios. And most time eco mode will work fine.Thanks for you help. |
@123dqwkhjk i think you can get 311 on ASUS support page But I leave it up to you, good luck :) I'm closing this, as there is nothing app can do to fix that anyway :) |
@seerge Hello, I apologize for the fact that ga503rm 315 version bios is not working sometimes. |
Describe the bug
dGPU cannot turn off while using eco mode.
Clear scenario to Reproduce
Steps to reproduce the behavior:
Expected behavior
dGPU should turn off.
App Logs
Please include and attach log.txt from
%AppData%\GHelper
Desktop (please complete the following information):
log.txt
The text was updated successfully, but these errors were encountered: