weird effect after undervolting 13700KF

[mantllbox]

I'm trying to undervolt my 13700kf with throttlestop, but i notice very strange behavior of "CPU Core - Offset", its value jumps randomly.
Here i set CPU Core offset to -56.6 mv and P Cache/E Cache to -55.7mV. however you can see the all applied offset voltage are -0.0557 on the top right.
But the offset value is adjustable. as the following two screenshots show. actually, -55.7/54.6/56.6mv are all settings i applied few seconds ago, but now I change the offset value to -56.6, and the offset value starts jumping randomly between my settings. reboot don't fix the problem as well. I cleared all settings, set the offset to -54.7, save and reboot, after startup it starts jumping between 0 and -55.
Setting voltage offset with XTU does not face the problem, but i wonder why throttlestop fails.

 

[unclewebb]

Setting voltage offset with XTU does not face the problem

Intel CPUs have a single voltage control register. Reading and writing each individual voltage goes through this one register. If the ThrottleStop FIVR monitoring table is not showing consistent results then you likely have other programs running on your computer that are accessing the voltage control register. Is Intel XTU running in the background when you are using ThrottleStop? That could be a problem.

Try exiting Intel XTU including all of the various tasks it runs in the background. Also exit any other manufacturer's control software that is running on your computer and any other monitoring programs that are accessing the voltage control register.

Most users get consistent results when only using ThrottleStop. If you are still having problems then you will have to stick to using Intel XTU.

 

[mantllbox]

Intel CPUs have a single voltage control register. Reading and writing each individual voltage goes through this one register. If the ThrottleStop FIVR monitoring table is not showing consistent results then you likely have other programs running on your computer that are accessing the voltage control register. Is Intel XTU running in the background when you are using ThrottleStop? That could be a problem.

Try exiting Intel XTU including all of the various tasks it runs in the background. Also exit any other manufacturer's control software that is running on your computer and any other monitoring programs that are accessing the voltage control register.

Most users get consistent results when only using ThrottleStop. If you are still having problems then you will have to stick to using Intel XTU.

Thanks for the advice. I uninstalled XTU (found a background service), and exited other hardware related programs (gpuz, fancontrol, razer synapse and asus armoury crate on my computer), but the values are still inconsistent. I tried to identify which program is messing up the MSR register by enabling Hyper-V. In the event viewer, the folder "Hyper-V Hypervisor" logs illegal access to MSR registers, but I only got ThrottleStop.sys after reboot (the top 3 entries are all related to throttlestop). Then I reboot with identical startup settings except VBS disabled, but the value is still floating randomly. I checked earlier event logs of Hyper-V (date 18 Jul and earlier) but don't get any hint.
XTU can't apply preset automatically after reboot on my computer, so I still wish to find a way to use TS. I wonder if there's any other way to locate the problem

 

[unclewebb]

If you run ThrottleStop with VBS enabled, it is a good idea to exit ThrottleStop, delete the ThrottleStop.INI configuration file and reboot before running ThrottleStop again. I have seen situations where the ThrottleStop.INI file can become corrupted when running ThrottleStop with VBS enabled. I have never looked into this problem further to try and find out why this happens. Deleting the ThrottleStop.INI file was the easiest fix.

I do not know how to find out what program or driver might be writing to the CPU voltage control register. You had a lot of different programs running on your computer that could access this register. I know Intel XTU can leave other tasks running in the background even after you exit XTU. I have no experience with any Razer software or Asus Armoury Crate. Double check to see if anything related to them is running in the background.

How often does the FIVR monitoring table show that the CPU Core is getting reset to 0.0000? Is there any consistency like exactly every 5 or 10 seconds? How long does ThrottleStop show 0.0000? Does it usually only last for 1 second?

After a million plus downloads of TS 9.6, only a few people have ever reported a similar problem. They have always been able to find some other program running on their computer that was responsible for this.

It is possible that this could be some obscure bug in ThrottleStop. I have never had this issue on my computer so I cannot troubleshoot a problem that I cannot reproduce. During any testing, the requested offset voltage entered into ThrottleStop is always reported exactly the same in the monitoring table. The CPU Core offset voltage value never changes no matter how long I stare at the data.

Let me know if you ever find something that is causing this.