Skip to content

Instantly share code, notes, and snippets.

Show Gist options
  • Save Arie/af8e353dec6ce6b47359529571ace45f to your computer and use it in GitHub Desktop.
Save Arie/af8e353dec6ce6b47359529571ace45f to your computer and use it in GitHub Desktop.
Re: How to get higher pkg C-States on Asrock Z790 motherboards (guide)
https://www.reddit.com/r/ASRock/comments/1998ozl/how_to_get_higher_pkg_cstates_on_asrock/
Notes for Asrock Z790 board:
Prereq:
USB stick that will fit Windows 11 installer (8-ish GB)
Basic DOS skills like "C:" and "cd some-directory".
1.
Get the SCEWIN tool from https://github.com/ab3lkaizen/SCEHUB.
Run the DL_SCEWIN executable from the release. This downloads the SCEWIN_64.exe etc... (aka AMISCE 5.05)
2.
Create a bootable Windows 11 installer:
https://support.microsoft.com/en-us/windows/create-installation-media-for-windows-99a58364-8c02-206f-aa6f-40c3b507420d#ID0EJD=Windows_11
3.
Place the files created by DL_SCEWIN on the USB bootable drive created by the Windows 11 media tool in some easy to find directory on the USB disk.
Reboot
4.
Enter BIOS
Make sure there is no BIOS password set (Neither supervisor or normal) and boot into the Windows 11 installer USB disk
5.
Press Shift+F10 while in the Windows installer to open command prompt.
Find your USB drive, might be C:, D:, E:, w/e depending on amount of your drives
Find the directory you put the files downloaded by DL_SCEWIN
6.
Run `SCEWIN_64.exe /o /s "setup_script_file.txt" /a`
Takes a few seconds, after running this, you should be able to get meaningful output from:
`SCEWIN_64.exe /o /lang "en-US" /ms "Low Power S0 Idle Capability" /hb`
7.
Reboot, enter BIOS and set a supervisor password, keep it simple.
Boot from Windows 11 USB installer again.
Press Shift+F10 again to open a command prompt and find the SCEWIN_64 file again.
8.
`SCEWIN_64.exe /i /lang "en-US" /ms "Low Power S0 Idle Capability" /qv 0x1 /cpwd YOUR-BIOS-ADMIN-PASSWORD`
Done, or set w/e other hidden BIOS setting Asrock didn't want you to touch.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment