Everytime I wake my computer up from sleep, Intel Extreme Tuning Utility turns on Power Limit Throttling

willyrkl123

Prominent
Jan 15, 2018
2
0
510
Hi, I didn't know what category to post this in, but here we go.

As the title states, every time I wake my computer from sleep, Power Limit Throttling in XTU turns itself on, and causes my computer to lag.

It's not a huge problem, as I can apply my profile again and it turns off immediately, I was just curious if there was a reason for it, and if there were any ways I can fix it permanently.

 
Solution
to the OP - what you might do is, after activating all the value measurements in XTU, run a benchmark and take a screen capture while it's running

Print that out, go into your BIOS, and find the selection to restore all defaults, boot bact up, open XTU and compare the values it's showing with the ones on the screenshot capture - if you see any in the screenshot capture that are lower than the default value, that's a pretty good indication those values are what's throttling your system -

willyrkl123

Prominent
Jan 15, 2018
2
0
510


Thank you for the insight, but I usually put my computer to sleep when I'm done with it instead of turning it off because of my startup speeds are pretty slow.

I will definitely keep that in mind though, thank you!
 
actually XTU doesn't turn Power Limit Throttling on, rather it's telling you one of your BIOS settings has changed and the CPU is now being throttled

i use XTU, and for whatever reasons, i can't leave it installed on my i7-4790 computer running win 7 pro x64 w/Asus Z97mobo - it spontaneously would change settings in my BIOS, so after using it i simply un-install it. Shutting it down doesn't correct the issue, it has to be un-installed. On the computer described in my sig below w/Asrock mobo, i've never had that problem

but use it to adjust your settings, run benchmarks etc, then un-install it when done. It doesn't take a minute to re-install
 


just curious - anything you know about it that you can share? It's been a pretty useful tool, and has helped me to OC my 5960X. That issue with it corrupting BIOS settings aside - as long as that aspect is recognized, and it's un-installed once the user is done making adjustments.
 
well, like i said, it hasn't shown any corruption issues on the Asrock mobo. On the Asus board, i'll install it, make whatever changes i want, then un-install it. Plus my 4790 on the asus mobo is a non-k cpu, so there's not a lot of values i can change.

the way i used it was to read the BIOS settings while in windows - i initially used Asrock's Tuning utility to OC, then look at what changes it made using XTU. Asrock's utility though, makes generalized settings, especially in terms of power and current - after noting the changes it made at various OCs, i noticed the pattern asrock's utility was demonstrating, ie what settings it changed for higher clock freq, and that let me make fine tweaks.

Those i'd do from XTU though, and like i said i haven't had any problems of instability leaving it installed on my 5960x cpu, but that's installed on an asrock mobo - i suspect the asrock bios "plays nice" with XTU where the Asus Bios doesn't. For the record, I'm just now learning or "feeling" my way around learning OCing.

One of the other useful aspects, when i first started learning OCing - XTU, when you run a benchmark in it, it will then ask if you want to upload the results to HWBot online. If you do, once there, it let's you compare your benchmark to other users running the same cpu/chipset combo - as you move your cursor over others' results on the graph, and it will show you their score as well as compatibility with your setup. The ones showing 92-100% compatibility, you can download, import into XTU and then select for XTU to install those settings. Sometimes they work, and sometimes not, but with the ones that worked, it gave me an idea of what my mobo and cpu wanted tweaked. That's what i called the "Fred Flintstone" approach to OCing.

One other useful aspect, it was the surest way for me to access how accurate different utilities were in reporting core temps - i assume intel would have the most accurate readings on it's own processor die sensors. CPUID seemed to always mirror the XTU temps, no matter what heat range, while RealTemp seemed to have a small differential with XTU's readings at low or idle temps (2-3 degrees C), but a huge differential at high temps (ie in the 70-79C range, XTU was showing temps sometimes 10 degrees higher). So i dumped RealTemp

But XTU also gives me access to settings that aren't shown in Asrock's BIOS - ie, they only show as "Auto", Default or manual, with only one setting offered under "manual".
 
to the OP - what you might do is, after activating all the value measurements in XTU, run a benchmark and take a screen capture while it's running

Print that out, go into your BIOS, and find the selection to restore all defaults, boot bact up, open XTU and compare the values it's showing with the ones on the screenshot capture - if you see any in the screenshot capture that are lower than the default value, that's a pretty good indication those values are what's throttling your system -
 
Solution
just occurred to me after opening XTU - i hadn't used it for a few weeks

to take the snapshot before you reset all bios settings to default, on the left hand side, go to Advance Tuning > All controls and take a snapshot of that page - then after setting defaults come back to that page and compare your snapshot to it - any values on it that are higher under default settings than what they are when XTU is showing that yellow bar indicating power limit throttle - those values need to be adjusted the next time it shows power limit throttling

and i'm not sure how predictably XTU corrupts your BIOS settings - i never used to put my 4790 rig to sleep, and it wouldn't corrupt my BIOS settings regularly but would every week or 10 days, after being shut off and turned back on every day. I kept thinking my BIOS was unstable and would reflash the latest BIOS from ASUS - then it hit me, this didn't start until i started using XTU. I un-installed and it quit happening. So like i said earlier, i re-install it when i want to adjust any values or just take a look at them, then un-install when i'm thru, before shutting the computer down