The ThrottleStop Guide

Just popping by to note how ThrottleStop 8.40 expired today and that I found myself having to move to the Obsidian 8.48 version, simply due to being able to use the program and not its newer features that target Skylake and newer. However, this specific version seems to have DPI issues when ran on a system that has anything other than 100% scaling. Changing DPI settings in the .exe's compatibility tab changes nothing. I should note that this didn't happen with 8.40.

Screenshot for reference: http://i.imgur.com/F9hmPTv.png



I used to be able to have all threads visible without any scrolling bars, vertical or horizontal, same for TDP Throttle not clipping or any other UI element. This is observed at 125% scaling, haven't tested at other scaling options since this is the exact setting I've been using for years without any issue.

 

Yes , anything related to intel xtu will cause a conflict so.. remove dragon center & then restart.... after that set your settings on throttlestop and it will stick

 

The ThrottleStop voltage options will be grayed out if voltage adjustment is either locked by the bios or locked by the CPU itself. I have never owned or had access to any Xeon processors and I cannot remember any Xeon E5-2683 v4 feedback being posted in this forum so I have no way to determine if this problem is CPU related or bios related.

Thanks for posting that info. The recommended VCCIN voltage when using PowerCut was just a number I pulled out of my hat. The default VCCIN I chose seemed to be close to the default VCCIN that my 4700MQ uses so I thought 1.75 V would be a good place to start. No idea why this voltage did not work for you but other voltages did. This feature is taking advantage of a bug within the CPU so anything is possible.

It is always worth under volting, especially on the low power U CPUs. This line of Intel CPUs is designed to throttle and slow down based mostly on power consumption. Reducing your voltage, reduces power consumption and that will let your CPU run faster, longer before throttling. In some cases, reducing voltage can completely eliminate throttling for most uses. Under volting is always trial and error. CPUs are unique so no one in a forum has any magic numbers for your specific CPU. Always best to do your own testing on your own CPU.

It depends on the application you are running. If you were running a high stress application like Prime95, reducing voltage will allow the CPU to run faster but it is still going to be throttling based on power consumption. With or without the under volt, the CPU will still be sitting there, throttling along at its rated 15 Watt TDP level. Same power consumption = same temperatures. Some laptop models reduce their CPU fan speed depending on temperatures so that is another reason why your question is impossible to answer. Go play some games and do some testing and let us know what you find out.

ThrottleStop has to be running on your system, minimized to the system tray, so it can continuously manage your voltage. Check the voltages displayed in the ThrottleStop FIVR monitoring table. Some monitoring apps cannot be trusted because they do not update themselves after ThrottleStop has changed the CPU voltage. The monitoring data in TS is continuously updated.

If you have moved your ThrottleStop folder and its contents, it is best to delete the ThrottleStop.INI configuration file so ThrottleStop can create a new config file with the proper read write file permissions. Windows has a nasty habit where it can change these permissions when you move a file. This can prevent ThrottleStop from saving any changes in settings.

As for starting ThrottleStop using the Task Scheduler, you can start from scratch and try using the guide I wrote.

http://forum.notebookreview.com/threads/the-throttlestop-guide.531329/page-514

Don't just look at the pictures. Read each step and decide exactly what you want ThrottleStop to do.

Thanks @tribaljet for your feedback. The next version will have a new option to control the monitoring table font to keep users happy.

 

Have you tried increasing the window size of TS by moving the cursor to edge of the window and increase the size and see if it helps.

 

@unclewebb Certainly. I'm still a firm supporter of ThrottleStop over any and every other contender and highly recommend it to all eligible users. That said, even though this issue might be a UI matter, it ought to impact anyone with non default DPI settings.

EDIT: I'm currently unsure what changed in that regard from 8.40 to 8.48 but 8.40 did behave as DPI-Aware, so monitoring table adjustments will be indeed welcome but perhaps having the previous DPI settings in place could also be considered, given 8.40 worked for default and non-default DPI settings.

ThrottleStop's window cannot be resized through window edges nor maximize controls. However, that does make me wonder if being able to manually adjust width and height would be another valid workaround.

 

I have been using TS to undervolt my XPS 15 for quite some time now and I can't seem to get OBSIDIAN working the same as 8.40 and earlier...

In 8.40 and earlier, I had TS start with windows via Task Scheduler however it was always hidden and running completely stealth. I never saw the program being opened, minimized or any notification area icons. Does anyone know what settings I need to apply to have it running like this again?

Btw, I never had to actually "Turn On" TS, just having TS in Monitoring mode was enough to apply the Core and Cache offset voltages

 

Yep. Did all those things. Read everything, and applied everything as i want it. Removed all the MSI softwares like dragon center, scm. Removed Throttlestop. Restarted my laptop. Installed Throttlestop in the program files of my main drive (haven't moved the folder at all), set my undervolts and saved it.

The undervolts stick if i restart my laptop. Here's how it looks after a restart:
However, if i completely shut down and start the laptop again, it gets reverted back to default:

Don't know what's wrong at this point.

 

Are you using windows 10? Maybe the hyberboot thingy causing some problems... I really don't know what else to say... I will tell you 2 possible solutions...

[1]- Have you tried to do this... (Win+X) and shutdown your computer from there? See if the voltage sticks or not

[2]- Have you tried to exit the throttlestop and then open again and see if it sticks the same voltage? If it sticks--> then shutdown your computer and open it again and see ...

 

Hello and thanks for your reply Could I be of any assistance? Could i test something that you will give to sort if this is BIOS or CPU related?

Cheers

 

Solution number 2 seems to have worked. It worked once, i'll have to try it a few more times. Why did that happen though? Any explanation?

 

Hmmm I see... the explaination is because you are choosing the option to save the voltage after the throttlestop [Successfully] exits but sometimes when you shutdown your computer... it kills throttlestop rather than exiting normally and due to that throttlestop will think that your system was unstable or crashed or BSOD or etc.. so it will reset to the default so..the 2nd solution worked for you was becasue your were telling throttlestop to save the voltage when throttlestop exited Successfully and it wroked for you because it was not being killed but it was exiting Successfully (by right clicking on the throttlestop icon and exit) because being killed causing throttlestop to think that your system was unstable so... it will reset the voltage automatically to its default

The reason is becasue you choosed this option [Save the voltage after exiting Throttlestop] and thats why this problem is happening due to windows stupid shutdown proccess

To prevent this... choose [Save voltage immediatly] but after you make sure that your choosen voltage is stable enough

Glad it worked for you and sorry for the long post I hope I didn't waste your time or something but I am trying to explain things clearly to avoid any confusion or misunderstanding

 

@tribaljet - At 100% or 125%, the table is drawn correctly on my Windows 10 laptop. The table width and individual table columns are both calculated correctly so there is no need for any scroll bars. On your computer the width of the table is slightly too wide, only by a pixel or two. This automatically causes a bottom scroll bar to be drawn which takes up space and then that wasted space causes a right side scroll bar to be needed too. When I was doing my testing, everything looked OK but I later figured out that I was using the original version of Windows 10. Microsoft has updated Windows 10 a few times since then so now for some people, in some countries, TS looks like a mess. It is not really a DPI problem though. It is more of a Microsoft makes random changes kind of problem and then programmers need to update their code to comply with and work around their changes.

I have a few ideas to make TS more compatible with more operating system versions and with more fonts around the world. Until I get this problem fixed up, I will send you a TS 8.40 version so you do not have to look at a messed up monitoring table. I will send you a message in a day or two. Your feedback is appreciated.

@antik - Read the included ReadMe file, towards the bottom. The part about cleaning the Windows icon cache. After that, follow my Task Scheduler guide.

http://forum.notebookreview.com/threads/the-throttlestop-guide.531329/page-514

@THEBOSS619 - Thanks. Great explanation. That saved me lots of typing.

@ribben - Without proper documentation from Intel, I have no way to determine if voltage adjustment is disabled because of your bios or CPU. I would suggest trying to find someone that is running your CPU model but on a different board from a different manufacturer and see if there is any change.

 

@unclewebb what is your stance on Process Lasso? I don't know if you are familiar with that program.

It does wonder combined with your program on lower-end CPU's, but I am unsure how those two might interact/overlap.

 

Thanks for the reply. I have no issues creating a task schedule, that's not the issue.
Is it possible to have TS run on boot without the program actually opening and me needing to minimize it after each boot? I had it running like this before I updated to OBSIDIAN

 

Yeah, Obsidian fails to go to the notifications bar for me too, and the window stays open, even after the "notification bar clean" thing.

 

Thank you so much @unclewebb you rock! I'm happy and glad that I helped by any means neccesary

 

I have heard of Process Lasso but have never needed to use it. As far as I know, I think it just varies the priority of your background tasks so Windows does not feel sluggish when your computer is full or nearly fully loaded. My solution for any sluggishness is to either throw more MHz or throw more cores at the problem. I avoid the sluggish Windows Balanced power profile. I also disable things like automatic Windows Updates and as much background junk as possible to keep the idle C0% low. There shouldn't be any overlap between Process Lasso and ThrottleStop so if you like it, use it.

Do you guys have the Task bar option checked on the main ThrottleStop screen?

Do you have the ThrottleStop - Start Minimized option checked?

Edit - If you are still having problems, start showing me lots of screenshots of how you have ThrottleStop and the Task Scheduler setup.

 

@unclewebb I tried unplugging the battery cable from a GT73VR 7RE (1070 based MSI titan) and I was getting very strange CPU core and ring throttling that did not appear on Throttlestop. It seemed like I could not exceed 140W total with both GPU and CPU loaded (GPU would not throttle but the CPU would). Throttlestop showed absolutely nothing wrong (besides the lower clocks), however HWinfo64 showed "Core 0 power limit exceeded: Yes", "Core 1 power limit exceeded, Core 2, Core 3, etc, and Ring power limit exceeded.

example: if GPU was drawing 120W, CPU would not draw more than 20W.

But nothing appeared in Throttlestop.
It clearly wasn't the current limit (ICCmax) as EDP other didn't appear.

Any ideas? (I'm trying to prevent whatever is causing the throttle when the battery cable is unplugged; 330W PSU in use).

 

@THEBOSS619 Thank you so much for the help. I actually needed that long explanation to be honest.

 

I just bumped into a very odd issue.
I have been using ThrottleStop for a while now.
My system is a Clevo laptop with a i7-4712MQ

So today I have been messing around with some tweaks here and there and all of a sudden, my CPU stays in boost mode the whole time.
(in my case that's multipler 35, so 3500Mhz).

Even when I reboot the system even the BIOS says the CPU runs on 3000MHz.

I have deleted the .ini file etc, but I still don't get why my CPU is even at 3000MHz at startup?
It almost looks like the whole multiplier turbo lock is being unlocked.
(which gives a pretty big performance boost, but my cpu is getting very hot)

 

The BIOS doesn't see boost clock speeds.

You can just adjust the multiplier if you want lower temps, or undervolt if you like going that direction

 

Well, oddly enough the BIOS does.
If I boot by default my CPU is on 3000Mhz, even in windows (without TS)

Could it be that the PowerCut option has to do with this (ucode 0x1D)?

 

@Falkentyne - When you are having a problem, post some screenshots so I can see what you are seeing. Include ThrottleStop and Limit Reasons if your CPU is throttling. I don't even know what CPU you have. There are power limits for the CPU package as well as power limits for the individual CPU cores. Some of these limits are locked and some of these limits ThrottleStop has no access to. Hard to make any recommendations with what you have shown me so far.

@b_force - How about a screenshot of ThrottleStop while running 4 or 8 threads of the TS Bench test? A 4712MQ should have a 35 multiplier available when it is overclocked and a single core is active. This usually drops down when more cores become active.

That is your CPU's default speed when not overclocking and 3 or 4 cores are active. If it used to run slower, it probably was not setup properly.

 

@unclewebb

That confuses me. The default speed of the 4712MQ is 2.3GHz, with a turbo frequency of 3.3GHz
http://ark.intel.com/products/78933/Intel-Core-i7-4712MQ-Processor-6M-Cache-up-to-3_30-GHz

So the reason why it's running around 3Ghz by default is a huge mystery to me.

 

@b_force - Intel CPUs are designed to always use as much turbo boost as possible. By design, the CPU wants to and should be running as fast as possible. If a CPU has something to do, getting a task done quickly is the most efficient way to do it. No more mysteries. Sounds like your CPU is running exactly how Intel designed it to run. Fast and furious!

 

@unclewebb
Let me put it this way. I have my laptop for around 4 years now. Running TS for the last half a year.
It has never been doing this, even not with TS

 

@b_force - If your bios and Windows are set up correctly, a 4712MQ should be running at 3000+ MHz without needing any help from ThrottleStop. There are lots of bios tweaks and various other tweaks that are recommended on the internet. Following some advice will make your CPU run slower so you have to be careful what advice you are following. There is lots of good advice to be found in this forum.

 

@unclewebb
Like I said, in all these years, it never did.
So could it be that the Power Cut option, maybe tweaked this setting?
Therefore my BIOS recognizes the CPU correctly?

I can also see why, because my CPU is now hitting the 90 degrees C...

 

The 4712MQ runs with Turbo Boost up to 3.0 GHz (for 4 active cores), 3.2 GHz (for 2 active cores) and 3.3 GHz (for 1 active core).

 

Yes I know, but like I said, it never did. Only in short peaks, than it always quickly throttled back to 2.3GHz again.
Even with TS. But it seems since I used the Power Cut option (which should work very well with Hashwell CPU's), this has changed.

 

When your system is idle, check multiplier in TS. For my 6700 HQ, it is typical for speeds to fluctuate widely, often in the 3000 range when idling, but if you look at C states, it is spending 80-90% of time in C6 or C7. This is very different from situation under load. Max for my processor with 8 cores is 3100 mhz - and if I load all 8 cores with TS bench, speed for all comes up to 3100 and stays there, and C0 % becomes 100%. Best, Joe

 

@unclewebb I'm sorry I've been very busy on the clevo forum dealing with an issue with the unlocked ( @Coolane mod) GTX 1070 and power limits.

I have a MSI GT73VR 7RE with a GTX 1070 (modded with pascal bios mod editor), and a 7820HK CPU.
The GT73VR 7RE comes with a 230W power adapter but I'm using the 330W instead. The 7RE and 7RF are hardware identical except for video card (GTX 1070 vs GTX 1080). Same Bioses and EC firmwares are used on both. I'm trying to find out if the board detects the 1070 card and is limiting the power draw to 230W (But this isn't what I posted above; see below):

This seems to be a Bios bug however. There are two of them:

The problem with the battery unplugged, throttlestop detects absolutely nothing at all. There is nothing under limit reasons. HWinfo detects "power limit exceeded" on the cores and ring bus but Throttlestop detects nothing. This seems to be some sort of EC firmware issue where power draw is hard limited to *130W* (GPU+CPU) if the battery is unplugged. And TS detects nothing. I can open the laptop and unplug the battery and show a picture later. But that's a lot of work (I'm disabled), but I can do that later.

The other bug seems to be ANOTHER Bios bug: If Power draw exceeds 230W, the CPU starts throttling under "Power Limit 2" and "EDP Other" in Limit Reasons, despite what is set in the Bios (200/250W power limits, ICCMax at 100A). This ONLY happens if power draw exceeds 230W. I've been trying to discuss it with the others.

what I posted above was throttling that TS did NOT pick up at all, if the battery is unplugged (Something seems to prevent the AC adapter from drawing more than 130W).

 

Hello again @unclewebb , i followed a different approach... I got access to a same DELL PowerEdge R730 machine but this time with an Xeon E5 2695 v3 (Hasswell) and everything works fine... So i think that limits the problem that is the CPU side the fact that i cannot set any voltage offset... I know that there is no documentation from intel out there but if you would like me to dump any msr or whatever from the Xeon E5-2683 v4 that may come handy to solve the support for this CPU, i would be more than happy to provide it to you

 

Hi, I've few dell notebooks to tests, e6530's, m2800's, m3800's and my e6540.
They all seem to have same throttling problem, especially them in which somebody changed low i5 for higher i7.
My configuration is i7-4800mq with amd 9870m and it was stock like that. Best fan has 6.5CFM.
I changed my fan cause it was freezing at medium load, it kept switching on and off 3 times per one second making some "wub wub wub" noise.
Also replaced thermalpads and thermal paste. Added cooling pad.
Now it's about 5C cooler and runs 5 minutes more without throttling at same settings.
I'm angry only cause to be honest it really cannot run any games created since 2013 without additional tricks, lowering resolution, cutting fps or using external software. Every game in standard setting will run max. 15 minutes and after that time GPU runs about 70°C and it throttles from 1300-900MHz to 300-150MHz 4 times in every second. Sound is also slowed down and very noisy.
When I run ThrottleStop in limit reasons I only have red GPU POWER after some time and nothing happens.
Does undervolting CPU with other options from TS will help that much or it will just give me another max 5C ?
I can run any additional test if that will help me

 

@b_force - Now I understand what you are talking about. A 4712MQ has a power rating of only 37 Watts. Intel designed this CPU to slow down and throttle to 2.3 GHz whenever it is running an app that exceeds this limit. PowerCut prevents the CPU from reporting the actual power consumption. This allows a CPU to run at full speed regardless of power consumption. You should be able to overclock too with no more throttling. PowerCut is a wonderful feature when your CPU supports it. You can thank @Dufus for PowerCut as well as the vast majority of ThrottleStop's other useful features.

@Falkentyne - When people are talking laptops, I always think about laptops from the good old days where you would just reach behind and slide out the battery. A 2 second procedure. I forgot that many modern laptops have batteries buried deep inside. Don't bother disassembling just to show me a screenshot.

I do not own a laptop with a 7th Gen processor so I have done zero hands on testing. HWiNFO is a very thorough program when it comes to monitoring so I am not too surprised that it is detecting something that ThrottleStop Limit Reasons is missing. Without relevant hardware or access to the full Intel documentation, I have taken ThrottleStop about as far as it can go. It's had a good run.

@ribben - Your Xeon is reporting that voltage adjustment is locked. Thanks for offering to do a MSR dump but once something like this is locked, it cannot be unlocked by ThrottleStop. If it can be unlocked, this would need to be done either by Intel or by the bios.

You should be angry. People pay a lot of money for laptops and some of them become completely useless because of throttling problems. These problems only get worse after a laptop gets older.

ThrottleStop is not designed to fix AMD GPU throttling problems. What you can try though is using ThrottleStop to slow you CPU down so it reduces power consumption and heat. You should also try under volting the CPU Core and CPU Cache. Reducing the maximum CPU Cache speed can also help without killing performance too much. The goal is to prevent GPU throttling from ever happening. For testing CPU speed, click on Disable Turbo. That will limit your maximum CPU speed to 2.7 GHz. When combined with a -50 mV voltage reduction, you might be able to reduce your peak temperatures by 10°C.

Dell packed a capable CPU and GPU into your laptop but it seems like the engineers never considered what would happen if a user tried to use both of them at their full rated speed at the same time.
Sad, very sad.

 

@unclewebb
We found the problem, and why throttlestop doesn't detect anything.
It's MSI cancer firmware. Something @Prema has fixed on Evoc systems.

Basically, on AC power, with battery removed, total power draw is limited to 60%.
This also applies if battery is lower than 30%. This throttling is not picked up on throttlestop but is picked up on HWinfo.

The other problem (which is an active discussion on the "Pascal bios editor" thread in the Clevo section) is MSI cancer firmware detecting whether a GTX 1070 or 1080 is installed, and limiting total system power to 230W if a 1070 is installed (7RE is shown in the Bios) or 330W if a 1080 is installed. Since there is a pascal bios editor now, we can exceed the MXM 1070 TDP of 115W, and match the desktop TDP of 151W to 170W. This requires an SPI Programmer because NVflash won't flash it.

The problem is, if the bios detects the 1070 and limits total system draw to 230w, going past 230W will cause "power limit 2 / EDP Other" throttling on the CPU and limit it to 45W. It can't throttle the GPU so it hits the CPU. basically, the MSI GT73VR 7RE and 7RF are identical. The Bioses are byte 100% identical, the EC firmwares are identical. The difference is: 1) the 7RE comes with a GTX 1070, and a 230W power supply. 2) the 7RF comes with a GTX 1080 and 330W PSU.

If you use a 330W PSU on the 7RE, it doesn't matter, because the firmware is limiting the total power, drawing slowly from the battery at >160W, and triggering PL2/EDP Other (picked up by throttlestop) if total system power exceeds 230W. I'm trying to see if there is a Bios mod that can be done to 'trick' or force the Bios or EC to think a 1080 is installed and use 7RF mode, so I can bypass the 230W limit.

Clearly MSI didnt think that 1) someone would use a 330W PSU with a GTX 1070, 2) that a pascal editor would ever come out to allow more than 115W from a 1070.
Cancer firmware, limiting enthusiasts.

@Prema has already fixed and removed all of MSI's cancer throttling on the EVOC barebones systems.

 

I do have to say the thought of localized editions having rendering issues didn't cross my mind, mainly as I expected any disparities to be absent in modern OSes. In any case, take your time and I will definitely look into how 8.40 will perform and give feedback of it, that you can be sure of Not only for myself but for any users that might face similar issues.

Also, your idea of UI font size adjustments is quite interesting, same for the previously suggested idea of being able to adjust main TS window size, as well as the monitoring section's column width being adjustable, but then again those would possibly be workarounds for a core issue. That said, my main doubt was what could've changed from 8.40 to the current Obsidian 8.48 that could've impacted fonts in such a way when being used in the same system without any changes.

 

Interesting.

When Windows 7 power schedule is set to max, and TS is being turned off, the multiplier sits around 30~32.
The Core C state is at C7 for 90% (more or less), the package C state sits on C2 most of the time.

But it still doesn't explain why I had this behavior never before (and you have to believe my word on that)
Like I said, the CPU speeds where always locked at 2.3GHz and just occasionally went up to >3.1Ghz.
But that was just for a very brief period of time (like 2-3 sec at most).

So my question still is, could the Power Cut option in TS unlock this limit?
I mean, this Clevo isn't the best laptop in the world, and I also can see the potential heat problems allowing the laptop going op that high.
Simply because the cooling system isn't adequate enough. (maybe I will fire on my CNC to develop a better one, lol)

edit, some extra information.
According to the help file, I set VCCIN to 1.7402V to activate the power cut option.

Could that have changed something?

 

Hi Unclewebb!

I love your software and i have written from time to time on this thread before with problems and the community here is great I've been using your program since like 2009 or something like that and i've always loved it. But my biggest problem is that you make it expire. I currently run it on like 10 of my extended families computers + my own laptops. And suddenly i get calls, my computer is slow again etc and then i know this software have yet again expired

Could you please please release a version which wont expire, which i can use? You've answered this before, that you want it this way. But i honestly don't understand why their cant exist one version which doesnt have the time expiration thingy. Just write that if people are using that, dont ask questions or report error. Make it clear that people have to use the version that expire unless they know what they are doing.

Best regards,
Joel

 

the program in version 4.8 fails to start at start up. whatever option I choose to make it start up, nothing happens at boot....

 

I support this too

 

Hi,
First of all i'd like to thank @ unclewebb for making this tool. It's been a godsend in trying to diagnose some issues I've been having with my laptop.

I've got a new Xiaomi Air 13 (i5 6200u with a NVidia 940MX) and I've been having some issues with it. Randomly, under light/medium load and with normal temperatures (30C-40C) it starts beeping, gets a BD_PROCHOT from some component and gets stuck at 400Mhz (never returning to normal). Looking at ThrottleStop while it is under this looks like the images attached.

Now, from here, if I disable BD_PROCHOT on ThrottleStop it obviously gets back to normal. If I keep going and run something that puts the laptop under stress (while monitoring temperatures which go to 70C-80C), the fans start spinning up and after a time I can reenable BD_PROCHOT and it won't get throttled anymore... I know this isn't an advisable thing to do, but somehow it fixes the issue (though not always).

I'm trying to find out more about what can be causing the BD_PROCHOT and a way to fix this, and I would like to hear your opinion about this. I intend to open it up, reapply the thermal paste to the CPU and GPU and check the fans (waiting to get the tools to open it up), but i'm afraid this won't fix the issue.

Sorry if something along these lines has already been discussed in this thread, I read the first and last few pages, but I confess to not having gone through it all.

Thanks in advance.

 

@syncd - If disabling BD PROCHOT fixes your throttling problem then leave it disabled. It is obvious that either a sensor on your motherboard or within your power adapter has gone bad. Some laptops use puny and pathetic little power adapters that cannot supply enough power for normal use. You can pull your hair out trying to find out what sensor is bad or why this is happening but why bother. Disabling BD PROCHOT blocks signals from these sensors from getting to the CPU so it can run at its full Intel rated speed like it is supposed to. Remember, disabling BD PROCHOT will not prevent your CPU from thermal throttling if it ever gets too hot. Disabling BD PROCHOT only blocks out external signals from throttling the CPU.

I would also disable the Clamp option in the ThrottleStop Turbo Power Limits window and I would consider using the Speed Shift feature. An EPP value of 0 will get you maximum performance for gaming, etc. and a setting of 80 or 128 is a nice compromise kind of setting for when running on battery power. Post some more screenshots if you need help with this.

With BD PROCHOT disabled, if you are still having problems, go do some gaming or whatever you like to do and turn on the TS - Log File feature so you have a record of your CPU's performance. You can upload log file data to www.pastebin.com

Your CPU is only a low power U CPU with a 15 Watt TDP power limit so it might not be able to deliver the kind of performance that you are looking for. It would be interesting to see some log file data just to see how it is performing and to see if there are any other bizarre throttling schemes kicking in during normal use. That is why I like using Speed Shift. It can be used to over come some throttling schemes and manufacturers are not expecting anyone to be using Speed Shift. The element of surprise.

I already did.

https://www.techpowerup.com/download/techpowerup-throttlestop/

Click on Show more versions and download TS 6.00. It does not expire. There is also a TS 7.00 version available on the internet that does not expire because someone decided to crack it.

I have spent thousands of dollars and put thousands of hours into developing and supporting ThrottleStop to help out as many users as possible. How did the user community respond? Let's just say that the Donate button was used so infrequently that I removed it to save myself the embarrassment. To prove this point, my wife went out picking bottles out of garbage cans one day and made more in a couple of hours than I was making in a couple of months. Ouch. That hurt. My begging days are over.

Now I just work on ThrottleStop at my own pace for my own satisfaction. Next time I am out of work and I am getting hungry, I might release a commercial version of ThrottleStop that does not expire and then the user community can decide if they want to support it or not. Until then, the most recent versions will continue to be expiring freeware.

 

@unclewebb I don't mind donating!

 

@unclewebb Thank you very much for your help.

I see your point regarding disabling BD_PROCHOT, and i would just leave at that, but unfortunately that only solves half the problem because sometimes the laptop keeps on beeping (like right now...). Disabling BD_PROCHOT fixes the throttling but it can't do anything about the stupid beeps...

I believe it has something to do with the fans but I can't check it right now.

Any way, I've followed your suggestions and disabled BD_PROCHOT and enabled SpeedShift (why the hell do vendors disable this by default?). Haven't touched the Clamp option because I don't fully understand what it does, but i'm sure it is answered somewhere on this thread so i'll keep looking.

I've enabled logs and captured an instance of the issue occurring: https://pastebin.com/5CuT9M9q

Not sure if something can be conclude by it, I see the processor getting throttled (when the multiplier goes to 4) but not much else. By the way, this was triggered by opening a browser with 10 tabs or so opened, so even though the cpu goes to 100% and the power to 13W-14W it's really not much load. When the multipliers goes back up it's me disabling BD_PROCHOT on Throttle Stop.

Guess i'll have to open it up and check the fans. If I can't figure it out i'll have to send it back to China which I was trying to avoid.

Anyway, thanks for your help (and for Throttle Stop).

 

Hi unclewebb,
I have been using throttlestop form earlier versions and this is my favorite software. It is working great with my Lenovo y50 that likes to throttle. I have a problem with the new version of the throttlestop 8.4.8.0.
Previous versions I can set my cpu to 3.2 ghz but with the obsidian my cpu returns to its stock values and throttle to 2.6ghz. I have tried disabling/enabling BD Prochot anc cant fix the problem cpu temperatures are fine.
The previous versions works just fine. What am I doing wrong? Please help.

 

Did you check limit reasons?
Did you try checking the overclock box in fivr?

 

I thought this might be a good place to hawk my latest editorial: https://www.notebookcheck.net/Opinion-It-s-time-we-talked-about-throttling-in-reviews.234232.0.html

It's about 10 years overdue, but still

 

Yes, I have checked/unchecked overclock setting but that doesnt work...

 

In newer builds Windows Creators Fall Update, power throttling will be present, then we can never know for certain if a app is throttled by high temps or the OS itself. This happens on battery, I assume and not on AC.