Locked Undervolting AcerNitro 5 (an515-55- 73hh)

BulletInMyHead

Hello, 
I a trying to undervolt my CPU ( i7- 10750h ) with ThrottleStop and my FIVR section is greyed out with "Locked"  for a tag. I read somewhere that this means my CPU has disabled voltage control. If this is true, is there a way to enable it from the BIOS or anywhere at all. I am using Windows 10 Pro. I don't know if it is a BIOS problem or a windows register.

Thank you in advance for the help!

Leostat

its not possible to re-enable it on the 10th gen chips its been turned off by intel to mitigate a vulnerability i belive

unclewebb

Leostat said:

its not possible to re-enable it on the 10th gen chips

MSI laptops have an option in the BIOS that unlocks CPU voltage control on the 10th Gen CPUs. In other words, it is possible. Acer needs to look into adding this valuable feature or users will shop elsewhere.

Leostat

You could also argue that MSI dont care about a vuln ( https://plundervolt.com/ ) so its users should shop elsewhere? (Im not saying they should, buy the thing that makes you happy, its not that MSI dont care, its that they have deemed it better to leave the option rather than remove it which is their choice ). 

There is a good Jarod Video on this where you can compare how well it works : youtube.com/watch?v=4nlJkZ5PHZU . It does perform a bit cooler, and XMG have highlighted in the past that its not all bad news as a factory fixed undervolt is sometimes used, and the .1v undervolt isnt stable on the 10th gen chips anyway.

Its not as easy as turning features on or off. As it was rolled out mid cpu cycle some devices are able to undervolt with older UEFI versions, but then you miss out on the fixes later versions have (like the dell XPS), and other vendors never had it and instead have an adanced "secret" menu in the UEFI

BulletInMyHead

So basically I am screwed until intel drops undervolting update for 10th gen CPU-s (and that is IF they do it), at least on the current machine.

Leostat

Afraid so, and the issue is with the hardware within the CPU so its unlikly to be re-enabled. Kind of like when spectre/meltdown happened it had to wait for a revision to the CPU to fix without other issues