Crackling, popping, and stuttering audio after the Windows 11 24H2 update is a special kind of maddening — the speakers are fine, the files are fine, but every song, call, and video is peppered with glitches. This is a real-time processing problem, not a broken speaker: somewhere in the chain from application to audio codec, samples are arriving late. The 24H2 update is a frequent trigger because it reshuffles drivers and power behavior, exposing latency weaknesses that older builds tolerated.
The diagnostic approach here differs from “no sound” troubleshooting. You are hunting for what steals the CPU’s attention at the wrong moment: an outdated audio driver, a latency-spiking network or storage driver, aggressive power saving, or conflicting enhancements. For the pre-24H2 version of this problem, see our post-update crackling guide , and the speaker crackling repair covers hardware-adjacent causes.
Why this happens
The 24H2 update left an incompatible audio driver that cannot keep up with the new audio stack’s timing.
DPC latency spikes from another driver (network, storage, GPU) starve the audio pipeline of CPU time.
Audio enhancements add processing that glitches under the new driver and power conditions.
Aggressive CPU power saving lets cores sleep too deeply between audio callbacks, causing underruns on wake.
Sample rate mismatches force real-time resampling that the pipeline cannot sustain.
Bluetooth stack activity generates latency spikes affecting even the built-in speakers.
Corrupted audio driver components from the update produce intermittent buffer failures.
The 24H2 update re-enabled audio enhancements you had previously disabled, silently restoring the processing layer that was causing buffer glitches before the upgrade.
How to fix it
Work through these in order — diagnose first, then act.
Fix 1: Disable audio enhancements
The fastest test with the highest hit rate. Recheck enhancements after every feature update — Windows loves to turn them back on.
- Right-click the volume icon, choose Sound settings, then More sound settings.
- On the Playback tab, double-click your speakers/headphones and open Properties.
- On the Enhancements tab, tick Disable all enhancements.
- Play audio for several minutes — if the crackling stops, the enhancements were the cause.
Fix 2: Set the sample rate to 24-bit 48000 Hz
Remove the resampling stage from the pipeline. Some apps override the shared sample rate with exclusive mode — the exclusive-mode untick prevents that.
- In the same device Properties, open the Advanced tab.
- Set Default Format to 24 bit, 48000 Hz (Studio Quality).
- Untick Allow applications to take exclusive control of this device.
- Click Apply and test with the same audio that crackled before.
Fix 3: Reinstall the manufacturer’s audio driver
The core 24H2 fix — replace whatever the update left behind. Microsoft’s Windows support site documents driver reinstallation. Get the 24H2-specific audio package from the manufacturer, not the generic Windows 11 one.
- In Device Manager, expand Sound, video and game controllers.
- Uninstall the Realtek (or Conexant/IDT) audio device, ticking Delete the driver software.
- Restart the laptop.
- Install the audio driver from your laptop manufacturer’s support page for Windows 11 24H2 specifically.
Fix 4: Measure DPC latency with LatencyMon
Find the driver that is actually stealing the CPU. Let LatencyMon run during your actual workload, not idle — spikes often need load to appear.
- Download LatencyMon from its official site and run it as administrator.
- Press the play button and let it monitor for five minutes while playing crackling audio.
- Check the Drivers tab for the highest DPC execution times.
- Update or disable the offending driver — network and storage drivers are the usual culprits.
Fix 5: Disable CPU power saving for audio
Deep sleep states and audio deadlines do not mix. Test on AC power first to separate power-saving crackle from driver crackle.
- Open Power Options advanced settings and expand Processor power management.
- Set Minimum processor state to 50 percent or higher on plugged in.
- Expand PCI Express and set Link State Power Management to Off as a test.
- In the BIOS, consider disabling the deepest C-states if the option exists and crackling persists.
Fix 6: Update the chipset and storage drivers
The latency often originates outside the audio driver entirely. Storage drivers cause some of the worst audio latency spikes despite having nothing to do with sound.
- Install the latest chipset driver from your laptop manufacturer’s support page.
- Update storage controller drivers (Intel RST or the NVMe driver) to current versions.
- Update the network drivers — Wi-Fi and Ethernet drivers are notorious DPC offenders.
- Re-run LatencyMon after each update to confirm the spikes are gone.
Fix 7: Test with Bluetooth disabled and a clean boot
Isolate software interference systematically. A clean boot that fixes crackling proves software interference — then bisect the startup items.
- Turn Bluetooth fully off in Settings and test the speakers.
- Run msconfig, choose Selective startup, and disable all non-Microsoft services.
- Restart and test audio in the clean state.
- Re-enable services in halves to identify the interfering program.
Closing
24H2 audio crackling is a latency problem wearing a driver problem’s clothes: disable enhancements, set a sane sample rate, reinstall the manufacturer’s 24H2-era audio driver, and hunt DPC spikes with LatencyMon. That sequence resolves the overwhelming majority of cases. If crackling persists in a clean boot with fresh drivers and low DPC latency, the audio codec hardware itself may be failing — rare, but the remaining explanation once software is exhausted. Once the audio is clean, stress-test it the way you actually listen: play music for half an hour, join a video call, and scrub through a video timeline. Crackling that only appears under specific loads points at the remaining bottleneck — often a single latency-spiking driver that LatencyMon can still identify. Keep LatencyMon installed; it is the fastest way to check if a future update reintroduces the problem.
