Audio crackling, video stuttering, or mouse lag during demanding tasks on Windows 11 often point to high Deferred Procedure Call latency. DPC latency spikes occur when a hardware driver takes too long to complete a low-priority task, blocking the system from responding to real-time audio or video data. LatencyMon is a free tool that measures DPC execution time and pinpoints the exact driver file causing the delay. This article explains how to use LatencyMon to find the problematic driver and suggests steps to resolve the issue.
Key Takeaways: Identifying a Driver That Causes DPC Latency Spikes
- LatencyMon main window > Drivers tab: Displays a ranked list of drivers by DPC execution time, showing the highest offender at the top.
- LatencyMon > Monitor menu > Start monitoring: Begins collecting DPC and ISR data for at least 3 minutes during normal system load to produce accurate results.
- Device Manager > driver properties > Driver tab > Update driver or Roll Back driver: The primary fix for a driver that LatencyMon identifies as causing high latency.
What Causes DPC Latency Spikes on Windows 11
DPC latency spikes happen when a device driver holds the CPU longer than expected during a deferred procedure call. Windows 11 uses DPCs to handle non-critical tasks after an interrupt request. When a driver’s DPC routine exceeds 1 millisecond, the system may miss its real-time deadlines for audio playback, video rendering, or network throughput. Common culprits include outdated network drivers, buggy audio drivers, and poorly written storage controller drivers. LatencyMon measures the total time spent in DPCs per driver and reports the highest values, making it possible to isolate the offending driver without guessing.
Steps to Install and Run LatencyMon on Windows 11
Before you can identify the problematic driver, you need to download and start LatencyMon correctly. Follow these steps to set up the tool on your Windows 11 system.
- Download LatencyMon from the official website
Go to resplendence.com and download the LatencyMon installer. Run the installer and accept the license terms. The installation completes in under 30 seconds. - Launch LatencyMon as administrator
Right-click the LatencyMon desktop shortcut and select Run as administrator. Administrator rights are required for LatencyMon to access kernel-level performance counters. - Start the monitoring session
In the LatencyMon main window, click the Monitor menu and select Start monitoring. Leave the tool running for at least 3 minutes while you perform your typical workload, such as playing audio, watching a video, or using a web browser. Longer monitoring periods capture more data and improve accuracy. - Stop the monitoring session
After 3 minutes, click the Monitor menu again and select Stop monitoring. LatencyMon will process the collected data and display the results in the Drivers and Processes tabs.
How to Read LatencyMon Results to Find the Problematic Driver
Once monitoring stops, LatencyMon organizes data into several tabs. The Drivers tab is the most important for identifying the driver causing latency spikes.
- Open the Drivers tab
Click the Drivers tab at the top of the LatencyMon window. This tab lists every driver that executed DPCs during the monitoring period. The columns show Total Time, Count, and Average Time for each driver. - Sort by Total Time descending
Click the Total Time column header to sort drivers from highest to lowest total DPC execution time. The driver at the top of the list is the one consuming the most CPU time in DPCs and is the most likely cause of latency spikes. - Identify the driver file name
Look at the Driver column for the top offender. The file name is something like “e1d65x64.sys” for an Intel network driver or “usbaudio.sys” for a USB audio driver. Note the exact file name and the associated company name in the Company column. - Check the Processes tab for context
Click the Processes tab to see which processes triggered the DPCs. The top process often corresponds to the driver you identified. For example, if svchost.exe appears high, the network driver may be servicing a network-heavy process.
Resolving the DPC Latency Spikes After Identifying the Driver
After you know which driver is causing the problem, apply one of these fixes based on the driver type and your system configuration.
Update the driver to the latest version
Outdated drivers are the most common cause of DPC latency spikes. Open Device Manager by right-clicking the Start button and selecting Device Manager. Expand the category that contains the driver, such as Network adapters or Sound, video and game controllers. Right-click the device and select Update driver > Search automatically for drivers. Windows 11 will download and install the latest driver from Windows Update if available.
Roll back a recent driver update
If the latency spike started after a driver update, rolling back to the previous version may resolve the issue. In Device Manager, right-click the device and select Properties > Driver tab > Roll Back Driver. Confirm the rollback and restart your computer. After rebooting, run LatencyMon again to verify the driver is no longer causing high latency.
Disable the device temporarily
If updating or rolling back does not help, disable the device to see if the latency disappears. In Device Manager, right-click the device and select Disable device. Run LatencyMon for 3 minutes with the device disabled. If the DPC latency drops to acceptable levels, the device or its driver is incompatible with your system. You may need to replace the hardware or use a different driver version.
Common Issues When Using LatencyMon on Windows 11
LatencyMon reports high latency but the Drivers tab shows no single driver
This situation occurs when multiple drivers each contribute a small fraction of the total latency. The cumulative effect causes audio or video issues. In this case, update all drivers to their latest versions, especially chipset, network, and audio drivers. You can also try disabling unnecessary devices in Device Manager to reduce the number of active drivers.
LatencyMon shows high ISR latency instead of DPC latency
Interrupt Service Routine latency is different from DPC latency. ISR latency spikes often point to a hardware problem or a driver that runs at a high interrupt level. Check the ISR count in the Drivers tab. If a specific driver has a high ISR count, update that driver first. If the problem persists, the hardware may be faulty.
LatencyMon does not start or crashes on Windows 11
Ensure you are running LatencyMon as administrator. Some antivirus software may block LatencyMon from accessing kernel data. Temporarily disable your antivirus and try again. If the problem continues, reinstall LatencyMon using the latest version from the official website.
DPC Latency Monitoring Tools: Comparison
| Item | LatencyMon | Windows Performance Recorder |
|---|---|---|
| Installation | Free download from resplendence.com | Built into Windows 11 as part of the Windows Assessment and Deployment Kit |
| Ease of use | One-click start and stop monitoring | Requires command-line or GUI setup and analysis via WPA |
| Driver identification | Lists drivers sorted by DPC time in a single tab | Requires loading trace files and filtering by DPC events |
| Real-time monitoring | Yes, with live CPU and DPC graphs | No, only post-collection analysis |
| Best for | Quick driver troubleshooting for audio and video stutter | Deep system performance analysis by IT professionals |
LatencyMon is the more accessible tool for most Windows 11 users because it requires no trace file analysis. Windows Performance Recorder offers more detail but demands experience with the Windows Performance Analyzer.
You can now use LatencyMon to identify the driver causing DPC latency spikes on your Windows 11 system. After you find the driver, update or roll back the driver using Device Manager to restore smooth audio and video playback. For persistent issues, check the LatencyMon log for patterns during different workloads and consider disabling the problematic device as a last resort. Combining LatencyMon data with a review of recent driver changes gives you the fastest path to a stable system.