The ThrottleStop Guide

I'm only looking to break cpu benchmark, not combined. So I think even if the brick is 180w, it'll be fine?

How much is the price for an unlock system bios from svet?

 

Yeah, probably.

I don't know, I think it's $5 or $10 or something like that. But check around on the MSI forums and see if they have unlocked TDP first before trying out Svet, and if they DON'T, then ask Svet if his BIOS will grant that before getting it.

If the answer to both options is "no", then you might be able to handle it with powercut or an EC hack from Dufus, but then your power readout won't reflect what your system is actually drawing. The CPU however should function properly.

 

Does svet's bios actually do anything else rather than unhide options in the bios? Or most OC voltages can be accessed through throttlestop?

I'll try poking around msi forums if they can answer this.

 

It's basically like a Prema Mod for MSI, but not as thorough/good from my understanding of it. So yes, something like unhiding things. If there's an inherent problem (like the GT70 Haswell/Kepler models treating MQ chips like HQ ones and throttling to 47W after 2.5 minutes) then Svet's won't do anything. But if TDP consumption is locked by default and there is an option to unlock it with the unlocked BIOS, then that would work.

As far as I know, throttlestop should be able to access everything important about the CPU, including voltage/current limit/OC bins/cache/cache voltage/etc.

Good luck! I hope you find the answer (and that the answer is that it's unlocked by default).

 

Think that 1.45v for 4.4 or higher is a decent OC for 6820HK?

This is currently the world fastest 6820HK on superpi: http://hwbot.org/submission/3183082_mostafa_abbasi_superpi___32m_core_i7_6820hk_7min_41sec_899ms

 

1.45v? That seems extremely high for 4.4GHz... @Plur's 6700K does like 4.6GHz on 1.25v or so, I think.

Though I've heard 1.48v should be ok for Skylake in general at max, so good luck I guess. Not sure how you'll manage to cool that, though.

 

120MM AIO instead of the flimsy CPU heatsink

 

1.45v for 4.4 GHz is crazy. Even with idle voltage this is all to high!! Damn crippled silicon in BGA design!! And with crippled cooling you will start a fire 1.45 is more than enough for 4.9 GHz on Skylake.

 

On desktop chip it may be, but this is a badly binned BGA model we're talking about.

 

Badly binned or not... Not the first time I hear about the Silcon junk from Intel. HQ or Hk chips doesn't matter. Easy way for Intel to get rid of their last junk!!

 

Yeah, I feel like the HQ/HK series are just a dumpster for failed desktop chips.

 

Yes it does

 

Could someone please comment on how well Throttlestop works on an Core M-5Y71 (if at all)?

I am trying to decide between an i5-4300Y (HD 4200) and a Core M-5Y71 (HD5300) device for gaming performance. I've read about the i5-4300Y on this thread but I'm assuming the very low TDP of the Core M-5Y71 will drastically lower the gains to be had from controlling throttling if it can even be done which will cancel out any advantages of the newer iGPU.

Anyone care to correct/confirm please?

Thanks.

 

Whenever I try to run this with the settings in OP my laptop crashes or goes into BSOD.

am I doing something wrong?
my laptop is s lenovo y50.

 

Try less aggressive settings.

Every CPU is different; even the exact same SKU varies in abilities to overclock/undervolt.


Sent from my iPhone using Tapatalk

 

So True! Even my Haswell 4790K furnace does 4.5GHz @ 1.247V ..

Death to BGA! Junk is Junk!

 

no wonder even the 4900mq can't max the bins at 4.2

 

I'd first try to overclock up to a frequency you find suitable. On my Y50 I have 4.3GHz for single core and lower for multi (uCode 02), your requirements may vary.
After setting a frequency try with small undervolt steps for both cache and CPU, of around -5mV. Run TSBench a couple times on each decrement until you hit a BSOD.
When you hit a BSOD raise the voltage a few mV for stability.

 

Having some issues with the XPS 9550, maybe someone can help.

It has the 6700HQ, with a package power long of 45W and a package power short of 56W. PROCHOT at 97 C. It has both integrated graphics and a 960M, and the 960m turns off (almost?) completely when it is not needed. The throttling I experience is almost always, if not always, PL1 throttling. PL1 drops from 45W to a much lower value, oftentimes as low as 7W. The drop is often (near?) instant, although sometimes it will take a few minutes to go from 45 W to ~17W to 7W. Sometimes it stays at 7W for a while, and sometimes it slowly climbs back up. Sometimes it slowly climbs back up, then freezes (maybe around 25 W), then slowly climbs down, then up. Temperatures don't seem to have much to do with it. Currently my CPU is at 55 C but PL1 is slowly oscillating around 25 W. Other times PL1 stays at 45W for hours at 85+ C.

I get inconsistent throttling behavior. When the dGPU is off, I usually get no throttling whatsoever. I have run multiple workloads that cause the CPU to draw a constant 45W and reach nearly 90 C for hours on end, with no throttling. However, occasionally I get throttling during these CPU-only workloads.

When the dGPU is on, throttling goes nuts. The CPU and dGPU could both be < 70 C, and doing a light workload, but the laptop will decide that it needs to throttle hard.

I've tried the basics (turning off BD PROCHOT, increasing the package power limits (this has no effect on their reported values in HWINFO), trying different BIOS/driver versions) but to no avail. Any ideas? One idea I had is that PL1 might be lowered based on a reading from some sensor outside of the CPU, e.g. a chassis temperature sensor located near the GPU. Maybe I could disable the sensor or change the value it reports? Or maybe I could trick the CPU into thinking it's drawing less power than it actually is? I know that throttlestop has such a feature (powercut?) but I don't see it documented anywhere.

 

Did you by any chance look in the readme file in the ThrottleStop folder? It's documented there...

 

Yes, you're right about that. I got it mixed up with some of the TPL settings that I can't figure out the function of.

 

@Squigglyboo - Unfortunately the PowerCut feature is only available on the early 4th Gen CPUs. Your 6th Gen Skylake is not supported.

Is it too late to tell Dell that they can have their throttling XPS 9550? I don't have any tricks up my sleeve to fix the throttling mess that you are describing.

It sounds like your laptop is entering a low TDP mode. Can you post some pictures of the main ThrottleStop window, the FIVR window and the TPL window so I can see how you have TS setup? There is probably nothing that ThrottleStop is going to be able to do for you but if I see something obvious, I will let you know what you can try.

Edit - Are you using the proper power adapter? How many watts is it rated at.

 

That seems in some ways similar to what I am experiencing - see my post here: http://forum.notebookreview.com/threads/the-throttlestop-guide.531329/page-388#post-10128108

The only partial fix I found was to undervolt my CPU but dropping package power from 45W to 7W sounds ridiculous.

I'm almost certain that some form of power limit throttling has been implemented but the problem for me is that there is no way for me to access whatever is causing it. HWInfo reports that it is a PL4 limit (i.e. some form of maximum current limiting) - so I'm assuming to save the battery longevity in my laptop or something it doesn't allow a 15W load on the battery for too long. After all, that is a 0.5C discharge which will significantly drop battery life in the long term if consistently done. Presumably the same but worse applies for a 45W load which is >1C

 

Strange, I have i7-6500u and some controls don't work. I can control voltage (all of them: cpu,cpu cache..., gpu) , some controls are locked and its fine, but TPL menu is unlocked and I can set even 125 TDP, don't think it does anything. But "Set Multiplier" is not working at all, if I set it on x4 it will still run as it usually does, but disabling turbo does limit the cpu multiplier to x25 .

 

I think some chips can't do that low of a multi, try x8 or higher.


Sent from my iPhone using Tapatalk

 

@kosta20071 - Make sue the Non Turbo Ratio in the FIVR window is set to zero (0) if you want to use the Set Multiplier feature. Also make sure you are using the Windows High Performance power profile with the Minimum processor state set to 100%.

The i7-6500U is a locked CPU. TDP might be adjustable but in most situations, long term, the CPU will ignore settings that are beyond the rated TDP. I don't have access to enough documentation or hardware for testing purposes so if I am not sure about a setting, I try to leave it wide open for users to experiment with. A setting that might not work on your laptop model might work on a different model. Manufacturers can change what a CPU is capable of depending on how they set it up in the bios so the same 6500U can perform quite different depending on what laptop model it is in.

 

Same here on my HP Spectre x360.

I'm almost certain that this is locked due to the BIOS not permitting these controls.

 

Hello,

Im using TS on a Dell M4600,
i5 2520m
8GB
Quadro 2000m
500GB HDD
250 mSSD Samsung EVO 850
Windows 7 Professional SP1 All Updates

The I5 was not running with full Speed, capped at 1,8Ghz, only if turned of SpeedStep in Bios it was running with 2,5Ghz, but was not slowing down anymore.
Also the C-States Options in Bios were causing some trouble, if the CPU went in deep-sleep, the voltage was to low and my Notebook turned off.


Now i try TS, and so far, its running great.
The only problem i have, it wont go off my task bar, its always there. I used minimize on close, task bar, start minimized, all kind of combinations, its always showing in the task bar.

I use Version 8.10

Maybe someone can help, thank you.

 

For most mobile Intel CPUs, SpeedStep and Turbo Boost should be enabled in the bios. If you want your CPU to clock down when it is idle, you adjust that by going into the Windows Power Options. You need to adjust the Minimum processor state to a low number like 5%. The Maximum processor state should always be at 100%.



On Dell laptops, if SpeedStep is disabled in the bios, your CPU can end up locked at a reduced speed.

If you do not want to see ThrottleStop minimized on the task bar then make sure the Task Bar option is not checked and make sure that the system tray icon is available.



In the Options if you have checked No Notification Area Icon, ThrottleStop will minimize to the Task Bar so it doesn't disappear. ThrottleStop needs to be able to minimize somewhere so you still have access to it.

If you have any troubles with the System Tray icons, read the information at the bottom of the included ReadMe file.

 

Hey the Programm itself is running fine, its perfect. I have no Problem there.

The real Problem is, i cant get it off my Taskbar. Maybe i need to re install the prgoramm?
Here are my settings, if i click on Close (X) Its still on my Bar



Edit:

I have 1 SSD for Windows, 1 HDD for Date and stuff, its going to sleep after 5 min.
If i run the Programm from the HDD, its running fine, i can close it and its in the Try Section.
If i run it form the SSD, C: it dosent work anymore, i cant minimze it to the Try Section, UAC is off
If i run in form the HDD, i cant check "show CPU" i think my system is cursed...

 

No need to re-install anything. You just need to read the directions in the ReadMe file about cleaning the Icon Cache.

This is mostly a Windows issue. If you move ThrottleStop from one folder to a different folder or to a different hard drive, Windows gets confused. Find a permanent spot for ThrottleStop, put it there and leave it there.

Every time you decide to move ThrottleStop around, you will need to Clean the Windows Icon Cache before starting ThrottleStop.exe in its new location.

When you move the ThrottleStop folder from one hard drive to a different hard drive, some versions of Windows will change the read write file permissions of the ThrottleStop.INI file. It is best to delete the ThrottleStop.INI file after you move the ThrottleStop folder so ThrottleStop.exe can recreate the INI file with the proper permissions.

 

I saw that in the TS folder, but i thought, nah no need to read that, at the end its always the User

Its working now, thank you very much. Great Program to get the CPU running like it should. Now i just need to watch the C-States and see if its working.

My Notebook crashed form time to time, if i activate the C-State Optoin in Bios. With TS i dont have that problem so far.

 

There are the core C States and when all of the cores are in the same C State, then the entire CPU package can drop into that same C State. I have never had any problems with having the core C States enabled. When overclocking my 3570K, I did have problems with the package C States. Disabling the Package C States seemed to fix the random BSOD issues. I have also heard that as processors age, some of them need slightly more core voltage to remain stable. A reliable voltage when a CPU is brand new might not be as reliable after a year or two.

Glad to hear that you got TS working. The next version of TS will try to come up with a new fix to work around this Windows feature.

 

@n=1 was able to max his bins out at 1.25v. I don't know of a bunch of 4900MQs that couldn't max their bins (heat permitting, of course; many Haswell-using machines simply had very bad cooling; you'd need to attempt it in an ASUS top-end ROG, an AW18/AW17 R1, or a P17xSM(-A)/P37xSM(-A) with some good modding of the case and a lapped heatsink (or even the P370EM CPU/slave GPU heatsink for the SLI models).

 

And the inability to max out bins or overclock past 4.2 is because the chip is significantly hotter than what have come before them?

 

4900MQ can't OC past 4.2 without the microcode bug. 3.6GHz default 4-core turbo +600MHz = max. 4910MQ would be limited to 4.3GHz.

Heat was the main problem with OCing haswell as far as I know, except the 4940MX chips which I've heard don't OC nearly as well as the 4930MX ones.

 

4940mx worse than the 4930mx?

 

According to @Mr. Fox and a couple others, yes. Just worse binning, I suppose?

 

sad to hear

PM me details if you want to run some test on the 4980HQ I got for 2 weeks here

 

I don't know that all of them everywhere are. I only know I have never seen even just one example of a good 4940MX that overclocks nicely.

 

So I managed to manually lock the package power limits and they won't unlock anymore. Isn't that crazy? I remember adjusting all the values manually but now it won't reset, only the ppo resets when I reboot or remove throttlestop. Maybe they where locked by the bios anyway and it only became apparent when I was trying to adjust them.


[/IMG]

 

throttlestop don't want to minimize to notification area, help?

 

Have you enabled the setting? You may also want to search how to clear the icon cache too.

 

problem fixed now, just had to clear the notif area icon

 

The mobile Haswell chips, the 4930MX, 4940MX were just ovens.. I think they're horribly binned 4790Ks so all these issues... My 4790K does 4.5Ghz easily on 1.2V...

 

I've had no issues (other than thermals) with 4930MX. The one I had easily handled 4.8-4.9GHz totally stable. @Papusan had great results with his 4930MX as well. Both of us found Liquid Ultra to be what the doctor ordered and thermal problems instantly became a non-issue using the right stuff.

Unfortunately, all Haswell CPUs have thermal issues. The 4790K in my P750ZM handles 4.8GHz fairly well if I keep it cool on AC, but it pulls around 200W clocked that high under 100% load, which the 4930MX did as well. 4940MX struggles with 4.3GHz and finding one that can manage 4.5GHz with grace is especially rare.

 

Hallo again,

The random crashes are still there

Thats the error message, out of the windows event log

Warnung 29.07.2016 23:07:09 Kernel-Processor-Power 37 (7)

Code:

The speed of  processor " 3 " in the group " 0 " is limited by the system firmware. Since the last report the processor is since 71 seconds in that state with reduced power .

Original Error in German

Code:

Die Geschwindigkeit des Prozessors "3" in der Gruppe "0" wird durch die Systemfirmware begrenzt. Seit dem letzten Bericht befindet sich der Prozessor seit 71 Sekunden in diesem Status mit verringerter Leistung.

I have this Error 4 Times, for each CPU Thread
processor " 0 " in the group " 0 "
processor " 2 " in the group " 0 "
processor " 1 " in the group " 0 "
processor " 3 " in the group " 0 "

Code:

Protokollname: System
Quelle:        Microsoft-Windows-Kernel-Processor-Power
Datum:         29.07.2016 23:07:09
Ereignis-ID:   37
Aufgabenkategorie:(7)
Ebene:         Warnung
Schlüsselwörter:
Benutzer:      SYSTEM
Computer:      me-PC
Beschreibung:
Die Geschwindigkeit des Prozessors "3" in der Gruppe "0" wird durch die Systemfirmware begrenzt. Seit dem letzten Bericht befindet sich der Prozessor seit 71 Sekunden in diesem Status mit verringerter Leistung.
Ereignis-XML:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Kernel-Processor-Power" Guid="{0F67E49F-FE51-4E9F-B490-6F2948CC6027}" />
    <EventID>37</EventID>
    <Version>0</Version>
    <Level>3</Level>
    <Task>7</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2016-07-29T21:07:09.632391100Z" />
    <EventRecordID>8127</EventRecordID>
    <Correlation />
    <Execution ProcessID="4" ThreadID="64" />
    <Channel>System</Channel>
    <Computer>me-PC</Computer>
    <Security UserID="S-1-5-18" />
  </System>
  <EventData>
    <Data Name="Group">0</Data>
    <Data Name="Number">3</Data>
    <Data Name="CapDurationInSeconds">71</Data>
    <Data Name="PpcChanges">1</Data>
    <Data Name="TpcChanges">0</Data>
    <Data Name="PccChanges">0</Data>
  </EventData>
</Event>

I have a Critical Error too
Kritisch 29.07.2016 23:05:54 Kernel-Power 41 (63)

Code:

The system has rebooted without it was shutting down first . This error can occur when the system has become unresponsive or has crashed or lost power unexpectedly .

The Throttelstop Log is cutting of @23:03:00 and starts again @23:07:19

Code:

   DATE       TIME    MULTI   C0%   CKMOD  CHIPM   BAT_mW  TEMP    VID   POWER
2016-07-29  23:02:01  17.22   18.0  100.0  100.0        0   56   1.0408    7.7
2016-07-29  23:02:02  18.15   21.1  100.0  100.0        0   55   1.0408    8.5
2016-07-29  23:02:03  17.85   19.1  100.0  100.0        0   56   1.0408    8.1
2016-07-29  23:02:04  17.60   19.8  100.0  100.0        0   56   1.0408    8.1
2016-07-29  23:02:05  16.07   18.3  100.0  100.0        0   55   1.0408    7.5
2016-07-29  23:02:06  17.73   18.0  100.0  100.0        0   55   1.0408    7.9
2016-07-29  23:02:07  17.43   16.9  100.0  100.0        0   55   1.0408    7.6
2016-07-29  23:02:08  18.29   19.4  100.0  100.0        0   56   1.0408    8.4
2016-07-29  23:02:09  17.72   17.4  100.0  100.0        0   56   1.0408    7.9
2016-07-29  23:02:10  17.37   19.7  100.0  100.0        0   56   1.0408    8.1
2016-07-29  23:02:11  17.78   17.6  100.0  100.0        0   56   1.0408    8.0
2016-07-29  23:02:12  18.48   22.4  100.0  100.0        0   56   1.0408    8.7
2016-07-29  23:02:13  17.88   19.9  100.0  100.0        0   56   1.0408    8.3
2016-07-29  23:02:14  17.79   18.5  100.0  100.0        0   56   1.0408    8.0
2016-07-29  23:02:15  17.48   17.3  100.0  100.0        0   56   1.0408    7.7
2016-07-29  23:02:16  17.82   18.7  100.0  100.0        0   57   1.0408    8.1
2016-07-29  23:02:17  17.36   18.2  100.0  100.0        0   57   1.0408    7.9
2016-07-29  23:02:18  18.69   24.5  100.0  100.0        0   58   1.0408    9.2
2016-07-29  23:02:19  18.58   24.3  100.0  100.0        0   59   1.0408    9.3
2016-07-29  23:02:20  18.76   26.3  100.0  100.0        0   58   1.0408    9.8
2016-07-29  23:02:21  18.21   20.9  100.0  100.0        0   59   1.0408    8.5
2016-07-29  23:02:22  18.17   19.1  100.0  100.0        0   57   1.0408    8.4
2016-07-29  23:02:23  18.13   19.2  100.0  100.0        0   59   1.0408    8.3
2016-07-29  23:02:24  17.54   18.3  100.0  100.0        0   57   1.0408    8.0
2016-07-29  23:02:25  18.01   18.2  100.0  100.0        0   58   1.0408    8.1
2016-07-29  23:02:26  17.77   18.2  100.0  100.0        0   57   1.0408    8.1
2016-07-29  23:02:27  17.82   18.1  100.0  100.0        0   58   1.0408    8.1
2016-07-29  23:02:28  17.98   18.6  100.0  100.0        0   57   1.0408    8.2
2016-07-29  23:02:29  17.94   18.3  100.0  100.0        0   57   1.0408    8.2
2016-07-29  23:02:30  18.73   25.2  100.0  100.0        0   58   1.0408    9.7
2016-07-29  23:02:31  17.92   19.6  100.0  100.0        0   59   1.0408    8.7
2016-07-29  23:02:32  17.26   17.7  100.0  100.0        0   56   1.0408    8.3
2016-07-29  23:02:33  16.88   14.6  100.0  100.0        0   56   1.0408    6.7
2016-07-29  23:02:34  17.91   14.6  100.0  100.0        0   57   1.0408    6.9
2016-07-29  23:02:35  17.28   15.9  100.0  100.0        0   57   1.0408    7.5
2016-07-29  23:02:36  18.87   14.2  100.0  100.0        0   56   1.0408    7.1
2016-07-29  23:02:37  18.10   21.8  100.0  100.0        0   62   1.0408    8.4
2016-07-29  23:02:38  18.59   45.4  100.0  100.0        0   61   1.0408   11.3
2016-07-29  23:02:39  18.20   29.9  100.0  100.0        0   58   0.9957    9.8
2016-07-29  23:02:40  18.63   29.6  100.0  100.0        0   59   1.0408    9.7
2016-07-29  23:02:41  18.14   15.6  100.0  100.0        0   57   0.9957    7.2
2016-07-29  23:02:42  16.55   17.2  100.0  100.0        0   57   1.0408    7.3
2016-07-29  23:02:43  15.57   13.8  100.0  100.0        0   58   1.0408    6.9
2016-07-29  23:02:44  16.61   13.6  100.0  100.0        0   57   1.0408    6.5
2016-07-29  23:02:45  15.76   17.8  100.0  100.0        0   57   1.0408    7.2
2016-07-29  23:02:46  16.34   16.4  100.0  100.0        0   58   0.9957    7.3
2016-07-29  23:02:47  18.58   14.9  100.0  100.0        0   56   1.0408    7.2
2016-07-29  23:02:49  17.13   13.5  100.0  100.0        0   57   1.0408    6.6
2016-07-29  23:02:50  17.52   15.4  100.0  100.0        0   58   1.0408    6.9
2016-07-29  23:02:51  17.60   17.2  100.0  100.0        0   57   1.0408    7.9
2016-07-29  23:02:52  18.68   24.1  100.0  100.0        0   62   1.0408    9.3
2016-07-29  23:02:53  18.55   28.1  100.0  100.0        0   59   1.0408   10.1
2016-07-29  23:02:54  18.08   29.2  100.0  100.0        0   58   1.0408    9.4
2016-07-29  23:02:55  17.28   15.0  100.0  100.0        0   56   1.0408    6.8
2016-07-29  23:02:56  17.88   14.4  100.0  100.0        0   57   0.8806    6.8
2016-07-29  23:02:57  16.68   15.4  100.0  100.0        0   59   1.0408    6.7
2016-07-29  23:02:58  19.05   39.8  100.0  100.0        0   60   1.0408   11.7
2016-07-29  23:02:59  19.08   34.7  100.0  100.0        0   60   1.0408   11.5
2016-07-29  23:03:00  18.71   15.0  100.0  100.0        0   60   1.0408    7.4
2016-07-29  23:07:19  19.68   10.9  100.0  100.0        0   65   1.0408    8.8
2016-07-29  23:07:20  20.00    7.7  100.0  100.0        0   64   1.0408    8.6
2016-07-29  23:07:21  20.00    6.6  100.0  100.0        0   63   1.0408    8.5
2016-07-29  23:07:22  20.00   12.8  100.0  100.0        0   65   1.0408    9.2
2016-07-29  23:07:23  20.00    7.7  100.0  100.0        0   66   1.0408    8.6
2016-07-29  23:07:24  20.00    8.2  100.0  100.0        0   64   1.0408    8.7
2016-07-29  23:07:25  19.76    5.4  100.0  100.0        0   63   1.0408    8.3
2016-07-29  23:07:26  18.52    9.8  100.0  100.0        0   64   1.0408    8.6
2016-07-29  23:07:27  17.96    6.7  100.0  100.0        0   63   1.0408    8.0
2016-07-29  23:07:28  19.39    7.6  100.0  100.0        0   63   1.0408    8.4
2016-07-29  23:07:29  19.03    8.4  100.0  100.0        0   63   0.8756    8.4
2016-07-29  23:07:30  19.22    7.8  100.0  100.0        0   64   1.0408    8.3
2016-07-29  23:07:31  18.18    8.7  100.0  100.0        0   65   1.0408    8.3
2016-07-29  23:07:32  19.18   10.7  100.0  100.0        0   64   0.7855    8.7
2016-07-29  23:07:33  18.32   15.2  100.0  100.0        0   63   1.0408    8.9
2016-07-29  23:07:34  19.28   13.5  100.0  100.0        0   68   1.0358    9.0
2016-07-29  23:07:35  19.38   20.4  100.0  100.0        0   67   1.0358    9.8
2016-07-29  23:07:36  19.11   12.7  100.0  100.0        0   66   1.0358    9.0
2016-07-29  23:07:37  19.75   22.7  100.0  100.0        0   68   1.0358   10.3
2016-07-29  23:07:38  18.89   10.2  100.0  100.0        0   66   1.0358    8.7
2016-07-29  23:07:39  20.00   48.6  100.0  100.0        0   72   1.0358   13.1
2016-07-29  23:07:40  19.92   38.8  100.0  100.0        0   70   1.0358   12.0
2016-07-29  23:07:41  20.00   36.1  100.0  100.0        0   70   1.0358   12.0
2016-07-29  23:07:42  19.43   17.5  100.0  100.0        0   66   1.0358    9.4
2016-07-29  23:07:43  19.09   16.6  100.0  100.0        0   70   1.0358    9.2
2016-07-29  23:07:44  20.00   62.3  100.0  100.0        0   74   1.0358   13.9
2016-07-29  23:07:45  19.15   23.6  100.0  100.0        0   65   0.9907    9.9
2016-07-29  23:07:46  19.36   10.5  100.0  100.0        0   64   1.0408    8.6
2016-07-29  23:07:47  19.68    5.0  100.0  100.0        0   65   1.0408    8.3
2016-07-29  23:07:48  19.59    5.4  100.0  100.0        0   65   1.0408    8.2
2016-07-29  23:07:49  18.46    5.7  100.0  100.0        0   64   1.0408    8.1
2016-07-29  23:07:50  18.79   12.4  100.0  100.0        0   65   1.0358    8.8
2016-07-29  23:07:51  17.43   10.6  100.0  100.0        0   65   1.0358    8.3
2016-07-29  23:07:52  17.62   13.0  100.0  100.0        0   64   1.0358    8.4
2016-07-29  23:07:54  19.52   11.9  100.0  100.0        0   68   1.0358    8.9
2016-07-29  23:07:55  18.33   19.0  100.0  100.0        0   65   1.0358    9.3
2016-07-29  23:07:56  16.65    7.6  100.0  100.0        0   65   1.0408    7.9
2016-07-29  23:07:57  18.12    8.2  100.0  100.0        0   64   1.0408    8.3
2016-07-29  23:07:58  19.00   13.7  100.0  100.0        0   69   1.0358    9.1
2016-07-29  23:07:59  19.59   20.7  100.0  100.0        0   65   1.0358   10.1

Any Idea whats going on? Its running fine for hours, and than it goes off.. Sometimes it goes a second time after the reboot, its running for ~10Minutes than crash again.

 

That sounds like a feature that is doing exactly what it was designed to do. Using any of the ThrottleStop Lock options should be the last thing you use when trying to fix a throttling problem. If you decide to Lock a CPU register, you usually need to completely shut your computer down to get the register unlocked. If Windows is not letting you completely shut down then you might have to power down, unplug your laptop and remove the battery to force it to shut down. After you do this, restart your computer and do not run ThrottleStop or it will lock these CPU registers again. You will need to remove the ThrottleStop.INI file and start again to make sure that ThrottleStop does not lock anything.

@orbit88 - You were having problems before that you blamed on the C States. Have you done any stability testing recently? Your memory might be failing. I would run a couple of threads of Prime95, both FFTs and the Blend test to give your computer a good workout.

If your computer crashes, ThrottleStop is not going to be able to write out any log data to your hard drive. That is probably why a few minutes of data is missing. ThrottleStop only writes data to the hard drive once every minute by default. ThrottleStop might have an option to write all data to the hard drive in real time but I can't remember what that option is at the moment. Let me know if you need an option like that.

 

Hi, I just got my new laptop with a 6700K and i am trying to undervolt it in order to reduce the temperatures a little bit. Which stress test do you recommend me in order to be safe that the system is stable after undervolting with throttestop?
Thanks

 

I finally upgraded my old Core2-based laptop to Windows 10, and I'm pleased to say that ThrottleStop 8.10b2 is working fine.

A long time back I had posted some info about how to run ThrottleStop as a service. I still wanted to do that on my machine since it has multiple users. I found a better tool called NSSM, which is available for both x86 and x64, and makes it very easy install a service.

http://nssm.cc/

I setup ThrottleStop 8.10 as a service, and it seems to be working great. Thanks again unclewebb for your work on this!