You’re mid-stream, the game audio is fine on your end, then your chat starts spamming that your mic or game sound is “frying” — bursts of static, robotic stutters, or pops that come and go. If you’re running an audio interface into OBS or Streamlabs Desktop and hearing crackle, you’re dealing with buffer underruns: your computer isn’t feeding audio samples to (or pulling them from) the interface fast enough, or something electrical is polluting the signal. The symptom usually shows up in one of three places: in your headphones directly, in your recording, or only for your viewers — and figuring out which one is the first diagnostic step, because it tells you where in the chain the problem lives.
How urgent is it? Your hardware almost certainly isn’t damaged, so there’s no panic. But crackling on a stream is audience-hostile: viewers will leave over audio long before they leave over video quality, and it tends to get worse as your scene collection grows and CPU load climbs. Most cases are fixable in under 30 minutes with settings changes alone, so treat this as a high-priority but low-difficulty task. Work through the fixes below in order — they’re sorted easiest-first, and the majority of streamers find their culprit in the first three.
Likely Causes
| Cause | How to confirm | Fix difficulty |
|---|---|---|
| USB buffer too small / sample rate mismatch | Crackle gets worse under CPU load; interface control panel shows a small buffer (32–64 samples) | Easy |
| Windows power plan throttling USB | Crackle appears only when the PC is idle or on battery; disappears under sustained load | Easy |
| USB port or hub sharing bandwidth | Moving the interface to a different port changes or eliminates the crackle | Easy |
| DPC latency from network, GPU, or chipset drivers | LatencyMon shows a single driver spiking above 1000 µs | Moderate |
| Ground loop / electrical noise | Crackle or hum is constant regardless of PC load, and changes when you touch a metal part of the case or unplug the mic’s power | Moderate |
| Overloaded USB controller or failing cable | Crackle correlates with webcam or capture card activity; wiggling the cable changes it | Moderate to hard |
Fix 1: Match Sample Rates Everywhere
What causes it
When Windows, your interface’s driver panel, and OBS disagree on sample rate — say Windows runs 48 kHz while the interface panel is set to 44.1 kHz — the system resamples on the fly, which produces periodic clicks and crackles, often at regular intervals.
How to check
Right-click the speaker icon in the taskbar, choose Sound settings, then open More sound settings (or Sound Control Panel). Under the Playback tab, select your interface, click Properties, then the Advanced tab, and note the “Default Format.” Do the same for the interface on the Recording tab. Then open your interface’s own control panel app (Focusrite Control 2, Universal Control, MOTU Pro Audio, etc.) and compare. Finally, check OBS: Settings, Audio, Sample Rate.
What to do
Set everything to 48 kHz. Streaming video containers and most game engines natively use 48 kHz, so avoid 44.1 kHz entirely. In Windows’ Advanced tabs, pick “24 bit, 48000 Hz” for both playback and recording. Set the OBS audio sample rate to 48 kHz and restart OBS when it prompts you.
How to undo it
Reopen the same menus and restore whatever values were there before. Nothing else on your system is affected by this change.
Fix 2: Raise the Interface Buffer Size
What causes it
Buffer size determines how many milliseconds of audio the driver holds before handing it to hardware. A 32-sample buffer at 48 kHz is under 1 ms of headroom; any CPU spike overruns it and you hear crackle. Interface drivers are often installed with aggressive defaults because low latency matters for recording instruments — but streaming with monitoring in headphones rarely needs it.
How to check
Open your interface’s control panel and look for “Buffer Size,” “ASIO Buffer,” or a latency readout. Anything at or below 64 samples is a likely culprit for a streaming workload.
What to do
Raise the buffer to 256 samples and test. If crackle persists, go to 512. Streaming adds 2+ seconds of buffering to your output anyway, so even 512 samples (~10.6 ms) of input latency is imperceptible to your audience and barely noticeable in your own headphones. If you play a virtual instrument live on stream, drop back to 128 as a compromise.
How to undo it
Set the buffer back to its previous value in the same control panel. Some interfaces (like older Focusrite Scarlett units) fix the buffer in the driver rather than a panel app — for those, you may need to reinstall the driver and choose a different latency setting during installation.
Fix 3: Change USB Power Management and Power Plan
What causes it
Windows aggressively suspends USB devices and parks CPU cores to save power. When a core wakes too slowly or the USB hub takes a moment to resume, the audio stream starves. This is especially common on systems that crackle when “idle” but behave under full gaming load.
How to check
Open Device Manager (right-click Start, choose Device Manager), expand Universal Serial Bus controllers, double-click each “USB Root Hub” and Generic USB Hub, and look at the Power Management tab. If “Allow the computer to turn off this device to save power” is checked, Windows may be suspending your interface’s hub.
What to do
Uncheck “Allow the computer to turn off this device” on every USB Root Hub and Generic USB Hub entry. Then open Control Panel, go to Power Options, select “High performance” (or click Change plan settings, Change advanced power settings, expand USB settings, USB selective suspend setting, and set it to Disabled). On laptops, do this for both battery and plugged-in profiles.
How to undo it
Re-check the boxes and restore the Balanced power plan. Expect slightly higher idle power draw, which is why this isn’t the Windows default.
Fix 4: Move the Interface to a Different USB Port
What causes it
USB 3 ports generate electrical interference in the 2.4 GHz range and can share a controller with other devices. Webcams, capture cards, and external drives on the same root hub compete for bandwidth, and a shared controller can miss audio transfer deadlines. Front-panel ports are often wired through extra internal cabling and hubs, making them worse than motherboard rear I/O.
How to check
Note where the interface is plugged in, then move it to a USB 2.0 port directly on the motherboard’s rear panel — most audio interfaces are USB 2 devices regardless of what the port supports, and the audio data rate is trivial. Test whether the crackle changes. Also unplug non-essential USB devices (USB lighting, extra hubs) one at a time while streaming a test recording.
What to do
Keep the interface on the rear motherboard port that produced clean audio — usually a dedicated USB 2.0 port away from where your capture card and webcam are clustered. Never run the interface through a monitor’s USB passthrough or an unpowered hub.
How to undo it
Plug it back into the original port. If the original port turns out to be the problem long-term, a PCIe USB expansion card (choose one with its own controller chip) is the durable fix.
Fix 5: Diagnose and Tame DPC Latency
What causes it
Deferred Procedure Calls are Windows kernel tasks that, when slow, block the audio driver from running on time. The usual offenders are Wi-Fi and network drivers (killer combination with streaming, which hammers the NIC), GPU drivers, and power management on storage controllers.
How to check
Download the free LatencyMon utility, run it while doing a mock stream for 10 minutes, and check the Drivers tab. Sort by “Highest execution time.” Any driver routinely exceeding 1000 µs is a suspect — common names include ndis.sys (networking), nvlddmkm.sys or amdkmdag.sys (GPU), and storport.sys (storage).
What to do
If ndis.sys is the offender and you stream over Ethernet, update your LAN driver from the motherboard vendor’s site rather than Windows Update. If Wi-Fi is the offender, switching to wired Ethernet frequently eliminates the problem outright. For GPU drivers, do a clean install using the vendor’s app with the “factory reset” option. Update your motherboard’s chipset driver from the manufacturer’s support page. In Windows, you can also disable “Global C-States” or analogous idle power states in BIOS if LatencyMon shows massive idle-time spikes — check your motherboard manual for the exact setting name.
How to undo it
Roll back drivers via Device Manager (right-click the device, Properties, Driver tab, Roll Back Driver) or restore the previous BIOS setting. Driver rollbacks are always available if the new driver misbehaves.
Fix 6: Eliminate Ground Loop Hum and Electrical Noise
What causes it
If your interface connects to other mains-powered gear (a PC, an audio mixer, powered monitors) on different electrical circuits, small potential differences between grounds inject noise into the signal. This sounds like a steady 60 Hz hum with fizzing on top rather than load-dependent crackle.
How to check
Play audio through the interface and listen: does the noise persist even when the PC is doing nothing? Unplug the interface’s USB cable — if the noise vanishes, it’s coming down the USB path, not through your mic preamp. Temporarily power the PC setup and any speakers from the same wall outlet strip (using a proper surge protector, never by defeating the ground pin) and see if the noise disappears.
What to do
Put all powered audio equipment on one power strip or one wall circuit. If the interface has a ground lift switch, flip it. For stubborn cases, a USB isolator between the PC and interface breaks the ground path entirely. Also route audio cables away from parallel power cables, especially behind the desk.
How to undo it
Unflip the ground lift, remove the isolator, and re-route cables as they were. There’s no software component to this fix.
Fix 7: Adjust OBS Audio Settings and Monitor Path
What causes it
OBS’s audio encoder and monitoring can contribute crackle if the CPU can’t keep up, or if a plugin (VST filters like noise suppression or compressor chains) stalls the audio thread. Viewers-only crackle with clean local monitoring points at the encoder; crackle in your headphones too points upstream.
How to check
Determine the crackle’s location: record a short clip locally and listen, watch your own stream from another device, and listen with headphones directly on the interface. Then strip down your audio: in OBS, open the filter chain on your mic source (right-click the source, Filters) and disable all VST plugins one at a time.
What to do
First, try the OBS “Audio Monitoring” device setting: Settings, Audio, and set Monitoring Device explicitly to your interface rather than Default. If crackle persists only on stream, raise the encoder: in Settings, Output, use a hardware encoder (NVENC, AMF, or QuickSync) so audio processing doesn’t queue behind video. If a specific VST is the trigger, replace it with a lighter alternative or raise the process priority of OBS’s audio path — OBS 30 and later handle audio in a dedicated thread, but heavy filter chains still matter.
How to undo it
Re-enable your filters, restore “Default” monitoring, and switch the encoder back. Keep a screenshot of your filter list before making changes so you can restore it exactly.
Fix 8: Update or Replace the Interface Driver
What causes it
Vendor drivers get updated for exactly these kinds of bugs — new Windows builds and new chipset generations routinely break older driver releases. A stale driver that worked on your previous motherboard can crackle on a new one.
How to check
Compare your installed driver version (Device Manager, right-click the interface under Sound, video and game controllers, Properties, Driver tab) against the current version on the manufacturer’s support page for your exact model. Also check whether your model has graduated to a newer driver architecture — several manufacturers shipped major driver rewrites for Windows 11 24H2 and later.
What to do
Download the current driver from the manufacturer’s site, run the installer, and reboot when prompted. If the newest driver is the cause of the problem rather than the cure, install the previous version instead — manufacturers typically keep a driver archive page. Perform a restart (not just a fast-startup shutdown) after installing: open Start, hold Shift, and click Restart to bypass Fast Startup’s driver caching.
How to undo it
Reinstall the previous driver package from the archive, or use Device Manager’s Roll Back Driver option within the rollback window.
If Nothing Works
At this point, isolate hardware methodically. Test the interface on a completely different computer — if it crackles there too, the unit or its cable is faulty, and contacting the manufacturer’s support (most major brands offer two- to three-year warranties) is the right move. If it’s clean on another machine, the problem is your PC: try a PCIe USB expansion card on a controller the interface hasn’t used, test with a different USB cable (short, shielded, no extensions), and as a last resort do a clean Windows install on a spare drive to rule out deep software conflicts. Also test with a different DAW or recording app like Audacity running at the same buffer settings — if Audacity is clean while OBS crackles, you’ve narrowed it to OBS’s configuration rather than the interface, and rebuilding your scene collection from scratch usually resolves it. Between the settings fixes above and this isolation process, essentially every persistent crackle case gets solved; genuine hardware failure in modern interfaces is rare.
FAQ
Why does my audio interface only crackle when I’m streaming and not when I record?
Streaming adds CPU load from the encoder plus network traffic, both of which compete with your audio driver for CPU time. Recording locally with the same scene collection is a good test — if local recording is clean but going live crackles, the network driver DPC issue in Fix 5 or encoder load in Fix 7 is almost certainly your cause.
Does a more expensive audio interface fix crackling?
Rarely. Crackling is overwhelmingly a configuration, driver, or system-level issue, not a hardware quality issue. A well-configured budget interface is silent; a misconfigured flagship interface crackles. Spend money on a PCIe USB card or better cabling before replacing the interface.
Should I use ASIO or WDM in OBS for my interface?
Either can work, but they behave differently. ASIO bypasses the Windows audio mixer and gives you lower latency plus direct buffer control, but a buggy ASIO driver can crackle where the standard Windows path is fine. If crackle started after a driver update, try switching OBS to the regular MME or WDM input for the same device and compare — it’s a 10-second test that often solves it.
Can a USB hub cause audio interface crackling?
Yes, especially unpowered hubs and monitor passthrough ports. Even powered hubs can share a single upstream controller with high-bandwidth devices like webcams. Whenever possible, plug the interface directly into a rear motherboard USB port. If you must use a hub, use a self-powered one and keep the interface on it alone.
