Throttlestop 9.7.3 Legion 7 Pro 13900HX, RTX4090 locking frequency issue

[Lechu1777]

For clarity and easier to find for future reference, I'm creating this post here, regarding @unclewebb post on reddit: REDDIT comment

So many people with 13th/14th Intels are having the issue with cpu speed lock when using MMIO Sync/Lock. Let's try to figure out together if we can solve it.

I'm using the latest 9.7.3 version, which is supposed to fix the issue, but I tried both (separately) MMIO lock and MMIO sync, they both end up affecting CPU frequency on load and the only solution to unblock it again is doing a hard reset by holding the power button and starting up again.

I am attaching a few screenshots with current settings, all other TS views not included means I haven't touched them. I have marked two checkboxes in TPL section I have tried and both are causing the same issue,
which is locked CPU frequency at a value, I have seen 3.9Ghz once and 4.1Ghz another time. Limit Reasons always stay clear, there are neither warnings nor errors, I assume temps are too low for that, it's nowhere near the limits. Also I think when that happens then all Cores (P+E) are running under load at similar locked frequency and they are not even going down when the test ends, but I'd have to do more tests to be certain. Sorry but it's 1AM already, so I'll have to postpone further testing and call it a day.

The laptop I have is Legion 7 Pro with 13900HX + RTX4090, limits are 140W/190W, but I can see that Lenovo changed something along the way and now performance mode applies 185W PL2 (dynamic) and custom mode allows full 190W, but I tried both modes and it doesn't change anything as to the issue. And during Cinebench (at full clocks) those values apply just fine, CPU gets ~185-190W

I have found someone on reddit who claims that old NV drivers did not cause this issue for him, but newer ones does? I don't know how it might be related, but maybe it is. At some point I can DDU NV drivers and test it out with old ones. For me the main reason to get it fixed is because Lenovo applies some weird 85W limit when I am playing a game for a longer time, which locks CPU to 85W for no reason whatsoever and then it randomly changes back to default 140/190, and it's weird because the CPU temps are around 80-85C, far from set limit 98C and NV GPU drains around 90-120W, which combined is still within limits. Obviously when I lock or sync MMIO this doesn't happen and the CPU drains up to 90-95W while playing the game, because of fixed 140/190 limits.

If you have any suggestions or tests I can do, I'm looking forward. I should be able to provide some feedback in 1-2 days.

 

[unclewebb]

When the CPU is stuck at a fixed frequency, open up the new Per Core window. Post a screenshot of ThrottleStop with the Per Core window open. It is possible the Per Core values are not being set correctly. The main reason I added this new feature is to try and troubleshoot the problem that you have.

In the TPL window try checking the Speed Shift box and set Speed Shift Max to the max, 255.

I have a MSI laptop with a 14900HX and my CPU never gets stuck at a fixed frequency like other users have reported. It is difficult to troubleshoot a problem if it never happens on my laptop. There could be some sort of interaction between ThrottleStop and Vantage.

Thanks for offering to help. Hopefully we can figure something out.

 

[eniva]

A few days ago my speeds were also blocked and it may not be the same problem but I activated the high performance plan from the main throttlestop window and it started working correctly again.

Perhaps the problem comes from there, with some conflict with Windows and the power modes.

 

[Lechu1777]

Ok, I haven't been able to reproduce this problem ever again with Sync MMIO checked. I have no idea why it occurred earlier and it was consistent, even including system restarts (no fast boot).

1. Per Core limits stay aligned, Defaults/Now/Use show the same values when running Cinebench
2. PL1/PL2 stay locked during longer load sessions, I don't get weird 85W limit anymore, that was the crucial part for me.
3. For what it's worth, probably unrelated, but my NV drivers are 572.16, Legion BIOS KWCN48WW (latest as of today)

A few days ago my speeds were also blocked and it may not be the same problem but I activated the high performance plan from the main throttlestop window and it started working correctly again.

Perhaps the problem comes from there, with some conflict with Windows and the power modes.

I have never used power plan binding in Throttlestop, but I use Ultimate power plan, which Throttlestop does not recognize, anyway.
But just for the fun of it I changed my Windows power plan to Balanced and it gave me almost the same Cinebench result, no frequency lock happened.
I think in that case Lenovo Vantage Performance Mode and Throttlestop 140W/190W MMIO Sync have the upper hand.

Attached screenshot with benchmark results, freqs and power.

If I encounter the problem again, I'll share it.

 

[unclewebb]

I think there could be multiple factors that are causing the locked frequency issue.

Another user on this forum was able to track his locked frequency problem to having the Intel XTUService.exe running in the background that he was not aware of. He had not installed Intel XTU but this was part of Synapse / RazerXTU. Some manufacturers have their own branded control software. Most of these control programs are using the Intel XTU libraries.

ThrottleStop ratio limit changes don't apply anymore

Hello all, Up until 2 days ago everything was working like clockwork, voltages, V/F points, multipliers etc was working perfectly. It all changed with intel igpu driver update, no bios, no other new changes. I updated like I usually do: downloaded the package > went offline > deleted intel...

www.techpowerup.com

Check the Task Manager to see if there is anything XTU related running in the background. I used to think that you could run XTU and ThrottleStop together as long as you did not start XTU. Now I would recommend that if you are going to use ThrottleStop, completely uninstall XTU. Remove any XTU remnants that might have gotten left behind. There should be nothing XTU related running in the Task Manager.

I am not sure if Lenovo Vantage uses the XTU libraries. One look in the Task Manager should answer that question.

The problem seems to be with the ThrottleStop MMIO Lock option. This box is checked on my MSI laptop and I have never had any frequency locking issues. It seems that on some computers, if the MMIO power limits are locked out, a secondary control method is used which can significantly lower and lock the CPU frequency. It might also lower the turbo power limits.

@Lechu1777
If you ever want to do some more testing, clear the Sync MMIO box and try checking the MMIO Lock box instead. In theory, doing one or the other should work exactly the same. A CPU should not get locked or limited no matter what box you check.

If this turns out to be a Lenovo Legion specific issue then I might have to add some sort of warning message to ThrottleStop. Something like, do not use MMIO Lock.

 

[Lechu1777]

Well, actually I have both Razer Synapse app and XTUService. Razer Synapse does not auto start, I only have it installed to occasionally make some changes in mouse settings, but I don't keep it running. But XtuService (XTUOCDriverService) is very much running in the background and I have never installed Intel XTU soft manually. I am not sure if it comes from Vantage or from Razer Synapse, my guess goes to Vantage since it also has built-in OC and UV option, very limited, but they are there. Moreover, there are quite a few software components in Device Manager with XTU in the name, when I open any, it shows Location: on 13th Gen Intel(R) Core(TM) i9-13900HX. Attached screenshot. I probably should not touch them and I am not even sure I should disable XTUService without causing too much trouble.

Do I need to restart my laptop every time I change MMIO Sync or Lock checkboxes to make effect and possibly trigger the issue?

 

[unclewebb]

Do I need to restart my laptop every time I change MMIO Sync or Lock

I would recommend completely shutting your laptop down whenever changing between those two options.

I have never installed Intel XTU soft manually

That is the same as the other user that was having troubles with his CPU locking to a fixed frequency. XTUService seems to be doing things to the CPU settings that it should probably not be doing, In his case it was the Per Core multipliers that were being set to a lower value. If you ever have this problem again, check the Now column in the ThrottleStop Per Core window to see if it has changed. Try closing and opening the Per Core window a couple of times. I originally programmed that window to constantly update. This did not seem necessary so I got rid of that feature. Maybe I will add that feature back so it will be easier to see if something is changing the Per Core values.

Razer Synapse does not auto start

Once again, the same as the other user. XTUService seems to always get started whether you are using any of its CPU control features or not.

there are quite a few software components in Device Manager with XTU in the name

Next time you have any problems, try killing and then disabling XTUService so it does not start.

I have both Razer Synapse app and XTUService

It is possible that Synapse is installing an older version of XTUService. That version might have a bug or two that has already been fixed.

I have not done any XTU testing in many years. The biggest problem I used to see was that it was very inconsistent, especially after resuming from sleep. It would show that it was changing the voltage or some other setting. When I would manually check the values of registers within the CPU, it was obvious that it was not applying the value that it was claiming to have applied. If you have any problems in the future and if you cannot uninstall everything related to XTU, you might have to uninstall ThrottleStop instead.