Reproduce the problem while measuring
Start LatencyMon, then play audio and do whatever triggers the crackling - a game, a browser with twenty tabs, a USB drive copy. Measuring an idle machine proves nothing.
Clicks and pops under load are usually a driver holding the CPU too long, not a broken sound card. LatencyMon names the offender in minutes.
Run **LatencyMon** for ten minutes with audio playing, then look at the **highest DPC execution time**. Anything above about **1 ms** causes dropouts - the driver at the top of the list is the one to update or remove.
Start LatencyMon, then play audio and do whatever triggers the crackling - a game, a browser with twenty tabs, a USB drive copy. Measuring an idle machine proves nothing.
The **highest measured interrupt to process latency** is the main figure; values under 500 microseconds are healthy. The **highest DPC execution time** shows which driver blocks the CPU longest.
Open the **Drivers** tab and sort by highest execution. The .sys name tells you the vendor: ndis.sys is networking, nvlddmkm.sys is the GPU driver, Wdf01000.sys is a framework shared by many.
Update the chipset, network and GPU drivers from the vendor, not from Windows Update. Then disable power saving on the network adapter and the USB hubs.
powercfg /setacvalueindex SCHEME_CURRENT SUB_PCIEXPRESS ASPM 0
Set the Windows sound format to 24 bit / 48000 Hz and raise the buffer in the audio software. A tiny buffer on a busy machine produces clicks that no driver update fixes.
mmsys.cpl > Properties > Advanced > 24 bit, 48000 Hz
Change one thing, run another ten-minute test and compare the worst latency. Without a second measurement you cannot tell whether the change helped or the machine was quieter.
LatencyMon measures worst cases. If nothing is audible during your normal workload, leave it alone.
A framework, not a device. Sort the processes tab and look at the driver underneath it in the report.
A different codec or a crowded 2.4 GHz band. Test with a cable to confirm the rest of the system is clean.
That app's buffer or sample rate is wrong. Fix the app, not the driver stack.
It only reads counters. Run it for the test and close it afterwards.
Rarely. Most dropouts are driver and power-management issues, not the codec.
Uninstall LatencyMon and set the sound format back if you changed it. Driver updates can be rolled back in Device Manager under Properties > Driver.
Free · no account needed · tracks your progress