How to Find Which Driver Causes DPC Latency Spikes on Windows 11

Quick fix: Run LatencyMon for two minutes during a spike to see which driver is responsible — the top entry in “Drivers with highest ISR/DPC routine execution time” is your culprit. Common offenders: Wi-Fi (nwifi.sys), Realtek audio (RTKVHD64.sys), and NVIDIA (nvlddmkm.sys).

Audio crackles. Mouse cursor stutters during otherwise idle moments. Games hitch despite high frame rates. The symptoms point to DPC (Deferred Procedure Call) latency — a Windows kernel scheduling problem where one driver hogs the CPU briefly and blocks others. The fix is identifying which driver, not changing system-wide settings.

What DPC latency is and why it matters

Hardware drivers run in two kernel stages: ISR (Interrupt Service Routine, very short, must finish in microseconds) and DPC (Deferred Procedure Call, longer work scheduled after the ISR). Both run with higher priority than any user-mode code. If a driver’s ISR or DPC takes too long, real-time tasks like audio buffer refills miss their deadlines and you hear a glitch. Anything above 1 ms DPC time on a desktop, or 2 ms on a laptop, is suspect.

You can’t see this in Task Manager. You need a tool that hooks the kernel ETW providers and times each driver’s DPCs.

Method 1: Use LatencyMon to identify the driver

1. Download LatencyMon from resplendence.com/latencymon. Run it as Administrator.
2. Click the green play button. Reproduce the glitch (move the mouse, play music, run the game) for at least 60 seconds.
3. Stop monitoring. Click the Drivers tab.
4. Sort by DPC count or Highest measured interrupt to process latency. The driver at the top is your bottleneck.
5. Note the file name (e.g., nwifi.sys for Microsoft Wi-Fi, RTKVHD64.sys for Realtek audio, ndis.sys + e2nw11x64.sys for Intel Ethernet).

LatencyMon also reports total ratings: Your system seems to be having difficulty handling real-time audio means the top driver has a real problem.

Method 2: Update or replace the offending driver

Once you know the driver, the fix depends on which one.

1. If Wi-Fi driver: open Device Manager → Network adapters → right-click your Wi-Fi adapter → Update driver → Search automatically. If no newer version found, download directly from Intel/Killer/MediaTek website.
2. If Realtek audio (RTKVHD64.sys): update to the OEM-specific Realtek driver (laptop manufacturer’s site) rather than generic. The OEM build often has DPC fixes for that specific motherboard.
3. If NVIDIA (nvlddmkm.sys) or AMD (atikmdag.sys): use the latest WHQL driver. If the issue started after a driver update, roll back to the previous version (Device Manager → the GPU → Properties → Driver → Roll Back Driver).
4. If a USB driver (usbport.sys, usbxhci.sys): a faulty USB device is generating events. Unplug devices one at a time until LatencyMon improves.
5. Reboot after each driver change and re-run LatencyMon for 2 minutes to confirm improvement.

For network drivers, also turn off power management: Device Manager → adapter → Properties → Power Management → uncheck Allow the computer to turn off this device to save power. Wi-Fi power save is a frequent DPC culprit.

Method 3: Disable C-states or set power plan to High Performance

Some CPUs exit deep C-states slowly, and the wake delay shows up as kernel latency. Tightening power settings can help.

1. Open powercfg.cpl. Select High performance (or create a new plan based on Balanced with deep sleep disabled).
2. Under Change plan settings → Change advanced power settings, find Processor power management.
3. Set Minimum processor state to 100% while plugged in. This prevents deep C-states.
4. Save and re-test LatencyMon.
5. If glitches stop, the CPU’s sleep transitions were the cause. Revert if you don’t want the power penalty.

On modern laptops, this is rarely worth the battery impact — only do it on plugged-in workstations or when troubleshooting audio production gear.

How to verify the fix worked

• Run LatencyMon for 5 minutes during normal workload. The top driver’s highest measured DPC routine execution stays below 1000 us (1 ms).
• The summary line at the bottom reads Your system appears to be suitable for handling real-time audio.
• Play music for 30 minutes — no glitches.
• If you play games, no hitches during otherwise smooth gameplay.

If none of these work

If LatencyMon points to dxgkrnl.sys (the kernel-mode graphics manager), the issue is the GPU driver or a display-related setting — toggle Hardware-accelerated GPU scheduling off (Settings → System → Display → Graphics → Default graphics settings) and retest. If it points to wdf01000.sys (Windows Driver Framework, generic), one of several drivers using KMDF is involved — check Event Viewer for recent driver-related errors. For persistent latency that survives all driver updates, the cause may be a BIOS-level issue — check for a UEFI update from the motherboard or laptop vendor that mentions performance or latency fixes.

Bottom line: DPC latency is a driver problem, not a Windows problem. LatencyMon names the culprit in two minutes. Update or replace that driver, set its power management to high performance, and the glitches go away.