Why creators on 6GB and 8GB GPUs should test Windows HAGS

Windows hardware-accelerated GPU scheduling can consume scarce VRAM on 6GB and 8GB cards. Disabling it may free nearly 950MB but costs frame generation. Creators should benchmark.

What happened

Windows 11 has a graphics setting many people never touch: hardware-accelerated GPU scheduling, or HAGS. It is on by default on most PCs and is a requirement for DLSS Frame Generation. But for older or cheaper cards, such as an RTX 2060 with 6GB of VRAM or one of the many 8GB cards still on sale, HAGS can consume VRAM that the card cannot easily spare.

When XDA Developers switched HAGS off on an 8GB RTX 2070 Super, it freed up nearly 950MB of graphics memory for the loss of three to five frames per second. Textures that had been stuttering in Cyberpunk 2077 and Stellar Blade loaded properly again. On a card with 16GB or more, that much VRAM barely matters, but on 6GB or 8GB it can be the difference between a game running smoothly and one that runs out of memory.

Microsoft introduced HAGS in a May 2020 Windows 10 update. The feature shifts most scheduling work to the graphics card's dedicated hardware, while Windows still decides which apps go first. Microsoft rolled it out switched off by default and said users "should not notice any significant changes," but many Windows 11 systems now have it enabled. Nvidia added support starting with its GTX 10-series cards in the 451.48 driver; AMD didn't support it until December 2023 on the RX 7900, 7800 and 7700; Intel only supports it on Arc B-series cards.

Key facts

• HAGS is on by default on most PCs and is required for DLSS Frame Generation.
• Disabling HAGS on an 8GB RTX 2070 Super freed nearly 950MB of graphics memory at a cost of three to five frames per second.
• Tom's Hardware testing of an RTX 2080 Ti and a GTX 1050 in 2020 found an average change ranging from minus 0.73 percent to plus 0.06 percent.
• Gamers Nexus found no significant gains and even a repeatable 2.4 percent drop in F1 2019 on a four-core Intel Core i3.
• Steam's September 2026 hardware survey found 8GB cards still make up more than a quarter of GPUs, second only to 16GB, while 6GB cards account for 5.12 percent.
• OBS recommends switching HAGS off if you run into problems while recording or streaming.

Our analysis

The Steam hardware data matters because memory prices have been pushed to record highs and affordable GPUs are hard to find. This likely means many creators and streamers are still running 6GB or 8GB cards, exactly the hardware where HAGS can become a liability. The setting is not universally bad: on 12GB or more, the freed memory is less meaningful, and HAGS is required for frame generation. But the tradeoff changes on constrained cards.

The performance tests suggest that disabling HAGS usually costs very little in average frame rate. The measured range from minus 0.73 percent to plus 0.06 percent and the repeatable 2.4 percent drop in one title indicate that most users may not notice the FPS loss, especially if they gain nearly 950MB of VRAM to stop texture stutter. For memory-limited games, that VRAM headroom can be more important than a few frames.

The OBS recommendation is the clearest signal for creators: if recording or streaming is unstable, HAGS is a setting to test alongside encoder and capture options. Since HAGS is on by default on many Windows 11 systems, some operators may never have checked it, and a restart is required for changes to take effect.

What it means for operators

• Check the HAGS toggle in Settings > System > Display > Graphics > Advanced graphics settings on any workhorse PC, especially with a 6GB or 8GB GPU; a system restart is required after changing it.
• On 6GB or 8GB cards, test game by game: if a title is already maxing out VRAM, switch HAGS off and benchmark before and after to see if stutter improves at a cost of a few frames.
• If you use DLSS Frame Generation or have 12GB of VRAM or more, leave HAGS on; frame generation won't work without it.
• If OBS recording or streaming shows problems, follow OBS's recommendation and switch HAGS off, then retest capture performance.