• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.

throttlestop dead on windows 11

jhigh2000

New Member
Joined
Oct 16, 2021
Messages
11 (0.20/day)
I did change something, maybe that works for your particular case. Could you try this EFI with the same Loader please? -90mV CPU + -40mV iGPU there.

I'm so sorry that I cannot create a tutorial for building + deploying these EFI files. I have a busy week :/
No need to apologize at all! I really appreciate the builds that you have created. Unfortunately gEnableSaferAsm = 0 did not help, still freezing hard on programming. I'm wondering if there's another EFI shell that I should use for testing. I doubt it will make a difference, but it would be worth a try. Any suggestions?
 

validate

New Member
Joined
Sep 19, 2021
Messages
21 (0.26/day)
No need to apologize at all! I really appreciate the builds that you have created. Unfortunately gEnableSaferAsm = 0 did not help, still freezing hard on programming. I'm wondering if there's another EFI shell that I should use for testing. I doubt it will make a difference, but it would be worth a try. Any suggestions?
PowerMonkey should work if you put on a external USB by creating EFI folder, then creating BOOT folder in EFI folder, finally changing the name of PowerMonkey.efi to bootx64.efi, putting the BOOT folder that .efi and selecting the USB at boot menu on restart. If it doesn’t work, I don’t think that’s the issue with loader. Maybe your PC (BIOS) has some extra protections over these values, I don’t really know.
 

Sherpard2

New Member
Joined
Oct 25, 2021
Messages
3 (0.07/day)
I really hope Microsoft adds an exception/method to add an exception to VBS, in order to let a Power User do whatever they want with their device (Under their responsibility of course).

If they do not add such support, my current laptop won't be upgrading to Win11 anytime soon.
 

charlyo

New Member
Joined
Nov 7, 2021
Messages
1 (0.03/day)
Does anyone know if throttle stop still works in the release preview of windows 10 21h2??

Also tried powermonkey in my xps and works.
 

uri_by

New Member
Joined
Nov 21, 2021
Messages
2 (0.11/day)
I am trying to use PowerMonkey on my XPS, but nothing happens after PowerMonkey's boot screen. I built my EFI with -5mV or even 0mV but still freezing hard on programming. The same as jhigh2000 described.
 

obrobrio2000

New Member
Joined
Nov 22, 2021
Messages
2 (0.12/day)
I am trying to use PowerMonkey on my XPS, but nothing happens after PowerMonkey's boot screen. I built my EFI with -5mV or even 0mV but still freezing hard on programming. The same as jhigh2000 described.
Would you mind explaining which method you followed to build PowerMonkey? Last time I tried with VisualUEFI (VisualStudio method) I couldn't build it because of error "Cannot open input file BaseIoLibIntrinsic.lib".
 
Last edited:

netlan

New Member
Joined
Nov 23, 2021
Messages
2 (0.13/day)
Would you mind explaining which method you followed
VisualUEFI doesn't work for me, I got the same error about "Cannot open....". So, I used the 'long way' (EDK2 route). Just it's needed to follow several instructions and install some additional tools (Python, ASL, and nasm) besides Visual Studio Build Tools. Have a look please:
Also, some changes in EDK configs are required depending on your environment, OS, etc.
When all be done, run edksetup.bat Rebuild -> edksetup -> build in the ed2 directory.

Regarding freezes.
Keep in mind please the difference in CPUs. You need to check all settings in the PowerMonkey config. For example, pk->ForcedRatioForAllCoreCounts = 51; For me, it works with 51, but it looks potentially strong (as many other options). So, I used pk->ForcedRatioForAllCoreCounts = 0.

xps 9500 gives the great ability to set up own UEFI loader entry in the BIOS. I just placed PowerMonkey.efi next to bootx64.efi
 

uri_by

New Member
Joined
Nov 21, 2021
Messages
2 (0.11/day)
VisualUEFI build is relatively easy to fix. You have to create new projects for a couple of missing libraries using already existing projects as an example.

My CPU is i9-9980HK on xps 7590. I was aware of pk->ForcedRatioForAllCoreCounts = 51. I set it to 41 as a safer value.

I tried different ways to set up UEFI loader with or without EfiGuard. So, I don't think it is problem with the loader.
 

jhigh2000

New Member
Joined
Oct 16, 2021
Messages
11 (0.20/day)
VisualUEFI build is relatively easy to fix. You have to create new projects for a couple of missing libraries using already existing projects as an example.

My CPU is i9-9980HK on xps 7590. I was aware of pk->ForcedRatioForAllCoreCounts = 51. I set it to 41 as a safer value.

I tried different ways to set up UEFI loader with or without EfiGuard. So, I don't think it is problem with the loader.
We have the same system! No luck for me with any settings. Still freezing while programming.
 

obrobrio2000

New Member
Joined
Nov 22, 2021
Messages
2 (0.12/day)
VisualUEFI doesn't work for me, I got the same error about "Cannot open....". So, I used the 'long way' (EDK2 route). Just it's needed to follow several instructions and install some additional tools (Python, ASL, and nasm) besides Visual Studio Build Tools. Have a look please:
Also, some changes in EDK configs are required depending on your environment, OS, etc.
When all be done, run edksetup.bat Rebuild -> edksetup -> build in the ed2 directory.

Regarding freezes.
Keep in mind please the difference in CPUs. You need to check all settings in the PowerMonkey config. For example, pk->ForcedRatioForAllCoreCounts = 51; For me, it works with 51, but it looks potentially strong (as many other options). So, I used pk->ForcedRatioForAllCoreCounts = 0.

xps 9500 gives the great ability to set up own UEFI loader entry in the BIOS. I just placed PowerMonkey.efi next to bootx64.efi
First of all thank you very much!! I managed to build it and it works both with SaferAsm on and off (I'll keep it on). I tested it by putting EFI/Boot/PowerMonkey.efi on a USB stick. However, my Lenovo Yoga C940-14 doesn't give the same ability as your Dell XPS, so I can't make it start before Windows (?).
I just placed PowerMonkey.efi next to bootx64.efi
I'm still learning so sorry if I sound dumb, but with this do you mean mounting the EFI partition (mountvol X: \s) and placing PowerMonkey.efi near bootx64.efi (in EFI \ Boot)? Because I did but I think I understood wrong since PowerMonkey doesn't load. If you didn't mean that, do you think the only way to make PowerMonkey load before Windows is to use GRUB?

Thanks again for the help you gave me and thanks in advance :)

---------- EDIT ----------

After researching I downloaded the Shell.efi from Tianocore edk2 github, then I booted from it, added PowerMonkey to the boot list and made it default/first following the link in this reply.

Sorry guys if I lost myself in such an easy task, I'm still new to this :)

I'm happy that I can start undervolting again, I couldn't hold this 95°C nuclear central anymore.
Noted for when I'll need to purchase another laptop: never buy a laptop just because of the good-sounding speaker system it has.
 
Last edited:

netlan

New Member
Joined
Nov 23, 2021
Messages
2 (0.13/day)
so I can't make it start before Windows (?)
I think, you need the same option:
But, again, you have to be very careful and read enough for clear view.
 

jhigh2000

New Member
Joined
Oct 16, 2021
Messages
11 (0.20/day)
I was able to successfully boot and run PowerMonkey.efi an a slightly order laptop running Windows 11. Now that Throttlestop is crippled by Windows 11, what's the best way now to verify in Windows that the undervolt is actually being applied?
 
Top