Hardware-Accelerated GPU Scheduling (HAGS): what it changes and whether to enable it

Frost LIVEGPUProUndo: YesUpdated Oct 8, 2026View as Markdown

Short answer

Updated Oct 8, 2026

HAGS writes HwSchMode to SYSTEM\CurrentControlSet\Control\GraphicsDrivers (2 enables it, 1 disables it) and moves parts of frame scheduling from the driver onto the GPU. It is required for DLSS Frame Generation. Otherwise it is one of very few settings where you genuinely have to test: it improves frame-time consistency on some CPU and driver combinations and introduces stutter on others, with no way to predict which from specifications.

In the app

Enable HAGSPRO

Registry

HKLMSYSTEM\CurrentControlSet\Control\GraphicsDrivers

HwSchModeNot set2

What the switch writes. Your current value may differ.

What it does

Normally the graphics driver batches and schedules the work sent to your GPU. HAGS hands a portion of that scheduling to a dedicated processor on the GPU itself, shortening the path between your game submitting a frame and the GPU starting it.

The change takes effect after a reboot, which is why toggling it and immediately benchmarking shows nothing.

When it helps, and when it hurts

When it helps

It is a hard requirement for DLSS Frame Generation. If you use frame generation, HAGS must be on.
On recent CPU and driver combinations it often flattens frame times slightly, which shows up in 1% lows rather than average FPS.
It can reduce CPU overhead in games that submit a very large number of draw calls.

When it hurts

On some older CPUs and specific driver revisions it introduces periodic stutter. This is well documented and not rare.
A handful of capture and overlay tools have historically misbehaved with it enabled.
It is not a free win. Anyone telling you to always enable or always disable it has not tested it across enough machines.

What it writes

Exactly what the switch changes, read from the app's source. Switching it off is what the app writes when you turn the tweak off again.

Registry values the switch writes.
Key and value	With the tweak	Switching it off
HKLMSYSTEM\CurrentControlSet\Control\GraphicsDriversHwSchModeTells the graphics stack whether the GPU may manage its own frame queue: 2 turns it on, 1 turns it off. Without the value, Windows and the driver decide.	2	Not setThe value is deleted. Windows decides.

From the app's source (tweaks_hags.hpp), app 2.0.0, checked Oct 8, 2026.

The same change by hand

You do not need the app for this one. These commands make the changes from the table above. Run them in a Command Prompt opened as administrator, and make a restore point first.

Make the change · CMD

reg add "HKLM\SYSTEM\CurrentControlSet\Control\GraphicsDrivers" /v "HwSchMode" /t REG_DWORD /d 2 /f

Put it back · CMD

reg delete "HKLM\SYSTEM\CurrentControlSet\Control\GraphicsDrivers" /v "HwSchMode" /f

See what it is set to now · CMD

reg query "HKLM\SYSTEM\CurrentControlSet\Control\GraphicsDrivers" /v "HwSchMode"

How to undo it

In the app: Yes

Switching it off sets a standard Windows value, which may not be exactly how you had it.

Turn the toggle off in Settings > System > Display > Graphics > Change default graphics settings, or set HwSchMode to 1, and reboot. Switching it off in Frozen Tweaks deletes HwSchMode, so Windows goes back to its standard behavior for your GPU, which may not be exactly how you had it.

Changing several settings at once? The app's Make a restore point button, on every plan, makes a Windows restore point before you start.

Verdict

Test it. Benchmark the same scene twice, once in each state, and keep whichever gives better 1% lows. If you use DLSS Frame Generation the decision is made for you.

In the app