Audio latency in Windows 11 is a multi-layered problem. A note you play on a MIDI keyboard takes a path through your DAW, the audio driver stack, the Windows audio engine, the kernel, and finally your audio hardware. Each layer adds delay. For casual listening, this is invisible. For live recording, gaming, or real-time audio processing, it becomes audible and frustrating.

This guide breaks down each layer and gives you concrete steps to reduce latency at every stage.

Understanding the Windows Audio Stack

Windows routes audio through several processing layers:

Application → Windows Audio Session API (WASAPI) → Audio Engine (audiodg.exe) → Driver → Hardware

WASAPI Shared Mode — The default for most apps. The Windows audio engine mixes audio from all applications, applies effects, and resamples. Convenient but adds 10–30ms of latency.

WASAPI Exclusive Mode — Bypasses the audio engine. Your app talks directly to the driver. Latency drops to 3–10ms depending on driver quality.

ASIO (Audio Stream Input/Output) — A driver protocol that completely bypasses the Windows audio stack. Targets sub-5ms latency, often as low as 1–3ms with quality hardware. Required for serious audio production.

Checking Your Current Latency

Before making changes, measure your baseline. LatencyMon is the standard tool for this — download it free from Resplendence Software (resplendence.com/latencymon).

Run LatencyMon for a few minutes while doing normal computer activity. Look for:

Highest reported DPC routine execution time — Should be under 500 µs (microseconds). Above 1000 µs is problematic.
Highest ISR execution time — Should be under 500 µs.
Problematic drivers — LatencyMon identifies which drivers are causing spikes. Common culprits: ndis.sys (network), nvlddmkm.sys (Nvidia GPU), dxgkrnl.sys (DirectX), storport.sys (storage controller).

The Drivers tab in LatencyMon ranks every driver by execution time. The top offenders tell you exactly where to focus.

Fix 1 — Address DPC Latency Sources

DPC (Deferred Procedure Call) latency is kernel-level interrupt processing. High DPC latency from any driver will cause audio glitches regardless of your buffer settings.

Network Adapter — The Most Common Culprit

# Disable interrupt moderation on your network adapter
Set-NetAdapterAdvancedProperty -Name "Ethernet" -DisplayName "Interrupt Moderation" -DisplayValue "Disabled"

Also disable these if present on your NIC:

Large Send Offload (v1 and v2)
Receive Side Scaling (RSS) — try disabling and re-test

USB Controllers

USB 3.0 controllers are frequent DPC latency sources. In Device Manager → Universal Serial Bus controllers, try disabling USB 3 controllers you aren’t using. If you have nothing plugged into rear USB ports, those controllers can be power-managed aggressively.

Nvidia Drivers

If nvlddmkm.sys appears in LatencyMon:

In Nvidia Control Panel → Manage 3D Settings → set Power management mode to Prefer maximum performance.
Disable CUDA - Force P2 State if visible.
Consider using the DDU + studio driver workflow instead of game-ready drivers — studio drivers are often more stable under audio workloads.

Fix 2 — Configure WASAPI Exclusive Mode

For apps that support it (foobar2000, some DAWs), enabling WASAPI Exclusive Mode eliminates the audio engine overhead:

In foobar2000:

Go to Preferences → Playback → Output.
Select WASAPI (event): [Your Device].
Set buffer length to 10–20ms.

In Windows Sound Settings:

Right-click the speaker icon → Open Sound settings → More sound settings.
Select your playback device → Properties → Advanced tab.
Check Allow applications to take exclusive control of this device.
Uncheck Enable audio enhancements (this adds latency and distortion for critical listening).

Fix 3 — Install ASIO Drivers

ASIO is the gold standard for low latency. If you have a dedicated audio interface (Focusrite Scarlett, PreSonus AudioBox, RME, etc.), install the manufacturer’s ASIO driver:

Focusrite: Download Focusrite Control + Scarlett ASIO driver
PreSonus: Download Universal Control
RME: Install RME driver package (RME drivers are considered best-in-class for latency)

After installing, configure the buffer size in your DAW. Start at 128 samples and work down:

Buffer Size	Approximate Latency	CPU Load
512 samples	~12 ms	Low
256 samples	~6 ms	Medium
128 samples	~3 ms	Medium-High
64 samples	~1.5 ms	High
32 samples	~0.7 ms	Very High

For recording: use 64–128 samples. For mixing/playback: use 256–512 samples to reduce CPU load.

No audio interface? Install ASIO4ALL (asio4all.org) — a free wrapper that gives generic hardware ASIO capability. It works surprisingly well for built-in audio and budget USB sound cards.

Fix 4 — Disable Audio Enhancements

Windows applies spatial sound, equalization, and enhancement effects to audio output by default. These add latency and can degrade audio quality:

Settings → System → Sound → select your output device → More device properties.
On the Enhancements tab, check Disable all enhancements.
On the Spatial sound tab, set it to Off.

Or via PowerShell:

# Disable audio enhancements via registry
# (Replace {GUID} with your audio device GUID from regedit)
# Navigate to: HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\MMDevices\Audio\Render\{GUID}\FxProperties
# Set: {d04e05a6-594b-4fb6-a80d-01af5eed7d1d},0 to 0x00000001

The manual Settings approach is more reliable for this specific change.

Fix 5 — Set a Real-Time Process Priority for Your DAW

Windows 11’s default process scheduling is optimized for throughput, not latency. Setting your DAW to real-time priority reduces scheduling jitter:

# Set a running process to real-time priority (use carefully — can make system unresponsive)
# Replace "Ableton Live" with your DAW's process name
$proc = Get-Process "Ableton Live"
$proc.PriorityClass = [System.Diagnostics.ProcessPriorityClass]::RealTime

Most DAWs have a built-in option to set their own priority — check Preferences first. Real-time priority can cause other applications to become unresponsive if the DAW is misbehaving, so use with awareness.

Fix 6 — Power Plan for Audio Work

The Balanced power plan allows CPU C-states that introduce microsecond-scale wake-up latencies. For audio work, switch to High Performance:

powercfg /setactive 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c

Or search for Power & sleep settings → Additional power settings → select High performance.

Verification After Changes

After applying fixes, re-run LatencyMon for 10 minutes under normal load. You should see:

DPC execution times below 200 µs consistently
No drivers highlighted in red
Audio playback in your test app without glitches at 128-sample buffer

If spikes remain, check the Drivers tab and research the specific driver name — there’s often a firmware update, driver version change, or specific setting that resolves it.

Summary: Low-Latency Audio Checklist

Run LatencyMon and identify problematic drivers
Disable Interrupt Moderation on network adapter
Disable audio enhancements in Sound settings
Enable WASAPI Exclusive Mode or install ASIO drivers
Set buffer to 128 samples for recording
Switch to High Performance power plan during sessions
Disable Nvidia GPU power saving features
Disable USB controllers not in use

Getting sub-5ms round-trip latency on Windows 11 is absolutely achievable with the right configuration. The key is identifying your specific bottleneck with LatencyMon rather than applying every fix blindly.