The ThrottleStop Guide

That is great news because I was out of ideas.

Most recent laptops enable Speed Shift automatically. It is not going to hurt anything to have the Speed Shift box in the TPL window checked and it might cause problems like you were having if it is not checked. Checking this box helps ensure that the Speed Shift Min and Max values are being sent to the CPU.

When overclocking, I am not sure if Windows can handle Speed Shift Max correctly or consistently. I always check the TPL - Speed Shift box. That tells ThrottleStop to keep an eye on things.

It is OK if you want Windows to be in charge of Speed Shift EPP and not ThrottleStop. I recommend letting Windows handle EPP to avoid any fights over the EPP register. You can leave the Speed Shift EPP box on the main screen unchecked but I would still check the Speed Shift box in the TPL window.

 

Thanks unclewebb!

 

I don't know if this is a BIOS bug or throttlestop bug, but when I adjust the voltage offset for GPU unslice in the BIOS, throttlestop does not pick up on it compared to core, cache, GPU, and uncore voltages, which it all picks up fine. Is the BIOS not properly setting the igpu unslice voltage, or is throttlestop not reading it correctly?

 

@Raidriar - If you make any changes in the BIOS to voltages, etc., you will need to delete the ThrottleStop.INI configuration file before running ThrottleStop. If you do not do this, ThrottleStop will ignore any BIOS changes and will use whatever settings were previously saved to the ThrottleStop.INI configuration file.

Do you have Intel XTU installed? Can we blame XTU?

I cannot remember testing this in recent memory. If my motherboard BIOS lets me adjust the iGPU Unslice offset voltage, I will see if I can prove if ThrottleStop is reading this correctly or not. It should be.

 

I always delete the ini before making BIOS voltage changes. I do not have XTU installed, as there is really no point since I have an unlocked BIOS. Razer BIOS is known to be buggy, so it would not surprise me if it looks like it is setting the igpu unslice voltage, but not actually doing it. I just found it weird this is the one value throttlestop doesn't detect.

 

Run HWiNFO after you boot up and double check the GT Slice and Unslice Voltage Offsets.



My Asus desktop motherboard BIOS only has a single entry for adjusting the CPU Graphics voltage.



The HWiNFO screenshot was taken with the BIOS set to -0.125 V. This BIOS option does work and it does reduce the iGPU voltage and power consumption but nothing shows up in HWiNFO or ThrottleStop for Voltage Offset. I also manually checked the register that contains the offset information and it was all zeros. There was nothing hiding in that register.

I ran a simple GPU-Z render test and watched the Kill-a-Watt meter for power consumption. This confirmed that the BIOS Graphics undervolt was working. On this desktop board, the BIOS CPU Graphics undervolt is separate from the iGPU undervolt that ThrottleStop lets you set. If I enter a GPU and iGPU Unslice undervolt into ThrottleStop, this undervolt seems to be applied in addition to any BIOS undervolt.

To make things more interesting, a -125 mV GPU undervolt in the BIOS is not the same as a -125 mV GPU / iGPU Unslice undervolt in ThrottleStop. Using ThrottleStop to undervolt the Intel GPU is more productive. It lowers the voltage and power consumption more compared to doing this in the BIOS.

For a final test, I used a separate tool to manually set a GPU / iGPU Unslice undervolt. I deleted the ThrottleStop.INI configuration file and ran ThrottleStop. It had no problem detecting this undervolt. The values showed up in the FIVR monitoring table and HWiNFO was also reading both the Slice and Unslice GPU voltages correctly. They both get a gold star. You should be able to use either tool to see if your Razer BIOS is setting the Unslice voltage correctly.

If you use ThrottleStop to make any voltage changes, you will need to restart HWiNFO so it updates its Voltage Offset information. The ThrottleStop FIVR monitoring table updates the offset voltages automatically every second.

 

I can confirm HWinfo shows the same voltages as throttlestop, so I'm going with razer's BIOS being buggy and not applying the unslice voltage offset like its supposed to. Was hoping to use a software-free approach to undervolting, but oh well. Thanks for helping me sort this out!

 

Well, after a shutdown it stopped working. The way i "unlocked" it before doesn´t work, the only way now to get it right again is to check "disable and lock turbo power limits" on the FIVR window.

 

That is why I always recommend checking that magic box.
I seem to recall hiding some code in there for enthusiasts that like to overclock.

You can also check the MMIO Lock option in the TPL window. I think checking that box accomplishes the same thing as checking the Disable and Lock box.

 

Yeah, the MMIO Lock option in the TPL window appeared enabled by itself after i checked "disable and lock turbo power limits".

 

Good news. I was not sure if ThrottleStop was going to work correctly on Intel's new 12th Gen desktop CPUs. Surprisingly, ThrottleStop 9.4.2 starts up and it looks like a lot of things actually work.

The monitoring results look correct. It shows the P cores of this 12600K are all running steady at the 50 multiplier and the E cores are all running with the 40 multiplier.

Thanks to GerKNG on TechPowerUp for doing some testing for me.

 

Got some questions - sorry if I am repeating but didn't find anything yet:

As the Author let me know pls- what is proper with TURN ON or TURN OFF to keep -(on main windows program screen ) - green or red in taskbar after it for your program?!

and in FIVR page - for Cache needs to be increased IccMax? You told me for CPU - yes to the Max.

and from screenshot some numbered:

1. after running some test - thermal sometimes Red,
VR current exists in core
EDP other exists in core and in ring

anything needs to do with it?
2. in TPL page - is it ok or increase anything?

3. by default - it is Disable control for 11800H
anything needs to do with it?

4. If on main screen SpeedShift I read you advice to check in, but here in TPL it is not?!

5. in TS Bench window-this numbers - higher is better or what is the difference? meaning?

 

Turn On / Turn Off controls the Clock Mod feature and the Set Multiplier feature. Most recent computers do not use Clock Mod throttling and the Set Multiplier feature is not available if Speed Shift is enabled. That means Turn On and Turn Off does not matter.

Your screenshot shows that the maximum temperature of one of the cores reached 100°C. THERMAL in red means your CPU is thermal throttling. It is forced to slow down to protect against any long term damage.

That means your voltage regulators are having a problem delivering enough current to your CPU. When this is red, the CPU is forced to slow down. Intel says the 11800H is a 45W processor. Your are trying to run it at 90W. Guess what? It looks like the manufacturer never planned for someone running their CPU at 100% more power consumption compared to the Intel rated TDP.

https://ark.intel.com/content/www/u...1800h-processor-24m-cache-up-to-4-60-ghz.html

You cannot easily replace the voltage regulators on the motherboard. The only way to avoid VR Current throttling is to avoid stress testing your computer at 90W. It was not designed for this kind of use.

EDP stands for Electrical Design Point. To try to fix this type of throttling, set IccMax for the core and the cache to the maximum, 255.75 and in the TPL window set Power Limit 4 to 0 or try setting Power Limit 4 to the maximum, 1023. This might not solve your EDP throttling problem. Your laptop was only designed to handle so much abuse. Running a 45W CPU at 90W and 100°C is more performance than your computer was designed to deliver.

My advice for Speed Shift is the opposite of what you read. I recommend checking the Speed Shift box in the TPL window.

On the main screen, you only need to check the Speed Shift EPP box if Windows cannot manage EPP. On most recent computers, Windows 10 or Windows 11 can manage Speed Shift EPP. If Windows can manage Speed Shift EPP, you do not need to check the Speed Shift EPP box in ThrottleStop.

To test this, clear the Speed Shift EPP box. Open the FIVR window and have a look at the monitoring table. What Speed Shift EPP value is the CPU using? When you change from the Windows High Performance power plan to the Windows Balanced power plan, you should see the Speed Shift EPP value in the FIVR monitoring table change. Does this happen on your computer? When you change back to the Windows High Performance power plan does the EPP value change back to 0? It should. This test will confirm if Windows is capable of managing the EPP variable.

The value at the top of the TS Bench screen is like a stop watch. It is showing you how many seconds it takes to complete a test. If you are at the drag strip and it takes 15 seconds for a car to travel a quarter of a mile and the next car goes the same distance in only 10 seconds then it is pretty obvious that the 10 second car is a much faster car compared to the 15 second car. The less time it takes to complete a task the better.

Your computer has 8 cores and 16 threads. When the TS Bench is set to 16 threads, the problem it is trying to calculate is broken up into 16 equal sized chunks. This is usually the most efficient way to calculate this problem on an 8 core / 16 thread CPU. If you break the same problem up into 20 threads but your CPU can only process 16 threads at a time, this is not as efficient. The operating system has to swap 20 tasks into and out of the CPU when there are only 16 threads available.

Your TS Bench results confirm that breaking a problem up into too many little pieces is not a good idea. There is more overhead swapping tasks and threads. When set to 20 Threads, the benchmark takes longer to complete. Your results show that the amount of time it takes to complete the calculation has increased. More time to complete a task is just as bad as a car at the drag strip that takes more time to drive down the track.

I do not like to see a green or red T in the system tray. In the Options window, I turn Notification Area Icon off.

I like looking at the CPU temperature and CPU power consumption. That is useful information.

 

Thank you very much!!!
Tried to do all steps-in TPL windows checked SpeedShift
Looks like with Powerlimit 1023 - 1023 EDP is gone.
ok
And I think questions in yellow - nothing to change for OC there?

PS. Changing Cache ratio is useless for this 11800H CPU in FIVR section?

 

It is Sunday so I feel like a football coach drawing up a play.

The Turbo Power Limits section at the top is constantly monitoring what the MSR PL1 and PL2 power limits are currently set to. It also reports what the MMIO PL1 and PL2 power limits are currently set to. ThrottleStop will immediately show if any software on your computer has changed either of these power limits.

Your screenshot shows that the MSR power limit register is set to 200W for both PL1 and PL2 and the time limit is set to 56 seconds. The Power Limit Control section allows you to send different power limit values to the MSR power limit register. There are two reasons why a user might need to do this.

Reason #1 - If the BIOS does not let you set custom MSR power limits then you can use ThrottleStop to do this.

Reason #2 - If Windows or some software on your computer is randomly changing the MSR power limit register, you can use ThrottleStop to monitor and automatically correct any changes.

If you have either of these problems, clear the Disable Control check box. When this box is clear, ThrottleStop will send the power values in the Power Limit Control box to the CPU MSR power limit register. It will also constantly check and maintain these power limit values. If some bad software lowers your MSR power limit to the 45W TDP, ThrottleStop will quickly detect this problem and change the MSR power limit register back to 200W like you have requested.

When the Disable Control box is checked, ThrottleStop will ignore any changes to the MSR power limit register. Checking that box is telling ThrottleStop that you do not need ThrottleStop to manage this register. I have the Disable Control box checked on my desktop computer. I have set the power limits in the BIOS and there are no issues with these limits ever randomly changing.

If you can set both power limits in the BIOS to 200W and you do not have any software on your computer running amok and randomly setting these power limits to something else, then you do not need ThrottleStop to constantly monitor and change the power limit register. For you, checking Disable Control is best. It tells ThrottleStop not to waste its time and not to waste any CPU cycles checking a register that never changes. I like adding features like this to ThrottleStop so it is as efficient as possible. You can turn off features that you do not need. There is a reason why ThrottleStop uses 1/10th the CPU and memory resources compared to Intel XTU.

The MMIO power limits are a secondary set of turbo power limits. The CPU constantly compares the MSR and MMIO power limits and uses the lowest power limit value it finds. Your screenshot shows MSR PL1 is set to 200W but the MMIO PL1 is only set to 92W. That means your CPU will start to throttle at 92W. If you want your CPU to throttle at 92W, set the MSR PL1 power limit in the BIOS to 92W. Setting MSR PL1 to 200W does not accomplish anything if the MMIO PL1 is set to 92W.

In the name of efficiency, I prefer to check the MMIO Lock box. That does two things. It eliminates the 92W power limit and it locks the MMIO power limit register so no other software on your computer can make any changes to it. On many recent laptops, the MMIO power limit is more likely to be randomly changed. When the MMIO register is locked, ThrottleStop does not have to waste its time monitoring and adjusting this register. I highly recommend checking this box. No CPU needs two separate sets of power limits. When the MMIO power limits are locked out, the MSR power limits will still work just fine. The MSR power limits are enough to control the CPU.



At the bottom of your screen, the PP0 Power Limit is not checked so neither it nor the PP0 Turbo Time Limit are being used. Leave this as is and leave the time limit at its default value, 0.0010 seconds. My 10th Gen desktop does not use this power limit and I doubt an 11th Gen mobile CPU uses this either.

There is no reason to check anything in ThrottleStop if it is not being used or not causing a problem. ThrottleStop is a generic tool. Only use what you need.

 

Wow - that`s a real manual and education stream-writing lesson! Thanks a lot.

I did recommendation LOCK MMIO - so now it looks like this:
And now CPU will have instead of 92W->200W limits - which could be slightly better? (Keeping in mind limited cooling with this CPU anyway?)


PS. and about changing Cache ratio is useless for this 11800H CPU in FIVR section?
PS2. I have desktop with i9-10900K - and it setup and OC in BIOS as Fixed voltage. Is there any sense to try use over it plus Throttlestop and higher layer to OC? Offset wouldn't work with BIOS fixed?

 

The 200W PL1 power limit looks good. No chance an 11800H will ever be able to maintain this much power consumption without overheating or in your laptop, triggering VR CURRENT throttling to glow red.

An H CPU is not a fully unlocked K series CPU. You should be able to use ThrottleStop to lower the cache ratio but you probably cannot use ThrottleStop to overclock the cache ratio. I know the 11800H is partially unlocked. You can go +400 MHz on the core. Maybe you can also overclock the cache some when you are overclocking the core. Not sure. Do some testing to find out what is possible.

I have a very similar 10850K. In the Asus bios, I enabled SVID support. This allows ThrottleStop to control the voltage based on the VID of the processor. I found that the VID voltage table set by Intel for this processor closely tracks the voltage that the processor needs. That makes it easy to dial in an offset voltage that works well at many different CPU speeds.

If you have locked your 10900K to a single speed and you are happy with this then it is OK to lock the CPU voltage in the bios. On a desktop board, when you are running a fixed voltage, the VID voltage is usually ignored. That means trying to do an offset voltage when the board is set to a fixed voltage is probably not going to work.

It should be easy to test this. Run a consistent stress test like the TS Bench or Cinebench and play around with the offset voltage sliders while the CPU is loaded. If your computer crashes then I guess that proves that the offset voltage slider must be working. You can also watch CPU temperature and power consumption for any changes.

What voltage and speed are you running your 10900K at? My 10850K has been an enjoyable CPU. After you add lots of voltage, it competes well with most 10900K.

https://valid.x86.fr/yu1kle

Don't believe the MHz. I was playing around with ThrottleStop to see if I could trick the CPU-Z validation algorithm. I succeeded.

Those scores are very competitive with most 10900K. It was a great CPU until the 12900K arrived. Now 10th Gen single core scores look kind of pathetic in the CPU-Z benchmark test compared to the beast that Intel just released.

 

I noticed today my Throttlestop (9.4.2 beta) isn't showing entering any C States below 1 (shows 0 for all values) even tho limit is set to C10 - is there some option I have set somewhere wrong that would be causing this?

 

Did you ever use ThrottleStop to disable your C states?

Check the C States - AC box, select the On radio button and press Apply and see if that gets your C states working.



If you are still having problems, do you remember installing any recent BIOS updates?

Open Power Options and try pressing the Restore plan defaults button.



There are 101 things that can interfere with the C states working correctly. Some manufacturers release updates that deliberately disable the C states. If you do not know when they stopped working, it is difficult to troubleshoot what might have changed.

 

Thank you about desktop - will look it trough, but your is faster!?!?
My silicon voltage is 1.35V and under load falls till 1.29V something (have LLC - Turbo to keep it not lower) and if lower is freezing with OC CPU 51x. ( I think my mb Gigabyte meeh and slow DRAM are involved.)

Now my task to make the most slow profile for laptop: I have one as MAX OC and one even powering a laptop from electricity I tried to make it slower - so chose Battery mode and Turbo ratio limits pull till down possible 23?!
Get Speedshift EPP till 153. Cache ratio 8 now - getting CPU frequency 0,8-1,2 GHz and under some CPU load - trying to keep lower Temperatures and less impactful on GPU under load and fan runs slower!
Surprised that still get quite high CPU temperature around 55-57C with 3% utilization from Windows Task Manager (49-51C during the rest if I am not wrong), and in OC Performance mode under same load - 60-63 and it already affects -> +GPU temp -> +Fans... At least tuned fans and temp - after this downgrade speed are bearable.

(on screenshot to look and compare - GPU is under heavy load and FAN RPM for big 17 laptop chassis tuned down but still CPU could he colder!?).

 

So, I had to do a bios reset and forgot to disable the bios virtualization related settings. Obviously, voltage control in TS got locked. The thing is, even after disabling all virtualization features on the bios and windows, and deleting TS ini file, I still have voltage control locked. Any ideas?

Edit: forgot to mention that undervolting through my laptop's control center works fine.

Edit: Got voltage control back. Not really sure why, I suspect it came back when I switched from mshybrid to dgpu. Or maybe when I cycled through all my laptop's control center profiles to setup in each one my desired undervolt.

 

Here is a nasty trick to play on consumers. My friend GerKNG who is helping me with updating ThrottleStop for 12th Gen CPUs has bought two different motherboards from two different manufacturers and both of them are enabling BD PROCHOT. They are also both setting the lock bit to prevent BD PROCHOT from being disabled. Manufacturers will likely start doing this to laptops at some point.

More throttling on the horizon. Users will be forced to do some UEFI bios mods to get around this limitation.

 

C states enabled in BIOS, "restore plan defaults" greyed out - C states totally broken, don't get it?

 

I don't get it either. Not sure why "Restore plan defaults" would be greyed out.

Try running this command,

Code:

powercfg -qh >C:\power.txt

This will create a file called power.txt and it will place it in your main C directory. There might be something hiding in your power plan that is not set correctly. Attach that file to your next post or copy and paste the data to www.pastebin.com so I can have a look. I will compare the values in your power plan to what is supposed to be there.

I think last time I helped a user with a similar problem it was the idle promote threshold setting that was preventing the CPU from using any of the C states. Maybe I will get lucky again and find something hiding in your power plan info.

Code:

    Power Setting GUID: 7b224883-b3cc-4d79-819f-8374152cbe7c  (Processor idle promote threshold)
      GUID Alias: IDLEPROMOTE
      Minimum Possible Setting: 0x00000000
      Maximum Possible Setting: 0x00000064
      Possible Settings increment: 0x00000001
      Possible Settings units: %
    Current AC Power Setting Index: 0x0000003c
    Current DC Power Setting Index: 0x00000028

Some manufacturers seem to disable the C states deliberately. This trick prevents the CPU from using the maximum turbo multipliers. It is not a good idea to do this to a laptop.

 

https://pastebin.com/PDt1QU2u

 

@amihail91
The power plan you are using is not one of the default Windows power plans. Have you tried using ThrottleStop to switch to the High Performance power plan? Does the Restore plan defaults button work then? Do the C states work when using the High Performance power plan?

I am not sure who created the Ultimate Performance Quiet power plan you are using but that might be the problem. Do you remember where this power plan came from?

I will go do a comparison to see if anything is obviously not right.

Edit - I do not see anything obvious in your power plan that would prevent the C states from being used. I do not like the EPP values this power plan uses or the minimum processor state values but these settings should not make any difference to C states.

Can you post a screenshot of ThrottleStop with the C States window fully open?

 

High Performance reset to default

 

I thought all of your C states were disabled. The core C states are working OK. Do the core C states work when using your Ultimate profile?

One possible reason your package C states are not being used is because there is too big of a load on the CPU. If your computer is spending 12.7% of its time in the C0 state then it is not even close to idle.



Have a look in the Task Manager at the details tab and find out what is running in the background. My cores can average 99% of their time in the core C7 state when my computer is idle. That allows the CPU package to idle down and enter some of the package C states.



Running a TS Bench 1 Thread test is only keeping one thread and one core busy. That is enough load to prevent the CPU package from using any of the package C states. One fully active core means the package is also fully active.

 

There's likely some deeper issue that can only be solved by a reinstall here - that screenshot is "idle" with 0 programs open in the foreground ... won't go below C0 anymore.

EDIT: I notice that when killing all Razer Synapse services I can get down to C3 - this is new behaviour for this machine though and I've had it nearly 2 years.

 

Too much useless crap (Razer bloatware) running in the background will prevent the CPU from being able to use any of the package C states.

You have to keep a close eye on things. I am hyper sensitive to wasted CPU cycles. I keep a close eye on the C states data in ThrottleStop because I know it is the most accurate way to determine if something, somewhere is running in the background. My Windows install averages 99% in core C7 when I am idle at the desktop. If I shut down Chrome, it goes a tiny bit higher. Same with the C0 data on the main screen. That is typically 0.1% when idle or a hair less when Chrome is shut down. It is usually so low that I had to add another digit to the C0% data that ThrottleStop reports so now I can see when it goes below 0.1%.



OCD is a wonderful trait when you are hell bent on writing efficient software.

I would rather be poked in the eye with a pointed stick than have to reinstall Windows. Every time you install anything on your computer, you have to keep an eye on any changes in C state activity. If you know that you did not install anything recently and all of a sudden there is a significant change, right away you will know that something is going on and you can track it down. The Task Manager Details tab is always a good place to start.

Process Explorer from SysInternals is an even better tool for tracking down bad or useless stuff.
https://docs.microsoft.com/en-us/sysinternals/downloads/process-explorer

O&O Shutup10 is also useful so you can help prevent Microsoft from sending your hard drive contents to Redmond.
https://www.oo-software.com/en/shutup10

 

What I'm saying is this is new behaviour as of very recent - perhaps in a new version of Synapse because I've had this machine 2 years and modded it to get to at least C7 while just sitting on the desktop and it doesn't do that anymore.

EDIT: How about we go one deeper and see what the Synapse process is up to - why would it be blasting my registry trying to changed EnableDhcp to 1 every second?

 

New and improved!

I try to avoid any manufacturer's software. Window's Updates are enough of a gamble.

Do you really need any apps from Razer? My computers run fine without poorly written apps sucking up CPU cycles. Get rid of what you do not need and enjoy a smoother running computer.

 

Razer laptops fans won't even work without Synapse open ...

 

I want to ask about right part - is there anything needs to be checked?
Undemotions !?

 

Checking or unchecking the Demotion or Undemotion boxes makes very little difference to anything.

I like to clear the Demotion boxes and I check all of the Undemotion boxes.



This helps give me a steady 50X multiplier when idle.

You can go through them one by one or check and uncheck two or three of these options at a time. Press the Apply button each time and see if it makes any difference. I am always plugged in so a few milliwatts one way or the other does not make any difference to me.

 

For desktop idling and of course some background tasks from manufacturers (for example RGB lights) - what is your opinion about good C0?!
Around around 1-1,5 acceptable?

 

My opinion for idle C0% is as low as possible. If you need to run programs for fan control or if you need to use programs for RGB lighting, you get to decide how necessary and how important these programs are to you. Some computers have the fan going full speed trying to keep the CPU cool because of the bloatware running in the background.

I grew up in an era when computers had single core CPUs and ran at a blistering 7 MHz or less. That is why ThrottleStop is so efficient. Many programmers growing up with today's hardware do not know or care about writing efficient code. Why waste time coding when you know Intel and AMD will add a few more cores with each new generation. Perhaps the real purpose of Intel's new E - efficiency cores is so bloatware will have a place to run without interfering with the P - performance cores.

 

just need approval of the Idea ;-) - making balance profile and medium turbo limits in FIVR will make CPU wattage usage go down and temperatures?

Didn't tried yet - reviews give idea that Balanced mode and Extreme mode settings do the same for (MSI) laptops. (for me they looks like mostly fan settings).
So may be instead use hot OC CPU 85-98C in games and noise fast working fans anyway have a thermal limits, use this 35x?40x? medium (slowdown) CPU,
which would be still enough in games!?
And leave most of work for GPU?! (sure undervolted etc in MSI Afterburner) but as the Idea is it worth and proper direction from anybody experience?

PS. Dynamic Boost on or off - next switch option to reconsider. It takes Wattage->Temperature in one place(CPU-what is good!) but brings it to another (GPU) ;-(

 

v2. Update
did some tests and completely lost:
Idea was take down wattage(->temp) from 11800 CPU and not give extra to GPU (and possibly not harm CPU) performance, +fans slower lower benefits.

So did with from OC 46x + IccMax 225 OC CPU --> 42x where IccMax 225, -->40x IccMax 105 and HWinfo show me NO difference in Wattage usage! During Cinebench23 = 76-88W.

And crazy inexplicable stuff for me - that Cinebench 23 shows that max results 13020 with 40x IccMax 105 settings.... for example and all others 200 less!?!
At All settings 40-42-46x CPU throttled till 38x approx. When I choose battery 20-23x and etc then only I got 25W package and twice predictable slower in C23.

What is a golden middle!? What is better to use for games and Thermals Temps...

 

I am not able to follow your thoughts 100%, but what you should do to get a decent foundation for your experiments:
Run the system at stock settings, have a benchmark run on repeat and write down at which settings the system settles.
You want to make sure that you get the following data points, preferably via a HWInfo64 log:
- frequency it throttles down to
- package power during the benchmark, once it has reached that stable frequency
- temperature at that stable frequency
- limiting flags during the benchmark

The reason for that is rather simple:
If your device needs to throttle down to 3.8GHz to reach a "safe" temperature, you will not get anywhere by reducing the maximum frequency from 4.6GHz to 4.2GHz, as your device will need to throttle down further.

Once you have those data points, you can start experimenting with how to most efficiently reduce the temperature, as that is likely the reason for your throttling.

 

I would not touch IccMax. Set the core and cache IccMax to 255.75 so it does not cause throttling. You are playing around with so many different variables, all at the same time, that it is impossible to know what limit is in command of your CPU.

Keep things simple. If you want less CPU heat, open the TPL window and reduce the turbo power limits. Less power equals less heat. Check both Clamp options so your power limit requests are enforced. ThrottleStop gets another gold star for providing access to the Clamp feature. Intel XTU does not think being able to toggle Clamp is important.

 

@unclewebb what are the chances of disable E cores with the 12th gen with TS? in anandtech's review showing they had to disable it in the bios, unsure if it can be done via software side.

 

thank you.
So first unDisable Control:
what numbers do you suggest to input? I see 2 options for long and short
Sync MMIO - don't touch?
Turbo time limit - any changes?
And use LOCK after putting numbers?

 

No chance. This has to be done by the BIOS before Windows boots up.

After Windows has started, you could use the Task Manager Processor Affinity tool to prevent individual tasks from using the E cores. Software like Process Lasso might make this task easier.

Here is how to turn my 10850K into a low power CPU with a 50W power limit. Both PL1 and PL2 are set to 50W.



My computer does not use the MMIO turbo power limits. They are already set to 0 by the BIOS. If your computer uses these limits then I would check the MMIO Lock box to prevent these limits from being used. Intel CPUs do not need multiple sets of power limits, all fighting over control of the CPU.

The turbo time limit does not matter when PL1 and PL2 are set to the same value. I always use 28 seconds because that was the value that Intel used on most of their CPUs for many years. Old habits are hard to break. The default value for a 10850K is actually 56 seconds. Does it make any difference if a CPU spends 28 seconds at the 50W PL2 power limit before switching to the 50W PL1 limit or if it spends 56 seconds at the PL2 power limit before switching to the 50W PL1 limit? When both power limits are the same, it makes no difference.

You only need to use the Lock option in the Power Limit Control section if some other software on your computer is changing the MSR power limits. The values at the top in the Turbo Power Limits section shows in real time what the MSR power limits are set to in the CPU. If this data consistently shows your requested PL1 and PL2 power limit values then there is no need to lock this register.

@ole!!! - Here is a good trick I learned recently. If you change the process affinity of explorer.exe, any task you start up after that will also be limited to that subset of cores and threads. When I start ThrottleStop after doing this, it can no longer read any data from the last 4 threads of the CPU because it gets the same affinity as I gave to explorer.exe



You should be able to use this trick so when you start a game after doing this, it will be limited to only the P cores. Every new task / thread a game starts should also be limited to the P cores.

 

i'll give that a try, but it might be a window 10/11 thing. i am still on server 2012, which is win8.

 

Thanks - and I see "coming soon in this windows" TPK Window - when I tried to make it different for High performance and Battery mode profile.
It is in work now?

>Here is how to turn my 10850K into a low power CPU >with a 50W power limit. Both PL1 and PL2 are set to >50W.

 

Hi!
I was using this feature to automatically lower my refresh rate when on battery

 

New XTU version came today.

With new features, like : "Decoupled core and cache voltage controls."

 

Deleted.

 

I updated my ThrottleStop to the latest version and now I can't get my Lenovo x12 w/ an i7-1180G7 to idle in deeper sleep states. Previously at idle it would only be pulling .5-1 watt. Now I cant get it below 3-4 watts and thats using TPL limits clamped. Setting my TPL limits to 1-2 watts wont even let it idle its just causes massive stutters. I used to be able to leave my TPL 1 and TPL 2 at 15 watts for emulation and gaming and it would still idle .5-1 watts. Everything was working great and I was getting exceptional battery life until I updated to 9.4.2? It seems to be stuck in C7. Can anyone help me troubleshoot this?