That occasional pop, click, or crackle interrupting your music or game audio isn't always a sign of faulty hardware. For thousands of Windows users, the culprit lies deep within the CPU's power-saving features—a class of technologies collectively known as C-states. Disabling these sleep states can banish audio glitches for good, but the fix comes with a trade-off.

Audio crackle and DPC latency spikes have long haunted Windows-based systems, particularly those used for real-time audio production, gaming, or high-fidelity playback. Users often swap DACs, upgrade cables, or reinstall drivers, only to find the problem persists. The real issue, more often than acknowledged, is the processor going to sleep on the job.

The Silent Saboteur: What Are CPU C-States?

Modern x86 processors from Intel and AMD operate in multiple power states, defined by the Advanced Configuration and Power Interface (ACPI). These C-states range from C0 (active, full power) to deeper idle states like C1 (halt), C6, and even C10 on newer chips. When the CPU has nothing to execute, it enters a low-power C-state, which reduces voltage and clock speed, and may flush caches or power-gate entire cores. Waking from these states takes time—microseconds to milliseconds—and this latency is the enemy of real-time audio.

Audio playback demands a steady stream of data at precise intervals. A typical USB audio interface might request a 256-sample buffer every 5.8 milliseconds at 44.1 kHz. If the CPU is in a deep C-state when a new buffer is needed, the wake-up delay can cause a buffer underrun, resulting in a pop or crackle. The problem is exacerbated by the Deferred Procedure Call (DPC) mechanism in Windows, where drivers queue work for later execution. If the CPU is sleeping, DPCs pile up, and when it wakes, a burst of deferred tasks runs, hogging the system and starving the audio stream.

DPC Latency: The Canary in the Coal Mine

The link between C-states and audio glitches is best understood through DPC latency. DPCs are routines that drivers request to run at heightened IRQL (Interrupt Request Level), taking precedence over most user-mode threads. A high DPC latency means the system is spending too long in these privileged routines, blocking time-sensitive audio processing. Tools like Resplendence LatencyMon have become the go‑to diagnostic for audio professionals. On a clean system, DPC latency should stay below 100–200 microseconds. When C-states are enabled, it's common to see spikes exceeding 1,000 microseconds, especially from drivers like ndis.sys (network) or storport.sys (storage).

Microsoft's own documentation for Windows driver developers explicitly warns about the pitfalls of C-state transitions. The power manager coordinates idle timeouts and wake events, but some transitions, particularly to C6 and deeper, require substantial hardware reinitialization. Badly written drivers can exacerbate the problem by holding spin locks during a sleep transition, causing system-wide stalls.

The Simple Fix: Disable CPU C-States

If your audio crackling correlates with high DPC latency and your system is an otherwise well-maintained Windows 10 or 11 machine, the single most effective fix is to prevent the processor from entering low-power C-states. This can be done through either the UEFI/BIOS firmware or, to a lesser extent, within Windows power settings.

Method 1: BIOS/UEFI Configuration

Restart your PC and enter the BIOS setup. Look for options typically found under \"Advanced CPU Configuration\" or \"AMD CBS\" / \"Intel RC ACPI Settings.\" The exact naming varies by motherboard vendor, but common labels include:

  • Global C-state Control – Set to \"Disabled.\"
  • Power Supply Idle Control – Set to \"Typical Current Idle\" (AMD) or \"High Performance\" (Intel).
  • C6 Mode / C1E Support – Disable these individually if you want to retain shallower states.
  • DF Cstates – On AMD systems, this controls data fabric power states; disable it.

After saving and exiting, boot back into Windows. The difference can be immediate. Many users report DPC latency dropping from over 1000 µs to a stable 20–50 µs. Resplendence LatencyMon will often show a green light for real-time audio suitability once deep C-states are disabled.

Method 2: Windows Power Plan Tweaks

For systems where BIOS access is restricted (e.g., many laptops), you can influence C-states through Windows. Open Control Panel → Hardware and Sound → Power Options. Select the High Performance plan, then click “Change plan settings” and “Change advanced power settings.” Expand Processor power management and set:

  • Minimum processor state: 100%
  • Maximum processor state: 100%

This prevents the OS from idling the CPU, but it doesn't fully inhibit all hardware C-state transitions; the CPU may still briefly enter C1. For deeper suppression, you can expose hidden power settings via Command Prompt (Admin) with powercfg -attributes SUB_PROCESSOR 5d76a2ca-e8c0-402f-a133-2158492d58ad -ATTRIB_HIDE to reveal the Processor idle disable power control option. Enabling “Processor idle disable” forces the CPU to stay in C0.

Some enthusiasts use tools like QuickCPU to fine‑tune C-state residency and core parking without diving into the registry. However, the BIOS method remains the most complete solution.

Real-World Results: What Users Experience

In audio production communities, disabling C-states is a known rite of passage. On multiple pro‑audio forums, users battling random pops from Focusrite, RME, or Universal Audio interfaces have found that toggling off C6 and C1E eliminated crackling overnight. A geeky gamer with a high‑refesh‑rate monitor noted that his screen flicker also disappeared, a testament to how deep power states can disrupt any time‑sensitive output.

Audio engineer and Windows tuning expert Pete Brown (of Microsoft's own Windows Audio team) has acknowledged that aggressive power management can interfere with real‑time audio. While Microsoft's AudioDG framework handles most consumer scenarios well, low‑latency ASIO or WASAPI exclusive‑mode streams are particularly vulnerable.

Performance and Power Draw: No Free Lunch

Disabling C-states forces the CPU to stay at high power, raising idle power consumption and heat. On a desktop with an Intel Core i9-13900K, idle package power can jump from 10 W to over 30 W. On a laptop, this will noticeably reduce battery life—potentially cutting unplugged runtime by 30–50%. For a mobile audio workstation, the trade-off may be acceptable during a recording session but unsustainable for daily carry.

That said, modern CPUs have grown so powerful that shallow C-states (C1) often suffice for most non‑audio tasks. Many users report that simply disabling C6/C7 and keeping C1E enabled strikes a reasonable balance, eliminating DPC spikes without doubling idle consumption.

Other Power Management Tweaks That Help

While C-states are the primary culprit, other power‑saving features can also degrade audio:

  • PCI Express Link State Power Management: Under Windows Power Options, set this to Off. Active‑state power management (ASPM) can cause latency when PCIe devices wake up.
  • USB Selective Suspend: Disable this to prevent your audio interface from being put to sleep. In Power Options, set “USB settings” → “USB selective suspend setting” to Disabled.
  • CPU Parking: The High Performance plan disables core parking, but you can verify with Resource Monitor. Parked cores introduce wake latency.
  • Network Drivers: Update Ethernet and Wi‑Fi drivers, or disable onboard LAN if not needed. Poorly optimized network drivers are notorious DPC spikers.

A Note on Windows Updates and Firmware

Microsoft continually refines its power management, and some audio improvements have landed in recent Windows 11 builds (23H2 and later). For instance, build 22631 introduced optimizations for Intel Thread Director that indirectly reduced DPC spikes. But the kernel still relies on driver discipline; a misbehaving Realtek audio driver or an outdated BIOS can reintroduce the problem even after tweaking C-states.

Before assuming C-states are the fix, ensure your system's firmware and chipset drivers are up to date. AMD Ryzen users, in particular, should install the latest AMD Chipset Drivers, which include a custom version of the Ryzen Balanced Power Plan that correctly manages the platform's odd hardware topology.

Step-by-Step Diagnostic Guide

If you're not sure whether C-states are your issue, follow this workflow:

  1. Run LatencyMon (free from Resplendence) and start a test.
  2. Play audio via your usual application. Watch for DPC spikes that correlate with crackles.
  3. Note the driver with the highest execution time—common offenders are ndis.sys, storport.sys, dxgkrnl.sys, and Wdf01000.sys.
  4. If the culprit is Wdf01000.sys (Windows Driver Framework), the issue often traces back to a USB or chipset driver that can't handle deep sleep.
  5. Enter BIOS and disable Global C-states, then repeat the test. If DPC latency stays flat and audio is clean, you've found the fix.

When C-States Aren't the Problem

A minority of cases have a different root cause. Faulty power supplies have been known to introduce electrical noise that mimics digital pops. GPU driver issues (NVIDIA's DPC latency problems with certain drivers) can also be the real source. If disabling C-states doesn't help, use LatencyMon to identify the offending driver and try rolling it back or updating.

Exclusive audio modes can also conflict. In your audio application, try toggling between ASIO, WASAPI exclusive, and WASAPI shared. Some USB interfaces behave better when Windows isn't mixing multiple streams.

The Future of Low-Latency Audio on Windows

Microsoft's push for modern standby (S0 Low Power Idle) in laptops has intensified the need for smart power management. The Windows Audio team is reportedly working on a new API that could allow applications to request a minimum C-state or DPC budget, but no timeline has been announced. For now, the onus remains on users and system builders to tune their machines.

In the enthusiast community, tools like Process Lasso and ParkControl offer per‑profile configuration, letting you automatically switch between a high‑performance audio mode and a power‑saving default. This hybrid approach is gaining traction among podcasters and live streamers who need their rigs to be both efficient and glitch‑free.

Conclusion: A Small Switch for a Silent Signal

Random audio crackle doesn't have to be a mystery. Before you spend money on a new DAC or a USB isolator, try the free, 10‑second fix of disabling CPU C-states. The improvement in DPC latency can be dramatic, transforming a stuttering nightmare into a smooth, studio‑quality signal. Just keep an eye on your power bill—or your battery icon—and remember that this tweak is easily reversible.

The next time a glitch interrupts your favorite track, dig into your BIOS and tell your CPU to stay awake. Your ears will thank you.