The ThrottleStop Guide

unclewebb, could you please post a link to download TS8? Can't seem to find it anywhere in the opening post, nor with a google search.

Thank you.

 

look in his signature.... :-D

 

ThrottleStop is a must for the Lenovo Y50 or Y510P. Both of these laptops disable Intel Turbo Boost soon after the Nvidia GPU is active. ThrottleStop has lots of features that specifically target the problems that these Lenovo laptops have. Intel XTU is useless because it does not give you any way to control these problems. I always like hearing from happy users.

You found the right thread to post in. Any ThrottleStop related questions are appropriate. I wish more desktop owners would give ThrottleStop a try but most people still think it is only for laptops. TS8 supports the majority of Intel CPUs released in the last 8 years; mobile, desktop and Xeon server. TS8 beta 2 should work correctly on the new Broadwell Core i7-5775C.

http://www.techpowerup.com/212531/intel-core-i7-5775c-broadwell-scrapes-5-ghz-oc-on-air.html

On the right hand side of ThrottleStop is the monitoring area. The CMod and Chip columns should always show 100.0. Anything less means your CPU is being throttled. If you are gaming, you can run a Log File and this log should also show 2 columns of 100.0. By default, ThrottleStop starts up in Monitoring mode. If you see a number like 25.0 in the Chip column, that means your CPU is using Chipset Clock Modulation throttling to lower the performance of your CPU. Go to the left side of ThrottleStop, put a check mark in the Chipset Clock Modulation box and set that to 100.0%. You need to click on the Turn On button at the bottom right to take ThrottleStop out of Monitoring mode and put it into active mode before you will be allowed to make changes to the 100.0% number.

If you are having problems, post some pictures of how you have ThrottleStop setup. I am hear to help. The quickest way to get help is to provide me with a screenshot or a ThrottleStop log file so I can see exactly what you are doing with ThrottleStop.

D2 Ultima - Most of the negative comments about lowering the timer resolution are not backed up with any testing. One of the complaints is that lowering the timer resolution will interfere with your CPU using the low power C States. The C State data displayed by ThrottleStop shows that there is hardly any difference. I can understand if a person is on battery power that maybe they should leave this alone. That's why the timer resolution goes back to the default value as soon as you unplug your laptop. When plugged in on AC, I have yet to see a single reason why you would not set this to 1. The default value that Microsoft uses for this value was first chosen back in the 1990s or earlier. A modern CPU can get WAY more accomplished during its time slice compared to that era so to me, reducing the timer resolution makes sense. If you ever find a benchmark that clearly shows an increase in performance or FPS, let me know. An increase in smoothness with less micro stutters is noticeable but it can be hard to prove to the non-believers.

Thanks for that comment. That is one problem I have. When I get busy adding new features, I never have enough time left over to actually use the features that I have added. Intel XTU would too often hang when starting it. Are you having any issues like that with ThrottleStop. Beta 2 has a new feature that disables the Cache overclock when going into stand by mode and then enables it after a successful resume from stand by. This has made a huge difference for me. My Y510P can resume now from stand by with no issues even when the Cache multiplier is fully maxed out.

 

Thank you In my previous comment, I said left instead of right, I wanted to tell you about what I see in the monitoring area. Anyways, I have taken two pictures of TS and RealTemp that can give an idea of what's happening.

This is when I alt+tab out of the game while it's running smoothly and take a screenshot immediately: http://www.mediafire.com/view/3ext7rq6pg13r7c/ingame.png#

And this is what I see when the spikes occur: http://www.mediafire.com/view/x3uuhgfkdb4ktbb/fpsdrop.png#

I get about 3 minutes of the smooth gameplay, after which comes the FPS drop that lasts about 30-60 secs (maybe less. feels like a lot). And it goes on like this cyclically.

Also, I have performance mode selected in Control Panel, with minimum CPU usage put to 100%.

 

Your second screenshot shows 25.0 for each core of your CPU in the Chip column. That is a sign that your CPU is being severely throttled. My previous post tells you how to fix this problem.

Follow that advice and see if that helps. Post another screenshot with this change and run a ThrottleStop - Log File if you are still having some problems and copy and paste your data to www.pastebin.com and then post a link here.

Edit - It would also be a good idea to put a check mark in the Set Multiplier box to make sure that your computer does not try to use that throttling method next.

 

Hey Unclewebb - I have a couple of thoughts regarding running as a service:

I've managed to get the app running (great!) and of course, no gui. I thought though - since it's basically a scripted CMD line to start, configure, stop etc (SC.exe built into windows) then is it possible to create a Service installer within the app? My suggestion would be something like - Split the app into a driver (service) and a gui (which you can configure the ini) then just restart the service when configuration changes have been made. If possible also it would be great to run the app as a boot service, or at least - the earlier the better.. It's a minor improvement of course, and perhaps not worth your time - but just wanted to suggest it

Also I sent you an email - hope you're well and keep up the amazing work!

 

Yeah, there is no real difference while plugged in except that stutters are less apparent in various games I have and use. Plain and simple. I've recommended it to my friends time and time again and every one on Windows 8.1 has noticed a distinct improvement in overall smoothness of the machine. If anybody else is a non-believer, let them sit there and stew while we move ahead.

As for the XTU hanging, I do not get that issue. It is possible that I'm all on SSDs here and that's why it works, but otherwise, no issues whatsoever with or without TS8 running with regards to XTU. The only issue I have is that since I pinned it to my start menu, it doesn't seem to find "limit reasons" when I click on the button, but it is mostly a non-issue for me since I can just open the TS8 folder.

 

ThrottleStop 8.00 beta 2
https://www.sendspace.com/file/b4oure

New Features:
- ability to change the Log folder and Limit Reasons location.
- TS Bench changed back to the original algorithm.
- minor changes to the TS Bench layout for improved high DPI support.
- added a Default Cache on Stand By option.
- more intuitive Offset Voltage Range adjustment.
- TDP Level multiplier reporting for the U CPUs.
- fixed Bay Trail power consumption and C State reporting.

 

Sorry it took me some time to get to this. My issue was that ThrottleStop can't increase TDP unless the value has already been increased in XTU. Here are the 2 screenshots you asked for. They look the same to me. I have also attached the MSR log file. Thanks!

P.S. Changing TDP limits to less than stock (17W) has an effect, but higher still tops out at 17W under load. This is all without XTU installed.

 

unclewebb,

Thanks for this beta release it is great!

One question, What API / method do you use to adjust the Intel FIVR voltages? I am trying to adjust the dynamic voltage offsets in Linux, but apparently there exists no tool to do this. And ThrottleStop does not run with Wine (although this was expected)...

After some research it does not appear to be doable simply by writing to MSRs.

Any help would be appreciated - I am not trying to write a ThrottleStop-like tool for Linux I simply want to undervolt my CPU under Linux..

Thanks in advance!

 

Sigs are off for me as they do not (normally) convey current information and generally slow down my reading speed on forums.

No problem, I now have the latest 8.00b2 from unclewebb's latest post.

 

ok i put the Gelid on my GPU and CPU. Tested 3D Mark 2011 Standard benchmark before and after.
GPU now only gets 60°C / was 63°C before
CPU now only gets 78°C / was 83° before
3D Mark Point stays the same ;-p

so that are good results for a <10€ investment... ;-D

 

LOL... I need to flash unlocked BIOS first... Damm 67W CPU power limit..

Indeed.. I had a similar result with IC Diamond

 

Ok, just installed 8.00b2, can indeed confirm high dpi is working (it changed more fonts than I expected), Limit Reasons opens flawlessly and interestingly within ThrottleStop's process, therefore no taskbar button for it, but sadly Overclocking still needs to be rechecked in order for the overclock to get applied.

I take it TS Bench results can't be compared between light and heavy versions, right?

Added ThrottleStop main window screenshot for high dpi scaling reference (125%).


EDIT: When I mentioned fonts changing, I meant different font sizes on the main window, whereas I thought that only TS Bench would be affected by the fix.

 

There are 2 sets of registers that can be used to limit the power consumption of the CPU. The programmers of Intel XTU have access to the full documentation and have access to both sets of registers. ThrottleStop is only able to access one set of these registers. For some laptops, that is enough but for some other laptops, you might need to stay with XTU. When using XTU, can your U CPU run above 17 Watts for a sustained period of time? Can you run ThrottleStop at the same time and turn on the Log File option while you are testing. You can copy and paste the info to www.pastebin.com

Let me know what stress test you are using to load your CPU.

This is still a secret and I am not yet sure if I am going to share this information. There is an email address in the About box of ThrottleStop if you would like to talk about this off the record.

You complained about high DPI so while I was fixing the TS Bench, I also changed a few of the other fonts. I am using a very old version of Visual C++ so it takes some extra programming so things don't look too ugly at high DPI settings.

Limit Reasons does not have a Task Bar icon even when you double click on it and run it that way. It's just a small and simple program that Dufus threw together. When testing, it tells me what I need to know.

The TS Bench results from beta 2 should be the same as TS 7 and previous versions. Beta 1 and Beta 2 are completely different and not comparable. Beta 1 used some newer instructions which made the benchmark run much faster but unfortunately it did not generate enough heat so it wasn't much of a benchmark. I still plan to write an AVX version someday. Hopefully that will create some heat.

I am not having this problem at all. When my CPU is at default settings, the moment I start ThrottleStop, the overclock is applied. When you are in the FIVR window, just above the OK button, try using the OK - Save Voltages Immediately option. After that, exit ThrottleStop, reboot and see if the overclock is applied. Are you starting ThrottleStop with the Task Manager? If you are still having problems, can you send me your ThrottleStop.INI file so I can have a look. You should be able to use www.pastebin.com for that info too.

If you moved the ThrottleStop folder from one directory to a different directory; the ThrottleStop.INI file might be write protected now. Try deleting that file and start ThrottleStop again so it can create a new one.

 

Oh, but it's great that window scaling is working perfectly now, just that I was caught by surprise by fonts changing

Well, one could look at 8.00b1 TS Bench as too efficient, but I think I understand what you mean.

Ok, I did set the Ok - Save Voltages Immediately option and... alas, overclocking works at logon! You sir are nothing short of amazing, I tell you *hats off*
The .ini file was never write protected, even when moving it between different ThrottleStop subfolders, which I believe could also be observed through toggling settings and said settings sticking. But why would the Save Voltages Immediately option impact my situation, given I didn't touch voltage settings at all, only the Overclock feature?

Also, considering I have my CPU set to 4.5GHz, would you find a CPU cache ratio of 42 (both min and max) to be a better setting than the stock 40?

 

I am as surprised as you are. TS8 b2 definitely looks better on high DPI screens than previous versions did.

For 4th Gen Haswell CPUs, the overclocking multiplier and the voltage information are both contained in the same register so the 2 are related. After I do some testing, I will need to add some more information about this to the Save Voltage Changes section so it is clearer. Thanks for your feedback about this.

A cache ratio of 40 vs 42 will barely be noticed in the majority of applications. I always like making sure my CPU is running at its peak and I like being able to use ThrottleStop to set my Minimum Cache Ratio higher than Intel XTU lets me set this but practically speaking, if you are not benchmarking, it doesn't make any meaningful difference one way or the other.

 

It's also that whole thing of being used to TS6/7/8 with the same look and finding an unexpected change... well, unexpected I'm currently on a 1440p 27" screen and TS8 does display everything in a clear manner.

About cache ratio, I sure would like to set it to 45, but I don't believe the system'll maintain stability at stock voltages (I'm a bit adamant at not feeding additional voltage, at least for now), but I might stress test it later.

 

3 - 5 degrees reduction was as expected. superb

 

If you ever use CLU on that CPU, expect that temp to go down to about 72 deg

 

Okay @unclewebb I noticed something odd. I just ran the notification area cleaner and whatnot and turned off TS8 beta 1 etc. Ran Beta 2, and in setting things up I noticed this thing:

Spoiler

Notice how throttlestop has the timer resolution set to 5 but the reported windows timer resolution is 1.001? I don't understand that. Shouldn't the timer res have defaulted back to 16 without TS8 beta 1 running? And shouldn't it be showing "5" rightnow since my timer res in TS8 is set to 5? I had already turned on TS8 beta 2 (as you see) and I hit "ok" at least once before bringing back up that options menu to see if that timer resolution would have defaulted back to "5", but it didn't.

I also checked by unplugging my PC and seeing if clockres.exe would show if my current timer resolution would change back to 16ms, but it was still at 1.001ms on battery.

EDIT:
Okay, I've restarted my PC and without any version of TS running, I get 1.001ms timer resolution. So I don't know why it's frozen like that... let me see if I can change it with TS7.

EDIT:
Even using TS7 to force timer resolution to 16ms doesn't seem to work; clockres still thinks I'm on 1ms.
Even closing every other program except task manager/headset software/mouse software I'm at 1ms. It seems like my version of windows is set to run at 1ms 24/7?

 

D2 Ultima, have you used any other software for the sole purpose of changing timer resolution before? If you did, perhaps its effects could've been stored on the system.

 

No, I haven't. Only clockres.exe to check if timer res was working properly.

The only thing I could possibly think of is that I probably had a shutdown at some point (like a black screen shutoff) while timer was at 1ms and somehow it stuck? But that doesn't explain how TS8 fixed my clock going out of sync if that was the case.

 

This is late reply, but I saved a screen dump of testing Bay Trail Atom using your new v8. I too noticed that didn't throttle on it's own without using Trottlestop, but I did notice that the IGP increased temp by a significant amount and would easily throttle the IGP losing speed with reduced frame rate. Bumping the power limit from stock 4 to 5 allows consistent full turbo from the IGP. Played around this this a bit lower to just 3, then the clock speed of the IGP would throttle under half of turbo. Also was able to lower the Vcore which took off good 5-7C from everything running, which isn't bad for something that doesn't really have a active cooling. Therefore from what I can see using ThrottleStop with Atom Bay Trail isn't fruitless, and can have a purpose of allowing full turbo on integrated graphics and the change to shave of a few degrees, maybe be easier on the tiny power adapter under stressful loading.

 

#THROTTLESTOP WIN

Anyway, update. I ran
powercfg -energy duration 1
in CMD and got the dump file and checked it and it counted my twitter program, my mouse software and chrome as programs lowering my timer resolution.

I proceeded to close every single direct program on the PC except display drivers/chipset drivers, basically. Then I used CMD to create a new dump file and check, and this time it didn't even list any programs; just simply said my PC was configured well but timer res was 1ms. So... I think it's a registry error or somesuch thing. Since timer resolution handles the lowest possible value set for it, throttlestop cannot override that and set it to "16ms" because something else at the kernel level seems to be setting it to 1ms.

So what I listed above is probably not a TS8 bug at all. I don't know what it is, but restarting the PC and stuff doesn't help it, so assume it to be a "D2 problem" and not a "Throttlestop" problem.

I'll still keep using it as it's great for temp monitoring and adjusting my CPU =D. Down with XTU, up with TS8.

 

ClockRes 2.0
https://technet.microsoft.com/en-ca/sysinternals/bb897568.aspx

With ThrottleStop running, ClockRes shows the system timer set to 5.0 ms



As soon as ThrottleStop exits, the timer gets reset to 15.6 ms so there must be something else running on your computer that is changing your timer resolution. It is possible to go as low as 0.5 ms but at the moment, ThrottleStop only allows you to go down to 1.0 ms.

I used this freeware program to test out 0.5 ms.

http://www.lucashale.com/timer-resolution/

My Asus VivoTab 8 has the power limit set to 5 by default. I guess if you had one of these devices and the manufacturer set the power limit to a very low number then TS8 might be useful. I was hoping to transform the lowly Atom into a Core i Extreme but it didn't happen. Remember to download TS8 beta 2 from my signature. I fixed the C State reporting as well as the power consumption reporting. The new version agrees with HWMonitor now.

 

my laptop is based on atom，baytrail-T，Z3735D

before use ThrottleStop_800，in aida64-CPUID，this is PL1 2.2W and Unlocked


just open it，refrash the software，I can see it has removed，PL1 11.8W，PL2 14.5W with 110seconds


open furmark，CPU package is 3.6-3.8W，and IGP keep 620mhz which is the max turbo


stress CPU，CPU package rise to 4.46W，and all clock keeps max turbo


before use it


the score changes a lot，66%-71%，so the PL1 can determine IGP's performance
but temp is worse……

my English is not good……

 

my ID is chinese，but it seems to be incorrect……孤独凤凰战士 or jeff……

 

Yeah, I said it in a post after the one I tagged you in, but my PC seems to be hard-locked to 1ms timer resolution. I can't change it, and no programs are causing it. Even when I exit everything and use CMD to run clockres and the energy duration dump file from WPF, it doesn't list any programs as being at fault. I guess it'll have to change with an OS reinstall or I have to contact microsoft.

 

Has anyone tried it with a core m 5y10c?
Would love to see results if it actually works, supposedly these chips throttle if temps are too high but this would be a perfect CPU to try it on .
Would you be able to undervolt to keep temps lower and maybe increase performance.. ( OK not increase performance but to let it run at full speeds without temp throttling)
Thanks

 

I might have found an oddity with TS8b2.

If I use TS8b2 and go to TPL, and change the turbo time limit to 64 and apply, then I check the value in XTU (turbo boost power time window) it does NOT show 64sec. it shows 0.00097656 seconds.

However, if I change it in XTU, and check in TS8b2, it shows 64 sec.

Unless I am comparing the wrong thing and if so, feel free to set me straight.

 

Thank you Jeff for posting your results. That is a huge increase in performance. It makes sense. When CPU power consumption increases, the temperature of the CPU will increase. More performance equals more heat.

You can also use ThrottleStop to lower your Bay Trail CPU voltage. This can help reduce heat.

That sounds like a bonus feature. You should thank Microsoft.

 

After you make changes with ThrottleStop, you will probably find that XTU does not automatically update itself with the new settings that ThrottleStop has set in the CPU. Both of these programs are trying to write information to the same registers within your CPU. I would not trust what XTU reports after using ThrottleStop.

To make sure that ThrottleStop is setting your CPU up correctly, after you boot up and before you start ThrottleStop, run CPU-Z, click on the About tab and then click on the Save Report (.TXT) button. CPU-Z will take a snapshot of your CPU registers. Look for the line that incluldes MSR 0x610. That register contains information about the turbo power and turbo time limits.

Code:

MSR 0x00000606        0x00000000    0x000A0E03
MSR 0x00000601        0x00101414    0x800002A8
MSR 0x00000610        0x804281D6    0x00DC8178

If you would like me to double check this, post the above 3 lines from the CPU-Z Report before you run ThrottleStop. Run ThrottleStop and make your changes to your turbo time limit or power limits and then run CPU-Z again, take a snapshot and post the exact same 3 lines. If this register is not locked, you should see some changes in MSR 0x610. MSR 0x601 has information about your current limit and MSR 0x606 will just tell me what units MSR 0x610 is in.

Post some screenshots and post some more information so I can help you out.

 

yes，when I stress the CPU and IGP for few minutes, the temp gets to 89℃ and then PL1 changes to 2.2W automatically.If the stress does not stop, then PL1 drop at 1W or lower. I can see the ratio become lower and lower. When I stop it, CPU is only 83.3*9 at most, and after a few seconds it can incrase one ratio.It seems to be the BD PROCHOT, which QUANTA ODM used in TWK and NL8.
Can I skip this BD PROCHOT?

 

If it was my laptop or tablet, I would turn off BD PROCHOT but maybe this will cause damage. Probably not but I do not know for sure. It is your decision. If you are worried that you will damage your laptop then you should not use ThrottleStop. Disabling BD PROCHOT might not make your laptop run any faster. There could be another temperature sensor that limits your performance when your laptop gets really hot.

Can you post a screenshot of ThrottleStop so I can see how you have it setup.

 

before:


MSR 0x00000606 0x00000000 0x000A0E03
MSR 0x00000601 0x40101414 0x80000100
MSR 0x00000610 0x004280C8 0x00978098
MSR 0x00000611 0x00000000 0x07002487

After:

MSR 0x00000606 0x00000000 0x000A0E03
MSR 0x00000601 0x40101414 0x80000100
MSR 0x00000610 0x004280C8 0x00218098
MSR 0x00000611 0x00000000 0x0756E9E2

Ok, so what's that telling me?

 

That is probably not telling you anything because it looks like a bunch of gibberish.

That bunch of numbers tells me that you probably have a U CPU because the power limits appear to be set to 19 Watts / 25 Watts and your current limit is locked at 32 Amps.

Code:

MSR 0x00000610        0x004280C8    0x00218098

If my calculations are right, it looks like you changed the turbo time limit from 3 seconds to 64 seconds. In the above line where you see the 2 digits 21; that is the code for 64 seconds. Intel created some overly complicated formula to pack a wide range of time values into a limited amount of space. For your next test you could try using only Intel XTU and try setting your turbo time limit to 64 seconds and then have a look at register MSR 0x610. For your CPU, if those 2 digits show 21 then your time limit is 64 seconds.

 

Xtu shows same. It just isn't reading it right. No shock. It is an i5 cpu in a surface pro 3, I'm trying to get the most out of it, but stable. I have undervolted a slight bit and thought if I bumped the time it would stay at "turbo" might help some. Not worried about battery life as much as thermal and power of cpu. I will accept any suggestions. And thanks for confirming.

Sent from my SM-N910T using Tapatalk

 

I just downloaded Intel XTU 5.1.2.2 and the latest version is still ignoring the lock bit on the power limit register.

http://i.imgur.com/aQNmRIM.png

The first digit 8 in MSR 0x610 confirms that the power limit register is locked. ThrottleStop shows a check mark in the Lock box. Intel XTU allows me to make changes and when I hit Apply, XTU shows that it has changed the power limit from 255 to 128. If you look in the power limit register it continues to show 7F8 for the long and short term limits.

0x7F8 = 2040
2040 / 8 = 255 Watts

In other words, nothing has actually changed. I booted up with both of these set to 255 and that register is locked so it will forever be at 255. The guys at Intel need to start reading their own documentation.

You can use ThrottleStop to make some slight improvements to a Surface Pro 3. When adjusting the power limits or the time limit, some settings will be ignored by your CPU. The maximum time limit for a 3rd Generation Core i5 U CPU was 32 seconds. If you set this to 64, that value will be ignored. I am not sure what the CPU will then default to and I am not sure if the 4th Gen U CPUs are still using the same 32 second limit. The 3rd Gen had a limit of 24 Watts for the long term turbo limit. Same as before. I am not sure what value the CPU will use if you try to go higher than this limit.

I don't own a Surface Pro 3 so you will have to do your own testing to see what works best. At least Microsoft was nice enough to leave this register unlocked so an enthusiast can play around with these settings. Like any laptop, you will probably get higher maximum performance when plugged in.

 

If what you're saying is correct, and 64 isn't being properly accepted, maybe that's why XTU is defaulting that back to the 0.0009xxxx number. I shall take your advice and set it down to 32sec. I'm quite sure that the overclock and power changes are probably locked pretty tightly on here, considering the power supply and battery are a finite number. I suspect other than the dynamic undervolt, there isn't much further I can accomplish.

I was suggested to look at the intel power balance under TPL and to increase the GPU portion. Not sure if that makes any sense?

 

Maybe I'm missing something, but you ought to be worried if the timer was hard locked to 15.6, not to 1.0 Now, in all fairness you having it set to 1.0 will impact battery as the expense of having more (subjectively theoretical) performance and (unquestionably real) lower latency, which is beyond welcome for anyone who works with audio.

On the timer resolution note, I do hope that ThrottleStop can eventually allow adjustments on the whole 0.5-15.6 range. I've been using that tool you linked for years now and having the possibility to integrate the same functionality on a single software package would be quite handy.
I'm yet to find out why my desktop defaults to 1.001 rather than 1.000, though. (when not using the tool)

 

Your desktop defaults to 1.000 but reports a slightly higher value. It's also rounding up, if you use powercfg to generate an energy report you'll see a reported value of 1.0007 for example. (with requested value of 1.0000).

 

The interesting bit is that my laptop (on the sig) had perfect 1.000, and it couldn't have been due to OS as that happened on both Windows 7 and 8.x.

 

It's supposed to be 15.6ms, at which point I would have been able to get better battery experience. I know at one point it was at 15.6ms because forcing it with TS7 and then TS8 caused no end of benefits to me.

I think that's a rounding function; like why it's 15.6ms and not 16ms

 

It was all part of my master plan. Create a unique program that many users cannot be without. The Y510P and Y50 are much better laptops when ThrottleStop is running.
Thanks for the positive feedback as well as showing us how to hunt down timer resolution issues.

 

I have tried again, but something has changed...

just open it, the PL1 changes to 11W and PL2 appread

TPL shows PL1 set 11 and PL2 set 14. Turbo time limit seems to be wrong.

when I stress the CPU and IGP, at first every thing goes normally, CPU package is about 4.4W.

This time, the time keeps longer. However frequency goes down at last. The temp is also lower than the last, 82℃.

The ratio has changed in few seconds.

The ratio goes to 9x

The ratio decrease 1x at once. But if it is lower than 6x, it will change to fractional part.

At last, the frequency is baout 64MHz. The screenshots has something wrong....

Then, the ratio will increase. The frequency will be 64~300MHz unsteadily.

When I stop the stress, the ratio will be increase, one ratio at once in few seconds.
GPU clock is always 620MHz, never changed.

maybe the information can help you....
In fact, this tablet is just ＄80, very cheap...

 

On the right side of ThrottleStop look in the CMod column. That reports Clock Modulation throttling and at one point it is down to the minimum which is 12.5. That will make your tablet run very slow. On the left side of ThrottleStop, try setting that to 100.0 and put a check mark in that box.

I would also check the Set Multiplier option and set that to 22 for your CPU. The Voltage ID will not work correctly unless Set Multiplier is checked.

 

When I set 22x and open it, the tablet will crashed...

 

If your tablet crashes it is because you have set your voltage too low. Set your voltage to the maximum before clicking on Set Multiplier. Do not lower your voltage unless you have done some stability testing like Prime95 or a similar stress testing program.

Edit - Can you run CPU-Z and go to the About tab and click on the Save Report (.TXT) button and then show me or send me that information. I just need to see these lines.

Code:

    MSR 0x000001FC        0x00000000    0x0044005E
    MSR 0x00000606        0x00000000    0x000A0E03
    MSR 0x00000601        0x00101414    0x800002A8
    MSR 0x00000610        0x804281D6    0x00DC8178

 

Code:

MSR 0x0000001B        0x00000000    0xFEE00900
    MSR 0x0000003A        0x00000000    0x00000005
    MSR 0x000001A0        0x00000000    0x00850089
    MSR 0x0000066C        0x00000000    0x13131616
    MSR 0x00000017        0x00040000    0x90141645
    MSR 0x000000CE        0x00000600    0x00001000
    MSR 0x000000CD        0x00000000    0x00000000
    MSR 0x00000606        0x00000000    0x00000505
    MSR 0x00000601        0x00000000    0x00000000
    MSR 0x00000610        0x00000000    0x00028020
    MSR 0x00000611        0x00000000    0x000E6424
    MSR 0x00000639        0x00000000    0x000BA6F0
    MSR 0x0000019C        0x00000000    0x88440040
    MSR 0x000001A2        0x00000000    0x00690000
    MSR 0x00000198        0x00007400    0x00000E38
    MSR 0x00000199        0x00000000    0x00000E38