The ThrottleStop Guide

Hello, I did not find it in the thread so I hope I am not asking redundant questions

I see Skylake is supported but is undervolting working, coz it does not have FIVR? Also is it fine to copy ThrottleStop.ini into new version directory or do I have to setup everything again?

 

When setting up the new version, I would advise turning it off, deleting everything in the directory, then reboot and set it up again. That way, you are starting from scratch with any new settings. BTW, Skylake does have FIVR - I'm using it with my 6700HQ. An old version might cause FIVR not to show. Undervolting does work, but CPU and Cache have to be set to the same value or it doesn't take.

J

 

It changes a flag in the embedded controller of the CPU/ motherboard. You can use RW Everything to change this flag too (but throttlestop automates this process)

In Skylake the Voltage Regulator (VR) is no longer fully integrated (FI) into the CPU.

However, thankfully (and I believe I was one of the first to discover this in this thread - it was a shock to Mr Unclewebb when I reported this), the external VR used in Skylake still uses the same memory addresses for its command and control. Throttlestop simply changes the "old" Haslake addresses and they continue to work.

However, there are some quirks around this probably due to different manufacturers using different voltage controllers. For example, on my HP 6500U:

• VCCIN does nothing
• Changing System Agent does nothing
• Changing Analog I/O does nothing
• Using Static Voltages (no matter how generous) immediately freezes the computer (no bluescreen nothing).

 

how much is the full version? i cant use TS anymore, beta expired

 

I'm having an issue with the notification area icon - if I change the resolution (which I do when playing more demanding games) the Throttlestop icon duplicates itself. It's pretty annoying when there's 10-20 Throttlestop icons in there.

I've tried clearing the icon cache with no luck, but if I change the Windows 10 icon/text etc. scaling to 100% it fixes the problem, though I have to squint to see anything on my 13" laptop. I didn't have this problem with any previous version before 8.20.

 

So I'm trying to make two profiles for my MSI GS73VR which uses an i7-6700HQ. I'm pretty much following a reddit guide to the letter to accomplish this. I think I finally did it but I changed a couple things on my own. For one, I'm leaving my laptop using the Windows High Performance profile, when he recommends using the Power saver profile . On power, I want throttlestop to use TS profile 2 and on battery I want it to use profile 4. Everything works as it should but now when I go to benchmark my battery saver profile, the multiplier is acting kind of strange. When I run Prime95, my multipliers will cap out at 9x. I'm 99% positive when I first set this up it was at 14x, which was the limit I had set. What's funny, is it will actually go up to 14x for normal tasks, just not with Prime95. I think it has something to do with Powersaver mode being actuated but I don't understand why Prime95 would trigger that. Any ideas what might be going on? I'm thinking perhaps I must have not had Powersaver checked in the past or something. Either that or I'm confused on how it actually works and what triggers it. FYI I'm using TS 8.20

 

The freezing when using static voltage doesn't seem to be specific to Skylake, though. My wife's i5-5200U does the same, whereas my i7-6820HK accepts it. Maybe it's an issue with the U processors?

 

@tb227 - Here is the official Intel definition.

Your laptop manufacturer might have accidentally put a power limit on the Intel GPU that is way too low. Your screenshot shows that the CPU is also using Clock Modulation throttling and the CPU is thermal throttling. These are all signs of a laptop that was not well designed. Try going into the TPL window, click on the Power Balance feature and set CPU to 0 and GPU to 31 and see if that makes any difference. Also check off Clock Modulation on the main screen and set that to 100.0%.

@Dashing_97 - The Windows High Performance profile is needed so the ThrottleStop Set Multiplier function can work correctly. Intel XTU ignores some of the changes that ThrottleStop makes. As soon as you start XTU, it might be making its own changes to the CPU power settings, etc. That is why I recommend not to use both programs at the same time. There is only one set of registers in your CPU. It doesn't make sense to have two different programs writing different information to the same registers. If your laptop shuts off, it is either over heating or your settings are not stable. Some people adjust various voltages and do not do any thorough testing to see if the new settings are reliable or not.

@illuzn - Were you playing with the new Speed Shift controls? Speed Shift and SpeedStep are two different things. Enabling Speed Shift might let your CPU drop down in MHz lower than it ever has before.

I have been telling people that for years. A slow CPU is an inefficient CPU and it might increase power consumption instead of decrease it.

Are you talking about the Disable Turbo option in ThrottleStop? This option changes a few registers in the CPU so you can disable Intel Turbo Boost.

@Crimeinal - I recently changed a line of code which might be causing your multiple icon problem. I will try to get that fixed up ASAP.

ThrottleStop is freeware, infinite beta software. The latest beta is in my sig.

@Derek712 - The Non Turbo Ratio has to be set to zero (0) if you want the ThrottleStop Set Multiplier and Power Saver features to work correctly. Your screenshot shows that the Non Turbo Ratio is locked to 26. If you locked this, don't lock it or lock it to 0. If your bios locked this, there is nothing that ThrottleStop can do about that.

 

Yes, Unclewebb I was playing with the speedshift settings. Not sure what I did but the CPU dropped to ridiculously low levels where it was consuming more Watts at idle than at higher multipliers.

And yes - I agree with you there is absolutely a sweet spot (especially with these U class processors). Running the CPU at 100% even on idle does generate higher idle power consumption as well. That sweet spot for me seems to be around 30% - which equates to a 8x100 multiplier). Less than that actually increases idle power consumption because the package doesn't spend time in its sleep states.

 

The Hello, how to do that would have always been at full capacity?Or always worked turbo?

 

Hi,

I've been using ThrottleStop 8.10 beta (like this one: https://www.techpowerup.com/downloads/2667/throttlestop-8-10-beta-2 ) to get my Dell notebook to behave under Win7 (basically without TS it was stuck at non-turbo freq, with TS I managed to get SpeedStep & Boost to work somehow).

However the version I've been using now tells that it has expired and doesn't start. I tried TS 8.20 from the first post but at the first glance it doesn't seem to work properly for me with the same settings.

Would it be possible to obtain TS 8.10 beta2 (as in https://www.techpowerup.com/downloads/2667/throttlestop-8-10-beta-2 ) but without the date expiration check so that I can continue using it?

 

Hello there,

As usual, awesome job with every new ThrottleStop iteration I have already been using 8.20 on a few laptops at work, and Speed Shift does indeed seem to be working as expected under Windows 8.1.

One thing I've noticed when updating from 8.10 to 8.20 on my i7-4790K desktop is that for some reason I've stopped getting C-State readings, and given how no setting has been changed I'm not quite sure what could be causing this. I wonder if this might be a bug of sorts.
I've attached screenshots for reference.



EDIT: Attachments seem buggy to me right now, not sure if forum's acting up, so I've uploaded images elsewhere just to be safe.

ThrottleStop's main window - http://i.imgur.com/jiCCWz7.png
ThrottleStop's C State window - http://i.imgur.com/3eIX5SA.png

 

So because I wanted to actually be able to use my laptop I did some digging. It seems that the *initialization* code from the old ThrottleStop 8.10 beta2 is what did the trick for me.

For context (I posted earlier in this thread about the settings I had to use) -- I have new Dell laptop that doesn't support Win7 in general (comes with Win10). I managed to install Win7 but SpeedStep & Turbo wouldn't work at all (CPU stayed at fixed non-turbo freq all the time).

Using ThrottleStop -- specifically enabling turbo multiplier, enabling SpeedStep (which doesn't seem to do anything), and (crucially) enabling Power Saver actually made both SpeedStep & Turbo work for me. I was pretty happy

unclewebb said though that it shouldn't work -- that Power Saver shouldn't actually do anything on modern CPUs. But it did work. However it didn't work after sleep/resume until ThrottleStop was restarted.

As I already mentioned it appears that the 'secret' is in whatever ThrottleStop 8.10 beta2 does during its initialization. It does something which afterwards lets 'Power Saver' checkbox to actually work on my machine. After sleep/resume this 'thing' is reset and therefore SpeedStep no longer works (CPU stays locked at very low freq) until ThrottleStop is restarted (thus running initialization again).

Something obviously was changed in 8.20 and I can't get SpeedStep/Turbo to work on my machine. However the initialization code from ThrottleStop 8.10 beta2 still executes (even though it then quits with expiration message) -- thus I am able to get SpeedStep/Turbo to work if I first run 8.10, kill/close it, and then run 8.20 -- at which point it magically 'works' until shutdown/sleep/hibernate.

This is obviously less than ideal solution

So, as I asked before, would it be possible to share 8.10 version that keeps working (doesn't quit with 'expiry' message)?

Additionally, if there's interest, I am prepared to run development/debug versions to try and figure out what magic thing in ThrottleStop 8.10 beta2 initialization code actually causes SpeedStep/Turbo to work on my machine (might be useful for other people with similar hardware).

Thanks!

 

Hi @unclewebb
first of all, thank you for the really nice work

I unlocked multiplier on my i7-4710HQ (downgrading CPU microcode) and I'm using TS 8.20 to overclock it. I reached 3.9 GHz with all 4 cores active and 3.9 GHz for the cache. I have CPU min/max to 100/100 in Windows Power Plan and TS starts automatically at Windows startup.



However, I have a little problem.
Often, after startup, cores multipliers go correctly to 39x, but cache multiplier doesn't go past 35x.
Limit Reasons says "Reserved" under Ring column, and in HWiNFO64 is triggered "RING: Running Average Thermal Limit", even with cold start and CPU at 40°.
I have to reboot my machine 1 or 2 times to get it work and have 39x both for CPU and cache.

Any suggestions?
Thanks

 

Hello!

I just got my g752vs with a gtx1070 and a 6820hk, and i'm playing with ts.
First of all, thanks for TS, amazing job unclewebb.

I'm in pursuit of a ultra-quiet mode for when i'm using the laptop next to my wife. The gtx1070 wont go above 70°C even with a mild OC, so the noise and temperature are all from the cpu.
Stock numbers i'm seeing 1,4v+ on the cpu. Isnt this too much?
My question is, for a skylake cpu where should I start UV for the cpu and for the cache? Do they have to be the same UV? Any sugestions and must have for a start?

Thanks!

 

For a start, you should take a look at the short and well-written "Undervolting and Overclocking Guide" by user Eason (see link in his signature below):

http://forum.notebookreview.com/thr...0-owners-lounge.783377/page-307#post-10351515

Then you might scan this thread (particularly the first few pages, do a search for Skylake, etc.)

I believe with all Skylake processors, you need to keep undervolt the same for the CPU and the CPU cache, but I am not 100% sure. I would start with a very mild undervolt (like -50mv), do some stress testing, and if you get no failures or black screens go "down" from there in small increments. For the Dell 9550 laptops, I see users get less undervolts with i7 vs. i5; that may be chip related or cooling related. Due to the secrecy of Intel, some of your Throttlestop will just be trial and error.

Word of caution. Don't try using ultra stress tests. FurMark can easily overheat and break your laptop. Thanks to professional laptop engineer here named GoNz0 for the tips. I usually try a combination of Prime95 and RealBench.

Dell has a power controller software that allows one to choose a "quiet" mode that effectively slows down the system and the fans; maybe ROG has the same?

Finally, you might look at fan control software. But do some research there as if the program has a glitch you could be stuck with an overheating situation.

 

@Solf__ TS 8.10 beta 2 doesn't exist anymore. I delete the old versions when a new version is done. How about boot up your computer, only run TS 8.20 and post some pictures so I can see how you have TS setup and what problems you are having. It's not that Power Saver doesn't work on newer CPUs, it's just a poor way to control a modern CPU so I do not recommend using it. Skylake CPUs should be using Speed Shift which is available in the ThrottleStop TPL window. I have heard that the latest version of Windows 10 enables Speed Shift automatically but I have not had any feedback about this issue. When Speed Shift is enabled, it takes over control of the CPU multiplier so when testing Speed Shift, do not complain that Set Multiplier and SpeedStep and Power Saver and etc. do not work. That is all by Intel design.

@andreacos92 - Nice overclock! In the ThrottleStop FIVR window, make sure under Cache that you have Unlock Adjustable Voltage checked and that Cache Ratio is adjusted to 39 and that Min Max Cache Ratio is adjusted appropriately. I think the Voltage and Cache Ratio are both in the same register so even if you are not adjusting your cache voltage, it still needs to be checked in TS to access the maximum cache ratio.

The purpose of microcode updates is to fix any bugs. Did you do any testing with the original microcode to see if there were any Limit Reason Ring problems? Can you post a screenshot of TS - Limit Reasons so I can see if this is being reported correctly. It might be a CPU bug or a bios bug that is causing this issue. Just for comparison, my 4700MQ does not show any Limit Reason activity when idle.

@tribaljet - Nothing has changed with the C States. Check your bios to make sure that they are still enabled. They might have accidentally been disabled in the bios. I am still getting the same core and package C state activity when idle as with previous TS versions.

@Miguel Pereira - As with any overclocking / under volting adventure, just start adjusting and see what is stable and what is not. It is always better to do your own testing on your own CPU compared to getting some values off the net that worked for somebody else. Skylake CPUs do seem to have very high default VID voltage settings. While stress testing, start lowering the bar until you lose stability.

Just added a new mini mode feature for @Papusan



All that junk on the left hand side is not used that often so it can be hidden if you want. The + sign at the lower right will display all that other stuff when you need it. Handy for benching!

 

@unclewebb thanks!

This is a screenshot of Limit Reasons - FIVR window and HWiNFO reporting the issue.



I have just to reboot 1 or 2 times to let the issue disappears and then I can go past until I find unstability and without any other limit, changing multipliers as I want without problems, ecc.. it seems completely casual.

With other recent microcodes I hadn't any issues, only limits were thermal and power limits (according to what I set in TPL window) but I can't go past 37x.
01 and 02 microcode exploit an Haswell bug that let you unlock multipliers like you have a -K processor

I have to say that, when I downgraded microcode, I had TS 8.10 (latest beta). I rebooted and TS said that my beta version was expired and I updated to TS 8.20, so I never tried with TS 8.20 and most recent microcodes.

EDIT: just tried 8.10 for testing, and I have the same issue. So, most likely, it's a bug of the old microcode.
It can be interesting to find out what causes this, because HWiNFO says "Running Average Thermal Limit" but it's obvious that this isn't a temperature related problem.

 

Though UncleWebb is clearly the authority, I think nonturbo ratio in FIVR is supposed to be set to 0 (or perhaps 1). BTW, turning on speedshift explicitly on TDP page dropped idle clocks and temps dramatically, without seeming to compromise performance (6700HQ). Some time I would love it if someone (UncleWebb?) woould walk through other settings on TDP page. I have looked through the thread, and, so far, haven't found a good description of what I can change and what it does.
Continued thanks to UncleWebb for his excellent work and support.

J

 

Whenever I run ThrottleStop 8.20 and minimize it, it minimizes to both the taskbar AND systembar. how do I get rid of it showing up in the taskbar and only show in the system tray? I have the option selected throttlestop. (Windows 10).

 

There was a recent post asking that same question. Just do a quick search...

 

I did and I even used the notification BAT tool that throttlestop recommends in their readme. it keeps showing up.

Nevermind. I fixed it. Uncheck "Taskbar" in Throttlestop. Oops

 

What's going on? Windows Defender has now decided that Throttlestop is malware! I'm beginning to think that Windows Defender is malware!

Best,
J

 

Nah, just what is expected from 'intelligent' software these days. (i.e. it's just a best guess until proved otherwise).

 

I send new idea's in PM Keep up the good work Unclewebb!!
And the new Package power feature is nice I can now see max power draw from the bench afterwards Here a Cinebench R11.5 run from BGA-KILLER with a baby Girl overclock at 4.6 GHz



Edit. @Miguel Pereira You're welcome!! http://forum.notebookreview.com/threads/investigating-6820hk-performance-and-overclock.795152/

 

I'm using windows10 and i've used the windows10 guide to have TS started automaticly, but somehow its not working.

When I start win10 TS is not starting. Is there another way? Could I be making something wrong?

 

Thank you! Thank you! Didn't realize you've added this option.

I just started with clean install of ThrottleStop 8.20 and I only changed 'Enable SpeedShift when ThrottleStop starts' under TPL. I didn't need to change anything else (well, apart of like 'start minimized' and hiding from task bar). I didn't even need to actually 'turn on' ThrottleStop.

Now it works like a charm. And it survives sleep/hibernate without having to restart anything. Just to clarify -- this is under Windows 7.

A couple of questions:
- Will 8.20 keep working or will it also expire at some point?
- You mentioned that under SpeedShift other options like SpeedStep do not work (which is completely fine by me). I just want to confirm that if I only use 'Enable SpeedShift when ThrottleStop starts' (without even 'turning on' ThrottleStop), then I don't need to worry about 'proper' settings for all other switches?

Thanks again!

 

Windows Defender is picking up a Trojan everytime I try to download, and use this now?

What's with that?

Also, how do I install 8.20 and keep my settings?
Do I just copy the executable into the old 8.10 beta 2 folder, or what?

 

My solution to the Defender problem was to turn Defender completely off, download and set up TS, and then go into Defender settings and tell it that the TS folder and program are exceptions. Then I turned Defender back on.

The settings live in the .ini file in the TS directory. However, it may be better to start over - turn off TS, clean the directory, install and reboot. There are a number of settings I don't yet understand, and am leaving at default until I do. Just a thought.

J

 

@unclewebb Yes, speedshift is on by default in Windows 10. The "Speed Shift Technology" box is greyed out and permanently ticked on my machine.

 

Don't know if someone mentioned this already, but the newest windows 7 update broke things. I get "CPU not supported" now when it tries to open.

 

Not sure why all of a sudden Windows defender is having a fit with TS and calling it a Trojan... It's been fine for a week. Anyone else having this issue?

 

Are you using 8.10 beta per chance? If so -- this is because it is expired. Dunno why it says 'unsupported cpu' instead of expired, but you could try setting date to June to test it out.

Or better yet just use 8.20.

 

I've used Throttlestop before the 8.20 update, and after updating it can't seem to keep my undervolt settings after a few restarts. I have "Adjustable Voltage unlocked" to CPU, GPU, and CPU cache and saved it, but after a few restarts the Adjustable Voltage box is unchecked and it loses my settings. Does anyone else have this problem / is there an extra setting that I have to watch out for? I'm also having an issue where my explorer.exe would freeze and terminate (have to restart cpu) after I updated to 8.20. I'm not sure whether the problem is related to Throttlestop 8.20 or the new Windows update that occurred last Friday. I currently removed Throttlestop and will see if the explorer problem will recur.

For reference, I have a Dell XPS 9350 (i5-6200).

 

Thanks for this excellent software.
I had an acer 571-9890 with an i7-3632qm inside and I tried playing with TS a couple years back. Unfortunately it couldn't do much for ivy bridge so I was stuck with a hella hot and throttling laptop, mitigated somewhat with aftermarket thermal paste.

Recently I got an inspiron 7559 (i7-6700HQ, gtx 960m) which runs super cool but I'm messing with TS 8.2 anyways and just from some cursory testing I am very impressed.

Here is prime95 running stock vs a -125mV offset on both core & cache (locked multiplier to x11, no speed shift, no idea if this is stable yet)

As you can see, CPU package drops from 8W to 6.3W when undervolted which is super nice.

EDIT:
I noticed that when unplugged from the outlet suddenly the 11x multiplier lock is ignored and the CPU sometimes jumps up to 3GHz+ and power/voltages jumps accordingly. Plugging back in brings everything back down to 1.1GHz though. weird.

EDIT
Also, after unchecking 'lock multiplier' in the main window and clicking 'turn off', the clocks didn't budge from 1.1GHz until I switched power plans in windows

EDIT
So I set voltages to -180mV and rebooted, ended up in a blue screen loop (but fortunately I was able get to desktop and disable TS voltage controls)... I had no idea the voltage offset applied by TS is persistent through reboots... is this intentional? It seems like very dangerous behavior by default that should be printed in bold somewhere, maybe I missed the disclaimer?

Also, my computer now wont drop back to idle clocks even when I don't have TS open. It seems the windows power settings are ignored and clocks are always 2-3+GHz even when nothing's going on. The only things in TS that I touched were the voltage offsets & multiplier locks (both in the voltage offset window [which didn't do anything] and in the main window), didn't mess with any of the options. The only thing active is the voltage offset but that doesn't seem like it should bump clocks to be higher than normal (and in my prime95 testing earlier it didn't). But exit TS, reboot, check clocks with cpu-z and clocks are really high... Tried plugging/unplugging AC, tried switching windows power plans (& restoring defaults, but they get ignored), tried multiplier locks - nothing. Seems very odd, did TS manage to do this? Only thing that managed to drop clocks back down was enabling speed shift in TS and setting the range low.

EDIT
So I turned off voltage controls in TS, unchecked the lock multiplier box, rebooted, made sure speed shift was off, rebooted a couple more times, and I can still see that windows power plan settings are getting ignored and clocks are not dropping back to idle even when throttlestop is not running. They are fluctuating between 2.5-3.3GHz, I can only force 800mhz for a split second by disconnecting AC. How is TS managing to do this? I've even renamed the folder the executable is in and it seems not to be autorunning. Is there some way I can unload whatever TS settings are persisting through reboots?

EDIT
Set multiplier in the main screen is also getting ignored. What is going on ?

EDIT
High clocks went away after hibernate. ¯\_(ツ)_/¯

Opened TS and set core/cache to -160mV, which is probably on the cusp of stability for me.
Noticed that when TS was open the CPU multiplier ignored windows power plan boundaries as before, and after closing TS the same behavior is back.
Guess can't have voltage offset without clocks ramping. Does anyone notice this?

 

margroloc, where did you get the new throttlestop. All the older versions seem to not support my 6700hq

 

TS 8.20 in @unclewebb 'd sig support Skylake.

 

As stated above, its in his sig
I would be careful.. based on my personal experience the past couple hours it seems that undervolts are persistent across reboots even if TS doesn't autorun, and somehow Windows (and TS's own set multiplier command) can lose the ability to control clocks and you'll end up with a CPU that can't idle without using speed shift.

EDIT: all on windows 7 sp1 x64
EDIT2: the high clocks went away after a hibernate ._.

 

I had Setup throttlestop via Task planer to Start on Windows (10 with 64 Bit) Login. For me in latest Version with every restart there are added new Icons in the taskbar. So that throttlestop Icons are hidden automatically (temperatur, ghz, Nvidia temperature). Can anyone confirm this. I installed 8.20 over the old version. . .

Clean Icons .bat did work but the Same symptoms are back again after a restart...

 

I stumbled into software called ParkControl, which permits one to tweak CPU parking and also set an "ultra-high performance" power plan.

https://bitsum.com/parkcontrol/

Is anyone currently running ThrottleStop with ParkControl simultaneously?

Are there any benefits or conflicts?

Thanks!

 

@andreacos92 - Looks like the microcode update fixed the bug that you found. Cache ratio is not that important so being able to overclock the CPU even if the Cache is limited would probably give best performance.

Windows Defender is correct. ThrottleStop can make your CPU run hotter and faster. To some, that might be a bad thing but most people here are quite happy when their laptops are finally running at their full rated speed.

All recent versions of TS will expire. That is a good thing because it means I am still working on it. Speed Shift is much better than the TS - Power Saver feature because it is done at the hardware level by Intel. This allows the CPU to get up to full speed much faster when it has been mostly idle. I knew some Windows 7 users would appreciate being able to access Speed Shift without being forced into Windows 10 just for this one feature. As always, use as many ThrottleStop features as you need to get your CPU running how you want it to run. It is a multi purpose tool and not all features are going to be needed for every single CPU. If you are ever unsure, post a screenshot and ask away.

Thanks for confirming that. What build version of Win 10 are you using? When Speed Shift is enabled, that automatically disables some TS features like Set Multiplier. I might have to make that more obvious because it seems to be causing some confusion. Something else I noticed is that when I am not running ThrottleStop, my Win 10 laptop now boots up with the Non Turbo Ratio set to 1. In Windows 8, it was always set to 0. This minor change completely changes how the Windows Balanced profile works and it also disables the TS - Set Multiplier function. This might be another "feature" recently forced on users.

@ methylethylphenyl - In the FIVR window, make sure that you have checked off, OK - Save voltages immediately.

Why would you want to turn a speedy 6700HQ into a slug? Sounds like you might also be having trouble controlling your CPU because of the Non Turbo Ratio. Don't blame TS. I think MS has been up to no good again. Another Windows update might be throwing a curve ball at users. Make sure Non Turbo Ratio is set to zero if you want Set Multiplier to work correctly.

This is totally up to your bios. When you reboot, it is up to the bios to completely reset your CPU speed and voltage. When you reboot, ThrottleStop is not running so it has zero control of your CPU. Sadly, some manufacturers don't know how to set up a CPU when it is rebooting.

When ThrottleStop goes from active mode to Monitoring mode, it simply leaves your CPU as is. It doesn't reset it to any particular state. The state your CPU ends up in, the voltage, the speed, etc., all depends on what else is controlling your CPU. Usually Windows takes over but depending on what you set in ThrottleStop, that can prevent Windows from taking charge. I think you need to slow down and change one thing at a time and get to know what sort of control each setting in ThrottleStop has on your CPU.

One bug I know about is that if you use TaskKill in a script, this will force ThrottleStop to immediately exit and will prevent ThrottleStop from cleaning up after itself. It won't have a chance to release any resources back to Windows and it will leave icons in the system tray because it won't have a chance to delete them before closing. Are you using a script? If not then I think the problem you are having is because I accidentally deleted one line of code. It seemed redundant at the time but in hindsight, I probably should have left it alone. That bug has been fixed and a new version of TS with some of @Papusan's suggestions will be out, probably within 24 hours. If there were less questions here, I might get more work done.

 

@unclewebb Windows 10 version 1607 Build 14393.222

 

Good Evening All - Need some assistance please!

ThrottleStop does not work on my machine - Lenovo ThinkStation w/ Broadwell-E Xeon. And there is no option to disable C1E in the bios -

I read a few pages back that there was a way to disable this in the registry or via Powercfg but no exact clear instructions.

RealTemp works and has a C1E box that I can uncheck and CPU goes to Max performance! but It does not stay upon reboot and unsure which command this is actually invoking.

Any help?! Please and Thank you!

 

Thanks for the clarification, that helped immensely.
I initially tried to lock the multiplier to test power draw by changing the 'non turbo ratio' in the FIVR panel before figuring out that the 'set multiplier' command was what I wanted to use. I didn't notice any changes after setting the 'non turbo ratio' to a non-zero number so I figured it did nothing and forgot about it. After undervolting and checking clocks that was the source of my confusion as I had forgotten that the default was 0. I set it back to zero and clocks are fine now. The undervolt is beautiful and idle temps dropped 4C to 36C on my inspiron 7559.

In case any skylake i7-6700HQ people are reading, my tests are showing that my sample is stable with -160.2mV on core & cache (so 800mhz at 0.589V or thereabouts) while -180mV leads to BSOD.

 

Hi unclewebb, i do not use any script like this. i only use a planned tast to start throttlestop when the user is logging into windows. The Task Bar list (the selection list - which items should be shown) is getting longer with every reboot. I have attached a sample.....

Spoiler

 

Hey guys it seems i have problems with latest beta version, 8.2. Just cant make it work.
I used 6.0 before without issues.
I have i7 4720HQ, win 10. No matter what options i choose, when i click on turn on nothing happens. Any tips?

 

Are you using ThrottleStop 8.20? I just helped a guy on the [H]ard Forum with the same problem. You might be the same guy. His problem with C1E was solved.

https://hardforum.com/threads/how-to-auto-disable-c1e-w-script.1912254/

@margroloc - Thanks for clarifying that your problems were solved by setting the Non Turbo Ratio to zero (0).

Are you using the Windows Task Scheduler for this? Do you remember if you moved the folder that contains ThrottleStop.exe? The ThrottleStop.INI configuration file in this folder keeps track of the icon ID information. If this file and folder gets moved to a different folder on your hard drive, Windows will change the permissions on this file and that might be blocking ThrottleStop from saving information correctly. To try and fix this, exit ThrottleStop.exe, go into the ThrottleStop folder and delete the ThrottleStop.INI configuration file. The next time you run ThrottleStop, it will be forced to create a new ThrottleStop.INI configuration file with the proper permissions. I am using Windows 10 and I am not having this problem. I will try to come up with a fix for the problem you are having.

If you are having problems, post some screenshots and let me know what doesn't work.

 

Nothing works for me in the newest version, multiplier cpu speed etc..
I went back to 6.0 and worked like charm. Strange tho, ill try to 'reinstall'

 

ThrottleStop 8.20 works on server 2012r2, but the notification icons in the taskbar fail to be fixed when I select ''show icons and notifications''. whatever I select, upon reboot, windows put back ''show only notifications''.

okay I used this program to reset the notifications and now it works.
http://www.sevenforums.com/attachme...reset-reset_notification_area_icons_cache.bat

 

I have something interesting to report on skylake.

I adjusted my CPU core/cache undervolt to -171.9 and it seems fairly stable so I moved onto system agent & iGPU.

To do testing I ran cpu burner (7 threads) & furmark (400x300) at the same time.
First I offset sys agent by -100mV. Nothing happened, power consumption/temps/performance didn't change.
I left sys agent at -100, and then offset iGPU by -100.
Immediately power consumption (of iGPU alone) dropped from a peak of 15.9W to 13W.
(CPU package also drops by the same amount in all of these tests and IA core didn't budge so I'm omitting both)
No crashing, so I kept moving the iGPU slider further, but power consumption stayed at 13W.

Eventually I ended up with -800mV "stable" on the iGPU (sounds ridiculous right?) and it behaved exactly as if I had undervolted by -100. Weird.
So I reset the iGPU back to -0mV, power consumption reset to 15.9W, tried again and same result.

I then individually undervolted system agent and iGPU again and nothing happened. Only when both were undervolted together did the iGPU power consumption actually drop, and CPU power use was never affected at all.

So, it seems that for the iGPU portion of the chip
- intel GPU undervolt is ignored if alone
- system agent undervolt is ignored if alone
- only when intel GPU & system agent are both undervolted together does iGPU voltage actually change, but by the lesser undervolt of the two.

I confirmed this in aida64's power usage graphs, gpu-z's graph, qualitatively w/ my laptop fans' rpm pattern, and when my comp BSOD'd after I set both sys agent & iGPU to -125mV to take some screenshots (but was stable with both at -100mV)

Is this behavior documented already? I may have missed it.
Does anyone know what analog I/O is for on skylake?

Throttlestop 8.2

EDIT: -100mV on both iGPU & sys agent turned out to not be stable for me, got into and escaped from a BSOD boot loop. Scary when that happens.