The ThrottleStop Guide

If i upgrade to a new version of ThrottleStop, i just need to copy the ThrottleStop.ini from the old to the new version?

 

Yes that would be correct. Just copy and paste

 

Hi unclewebb,

Already followed the task scheduler guide to the T. I think the problem for me was there's a grayed out checkbox in the condition tab.
Hope it works.

Thank you!

 

Yeah, me too. Waiting for this one.

 

You must first temporarily select the necessary "parent" checkbox to activate the greyed out "child" option you are trying to clear so you can then clear that "child" option. Don't forget to uncheck and deactivate the temporary "parent" selection afterwards to finalize everything.

 

Does anyone know how to unlock broadwell core m power limits?

I have a dell venue pro 7140 that I modded with a copper plate and heatpipe. It solved the thermal throttling issues so I replaced the core m 5y10 board (2.0 GHz boost) with a 5y71 board (2.6GHz boost) but there is a long term 6W power limit that prevents any meaningful gain in clock speed.



I think the power throttling is from "power limit 1"




Some searching pointed me to this post by Dufus in the anandtech forums
https://forums.anandtech.com/threads/intel-broadwell-thread.2394938/page-120#post-37678135
and this post by unclewebb
http://forum.notebookreview.com/threads/the-throttlestop-guide.531329/page-563#post-10478523

...which showed that the PL1 and PL2 settings for broadwell (and other gens) are hidden in MCHBAR (Chipset?) registers at the address FED159A0 & FED159A4 (FED10000 being the MCHBAR region).



For me these registers were set to
PL1: 001B8030
PL2: 00428078

In PL1 bits 16 and 15 were 1, meaning it is clamped and enabled. The "030" (bits 14 to 0) in hex is "48" in decimal, so divide by 8 to get the actual power limit (48/8 = 6) of 6W. The time (bits 21 to 17) is "01101" in binary, which is 13 in decimal. Using the formula in Dufus's post: the power limit time in seconds is 2 raised to the decimal number then divided by 1024, which gets 8s which AIDA64 reads correctly.

In PL2 bits 16 and 15 were 0 and 1, meaning not clamped but enabled. The "078" in hex is "120" in decimal, so divide by 8 to get power limit of 15W.

The bit 31 in offset 0xA4 (PL2, aka FED159A4) was set to 0 so both PL1 and PL2 are not locked via this bit. (Even though the AIDA64 screenshot above shows both as locked - I'm not sure where the lock is coming from).


So I tried setting FED159A0 (PL1) register to 001B8079 (changing the power limit from 6W to 15W), but unfortunately PL1 is still triggered at 6W and the throttling remains.

Next I looked at this post by unclewebb
http://forum.notebookreview.com/threads/the-throttlestop-guide.531329/page-304#post-10006245
which describes some sort of other power limit in the processor MSR 0x610.

Not sure if that power limit applies to broadwell but the report I pulled from CPUz shows it is set to something.

Code:

   MSR 0x00000606       0x00000000   0x000A0E03
   MSR 0x00000601       0x40101414   0x80000090
   MSR 0x00000610       0x80428078   0x001B8030
   MSR 0x00000611       0x00000000   0x05721F0C
   MSR 0x00000639       0x00000000   0x02A43FA8

Apparently the 8 in front means the power limit is locked via this register?

At this point I have no idea what to do LOL
This is what throttlestop shows in TPL, the package power limits is all greyed out. (I assume this is probably what the 0x00000610 MSR is controlling and is causing the throttling?)


If I exit throttlestop and open intel XTU these are the power limit options I see, all sliders are already maxed out.



At this point I am stuck and searching for other options. Would be appreciated if anyone has any other ideas. This is some next level stuff

 

I guess your idea about following the guide to a T is a little different than my idea of following the guide to a T. You must have missed this paragraph in the guide!

Maybe I have to update the guide and make this paragraph jump out at you in neon yellow. Good idea @Maleko48

Code:

MSR 0x00000610       0x80428078   0x001B8030

@margroloc - Looks like you figured out the source of your problem. The power limit that is holding you back is the one in MSR 0x610 and yes that initial 8 signifies bit[63] is set. That is the Lock bit and it is absolutely, positively, 100% set. HWiNFO shows this information and ThrottleStop also shows that this register is Locked to 6 Watts. There is no possible way to unlock this register once you have booted up into Windows. You need a modified bios to remove the lock bit.

There are no other options. Modified bios or you will forever be stuck at 6 Watts.

Updated purple version is on the way. I might have to quit my day job so I can get more work done on TS.

 

rest in pieces. in the meantime I dumped the bios and extracted the IFR data using this guide.
I found the variables for package power limit lock, platform power limit lock, configurable TDP, etc... and disabled them in nvram after booting from a GRUB usb stick. The changes persist across reboots.

In the end this unlocked some more settings in the throttlestop TPL. AIDA64 reads raised the power limits, as does hwinfo. I messed with the TPL settings and the FED159A0/A4 PL1/PL2 registers some more.


Intel XTU also shows all these settings now.


Unfortunately nothing changed, chip still throttles at 6W after a few seconds.
This was before your post so it makes sense now. I attached the uefi A09 dump in case someone else with a 7140 comes across this post and wants to mess with it. I will look into bios modding. No idea what i'm doing LOL.

Edit: Looks like the MSR_PKG_POWER_LIMIT 0x610 is designed specifically to stop user modification
https://i.postimg.cc/SxZN8P16/screenshot_13.png from ftp://ftp.axxiv.ch/FTP/AXXIV/WORKSTATION/DRIVERS/SVELT/SP67A/W7/Intel/XTU6/XTU%206.0%20BIOS%20Interface%20Specification.pdf
http://forum.notebookreview.com/threads/the-throttlestop-guide.531329/page-29#post-7159788

This is as far as I got https://i.postimg.cc/wv7j2Yb5/screenshot_14.png
don't see any option to toggle MSR 0x610. There is some weird stuff in the bios but I'm totally lost on how to read or configure it.
https://i.postimg.cc/XYJmpNZg/screenshot_15.png https://i.postimg.cc/cLS7bFWt/screenshot_16.png
GG dell

 

@margroloc - Congratulations on your perseverance. You have taken care of 2 of the power limits but guess what? There is a third turbo power limit controlled by PECI. I am not sure how to manipulate that one. There is a nice looking Intel PECI tool for this task but that is not available to the general public. You might have hit the wall but keep trying. There are a lot of people that would like to see you solve this problem. No one from Intel of course.

That is only true if a manufacturer sets the Lock bit. You found a way around that obstacle.

 

Greetings,

Long time lurker, but I've now signed up to this forum to dive into this insanely interesting thread! So, I recently purchased a used 2015 15" MacBook Pro with a 4980HQ that has some pretty nasty throttling issues that don't appear to be thermal-related (or at least, not from a "prochot" point of view). The throttling only occurs when the dgpu (Radeon M370X) is in use, so naturally, this makes gaming terrible.

Similar to your Y510P, setting NTR to 1 and locking it is the *only* thing that prevents throttling, and I am thrilled because I was a bit dismayed and thinking I was going to have to turn around and re-sell this puppy. Now I know it can be the beast it was meant to be. But I still have more work to do. I'd still like to figure out *why* this throttling is happening. Unfortunately, the "limits" option is grayed out, and sending limit reasons to the log doesn't actually do so. Is this because Apple's firmware blocks that information somehow? I actually have a case open with Apple that is escalated to their engineering tier, but it's clear that the more details I can provide, the better. I'm still getting responses back stating that I'm throttling because my disk is 70% full. I refuse to let them close the case on me until we can come to a resolution. Just check out their recent 2018 i9 fix...it almost seems like they purposefully limit their hardware via software, but they're getting called out now! https://www.macrumors.com/2018/07/24/throttling-fix-2018-macbook-pro-improvements/.

That brings me to my question: what does this setting actually do? I'm game to dive into any details. Thanks for creating such a useful utility!

 

You can start to read this two... And Apple is on same level. Only worse.
http://forum.notebookreview.com/thr...950h-coffee-lake.810891/page-92#post-10769126

http://forum.notebookreview.com/thr...rmance-explained-by-notebookcheck-net.808983/

 

I have a i5-8250U (-90mW, Turbo Ratio Limit from 34 is on 31, TB Long Power 25W and Short Power is 44W) everything is fine until the Windows 10 is on "Best Performance" mode (Which lock the CPU speed to 3.1GHz always).
If I change it to "Better Performance" (Which let the CPU go down from 3.1GHz) after a while i get BSOD during the Battlefield 4. What is the reason of this? Its because of the -90mW?

 

Hi, I have an Asus ROG notebook with a i7-4710HQ and latest version of ThrottleStop.

CPU is Haswell, so with the integrate voltage regulatore FIVR.
I OCced to 3.7 an all 4 cores and during stress test with AVX2 (AIDA64 FPU for example), after some minutes I notice some throttling caused by VR thermal limit.
In these conditions, Max Power is above 80W, so it's quite normale for a CPU of 47W TPU.

Limit Reasons shows VR THERMAL on both Core and Ring.

My question: is it the VRMs on the motherboard or the integrated FIVR on the CPU package that hits the VR thermal limit?


Thanks in advance

 

I still can't find that annoying little thing that's keeping my CPU from going to deep sleep states. I feel it's my mouse/touchpad, but I can't pin it down. C0% is still quite high.

 

Did you do some stress testing after your undervolt to make sure it was stable? And even if it is, there are cases where there is a BSOD after the CPU goes from a high load to a small load (or clock speed). Having the CPU locked at 3.1GHz might be preventing that from happening.

 

Have you checked out this guide here:

http://forum.notebookreview.com/thr...e-on-windows-enabling-deeper-c-states.815602/

 

Did you manage to fix that? My 7700HQ doesnt go deeper than C3 on idle

 

Are you running on AHCI or RAID? Are your SSD(s) set to Lowest or HIPM+DIPM in Window's advanced/hidden power options?

 

ThrottleStop 8.70.6
https://drive.google.com/open?id=19h2pOlAZWjP0UVecQw-i6HTJikgq_xzo

- fixed Core i5/i7 4xx0HQ Haswell, Crystal Well support.

I think I saw this problem a long time ago but must have forgot about it. I need to be nagged more to fix bugs like this. I would like nothing more than to blame Apple but in this case, it is all my fault. The CPUID for a 4980HQ is 0x40661. In two separate places within the ThrottleStop code, I forgot to write the 0x part of that number so ThrottleStop has not been detecting any of the Crystal Well series correctly. Here is Intel's list of Crystal Well based processors.

https://ark.intel.com/products/codename/51802/Crystal-Well

Hopefully Limit Reasons is no longer grayed out so you can finally see why your CPU is throttling and also do some under volting to minimize the problem.

If setting the Non Turbo Ratio to 1 fixes your problem, the actual throttle reason might not show up in Limit Reasons. This is a sign that Apple simply turns off Intel Turbo Boost when the GPU is active. Lenovo does the same thing on my Y510P. Nowhere in the specs do they ever tell users about this "feature". It is a real slippery, slimy business practice to include high performance hardware, deliberately castrate it so it cannot perform at its full rated speed and then turn to denial when they inevitably get caught.

I am not a violent person but anyone that tried to tell me that might get a punch in the face. I have never heard a lie quite that ridiculous.

For a Non Turbo Ratio example, if you set this to 18 and software or the operating system asks for a multiplier equal to or less than 18, the CPU will use that exact multiplier. If the OS asks for 12 or 15, the CPU will used the 12 or 15 multiplier. If the OS asks for a multiplier higher than 18, the CPU sees that you want a multiplier higher than the non turbo ratio so it determines that what you really mean is that you must want full turbo boost and will then use the maximum multiplier. Setting this to a low value like 1 is kind of a tricky way to get the CPU to ignore all of the lower / intermediate multipliers. In this mode, all the CPU knows is full speed ahead.

The default speed for my 4700MQ is 2400 MHz which is the 24 multiplier. Technically speaking, my Y510P does not disable turbo boost. When the GPU is active, instead of asking for the maximum multiplier, it just asks for the 24 multiplier. The result is the same, just the method is slightly different. By setting the Non Turbo Ratio to 1, when the Y510P asks for the 24 multiplier, the CPU says, that multi is way higher than 1 so you must want full turbo boost. Full speed ahead and an easy and simple way to disable this throttling scheme. Sounds like either Apple has learned from Lenovo or vice versa. They both get a Fail.

Post some TS screenshots of your 4980HQ. I might see something else that needs a tweak.

 

I almost pee'd on myself from laughing... no offence

Can't blame you on that

 

As I was searching for adventure to keep squeezing more juice of speed of my laptop [See my sig.].. I was looking for something to do so it came to my mind about DPTF.. since it was disabled by default on my unlocked BIOS so.. I wanted to experiment it.. so what I did was enable it from BIOS and restarted & I got for like 13 drivers devices added on device manager [Previously it was only 1]


Anyway.. I kept digging & looking through drivers files (.inf) and what does contains... it seemed to me that it missed adding power settings in able for DPTF to work fully so..

I read & searched about something related to DPTF kept googling & found some info. on some russian forums & this [ https://www.anandtech.com/show/9550...ower-and-thermal-framework-smarter-throttling] and this [ https://superuser.com/questions/909...al-framework-settings-what-exactly-do-they-do):] after digging deep.. I finally found some registry keys that needed to be present in order DPTF to work fully functional. It doesn't add them when you setup or when you just install its drivers only so... I added those missing keys and after adding it those power settings showed so.. after choosing those settings through windows power settings....


wow.. without even restarting.. it began to lower watts under heavy load or gaming..

I made sure that it is not throttling or crippling something because I have got my fully speed all the time and under heavy load with lower watts! which means= lower temperature! previously my cpu temp. was touching 80 c but now doesn't go over 73 c on all cores .. it is great

Edit:-

Oh yes.. I just found out now while writing this.. the reasons why I have have lower watts at the same full cpu speed is that it was playing with the CPU Cache speed.. it was lowering the CPU Cache speed when stressing my CPU so that it leads to lower watts = lower power consumption = lower heat.
So.. it was a great journey for me.. although I don't see any performance degradation at all actually it improved

For those who wants to have those power options.. make sure that you have all DPTF drivers installed bec. without them.. it doesn't have any effect no matter what settings you chose

Note:- Open a Notepad & Copy it from the spoiler then save it as .reg file to work or download it from the attachemnt

Spoiler: Intel DPTF fix

Code:

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\48df9d60-4f68-11dc-8314-0800200c9a66]
"FriendlyName"=hex(2):49,00,6e,00,74,00,65,00,6c,00,28,00,52,00,29,00,20,00,44,\
  00,79,00,6e,00,61,00,6d,00,69,00,63,00,20,00,54,00,75,00,6e,00,69,00,6e,00,\
  67,00,20,00,53,00,65,00,74,00,74,00,69,00,6e,00,67,00,73,00,00,00
"Description"=hex(2):49,00,6e,00,74,00,65,00,6c,00,28,00,52,00,29,00,20,00,44,\
  00,79,00,6e,00,61,00,6d,00,69,00,63,00,20,00,54,00,75,00,6e,00,69,00,6e,00,\
  67,00,20,00,53,00,65,00,74,00,74,00,69,00,6e,00,67,00,73,00,00,00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\48df9d60-4f68-11dc-8314-0800200c9a66\07029cd8-4664-4698-95d8-43b2e9666596]
"FriendlyName"=hex(2):43,00,6f,00,6e,00,66,00,69,00,67,00,20,00,54,00,44,00,50,\
  00,20,00,4c,00,65,00,76,00,65,00,6c,00,00,00
"Description"=hex(2):53,00,70,00,65,00,63,00,69,00,66,00,79,00,20,00,74,00,68,\
  00,65,00,20,00,43,00,6f,00,6e,00,66,00,69,00,67,00,20,00,54,00,44,00,50,00,\
  20,00,4c,00,65,00,76,00,65,00,6c,00,20,00,66,00,6f,00,72,00,20,00,49,00,6e,\
  00,74,00,65,00,6c,00,28,00,52,00,29,00,20,00,44,00,79,00,6e,00,61,00,6d,00,\
  69,00,63,00,20,00,54,00,75,00,6e,00,69,00,6e,00,67,00,00,00
"Attributes"=dword:00000002
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\48df9d60-4f68-11dc-8314-0800200c9a66\07029cd8-4664-4698-95d8-43b2e9666596\0]
"FriendlyName"=hex(2):48,00,69,00,67,00,68,00,20,00,54,00,44,00,50,00,00,00
"Description"=hex(2):43,00,6f,00,6e,00,66,00,69,00,67,00,75,00,72,00,65,00,20,\
  00,48,00,69,00,67,00,68,00,20,00,54,00,44,00,50,00,20,00,4c,00,65,00,76,00,\
  65,00,6c,00,00,00
"SettingValue"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\48df9d60-4f68-11dc-8314-0800200c9a66\07029cd8-4664-4698-95d8-43b2e9666596\1]
"FriendlyName"=hex(2):4e,00,6f,00,6d,00,69,00,6e,00,61,00,6c,00,20,00,54,00,44,\
  00,50,00,00,00
"Description"=hex(2):43,00,6f,00,6e,00,66,00,69,00,67,00,75,00,72,00,65,00,20,\
  00,4e,00,6f,00,6d,00,69,00,6e,00,61,00,6c,00,20,00,54,00,44,00,50,00,20,00,\
  4c,00,65,00,76,00,65,00,6c,00,00,00
"SettingValue"=dword:00000001
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\48df9d60-4f68-11dc-8314-0800200c9a66\07029cd8-4664-4698-95d8-43b2e9666596\2]
"FriendlyName"=hex(2):4c,00,6f,00,77,00,20,00,54,00,44,00,50,00,00,00
"Description"=hex(2):43,00,6f,00,6e,00,66,00,69,00,67,00,75,00,72,00,65,00,20,\
  00,4c,00,6f,00,77,00,20,00,54,00,44,00,50,00,20,00,4c,00,65,00,76,00,65,00,\
  6c,00,00,00
"SettingValue"=dword:00000002
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\48df9d60-4f68-11dc-8314-0800200c9a66\07029cd8-4664-4698-95d8-43b2e9666596\DefaultPowerSchemeValues]
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\48df9d60-4f68-11dc-8314-0800200c9a66\07029cd8-4664-4698-95d8-43b2e9666596\DefaultPowerSchemeValues\381b4222-f694-41f0-9685-ff5bb260df2e]
"ACSettingIndex"=dword:00000000
"DCSettingIndex"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\48df9d60-4f68-11dc-8314-0800200c9a66\07029cd8-4664-4698-95d8-43b2e9666596\DefaultPowerSchemeValues\8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c]
"ACSettingIndex"=dword:00000000
"DCSettingIndex"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\48df9d60-4f68-11dc-8314-0800200c9a66\07029cd8-4664-4698-95d8-43b2e9666596\DefaultPowerSchemeValues\a1841308-3541-4fab-bc81-f71556f20b4a]
"ACSettingIndex"=dword:00000000
"DCSettingIndex"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\48df9d60-4f68-11dc-8314-0800200c9a66\4a44b800-4f72-11dc-8314-0800200c9a66]
"Attributes"=dword:00000002
"FriendlyName"=hex(2):50,00,6f,00,77,00,65,00,72,00,20,00,4c,00,69,00,6d,00,69,\
  00,74,00,00,00
"Description"=hex(2):53,00,70,00,65,00,63,00,69,00,66,00,79,00,20,00,74,00,68,\
  00,65,00,20,00,70,00,6f,00,77,00,65,00,72,00,20,00,6c,00,69,00,6d,00,69,00,\
  74,00,20,00,66,00,6f,00,72,00,20,00,49,00,6e,00,74,00,65,00,6c,00,28,00,52,\
  00,29,00,20,00,44,00,79,00,6e,00,61,00,6d,00,69,00,63,00,20,00,54,00,75,00,\
  6e,00,69,00,6e,00,67,00,20,00,53,00,65,00,74,00,74,00,69,00,6e,00,67,00,73,\
  00,00,00
"ValueMin"=dword:00000001
"ValueMax"=dword:00000005
"ValueIncrement"=dword:00000001
"ValueUnits"=hex(2):4c,00,65,00,76,00,65,00,6c,00,00,00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\48df9d60-4f68-11dc-8314-0800200c9a66\4a44b800-4f72-11dc-8314-0800200c9a66\DefaultPowerSchemeValues]
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\48df9d60-4f68-11dc-8314-0800200c9a66\4a44b800-4f72-11dc-8314-0800200c9a66\DefaultPowerSchemeValues\381b4222-f694-41f0-9685-ff5bb260df2e]
"ACSettingIndex"=dword:00000003
"DCSettingIndex"=dword:00000003
"OverrideACSettingIndex"=dword:00000003
"OverrideDCSettingIndex"=dword:00000003
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\48df9d60-4f68-11dc-8314-0800200c9a66\4a44b800-4f72-11dc-8314-0800200c9a66\DefaultPowerSchemeValues\8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c]
"ACSettingIndex"=dword:00000005
"DCSettingIndex"=dword:00000005
"OverrideACSettingIndex"=dword:00000005
"OverrideDCSettingIndex"=dword:00000005
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\48df9d60-4f68-11dc-8314-0800200c9a66\4a44b800-4f72-11dc-8314-0800200c9a66\DefaultPowerSchemeValues\a1841308-3541-4fab-bc81-f71556f20b4a]
"ACSettingIndex"=dword:00000001
"DCSettingIndex"=dword:00000001
"OverrideACSettingIndex"=dword:00000001
"OverrideDCSettingIndex"=dword:00000001
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\48df9d60-4f68-11dc-8314-0800200c9a66\63c39116-4f72-11dc-8314-0800200c9a66]
"Attributes"=dword:00000002
"FriendlyName"=hex(2):41,00,63,00,6f,00,75,00,73,00,74,00,69,00,63,00,73,00,20,\
  00,4c,00,69,00,6d,00,69,00,74,00,00,00
"Description"=hex(2):53,00,70,00,65,00,63,00,69,00,66,00,79,00,20,00,74,00,68,\
  00,65,00,20,00,61,00,63,00,6f,00,75,00,73,00,74,00,69,00,63,00,73,00,20,00,\
  63,00,6f,00,6f,00,6c,00,69,00,6e,00,67,00,20,00,6c,00,69,00,6d,00,69,00,74,\
  00,20,00,66,00,6f,00,72,00,20,00,49,00,6e,00,74,00,65,00,6c,00,28,00,52,00,\
  29,00,20,00,44,00,79,00,6e,00,61,00,6d,00,69,00,63,00,20,00,54,00,75,00,6e,\
  00,69,00,6e,00,67,00,20,00,53,00,65,00,74,00,74,00,69,00,6e,00,67,00,73,00,\
  00,00
"ValueMin"=dword:00000001
"ValueMax"=dword:00000005
"ValueIncrement"=dword:00000001
"ValueUnits"=hex(2):4c,00,65,00,76,00,65,00,6c,00,00,00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\48df9d60-4f68-11dc-8314-0800200c9a66\63c39116-4f72-11dc-8314-0800200c9a66\DefaultPowerSchemeValues]
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\48df9d60-4f68-11dc-8314-0800200c9a66\63c39116-4f72-11dc-8314-0800200c9a66\DefaultPowerSchemeValues\381b4222-f694-41f0-9685-ff5bb260df2e]
"ACSettingIndex"=dword:00000003
"DCSettingIndex"=dword:00000003
"OverrideACSettingIndex"=dword:00000003
"OverrideDCSettingIndex"=dword:00000003
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\48df9d60-4f68-11dc-8314-0800200c9a66\63c39116-4f72-11dc-8314-0800200c9a66\DefaultPowerSchemeValues\8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c]
"ACSettingIndex"=dword:00000005
"DCSettingIndex"=dword:00000005
"OverrideACSettingIndex"=dword:00000005
"OverrideDCSettingIndex"=dword:00000005
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\48df9d60-4f68-11dc-8314-0800200c9a66\63c39116-4f72-11dc-8314-0800200c9a66\DefaultPowerSchemeValues\a1841308-3541-4fab-bc81-f71556f20b4a]
"ACSettingIndex"=dword:00000001
"DCSettingIndex"=dword:00000001
"OverrideACSettingIndex"=dword:00000001
"OverrideDCSettingIndex"=dword:00000001
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\48df9d60-4f68-11dc-8314-0800200c9a66\b29c73e0-1a8b-46fd-b4ae-1ce5a3d6d871]
"FriendlyName"=hex(2):4c,00,6f,00,77,00,20,00,50,00,6f,00,77,00,65,00,72,00,20,\
  00,4d,00,6f,00,64,00,65,00,20,00,53,00,65,00,74,00,74,00,69,00,6e,00,67,00,\
  00,00
"Description"=hex(2):53,00,70,00,65,00,63,00,69,00,66,00,79,00,20,00,74,00,68,\
  00,65,00,20,00,4c,00,6f,00,77,00,65,00,72,00,20,00,50,00,6f,00,77,00,65,00,\
  72,00,20,00,4d,00,6f,00,64,00,65,00,20,00,73,00,65,00,74,00,74,00,69,00,6e,\
  00,67,00,20,00,66,00,6f,00,72,00,20,00,49,00,6e,00,74,00,65,00,6c,00,28,00,\
  52,00,29,00,20,00,44,00,79,00,6e,00,61,00,6d,00,69,00,63,00,20,00,54,00,75,\
  00,6e,00,69,00,6e,00,67,00,20,00,53,00,65,00,74,00,74,00,69,00,6e,00,67,00,\
  73,00,00,00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\48df9d60-4f68-11dc-8314-0800200c9a66\b29c73e0-1a8b-46fd-b4ae-1ce5a3d6d871\0]
"FriendlyName"=hex(2):44,00,69,00,73,00,61,00,62,00,6c,00,65,00,64,00,00,00
"Description"=hex(2):44,00,69,00,73,00,61,00,62,00,6c,00,65,00,20,00,4c,00,50,\
  00,4d,00,20,00,4d,00,6f,00,64,00,65,00,00,00
"SettingValue"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\48df9d60-4f68-11dc-8314-0800200c9a66\b29c73e0-1a8b-46fd-b4ae-1ce5a3d6d871\1]
"FriendlyName"=hex(2):41,00,70,00,70,00,20,00,53,00,70,00,65,00,63,00,69,00,66,\
  00,69,00,63,00,00,00
"Description"=hex(2):53,00,65,00,74,00,20,00,41,00,70,00,70,00,6c,00,69,00,63,\
  00,61,00,74,00,69,00,6f,00,6e,00,20,00,53,00,70,00,65,00,63,00,69,00,66,00,\
  69,00,63,00,20,00,4c,00,50,00,4d,00,20,00,4d,00,6f,00,64,00,65,00,00,00
"SettingValue"=dword:00000001
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\48df9d60-4f68-11dc-8314-0800200c9a66\b29c73e0-1a8b-46fd-b4ae-1ce5a3d6d871\2]
"FriendlyName"=hex(2):4c,00,50,00,4d,00,20,00,53,00,65,00,74,00,20,00,49,00,6e,\
  00,64,00,65,00,78,00,20,00,32,00,00,00
"Description"=hex(2):53,00,65,00,74,00,20,00,4c,00,50,00,4d,00,20,00,49,00,6e,\
  00,64,00,65,00,78,00,20,00,32,00,00,00
"SettingValue"=dword:00000002
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\48df9d60-4f68-11dc-8314-0800200c9a66\b29c73e0-1a8b-46fd-b4ae-1ce5a3d6d871\3]
"FriendlyName"=hex(2):4c,00,50,00,4d,00,20,00,53,00,65,00,74,00,20,00,49,00,6e,\
  00,64,00,65,00,78,00,20,00,33,00,00,00
"Description"=hex(2):53,00,65,00,74,00,20,00,4c,00,50,00,4d,00,20,00,49,00,6e,\
  00,64,00,65,00,78,00,20,00,33,00,00,00
"SettingValue"=dword:00000003
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\48df9d60-4f68-11dc-8314-0800200c9a66\b29c73e0-1a8b-46fd-b4ae-1ce5a3d6d871\DefaultPowerSchemeValues]
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\48df9d60-4f68-11dc-8314-0800200c9a66\b29c73e0-1a8b-46fd-b4ae-1ce5a3d6d871\DefaultPowerSchemeValues\381b4222-f694-41f0-9685-ff5bb260df2e]
"ACSettingIndex"=dword:00000000
"DCSettingIndex"=dword:00000000
"OverrideACSettingIndex"=dword:00000000
"OverrideDCSettingIndex"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\48df9d60-4f68-11dc-8314-0800200c9a66\b29c73e0-1a8b-46fd-b4ae-1ce5a3d6d871\DefaultPowerSchemeValues\8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c]
"ACSettingIndex"=dword:00000000
"DCSettingIndex"=dword:00000000
"OverrideACSettingIndex"=dword:00000000
"OverrideDCSettingIndex"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\48df9d60-4f68-11dc-8314-0800200c9a66\b29c73e0-1a8b-46fd-b4ae-1ce5a3d6d871\DefaultPowerSchemeValues\a1841308-3541-4fab-bc81-f71556f20b4a]
"ACSettingIndex"=dword:00000000
"DCSettingIndex"=dword:00000000
"OverrideACSettingIndex"=dword:00000000
"OverrideDCSettingIndex"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\48df9d60-4f68-11dc-8314-0800200c9a66\e6902942-b0cf-41f2-9225-20839490eb8c]
"FriendlyName"=hex(2):48,00,44,00,43,00,20,00,53,00,65,00,74,00,74,00,69,00,6e,\
  00,67,00,00,00
"Description"=hex(2):45,00,6e,00,61,00,62,00,6c,00,65,00,73,00,20,00,48,00,61,\
  00,72,00,64,00,77,00,61,00,72,00,65,00,20,00,44,00,75,00,74,00,79,00,20,00,\
  43,00,79,00,63,00,6c,00,69,00,6e,00,67,00,20,00,66,00,6f,00,72,00,20,00,49,\
  00,6e,00,74,00,65,00,6c,00,28,00,52,00,29,00,20,00,44,00,79,00,6e,00,61,00,\
  6d,00,69,00,63,00,20,00,54,00,75,00,6e,00,69,00,6e,00,67,00,20,00,53,00,65,\
  00,74,00,74,00,69,00,6e,00,67,00,73,00,00,00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\48df9d60-4f68-11dc-8314-0800200c9a66\e6902942-b0cf-41f2-9225-20839490eb8c\0]
"FriendlyName"=hex(2):44,00,69,00,73,00,61,00,62,00,6c,00,65,00,64,00,00,00
"Description"=hex(2):44,00,69,00,73,00,61,00,62,00,6c,00,65,00,20,00,48,00,61,\
  00,72,00,64,00,77,00,61,00,72,00,65,00,20,00,44,00,75,00,74,00,79,00,20,00,\
  43,00,79,00,63,00,6c,00,69,00,6e,00,67,00,00,00
"SettingValue"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\48df9d60-4f68-11dc-8314-0800200c9a66\e6902942-b0cf-41f2-9225-20839490eb8c\1]
"FriendlyName"=hex(2):45,00,6e,00,61,00,62,00,6c,00,65,00,64,00,00,00
"Description"=hex(2):45,00,6e,00,61,00,62,00,6c,00,65,00,20,00,48,00,61,00,72,\
  00,64,00,77,00,61,00,72,00,65,00,20,00,44,00,75,00,74,00,79,00,20,00,43,00,\
  79,00,63,00,6c,00,69,00,6e,00,67,00,00,00
"SettingValue"=dword:00000001
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\48df9d60-4f68-11dc-8314-0800200c9a66\e6902942-b0cf-41f2-9225-20839490eb8c\DefaultPowerSchemeValues]
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\48df9d60-4f68-11dc-8314-0800200c9a66\e6902942-b0cf-41f2-9225-20839490eb8c\DefaultPowerSchemeValues\381b4222-f694-41f0-9685-ff5bb260df2e]
"ACSettingIndex"=dword:00000000
"DCSettingIndex"=dword:00000001
"OverrideACSettingIndex"=dword:00000000
"OverrideDCSettingIndex"=dword:00000001
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\48df9d60-4f68-11dc-8314-0800200c9a66\e6902942-b0cf-41f2-9225-20839490eb8c\DefaultPowerSchemeValues\8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c]
"ACSettingIndex"=dword:00000000
"DCSettingIndex"=dword:00000001
"OverrideACSettingIndex"=dword:00000000
"OverrideDCSettingIndex"=dword:00000001
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\48df9d60-4f68-11dc-8314-0800200c9a66\e6902942-b0cf-41f2-9225-20839490eb8c\DefaultPowerSchemeValues\a1841308-3541-4fab-bc81-f71556f20b4a]
"ACSettingIndex"=dword:00000000
"DCSettingIndex"=dword:00000001
"OverrideACSettingIndex"=dword:00000000
"OverrideDCSettingIndex"=dword:00000001

 

No I still can't get into package C6 state. If you have some time try install Linux and check package c state there to determine if it's blocked by BIOS or Windows issue. I was doing some experiment today with MSI BIOS but no progress at all.

 

Indeed. Extremely detailed guide, which I've followed as much as possible.

I noticed that the CPU C0% for the first core spikes to ~50% whenever I move the cursor: it doesn't matter whether I use a USB mouse plugged into a USB-A port, plugged through an adaptor into a USB-C port, or while using the touchpad.

 

Hi, thanks for posting that updated version! Please see https://imgur.com/a/9alWERM for all my settings, including two shots from the limit reasons. Interestingly enough - as you suspected - none of the boxes turn red when throttling...but one time the "vr thermal" box suddenly appeared. I completely shutdown and restarted, and it didn't appear the 2nd time. ¯\_(ツ)_/¯

Also, here's the video I uploaded for Apple support. Note they of course required I reproduce in macOS...whatever! The crazy thing is after throttling occurs, it never seems to recover while the gpu is engaged despite ever-decreasing temps (the madness starts around 4:00): https://streamable.com/ea7jr

 

So is it advisable to update TS(From 8.50 non-expire version to 8.70.6 by copying ini file) on broadwell based chips esp. 5220U?
@unclewebb I think @kurtzyload might be partially correct on disk throttling not because its 70% full but temperatures above 70C will throttle the M.2 or custom Apple/Samsung NVMe/SATA drives. Maybe that is incorrectly signalling PCH to stop IO requests from/to SSD and inadvertently causing CPU to starve/throttle. Maybe I'm wrong! Apple always does what's best for consumer experience( Always!!!)

Well DPTF is disabled by Dell on some models because it kills CPU. @Freitz has a issue when undervolting the cpu and WHEA when undervolted and he got replacement mobo which had zero issues.

 

I know & I heard alot of horror stories related to DPTF but I'm sure that due to DPTF not functioning correctly which leads to problems & BSOD's alot.. I did alot of searching.. and always what I have found that people tend to only install the driver mostly & rarely others install through a setup from OEM websites I even saw people mod there BIOS to disable DPTF...but guess what....
All of them doesn't have those power settings! They don't add those registry settings at all ! I'm sure it's the reason why DPTF was functioning like a crazy.. Shame on $hity Intel if they did that intentionally

After I tweaked those power settings until now it didn't cause any kind of problems or any kind of stuttering or lag or even less performance... but what I did noticed is lower power consumption while on load or gaming without doing any kind throttle on CPU but it does indeed throttle the CPU Cache speed

I'm sure that those people who suffered alot of issues because of DPTF was not fully functioning... at the end DPTF goals was:-
1) Lower temperature while maintaining high performance
2) Lower power consumption which leads to lower temperature
3) Longer battery life

But all those goals was crippled by $hity Intel setups or drivers... I blame on Intel not DPTF

 

AHCI, AHCI Link Power management HIPM/DIPM is set to Lowest

I guess I can try a live version. Which program do you use to see it? What were your results in linux?

 

Interesting thought re: SSD temp, and one I didn't consider! Unfortunately (or fortunately, depending on how you look at it), the SSD remains a frosty 40C when throttling occurs.

 

Try searching my username on that guide's thread ( http://forum.notebookreview.com/thr...e-on-windows-enabling-deeper-c-states.815602/ ).

I remember fighting with my deeper C states being on again off again for various reasons. Are you using an external monitor? Is your dGPU completely off? Those were two issues I think I remember discovering that prevented my C states from working correctly.

 

NVMe SSD correct?
Use HWINFO64 to see avg. temps when using CPU and GPU concurrently when playing a game or running simulations on OpenCL/Vulkan/Metal?

 

Can someone point me at the TPL setting guide in here? I have a i7-8850h thats hitting power throttle. its undervolted currently and limited to 4ghz. I have v8.70 TS

 

That is possible but I think you are being too kind. When pressed hard, some reps will say some crazy things.

@kurtzyload - When using Limit Reasons, you can click on the headings to clear the previous throttling reasons. It is a good idea to do this before you do any testing. That way you are starting with, or should be starting with, a clean sheet of paper so to speak. Depending on the device, some of these limits will go back to yellow immediately after you try to clear them.

Does Apple think that it is normal for a CPU rated to run at up to 4.00 GHz to be limping along at only 1.00 GHz? Your video tells a sad tale. It will be interesting to see what they say about this. How did Apple become a trillion dollar company by producing products like this? Bizarre.

Does the add limit reasons to the log file option work correctly now too?

When running Windows, can you use ThrottleStop to overclock your CPU? The 4980HQ shows that it supports +6 bins of turbo overclocking. Max multis should be 46, 45, 42, 42. Not sure if the 46 and 45 would be stable but it would be fun to try. In the FIVR window, check the Overclock box, crank up the Turbo Ratio Limits, run a single thread TS Bench test and snap a screenshot while loaded. I like seeing big MHz numbers.

ThrottleStop is very flexible. When a new version comes out, I just copy the new ThrottleStop.exe over top of the old version. If the new version has some new features, it will automatically save any new options in the ThrottleStop.INI configuration file. You can also downgrade without any worries. If you do not like a newer version, you can copy an older ThrottleStop.exe into your ThrottleStop folder. Any new INI options that were created by the new version will simply be ignored by the older ThrottleStop version. I try to avoid any conflicts to keep life simple for users.

I do not think there is one. Would you like to write one for me? Not enough users are stopping here to post examples of how they have ThrottleStop setup. The Core i7-8750H is a very popular processor but you would never know it in this thread. I have spent hours and days specifically creating new ThrottleStop features to help these 6 core CPUs but without feedback, I have no idea what works and what does not. A trick that works to make one of these run faster in one manufacturer's laptop might not do anything in a different laptop.

The 8850H is a fast CPU but when pressed hard, it might be forever limited to 45 Watts. By design, it is going to naturally want to throttle to stay under its 45 Watt power limit. There might not be any solution for this. Have you tried checking off and using the new FIVR - Disable and Lock Turbo Power Limits option? After you do that, does increasing the turbo Boost Power Limits in the TPL window help any?

Throw me a bone. Post some pics and run some ThrottleStop Log Files so I can have a look at what your problem is. It is impossible for me to make any recommendations when I do not own the hardware and I do not have any idea how you have ThrottleStop setup or what you are trying to accomplish with it.

 

@unclewebb , there is a solution for the 8850H. (And the 8750H). This has been successfully tested on MSI laptops. (This has also been tested with the 7700HQ on some systems, e.g. GT73EVR HM175 version). Changing the IMON SLOPE to under 100 (which is 1.0x) will make the processor report it is using less power than it really is. Combine a value like IMON SLOPE =50 (50%), with a negative (-) IMON OFFSET and you can make a processor running at 45W report it's using 15 watts.

You would just need the registers to change for these values. It might not be as standardized as ICCMAX however.

 

Why I can't change the Turbo Boost short and long power? I already tried to reboot the laptop but no change, its fixed to 25/44

 

@unclewebb for all that you do for us and give to us, writing up some helpful documentation to complement your earlier work is the least we could do. I can't promise anything, but I hope to get to work on it in the near future to share with everyone here. Unfortunately I am on a 7700HQ on a locked down Dell so I can only contribute so much in that regard. Step 1 however, means learning everything inside and out the best that I can and taking notes so I can keep all the details straight... I don't know how you do it! (I guess my memory is terrible.)

 

Will definitely let you all know how this progresses with Apple. It is completely insane. @Vasudev - sorry, yes - nvme. Temp stays in the low 40C range.

It doesn't appear that they are going to the log file, assuming I'm reading it right...I just toasted everything with prime95, limit reasons immediately lit up "thermal" but an associated log entry is:

2018-09-21 05:38:50 39.48 1.4 100.0 100.0 51942 66 65 1.1129 7.3

And, your wish is my command! Here's how I set FIVR and the outcome (please let me know if I misconfigured something): https://imgur.com/a/Xh54K08

*edit* - I take it back! I cleared the log, un-checked and re-checked the limit options, and it is working now:

2018-09-21 06:24:00 36.18 51.9 100.0 100.0 51974 100 59 0.9852 43.6 TEMP
2018-09-21 06:24:01 32.77 99.9 100.0 100.0 51974 98 60 0.9215 72.6 TEMP
2018-09-21 06:24:02 31.77 99.9 100.0 100.0 51974 99 60 0.8921 68.1 TEMP
2018-09-21 06:24:03 31.31 99.9 100.0 100.0 51974 99 60 0.9215 64.0 TEMP
2018-09-21 06:24:04 30.96 99.9 100.0 100.0 51974 100 64 0.8921 63.7 TEMP
2018-09-21 06:24:05 30.58 99.9 100.0 100.0 51974 99 64 0.8627 61.8 TEMP
2018-09-21 06:24:06 30.32 99.9 100.0 100.0 51974 99 64 0.8627 60.8 TEMP
2018-09-21 06:24:07 30.22 99.9 100.0 100.0 51974 99 66 0.8627 60.2 TEMP

 

Ok, so with this "fresh" log running along with limit reasons, I fired up Skyrim and let it rip for a while. You can see my brief prime95 run where TEMP fires, and you can see my Skyrim launch around 6:29. For a while, it's running perfect @ 60fps, and then you can see the throttling start to happen @ 6:31:49. But, check out the bat_mw column...it hits 0 right when throttling occurs, and never recovers and the performance goes into the floor. Note that in this log, Skyrim is running the entire time - I closed TS before I closed Skyrim. Interesting??? Apple firmware doing something crazy related to the battery?

https://file.io/IIvPrV

 

Sounds dangerous. I love it!
If I ever figure out how to do this, I will definitely add this to ThrottleStop.

Have you done any testing of this or are you just going by what HWiNFO is showing you? There are multiple power limits and depending on when you start up HWiNFO, it might not detect what the lowest limit is set to. For a test, how about exit HWiNFO, set both power limits in ThrottleStop to 15 Watts and then run something simple like the TS Bench and see what TS reports for power consumption. If the TS Bench is not a big enough load, try running Prime95. Open up Limit Reasons to see if anything lights up in red. If TS is working correctly, you should see throttling to the 15 Watt level.

@Maleko48 - The problem I have with writing documentation is I do not have access to a wide variety of hardware. That gives me no way to test or properly document many of its features. That makes it difficult to write a coherent document that explains them all. My thoughts have always been, if you are the kind of guy that needs documentation, you probably shouldn't be using ThrottleStop. It is more for people that know how to use Google and can figure out how to search a forum or two. Being able to quickly read a few hundred pages of forum posts is also a good skill to have. The docs might improve someday but probably not. Hanging out in the forums is more fun. It keeps me busy and makes me feel important.

Your overclock does not appear to be working. Overclocking might be blocked. When you raise the multiplier in the FIVR - Turbo Ratio Limits section, try going back out to the main screen, check the Set Multiplier option and increase that to 46.

The log file shows temps of 99°C and 100°C and it also shows TEMP in the log file which confirms that you are bouncing off the 100°C temperature limit. It sure looks like Limit Reasons in the Log File is working correctly. Your fast CPU cannot be fully utilized because it has been installed in a laptop with with inadequate cooling. Maybe let Apple know that it is kind of dishonest to charge extra for a performance oriented processor when it cannot be fully used.

I could not download or see your second log file. The good old 404 error. 0 in the bat_mW column means the battery is not being charged and it is not discharging. If you are plugged in and the battery is discharging while loaded, that is a bad sign. Some manufacturers are using this trick so they can ship their laptops with a small but inadequate power supply. Maybe try attaching that log file to your next post. You can also copy and paste the data to www.pastebin.com and then post a link so I can have a look.

 

@unclewebb check your PM.
I believe "IMON" is a register just like ICCMAX, and it should be addressable without it being bios specific. That is if ICCMAX is addressed in the same way.

BTW I managed to get C7 state half working.
Look at this........

The cores are in C7 but the package is in C3.
What is going on here?
(and this only seems to work on battery power. On AC it stops at C3. Might be a processor % in ac plan i didn't change but I set everything to minimum on battery.....

 

@UNFORSWEATABLE - I did some testing and HWiNFO will read the Turbo Power Limits that are set by ThrottleStop but if you make any changes with ThrottleStop to these limits, you need to restart HWiNFO so it can read the change from the CPU. That part of HWiNFO is not being updated in real time.

A Core i5-7600 has a TDP of 65 Watts so typical turbo power limits are 65W for the long term limit and 80W for the short term limit.



If I use ThrottleStop and switch both of these power limits to 30 Watts, HWiNFO will keep reporting the previous values until I restart HWiNFO.



Is the 30 Watt limit actually being used by the CPU or maybe ThrottleStop is full of crap? To test for this, I start up the TS Bench and fully load the CPU with that.



Looks like ThrottleStop is correct. It reports that the CPU is throttling and it is pulling exactly 30.0 Watts. I am using the TS Clamp option so the multiplier has sagged down below the default multiplier to keep at or below the 30 Watt limit.

 

I have to admit.. I really really reeaallyy REALLY specialist on how to search... it is the reason why my laptop is begging to me to stop
I will always squeeze more performance.. squeeze hard.. soo hard that my laptop will tell me [Leave me alone you control freak!!]

Just give me some time.. I will show or give a hint to Intel how CPU will look like to be optimized from all way around
Watch my name... https://hwbot.org/hardware/processor/core_i7_6700hq/
Right now I'm leading on RAM in general , CPU Freq. and Reference Frequency...and more will come

I'm not showing off (you might say that) but... I'm just trying to say that if you really know what you are doing.. you will always find someway to surpass the hard limit ... always!

This laptop is with me for 2 years (closing to 3 years) now and I still find something new every other day.. Intel CPUs are really full of secrets.. you just need patience & to know how to solve the puzzle


by the way....

I love this.. is that a feature was on TS long time ago? or you just added this feature recently? anyway.. I love it

It remembers numbers the last time you used ICCMAX. If you want to get back to default.. just double click and if you want to go to what you choosed before.. also just double click on the sliders
Thanks @unclewebb !

 

First check your Windows Power Settings (The hidden ones) and second.. check your drivers

 

I'll play around with the overclocking a bit more tonight.

Thanks for the pastebin suggestion, here's a link: https://pastebin.com/ktnp8yZt

The 100C was during the max heat prime95 test, so not shocked there. Temps were relatively reasonable during the Skyrim run (6:29:30 onward). I'm actually pretty surprised at how good the thermal management is in this thing, which makes the throttling even more ridiculous. I have done a repaste, so that could be part of it.

 

Yes i restart the HWINFO after i set the Turbo Boost Limits. I just tried the TS Bench now, with both 20W / 25W and 40W but my PKG Power is nearly always around 24W. Looks like its locked. Later i will try to change it with XTU

 

You are not the only one. My GS73VR after a clean Windows 10 install can only get Package C state C2. Core C state can always reach C7 though. After installing Intel AHCI driver, it reaches package C3. I think we should start a thread in MSI forum to see if anyone can get MSI laptop into package C6. Feels like something wrong with BIOS.

 

Just enabled my GS73VR Speedshift in BIOS. Now Windows 10 can control EPP value using the power mode slider. Is there any reason to use TS to control EPP besides manually setting it ?

 

Well @unclewebb, looks like the overclock is no dice...still doesn't break the 4GHz barrier. =/

 

I don't know if this happens on every laptop. But in my case, changing power plan by using slider not only controls speedshift value, but also package power and multipliers. I'd rather let throttlestop control those settings.

 

Not sure but I thought EPP value affects package power and multipliers? Just did a quick TS Bench with 3 modes when charging and 4 modes using battery. The CPU reaches the max boost and package power in all except better battery and battery saver.

 

@ unclewebb I just checked the (i5-8250U) Turbo Boost Power Max and the Turbo Boost Short Power Max settings with XTU and if i set it from the default 25/44W to for example 20/40W the HWINFO64 can read it correctly. It's looks like the ThrottleStop can't change it from the default