mV Boost @ 800 MHz - weird effect in HWiNFO

[Intrepidity]

In case of relevance: Lenovo Legion Pro 7 13900HX.

I attempted to set mV Boost to 50 as my impression is that it might help with unstability at idle due to high offset.

Not set, everything seems normal:

When define 50 mV boost I see the expected data regardless of load in Throttlestop and HWMonitor. HWiNFO however show up like this even when opened when running a stresstest to ensure correct data:

As I didn't understand if it's a bug related to how data is being read or something now being set uncorrectly I set it to 0 and disabled the setting. This did however not affect the data shown in HWiNFO even after a reboot. Still +0.050. To change the value shown in HWinfo I have to enable the mV Boost setting with another value. I am not able to get HWinfo to show the actual UV regardless of what I do. It only show the previously set mV Boost value regardless if the setting is active or not.

So, is something now set uncorrectly? Or is it just a bug related to how HWiNFO read data? Sorry if this is a known issue. Couldn't find anything explaining it when searching.

 

[unclewebb]

On my 10850K, HWiNFO does not seem to update the voltages that it is reporting. If I use ThrottleStop to make a voltage change, this change will immediately show up in the FIVR monitoring table. I need to exit HWiNFO and restart it to force the HWiNFO monitoring table to update itself. You can depend on the ThrottleStop FIVR monitoring table to report the CPU VID voltages correctly. The ThrottleStop data is accurate and it is being updated in real time. You cannot always trust what HWiNFO is reporting for the VID voltages if this data is not being updated.

If you want to reset the offset voltage, Unlock Adjustable Voltage has to be checked. Select an offset of 0 mV and press the Apply button. Make sure that the offset voltage has been zeroed out in the FIVR monitoring table. Ignore HWiNFO. If you exit ThrottleStop with an offset voltage already set, ThrottleStop will not automatically reset the voltage. If you do a fast restart in Windows, some computers will not automatically reset the voltage. You need to specifically tell ThrottleStop to set the voltage to zero if that is what you want.

The mV Boost feature works the same way. If you set this to 50 and then decide that you do not want to use it, while mV Boost is checked, you need to set this to 0 and press Apply so this information is sent to the CPU. After you do that, then you can clear the check mark in the mV Boost box. If you clear the mV Boost box without resetting this, the previous value will still be active in the CPU. A quick Windows restart might not reset the mV Boost register within the CPU.

The mV Boost value is separate from the other VID voltage values that are in the FIVR monitoring table. You will not see any changes in those values when using mV Boost. The only change you should see is in the reported Voltage ID value in the FIVR monitoring table or the VID value reported on the main screen of ThrottleStop. Here is an example with the CPU locked to 800 MHz with mV Boost set to 0.

Here is an example at 800 MHz with mV Boost set to 100. It is easy to see the change in the Voltage ID and VID.

HWiNFO does update the Core VID information that it reports in real time.

I have never tested the ThrottleStop mV Boost feature on a 13th Gen CPU. Almost no one has ever told me that they use this feature. With little feedback and no access to any modern hardware for testing purposes, I just have to assume that mV Boost continues to work the same as it works on an unlocked 10th Gen K series CPU.

 

[Intrepidity]

Appreciate the detailed response. I think I understand how it's supposed to work, but it doesn't work like that. As mentioned the data in HWinfo persist after restart of computer, HWinfo and Throttlestop. If it's just a bug in HWinfo in relation to how it's reading data that's fine, but as I currently don't understand why it won't update I wasn't sure if there is an actual issue or not. The only way I found to alter value in HWinfo is to set a value in Throttlestop (not 0, no change) and then restart HWinfo to make it update. It's currently seemingsly not possible to make HWinfo show the actual UV as visible on HWmonitor and Throttlestop.

I'll assume it's a bug in HWinfo for now

 

[unclewebb]

I'll assume it's a bug in HWinfo for now

Not sure why but HWiNFO does not update the voltages it reports in real time. Voltage changes made in ThrottleStop will not be reported until you restart HWiNFO.

If voltage info persists after a restart it is because either your BIOS is not resetting the voltage register like it should be doing or you are not doing a full restart. When using Windows 10, you have to hold the Shift key down on the keyboard while selecting the Restart menu option to force a full restart. I have not yet tried doing this in Windows 11 but it is likely the same.