The ThrottleStop Guide

[RickiBerlin]

Originally Posted by unclewebb

Super SLFM should work on the T9300. Did you have PowerSaver and EIST enabled?

yes

Originally Posted by unclewebb

Can you show me a screen shot of ThrottleStop at idle?

yes, but I do not do it. Explanation follows...

Have the explanation for the malfunction of SuperSLFM = 1 found.
As always, it is very simple. One must know:
If you have already finished their profiles (including SLFM on) and adds the command "SuperSLFM = 1" only following one, then it does not work.
Here one must SFLM off and back on again + saven profile.
Result 6x100MHz works now.

Vice versa, it is this: Get back to reach the normal value (8x100MHz), it is not enough to change the value in the ini or delete them.
Even without this ini entry (SuperSLFM = 1) the factor remains at 6x100MHz.
Not even no program restart!
Here too, of SFLM off and back on again + saven profile.
Result 8x100MHz works now.

I decided not to post the pictures already finished it. Even though I have this creates extra each charged with Ini's, it's not really meaningful.

But here is a little picture puzzle for you. No "ini" or other changes.
(No need for assistance)

That just looks good that screenshots can also confuse.
As you can see Power saver of, and the CPU runs at 6x100. The default is 13.5x200. EIST is on! You do not employ so wanted to show it only. Operator error on TS surface are not excluded. All depends on the constellation of settings.
(Will remove this later, he is no help)

Originally Posted by unclewebb

EIST should be on for all profiles except your Dual IDA profile.

Against a lock in low end is talking, but nothing. Or what?
The CPU throttling can not. (So yes ThrottleStop )
It would be important but only before the end of "ThrottleStop" to enable EIST. (Factory setting for Steping)

Can you (or better still, to me) to explain the value of HWiNFO32?
Please note that the four lines of the picture are not to be taken seriously!

Finally, I love your little program! It makes my CPU very large.

[JKleiss]

Originally Posted by RickiBerlin

I love your little program! It makes my CPU very large.

Oh my lordy

[RickiBerlin]

Originally Posted by JKleiss

Oh my lordy

Sure, you've identified an ambiguity in this sentence.
Will not hope that it is the same which I think.
Good thing I do not know what I write and read it even less, in that language. See, I can not English. So the best position to chat something on this site.

[unclewebb]

Thanks for your testing RickiBerlin. I hate SLFM and Super SLFM so I never use these functions. My main desktop computer that I use for programming does not support these features so I did not test these options thoroughly. I will do some more testing today to make sure that it works correctly for users that like SLFM.

HWiNFO32 looks like a big bug but I don't know why. Was your real bus speed still 200 MHz when it went crazy? Like your ThrottleStop screen shot shows, all software does crazy stuff sometimes.

It is difficult to understand your German to English translation but I appreciate your help.

Finally, I love your little program!

That's what I like to hear.

[lidowxx]

Originally Posted by RickiBerlin

Finally, I love your little program! It makes my CPU very large.

Damn you, dude, you made me spray a whole mouthful of water on my screen!!!

[RickiBerlin]

Originally Posted by lidowxx

Damn you, dude, you made me spray a whole mouthful of water on my screen!!!

What the funny thing about this set?
If I "CPU" not to abbreviate, otherwise something else does. (Something that can grow in male users)
Please clarify for me! I would also like to "spray a whole mouthful of water on my screen"

[RickiBerlin]

Originally Posted by unclewebb

Thanks for your testing RickiBerlin. I hate SLFM and Super SLFM so I never use these functions.

No problem
Super SLFM's also completely senseless. can save power so you do not.

Originally Posted by unclewebb

I will do some more testing today to make sure that it works correctly for users that like SLFM.

Not necessary!
1. It works wonderfully.
2. One does not need.
3. If you would you take a bit more time for my text, then you knew Item 1.(1= It works wonderfully.)
It is only a setting order problem. (Did it accurately described above)

And this is what I wanted to show you with the ThrottleStop image. Your Program includes operating faults. The picture does not do with "Super SLFM.
It is not a program error, but an unpredictable for you at the same time senseless Program setting.
Explanation of my approach to generate the image state.
1. SuperSLFM = 1 entry in ini.
2. ThrottleStop start it and make the following settings.
In options, "Default Profiles on AC Profile" and "Start Dual IDA" on.
Now we create the profile "Performance"!
Full Multiplier, power saver on, on SLFM (EIST does not matter) and save! (Yes, this setting is total nonsense, but it's all about control errors)
3. "Forget not turn on" then quit "ThrottleStop!
4. ThrottleStop start. Wait until the highest multiplier was captured.
5. Now you can switch from the context menu IDA. (Stop Dual IDA)
6. Now you can see my image of this post.
Reason: Start Dual IDA "terminated while" Power Saver ", but" Stop Dual IDA "reactivated" Power Saver "without showing it.

And so it is very similar with "SuperSLFM.
Operating sequence errors.

Originally Posted by unclewebb

HWiNFO32 looks like a big bug but I don't know why. Was your real bus speed still 200 MHz when it went crazy? Like your ThrottleStop screen shot shows, all software does crazy stuff sometimes.

I can not say more. If you can run HWiNFO32, the CPU bar sometimes appears in red. This happens so fast that it can hardly be perceived. (Under a second) this moment I have been fit and creates a screenshot. The value of 4.1 GHz I saw only on the screenshot and was very surprised.

Originally Posted by unclewebb

It is difficult to understand your German to English translation but I appreciate your help.

No problem, I write from now on German.
This would save me a lot of work.

[unclewebb]

I found a few problems. After you select Start Dual IDA mode, if you click on Power Saver or some of the other settings, it can cause some problems like you have found. I'm working on changing a few things so ThrottleStop works more consistently and warns users or blocks Power Saver mode when it is trying to get into Dual IDA mode. Just a few minor changes for the next update. I like software that works consistently with no surprises.

[lidowxx]

I have a question about my X9100, so far i have used it at x12.5/1.2125v, and it works fine. The problem is I want to bump up another notch to x13, the thing is orthos always gives me error after a few min until I increase the voltage all the way up to 1.3v.

Out of curiosity, I tried the x13 multiplier at default voltage 1.2625v(3.46Ghz), I tried some CPU intensive games(dragon age, etc), some CPU benchmarking(cinebenchR10, 3dmark06 CPU test), and also fired up dolphin emulator and did a long session of emulation, which is very CPU intensive, oddly enough, I didn't get any errors and lockups during the usage. Does it mean I can safely use the x13/1.2625v 24/7?

[unclewebb]

If there is a CPU error or two in a game, you might never notice the results and the game might keep playing just fine. If you fire a gun and the bullet misses its target because of a CPU calculation error, you're never going to notice and life will go on. When Orthos or Prime95 starts giving you errors it means it did something like added 2+2 and got 5 instead of 4. That's not a problem for a game but that is a huge problem for a computer that is searching for the next Prime number.

Run your CPU as fast as you like but keep in mind that if it is producing errors, in the long run, you might have to reinstall Windows if it gets corrupted or might see some other hard to explain problems. For me, that's not worth it. I could run my CPU a little faster but no one would be very happy with me if ThrottleStop had some random data in it. TS is dangerous enough as it is.

I found some fixes for the problems that RickiBerlin found. I'll post an update in the near future. I added a couple of safety features like blocking access to the Power Saver feature when TS is already trying to enter Dual IDA mode.