Throttlestop problems after CPU swap.

I went from a t9600 to a Q9200. I've used TS for a year without a single issue. Now though, I'm having issues with settings sticking. It does different things at different times. Right now, I can force any settings that are below stock, but nothing higher than that. stock vcore and multi are 1.1625/9x




I checked CPUZ just to make sure this was what was happening.

Also, this is what it's doing right this second. The problem I'm having manifests itself in different ways.

Last night, I had it running fine at 1.325v and 3.2ghz. I started playing BFBC2 and was seeing what i thought was throttling, even though ts was enabled. So i start logging with TS, and it shows no throttling of CKMOD or CHIPM, but then i look at the TS screen, and the CMOD% for one of the cores was showing 87.5%. Also, in the TS log the multi would go from 10.5 to 10.49 in some cases. I also noticed that even though the vcore and multi were accepting changes, if i tried to lower the clock modulation, it would not accept the change I made.

So at this point im thinking that there's something in the ini or something from my previous CPU that's giving me problems. So I delete the TS folder, restart my comp, and then download another copy of TS. Suddenly everything is fine! All my settings were sticking, and BFBC2 isn't throttling anymore. So i figure that I had found and fixed the problem. Now though, it's doing what i mentioned in the first paragraph with the pics. Do i need to reinstall windows or something? Could it be the CPU itself? This is driving me crazy.

edit: i'll also note that i've used version 2.85 and 2.89 in the last couple of days with the same type of results.

 

I've tried to make some changes to ThrottleStop lately, to help situations such as when you change the CPU but unfortunately, everyone is busy so I haven't got a lot of feedback lately.

The facts of life are that the M17x-R1 has a serious throttling problem. When you install a faster quad core processor, it will try to draw more power which will result in more clock modulation throttling. There's only so much that ThrottleStop can do about that. If the bios really wants to throttle your CPU then it is going to throttle regardless of what ThrottleStop wants.

I'm sure I can improve ThrottleStop but I can't do that without any hardware to test on and without users willing to take the time to help me out with testing.

If you have the time to help me with testing then send me a PM. Send me a log file while gaming with the More Data option checked so I have lots of data to look at. You can upload it to Free File Hosting Made Simple - MediaFire

A tiny variation in the multiplier from 10.50 to 10.49 is not an end of the world moment. When lightly loaded or when clock modulation is being used, a slight amount of variation like this is normal.

 

I'll try and takes some logs when I get an opportunity. There seems to be no consistency though, I've witnessed instances of BCBF2 not throttling for 30+ minutes of play @3.2ghz/1.325v. Yet I've also seen it throttling with the CPU at stock speed/voltage. Does the machine set a lower throttling threshhold after it gets tripped once until you restart or something?

 

Thanks very much for finding this problem and letting me know about it. Someone else noticed a problem but when I tried to follow up with them, they didn't provide me with any further info so I had to assume that their problem went away. I found a big bug where the anti-throttling stuff was getting turned off behind the scenes which would explain some of what you were seeing.

ThrottleStop 2.90 beta 9
ThrottleStop_290b9.zip

If you have any more problems, can you post them in the ThrottleStop guide thread that is in my sig. Thanks. After the holidays, hopefully everyone will have more time to help me get ThrottleStop working like the good old days.

 

wow! thanks for such a quick and meaningful response. So far everything seems to be working fine with beta 9. I'll let you know how it works out.

I would probably really hate this computer if it were not for TS. I really appreciate what you do.

 

As mentioned, follow up can be posted here

http://forum.notebookreview.com/har...arket-upgrades/531329-throttlestop-guide.html

thanks.