f86a90f1-04cf-47e7-a053-87c4c9fb2891

Windows Power Plan Manager

by BIOS

Simple Power Plan Manager

Windows power plans control how your PC balances performance, power draw, heat, and battery life, and a good Windows Power Plan Manager makes them easy to handle without old Control Panel pages or powercfg commands. Managing them the manual way is slow and easy to get wrong. Simple Power Plan Manager is a small, native Windows app that puts every common power plan action in one clean window.

In this guide, we walk through the whole app: viewing installed plans, switching the active plan, importing and exporting .pow files, renaming and duplicating plans, deleting them safely, and restoring missing Windows defaults.

The goal is simple: make the everyday power plan workflow faster and clearer, without forcing you to memorize commands or dig through nested Windows menus.

Important: Simple Power Plan Manager only changes the plans you tell it to. It never silently alters your hardware settings. Every switch, export, rename, and delete is an action you click.

Backup note: Before making bigger changes, use Export All to save every plan as a .pow backup. A backup is your one-click route back to a known-good setup, especially before deleting plans or restoring defaults.

What Is a Windows Power Plan?

A power plan is a saved collection of hardware and system settings, such as display and sleep timeouts, processor power states, USB behavior, and PCIe power management. Windows uses the active plan to decide how aggressively your PC chases performance versus how much it tries to save power.

Many people keep several plans: a balanced profile for everyday use, a high performance profile for gaming or heavy work, and a low-power profile for quiet operation or battery life. The plans themselves are useful. The friction is in managing them, and that is exactly what a dedicated Windows Power Plan Manager removes.

Reminder: After a Windows reset, driver update, or on trimmed-down systems, default plans like High performance or Ultimate Performance can be missing entirely. Simple Power Plan Manager can bring them back.

You can also download our optimized AMD and INTEL power plans from here.

Power Plan Terminology

Power Plan

A saved bundle of power and performance settings that Windows applies as a single profile. Switching plans changes how your hardware behaves without touching each setting individually.

Active Plan

The plan currently in effect. In the app it is clearly tagged ACTIVE in green, so you always know which profile Windows is running.

GUID

The unique identifier Windows assigns to every power plan. The app shows the GUID of the selected plan, which is useful when scripting or matching plans across machines.

.pow File

The standard Windows export format for a single power plan. Export creates one; import loads it back in. It is ideal for backups or sharing a tuned profile with another PC.

Default Plans

The built-in Windows plans: Balanced, High performance, Power saver, and Ultimate Performance. Some are hidden or absent on certain systems until they are restored.

Duplicate

A copy of an existing plan with a new GUID. Duplicating before tweaking lets you experiment freely while the original profile stays untouched.

Description

A short note attached to a plan. Clear names and descriptions make a long plan list easy to understand at a glance.

Important: The GUID is how Windows truly identifies a plan, not the name. Two plans can share a friendly name but always have different GUIDs. When in doubt, check the GUID shown in the details panel.

Getting the Windows Power Plan Manager App

Download the app from GitHub, here

First Launch

Open the app. The window is split in two: a list of installed plans on the left, and a details panel on the right that shows the selected plan’s name, GUID, description, and available actions. The active plan is tagged ACTIVE in green.

Windows Power Plan Manager main window showing installed plans and the details panel

If you ever change plans outside the app, press Refresh to reload the list from Windows.

Viewing and Activating Plans

Every installed plan is listed the moment the app opens. Click a plan to select it, then look at the right panel for its details and actions.

To switch the active plan, select it and press Activate. There is no Control Panel round-trip. This is the fastest way to hop between a daily, a performance, and a quiet profile.

The actions available for a selected plan are Activate, Duplicate, Activate & Edit, Export, and Delete. The active plan cannot be deleted, which prevents you from removing the profile your system is currently using.

Importing and Exporting .pow Files

Windows plans can be saved as .pow files. Use Import to load one or more tuned profiles straight into Windows, and the Export options to back them up. This is perfect before a reinstall or for sharing a profile.

To import, press Import and select one or more .pow files in the native Windows picker.

To back up everything at once, press Export All and choose a folder. The app writes every installed plan into that folder as a separate .pow file.

Exporting power plans as .pow backup files in the Windows Power Plan Manager

To save just one plan, select it and press Export Selected. The app suggests a sensible file name based on the plan name.

Backup note: Run Export All before any bigger change. If something goes wrong, a quick Import restores your plans exactly as they were.

Renaming, Describing, and Duplicating

Give plans clear names and descriptions so each profile explains what it is tuned for. Select a plan, edit the name and description fields, then press Save to write the changes back to Windows.

Before experimenting with a plan, press Duplicate first. Copying a plan creates a new GUID, so you can tweak the copy freely while the original stays exactly as it was.

Deleting Plans Safely

Plans you no longer need can be removed with Delete, but never by accident. A confirmation dialog names the plan and warns that it will be removed from Windows before anything happens.

Delete confirmation dialog in the Windows Power Plan Manager
Important: You cannot delete the active plan. Activate a different plan first, then delete the one you no longer want. Deleting a plan is permanent, so keep a .pow backup if you might need it again.

Restoring Missing Windows Defaults

If Windows is missing its built-in plans, press Enable Windows Defaults to bring them back. This covers Balanced, High performance, Power saver, and Ultimate Performance. It is handy on fresh installs and trimmed-down systems where some of these are hidden or absent.

Reminder: Export All first. Restoring defaults is a larger operation, so a fresh backup means you can always return to your previous setup if you change your mind.

Recommended Workflow

A safe routine for getting a tidy, tuned setup without risking your current configuration:

  1. Open the app and confirm which plan is currently active.
  2. Press Export All to back up every plan before making changes.
  3. Duplicate a plan if you want to experiment, so the original stays safe.
  4. Rename the copy and add a description so it is easy to identify later.
  5. Activate the plan you want to use.
  6. Use Activate & Edit only when you need Windows’ advanced settings.
  7. Delete leftover test plans you no longer need.

Action Reference

A quick map of every control in the app and what it does:

Action What It Does
Refresh Reloads the plan list from Windows.
Activate Sets the selected plan as the active Windows plan.
Duplicate Creates a copy of a plan, with a new GUID, for safe editing.
Import Loads one or more .pow power plan files into Windows.
Export Selected / All Saves the selected plan, or every plan, as .pow backup files.
Rename / Description Updates the friendly name and description of a plan.
Enable Windows Defaults Restores missing built-in Windows power plans.
Activate & Edit Activates the plan and opens Windows’ advanced power settings.
Delete Removes a plan from Windows after a confirmation prompt.

The Process

The basic workflow for keeping a clean, reliable set of power plans is:

  1. Back up everything with Export All.
  2. Restore any missing defaults you actually use.
  3. Duplicate before tweaking, and rename copies clearly.
  4. Activate the plan you want as your daily profile.
  5. Delete leftover test plans, keeping a .pow backup of anything you might want again.

TL;DR: Export All for safety, Activate to switch in one click, Import to load tuned profiles, Duplicate before experimenting, Enable Windows Defaults to recover missing plans, and Delete what you do not need.

Important: A dedicated Windows Power Plan Manager makes your power plans easier to manage, but it does not replace tuning the rest of your system. For real, end-to-end responsiveness you also want a stable CPU, memory, and BIOS setup.

For CPU-side overclocking and stability testing, read our AM5 Infinity Fabric – FCLK overclocking and stability testing guide, book a BIOS consult and let us do the work for you or join the discord!

9800x3d

AM5 Infinity Fabric – FCLK overclocking and stability testing.

by BIOS

AM5 FCLK Overclocking Guide: Tuning, Stress Testing, and Stability Validation

In this AM5 FCLK overclocking guide, we will cover how to tune Fabric Clock, stress-test it with Linpack and y-cruncher, and validate stability on an AM5 Ryzen system.

FCLK Overclocking Basics for AM5

FCLK, or Fabric Clock, is the clock frequency of AMD’s Infinity Fabric interconnect.

On AM5 DDR5 systems, FCLK is usually tuned independently.

FCLK frequency depends on both silicon quality and BIOS/AGESA version. During the early Ryzen 7 9850X3D release window, our chip would instantly crash at 2100 MHz FCLK. With later BIOS/AGESA versions, 2200 MHz became stable on the same chip.

An unstable Curve Optimizer configuration or excessive boost-clock offset can mimic FCLK instability — creating high variation during Linpack and even number variation during y-cruncher VT3.

Before tuning FCLK, make sure your system is running from a known-stable baseline. Your RAM timings, PBO, boost-offset, and Curve Optimizer settings should already be stable. If they aren’t, fix them first, otherwise, Linpack or y-cruncher variation can be caused by something other than FCLK.

Important: Disable your iGPU before proceeding.

FCLK overclocking BIOS iGPU setting on AM5

Reminder: If your PBO settings or RAM timings are not fully stable, your FCLK tuning results will not be reliable.

If your motherboard allows it, set CPU and VDDCR_SOC/VSOC power and duty control to Extreme for additional stability under load. A higher load-line calibration setting may also help, but this should be determined during your PBO tuning phase.

FCLK overclocking BIOS power and duty control settings

Voltage Terminology

Before tuning, it’s important to understand the voltage rails involved. BIOS names vary by motherboard vendor, but the terms below match the common AM5/Ryzen terminology used for memory and fabric tuning.

VDDCR_SOC / VSOC

Powers SoC logic, including the DDR5 memory controller and other IOD/SoC IP blocks. Important for RAM and UCLK stability. Do not treat VSOC as the dedicated fabric voltage.

CLDO VDDP / VDDP

The DDR5 bus-signaling / DRAM PHY supply. Affects memory training, boot behavior, and RAM stability.

CLDO VDDG IOD & CCD

Fabric/data-path signaling voltages for the IOD↔CCD Infinity Fabric/GMI links. The primary tools for stabilizing higher FCLK frequencies. These are separate rails and may prefer different values depending on the CPU.

VDDCR_MISC / VDD Misc

A supply rail and the source rail for the internally regulated VDDG fabric voltages. Changing VDD Misc does not automatically change CLDO VDDG CCD/IOD — set and verify VDDG separately.

For FCLK overclocking specifically, the key rails are usually CLDO VDDG IOD and CLDO VDDG CCD, while VSOC should be treated mainly as the voltage needed for your RAM and UCLK target.

FCLK Overclocking and VSOC Behavior

High FCLK can be sensitive to VSOC, but higher VSOC does not universally improve FCLK headroom.

Treat VSOC primarily as the voltage needed for your RAM and UCLK target, and use the lowest stable value — excessive VSOC can hurt FCLK stability. For fabric-specific tuning, focus on CLDO VDDG CCD/IOD.

VSOC requirements are silicon-dependent. On our Ryzen 7 9850X3D, we needed 1.25 V VSOC to run UCLK 3200 MHz.

Before continuing: Find the baseline VSOC voltage that works with your RAM and UCLK target first.

BCLK and Spread Spectrum

Head into the BIOS and find BCLK or CPU Clock Control, then set it to 100.000 MHz. This is a picture from a Gigabyte board:

Gigabyte BIOS CPU Clock Control set to 100 MHz

And here’s the same setting on an ASUS board:

ASUS BIOS CPU Clock Control set to 100 MHz

Then look for Spread Spectrum and disable it.

BIOS Spread Spectrum option set to disabled

Starting Voltages for FCLK Overclocking

Set VSOC according to your own silicon and memory-controller requirements. Around 1.20 V is a reasonable starting target for many AM5 CPUs, but our sample uses 1.25 V.

Suggested starting values:

  • VSOC: Your known-good RAM/UCLK value
  • VDDP: 1.00 V
  • VDD Misc: 1.10 V
  • VDDG CCD: 0.95 V
  • VDDG IOD: 0.95 V
FCLK overclocking BIOS voltage settings for VDDG and VSOC

The key voltages here are VDDG CCD and VDDG IOD.

On some boards and AGESA versions, Auto rules may make Ryzen Master or HWiNFO report CLDO VDDG CCD/IOD around 1.050 V (1050 mV). Treat this as board/BIOS-dependent behavior, not a universal AMD default.

Some chips may prefer lower IOD voltage. In our FPSHEAVEN consultations, several Ryzen 7 9800X3D systems showed lower Linpack deviation at 970 mV than at 1050 mV, while both settings still passed within accepted deviation. If your system can run lower voltages while remaining stable, that is ideal.

FCLK Overclocking Target

Your goal is to reach 2100 MHz FCLK or higher. 2100 MHz as the first meaningful manual test point.

Recommendation: If you can’t stabilize 2100 MHz after proper testing, do not settle for 2033 MHz or 2067 MHz. Return to 2000 MHz, stop FCLK tuning, and move on to PBO and memory-timing optimization.

For this workflow, use the same test settings after every BIOS change so the results remain comparable.

Required Tools

Download the following tools and place them in a single folder on your desktop.

Required dependency: Install the latest Visual C++ Redistributable Runtime package before running y-cruncher.

Initial BIOS Setup

Enter the BIOS, set FCLK to 2100 MHz, save, exit, and boot into Windows.

Linpack and y-cruncher results can be affected by Windows background processes and other applications, so we’ll run our testing in Safe Mode.

Booting Into Safe Mode

  1. Open msconfig.
Opening msconfig in Windows for FCLK overclocking Safe Mode testing
  1. Go to the Boot tab.
  2. Select Safe boot.
  3. Click Apply, then OK.
Safe boot option in msconfig

Your PC will now restart into Safe Mode.

Important: When testing is finished, return to msconfig and uncheck Safe boot. Otherwise, Windows will keep booting into Safe Mode.

Linpack Xtreme Configuration

Once you’re in Safe Mode, open Linpack Xtreme and configure it as shown below.

Step 1 — Enter 2:

Linpack Xtreme configuration step 1

Step 2 — Enter 5:

Linpack Xtreme configuration step 2

Step 3 — Enter 40:

Linpack Xtreme loop configuration

Step 4 — Answer the remaining prompts:

  • Y
  • Y
  • N
  • N — press N when you see the warning
Linpack Xtreme warning prompt

Linpack is now configured to run 40 loops using 10 GB of RAM. You can select 30 loops if you wish to wait less time.

Reading Linpack Results

Each Linpack result has one important value: GFLOPs.

The image below shows a 40-loop, 10 GB result from our Ryzen 7 9850X3D using 950 mV for both VDDG CCD and VDDG IOD.

Stable Linpack Xtreme result during FCLK overclocking

During FCLK overclocking, Linpack consistency is useful because large GFLOPs swings expose instability quickly. Focus on the difference between the GFLOPs values from each run.

Our standard is strict: we allow a maximum difference of roughly 1.0 to 1.2 GFLOPs at best. Some users may accept variation around 2 GFLOPs, but we prefer tighter consistency.

At the bottom of the result you’ll also see the average and maximum values. These should be as close together as possible but the most important thing is the per-run variation.

This an image from our customer using a 7800X3D. The consistency of the results are excellent.

Example of Unstable Behavior

The altered image below shows what unstable or FCLK-related behavior may look like during Linpack testing.

Example of unstable Linpack result during FCLK overclocking

In this example, some runs show values such as 363, 377, and 375 GFLOPs while others are around 482 GFLOPs. This result is not stable.

At this point, go back into the BIOS and raise VDDG IOD from 950 mV to 1000 mV. We recommend starting with a 50 mV bump to save time during initial testing — once stability is found, you can lower the voltage in 10 mV steps to find the minimum stable value.

Guide limit: In this tuning procedure, keep CLDO VDDG CCD/IOD at or below 1050 mV.

FCLK Tuning Loop

After changing voltage, return to Safe Mode and run the same Linpack test again. When the test is complete, check the GFLOPs variation:

  • Is the variation above 2 GFLOPs?
  • Is the spread larger than your acceptable limit?
  • Are some runs clearly much lower than the rest?

If the variation is still too high, continue tuning:

  1. Raise VDDG IOD until you reach 1050 mV.
  2. If variation is still too high, begin raising VDDG CCD by 10–20 mV.
  3. Retest after every change.
  4. Do not exceed 1050 mV on either VDDG CCD or VDDG IOD.

If you still can’t achieve consistent Linpack results, set FCLK back to 2000 MHz, stop FCLK tuning, and continue with PBO and memory timing optimization.

Further Validation

After Linpack testing, ou can further validate your AM5 FCLK overclocking stability with y-cruncher and FurMark. We’ll start with y-cruncher and observe the variance between each run.

y-cruncher VT3 Setup in Safe Mode

  1. Open the folder you created on your desktop.
  2. Right-click y-cruncher and create a shortcut.
  3. Right-click the shortcut and open Properties.
  4. Find the Target field.
y-cruncher shortcut properties

At the end of the Target field, append the following command:

stress -TL:3600 VST VT3 -M:28g

The final target should look similar to this:

"C:\Path\To\y-cruncher.exe" stress -TL:3600 VST VT3 -M:28g

This starts y-cruncher for 3600 seconds (one hour) using the VT3 test and 28 GB of RAM. You can adjust the memory amount if needed. Double-click the shortcut to start y-cruncher.

y-cruncher VT3 running during FCLK overclocking validation

The image above shows our Ryzen 7 9850X3D running VT3.

Reading y-cruncher VT3 Results

During VT3, focus on the first speed value shown in each result line.

y-cruncher VT3 speed variation

We consider a variation of roughly 0.03 to 0.06 acceptable. In our example, the test started around 1.04 and later stabilized around 1.07 — a difference of about 0.03, which is very acceptable.

In Safe Mode, we don’t focus too heavily on y-cruncher speed variation. The main goal is to check whether the test crashes, shows abnormal number variation, or produces WHEA hardware-error events.

A crash may look like this:

Example of y-cruncher crash

You can stress-test with y-cruncher for longer if needed, but one hour is enough for an early stability check. We suggest a minimum of 70 iterations.

Final Confirmation: y-cruncher + FurMark

After passing the Safe Mode checks, leave Safe Mode and boot back into normal Windows. This final AM5 FCLK overclocking test combines CPU, memory fabric, and GPU load to expose instability that may not appear during isolated testing.

  1. Boot back into normal Windows.
  2. Download and install HWiNFO.
  3. Open HWiNFO and press Start.
  4. Open FurMark and copy the settings shown below.

We use a 1080p monitor, so we keep the FurMark resolution set to 1080p. Start the FurMark test, then minimize it.

FurMark stress test settings

Now find your y-cruncher shortcut and run it again. Arrange HWiNFO, FurMark, and y-cruncher on screen so you can monitor all three at the same time.

In HWiNFO, scroll all the way down and look for WHEA Errors. Monitor the WHEA hardware-error counters during the test.

HWiNFO WHEA error monitoring during FCLK overclocking validation

The final FCLK overclocking check should include normal Windows testing, GPU load, and WHEA monitoring. The duration is up to you — FCLK instability often shows up quickly, so even one hour of stress testing can provide useful clues.

Important: Passing every synthetic test does not guarantee perfect real-world stability. FCLK can still be unstable during gameplay.

Use this guide as a repeatable validation process — not a guarantee that every AM5 CPU will reach the same frequency.

Alternative: OCCT Instead of FurMark

You can also use OCCT instead of Furmark to put load into your GPU and FCLK.

  1. Download OCCT from here and open the application.
  2. Go to settings and then enable Stop on error and Stop on WHEA error.
OCCT settings with Stop on error and Stop on WHEA error enabled
  1. Click on Stability Test and select Combined with 3D Adaptive and VRAM.
  2. Copy the settings below and start the test.
OCCT Combined stability test settings

Wait 10 seconds and then as soon as the test starts, launch y-cruncher.

TL;DR

The short version of this AM5 FCLK overclocking guide:

  1. Make sure your PBO and RAM tune are rock stable. If unsure, revert to defaults and tune them later.
  2. Disable the iGPU.
  3. Set VDDP to 1.00 V, MISC to 1.1 V and VDDG CCD & IOD to 950 mV.
  4. Boot into Safe Mode and observe Linpack variation. We aim for 1.0–1.5 GFLOPs max.
  5. If unstable or variation is too high, raise VDDG IOD by 10 mV and retest. If you hit 1050 mV and it’s still unstable, start raising VDDG CCD.
  6. Stable in Linpack? Run y-cruncher VT3 for further validation — or, if you’re lazy, boot back into Windows and run y-cruncher + FurMark (or OCCT GPU+VRAM) while watching WHEA errors in HWiNFO.
  7. Rinse and repeat until you’ve found your stable FCLK ceiling.