Throttlestop Settings Save but with Hyper-V warning event

[Axios Deminence]

I am on Windows 10 Pro version 21H2 (19044.1766) and need to keep hyper-v and other virtualization technologies enabled since I use wsl2. The throttlestop settings save (shown in the first picture) but it will also throw a warning event to Hyper-V Hypervisor - Operational (shown in the second picture). I was wondering if the throttlestop settings are misreporting that they're being saved and what the event warning means. When using other programs to see the voltage information (eg. hwmonitor or hwinfo), they will also report that the voltage offset is properly applied. Thanks for your time.

Overall system details (if there's any other specs that may be relevant, do let me know and I can provide them as necessary):
* Dell G5 5590 (laptop) with a i7-9750H
* Windows 10 Pro version 21H2 (19044.1766)

 

[unclewebb]

The warning message shows that the driver is cpuz152_x64.sys

Are you sure this error message is being caused by ThrottleStop? Looks like a CPU-Z issue.

Your voltages look OK. I assume ThrottleStop is working correctly but I cannot guarantee anything when Hyper-V is enabled. I have done zero Hyper-V testing.

I think ThrottleStop works OK in Windows 10. It does not work properly in Windows 11 if Hyper-V is enabled.

 

[Axios Deminence]

Sorry, it might have been a picture when I had booted up one of my hardware monitoring softwares. This is a picture of the event being caused by Throttlestop. The voltages are still being reporting as being correctly set. Throttlestop also correctly reports the turbo ratio limits.

 

[unclewebb]

MSR 0x1AD and MSR 0x1AE that Windows Hyper-V is complaining about are the two registers that control the turbo ratio limits. If MSR 0x1AD is not a restricted MSR then there is no reason for Microsoft to include MSR 0x1AE on its restricted register list. For Windows 11, Microsoft decided to also add the CPU voltage control register to their restricted list. Luckily ThrottleStop seems to be able to access the voltage register just fine in Windows 10 when Hyper-V is enabled.

For ThrottleStop to support a wide variety of CPUs, it has to read and write to various registers. This is how it determines if a register is available or not. The newer 12th Gen CPUs use MSR 0x1AE as well as some older Xeons. The 9750H does not use this register. Whether ThrottleStop tries to read or write to this register is not really that important.

I will have a look to see if I can avoid trying to access MSR 0x1AE when a 9750H is detected.

If this seems like a major issue then you will have to stop using ThrottleStop. I consider this to be a non issue.

 

[Axios Deminence]

Nope. If it's working for my purposes, then it's ultimately a non-issue. I just remember hearing recently that some people may have had problems with Hyper-V enabled on Windows 10 and led me to investigate if it was working properly. If it's working, then I ain't complaining. Thanks for the help!