Your USB condenser mic sounds perfect during sound check, then vanishes for a half-second — or several seconds — right in the middle of a stream. Chat hears robotic chopping, Discord shows your mic going gray then green again, and OBS reports the source as active even though no waveform appears. Sometimes the mic comes back on its own, sometimes you have to unplug and replug it to get it recognized again.
If you let this ride, you will lose more than a few words. Most USB microphones that cut out intermittently are dropping power or fighting another app for exclusive control, which means the dropouts will get longer and more frequent until Windows finally flags the device with a USB Device Not Recognized error. Fix it now while the mic is still detected, and you can usually solve it without replacing hardware. The procedure below is tested on current Windows 11 builds shipping in early 2026 and works for popular USB condenser mics from Blue, Elgato, HyperX, Razer, Audio-Technica, and FIFINE.
Likely Causes
| Cause | How to confirm | Fix difficulty |
|---|---|---|
| Windows USB power saving turning the port off | Dropouts happen after 5-15 minutes of talking, mic returns after you stop and start talking. Check Power Options for USB selective suspend enabled. | Easy |
| Weak cable, loose port, or unpowered hub | Wiggling the connector triggers a cutout. Windows makes the USB disconnect sound. Mic is on a front-panel port or hub. | Easy |
| Sample rate or Exclusive Mode conflict | Mic cuts out only when OBS, Discord, and a game are open together. Format in Sound settings does not match OBS sample rate. | Easy |
| Streaming app noise gate or noise suppression set too high | Meter in OBS or Discord drops to zero on soft speech but picks up loud claps. Cutouts do not produce a USB disconnect sound. | Easy |
| Outdated or generic USB audio driver and chipset driver | Device Manager shows mic as USB Audio Device with a 2020 or older driver date. No manufacturer driver listed. | Moderate |
| Electromagnetic interference or high USB gain causing clipping protection | Buzz before the cutout. Mic is next to LED strip power brick or PC case. Gain knob above 75 percent. | Moderate |
Fix 1: Stop Windows From Powering Down the USB Port
What causes it
Windows uses USB selective suspend and per-port power management to save power. For low-current devices like a condenser mic, Windows may suspend the port during quiet moments and fail to wake it fast enough, which sounds like a dropout.
How to check
Press Win + R, type powercfg.cpl and press Enter. Next to your active plan click Change plan settings > Change advanced power settings. Expand USB settings > USB selective suspend setting. If it says Enabled, this fix applies. Also open Device Manager > Universal Serial Bus controllers, right-click each USB Root Hub and Generic USB Hub > Properties > Power Management tab and see if Allow the computer to turn off this device to save power is checked.
What to do
In Advanced power settings, set USB selective suspend setting to Disabled for both On battery and Plugged in, then click Apply. In Device Manager, on the Power Management tab for every USB Root Hub, Generic USB Hub, and USB Input Device that corresponds to your mic, uncheck Allow the computer to turn off this device to save power and click OK. Restart the PC. For good measure, go to Settings > Bluetooth & devices > USB > and turn off USB Battery Saver if the toggle appears.
How to undo it
Return to powercfg.cpl > Change advanced power settings and set USB selective suspend setting back to Enabled. In Device Manager, recheck Allow the computer to turn off this device to save power on each hub.
Fix 2: Rule Out the Cable, Port, and Hub
What causes it
Most USB condenser mics ship with a thin cable and draw close to the 500 mA limit of USB 2.0. A long or damaged cable, a front-panel header with a poor connection, or a bus-powered hub causes voltage sag that resets the mic controller.
How to check
Listen for the Windows disconnect chime when the dropout happens. Open Event Viewer > Windows Logs > System and filter for Source: UsbHub3 or USBHUB3. Look for warnings like Device was not migrated or Port reset failed around the timestamp of the dropout. Physically check if the Type-C or Micro-USB plug wiggles at the mic end.
What to do
Plug the mic directly into a rear USB port on the motherboard, preferably a USB 2.0 port if available, without any extension, adapter, or hub. Use the shortest cable that came with the mic, or a known-good shielded cable under 6 feet (2 meters) that supports data, not charge-only. If you must use a hub, use a powered hub with its own AC adapter rated at 12V 2A or higher. Avoid running the mic cable parallel to power bricks, monitors, or LED power supplies. Press Win + Ctrl + Shift + B is not needed; just reseat the cable firmly at both ends.
How to undo it
Move the cable back to its original port or hub. No software setting changes to revert.
Fix 3: Lock Sample Rate and Disable Exclusive Mode
What causes it
When Windows, OBS Studio, and Discord each request a different sample rate, the Windows Audio Engine resamples on the fly and one app can claim Exclusive Mode, which mutes the mic for all other apps and appears as a cutout.
How to check
Right-click the speaker icon > Sound settings > More sound settings > Recording tab. Double-click your USB mic > Advanced tab. Note the Default Format, for example 2 channel, 16 bit, 48000 Hz. In OBS Studio go to Settings > Audio > General and note Sample Rate. In Discord, there is no sample rate control, but Discord will try 48000 Hz by default. If formats differ, or if both Allow applications to take exclusive control is checked, you have a conflict.
What to do
In Sound > Recording > your mic > Advanced, set Default Format to 1 channel, 16 bit, 48000 Hz (or 24 bit, 48000 Hz if the mic supports it). Uncheck both Allow applications to take exclusive control of this device and Give exclusive mode applications priority. Click Apply. In the Playback tab, do the same for your headphones or speakers to prevent shared-mode switching. In OBS Studio > Settings > Audio set Sample Rate to 48 kHz. Restart OBS and Discord. In Windows Settings > System > Sound > Volume mixer, ensure the mic Input device is set to your USB mic and not Default.
How to undo it
Return to Sound > Recording > Advanced and set Default Format back to its previous value, typically 1 channel, 16 bit, 44100 Hz, and recheck both Exclusive Mode boxes if you need them for a DAW.
Fix 4: Turn Off Aggressive Noise Gates and Suppression
What causes it
OBS noise gates, Discord Krisp or Noise Suppression, and NVIDIA Broadcast all gate or mute the mic when they think you are silent. If the close threshold is too high or suppression is too aggressive, quiet consonants and endings are mistaken for noise and cut off.
How to check
In OBS Studio, click the gear on your Mic/Aux source > Filters. If Noise Gate, Noise Suppression, or NVIDIA Noise Removal is listed, note the thresholds. Keep talking at a normal low volume and watch the OBS audio mixer meter. If the meter collapses to -inf dB while you are still speaking softly, the gate is too aggressive. In Discord > Settings > Voice & Video > Advanced, see if Noise Suppression is set to Krisp or Standard and if Noise Reduction is toggled on.
What to do
In OBS, edit Noise Gate and set Close Threshold to -50 dB to -55 dB, Open Threshold to -45 dB to -50 dB, Attack Time 25 ms, Hold Time 200 ms, Release Time 150 ms. Or disable the filter entirely to test. Set Noise Suppression to RNNoise rather than Speex if you need some suppression, and keep it at the lowest level. In Discord > Settings > Voice & Video, set Noise Suppression to None for testing, disable Noise Reduction and Echo Cancellation, and turn off Automatically determine input sensitivity, then manually set the slider so your quiet speech still lights up the indicator. In NVIDIA Broadcast, reduce Noise Removal Strength to under 50 or bypass it.
How to undo it
Re-enable your previous Filters in OBS and set Discord Noise Suppression back to Standard or Krisp. Restore original gate thresholds.
Fix 5: Reinstall USB and Audio Drivers
What causes it
A generic Microsoft USB Audio 2.0 driver from an older Windows install or a missing motherboard chipset driver mishandles isochronous USB audio packets, causing dropouts under load while streaming.
How to check
Open Device Manager > Sound, video and game controllers > right-click your mic > Properties > Driver tab. Check Driver Provider and Driver Date. If Provider is Microsoft and Date is older than one year, or if Device status says This device is working properly but Events shows Device install requested, you should update. Also check Device Manager > Universal Serial Bus controllers for any yellow warning icon.
What to do
Disconnect the mic. Download the latest chipset driver package from your motherboard vendor support page, such as AMD Chipset Driver or Intel Chipset Device Software and Intel ME, and install it, then restart. Reconnect the mic to a rear port. In Device Manager, right-click your mic > Uninstall device > check Attempt to remove the driver for this device if shown > Uninstall. Unplug the mic for 10 seconds, plug it back in, and let Windows install USB Audio Device automatically. Avoid third-party driver updaters. If your mic vendor provides a dedicated driver or firmware tool, such as Elgato Wave Link or HyperX NGENUITY, install it from the vendor site and check for firmware updates.
How to undo it
In Device Manager > mic Properties > Driver tab, click Roll Back Driver if available. Or download the previous chipset driver version from the vendor download archive and reinstall it. Windows will also reinstall the prior USB Audio driver on next plug-in.
Fix 6: Lower Gain and Move Away From Interference
What causes it
Running the analog gain knob at maximum makes the mic capsule clip on plosives and loud laughs. Some USB condenser designs briefly mute or reset the analog-to-digital converter when clipping is sustained. Nearby electromagnetic interference from a PC, monitor power supply, or RGB controller adds a high-pitched whine that triggers that protection.
How to check
Open Settings > System > Sound > Input > your mic > Input volume. Speak at your loudest stream voice while watching the test bar. If it hits 100 percent and stays pinned, gain is too high. Listen on headphones directly from the mic if it has a monitor jack. If you hear buzz that changes when you move the cable, interference is likely.
What to do
Set the physical gain knob to the 9 to 11 o’clock position, roughly 40 to 60 percent, then set Windows Input volume to 75 to 85 so peaks hit around 75 to 85 percent on the test bar, not 100. In Sound > Recording > mic > Levels, aim for 70 to 85. Keep the mic at least 12 inches from power bricks, power strips, and the side panel of the PC. Use a cable with a ferrite bead or add a snap-on ferrite core near the PC end. Switch the mic polar pattern to Cardioid if it has a pattern switch, and use a windscreen or pop filter to reduce plosive spikes.
How to undo it
Turn the gain knob back up and raise Input volume to the previous value. Remove the ferrite core if you added one.
Fix 7: Fix Conflicting Software and Background Access
What causes it
Two apps that both control the mic, such as OBS, Discord, Wave Link, SteelSeries Sonar, or Voicemeeter Virtual Mixer, can start and stop the audio stream repeatedly, which OBS shows as intermittent audio packets dropped.
How to check
Press Ctrl + Shift + Esc to open Task Manager > Startup and Processes. Look for multiple audio mixers running: WavLink, Sonar, Voicemeeter Engine, NVIDIA Broadcast, RTX Voice, or similar. In OBS > View > Logs > Show Log Files, open the latest log and search for WASAPI and device disconnected. In Settings > Privacy & security > Microphone, see which apps recently accessed the microphone under Recent activity.
What to do
Choose one mixer as your primary. If you use OBS, let OBS control the mic directly and close Wave Link or Sonar for testing, or route the mic through one virtual device only. In Settings > Privacy & security > Microphone, make sure Microphone access and Let apps access your microphone are On, then leave only OBS, Discord, and your mixer enabled. In Discord > Settings > Voice & Video > Audio Subsystem, try Standard instead of Experimental. Restart all audio apps: close them completely from the system tray, then launch your mixer first, then Discord, then OBS last. In OBS, remove and re-add the Audio Input Capture source: Sources > plus > Audio Input Capture > select your mic > Device set to your specific mic name, not Default.
How to undo it
Re-enable the apps you disabled in Privacy & security > Microphone and in Startup. In OBS, revert Audio Subsystem changes in Discord and re-add previous Filters.
If Nothing Works
Test the mic on a different PC or laptop with a rear port and no hub for at least 30 minutes of continuous recording in Voice Recorder or Audacity. If it still cuts out there with a different cable, the mic itself is likely faulty and should be returned under warranty. If it works fine on the second PC, the issue is isolated to your main PC. At that point, run Settings > System > Troubleshoot > Other troubleshooters > Recording Audio > Run, reset Windows audio services by pressing Win + R, typing services.msc, restarting Windows Audio and Windows Audio Endpoint Builder, and checking the file C:\Windows\Inf\setupapi.dev.log for repeated device install failures near the dropout time. A clean Windows user profile or a BIOS update that improves USB stability is the last software step before replacing the motherboard USB header or adding a PCI-e USB expansion card.
FAQ
Why does my USB condenser mic cut out only when I stream or game?
Games and streaming push CPU and USB bandwidth higher and wake exclusive-mode requests. If your Default Format is 44100 Hz while OBS is set to 48000 Hz, or if selective suspend is enabled, the conflict only appears under that load. Lock both to 48000 Hz, disable exclusive mode, and disable selective suspend to remove the load-dependent trigger.
Should I use a USB 3.0 port for my mic?
Not necessarily. Most condenser mics are USB 2.0 audio devices and are more stable on USB 2.0 ports, which often have separate power regulation and less sharing with high-speed devices. Use a rear USB 2.0 port directly on the motherboard for testing. Only move to USB 3.0 if you have no USB 2.0 ports free and the mic stays stable there without a hub.
Will a powered USB hub fix cutting out?
A powered hub can help if the root cause is voltage drop on a front-panel header or an unpowered hub, but it adds another controller that can cause latency or selective suspend. Direct rear motherboard connection is always preferred. Only add a powered hub with its own AC adapter if you need distance or have no free rear ports, and disable power saving for that hub in Device Manager.
Does 16-bit vs 24-bit matter for dropouts?
Bit depth rarely causes dropouts directly, but mismatched depth between Windows and your DAW or OBS can force resampling that stutters under load. Keep Windows Sound > Advanced Default Format and OBS Settings > Audio Sample Rate aligned at 48000 Hz. Use 16-bit unless your mic and editing workflow specifically require 24-bit, and apply the same format everywhere.
