The ThrottleStop Guide

TS was showing "TDP throttle", while HWinfo showed the other reasons. I *think* I may have fixed it. The Package Power Short was 45, which should have been 56. The Primary Plane Power Limit was 45, and it should have been 90.

 

you should fill the path to throttlestop.exe in the field "Start in" in Step 7. Otherwise tools like Limit reasons will not work from within the GUI of throttlestop !

 

Thanks unclewebb! I didn't noticed that but you are right, the exiting was due to task scheduler settings As for the AMD driver and temp reporting, i did a clean install just to make sure and it either a driver issue or AMD decided to change their code. This is driver 16.4.2, anything prior to that had no issues. I hope someone else with AMD confirms this is the case, and if a new driver fixes this i am going to report back!

 

Thanks for this tool, I've been using it since I got this laptop. My package C state never got into C6, it always been like this when idle




My laptop is Lenovo Y410p (i7-4700MQ, GT 750M, 16GB, modded BIOS)

 

Couple of quick things:
Are you plugged into AC power?
Are you using High Performance mode?
Are you using the touch screen or a tablet pen?

All of these prevent the CPU from entering package C6 and C7 states on my laptop because there is a latency trade-off with entering C6 and C7 package states.

 

yup, I'm plugged into AC. Always been on High Performance. No, I don't have those device and my laptop is not touch screen. I'm on Windows 10. Just reinstall my windows recently since I'm upgrading to SSD.

 

Unplug and switch to Balanced. That should allow the CPU to drop into Package C6 and C7 states.

It makes sense that the processor doesn't enter Package C6 and below states on AC power - this effectively turns the entire CPU off and there is a latency trade off in doing so. That's the same reason why using touch screen and or tablet pen prevents the CPU entering Package C6 states.

Finally, there are package states even lower than the C7 state which throttlestop is capable (or is programmed) to show - although this is unlikely given you are plugged in and on high performance. It may be that your computer is in a C8, C9 or C10 state - have a look at this guide from Anandtech.

Edit: Actually that last statement is not possible given your CPU is 90% in C3.

 

Thanks @plazing for all of your pics. That makes it a lot easier for me to see TS in action without having to ask a million and one questions.

I have the very similar Y510P and it uses package C6 whether it is plugged in or on battery power. I am also using the Windows High Performance power profile in Windows 10. C8, C9 and C10 were introduced in the Haswell U and Y series CPUs but the 4700MQ does not use those so your CPU is not in one of those states.

One setting that I found that could prevent a CPU from entering package C6 was the Interrupt Response Limit. That is why I added that adjustment to ThrottleStop. Your screenshot shows your C3 IRL set to 66 which is the same as my 4700MQ. I have C6 IRL set to 106 which I think is the default setting and then for C7 IRL, I have that set to 88. On this laptop, C7 IRL seems to be the important one. If I decrease that setting to 80, that prevents my CPU from using the package C6 state and the deepest package C State then becomes C3 just like you are seeing.



A setting of 72 eliminates the Package C3 state.



Going down in steps of 8 when I reach 32, that eliminates all of the Package C States.



I thought this would be an interesting feature for all of the C State haters out there but I have not seen much testing. It seems to work differently depending on the processor or on how each individual manufacturer set up there CPU in the bios. Since we both have similar Lenovo laptops, perhaps playing with this setting will help you find your package C6 state. It lowers power consumption and heat when the CPU is lightly loaded. When you are using the Windows high performance profile, latency will probably not be an issue. Some of the SSD benchmark testing I have seen was done while using the Windows Balanced profile which prevents the CPU from running at full speed. This could be the most significant cause of the increased latency.

The other thing I noticed in your screenshots is that you are using the overclocking multipliers like 36 but the Overclock box is not checked. This box usually needs to be checked if you want to use the 36 multiplier on a 4700MQ. Run a single thread TS Bench test to see if your 36 multi is working or not. You should see a hair under 36 during this test.

Edit - I just noticed that you are using a modded bios. Double check in there to see if there are any C State adjustments.

 

This is the BIOS mod I'm using , v3.05. There is tons of setting in the BIOS, I don't really touch them since I'm not sure what they do. I don't overclock unless I want to do benchmark, and yes it goes to 36 multiplier when doing single threaded TS Bench.

https://www.techinferno.com/index.p...ked-bios-wlan-whitelist-mod-vbios-mod/&page=1

 

Did you ever see your CPU using Package C6 when you were on the original bios?

That unlocked bios has a million and one features. I plan to install it someday but I haven't got around to it yet. There could be an item in there that is limiting your package C States. Did you try playing with the C7 IRL setting in ThrottleStop?

 

Very interesting... for me, the only reliable way to enable C6 and C7 on AC power is to switch to "power saver" battery profile. This is even if I make all of the settings in there the same as the Balanced profile.

Strangely the only difference between power plans is the internal GUIID which Windows 10 assigns to it. Wondering what other people are experiencing. Create a new power plan based off Power Saver and change all the settings so that they are like balanced - my laptop now enters the C6 and lower states.

 

It only uses package C6 when I'm on Balanced/Power Saver profile with battery. Here are the C-States option on the BIOS, all of it in its default value.

 

Interesting find @illuzn

There are a lot of hidden settings associated with each Windows power profile that a user does not have easy access to. The best way to fully examine each power profile is switch to that profile and then open up a command window and type in this command.

powercfg -qh >C:\report.txt

-q stands for query and the h option will include the hidden entries.

> redirects the output of the powercfg command so all this info goes into a file called report.txt which will be created in the main C: directory. If you do not redirect the output, it will scroll all over the screen and you will probably not be able to go back to the beginning and see all of the entries.

I think what C States are used is a combination of how the bios sets up your CPU as well as what Windows wants.

@plazing - Maybe the Demotion - Package C State option needs to be enabled. Not sure. Hopefully illuzn finds an easier way to get all of the package C States working.

 

Perhaps it's useful to reveal those hidden settings in the Power Options menu. Made a small Google sheet some years ago that generates an 'unhide' for every item it finds on the system. Haven't checked it once since then, but just did so and, sure enough, it's still working ...

Spoiler: spreadsheet output, run to unhide

Code:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\0012ee47-9041-4b5d-9b77-535fba8b1442\0b2d69d7-a2a1-449c-9680-f91c70521c60]
"Attributes"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\0012ee47-9041-4b5d-9b77-535fba8b1442\80e3c60e-bb94-4ad8-bbe0-0d3195efc663]
"Attributes"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\0012ee47-9041-4b5d-9b77-535fba8b1442\dab60367-53fe-4fbc-825e-521d069d2456]
"Attributes"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\238C9FA8-0AAD-41ED-83F4-97BE242C8F20\25DFA149-5DD1-4736-B5AB-E8A37B5B8187]
"Attributes"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\238C9FA8-0AAD-41ED-83F4-97BE242C8F20\7bc4a2f9-d8fc-4469-b07b-33eb785aaca0]
"Attributes"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\238C9FA8-0AAD-41ED-83F4-97BE242C8F20\A4B195F5-8225-47D8-8012-9D41369786E2]
"Attributes"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\238C9FA8-0AAD-41ED-83F4-97BE242C8F20\abfc2519-3608-4c2a-94ea-171b0ed546ab]
"Attributes"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\238C9FA8-0AAD-41ED-83F4-97BE242C8F20\d4c1d4c8-d5cc-43d3-b83e-fc51215cb04d]
"Attributes"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\245d8541-3943-4422-b025-13a784f679b7]
"Attributes"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\29e6fab8-ce22-4a98-9d8b-75fe10526ac7\a1c4769d-6eb7-4162-b11e-b69e691038e4]
"Attributes"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\2adaa5b8-1289-467b-a809-b95c40d27b4c\c9c2796d-df60-4e51-88af-d2b71eb3a3ba]
"Attributes"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\4f971e89-eebd-4455-a8de-9e59040e7347\833a6b62-dfa4-46d1-82f8-e09e34d029d6]
"Attributes"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\4faab71a-92e5-4726-b531-224559672d19]
"Attributes"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\54533251-82be-4824-96c1-47b60b740d00\06cadf0e-64ed-448a-8927-ce7bf90eb35d]
"Attributes"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\54533251-82be-4824-96c1-47b60b740d00\0cc5b647-c1df-4637-891a-dec35c318583]
"Attributes"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\54533251-82be-4824-96c1-47b60b740d00\1299023c-bc28-4f0a-81ec-d3295a8d815d]
"Attributes"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\54533251-82be-4824-96c1-47b60b740d00\12a0ab44-fe28-4fa9-b3bd-4b64f44960a6]
"Attributes"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\54533251-82be-4824-96c1-47b60b740d00\2ddd5a84-5a71-437e-912a-db0b8c788732]
"Attributes"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\54533251-82be-4824-96c1-47b60b740d00\3b04d4fd-1cc7-4f23-ab1c-d1337819c4bb]
"Attributes"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\54533251-82be-4824-96c1-47b60b740d00\40fbefc7-2e9d-4d25-a185-0cfd8574bac6]
"Attributes"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\54533251-82be-4824-96c1-47b60b740d00\447235c7-6a8d-4cc0-8e24-9eaf70b96e2b]
"Attributes"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\54533251-82be-4824-96c1-47b60b740d00\45bcc044-d885-43e2-8605-ee0ec6e96b59]
"Attributes"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\54533251-82be-4824-96c1-47b60b740d00\465e1f50-b610-473a-ab58-00d1077dc418]
"Attributes"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\54533251-82be-4824-96c1-47b60b740d00\4b92d758-5a24-4851-a470-815d78aee119]
"Attributes"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\54533251-82be-4824-96c1-47b60b740d00\4d2b0152-7d5c-498b-88e2-34345392a2c5]
"Attributes"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\54533251-82be-4824-96c1-47b60b740d00\5b33697b-e89d-4d38-aa46-9e7dfb7cd2f9]
"Attributes"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\54533251-82be-4824-96c1-47b60b740d00\5d76a2ca-e8c0-402f-a133-2158492d58ad]
"Attributes"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\54533251-82be-4824-96c1-47b60b740d00\68dd2f27-a4ce-4e11-8487-3794e4135dfa]
"Attributes"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\54533251-82be-4824-96c1-47b60b740d00\6c2993b0-8f48-481f-bcc6-00dd2742aa06]
"Attributes"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\54533251-82be-4824-96c1-47b60b740d00\71021b41-c749-4d21-be74-a00f335d582b]
"Attributes"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\54533251-82be-4824-96c1-47b60b740d00\7b224883-b3cc-4d79-819f-8374152cbe7c]
"Attributes"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\54533251-82be-4824-96c1-47b60b740d00\7d24baa7-0b84-480f-840c-1b0743c00f5f]
"Attributes"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\54533251-82be-4824-96c1-47b60b740d00\8809c2d8-b155-42d4-bcda-0d345651b1db]
"Attributes"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\54533251-82be-4824-96c1-47b60b740d00\8f7b45e3-c393-480a-878c-f67ac3d07082]
"Attributes"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\54533251-82be-4824-96c1-47b60b740d00\943c8cb6-6f93-4227-ad87-e9a3feec08d1]
"Attributes"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\54533251-82be-4824-96c1-47b60b740d00\984cf492-3bed-4488-a8f9-4286c97bf5aa]
"Attributes"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\54533251-82be-4824-96c1-47b60b740d00\9ac18e92-aa3c-4e27-b307-01ae37307129]
"Attributes"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\54533251-82be-4824-96c1-47b60b740d00\a55612aa-f624-42c6-a443-7397d064c04f]
"Attributes"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\54533251-82be-4824-96c1-47b60b740d00\c4581c31-89ab-4597-8e2b-9c9cab440e6b]
"Attributes"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\54533251-82be-4824-96c1-47b60b740d00\c7be0679-2817-4d69-9d02-519a537ed0c6]
"Attributes"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\54533251-82be-4824-96c1-47b60b740d00\d8edeb9b-95cf-4f95-a73c-b061973693c8]
"Attributes"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\54533251-82be-4824-96c1-47b60b740d00\df142941-20f3-4edf-9a4a-9c83d3d717d1]
"Attributes"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\54533251-82be-4824-96c1-47b60b740d00\dfd10d17-d5eb-45dd-877a-9a34ddd15c82]
"Attributes"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\54533251-82be-4824-96c1-47b60b740d00\e70867f1-fa2f-4f4e-aea1-4d8a0ba23b20]
"Attributes"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\54533251-82be-4824-96c1-47b60b740d00\ea062031-0e34-4ff1-9b6d-eb1059334028]
"Attributes"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\7516b95f-f776-4464-8c53-06167f40cc99\82DBCF2D-CD67-40C5-BFDC-9F1A5CCD4663]
"Attributes"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\7516b95f-f776-4464-8c53-06167f40cc99\90959d22-d6a1-49b9-af93-bce885ad335b]
"Attributes"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\7516b95f-f776-4464-8c53-06167f40cc99\A9CEB8DA-CD46-44FB-A98B-02AF69DE4623]
"Attributes"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\7516b95f-f776-4464-8c53-06167f40cc99\EED904DF-B142-4183-B10B-5A1197A37864]
"Attributes"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\7516b95f-f776-4464-8c53-06167f40cc99\FBD9AA66-9553-4097-BA44-ED6E9D65EAB8]
"Attributes"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\e276e160-7cb0-43c6-b20b-73f5dce39954\a1662ab2-9d34-4e53-ba8b-2639b9e20857]
"Attributes"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\f693fb01-e858-4f00-b20f-f30e12ac06d6\191f65b5-d45c-4a4f-8aae-1ab8bfd980e6]
"Attributes"=dword:00000000

Spoiler: unhidden Power Options options

 

Okay showing hidden options definitely causes a lot more settings to be revealed.

My methodology was to print out both my balanced policy and my high performance policy to a text file and then use MS Word to compare entries.

I was looking for entries where:
1. AC and DC settings were different in the balanced policy.
2. DC settings were different between balanced and high performance policies.

I then changed each entry one by one using powercfg to see its effect on C6 and C7 states. I then switched policies to enable those new settings.

That didn't work though so my conclusion is either:
1. There is a complex combination of multiple settings that enables C6 and C7 states.
2. I need to restart my computer in order to refresh the power profile.

Here is what my C7 window shows in High Performance mode:


and Balanced Mode (I have deliberately disabled CPU scaling here for parity):


Question @unclewebb, how relevant are all these threshold and scaling parameters on Skylake (I saw a whole heap of them in the hidden powercfg settings too) now that Microsoft Windows 10 has handed control of this back to Intel? I just had a random thought that this may be why my C7s settings literally do nothing at all.

 

Intel Dynamic Storage Acceleration (LakeTiny) can affect C-States

 

does it have something to do with Lenovo Energy Management, since I'm using Optimized Battery Mode?

is it same as Intel RST?

 

Can be a part of it.

 

I must say that I perhaps have quite a bit the chip in my surface pro 4. -100.6 undervolt in everything (CPU\Cache\iGPU). Stable in prime95 and games. Throttle stop really brings a whole new level of power in this surface....

 

@Eason Dell XPS 9550 probably uses the same cooling design as 9530, where GPU and CPU are side by side on the motherboard, and connected to a single heat pipe which extends to 2 fan modules on the sides.

What happens here is that the GPU practically cooks the CPU because of the common heatpipe.

If you run Throttlestop and GPU-Z to observe things it will become damningly clear: run Furmark or other GPU heavy test and watch your CPU not just get to PROCHOT 97, but actually shut down half of the cores due to overheating! The cpu don't need to do anything, all the heat comes from the GPU. If you want to see your system die from heat overload, add Prime95 into the mix.

It's a retarded design but seems Dell doesn't have any problems selling crap to consumers. GPU max temps are way hotter than CPU, so the engineer who came up with this braindead design probably got his degree from a printer...

And in case you come up with the genius idea of cutting the heat pipe into two halves because there's 2 fans, it won't work because the heat load on the system is such that the cpu alone needs the full cooling power of those 2 fans when stressed to max (with prime95 for example). Actually they're not even enough: on a system with base speed 22 and turbo up to 34, the system will struggle to perform even at the base. Probably will be thermally throttled down to 17-18 on average. Miserable.

And as the heat load from the GPU is greater, the engineers should have known they cannot put 2 units of heat load into a system that's barely capable of cooling 1 unit of heat load, and expect things to work smoothly, or at all. The cooling solution is not adequate for either gpu or cpu alone, much less both together.

Or maybe they did know, but their boss told consumers are idiots and will buy this **** anyway...like I did.

The only way to truly solve this is to re-engineer the whole cooling solution and issue a global recall. It's up to anybody's guess how many millions of thermally crippled systems Dell has sold so fat chance of that happening!

So next time you want to buy a performance laptop, demand figures showing it running Throttlestop, GPU-Z, Prime95 and Furmark all at the same time, without throttling. Or prepare to become conned Dell customer who bought into their slick marketing.

 

I appreciate the post, but the temperatures were fine. Never went above 78/82 for any period of time.

It was actually a throttlestop setting that was in my .ini from my previous notebook that caused it; it's been fixed.

 

Hello @Mr. Fox

I noticed in one of your excellent videos that you were having problems with the ThrottleStop - Set Multiplier feature on your 6700K. When you have a chance, can you try testing with SpeedStep enabled. In theory, enabling SpeedStep should let you access the multis from 8 to 40.

 

Hi @unclewebb

I have the SpeedStep box checked. The Set Multiplier feature on the main program screen is ignored, but the ratios are adjustable on the FIVR screen.

Here is what I have discovered... Above 40x the Set Multiplier values are ignored. In other words, I can set 40, 39, 38, etc. If, for example, my core ratio is currently set at 47x4 as soon as I select 41x in the Set Multiplier box the CPU jumps right up to 47x4 (or whatever I have the core ratio set to on the FIVR screen or in the BIOS). Since I can adjust the core ratios on the FIVR screen, this is not adversely affecting my experience with ThrottleStop in any way, but it would be nice if the feature worked at clock speeds beyond 40x. I have been making any desired core clock changes on the FIVR screen with Skylake rather than using the Set Multiplier option.

 

Would to to have this.

Also any one know how i can stop 3D Mark throttling my processor speeds down to 4Ghz. If i do anything like TS Bench or Prime95 the clock speeds (4.8Ghz+) hold without issues, but with 3D Mark and CineBench they drop to 4Ghz. Any idea why? My voltages seem to be fine, since i am not over heating or having any locksups/crashes.

 

I was gonna ask if your power brick can supply enough watts to your CPU & GPU when being stressed hard during benching, but normally power bricks will just shut off when they exceed their power limits, unless there is some other protection going on associated with the motherboard/BIOS.

 

I was using 2 x 330W bricks when benching at 4.8Ghz to 5 Ghz.

 

That's the same setup (dual power bricks), that Mr Fox has used when overclocking, so I should think you're not limited by that then, although I think I have seen some of his testing where Watts spiked briefly to something insane like 800 odd Watts, but the power adapters could handle that if only held for a short time. Always useful to have a KillaWatt meter to see what your laptop is sucking in Watts. Probably another reason for your throttling though.

 

Yeah i have a Kill-A-Watt and everything's under limits.

 

Ah, well that's good news that you know it's operating within the limits of the power bricks, so it's not that then - I'll have to let someone else help you that has experience with your Clevo/Throttlestop & overclocking.

 

CPU clock speeds dropping under a combination of extreme CPU and GPU load without ThrottleStop to help circumvent that nonsense is common on laptops. This is especially true with 3DMark 11. It has been that way for as long as I can remember, but ThrottleStop has always stopped that for me as long as the correct BIOS settings are used, and that includes disabling a lot of things to stop the CPU and GPU from communicating with the BIOS and EC.

Unfortunately, most laptops are engineered with a goal of protecting hardware from idiot owners and managing power consumption. These "features" can be an overclocker's arch enemy. I want my machines to do whatever I tell them to do, even if that means they are ultimately going to be destroyed by following my orders. Laptops use firmware that generally won't allow that to happen as easily as desktops will.

As far as settings are concerned, I see you have BDPROCHOT enabled, HyperThreading and SpeedStep disabled. I do the exact opposite. I also disable Watchdog Timers, ACPI features and everything I can find access to with respect to thermal sensors and power management. I don't want my parts talking to the firmware or the firmware telling my parts to follow orders contrary to my settings. I don't want or need any protection features coming from firmware. In addition to disabling every sensor I can find, I max out everything relating to power limits except voltage. I hold back on the voltage only because I have to. Voltage is the only thing where too much is a bad thing, but so is not enough.

 

OOOOoh, gotcha! That makes sense. Thanks for explaining that, i didnt quite get the time to test out all the options, but it was much more easier to play and tweak settings with. Is there any way i donate to @unclewebb ?
Ill give it a shot on Thursday or Friday once again. Lets see if i can beat Papusan this time .

 

@bloodhawk - Donation is a dirty word on the NBR forums so I do not talk about that here. Got to keep the mods happy. Thanks for the offer.

@Mr. Fox - Set Multiplier needs SpeedStep enabled and it also needs the Non Turbo Ratio in the FIVR window set to zero. Can you try testing that? Intel makes things overly complicated so it is possible that there is some other obscure setting that is blocking this feature on your laptop. On my desktop Skylake i3-6100, I can run any of the lower multipliers without issue so in theory, you should be able to do the same on a 6700K.

 

@unclewebb
@Mr. Fox
I have just moved across to throttlestop from xtu as many people have told me it is far superior. I have noticed you have just brought up a link to a video Mr. Fox made about current thermal throttling on the 6700k. Now I know this has been cured by Prema with modded Bios, but my question is will I be able to limit or completely negate this happening on my machine (p771dm-g) that is still running stock Bios with the use of throttlestop?

Sent from my SM-N910F using Tapatalk

 

Dude ... if that's ' within limits' ... pretty please, direct us to your dealer ...

 

Oh lol, I meant for 2 Bricks .

 

@bloodhawk your first pic shows EDP limiting? As Mr. Fox points out there are a lot of reasons for throttling and curing one can lead to another.

Seems your turbo might have been disabled or power limited to base frequency. Perhaps you could try a higher bclk such as 40x 125MHz which would give you 5GHz while at base multi and therefore no turbo throttling Voltage slope will be a mess but might be worth experimenting to see if it works, throttles with MPO or gives up trying to throttle and shuts down.

Great clocks BTW, watch out with the voltage and current. Would be a real shame to kill that CPU.

 

Yeh, it has something to do with the Voltage being limited. My temps are well within limits. I was able to lock down the 4.9Ghz for Wprime, but as soon as i try CineBench or FireStrike Physics test, they start dropping to 4Ghz.
Spent like 40 mins trying to lock things down using TS, but haven't been able to. They end up falling to 4Ghz and then never going back up unless i restart the system.
Kinda about to give up, haven't been able to figure out why this is happening . This same processor in a desktop can hold 5Ghz @ 1.425v and stays super cool using an AIO cooler.

Would really appreciate it someone can guide me on how to use TS to lock my frequencies and the corresponding BIOS intricacies. When i OC to 4.7Ghz using the BIOS only, the clocks stick no matter what.
@Mr. Fox @Papusan

 

Why not try using my BIOS settings and then use ThrottleStop to fine tune everything? Your 6700K may not be able to hold turbo clock at 4.8GHz or higher. The one I have in the Sky X9E won't most of the time. But, it never budges from 4.7GHz and the temps are fine.
[parsehtml]<iframe width="853" height="480" src="https://www.youtube.com/embed/QQjE3U1Oq5Q?rel=0" frameborder="0" allowfullscreen></iframe>[/parsehtml]

@unclewebb, I cannot set the core ratios less than 40 on the FIVR screen. 40 is as low as they will go.

 

How does this look? Good old 3DMark 11 Test #1... brutal, LOL. Pretty sweet, huh? @Prema vBIOS FTW. 125W over stock TDP.
Now, if we could just have two of these 200W 980 monster cards in SLI we would be set.

 

Awfully hot for a single 980 there...

 

Nah, no worries. Just ran 3DMark 11 Test #1 to see how much power it was slurping up. That insane overclock was with the machine sitting in my lap in my living room recliner with the automatic fan profile. Needs to be on AC for that kind of benching. Not too bad for stock paste and pads, though. But, yeah... 325W is a lot of power for one GPU.

 

Edit: For some reason I thought it was 95C. I guess low 80s are still acceptable.

Still remember when Fermi runs at 95C.

@unclewebb Would throttlestop still work for future Broadwell E systems? I noticed that TS only tracks up to 8 cores/threads. I am planning on a new Broadwell E system and would love keep using your software to overclock!

I also would be ok with playing the guinea pig when I build the system to iron out bugs!

 

Ahh, let me give those settings a shot. When i tried to change things with my 4.5Ghz settings TS wasn't able to change anything. Im guessing that was because of the core multiplier being set to 45 in the overclocking menu.

 

BIG FRRAKING ALL CAPS THANK YOU FOR THE VIDEO!!
I managed to cook a mix of settings based on what you did i the video , and now the clocks hold steady at 4.8 and 4.9 Ghz.
Managed to get upto 11.65 in Cinebench 11.5 .
But having a really weird problem with Firestrike Physics test. The FPS starts out at a good 50+ , but suddenly drops to 10-20 fps for a few seconds and then steadies around 45. Not sure why that is happening. When doing Cinebench, everything holds super steady. Any clue ?
I'm not having any voltage warnings like before, so seems that everything is well under limits.

 

Throttlestop 8.20 available for download yet?

 

The multipliers in the FIVR screen control the amount of turbo. The 6700K has a default multiplier of 40 so it is correct that this adjuster can only be adjusted from 40 and up.

In the FIVR screen, what do you have the Non Turbo Ratio set to? If you set the Non Turbo Ratio to 0, I think the Set Multiplier adjuster on the main screen should work properly from 8 to 40 or from 8 to your maximum turbo ratio.

The future is now. With a few very minor adjustments, TS should work just fine on Broadwell E. All of the FIVR stuff works pretty much the same on Haswell, Broadwell or Skylake. No money in my piggy bank to buy a 10 core Broadwell E system so someone that can help with development is just what I am looking for. Send me a PM when you have some new toys.

I have been slacking off lately. Thanks for the reminder. I need my arm twisted once in a while. The @Papusan edition is almost ready to go.

 

Ah, thanks.

In another note, I still can't get the 4700MQ to turbo 3.4ghz indefinitely (single core benchmark still stuck 3.4)

 

+++ Rep added. I really like the version name Maybe put it into the read me file

 

Will do.

 

I tried setting the non-turbo ratio to zero and that did not work. 40 was still as low as I could set.