The ThrottleStop Guide

Just realize, when gaming on battery, the battery may not be designed to handle a massive 300w+ draw and may need to throttle the components.

 

I've been at this for days.

I have a clevo with a 980m and 4720HQ.

Just about any time my GPU has any reasonable load, the CPU throttles itself (disables turbo?) and the EDP buttons flare red despite humble temperatures, even if I'm barely using the CPU. I have tried raising amp limit in bios, in throttlestop, I even bought a 330W power supply. And about every other bios and throttlestop setting that seems related to power management. I think Unclewebb somehow solved this issue on his laptop but can't quite figure out how.



Assuming no one has any ideas, does anyone know if there's a GPU equivalent of Dufus' powercut? Seems that throttling is a function of GPU so tricking the computer into believing GPU draw is lower might work.

 

@zamoeba - As always, can you post a screenshot of how you have ThrottleStop setup? Have you tried using the PowerCut feature in ThrottleStop?

There is a duplicate current limit in the CPU that ThrottleStop does not have access to. If this variable is not locked by the bios, you might be able to use RW Everything to change it. The throttling problem you have is different than the throttling problem in my Y510P. My Y510P disables Turbo Boost but it does not set off EDP in Limit Reasons.

 

Here's a screenshot of my current settings.
Why does my CPU wattage increase when I lower VCCIN (no powercut)? Is it because it measures the relative voltage to the regulator so it perceives it as higher?
Powercut seems to correctly obscure my CPU TDP but it doesn't seem to do anything other than that.
If I run furmark, my cpu throttles to about 2.7ghz and voltage ID drops to about 0.8. And furmark is very weak on CPU usage.

If I undervolt my CPU by 50mv or so, then it throttles to 2.9ghz, however that's still a very noticeable throttle and I "feel" like there must be a better way.

I noticed a few other posters' GPU throttling their CPU but have not come across explicitly how they solved it.



You have put a lot of effort and work into this. And continue to help people all this time. Not really thanking you (though there is that) I guess I just admire it.

 

That's not a novelty. http://www.notebookreview.com/news/clevo-d900c-surfaces-the-worlds-fastest-notebook-updated-412/ - and this one probably wasn't the first either. IIRC, there were some laptops with Pentium 4 desktop cpu's before.

 

At least on a Desktop I7-6700k setting the multiplier is working.

 

Thanks for the program!

 

@unclewebb when you do implement the left/right click in next beta, is it also possible to have more than 4 profiles lol. i find 4 isnt enough haha.

 

@unityole - I have to be honest, a few more profiles has been on my mind. I typically only use one profile but I will keep thinking about this idea.

 

IMO I think 2 -3 profiles is best. Too much and it gets messy with diff. settings to manage for each profile. Just my 2 cents. To each his own

I use one for high performance / benchmarking, 1 for gaming, and one for normal use / internet browsing

 

I would second that.. Having too many sometimes isn't the best thing

 

@unclewebb

what I would love to see is a "Duplicate Settings from profile X to profile X"

Example, I set my base overclock or default settings the same as in BIOS when it comes to core/cache ratios, voltages, etc. Rather than having to do this for every profile from scratch, if we can copy a particular profile settings of our choice to another profile of our choice, then the changes needed for that second profile that we need to make would just be a few clicks away like changing the voltage / multipliers and baam, you'e done, rather than having to go to FIVR change the settings all over again for Core, then Cache, then System agent, it's too much work

another thing I would like see automated it creating an auto startup that skips UAC warnings if UAC was enabled and runs automatically at startup. Right now I do this by manually creating a task in Task Scheduler but I know a lot of people don't even know how to do that so if there was a simple checkbox in the program like is the case with EVGA Precision X where it creates a task in Task Scheduler with the correct settings to run at every user logon or whatnot, it would make like much easier

 

This is nothing to do with me, but Throttlestop is an enthusiast tool, and there might be an argument to be had that if you can't work out how to create a task in Task Scheduler then you shouldn't be messing with Throttlestop. (There's even instructions in the first few posts of this thread on how to set up Task Scheduler). Afterall, Throttlestop is overriding some elements of OEM control, thereby placing that responsibility on the users shoulders, those shoulders should arguably be able to follow instructions & be able to create Task Scheduler tasks. Peoples need to be smart!

 

no one talked to you or mentioned you., you are on my ignore list anyway. It was a suggestion to unclewebb. I know how to create tasks, I am suggesting small things which would make the task creation easier to use for others. I have met many people lately that had no idea how to start TS automatically.

My suggestion was to unclewebb, he can take it or leave it.

 

"Ignore List", what's wrong with you! I'm just thinking playing Devil's Advocate. I'm just providing my point of view, which is why I said that it's nothing to do with me - it's just my input (I like commenting on stuff!). Why I'm on your ignore list I don't know (although I'm not disappointed really).

EDIT: yes, I know you know how to create Task Scheduler tasks, that wasn't my point.

 

It sounded like you are dissing my suggestion. I understand that Pro users can do this easily. Would I prefer having an automated button or option to do this automatically? sure why not. I cannot even remember why you are on my ignore list it was probably many negative comments from you in the past. Either way, let's keep things the way they are. Cheers

 

I was just providing a counterpoint to your suggestion, not randomly dissing it. Wasn't anything personal. I can't remember targetting you with negative comments, although if I rack my brain and if I'm not mistaken you used to call yourself Matrix Leader which I found kind of entertaining & I have vague recollections of tin foil hats & Windows 10. Even if my recollections are completely wrong & if I'm mistaken then I'm still just providing a counterpoint to this argument, it's fun to debate.

 

removed from ignore list. Cheers

 

Haha, ok!

 

Ignore lists: (used) by people that think they can't learn or grow anymore.

Yeah; my 2 cents.

Glad to see you're still learning and growing Phoenix!

 

Absolutely, just when you thought you knew every insult in the book someone comes along and teaches you a new one.

@Phoenix you could try maximum performance override MPO using RWEverything to set MCHBAR + 0x5590 (usually memory address 0xFED15990) to 0x14. Don't know if it works on SKL, worked on previous chips.

 

@Robbo99999 and @Phoenix: Indeed, a case can be made either way. You worked it out nicely, thank you for that!

 

I'm a noob so forgive me for asking a silly question... will this potentially ruin your computer permanently if you poke at the wrong address?

 

Well potentially one could disable over voltage protection and set HSW CPU voltage at 3V which should be more than enough to kill the CPU if poking the wrong places with the wrong data I suppose. Not that I've ever tried applying 3V to Haswell CPU's so only speculation on my part. Usually though it's much more likely to result in nothing or a BSOD.


EDIT: revise statement for HSW, yes I have run much older Intel CPU's at over 3V, even over 5V.

 

*eyes suspiciously*

 

The problem was Windows' 10 safety measures. This app requires more privileges than other apps it seems - this is why I had to modify local policies in gpedit.msc to be able to run this app.

Regarding being stuck at 0.78Ghz, this app rarely works in my case.
I have i5 2410m CPU. BIOS has almost no options regarding CPU. SpeedStep cannot be turned off there.

Saying rarely I mean one time it forces CPU to be faster, another time it won't - regarding setting on\off SpeedStep, Clock Modulation or Chipset Clock Modulation.
Multiplier never changes anything, same as changing button to Turn on from Turn off state.
There is no way to force this CPU to change its state via this program with 100% accuracy - more time it just does randomly. Stubborn CPU
It is laptop.

 

It sounds like you are randomly clicking on things without really understanding the problem or how you should set ThrottleStop up to try and solve it. Show me a screenshot of ThrottleStop while 1 Thread of the TS Bench test is running. I need to see what options you have checked off and I need to see your CPU stuck at 0.78 GHz. Make sure you are using the Windows High Performance profile with the Minimum processor state set to 100%.

Turning SpeedStep off is the last thing you should be doing. The Set Multiplier feature will not work correctly when SpeedStep is disabled.

 

TS is still being exited every time I unplug AC. If I try to restart it immediately it doesn't open, but a few seconds later it will launch okay. Any way I can track why it's exiting?

(of course, exit on DC is 0)

 

@Eason: I'm glad you asked I was going to post this anyway. I assume that you are using task scheduler to automatically launch Throttlestop. Check out step 8 below.

Guide to automatically launching Throttlestop in Windows 10

1. Launch Start, search for "Task Scheduler" and run it.


2. Select your "Task Scheduler Library".


3. Create a Task


4. Name the task whatever you would like. Run it only when a user is logged on and Run it with highest privileges.


5. Create a new trigger.


6. The task should run at logon and the trigger should be enabled. I set it to automatically attempt to re-run every hour in case a crash causes it to exit accidentally (this is optional).


7. Set the task to run Throttlestop. You will need to find this on your computer.


8. Make sure you completely disable "Stop if the computer ceases to be idle" and "Stop if the computer switches to AC power". Even though these options may be greyed out, it appears that they still affect the task.

 

Thanks for the post. That was exactly the problem!

 

I couldn't believe it myself. I mean the options are greyed out which implies that they shouldn't affect it yet they do.

It may very well be a bug.

 

Hello everyone.

Is there a tutorial on how to overclock the 4700MQ and how to control voltage (undervolt)? The laptop in question is an Alienware 18.

Thanks in advance.

 

@illuzn - I posted a link to your guide in the first post in this thread, near the top, so hopefully others can find it. Thanks.

@Mobius 1 - For the 4700MQ, all of the important stuff can be found in the FIVR window. Unless you are running a modified bios with the early microcode, overclocking will be limited. My 4700MQ is running microcode 0x1C so the max multiplier when a single core is active is 36. There are a wide range of voltage adjustments available in the FIVR window. Post a screenshot of that if you need some help.

 

With FIVR, core and cache is -80mv. But does not seem to respond to unvervolt when running AIDA64, undervolt work with throttlestop bench.

Multiplier all cores is set at 34, but single thread TS bench doesn't push it above 34. 8 thread bench stays at 34 multipler.

 

What do you mean by this? What kind of response are you looking for?

In the FIVR window if you have set all cores to 34 then you will not have access to the 36 multiplier. An overclocked 4700MQ should look like this so the CPU can use the 36 multiplier when a single core is active.



You should see the multiplier approach 36 during a single thread TS Bench test. You also need to have the core C States enabled (at least C3).

 

Ok, I fix to 36/36/34/34. But with throttlestop single thread, still 34.

-50mv on core and cache.

 

It should be 36, 35, 34, 34.

Are your C States enabled? They need to be enabled so the CPU can access the 36 multiplier. Make sure the Set Multiplier value is set correctly too.

 

C state enabled. Fixed to 36/35/34/34

During aida64 test it's completely stable, but I cannot seem to hit 3.6ghz on throttlestop single thread benchmark

 

If you are having problems, click the Set Multiplier box and set that to 36T. Also post a screenshot of the C State window when your CPU is idle so I can see what C States are being used. Are you using the Windows High Performance power profile? Your low multis are screaming Balanced Profile.

Also set your Non Turbo Ratio to 0 when testing. I am not sure how 38T ended up in the Set Multiplier box. Were you using this version of ThrottleStop with a different CPU? Some people put ThrottleStop on a USB drive and then swap it in and out of various computers without deleting the ThrottleStop.INI file which has all of the specific settings for each CPU.

 

The multiplier box checked and x36, not working with single thread.

Throttlestop I downloaded from your signature, not copy from usb.

 

I've been getting "TDP throttling" on my XPS 9550 sometimes, according to TS, and I"m not sure why. The wattage is shown as 8W or so when it's throttled. Happens during gaming.

 

IA: Package-Level RAPL/PBM PL2/PL3 and GT: Package-level RAPL/PBM PL1 were both triggered. Could this be caused by a PP0 limit incorrectly set in TS?

 

@Mobius 1 - Here is how my 4700MQ looks when it is idle.



When running a single thread of the TS Bench test, ThrottleStop is showing that the CPU is spending about 13.0% of its time in the C0 state. The bench itself contributes about 12.5% to that number and then the CPU needs to spend another 0.5% of its time in the C0 state to complete the various Windows background tasks. The screenshots you have posted so far show that your CPU is not very idle. If you have tasks running in the background keeping cores active, this can prevent your CPU from using the highest multiplier. If that is not the problem then I am not sure what is preventing your CPU from running faster. Are you using the Windows High Performance power profile with the Minimum processor state set to 100%?

@Eason - I have not played around with Skylake throttling reasons yet. What software are you using to report the info you posted. I know Limit Reasons by Dufus does not support Skylake. I might try to add some more info directly to ThrottleStop to help track down Skylake throttling reasons. On my 4th Gen laptop, PP0 Power Limit, Lock and Clamp are not checked and this register is set to zero because it is not being used.

 

Oh yes, I set the minimum processor state to be 0%

Should I use 100%? Maybe unpark cores too?

Trackpad driver also causing a bit of cpu load when used. Idk why.

 

I was also having heavy CPU load issues because of a poorly written ELAN track pad driver. The driver I am using now in Windows 10 is not perfect but it is much better. Before, just resting a finger on the track pad, not moving it at all, was sending CPU usage on the first core straight up. That's a sign of a poorly written driver that is sampling the track pad WAY too much. CPU's run at billions of cycles per second. There is no need to sample the track pad tens or hundreds of millions of times per second. You can have a smooth track pad without doing that. I think some programmer was copying and pasting code since the 1990s. Junk like that kills battery run time. The ThrottleStop C State data is a great tool for tracking down junk software like that.

I would try using the High Performance profile with the Minimum set to 100% like it is supposed to be. This does not cause any problems unless your computer has too much junk running on it. Get rid of the junk.

I have not played with core parking in recent memory.

 

Does minimum 100% increase heat/tdp?

 

Try it and find out. On my laptop it doesn't but that is because my cores are spending almost 99% of their time in C7 where they are running internally at 0 MHz and they are disconnected from the voltage rail getting 0 volts. That is how to improve temps and battery run time. Get rid of the junk software on your computer that is preventing your CPU from spending its idle time in C7.

Windows 10 can be a pig if you let it. Might want to try this tool. It is an easy way to disable some of the more annoying and useless Win10 baggage.

O&O ShutUp10
https://www.oo-software.com/en/shutup10

 

I'll try 100%

 

Hello U nclewebb and thanks again for developing this program. I'm still on 1st gen i7 so I can't comment on the improvements you make I usually update every time it expires. I'm on Win 10, Throttlestop 8.10 (not sure which beta version), and I noticed after I updated my AMD graphics drivers from 16.4.1 to 16.4.2 that the throttlestop gpu temp icon in the taskbar has disappeared! I am running a 7970m btw. I tried playing with the settings and rebuild the iconcache but it won't come back. Probably AMD did something here, but I haven't back rolled to the previous version to confirm.

Another issue is present for a long time from version 7 at least, is sometimes when I disconnect from power cord and go to battery and then back to power cord, throttlestop crashes invisibly, no error box or nothing (I didn't bothered to check the event log though, I should). Note that I have a profile switch from battery to plugged in so that could be a hint. If you need me to do something please tell me. I think it has to do something with WIN10 since I know one more specific program that does the same thing, but that one sometimes does it when hdmi is connected/disconnected but gives an error box crash.

Kind regards

 

@TnF - Are you using the Task Scheduler to start ThrottleStop? If yes, there is an option in there that can cause ThrottleStop to quit when switching to battery power. This was mentioned in the guide that was posted 2 pages ago. In the Task Scheduler entry for ThrottleStop, go to the Conditions tab and make sure, "Stop if the computer switches to battery power" is not checked. ThrottleStop also has a DC Exit Time setting in its Options window. Also make sure that is not checked.

ThrottleStop has always acquired GPU temperature data from the AMD or Nvidia driver. This has worked fine for a long time. It is possible that the method ThrottleStop uses is is not supported in the AMD driver that you are using. I do not presently have access to a computer with a recent AMD GPU so I will probably not be able to come up with a fix for this problem. Thanks for including the driver version number just in case I find some suitable hardware.