GPU presentation and power management in Windows 11 25H2

Short answer

ForceDirectFlip, SmallQuantumMode, EnableRuntimePowerManagement and DisablePStateManagement are confirmed at the level of reading and conditions of application. Their effect on frames and power consumption depends on the GPU, driver and output mode, so there is no universal gain from changing them.

What was checked

We checked whether the graphics subsystem reads these parameters, under what conditions they take effect, and which adapter capability checks limit their application.

Scope of research

Windows 11 25H2 build 26200.9168, dxgkrnl.exe and system power management paths. Some checks were performed in VMware or with the basic display driver, so conclusions about physical GPUs are limited.

Methodology

Static mapping of parameters to code and verification of branches by adapter capabilities; for HAGS and presentation — cross-checking against public Microsoft documentation.

Canonical values

Registry path	Value	Type	Default	Role
HKLM\SYSTEM\CurrentControlSet\Control\GraphicsDrivers	ForceDirectFlip	REG_DWORD	0	direct-flip policy permission
HKLM\SYSTEM\CurrentControlSet\Control\GraphicsDrivers	SmallQuantumMode	REG_DWORD	1	scheduler quantum policy
HKLM\SYSTEM\CurrentControlSet\Control\GraphicsDrivers	EnableRuntimePowerManagement	REG_DWORD	1	runtime D3 power policy
same path	DisablePStateManagement	REG_DWORD	0	GPU P-state policy

Presentation and quantum

ForceDirectFlip allows a suitable surface to be output without the usual full composition. The possibility of such output depends on DWM, the buffer chain (swap chain), the driver and GPU capabilities. The setting does not allow it to be forced for every window.

SmallQuantumMode is read directly from the root of GraphicsDrivers; the GraphicsDrivers\Scheduler plug-in does not use this code. In Windows 11 25H2, the value 0 forcibly disables the short quantum, 2 enables it, and 1 and the remaining values leave the automatic choice based on hardware capabilities. The value 2 means a short, not a long, quantum.

These parameters are worth considering when diagnosing a specific composition or driver problem. ForceDirectFlip does not guarantee DirectFlip: if the capability check fails, the graphics subsystem clears the forced flag. To evaluate a change, a reproducible symptom or an ETW trace is needed; the effect may be absent.

Related BoosterX settings

The research is related to the “Hardware-accelerated GPU scheduling”, “HDCP” settings and power parameters that depend on the GPU manufacturer. Hardware-accelerated GPU scheduling and DirectFlip need to be checked on a specific graphics card and driver. HDCP controls protected content; there is no reason to expect universal game acceleration from it.

HAGS

In Windows 11 25H2, reading the HAGS parameter is confirmed in dxgkrnl.sys. The selected state is taken into account when the graphics subsystem loads. For it to actually be enabled, WDDM 2.7+ and support from the GPU and driver are also required. Changing it requires a reboot.

The configuration mechanism is confirmed. Its effect on performance must be checked separately: compare frame time and micro-stutters in identical game runs on your own system.

Practical page: “HAGS”.

• D3DKMT_WDDM_2_7_CAPS, Microsoft Learn, checked 2026-08-27.

Runtime power and P-state

EnableRuntimePowerManagement allows runtime power management for a suitable adapter. DisablePStateManagement disables the selection of performance states only where the specific adapter supports it.

In a VMware environment or with the basic display driver, execution may not reach the reading of these parameters because of the adapter capability check. Such an observation cannot be used to judge their presence on a physical GPU.

Power parameters affect idle consumption, temperature and clock boosts under load. On a desktop GPU with a constant high load, changing them may increase consumption and temperature without a gain in performance.

What is confirmed

• The paths, types and default values of the parameters in the build studied.
• Reading SmallQuantumMode from the root of GraphicsDrivers and the meaning of the values 0, 1 and 2.
• Reading the HAGS parameter in dxgkrnl.sys and the WDDM 2.7+ requirement.
• The dependence of power parameters on the capabilities of the specific adapter.

What is not confirmed

• A gain in FPS, frame time or stability from changing the parameters.
• The behavior of ForceDirectFlip in specific games and configurations.
• The effect of power parameters on a physical GPU outside the tested environment.

Practical conclusion

Leave the default values. Change the parameters only to diagnose a reproducible frame output or power problem on a specific graphics card, and compare the result in identical runs.

Restoring the state

Return the stock values or delete the optional entries. For HAGS and power parameters, a Windows reboot may be required for them to take effect.

Limitations and sources

The conclusions apply to build 26200.9168, WDDM and the capabilities of the tested environment. A physical GPU and its driver require a separate check with DWM frame output tracing.

For how to reproduce the dynamic part of the observations, see How to check it yourself.

The research and the tools used belong to the BoosterX developer, so the developer has a direct interest in the results. The methodology and the limits of applicability are described above, and the conclusions can be verified against open data and the listed public sources.

• Multiplane Overlay, Microsoft Learn, checked 2026-09-01.
• GPU power management, Microsoft Learn, checked 2026-09-01.

Public sources checked: 2026-09-02.

Change history

• 2026-09-20: added a conflict-of-interest disclaimer and a link to independent verification of the dynamic observations in the methodology.
• 2026-09-02: first publication; reading and conditions of application of the parameters confirmed, limits for physical GPUs added.