The ThrottleStop Guide

A Core i5-3317U is a low power CPU. Intel designs these so they automatically throttle back after a set time limit.

Copy and paste a ThrottleStop log file to Pastebin.com - #1 paste tool since 2002!

Your screen shot has ThrottleStop in Monitoring Mode. Make sure that is enabled when logging data. Post a screen shot of how you have ThrottleStop set up, including the TPL window from when you are logging data so I can compare.

 

Let's talk on this topic.
http://forum.tabletpcreview.com/acer-gateway/54122-w700-throttling-2.html

 

Hello Unclewebb,

I doubt you remember me (we had some PMs about throttlestop on i7 720qm XPS), but here goes:

I have recently bought a SSD (samsung 830). When I benchmarked it, I immediately noticed the performance was off.
I thought I was done with throttle & XPS 1645, but of course not. Apparently my SSDs performance is linked to my i7's or motherboards speed!
Well long story short, I tried some of the tweaks found on this forum which helped but also disabled turbo boost on my dell XPS 1645 (i7 720qm).

I then stumbled upon the the c-state options for throttlestop 5.00. I've been using your throttlestop since the beginning but never used this.
So your manual says to use Package state limit "C1" and both demolition options to prevent sleep states and increase 4K speeds...and it does seem to work! No more need for the registry tweaks.


But I have two question:
1) If throttlestop is supposed to limit to C1, why does TS report such high % of C6 states?


2) Would you have any other ideas on how to get the maximum out of my SSD? I already disabled core parking which also helped. Basically, when I'm on AC, I don't want any of the cores to sleep or slow down or whatever - they should be maximum performance mode all the time.

Thanks!

 

I have a question that pertain to much older Intel CPUs. Penryn Intel T9300. I have read a few articles that pertain to the C3 and C6 state. However looking at the ThrottleStop, those states (at least on this CQ62-219WM) are '---' out. They never change. I am also using ThrottleStop on an I5-750 Desktop system, those C3% and C6% are constantly moving/changing.

I guess my question is... is it because of my BIOS on this Toshiba that is not allowing the CPU to enter C3 or C6? Or I don't have something setup correctly?

 

I remember you well DuranXL. The XPS 1645 was the reason why I wrote ThrottleStop. I had no idea I would still be updating it years later.

Edit: Now I can see your image.

Individual cores can enter the various sleep states. If all the cores go into the same C state then the entire CPU package can enter that C state. ThrottleStop lets you block the CPU package from going into the deeper sleep states but it does not prevent the individual cores from entering the deeper sleep states.

There is a registry hack to disable all of the C states but the problem with that is it also disables turbo boost on the non-Extreme CPUs. On a 720QM, that will kill performance so it should be avoided. It sounds like you have maximized your SSD performance with all of the usual tricks. What are your SSD scores on your laptop. Some of the benchmarks might be a little misleading if they don't put enough load on your CPU to get it running at full speed. During normal use, your SSD is probably performing just fine.

mbze430: ThrottleStop only reports C3 and C6 residency time for the newer Core i CPUs. There is no easy way to calculate this on the older Core 2 based CPUs so I didn't bother.

 

Ah, I understand. So I guess TS is limiting as it should.
With just the disabled parking and TS running I get this (SATA 2!)

I still think my 4k-64 READ is way off.. Should be 250mB/s

 

Here are some numbers for comparison while using an Intel 520 Series SSD.

AS SSD 4021 MHz


AS SSD 4021 MHz - C3 C6 Enabled
http://img832.imageshack.us/img832/350/asssdc3c6.png

The first test is a desktop 3570K, locked at 4021 MHz, with all C states disabled. The second test was at the same speed but with the C3 and C6 core sleep states enabled. This one adjustment drops power consumption at the wall by one third while the real world SSD performance hit is minimal.

There is a huge difference in our Sequential benchmark scores but that is because my desktop motherboard uses SATA 3 while your laptop motherboard only supports SATA 2.

Your 4K-64 test actually looks really good. My CPU is running 50% to 100% faster than your CPU while using a SATA connection with 100% more bandwidth and I can't even hit 250 MB/s in that test. When you look at it that way, I don't think your expectations are reasonable. Be happy or else you will need to go spend some money on a new laptop with SATA 3 to get some better AS SSD scores. Beyond benchmarking, I don't think you will ever notice any difference. A modern SSD on SATA 2 or SATA 3 is lightening fast compared to any mechanical hard drive.

 

The reason I thought it should be 250mB/s is because a friend of mine has the samsung 830 with a similar laptop (its a bit faster and has SATA 3) and he gets around 280mB/s.
I figured mine should also get that similar results since 250mB/s should be within the capabilities of SATA2.

I guess it doesn't work like that

edit: here is his picture.
The only difference is he has a newer generation i7 (2ghz) and SATA 3

 

Can ThrottleStop work in a Windows PE environment? Has anyone tried? Any pointers? (I guess the service would need to be taken care of).

GL

 

My laptop randomly turns off after enabling BD PROCHOT and playing a game.
I suspect that this is because my laptop is overheating.
I have a Lenovo E420 with an i5-2410 M 2.3 ghz.
Is there a setting I could change to run it at faster than normal performance without overheating?
I have not changed any other settings besides BD PROCHOT.

 

Post a screenshot of TS please when it's overheating

 

Sadly, I cannot do that.
The computer simply shuts down without warning while I'm in the game...therefore, I have no idea when it is actually overheating.

 

Now I don't know how old your machine is. But it may be dust inside the system, also the cooling is not the best in the E420 so bad cooling + old paste/stock paste = overheating.

If you could, without hurting your warranty, I would recommend repasting, or just buying some canned air to spray your vent and get that damn dust out

 

Can you clarify a bit more about the compatible mobile CPUs?

It does not work with any of the Core i7-XXXX QM Clarksfield, Sandy Bridge and Ivy Bridge processors, only the XM?

 

You can enable the "log file" feature it will log until it shots down. You can post that

 

throttlestop doesnt work properly in Windows 8 x64 enterprise. I use Q9200ES cpu. first issue is that Throttlestop reports different speeds sometimes it will show 2.4 ghz then you reboot and will show proper speed, i mean speed i overclocked to. Other issue is that for example the cpu is overclocked to 3.3ghz after reboot and going to Bios it show 3.5ghz and after logging into windows it will show 3.3ghz. another issue is that the CPU need more power to work overclocked comparing to windows 7. in windows 7 after overclocking to 3.3 the power needed was 1.3v in win 8 1.4. There are other issues like after overclocking at some points mouse cursor slow down and stuff like that. few times got blue screen. Laptop has proper cooling the temp never goes over 80 no matter how much i overclock it to.

 

moviemarketing: ThrottleStop should work with most Intel Core 2 and Core i processors released during the last 6 years . It doesn't work with some of the Atom processors because they are missing 2 high performance timers that ThrottleStop depends on. The features available will vary depending on what CPU model you have. For example, the UNLK button to unlock Core 2 Extreme CPUs will not be available if you are running ThrottleStop on a Core 2 CPU that has a locked multiplier or if you are running ThrottleStop on a Core i processor. The Turbo Ratio Limits and Turbo Power Limits buttons are for Core i processors. The TRL and TPL buttons won't show up if you have a Core 2 based CPU. The TPL window will also vary depending on whether you have a first generation Core i CPU compared to how ThrottleStop will look if you have a Sandy or Ivy Bridge CPU. If the power related settings in the Sandy and Ivy Bridge CPUs are locked by the bios, ThrottleStop will gray out the adjustments in the TPL window. ThrottleStop adjusts itself automatically based on the CPU detected. You can check out the first post in this thread for 2 examples.

alice43: I briefly tested ThrottleStop on Windows 8 using an unlocked Core 2 QX9650 and it seemed to work OK. Windows 8 does not always report the CPU speed correctly. What are you comparing ThrottleStop to? If it shows your CPU running at 2.4 GHz then it is probably running at 2.4 GHz. If you are still having a problem, run the TS Bench test and show me a screen shot of CPU-Z 1.62 and ThrottleStop 5.00 while TS Bench is running.

When you start ThrottleStop, it uses the previous settings that you saved. If you re-boot and go into the bios and change the speed of your CPU, when you start ThrottleStop, it will ignore any changes you made in the bios and it will try to use the previous ThrottleStop settings. ThrottleStop has always worked like this no matter what operating system you are using.

When a laptop starts up or is re-booted, the bios is supposed to reset the unlocked multiplier but some laptops do not do that. If that is a problem for you and your laptop, it is a problem with your bios. Intel was very secretive about this feature so maybe some bios writers had no idea what they were supposed to be doing.

When overclocking Core 2 CPUs to 3400 MHz and beyond, they start to lose stability when the core temperature gets up to 80C and higher. Core i CPUs are a lot more stable than Core 2 CPUs when overclocking and running between 80C and 100C. What sort of stability testing have you completed in Windows 7? Are you Prime 95 Small and Large FFT stable as well as IBT or LinX stable? If you are having blue screens then that is telling me that your overclock is not 100% stable. You need to overclock it less or find a way to run it cooler. You are hitting the outer limits of your CPU.

 

unclewebb this q9200es, was working in windows 7 at 3.6 ghz without problem but i have set 3.3ghz at 1.3V in windows 7.
Now i use windows 8 and have set 3.3ghz 1.3v and got blue screen had to increase to 1.4v
in windows 8 i set cpu to 3.2ghz 1.3v and reboot pc the Bios reports not 3.46ghz.
when i said theres issue with Throttlestop reporting wrong speed i mean i start CPU-z and other apps and all report 3.46ghz and throttlestop reports 2.4ghz. other time 3.2 etc. if you want i will take pics to show you

i use throotlestop since ver 3 not since yesterday and there are some issues in windows 8.


when laptop is rebooted CPU speed aint reset. not only in this laptop but in any other. the only way to reset is to switch laptop totally off mean pull electric wire of the laptop or reset bios


what stability, 3ds max rendering

 

Anyone with an ASUS G53SX(Best Buy version) knows if ThrottleStop works smoothly? I have the factory BIOS(205) and updated my graphics card(GTX 560M) to the new 310.7 driver.

Just trying to be cautious here(PC NEWB) lol.

 

Alright, so my laptop randomly turns off after starting a game.
I am sure of it overheating now that I have taken a look at the log file :/
Are there any settings that I could change to limit the speed at which it is running while still making it faster than it already is?
The log file is below

Code:

   DATE       TIME    MULTI   C0%   CKMOD  CHIPM   BAT_mW  TEMP    VID   POWER
2012-12-22  12:50:01  14.29    3.6  100.0  100.0        0   47   1.1659    4.6
2012-12-22  12:50:03  15.44    4.1  100.0  100.0        0   48   1.1709    4.9
2012-12-22  12:50:04  19.04    6.4  100.0  100.0        0   48   1.1709    5.6
2012-12-22  13:02:52  27.59   33.0  100.0  100.0        0   75   1.1709   17.8
2012-12-22  13:02:53  27.84   30.2  100.0  100.0        0   75   1.1709   17.2
2012-12-22  13:02:54  27.60   31.4  100.0  100.0        0   75   1.1709   17.8
2012-12-22  13:02:55  27.70   31.7  100.0  100.0        0   80   1.1709   17.8
2012-12-22  13:02:56  27.51   31.1  100.0  100.0        0   76   1.1709   17.8
2012-12-22  13:02:57  28.03   28.7  100.0  100.0        0   74   1.1709   17.0
2012-12-22  13:02:58  27.87   29.7  100.0  100.0        0   76   1.1709   17.2
2012-12-22  13:02:59  27.38   33.1  100.0  100.0        0   78   1.1709   18.0
2012-12-22  13:03:00  27.82   30.2  100.0  100.0        0   76   1.1459   17.2
2012-12-22  13:03:02  27.58   30.5  100.0  100.0        0   76   1.1709   17.5
2012-12-22  13:03:03  27.78   35.4  100.0  100.0        0   77   1.1709   18.5
2012-12-22  13:03:04  27.90   34.7  100.0  100.0        0   77   1.1709   17.5
2012-12-22  13:03:05  28.76   26.8  100.0  100.0        0   77   1.1709   16.9
2012-12-22  13:03:06  27.65   37.0  100.0  100.0        0   74   1.1709   20.1
2012-12-22  13:03:07  27.11   17.6  100.0  100.0        0   82   1.1659   26.2
2012-12-22  13:03:08  27.09   18.2  100.0  100.0        0   80   1.1459   27.7
2012-12-22  13:03:09  28.28   27.7  100.0  100.0        0   88   1.1709   22.9
2012-12-22  13:03:10  27.88   31.3  100.0  100.0        0   87   1.1709   19.2
2012-12-22  13:03:11  27.63   29.6  100.0  100.0        0   83   1.1709   24.8
2012-12-22  13:03:12  27.90   31.4  100.0  100.0        0   81   1.1709   16.2
2012-12-22  13:03:13  27.40   36.8  100.0  100.0        0   83   1.1709   22.9
2012-12-22  13:03:14  27.41   43.1  100.0  100.0        0   91   1.1709   22.8
2012-12-22  13:03:15  27.00   54.3  100.0  100.0        0   93   1.1709   22.5
2012-12-22  13:03:16  27.01   60.8  100.0  100.0        0   92   1.1709   23.1
2012-12-22  13:03:17  27.41   45.2  100.0  100.0        0   88   1.1709   23.0
2012-12-22  13:03:18  27.69   35.4  100.0  100.0        0   93   1.1709   22.6
2012-12-22  13:03:19  27.08   54.2  100.0  100.0        0   89   1.1709   23.8
2012-12-22  13:03:20  26.90   35.0  100.0  100.0        0   91   1.1709   31.7
2012-12-22  13:03:21  27.28   29.3  100.0  100.0        0   96   1.1709   29.0
2012-12-22  13:03:22  27.22   40.0  100.0  100.0        0   97   1.1709   26.5
2012-12-22  13:03:23  24.32   52.6  100.0  100.0        0  100   1.1709   32.9
2012-12-22  13:03:24  24.75   48.4  100.0  100.0        0   96   1.1709   30.0
2012-12-22  13:03:25  26.49   34.3  100.0  100.0        0   96   1.1259   30.6
2012-12-22  13:03:26  24.70   37.7  100.0  100.0        0   95   1.1709   26.1
2012-12-22  13:03:27  24.39   35.5  100.0  100.0        0   91   1.1359   26.2
2012-12-22  13:03:28  24.58   32.2  100.0  100.0        0   93   1.1609   26.9
2012-12-22  13:03:29  24.38   49.4  100.0  100.0        0   92   1.1709   27.1
2012-12-22  13:03:30  24.41   38.7  100.0  100.0        0   90   1.1259   25.6
2012-12-22  13:03:31  24.46   42.6  100.0  100.0        0   93   1.1609   26.4
2012-12-22  13:03:32  24.89   45.9  100.0  100.0        0   93   1.1709   27.4
2012-12-22  13:03:33  24.45   30.3  100.0  100.0        0   91   1.1359   25.8
2012-12-22  13:03:34  24.40   27.4  100.0  100.0        0   87   1.1359   25.6
2012-12-22  13:03:35  24.54   29.2  100.0  100.0        0   88   1.1359   25.9
2012-12-22  13:03:36  24.51   47.9  100.0  100.0        0   97   1.1359   27.1
2012-12-22  13:03:37  24.43   48.2  100.0  100.0        0   96   1.1609   27.0
2012-12-22  13:03:38  24.43   43.6  100.0  100.0        0   93   1.1259   27.2
2012-12-22  13:03:39  24.50   43.5  100.0  100.0        0   96   1.1359   27.2
2012-12-22  13:03:40  24.67   47.8  100.0  100.0        0   97   1.1259   27.8
2012-12-22  13:03:41  24.64   44.4  100.0  100.0        0   96   1.1359   27.0
2012-12-22  13:03:42  24.59   43.4  100.0  100.0        0   96   1.1359   27.0
2012-12-22  13:03:43  24.42   47.2  100.0  100.0        0   97   1.1709   28.1
2012-12-22  13:03:44  24.89   38.4  100.0  100.0        0   91   1.1359   26.0
2012-12-22  13:03:45  25.84   43.2  100.0  100.0        0   93   1.1459   27.0
2012-12-22  13:03:46  24.57   38.3  100.0  100.0        0   94   1.1259   26.7
2012-12-22  13:03:47  24.18   30.3  100.0  100.0        0   92   1.1259   26.4
2012-12-22  13:03:48  24.16   29.7  100.0  100.0        0   93   1.1459   26.2
2012-12-22  13:03:49  24.37   35.2  100.0  100.0        0   93   1.1359   26.3
2012-12-22  13:03:50  24.55   48.1  100.0  100.0        0   99   1.1609   28.0
2012-12-22  13:03:51  24.62   47.3  100.0  100.0        0   97   1.1459   27.9
2012-12-22  13:03:52  24.50   44.2  100.0  100.0        0   97   1.1259   27.7
2012-12-22  13:03:53  24.33   41.0  100.0  100.0        0   94   1.1409   27.1
2012-12-22  13:03:54  23.97   30.1  100.0  100.0        0   94   1.1359   25.5
2012-12-22  13:03:55  24.14   29.7  100.0  100.0        0   90   1.1058   25.3
2012-12-22  13:03:56  24.27   35.6  100.0  100.0        0   90   1.1709   25.6
2012-12-22  13:03:57  24.32   36.6  100.0  100.0        0   91   1.1709   25.8
2012-12-22  13:03:58  24.46   38.7  100.0  100.0        0   92   1.1709   26.4
2012-12-22  13:03:59  24.18   38.5  100.0  100.0        0   91   1.1259   24.8
2012-12-22  13:04:00  24.24   42.3  100.0  100.0        0   94   1.1259   26.9
2012-12-22  13:06:53  28.21   25.8  100.0  100.0        0   74   1.1459   15.0
2012-12-22  13:06:54  27.24   32.0  100.0  100.0        0   65   1.1459   13.9
2012-12-22  13:06:55  27.22   13.9  100.0  100.0        0   57   1.1609    8.9
2012-12-22  13:06:56  25.19   19.7  100.0  100.0        0   61   1.1709   10.9
2012-12-22  13:06:57  25.66    8.4  100.0  100.0        0   58   1.1459    6.5
2012-12-22  13:06:58  25.55    7.7  100.0  100.0        0   55   1.1459    6.2
2012-12-22  13:06:59  18.82    7.1  100.0  100.0        0   52   1.1709    5.9
2012-12-22  13:07:00  25.94   10.8  100.0  100.0        0   53   1.1659    6.9
2012-12-22  13:07:01  22.30    8.4  100.0  100.0        0   58   1.1709    6.7
2012-12-22  13:07:02  22.16    6.7  100.0  100.0        0   53   1.1659    5.9
2012-12-22  13:07:03  25.83   15.3  100.0  100.0        0   55   1.1609    8.7
2012-12-22  13:07:04  18.23    2.9  100.0  100.0        0   51   1.1659    4.2
2012-12-22  13:07:05  18.38    3.4  100.0  100.0        0   51   1.1459    4.5
2012-12-22  13:07:06  16.43    4.1  100.0  100.0        0   50   1.1609    4.7
2012-12-22  13:07:07  15.23    2.5  100.0  100.0        0   47   1.1659    4.0

 

renzpwns: Try asking your question in the Asus G53SX thread. I think the Asus 53 and 73 series had some throttling problems. Some of these problems might have been fixed with updated bios versions. If you have a problem, ThrottleStop will probably be able to help you out.

alice43: Yes, please show me a picture of CPU-Z 1.62 and ThrottleStop 5.00 when your CPU is fully loaded and show me another screen shot when your CPU is idle. You can also run the Log File option in ThrottleStop and show me that too. If both programs report the same MHz when fully loaded but are different when lightly loaded or idle; the difference is probably because Windows 8 is using some CPU C sleep states that Windows 7 was not using. Most monitoring programs ignore when your CPU is using various C States. ThrottleStop will report that as a reduced multiplier when your CPU is lightly loaded. This might also be the reason why your CPU is not as stable in WIndows 8 as it was in Windows 7. The deeper C sleep states will drop your CPU core voltage down far lower than normal which can cause a BSOD, especially on an ES processor.

Windows 8 is a brand new operating system. It is not surprising to me that your computer is not as stable when running Windows 8 compared to Windows 7. That has nothing to do with ThrottleStop. ThrottleStop 5.00 is still the exact same program as it was 6 months ago. Windows 8 is more optimized than Windows 7 so it is probably using some new instructions within your CPU that Windows 7 never used.

Is your computer Prime95 and IBT/LinX stable at 3.6 GHz and for how long? A 100% stable CPU can run any of those programs for hours without overheating or without any BSOD problems. I am trying to tell you that you are running your CPU on the edge where it is not 100% stable. It might have been stable in the programs you were using before but you are using a totally different operating system now. There is no guarantee that your computer will still be stable when you make a major change like that.

Push the ThrottleStop Reset button before you reboot. This resets the maximum multiplier and your CPU will be running at a maximum of 2.4 GHz after you press Reset. When you reboot, your CPU will run at whatever speed that has been set in the bios. As soon as you start up ThrottleStop, it will Unlock your CPU and it will try to set your CPU to the previous values you saved when you were last using ThrottleStop. If you don't want this to happen, delete the ThrottleStop.INI file before you start ThrottleStop. This will delete all of your previously saved settings.

If stability is important to you then switch back to Windows 7 until Windows 8 has all the bugs worked out. That is why many businesses do not upgrade to a new operating system at least until the first service pack comes out.

sardinesrule: Your laptop is telling you that it is not happy when you run the CPU up to 100C. If it was my laptop, I would pull it apart and try to improve the cooling. If you don't want to do that then you will need to run it slower. You can use the Set Multiplier option in ThrottleStop to slow your computer down. Lower it until your CPU stops overheating and randomly shutting down. Different games will have different maximum safe speeds depending on how hard they are working the CPU.

If you do not fully understand what BD PROCHOT is all about, you should not be turning it on or off.

Think about this for a moment. Your Lenovo E420 is not capable of running at its rated speed without overheating. Trying to run it faster than its rated speed is only going to make things worse. There is no magic setting that can fix poor design.

 

uncleweb hope this pic will make you sure that Throttlestop do not work properly in Windows 8
and its not only ver 5.05 but none of them work properly in win 8


i could overclock to 3.6 ghz in win 7 but didnt do any work on it it was only for testing, for work it was set to 3.3ghz 1.3v and worked without any issues
in win 8 i can have max 3.18ghz 1.325V in win 8 impossible to go over 3.3 ghz and even at 3.3 isnt stable. anyways doesnt matter really 3ghz is good too and the temp very low.

 

Thank you for posting that alice43.

I thought the problem was with the CPU multiplier but that and the VID looks OK. When you click on the FSB button in ThrottleStop, it re-calculates the FSB speed each time you press that button. Does it always report pretty much the exact same speed or does the reported bus speed vary randomly all over the place?

I have not had a lot of feedback from ThrottleStop users running Windows 8 and I have only tested ThrottleStop for one day with the beta version of Windows 8. I didn't see any obvious issues. For feedback I usually look around the forums and for some users, I know that ThrottleStop is working OK when running Windows 8.

700T Heat - Page 2

ThrottleStop uses a high performance timer within your CPU to calculate the MHz. Could you try running this testing program to make sure the 2 main timers in your CPU are in sync?

WinTimerTester 1.1
WinTimerTester_1.1.zip

Within about 60 seconds, these two timers should be within sync and should show a ratio very close to 1.0000:1

If your timers are OK, I am not sure how to fix this problem. I don't have access to Windows 8 and I don't have any plans at the moment to update ThrottleStop for Windows 8. It probably won't ever happen.

If you believe that ThrottleStop is causing you stability problems then you can still use it to unlock your maximum multiplier. Use ThrottleStop to set your maximum multiplier and maximum voltage and then exit ThrottleStop. I provided an INI option for people that don't need to run ThrottleStop all the time,

ExitTime=5

This will force ThrottleStop to exit 5 seconds after it starts. Now if your laptop crashes when using Windows 8, you can't blame ThrottleStop.

Edit: If there is a problem with the high performance timer that Windows 8 is using, have a look at this thread to see if the problem can be corrected.

http://forum.notebookreview.com/asu...-game-timing-problem-g60jx-2.html#post7364805

If WinTimerTester reports a different clock MHz in Windows 7 and in Windows 8 on the same laptop then that means Windows 8 is using a different timer internally.

 

""""I thought the problem was with the CPU multiplier but that and the VID looks OK. When you click on the FSB button in ThrottleStop, it re-calculates the FSB speed each time you press that button. Does it always report pretty much the exact same speed or does the reported bus speed vary randomly all over the place?""""

look Uncleweb. I set Throttlestop to 3.33ghz multiplier 12.5 and 1.4v, I save settings and reboot. After reboot i go to Bios and i see 3.46Ghz multiplier 13. i start System and sometimes Throttlestop report coreclty mean it will report 3.33ghz other time after reboot Throttlestop will report wrong speed for example 2.4ghz.

At the moment throttlestop report correct speed as i have set it for now mean 3.2ghz but if i rebooted and went to bios, bios would report 3.46ghz and if i went back to windows it could report the correct speed other time wrong one.

At the moment it report correct speed and after pressing FSB button the speed in Mhz jump from between 260Mhz to 290Mhz. if i keep pressing the button and the throttlestop isnt on power saving mode, when i keep pressing FSB the speed stays around 265Mhz

When reboot of the system and back and throttlestop report wrong speed the FSB speed in Mhz show around 180Mhz


heres Win timer result





""""If WinTimerTester reports a different clock MHz in Windows 7 and in Windows 8 on the same laptop then that means Windows 8 is using a different timer internally. """"

i dont have win 7 anymore to much trouble installing it again. The Point is that when Throttlestop starts it change something i mea its normal but after the Throttlestarts and whatever it change for example the speed will be set to 3.33ghz even i exit throttlestop speed will be 3.33 and thats good but after reboot and going to BIOS speed shown there will be 3.46ghz
something wrong


And i do think win 8 is very much different than 7.

 

i just found, So this Timer tester reports 3.37Ghz and TS reports 3.19 Ghz

is this normal ?

 

Update

after setting TS to ExitTime=5 TS exit and the CPU jump to 3.46ghz (((remember no matter TS working or not BIOS cpu speed jump to 3.46 as soon as i first time touch TS ))) not as TS was left 3.2ghz Whats wrong UWebb ???

3.46ghz is to much cuz of the voltage i would like it to be around 3.33


heres update from the timer tool after bcdedit /set useplatformclock true TS is off

 

Is there a way after TS timeexit=5sec to make CPU speed be 3.33ghz instead 3.46ghz ? the problem is that 3.46 isnt very stable.

If i set TS at 3.2ghz then timeexit=5 and after the system start and TS exit after 5sec the cpu jump to 3.46ghz

 

And here is Time tool after full TS reset

 

here's one more pic CPU fully loaded at 3.3ghz 1.325 V thats the minimum voltage to make the cpu be stable. In win 7 1.3 was enough

 

ok i will leave at 3.3ghz and 1.325v its 0.025v more than in win 7 but it seems work. unclewebb if you would like me to test something more i can do it for you

 

Update i left cpu at 3.33ghz and 1.325v and while running benchmark everything was ok then tried windows score and it crashed at cpu test several times and had to increase voltage to 1.3375v hope the cpu wont burn.

thats 0.0375 more than in windows 7

 

On your laptop, Windows 8 was originally using an internal timer that was running at 3.37695 MHz for its high performance timer. When you used the bcdedit command, that changed Windows 8 so now the high performance timer is based on an internal timer that is running at 14.31818 MHz. This results in more accurate time measurement for any program running on your computer. Using this more precise timer should let ThrottleStop calculate your bus speed more accurately too.

When you click on the FSB button 10 times, how consistent are your results? The bus speed hardly varies on the computers I have tested. Programs like CPU-Z do things differently. They calculate your bus speed continuously. To do this accurately, you need to fully load a CPU core, usually every second, for a short amount of time each time. Running a program like this all the time uses up a lot of CPU cycles and in a laptop, it drains your battery. ThrottleStop was designed to be a very efficient tool for laptops so I decided to only load your CPU like this once when you start ThrottleStop or a user can recalculate the bus speed whenever they want by pushing the FSB button. If the internal timer is accurate, the results are usually good enough without wasting a lot of CPU cycles.

You can use Process Explorer if you want to see how many CPU cycles ThrottleStop uses when minimized compared to CPU-Z.

Process Explorer v15.23
Process Explorer


I think I understand the other problem you were having. If you Unlock the CPU multiplier and then you adjust the multiplier too high and change your mind and decide to go lower, you have to push the Reset button to reset the maximum multiplier. This will take your maximum multiplier back to the default which is 9 so you can start adjusting again.

When you originally adjusted your multiplier to 13, that setting must have got saved either in ThrottleStop or it got saved within your CPU. If you went up to 13 and then went back to 12.5 and pushed Save, the maximum multiplier for your CPU is still 13. When you exit ThrottleStop and reboot, the maximum is still going to be stuck at 13 if the bios is not smart enough to reset this like it is supposed to do. This value gets written directly to a register within the CPU. If you went up to 13 and your laptop immediately had a BSOD, your laptop maximum multiplier is going to be stuck at 13 until you completely power it down. On some laptops, you might have to remove the battery too.

An unlocked multiplier is a powerful feature so you need to be extra careful when adjusting this. Never raise the multiplier too high and if you do, use the Reset button to reset your CPU and then start again.

When setting the VID voltage, the actual core voltage your CPU is receiving is usually less. Most motherboards have some vdroop so a VID setting of 1.325 might only result in 1.275 volts getting to your CPU. At the speeds you are trying to run at, that might not be enough. That might have been enough in Windows 7 but Windows 8 is a new beast. A BSOD or if Prime95 is not stable usually means that your CPU needs some more voltage. You are not going to hurt anything at the voltages and speed you are running at. Everyone worries about burning up their CPU but there are virtually no reports of this actually happening. There are a lot of crazy overclockers out there so you would think there would be a lot more stories of damaged CPUs but there are hardly any stories like that.

I am happy to hear that ThrottleStop is working better for you on Windows 8. ThrottleStop interacts with the CPU registers directly so it shouldn't matter too much what operating system you are using. Windows 8 should become more stable as various bugs are fixed. With a new operating system, there are always going to be some bugs.

 

Hi Unclewebb

When you click on the FSB button 10 times, how consistent are your results?

CPU idle pressed 10 times the times was moving from 265.999 to 266.0

CPU 100% load, was pressing the fsb button and the timer was moving from 265.999 to 266.001


below you can take look at processes




I think I understand the other problem you were having.

If i start TS and set multiplier to 12 the cpu speed will be 3.2 Ghz and if i exit TS and never start it again the CPU speed will change by itself from 3.2 to 3.46 Ghz up till when i pull electric cord of my laptop. Do you undertsand now unclewebb ? the TS after exiting dont know change the cpu speed from 3.2 as i have set to 3.46 ghz.

If i set TS to start at Boot up and i set multiplier to 12 the speed will be 3.2 Ghz i save the setting and reboot. and i go straight away to BIOS the speed will show 3.46 Ghz and i exit BIOS and go back to windows the speed will be changed in windows from 3.46 to 3.2 Ghz

I dont know how it can happen like that but it does happen

in windows 7 when i set speed to 3.2ghz in TS after reboot BIOS show 3.2ghz
in windows 8 when i set speed to 3.2 ghz or 3.0 ghz or whatever in TS and i reboot BIOS show always 3.46Ghz

Hope now you understand my english

in windows 8 no matter what i set TS, the TS will in someway change something make the speed be 3.46ghz as soon as TS exit

no matter i reset TS or remove and install it again as soon as i press on and unlink and use multiplier and voltage and set multiplier to something and vltage and exit TS, the speed will go to 3.46 in Bios in some magic way even i set the speed in TS to 3.2ghz


TS in win 8 is working the only thing is that as i said the speed isnt correctly reported by TS sometimes after reboot for example I set TS to multiplier 12.5 and speed 3.33 GHZ and i reboot and go to bios bios will report 3.46 ghz and i go back to win 8 and TS will report 2.4ghz
and the speed will be reported 2.4ghz by TS until i reboot again and after i reboot it may show correctly after reboot mean as i have set TS previously to 3.2ghz or it still may show 2.4ghz after reboot.

just so you undertsand. I set TS to 3.2ghz multiplier 12 save settings, TS is set to start at user login
I reboot and go straight to BIOS and bios will always report 3.46ghz mulitplier 13
i exit bios and go to win 8 TS will start and it may show correct speed as i left it before reboot mean 3.2ghz or it may show 2.4ghz

if i remove TS from windows delete it and pull cord of my laptop all will get reset and speed will go back to default mean 2.4Ghz and i reboot and go to BIOS and bios will report 2.4 Ghz

Hope now alll clear and + in win 8 to overclock to 3.3 ghz and make system stable the voltage has to be 0.0375v higher than in win 7.

anyways thats all.


and Marry Christmas Unclewebb and everyone else

 

That is good news that the bus speed is working correctly.

The maximum multiplier for your CPU is stuck at 13. That information has been saved in the ThrottleStop.INI file with the rest of the settings and the 13 maximum multiplier will also get saved in the CPU.

When you push the Reset button what multiplier do you see? After you push Reset, press Save to change the maximum multiplier in the INI file and in the CPU.

The maximum multiplier is not the same as the multiplier in the Set Multiplier box. If you unlock the CPU and increase the Set Multiplier value, the Maximum Multiplier automatically goes higher. If you reboot or exit ThrottleStop after using the 13 multiplier, the 13 multiplier will become your new maximum multiplier and your CPU will try to use the 13 multiplier as the default multiplier until you power down.

If you don't want this to happen you need to press the ThrottleStop Reset button before you exit ThrottleStop and before you reboot. You also need to save the new maximum multiplier in the ThrottleStop.INI file or else ThrottleStop will set the maximum multiplier to 13 as soon as you start up ThrottleStop again.

You can also try using the Do Not Reset FID / VID on Exit option. This also will give you some control of what ThrottleStop will do when you exit ThrottleStop.

 

[ThrottleStop]
TJMax=100
DTSAlarm=1
GPUAlarm=105
LowBattPercent=0
Profile=0
ProfileName1=Performance
ProfileName2=Game
ProfileName3=Internet
ProfileName4=Battery
ResumeProgram1=
ResumeProgram2=
ResumeProgram3=
ResumeProgram4=
Options1=0x0210288C
Options2=0x02102980
Options3=0x02102980
Options4=0x02102980
DutyCycle1=16
DutyCycle2=16
DutyCycle3=16
DutyCycle4=16
ChipsetDutyCycle1=8
ChipsetDutyCycle2=8
ChipsetDutyCycle3=8
ChipsetDutyCycle4=8
EIST=15
DTSButton=0
CPUColor=0xFFFFFF
GPUColor=0xFFFFFF
CPUMHzColor=0xFFFFFF
CPUIcon=0
GPUIcon=0
CPUMHzIcon=0
FontQuality=0
DIDAProfile1=0
SuperSLFM=0
StartDIDA=0
BatteryMonitoring=0
DCExitTime=0
BeforeRunProgram=15
BatteryButton=0
PSMinimum=35
Payload1=0x4C32
Payload2=0xC2F
Payload3=0xC2F
Payload4=0xC2F
HotKey0=0x0
HotKey1=0x0
HotKey2=0x0
HotKey3=0x0
HotKey4=0x0
FIDVID=0x4C32
Results00=0
Results01=0
Results10=0
Results11=0
Results20=16873
Results21=0
Results30=0
Results31=0
Results40=0
Results41=0
Results50=0
Results51=0
CheckSum=0x7EB23990

 

where is that 13 multiplier ?
ouch now its working i mean BIOS is reporting the speed correctly even after i exit TS. just where is that max multiplier in TS ini ?

 

Do not reset FID VID doesnt work in windows 8

 

I think that is the INI option for the Core 2 Extreme CPUs.

0x4C is the maximum FID (multiplier) and 0x32 is the maximum VID.

4C is a code. 4 stands for the half multiplier and 0xC is equivalent to 12 so when combined you get the 12.5 multiplier.

The 13 multiplier would be 0x0D since it is not using the half multiplier. This is Intel's numbering scheme and is not something that I dreamed up.

Do you know what this options is supposed to do? How do you know it doesn't work? This option does not have anything to do with the maximum multiplier.

ThrottleStop works the same in Windows 8 or Windows 7. Last time I tested this feature in Windows 7 it worked correctly.

The included documentation explains what this feature is designed to do.

 

Hi Unclewebb thanks for the answers and help.

yes its q9200ES



"..Do you know what this options is supposed to do?...."

i thought reset FID VID will reset cpu speed and multiplier to its default when exiting TS

 

Hello unclewebb, first thank you for this great program, really help me with my G41 and Q6600 running on overclock ... when put my cpu to 2.8ghz or More I got error in IBT (intelburntest) , checked on HWINFO and my core speeds drop to 6xx mhz, with ThrottleStop I see that Chipset clock modulation drops from 100 to 25% after high load (high load time) and then back to 100% when load stop... sometimes this occur in games to.. to bad cause I got a massive FPS drop/lag , now setting chipset to 100% there is no more problems with Clock Throttling or FPS drop , but my question, this Chipset clock modulation by-pass the OCP ?(over current protection of mobo) , its safe to set 100% ? i think that mobo drops the clock after cpu wattage pass certain point, like 110watts, so , its safe to run my overclock with Chipset Modulation at 100% ? thanks in advance

Scouty

 

Scouty: You're welcome!

Linpack / IBT / LinX is a very demanding test for a Core 2 processor. What maximum core temperature does ThrottleStop report during testing? Most applications do not put nearly as big a load on a CPU as IBT does so for gaming, you will probably be OK with Chipset Clock Modulation at 100%. Your motherboard reducing performance by over 75% seems a little excessive to me.

I do not know why your motherboard manufacturer decided to use Chipset Clock Modulation throttling. They were probably trying to protect some under designed component on your motherboard. Their limit might be based on the voltage regulator temperature or power consumption.

Thousands of people have been using ThrottleStop every day now for over 3 years and there have been very, very few reports of damaged motherboards because of ThrottleStop. I didn't engineer your motherboard so ultimately, it is your responsibility if you decide to run ThrottleStop to take care of the problem you are having.

 

thanks for reply unclewebb

well.. using linpack(linx)/OCCT(PSU TEST 10minutes) or IBT .. max temp is 61ºC on core 0 and 1... I got a good cooler =) plus I added 3 fans on VRM/GPU

I think that the trottle is related to POWER comsumption , since its only drop when 1.32v is active ... with stock speed of my Q6600 (2.4ghz ) and 1.32v I got chipset drop.. but with 1.26v theres no drop
but I need 1.32v to get stable at 2.8ghz.. with 1.32v I think that power comsuption go above 105w

Thank again , I´ll keep chipset mod 100% because I dont like random fps drop =)

ThrottleStop FTW :thumbsup:

ps. in HWinfo64 sensors theres AUX that reach 68ºC on IBT , and I noticed that chipset drops(without throttlestop) when that temp reach 65ºC ,maybe its coincidence, do u know what sensor are this?

 

Good Day,

Thanks for a great program. I am running Asus EP121 and your ThrottleStop is a definite asset. I have Windows 8 64 bit and I have a question.

I notice when I put the computer to sleep with ThrottleStop running, the computer fails to log back on properly. Instead it crashes and has to restart.

I then unchecked the the "Do not reset FID/VID on Exit" and exited ThrottleStop and then go to sleep and wake properly. Any way that I can leave this option checked abd still sleep properly?

Thank you,
Jasper

 

I don't own an Asus EP121 and I don't use Windows 8 so I don't think I will be able to come up with a solution for you. In theory, a CPU should be able to resume from Sleep without any issues no matter how you have ThrottleStop setup but I know that is not always the case. I have an old Core 2 laptop which also refuses to resume from stand by correctly about 25% of the time.

Can you post a screen shot of how you have ThrottleStop setup? Have you tried using different settings? If I see anything obvious, I will let you know but you might have to live with this bug. Maybe I will have to come up with a feature that temporarily suspends ThrottleStop when it senses that you are going into stand by mode and then ThrottleStop can get back to business after it figures out that you have resumed.

 

I have an EP121, I don't currently have windows 8 on it, but I did for about a month.

I"m sorry to say i didn't have any issues with TS when i put the computer to sleep and turned it back on, everything worked as intended, with no crashes, post a screen shot of the options you have throttlestop running with and i'll take a peak at them.

 

I don't have an Asus EP121 do run Windows 8 and I have no issues with resuming from sleep with Throttlestop running. Usually, computers that have issues with resuming from sleep do so by themselves, regardless of additional software running, such as Throttlestop.

 

Hi Unclewebb, the newest Throttlestop doesn't work anymore with the Win 8 UEFI Secure boot since it cannot load the winring driver. I'm going to try and bypass the driver enforcement and report back.


confirmed, the winring.dll driver can't be loaded even with Admin ownership and disabled driver enforcement, must be something with the fact the drivers have to be signed with the bootloader.

This is really weird since Batterycare also uses winring0.dll with no issues, I initially thought there might be a conflict but TS5 still doesn't work with batterycare uninstalled.
Whats even weirder is Realtemp works with no issues since this and TS are like siblings :s

I'm hoping there would be a workaround.

EDIT: false alarm, re-extracted TS, turns out driver enforcement was only disabled for 1 boot, everything is now back to normal

 

Thanks for the update Marksman30k. You had me worried there for a second.

Someday the WinRing0 driver will expire or be permanently blocked and then RealTemp and ThrotleStop and many other useful utilities will be dead.
Hopefully that doesn't happen until Windows 9.

 

As soon as i restart my pc if i havnt set throttle stop to start when windows does, does it put my CPU setting back to stop, in other words are the setting permanent?

 

Nothing ThrottleStop does is permanent. It does not modify your CPU and it does not write any values to the Windows registry. All of the settings it stores and uses are within the ThrottleStop.INI file so if you are ever having problems, just delete the INI file.

As long as your laptop bios correctly resets your CPU when it boots up; if you DO NOT run ThrottleStop, your CPU should boot up and be at its default speed and settings.

There are some laptops that do not correctly reset the maximum multiplier when using a Core 2 Extreme processor. If you have one of these, you might have to fully power down, including pulling the AC plug and removing the battery to force the CPU to reset to its default settings. I have not heard of this issue on any of the newer Core i motherboards but anything is possible. Not all bios writers follow the Intel guidelines for resetting the CPU when booting up or rebooting so any laptop with that problem will need to be fully powered down so the CPU can get back to its default settings.

ThrottleStop mostly just modifies how the bios and how Windows has set up the CPU. That is why I recommend that you only use it with the Windows High Performance profile so ThrottleStop can do its thing without Windows interfering with anything.