Jump to content

@biruk

Your screenshot shows that Windows Virtualization Based Security (VBS) is enabled. ThrottleStop needs full access to the CPU voltage control register. This is not possible when VBS is enabled. 

 

Disable Windows core isolation memory integrity, exit ThrottleStop and delete the ThrottleStop.INI configuration file and then reboot. Post an updated FIVR screenshot if you are still having problems. When the FIVR monitoring table Voltage column shows a bunch of odd looking values (0.3799), that is a good sign that something VBS related is still enabled. 

 

https://beebom.com/how-disable-virtualization-based-security-vbs-windows-11/

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×