The ThrottleStop Guide

I have never heard of a TouchPad getting that hot which brings me back to your software. Now I am not knocking your software or your team but to me it's software related. Have you tested it on another Toughpad ?

 

As usual, excellent results. I am very pleased with how it works with my 2920XM, 3920XM, 4930MX and 4930K. Great job, and nothing negative to report. I feel worthless having no input, but it's hard to improve on excellence.

Wish it could adjust voltage on my X79 laptop, but can't have everything.

Thank you for the update, @unclewebb

 

I wonder if the underlying problem lies with some inefficient programming such as a continuous loop that keeps the CPU busy.

Prevention of throttling when a system is overheating could well result in damaged hardware.

John

 

this my test on ts bench 100% on all core, 2.5 Volt VCC in, 64.5 mv undervolt on Core

 

Hi,
We have tested it on its "big brother" the G1 which has a 10" screen and more importantly has a fan. It works fine.
I should also say that when the M1's clock speed is at 2100 Mhz, the software takes up 16-23% CPU so it's not that the CPU is very loaded.

 

Hey,

It seems that on the "Alarms" option, the GPU C is "more important" than DTS. Can this be changed, preferably through a drop-down menu?

Although I'd agree in several scenarios, it's conflicting with my particular "hack". The 4700HQ on my rather slim Lenovo Y50 runs fine at 3.1GHz with all cores alone, hovering around 85~88 But, during gameplay, the shared heatsink with the GPU makes it skyrocket to 97~100, which causes throttling and, on extreme scenarios, sudden shutdown.

One way I found to counter this is to simply disable the "[force] Set Multiplier" when the GPU comes on, as by default, this laptop locks to 24x when a fullscreen game is going on, and the stock 2.4GHz is fine for every game I play. So I've setup a profile "Game", that is selected when the GTX is around 40 C. As it only turns on -- and TS gets a reading of it -- during games, this setup is pretty fine. Hooray!

However, when games aren't fullscreen (or when it's something that's taxing the GPU and CPU, but it isn't a game), the turbo doesn't turn off, and it runs at 2.8GHz~3.1GHz until it "dies". So, logically, I've set another "Alarm" that sets it to the Battery profile when it "reaches a certain temperature", which locks it to 1.4GHz, and drastically lowers the voltages. Sounds fine.
But it seems that the GPU Alarm overrides the DTS Alarm, and it keeps burning itself down happily.

Could you please make these alarms interchangeable or selectable which one is more important? Also, if I could make another suggestion, could there be an option to hold a certain alarm profile a little longer? I've noticed that when it hits the DTS Alarm, it keeps going back and forth, as when it falls to 1.4GHz, the temperature drops sharply, it goes outside the DTS Alarm threshold and it just goes back to the Normal profile, which rises the temperature to just before what it was. Then it hits the DTS Alarm threshold and it does that in a loop -- until the GPU C Alarm is met.



P.S.: A workaround would be to check "Disable Turbo" on the "Game" profile, as that's expected on the "Game" profile. But it's still good to have a little CPU horsepower during encoding operations, which uses the GPU without being a fullscreen application, and for the DTS Alarm, which could be used as an generic temp throttle. Rather good for times when I leave it over my bed, and it can't breathe properly

 

Lighten up grandpa, I was just kidding. I've read enough of your posts to see that you treat people with respect. About the links to B2 though, there's another place that UncleWebb frequents that had a working link. Fist page of Google results for me.

Thanks for the release, this application allows me to get the highest geekbench scores posted for my machine
~Aeny

 

Hi, @unclewebb. I have been using your new beta of Throttlestop with a Broadwell i3 5005U. I half expected throttling in the mini PC (MSI Cubi) that houses that CPU. Fortunately, the CPU has not throttled at all.

While toying with the settings, I was surprised to find most of the voltage options under FIVR are functional. I made good use of those options with my 4790K, but I did not expect them to work with the Broadwell, since the voltage regulator was moved outside the CPU. I was able to significantly reduce the core voltage and lower the peak CPU temperature. CPU-Z confirms that the tweaks are indeed working.

While surprised at this bonus functionality, I salute you. Thanks again for Throttlestop!

 

This is incorrect. Broadwell keeps FIVR, it is Skylake where it has been moved off the CPU.

 

I won't use the VCCIN feature, but I'm very happy to have beta 3 at last! It's nice that the "i" processors have many controls exposed, just wished Intel had FIVR available to Atom chips like the Z3735G.

 

Holy cow dude, 0.8w? how?!




on another topic: Does your C states (between BCLK and DTS, on the right lower corner) shows C7s only on Profile 1?

 

Because he's using lower C-states.

 

The power consumption data that Intel CPUs calculate is not 100% accurate, especially when a CPU is lightly loaded or idle. The only purpose of this data is to control the Intel Turbo Boost feature. We have already seen that playing around with VCCIN screws up the accuracy of the power consumption data. I have C7 and Package C6 enabled on my 4700MQ and it usually reports about 2.0 W. His CPU might be using Package C7.

Maybe a reading of 0.8 W indicates a good core or maybe it is completely meaningless data. Not sure.

Has anyone played with this new feature yet?



Setting and locking the Non Turbo Ratio to 1 disables the Set Multiplier register. Lenovo used the Set Multiplier register to throttle the Y510P down to 2400 MHz when gaming. That new ThrottleStop setting eliminates that problem and if you check off the lock option, you can exit ThrottleStop with no worries that the multi is going to drop down to 24 anymore. This is a more efficient way to handle this throttling problem than checking off Set Multiplier. Full Turbo Boost for the win!!!

I think a few different Lenovo laptops use this throttling method.

@Fujikido - ThrottleStop should support the Atom Z3735G so you can reduce the voltage. Not as many features as FIVR control but better than nothing.

 

Hello, Im using ThrottleStop 8 beta 3 now. The problem is that I cant select the options "Show CPU" and "Show GPU".

 

Try following the directions in the included ReadMe file.

ThrottleStop might still have a bug with not updating the C States button to the correct value. C States are locked on my CPU so I have not been able to properly test this yet.

 

Mine still throttles during games, to 24x. I can't set the Non-Turbo Ratio to anything other than 24. It also always says Locked.



I can't see my laptop running at anything lower than 4W, no matter what I do. Battery dies within two hours of web browsing at 50% brighness. The processor rarely goes below 45c, although it sits at 800~1000MHz most of the time.

My package C states seems to be C1 for all profiles, but the 1st profile, that says C7s. How do I know if I properly set it up?

 

Here's how to read ThrottleStop. Non Turbo Ratio - 24 means the Non Turbo Ratio is currently set to 24. Your CPU is reporting that this register is already Locked. I assume that the bios did that. If this register is Locked by the bios, you cannot use ThrottleStop to change this register. That is why your CPU is still throttling down to 24X.

As for the C States, open up the C States window and have a look in there to see what C States your CPU is using. If the bios has disabled some of the deeper C States, your CPU will consume more power and battery run time will decrease significantly.

 

Any profile that isn't the #1

Profile #1

I don't know if I have C states locked or something. The friend above has the same laptop as I do (Lenovo Y50-70), but with a slightly different processor, and achieves 0.8w.


(edited to avoid polluting the thread with too many images)


----------------------

It seems that my laptop got either something wrong with it, or something's disabled.
I've checked Fujikido's screenshot again and noticed this:

while mine's always zeroed. I'll try fresh installing ThrottleStop (I've been copying the settings over a couple of computers) and restarting the laptop to see if it helps

 

I wonder if this would help those throttling Alienwares?

 

Thank you unclewebb, I have solved the problem with this advice.

 

In the C State window, the Package C State Limit button is grayed out. That means that this feature is locked by the bios and cannot be changed. It looks like this ThrottleStop bug has not been fixed yet. Your screenshots will help me track this bug down and hopefully fix it. Can you run the Dump tool by Dufus so I can see what is in your C State register.

https://www.sendspace.com/file/iumw0k

After running Dump.exe, copy and paste the info to www.pastebin.com and post a link here.

Your CPU seems to have disabled the deeper Package C States. My 4700MQ spends about 80% of the time in Package C6 with Google Chrome open and about 85% with nothing open. That helps to reduce power consumption.

http://i.imgur.com/fyZYlsp.png

 

Any reason why would it not change the C state? The other guy has a Lenovo Y50-70 with a 4720HQ (Mine's a 4700HQ -- pretty much the same, but with bumped clocks, I guess?) and it seems that his model is able to reach deeper C states.

After "reinstalling" (I've only renamed the old ThrottleStop folder and pasted the new one where it was previously), it seems that ThrottleStop now reports C7s for all profiles, although they're still grayed out

Here's the pastebin: Is that correct?
http://pastebin.com/0Vx87RwW

I've ran the dump executable while running the "clean" ThrottleStop version

 

Only one more thing.



Why does the temperature that is showed in "Temp" (46 C) is not the average of the temperatures of the 8 threads? Indeed is 2 degrees above the highest Temp of the threads (44 C).

 

Code:

0xE2 00000000:1E008405

The 8 in that register shows that the Package C State Configuration Control register is locked by the bios. The 5 at the end shows that C7s is the maximum Package C State. This register is set to the exact same value that my CPU is set to. There is another register that I know of that can also be used to limit the C States but at the moment, ThrottleStop does not access this second register. I will compare your Dump.txt file to one from my CPU to see what I can figure out.

When you switch to battery power, have a look to see if any of the deeper Package C States are enabled then. Sometimes this automatically changes when you switch from AC to battery power. If it does change, run the Dump program again and take another snapshot of your registers.

 

Good question. The temperature reported in the Temp box is called the Package temperature. There are the individual core temperature sensors but there are also other temperature sensors on Intel CPUs. I am not 100% sure where the other sensors are located but I think there is one on the Intel GPU. The package temperature compares all of these sensors and reports the highest value it finds. Sometimes one of the cores might be the hottest point on the CPU package and other times it might be the Intel GPU or somewhere else on the CPU package.

 

I was on battery mode when I sent you the first dump txt
I'll have a look on my BIOS to see if I can turn something on there. Can this be a processor issue, a damage of some sort? My processor has a slight dent on the die ( http://i.imgur.com/BmWqeYu.jpg), but idk if that affects the power states somehow

---------------

The only thing that I could change there that was remotely related to the processor was Virtualization (which I use a lot). Disabled it and nothing has changed, still no lower C states.

 

It is highly unlikely that a dent on the CPU die would cause C State issues. I also don't think there will be any option in the bios that will let you control your C States. There are many registers in the CPU that the bios sets when you boot up but there won't be options in the bios to control any of them. If I can find a register that is not locked, maybe I can try changing that register to see if the Package C States changes.

 

Thank god. This CPU dent has been haunting me since I discovered it (it's a manufacturer defect), and I've been worried with it ever since. But it seems to not affect anything at all, luckily.

Yeah, there isn't anythgin much useful on the BIOS... but I wonder why mine can't reach low C states? I remember I had set something on Windows power profiles to allow parking cores and setting up some stuff. Do you think this is directly related?

http://imgur.com/a/gFlHB

Anyway, I'll be looking for a way to revert this power profile and report back

------------------

Oh well, it seems that the power profiles do affect it:

This is the Power-Saver profile. Note how C3 finally comes on

And I can't recover them as I don't have a backup.
Hmm. Time to reinstall. Will be back in a bit

---------------

Yeah so.. um, it seems I just wasted time. Still no low C states.
Funny that C3 isn't coming in anymore It entered C3 in Power Saver power profile, after the video drivers were installed. Do I have to install a driver or something, or are the C states dealt in a lower level?


Waiting your magic! Please, take your time. Thanks

----------------

Heh. Now every profile has a Power state -- Even C8!

http://imgur.com/a/SJZmR

I'm considering it just a read bug. I've had the GPU drivers crash on me when I removed the power cable during gameplay, to test.
It might have affected TS somehow, idk. I still can't enter C6/C7 state, only C3 when I use a profile based on "Power Saver"

Here's another processor dump, moments before the GPU crash, if needed for anything.
http://pastebin.com/pXv8Nw5U

 

Hey bro, what about asus laptop? Should i use this value for non turbo ratio? Thank you for your awesome soft!

 

Hi unclewebbb,

I have a Lenovo T450s with a i7-5600U CPU.

When using your version 8 beta 2, everything was fine.
However, after switching to beta 3, the CPU will no longer down-clock whatsoever (even when 'idle').

The multiplier sticks at around 28, see these log entries:
DATE TIME MULTI C0% CKMOD CHIPM BAT_mW TEMP GPU VID POWER
2015-10-12 11:45:00 28.07 7.4 100.0 100.0 0 43 0 0.9147 3.1
2015-10-12 11:45:02 27.27 6.5 100.0 100.0 0 42 0 0.9147 3.0
2015-10-12 11:45:02 28.20 6.2 100.0 100.0 0 42 0 0.9147 2.8

None of the settings will change (up or down) the CPU speed, apart from 'Disable Turbo', which brings the multiplier down to 26.

Perhaps there is a small issue with beta 3 in combination with the low voltage U processors?
I tried everything I could think off, including deleting the .ini file. Also I tried many settings to see if I could make it work.

Now I reverted to beta 2 and all is fine again...
Do you have any idea whats going on?

Thanks and greetings, Auke Nauta

 

http://i.imgur.com/YilQcE7.png

@GTMoraes - When I am sitting at the Desktop with nothing running, my CPU spends 0.4% of its time in the C0 state. If you have a lot of junk running in the background on your system, your CPU will be prevented from using the low power package C States. If you changed your core parking settings, this can also prevent your CPU from using the deeper package C States.

I think only the low power U type CPUs support C8 / C9 / C10. ThrottleStop might let you adjust the package C State register to one of these values but if the CPU does not support it then those values will be ignored by the CPU. I am not sure what you will end up with. Any power plan that locks your CPU to the 8 multiplier can also reduce the amount of time your CPU spends in the low power C States. Running a CPU fast when idle isn't such a bad thing because that allows it to get background tasks done quickly so it can spend more time in a low power C State where it is disconnected from the voltage rail.

Why is that a bad thing?

The purpose of ThrottleStop has always been to encourage your CPU to run as much as possible at its full rated speed. The goal has always been maximum performance when plugged in. Battery run time has never been a priority because you are not supposed to be using ThrottleStop to force your CPU when running on battery power.

The thing that has changed in beta 3 is the new Non Turbo Ratio setting in the FIVR window. That setting can encourage your CPU to get stuck at a high multiplier which for many users, is not a bad thing at all. Post a screenshot of that part of the FIVR window. How do you have that feature setup and are you using the Windows High Performance power profile? If you want the Set Multiplier feature to work, make sure the Non Turbo Ratio is set to 0. If this setting shows Locked, either you or the bios has locked this feature.

@zoulll - I do not own your Asus laptop model so I am not sure what ThrottleStop settings will work best for you. It never hurts to try different settings and then monitor your CPU to see how it performs.

 

It never rests =(

On AC: http://i.imgur.com/irB5OO0.png
On Battery: http://i.imgur.com/WGi998Z.png

C3 is only achieved if I use a power plan that is either Power Saver or based on Power Saver, for some reason. Perhaps some of the hidden settings that can enable/disable C3, can also enable/disable C6/C7s?

I've reinstalled Windows, and so I believe the Core Parking settings have now been defaulted to Windows 10 values
The power plan is only set to limit the maximum frequency, which is to around 1500MHz, when on battery. Using the default power plans won't make it reach lower C states either.

I can't understand why mine cannot reach lower PC states =(

 

@GTMoraes - It can be something simple like one poorly written driver that can interfere with your CPU entering the low power C States. After installing Windows, I keep a close eye on the C State data while I add individual programs to my system. That makes it easier to spot a problem. I use Avast antivirus which may not be the best but it is more efficient than most antivirus programs.

To look for a hidden power plan setting, open up a command window and enter this command.

powercfg -qh >C:\settings.txt

The q option will query your Windows power plans and the h option will also include the hidden values.
The > option will redirect the output from this command to a file called settings.txt and will stick that file on your C drive so it is easy to find. Maybe you will find something in there.

 

It wasn't even entering C3 State when I first installed Windows, only after the video drivers were installed, that it was able to.
Since then, when only ThrottleStop was installed, only C3 works. All other drivers have been installed by either Windows Update or known updated sources.

I've read that the C6/C7 Pstates depends on the IGP to enter. I'll have a look on the Intel drivers (Mine seems to be more updated than the Lenovo website, so I'm gonna downgrade)

Thanks for the cmd line, I never knew that ">" would write the output to a file! Made reading much easier. Sadly, there were no relevant option disabled.
Can I read a file and write it back to the power profile? Although I didn't find anything particular to the package power states that wasn't already enabled, there were a few options that I'd like to tweak. Sorry if that's a bit off topic =D

------------------

Installed the Intel IGP drivers from the Lenovo Website.. no dice, still no C6/C7s.
Could Lenovo just had simply disabled it on BIOS? I'm using the latest version, released few months ago. The one with the new Lenovo typeface, v3.03

I've changed the RAM for two modules of Corsair Vengeance RAM (1.5V, DDR3) and I'm running on a SSD. That's all that's different from stock... just in case that info is worth something.

 

@Papusan how is CPU performance with new Thorttlestop? Run some benches.. D2 Ultima was wondering about Alienware CPU throttling...

 

The powercfg command lets you make 101 different changes to your laptop power profile.

https://technet.microsoft.com/en-us/library/cc748940(v=ws.10).aspx

That is very likely. I used to see some random BSOD issues on my 3570K desktop CPU when overclocking with the package C States enabled. There were also some Asus laptops that were randomly crashing. Disabling the package C States seemed to fix that issue. Turning them off might not be a bad thing to do. Surprising they don't work when on battery power. Head to the Lenovo forum and see if this is a common problem. Contact Lenovo and tell them to fix it. They will probably ignore you.

That is the kind of feedback that I am interested in too. For me, beta 3 is the best TS ever. The VCCIN feature can be used to slightly improve full load performance and the Non Turbo Ratio feature gives me a new way to maintain the maximum multiplier without having to use the Set Multiplier feature. Increased TS efficiency = improved performance. I think the low power U CPUs are the ones that are most likely to benefit from these new features.

 

Thanks, I'll have a look into it.

I made a thread there to see if someone has something to say, but I'm expecting to be ignored.
A friend and neighbour of mine has a similar laptop model as I do, though it's not a touchscreen model, and uses a i7 4710HQ. His package C states works when on battery mode, and the C3 State works even when in High performance profile (whereas mine wouldn't work if not set to Power saver). He's on v2.xx BIOS and I'm on v3.xx BIOS. He can squeeze 3:30hrs on his laptop, on battery mode.

I'm out of ideas.. I'll try restoring the BIOS setup defaults to see if that does something. If it doesn't work, my only hope is to wait it to eventually work out..

Thanks for the help!

 

@GTMoraes - You might be interested in running Intel BITS. This program starts up before Windows loads so you can see if the bios is setting your CPU up correctly.

http://biosbits.org/
https://downloadcenter.intel.com/download/19763/BIOS-Implementation-Test-Suite-BITS-

It lets you see your C State core and package residency percentages before Windows loads so you can figure out if you have a bios issue or a Windows issue.

 

Unclewebb, once my Damm accounting exam is over, I'm gonna try Throttlestop 8 beta 3 on the i5-5300U in the Lenovo T450 which work gave me... Need non-throttle sustained performance for all that code lol

Will happily give you some info about it.. The VCCIN feature looks really revolutionary and I can't wait to try it

Sent from my LG-H811 using Tapatalk

 

Great! I was thinking about using a live Ubuntu build, but they seem to be having problems of their own, with the C6 and C7s states.
Many thanks for the suggestion. I'll try to use it here

-----------------------

Weird. BITS said it couldn't identify my processor, and only displayed generic tests. As such, there is no C-State tests to be displayed. How come?

 

Thanks Tom. I would get a lot more accomplished if I could afford one of everything but sadly I cannot. User feedback is necessary and is always appreciated. Lots of screenshots or links to screenshots to keep the mods happy is also appreciated.

@GTMoraes - That's odd that BITS does not support your CPU. I am out of ideas, for the moment at least.

 

Eh... I'm on a bad luck trail.

I recently had a horrifying crash, where my game would lock up, the last millisecond of audio would repeat like a fast machinegun, then it'd unfreeze, run for half a sec at 0.5FPS, then lock up again. Repeated this a couple of times, then displayed a garbled blue screen with a bugged sadface all over the screen. Thought it wouldn't turn back on after force shutting down, lol
As I've never experienced this crash before, I went on to find the source of the problem before playing again. And I found that the VCCIN is getting messed up between reboots, which I guess it was the cause of it.

I have a "Normal" profile and a "Game" profile, also a "Battery" profile. VCCIN in Normal and Game is set to 2.1250 and on Battery it's set to 1.7305.
When I reboot, sometimes the VCCIN of the Battery is set to 2.1250. Sometimes Normal or Game profile is set to 1.7305.

Does anyone experience the same behaviour? Or I'm not supposed to have different VCCIN values for different profiles?

 

Maybe you somehow got an ES or QS sample instead?

Even though the 860M doesn't coincide with that release time frame...

 

That'd be the icing on the cake.
But perhaps not. It's soldered on the board, no way they'd release a fully working laptop with serial numbers and stuff with a ES or QS processor

I don't know if the v3.03 BIOS I'm using disables the C states, and previous BIOS versions wouldn't. I can downgrade the BIOS, as it's supported, but I'm too damn afraid to flash BIOSes, even more to downgrade.
I dream of, someday, having the balls get my BIOS "unlocked" and flash it. I'm pretty certain it's the BIOS that's messing up with the C-States.

 

@GTMoraes what BIOS version do you have?

A screenshot from my Y50 with 4700HQ, running W10. BIOS is 3.03(latest)

 

V3.03. Oh well, at least I can scratch off a BIOS downgrade. That's exactly the picture I was hoping to ever get -- the exact processor model with the same laptop model. You've got the C6 state coming in, so it supports (as expected).
Is it a Touch model? How long does it last on battery?

What could possibly be the cause...

----
Just in case it's worth something, my ThrottleStop config:
http://imgur.com/a/whZ1b

I don't think there's anything to do with the fact that I can't enter lower package C-States, because it can't, even with a fresh restart, and using RealTemp (to avoid ThrottleStop possibly changing something) to check the C-States...

----
Hey @ATG , could you please run this command:

powercfg -qh >C:\settings.txt

and paste on pastebin the results? I'd like to compare with mine, and possibly find the cause of this

The processor only drops to C3 Package state only if I use the "Power Saver" profile, while on my friend's Y50 it drops even in High Performance mode. There *may be* something on the profiles, so I'd like to clear that out

 

I´m currently at work I´ll send you the powercfg output when I get home.

Fyi I haven´t done any changes in the TS´s config apart from what you see on the screenshot - no profile set up, no undervolting or anything. I normally don´t have TS running because I don´t run anything demanding right now, I just ran it to help you out.

My Y50 is a non-touch FHD model, 1+ year old. I rarely use it on battery so I can´t tell you how long it would last.

P.S. The screenshot above was taken with power supply connected, do you want one with AC disconnected?

 

Could someone explain what the Non-Turbo Ratio does and what changing the number will do?
For my i7-5500u, the original number for the Ratio was 23. If I put 24 (anything higher than 24 defaults to 24), Turbo is deactivated. If it remains at 23, Turbo remains. However. if I leave it at 24, unplug my charger and replug it, Turbo appears.

 

Me too. I was playing with the VCCIN setting last night, exploring the outer limits of 2.3047 V and my Y510P locked up with a blue screen. What I think happened after that is when my laptop rebooted, the bios did not reset the VCCIN setting. I had a few blue screens because of this when trying to boot up over and over. I finally held the power button for 4 seconds which forced the CPU to reset itself. After booting up, everything was fine. After that test I decided to change ThrottleStop slightly. I set the maximum VCCIN setting to 2.3047 V since nothing beyond that works on my CPU anyhow and if this is the new maximum, users might be encouraged to stay a little below that.



There should be no problem using different VCCIN values for different profiles. Make sure that each profile has Unlock Adjustable Voltage checked. If you are playing with VCCIN, you will not be able to go back to the Default VCCIN value unless you reboot or do a Stand By resume cycle. My 4700MQ would instantly crash when trying to go back to the Default value so I deliberately blocked that. Once you boot up and start using VCCIN, you will have to continue using VCCIN. My laptop can quickly go into and come out of Stand By so this is not a big deal for me. A setting of 1.7305 V might be too low for your CPU. 1.77 V and I had an instant black screen. Not a crash but the screen went blank.

There is an adjustable time component to the C States. For example, if a CPU is in C3, it starts a timer and when that timer ends, it will switch to C6. If during that time period something comes up that the CPU has to process, it will go back into the C0 active state and will avoid going into C6. I think you can see that if this timer is set to a very small amount of time, the CPU will have a better chance of getting into C6 on a regular basis. If this timer is set to a large amount of time, your CPU will rarely if ever enter C6. Something like that might be the difference between my 4700MQ that can spend 85% of its time in the package C6 state and the Y50 that is spending hardly anytime in the package C6 state. Maybe adjustable C State timing might be a new feature for ThrottleStop.

@Game7a1 - My Lenovo Y510P - 4700MQ sets the Non Turbo Ratio to 0 which seems to be the default value. When set like this, the Set Multiplier option in ThrottleStop lets me fully control the speed of my CPU. I can adjust this from 8 to 34 and at each step, the CPU will run with that multiplier.



If I change the Non Turbo Ratio to a fixed value such as 16, now Set Multiplier can still be used to fully control my CPU at any multiplier of 16 or less.

http://i.imgur.com/QQvMwoK.png

If I try to use a multiplier of 17 or higher, the CPU sees that this request is above the Non Turbo Ratio so that means it is time for the CPU to start using as much Turbo Boost as possible.

http://i.imgur.com/kVeDn5h.png

Some people with low power U CPUs have complained that the Set Multiplier feature in ThrottleStop does not work. Based on this testing, I am thinking that the reason for this is because of how the Non Turbo Ratio register is set. Now users have access to this register so they can see how it is setup and if it is not locked, they can change it. In the screenshot above, Non Turbo Ratio - 16 means that the CPU is currently set to 16. If it shows nothing beside Non Turbo Ratio then the CPU has set this to zero or the Default value. If it shows Locked in this box to the right, this register is locked and cannot be changed.

My Y510P uses the Set Multiplier register to disable Turbo Boost when gaming. By setting the Non Turbo Ratio to a very low number between 1 and 7, this tells the CPU to ignore this low multiplier request. Lenovo tries to set the multiplier to the default value of 24 to disable Turbo Boost. The CPU sees that this is above the Non Turbo Ratio so it replies, no thanks Lenovo, I am going to use full Turbo Boost instead! I am not sure if this is going to be a useful feature for the U CPUs but I thought, depending on the laptop model and the throttling scheme being used, this new feature might help out. You can also set the lock bit within the CPU so if you use ThrottleStop and set it to 1 and lock it, no other software can change this value. I can exit ThrottleStop after that and run my CPU at full Turbo Boost without any worries of being throttled. It will only throttle if it reaches the thermal limit or if the CPU reaches the turbo power limit but it will no longer throttle randomly because Lenovo thinks it is a good idea to disable Intel Turbo Boost when gaming.

@intruder16 - Thanks for posting that link. I decided to play around with this setting some more so I could understand Non Turbo Ratio better and provide a more thorough answer.

 

@GTMoraes

Powercfg output - http://pastebin.com/qpJiVN5v

Dump output attached, just in case someone is interested.

Screenshot from TS while running on battery: