-
-
Notifications
You must be signed in to change notification settings - Fork 310
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
Power limits reset randomly #2355
Comments
@skipster1337 hello, try this build Since you have a very old device, it doesn't support power limits in an "asus"-way, same as other models. So app already sets them in a same way as UXTU does. It will re-apply power limits, but it will use existing re-apply timer from Advanced section (so you need to check it there) |
@skipster1337 For fPPT - I don't want to overcomplicate it. If you want some hardcore tuning, you can indeed use UXTU or so Can you check if this build works correctly, I have made few cleanups here |
@skipster1337 default reapply timer is 30 seconds, but you can override that with in config.json
Also keep in mind, when it re-applies it won't write to log :) |
Hmm, there's no such option in the config, should it be added manually? |
@skipster1337 yes, there is no such option by default. Just in case 30 seconds should be more than enough. |
Ok, this should work. I set a 25w limit on the cpu and limited the frequency + undervolted my gpu so this poor old laptop doesn't burn up before I get to repaste it lol |
Rules
What's wrong?
When I set the CPU power limit in the Fans + Power menu (20w for example), it works for a period of time then seems to reset back to default as seen in Afterburner's CPU power usage. The power limit can last from around five minutes to an hour, but it will eventually reset (I believe this is a BIOS related issue, reapplying the "stock" power settings at random, other apps like UXTU circumvent this by setting a reapply timer).
![image](https://private-user-images.githubusercontent.com/91155070/318426358-f3af114c-221b-4811-b518-4ba376f94c35.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkzNjQwNTAsIm5iZiI6MTczOTM2Mzc1MCwicGF0aCI6Ii85MTE1NTA3MC8zMTg0MjYzNTgtZjNhZjExNGMtMjIxYi00ODExLWI1MTgtNGJhMzc2Zjk0YzM1LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMTIlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjEyVDEyMzU1MFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTYxZjg0ZjlmYjFlYzliNGMwZGIxNDQ2YWIyNmFkYTczYWY0ODIxZmQ4Mzg4NDZiZmExYjgxMGZmMTdhODI1NGYmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.yYgppvCNYVqPYIGZZ9yGbAMz9dlUPigFiJwsLYU0UJE)
Also the slow boost limit doesn't do anything because it gets set to the same value as the sustained limit as seen in the log. It's possible to set a separate boost limit through other apps, such as UXTU and Renoir Mobile Tuning, so it should be possible to implement it in G-helper as well.
How to reproduce the bug?
Logs
log.txt
Device and Model
ASUS TUF A15 FA506IU
Additional information.
No response
Armoury Crate
Uninstalled
Asus Services
None
Version
0.164.0
OS
Windows 10 22H2
The text was updated successfully, but these errors were encountered: