DirectX 11 & Game Stutters (micro-freezes)

Updated 1/27/26 – Still in testing

Create a Restore Point before tweaking to restore settings if conflicts arise.
1) Open Start Menu, type restore in the search bar.
2) Open Create restore point, select the Create button.
3) Name the restore point and click Ok

Understanding the difference between DX9 and DX11.

Direct3D 11 introduces a higher level of polymorphism on video memory resources, called views. Unlike in Direct3D 9, where a single object represented a texture, there are now two separate objects: the texture resource, containing the data, and the resource view, specifying how the view is utilized for rendering.

Increased DX mode places more demand on the system due to higher texture resolutions in games, impacting frame rates. Higher-end video cards and systems tend to handle DX11 games more effectively than mid to low-end alternatives.

Today’s more advanced systems require a more powerful DirectX API, leading to the development of DX11 and DX12 in order to handle advanced multimedia and games.

DX11 can strain older systems, leading to lower frame rates when gaming with mid to low level systems/video cards. Lowering the DX mode may improve performance, but it could also impact image quality.

In Aces High III, the DirectX 11 version is needed for Virtual Reality views. If you are having problems, like game freezes with the DirectX 11 version, and you do not use VR, you can use DirectX 9 version, or use the tweaks below to use DX11.

DirectX 11 Game Stutters, often referred to as micro-freezes.

The following information below provided by Aces High player “Dadtillica”. It has been condensed from original form for this page.

It’s original form may be found here https://bbs.hitechcreations.com/smf/index.php/topic,412054.msg5464986.html#msg5464986

What using Aces High III DX9 version to “Fix It” does NOT mean.

It does not mean the GPU is too weak
It does not mean Aces High III is poorly optimized
It does not mean the GPU driver is fundamentally broken
It does not mean reducing graphics settings is required

It means the DX11 > Windows > Display timing chain is being disrupted by modern scheduling features that AHIII does not need and does not benefit from.

Bottom Line
This is a Windows/DX11 presentation issue, not a GPU brand defect. DX11 uses the modern Windows flip-model presentation path.
This path is sensitive to timing interference from the OS and driver stack. If DX9 eliminates the stutter, the GPU is not underpowered—the pipeline is misaligned.

Root causes

DX11 frame pacing conflict:
DX11 uses the modern Windows flip-model presentation path.
This path is sensitive to timing interference from the OS and driver stack.
Fixed-refresh rate
Example: A TV operates at broadcast-standard 59.94 Hz, not true 60.00.
Small timing mismatches accumulate and cause periodic frame queue stalls. It’s always best to use native refresh rates.
Windows “Optimizations for Windowed Games”
Forces flip-model even when fullscreen is requested.
Competes with DX11’s internal frame pacing logic.
Hardware-Accelerated GPU Scheduling (HAGS)
Adds a GPU-side scheduling queue managed by Windows.
Under DX11, this can intermittently block present calls.
Using DX9 avoids the issue incidentally.
DX9 uses legacy exclusive full screen presentation.
By using a blit-based or legacy swap chain path, DX9 sidesteps modern flip-model behavior where missed presentation deadlines can stall the render queue.

Aces High III Clipboard can trigger stutters with the root cause.

Leaving the Aces High Clipboard open can be the quickest way to manifest the root cause, above.

Some stutters are tied to high-frequency UI updates, not the core rendering loop. UI redraw bottleneck.

What’s likely happening under the hood

The clipboard map is a 2D UI overlay that forces frequent CPU → GPU synchronization to redraw icons, text, and vectors.
When activity density is high, the map triggers bursty draw calls and state changes that momentarily stall the render thread.
DX11 + Windows’ modern presentation pipeline (DWM, flip model, fullscreen optimizations) can briefly block the frame queue when a UI surface updates aggressively.
Closing the map removes that UI update path entirely, which is why the stutters disappear.

What you can do next (optional mitigation)

Minimize time with the clipboard map open during peak furballs.
Avoid right-click panning/zooming the map during extremely dense activity.
If available, reduce map detail options (icon density, labels, vector length).
Treat the map as a situational tool, not a persistent overlay, during large engagements.

SUGGESTED WINDOWS SETTINGS

The best way to apply system tweaks is to try them one at a time, reboot the device, and test in-game before moving to the next one until the problem is fixed.

Disable Hardware-Accelerated GPU Scheduling to remove GPU queue conflicts.

Hardware-Accelerated GPU Scheduling (HAGS) is a Windows feature that lets the GPU directly manage its memory and tasks, shifting work from the CPU to the GPU for lower latency, improved performance, and better efficiency in graphics-intensive tasks like gaming or rendering. While it offers potential benefits by reducing CPU overhead, its impact varies; users should enable it in Windows Graphics Settings and restart their PC to test if it improves performance for their specific hardware and applications, as some games run better with it on, while others might see issues.

How it Works
Traditional: The CPU manages all commands and resources for the GPU. With HAGS: The GPU’s own processor handles scheduling its workloads and memory (VRAM) in batches, freeing up the CPU.

Benefits
Lower Latency: Reduces input lag in games.
Improved Performance: Frees CPU resources, boosts overall system responsiveness, and can increase FPS in some scenarios.
Enhanced Efficiency: Optimizes GPU resource allocation for smoother visuals.

1) Open the Start Menu type Settings in the search bar. Open it and select System, then Display.

2) Choose Graphics,

3) Under Advanced graphics settings (or “Default graphics settings” for Windows 11) toggle off Hardware-Accelerated GPU Scheduling.

Disable Optimizations for Windowed Games to restore true fullscreen control

Optimizations for windowed games improves gaming on your PC by using a new presentation model for DirectX 10 and DirectX 11 games that appear in a window or in a borderless window.

When these optimizations are used, games that originally use the legacy blt-model presentation can use the newer flip-model presentation instead (if the game is compatible). This results in lower frame latency and lets you use other newer gaming features; for example, Auto HDR, and variable refresh rate (for displays that support it).

This process allows the game to run in full screen mode with full control over the display, potentially improving performance and reducing input lag. However, be aware that disabling optimizations may cause some games to behave differently or may not be compatible with certain overlays or background applications. Always test the game after making these changes to ensure the best performance for your specific setup.

1) Locate the Game’s Executable: Find the main executable file (.exe) of the game you want to modify.
2) Open Properties: Right-click on the executable file and select Properties.
3) Go to the Compatibility tab in the Properties window.
4) Disable Fullscreen Optimizations: Check the box labeled ‘Disable fullscreen optimizations‘ and click Apply then save the changes.

Enable Game Mode for consistent CPU scheduling.

This option optimizes your device for gaming by prioritizing the game’s performance, reducing background tasks (like updates and notifications) for smoother frame rates, and lowering input/audio latency for connected accessories like controllers and headphones. On PCs, it gives games more CPU/GPU access; on iPhones, it silences interruptions and boosts responsiveness for Bluetooth audio. On TVs, it reduces image processing to minimize input lag for quicker on-screen response.

On PCs, it allows better CPU/GPU access for games; on iPhones, it silences interruptions and improves Bluetooth audio responsiveness. On TVs, it lowers image processing to reduce input lag for faster on-screen response.

1) Open Settings and click Gaming.
2) Windows 10: select Game Mode from the left menu.
(Windows 11: Gaming > Game Mode.)
3) Set Game Mode to On.

SUGGESTED GRAPHIC CARD (GPU) SETTINGS

The best way to apply system tweaks is to try them one at a time, reboot the device, and test in-game before moving to the next one until the problem is fixed.

NVIDA

Low Latency Mode

Ultra Low Latency Mode (NULL) reduces input lag in games, particularly in DirectX 9/11 titles, by minimizing the frame buffer. This results in a more responsive gameplay experience, similar to a system that submits frames as soon as the GPU is ready instead of waiting. You can enable it in the NVIDIA Control Panel under “Manage 3D Settings.” However, it may lower FPS or cause stutter if your CPU can’t keep up, even though it generally enhances 1% lows for smoother performance.

“On” is usually the best choice for most games since it limits the render queue to one frame, balancing performance and latency; “Ultra” should only be used in GPU-heavy situations (95-100% usage) where your system has trouble keeping up, as it aims for zero frames and may cause stuttering if the GPU lags, while “Off” is often better for CPU-heavy games or when your GPU has plenty of power, with Reflex settings taking priority if available.

V-Sync

The main downside to using VSYNC is that it can reduce your computer’s performance. Additionally, some people may notice input lag or stuttering when using it. However, these issues are usually only noticeable in certain situations and may not affect everyone.

Turning off VSync (Vertical Sync) disables the synchronization between your graphics card’s frame output and your monitor’s refresh rate, which removes screen tearing but can introduce input lag, making games feel less responsive; it allows your GPU to render frames as fast as possible, potentially leading to higher frame rates (FPS), but also causing the GPU to work harder and render frames you can’t even see on your screen, sometimes resulting in stuttering if the FPS drops significantly below the monitor’s refresh rate.

Fast settings. Fast reduces latency without causing tearing. This is available on Pascal and newer GPUs in single-GPU setups.

Note: V-Sync settings in Nvidia Control Panel will over-ride V-sync setting in Aces High

Nvidia Control Panel Settings

1) Go to manage 3D settings
2) Vertical Sync (V-sync): select Fast. Nvidia settings over-ride Aces High settings, “Use the 3D application setting” in AH default is on so this would mean you’re turning it on, defeating the purpose.
3) Low Latency Mode: select Off (avoid Ultra for DX11).

*4) Max Frame Rate: Set to match monitor refresh rate. Small timing mismatches accumulate and cause periodic frame queue stalls. It’s always best to use native refresh rates. The human brain is really only able to identify images up to 75fps.

AMD

• Turn off FreeSync on fixed-refresh TVs.
• Use exclusive fullscreen where possible.

Most AMD users report improvement, but may need trial-and-error with VSync and FreeSync combinations.

Note: Replace the AMD Drivers with prior version to remove conflicts with DX11.

INTEL iGPU / ARC GPUs

• Lock CPU minimum frequency in Windows power plan
• Disable panel self-refresh and adaptive brightness.
• Avoid borderless/windowed modes entirely.

Fixable in many cases, but not guaranteed without deeper tuning.

Flushing DirectX Shader Cache
On Windows 11, DirectX Shader is an optimization feature for storing pre-compiled versions of special instructions, known as shaders.
Shaders are small programs understood by the graphics card that control various graphical effects.
Compiling shaders can be time-consuming, and using a cache helps optimize performance by providing easier and faster access to pre-compiled versions.

The decision to clear the cache will depend on you. However, below are some reasons why you may want to do so.
To resolve performance issues – A cleared DirectX Shader cache may resolve some performance issues, including graphical glitches and stuttering.

Freeing up disk space – Even though the cache may not take up much space, clearing it will still free up some extra space on your computer.

To update the cache – If you have just updated your graphics card or installed new games, you may clear the DirectX Shader cache to fill it with new information.

Note: clearing the cache is not something you must do often. It is mainly a troubleshooting step when you face some graphical issues.
This procedure will not negatively affect your system. This is because the cache is isolated storage with no permanent information.
You cannot disable or prevent the creation of the DirectX Shader Cache. Windows 11 has no official way of disabling this optimization feature.
Ccleaner provides an option to flush the DirectX Shader Cache.

To flush DirectX Shader Cache Using Disk Cleanup
1. Open Start Menu, type cleanup in the search bar, click Disk Cleanup to open it..
2. Select your C drive, then click the OK button.
3. Tick the DirectX Shader cache option and click OK.
Note: Though this is meant to flush DSC, it could be a good idea to check every listed item.

End