The ThrottleStop Guide

Maybe there's a defect in the board or the BIOS itself. Generate a battery report from Windows using this guide https://www.windowscentral.com/generate-battery-report-windows-10

powercfg /batteryreport /output "C:\battery_report.html"

 

I'll give it a go when I'm home. Right now the M2 SSD resides in my work laptop (which had working c-states before) and c-states stopped working again. That's two laptops (same generation etc) with the problem. I don't have any other M2 SSD to test with (2242mm isn't too common) so I can't test if it's the port on the laptop or the M2 itself. It's just odd that I can't install new Windows and have working c-states on either laptop. I tried Windows 8.1 yesterday and I had working C3 state when power saver profile was selected, but not C6 or C7. When I installed Intel RST driver that stopped working all together.

What an awful experience this is, Jesus... and it's even a CPU that's meant to be powersaving.

 

I keep getting the error "Could not open WinRing0.dll" on the latest Insider build (16273). It was working before I updated to this latest build today. Is anyone else experiencing this?
Thanks!

 

Maybe Microsoft has finally pulled the plug on ThrottleStop. This has always been a possibility.
Thanks for the info. I will be avoiding that build until I hear more.

 

Is there any testing I might be able to help with?

 

Have you tried in compatibility mode using W7/8.1?

 

Just tried it, but same error As soon as I rolled back to 16257, it works fine again, so it is the new build I think.

 

Did you notice anything about VC++ 6 or something being removed in the changelog?

 

Welp, MS is killing it. I guess they want you to use XTU.

 

Nothing I saw, but I just looked for Visual C++. Here is the link if you would like to look: https://blogs.windows.com/windowsex...ng-windows-10-insider-preview-build-16273-pc/

 

You might wanna give a feedback regarding VC++ 6 apps running on W10 CFU. Or they may be deprecating vc++ 6 from the Shell itself and forcing developer to move to UWP or VC++ 15/17.
Can you disable Power Throttling in Windows and re-run it.

 

How do I disable it for all apps?

 

I also I have this issue on this build (16273) ... I hope it is one build issue . We are getting closer to RTM build . If it is not fixed, the final build which everyone will update to, might have the same issue.

 

I don't know but try this link https://blogs.windows.com/windowsexperience/2017/04/18/introducing-power-throttling/

 

XTU isn't even letting me change anything except for reference clock... Like no slider bars are showing up except for that one.

 

Then its a bug. Report it. I think w10 cfu messed up icc watchdog driver. I reckon hybrid shutdown aka fast startup is disabled.

 

Just reported the bug. The more people who do, the more likely it is to be resolved soon.

On the XTU website, it says "
. If the issue still occurs, check the Device Manager for the following drivers:

• Iocbios2 installed under Hidden devices
• ACPI BIOS Control Driver under System devices"

Both of these are missing on my xps 15 9550. Could that be the problem?

 

Reinstall XTU.

 

Guys I need help.
So I have dell inspiron 5537
Core i5 4200U
Ati 8670M

I start playing fifa 17 at 60 fps and after 3 or 5 min it goes down to 30-40
in throttle stop i see edp current & core power & gpu power
the temp is not higher than 70 degree though
how to disable throttling and keep getting 60 fps

 

Check your core clocks and memory clocks in MSI Afterburner and double check your GPU clock rate and memory clock rate
https://www.techpowerup.com/gpudb/1950/radeon-hd-8670m
https://www.techpowerup.com/gpudb/1950/radeon-hd-8670m

 

Hi guys, i'd need a little bit of your help

recently I've been having issues with games, ie: path of exile. which ran flawlessly with everything at high, at 60 FPS and above. but now it cant even run with everything turned down to the minimum specs. i get insane freezes and frames below 10 fps.

Specs of the pc (laptop):
Dell XPS 9550 (2016)
I7-6700HQ
GTX 960M
8gb ram.

I ran multiple benchmarks and tests, temps never exceed 60-65 degrees on either graphics or CPU, according to aida64. Note that under stresstest from aida64, with all test selected, it tends to thermal throttle within 5 minutes. But this is absolutely not happenning in game (i'm monitoring everything with my second screen)

After that i ran TS, just to double check throttling reasons and i noticed something funny.
At idle, while doing absolutely nothing i have an EDP OTHER throttle on RING. CPU and GPU are fine, nothing moves. i have cleared the alerts and this one comes back instantly, and goes to red from time to time.


D'you guys have any idea as to what could link to this?

thanks!

edit: Here is what my performances look like when i boot up :

 

@unclewebb

Hey man, when are we getting an update to ThrottleStop it's been a while since we've been at v8.48

 

Are you going to buy 8th gen CPUs?

 

@unclewebb it seems most of the 800mhz throttle on haswell and skylake models are due to BD prochot.. so i just want to know, what all components can trigger BD prochot.. is there a specific names ? like GPU core sensor, VRM, PCH temp sensor ?? etc.. is there a way to find out from which sensors its getting triggered.. and thank you for the wonderful TS..

 

I haven't touched TS in months. I have been working on a different project lately. It will probably be a few more months before I have a new version of TS ready for release. If Microsoft have finally decided to block the WinRing0 driver, there is not much point in continuing to develop a tool that no one will be able to use anymore. The WinRing0 driver signature expired long ago. Using this driver has always been a bit of a security risk. I am not surprised if Microsoft finally decided to block all of the apps that use it. I am going to try to install Windows 10 - 16273 next week to see what is going on and if anything can be done.

@VICKYGAMEBOY - I do not know how to determine the source of BD PROCHOT throttling. Different manufacturers use this feature in different ways and no one wants to admit that they are doing this at all. It is a big secret. Maybe we could get Mr. Trump to go after laptop manufacturers for his next crusade. It is not only news that is fake. Some manufacturers have some very fake performance specs, especially when throttling kicks in.

 

trump throttling is legit.. anyways thanks for the info.. seems like its not that easy to figure out what is triggering.. ill have to manually test so many stuffs along with other users.. instead of playing games on gaming laptops, we are just playing games to check whether the laptop throttles or not.. evolution of laptops.. lol

 

@unclewebb

I too experienced the WinRing0 error on the x64 Windows 10 build 16273 (which is actually being upgraded to 16275 this moment). I'm not so sure that it's a deliberate effort to block the driver, because the Event Log reports the driver/service loading successfully, and OpenHardwareMonitor (which also uses WinRing0) still works.

I found a way to make ThrottleStop work: open and leave OpenHardwareMonitor running, then open ThrottleStop. For some reason, TS will launch correctly and appears to work as expected. OHM uses the WinRing0 driver, so my guess is that TS will use the existing driver loaded into memory by OHM. I would suggest therefore that TS is not initializing the driver correctly (or at least in a way that the new build doesn't like).

 

@unclewebb @ keshavmot2 @kosta20071
I'm on build 16273 and I haven't had an issue with ThrottleStop, I wonder why.

Anyway 16275 rolled out today, have a try with that.

Go to blogs.windows.com and see if there is anything special in the changelogs

Power Throttling has been implemented for us Insiders for ages. It shouldn't be it.

 

Same issue on 16275. However, psyke83's method worked for me.

 

Anyone have recommendations for using Throttlestop on an Atom X7-Z8750? I'm looking to get max performance of the GPU under 3D load, i.e. gaming, even if sacrificing some CPU performance.

 

so guys
core i5 4200U

undervolted cash and cpu to 50mv
gpu 70 mv
gpu2cpu 7 ( i have dedicated amd gpu so i don't need intel igpu in gaming)

playing cs go and in 15 minutes power limit throttle kicks in
the package tdp is under 15 W
why da hell does this happen any tips?

 

Because it's an ultra low voltage chip.

 

is there a way to jump over this limitation ?

 

@unclewebb
Is it possible to extract the winring0.dll driver from Open Hardware Monitor and put it in the Throttlestop folder so I don't have to run OHM on the Insider builds to open TS?

Thanks for all of your hard work!

 

@unclewebb - any chance this can be used for something like Ryzen or TR, or do you have a recommendation for looking for throttling on those platforms?

 

@HTWingNut - In the TPL window, try enabling and adjusting the Intel Power Balance feature so the Intel GPU gets more of the power budget than the Intel CPU. I have had zero hands on time with an Atom x7-Z8750 so I am not sure what is possible.

Some manufacturers force their U CPUs to go into cTDP down mode so the TDP power limit will drop down to 10 Watts or maybe only 7.5 Watts. A lot of times this is totally unnecessary but they do it anyhow and there is nothing a user can do about this. It is too late for you but my recommendation for others is if you buy a low power U CPU, run it into the ground day one and if it is not fit for your purpose, take it back immediately. I was getting 28 Watts out of my wife's U CPU so a low power U does not have to be a miserable experience. It all depends on the individual manufacturer. A U CPU can be brutally sluggish and close to unusable for anything beyond surfing the net or it can run like this 7500U. Definitely no complaints here.



@keshavmot2 - Open Hardware Monitor has wrapped the WinRing0 driver within their OpenHardwareMonitorLib.dll
Windows 10 Build 16273 does not like the WInRing0 driver that ThrottleStop is using so switching over to the OpenHardwareMonitorLib.dll is a possibility but a month from now, Microsoft might decide that they do not like the Open Hardware Monitor driver either and will block that too. I have got a feeling that Microsoft really does not want individual programmers like myself being able to control CPU voltages, etc. Their friends at Intel have probably been twisting their arm for years about this security risk so MS is finally cracking down.

At the moment, I do not plan to do anything about this problem. I really do not need the new Emoji Bot or the new Bahnschrift font that Build 16273 brings to the table so I am in no hurry to upgrade to this.

@psyke83 - Thanks for finding the Open Hardware Monitor trick.
I am sure Microsoft appreciates your work as much as Intel appreciates my work.

@ajc9988 - ThrottleStop will never support Ryzen CPUs.

 

If there is a possibility to fix it, at least for the time being, we would really appreciate it as this will affect all users who update even in the normal ring soon enough.
I really appreciate all of your hard work, and if you can't do it, I totally understand. If there is a way I could replace the driver myself or something, I am willing to do that also if guided.

 

How is XTU getting away with this then? There is nothing safe in XTU compared to TS. Freaking control freaks.

 

@keshavmot2 - There is no possibility that this is going to be fixed anytime soon. Using the Open Hardware Monitor driver is one possibility but I would be required to release all source code for ThrottleStop as open source which I am not willing to do at the moment.

Intel's pockets are quite a bit deeper than my pockets. They can afford their own drivers. This is all about squeezing individual developers out of the picture in the name of improving security. If I wasn't the one being squeezed out, I would be all for improved security.

 

any known issues with Throttlestop with Windows 10 16278.rs3? Keep getting error message can't load WinRing0.dll since the last Fast Ring update

 

Yes, if you read above, its been happening since 16273.

 

I'd love you to release the source, but for this particular problem, it's not necessary. I'd suggest the opposite - look at precisely how OHW interfaces with the driver in their source. Why? OHW's WinRing0 driver is sha1sum identical to the x64 version you've packaged with ThrottleStop (and presumably, the x86 version would be extracted/used on a 32 bit OS). OHW embeds the driver into the executable, which extracts as "OpenHardwareMonitorLib.sys" when the application runs, but I assure you that it's the same.

I'm hoping that you're wrong re: Microsoft deliberately targeting ThrottleStop, but just in case, I'm ambivalent about reporting the issue (and workaround) via the Feedback app, etc.

 

@psyke83 - It looks like Microsoft has blocked any program that directly uses the WinRing0 driver. Open Hardware Monitor still works because the WinRing0 driver they use is hidden within their OpenHardwareMonitorLib.dll

@keshavmot2 checked out RealTemp for me today and it is blocked too. I have heard that MSI Afterburner is also broken by this Windows update but I have not confirmed that yet.

The security vulnerability that WinRing0 has is that once a program loads it into memory, other programs can use its functions. That could give a virus wide open access to the CPU and a whole lot more. At some point, Microsoft will probably block the Open Hardware Monitor driver too because it has the same vulnerability.

If I ever come up with a plan B, I will post it here. Long term, this is not looking too good at the moment.

 

Thank you. I may give it some trials and report back if there's not much info out there.

I have used Windows Power Options and setting fixed frequency doesn't work. I can set max processor state to 99% and the CPU won't go past 1.6GHz, and the GPU typically runs at 600MHz then. Setting the frequency does not do anything. If I set max processor state to 100% then CPU will boost to 2.6GHz, but GPU will run at 400MHz max. Seems it is a TDP balancing issue. I'll see what I can do with TS.

If there is a way to set frequency of CPU to 2000MHz or 2100MHz that would be a good balance if I can maintain 600MHz on the GPU. Wish there was a way to increase TDP slightly, or set it for temp throttle instead of TDP throttle. It never exceeds 62C, so there's lots of thermal head room. The power adapter is capable of 15W over 5V, so that shouldn't be an issue either.

 

@unclewebb WinRing0 v2.0.0.20 (VirtualChecker3). Missing 64-bit DLL.

 

@j95 - Thanks for helping out. The problem with WinRing0 v2.0 is that some of the more useful features of this driver were removed. Version 2.0 does not let you write anything to registers within the CPU so that means none of ThrottleStop's useful features like voltage and MHz control, etc. would work anymore. Sad times for ThrottleStop and other useful programs that have depended on the WinRing0 driver for years.

 

Hopefully it's a temporary block, M$ bundled power throttle doing its thing and/or Insiders wrong settings causing BSODs, etc. OHM proves that there's no hash rule for WInRing0; TS is the target. Renaming....

XTU's IOCBIOS was, as it still is, unreliable to say the least. One of the many reasons why I use TS instead.

 

Hi, been researching on undervolting my 7700hq because of the 97° is hitting on BF4.
Found throttlestop and really love the features.
I'm having a strange problem that i think it has to be user related.
Whenever i use TS to undervolt, say -140, it won't lower any temps at all, while doing it on XTU it does help.
I double checked that i have "Turned on" TS. I also ckeched with HwInfo and it does show the undervolting done, but no temps change.
The only thing that made the temps go low was disabling turboboost.
Is there any way Intel is limiting the undervolting or am i doing something wrong?

 

You need to undervolt the cache and core.
I believe if you undervolt only the core, but not the cache, the core still gets full volts, regardless of what is shown on the readout.

This may be a Bios issue with MSR's.

 

I did.
I followed this guide.

There are 6 elements under “FIVR control”, but we only care about three: CPU Core, CPU Cache, and Intel GPU. In fact, CPU core and CPU cache should almost always be set to the same value. Make sure the radio button for “Adaptive” is selected, as well as CPU core, and now we can select an undervolt for it. Only adjust the Offset Voltage. How much you should undervolt depends a fair amount on what chipset you have. In general, Skylake quad-core mobile CPUs undervolt very well (between -125-165mv) while Kaby Lake quad-core CPUs don’t do so well (generally between -100-125mv). For this guide, I suggest a conservative undervolt of -80mv for your CPU Core. Once that is done, click “CPU Cache” and perform the same steps. CPU Core and CPU Cache should generally have the same undervolt. Lastly, select “Intel GPU” and give it a more conservative undervolt. The Intel GPU can generally be undervolted -50mv, but more than that is not guaranteed.

Once you have done Core, Cache, and GPU, I recommend pressing “Apply”. If the voltages take and it doesn’t crash immediately, select “OK - Save voltages immediately”, as it is very annoying to re-enter all your voltages after a crash during testing. Before applying your undervolts to your other profiles, spend some time using your computer in various scenarios to make sure they’re stable.