Gigabite auros 17X laptop (2024) undervolting

[geoff79]

Hi great forum and pages you guys have here lots of info and good reading for the uneducated like myself. So after looking through lots of the throttle stop posts and seeing one saying that my model of laptop couldnt be undervolted cause the voltage setting were locked i looked through the advanced bios and found overclocking and undervolting options and enabled them and found that i can now adjust voltages in throttle stop. Although one or two things seem to still be locked like the PL4 and one of the voltage sliders so my question is should i still go ahead with undervolting with what i can adjust or is it not possible / worth it ? Or are there other options in the bios i should look to for unlocking or disabling.

Im no expert but have undervolted and overclocked my desktop to bring temps down and increase preformance but did all that through the bios so am very keen to give throttle stop a go for my laptop. Ive attached pics of throttle stop and the menus in my bios that ive changed.

The laptop is currently running fine with no real issues gets a bit of thermal throttling while gameing which drops fps and stutters a little bit at times but locking fps down to a stable amount nearly eliminates this but if i can run at full preformance using throttle stop id much rather run the laptop that way....thanks in advance for any info or guidance cheers

Laptop specs also in attached photos

 

[unclewebb]

It looks like you originally tried to run ThrottleStop when virtualization (VBS) was enabled. This can corrupt the ThrottleStop.INI configuration file. It would be best to exit ThrottleStop, delete the ThrottleStop.INI configuration file and then do a full reboot so the CPU can reset itself. Holding down the Shift key when selecting Restart or powering down your computer should reset the CPU.

After you start back up, run ThrottleStop and post an updated screenshot of the FIVR window. In the FIVR window you should not be seeing a column of weird looking values in the Voltage column, the VCCIN slider should be disabled and IccMax for the core and the cache should be a lot higher than what it is showing now.

Gigabyte might have decided to lock Power Limit 4. They like doing stuff like that to their laptops to keep them safe. Hopefully it does not get in the way of maximum performance.

If you need to run things like WSL2, you will not be able to use ThrottleStop to access the voltage control register.

 

[geoff79]

It looks like you originally tried to run ThrottleStop when virtualization (VBS) was enabled. This can corrupt the ThrottleStop.INI configuration file. It would be best to exit ThrottleStop, delete the ThrottleStop.INI configuration file and then do a full reboot so the CPU can reset itself. Holding down the Shift key when selecting Restart or powering down your computer should reset the CPU.

After you start back up, run ThrottleStop and post an updated screenshot of the FIVR window. In the FIVR window you should not be seeing a column of weird looking values in the Voltage column, the VCCIN slider should be disabled and IccMax for the core and the cache should be a lot higher than what it is showing now.

Gigabyte might have decided to lock Power Limit 4. They like doing stuff like that to their laptops to keep them safe. Hopefully it does not get in the way of maximum performance.

If you need to run things like WSL2, you will not be able to use ThrottleStop to access the voltage control register.

Thanks mate ill give all that a try when i finish work and post up the pics....i just downloaded throttle stop and started messing around with it didnt know there was rhings needing to be turned off before downloading it and only thing i had previously done was put put a voltage cap of 1400 to stop the high vid requests

It looks like you originally tried to run ThrottleStop when virtualization (VBS) was enabled. This can corrupt the ThrottleStop.INI configuration file. It would be best to exit ThrottleStop, delete the ThrottleStop.INI configuration file and then do a full reboot so the CPU can reset itself. Holding down the Shift key when selecting Restart or powering down your computer should reset the CPU.

After you start back up, run ThrottleStop and post an updated screenshot of the FIVR window. In the FIVR window you should not be seeing a column of weird looking values in the Voltage column, the VCCIN slider should be disabled and IccMax for the core and the cache should be a lot higher than what it is showing now.

Gigabyte might have decided to lock Power Limit 4. They like doing stuff like that to their laptops to keep them safe. Hopefully it does not get in the way of maximum performance.

If you need to run things like WSL2, you will not be able to use ThrottleStop to access the voltage control register.

 

[geoff79]

After deleting the INI file this is what i ended up with looks pretty much the same to me

 

[unclewebb]

Did you disable Windows core isolation memory integrity? It looks like Windows virtualization based security is still enabled. You can run msinfo to double check the virtualization status.

Follow the links in my signature to learn how to disable VBS so you can run ThrottleStop.

 

[geoff79]

Did you disable Windows core isolation memory integrity? It looks like Windows virtualization based security is still enabled. You can run msinfo to double check the virtualization status.

Follow the links in my signature to learn how to disable VBS so you can run ThrottleStop.

Thanks mate ill give it a good read and post screen shots when i go through it again