Audio issue detected, intermittent glitches observed.

K

Killerman1834

01-25-2026, 02:13 PM #1

On any applications that use voice chat (so far tested discord and VRChat), people's mics will often make popping sounds and sometimes just cut out for a second, shown by their icon stops lighting up, and then coming back, making a pretty bad popping sound. Popping sounds also occur when this doesn't happen. I have built a completely new computer except for my GPU, but I even tried out my friends GPU as well with the new build. I have also tried dual booting Windows 10, as well as contacting my ISP and asking if they see any issues on their side or with my connection, which they said no.
I have tried multiple different Nvidia drivers, I have reinstalled all my motherboard/sound/LAN/etc. drivers multiple times, even trying generic Windows audio drivers. I have tried multiple audio outputs but that shouldn't even matter because I can screen record the issue in Windows. My headphones even have a DAC but that doesn't help.
I've tried different Bios tweaks, Windows power settings, etc. I've tried both Ethernet and wireless internet connection. I've changed my page file minimums and maximums. I've run event viewer, wireshark, latencymon, process lasso. I honestly don't know what to do at this point. I can send my latencymon report from the other night and some videos showing my issue.
I've been dealing with this for 2 months and nobody knows how to fix it. I've tried a bunch of other fixes over the course as well but I can't remember at this time; I've tried DESPERATELY to fix this. I even took my old PC that had this issue to my friends house and it still had the same issue. I do not have issues with spotify at all. Tested twitch and youtube it all seemed fine. Game audio is fine too, just not peoples mics. I've tried Cloudflare WARP and a vpn as well.
Edit(s):
New video clearly displaying the difference of my game and my friends game. We recorded the same conversation between people and there is a clear distinction of the audio issue I am having:
View: https://youtu.be/jVgerxgTrKI
Specs:
GPU: Asus TUF 4090
CPU: Ryzen 9950X3D
Mobo: ROG X870E-H
SSD: 2 x 2TB Samsung 990 NVMe
RAM: 64GB DDR5 6400mhz (set to 6000mhz)
View: https://youtu.be/TPpGrE3spyI
View: https://youtu.be/zuDzUY-7XXc
View: https://youtu.be/5Zx8uBPO6VU
View: https://youtu.be/qqLrXhDY6eE
View: https://youtu.be/vTFznQflBD8
LatencyMon Report:
_________________________________________________________________________________________________________CONCLUSION_________________________________________________________________________________________________________Your system seems to be having difficulty handling real-time audio and other tasks. You may experience drop outs, clicks or pops due to buffer underruns. One or more DPC routines that belong to a driver running in your system appear to be executing for too long. One problem may be related to power management, disable CPU throttling settings in Control Panel and BIOS setup. Check for BIOS updates. LatencyMon has been analyzing your system for 0:37:14 (h:mm Confused s) on all processors._________________________________________________________________________________________________________SYSTEM INFORMATION_________________________________________________________________________________________________________Computer name: SCP-079OS version: Windows 11, 10.0, version 2009, build: 26200 (x64)Hardware: System Product Name, ASUSBIOS: 1804CPU: AuthenticAMD AMD Ryzen 9 9950X3D 16-Core Processor Logical processors: 32Processor groups: 1Processor group size: 32RAM: 63120 MB total_________________________________________________________________________________________________________CPU SPEED_________________________________________________________________________________________________________Reported CPU speed (WMI): 430 MHzReported CPU speed (registry): 430 MHzNote: reported execution times may be calculated based on a fixed reported CPU speed. Disable variable speed settings like Intel Speed Step and AMD Cool N Quiet in the BIOS setup for more accurate results._________________________________________________________________________________________________________MEASURED INTERRUPT TO USER PROCESS LATENCIES_________________________________________________________________________________________________________The interrupt to process latency reflects the measured interval that a usermode process needed to respond to a hardware request from the moment the interrupt service routine started execution. This includes the scheduling and execution of a DPC routine, the signaling of an event and the waking up of a usermode thread from an idle wait state in response to that event.Highest measured interrupt to process latency (µs): 769.10Average measured interrupt to process latency (µs): 11.625032Highest measured interrupt to DPC latency (µs): 760.50Average measured interrupt to DPC latency (µs): 6.139676_________________________________________________________________________________________________________ REPORTED ISRs_________________________________________________________________________________________________________Interrupt service routines are routines installed by the OS and device drivers that execute in response to a hardware interrupt signal.Highest ISR routine execution time (µs): 80.980Driver with highest ISR routine execution time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft CorporationHighest reported total ISR routine time (%): 0.002463Driver with highest ISR total time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft CorporationTotal time spent in ISRs (%) 0.002577ISR count (execution time <250 µs): 2804819ISR count (execution time 250-500 µs): 0ISR count (execution time 500-1000 µs): 0ISR count (execution time 1000-2000 µs): 0ISR count (execution time 2000-4000 µs): 0ISR count (execution time >=4000 µs): 0_________________________________________________________________________________________________________REPORTED DPCs_________________________________________________________________________________________________________DPC routines are part of the interrupt servicing dispatch mechanism and disable the possibility for a process to utilize the CPU while it is interrupted until the DPC has finished execution.Highest DPC routine execution time (µs): 1323.710Driver with highest DPC routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft CorporationHighest reported total DPC routine time (%): 0.056283Driver with highest DPC total execution time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft CorporationTotal time spent in DPCs (%) 0.154295DPC count (execution time <250 µs): 10927308DPC count (execution time 250-500 µs): 0DPC count (execution time 500-10000 µs): 34DPC count (execution time 1000-2000 µs): 6DPC count (execution time 2000-4000 µs): 0DPC count (execution time >=4000 µs): 0_________________________________________________________________________________________________________ REPORTED HARD PAGEFAULTS_________________________________________________________________________________________________________Hard pagefaults are events that get triggered by making use of virtual memory that is not resident in RAM but backed by a memory mapped file on disk. The process of resolving the hard pagefault requires reading in the memory from disk while the process is interrupted and blocked from execution.NOTE: some processes were hit by hard pagefaults. If these were programs producing audio, they are likely to interrupt the audio stream resulting in dropouts, clicks and pops. Check the Processes tab to see which programs were hit.Process with highest pagefault count: vrchat.exeTotal number of hard pagefaults 43120Hard pagefault count of hardest hit process: 42552Number of processes hit: 21_________________________________________________________________________________________________________ PER CPU DATA_________________________________________________________________________________________________________CPU 0 Interrupt cycle time (s): 255.450929CPU 0 ISR highest execution time (µs): 80.980CPU 0 ISR total execution time (s): 0.53910CPU 0 ISR count: 781486CPU 0 DPC highest execution time (µs): 1323.710CPU 0 DPC total execution time (s): 72.887012CPU 0 DPC count: 8328556_________________________________________________________________________________________________________CPU 1 Interrupt cycle time (s): 111.267943CPU 1 ISR highest execution time (µs): 30.870CPU 1 ISR total execution time (s): 1.300952CPU 1 ISR count: 2020029CPU 1 DPC highest execution time (µs): 500.730CPU 1 DPC total execution time (s): 35.668261CPU 1 DPC count: 2166251_________________________________________________________________________________________________________CPU 2 Interrupt cycle time (s): 18.950642CPU 2 ISR highest execution time (µs): 23.690CPU 2 ISR total execution time (s): 0.002675CPU 2 ISR count: 3304CPU 2 DPC highest execution time (µs): 501.40CPU 2 DPC total execution time (s): 0.111434CPU 2 DPC count: 32954_________________________________________________________________________________________________________CPU 3 Interrupt cycle time (s): 19.868649CPU 3 ISR highest execution time (µs): 0.0CPU 3 ISR total execution time (s): 0.0CPU 3 ISR count: 0CPU 3 DPC highest execution time (µs): 421.420CPU 3 DPC total execution time (s): 0.098259CPU 3 DPC count: 29850_________________________________________________________________________________________________________CPU 4 Interrupt cycle time (s): 18.145457CPU 4 ISR highest execution time (µs): 0.0CPU 4 ISR total execution time (s): 0.0CPU 4 ISR count: 0CPU 4 DPC highest execution time (µs): 498.760CPU 4 DPC total execution time (s): 0.110460CPU 4 DPC count: 33121_________________________________________________________________________________________________________CPU 5 Interrupt cycle time (s): 17.209934CPU 5 ISR highest execution time (µs): 0.0CPU 5 ISR total execution time (s): 0.0CPU 5 ISR count: 0CPU 5 DPC highest execution time (µs): 96.850CPU 5 DPC total execution time (s): 0.113018CPU 5 DPC count: 36633_________________________________________________________________________________________________________CPU 6 Interrupt cycle time (s): 15.661911CPU 6 ISR highest execution time (µs): 0.0CPU 6 ISR total execution time (s): 0.0CPU 6 ISR count: 0CPU 6 DPC highest execution time (µs): 131.490CPU 6 DPC total execution time (s): 0.132458CPU 6 DPC count: 38541_________________________________________________________________________________________________________CPU 7 Interrupt cycle time (s): 15.548052CPU 7 ISR highest execution time (µs): 0.0CPU 7 ISR total execution time (s): 0.0CPU 7 ISR count: 0CPU 7 DPC highest execution time (µs): 416.80CPU 7 DPC total execution time (s): 0.128562CPU 7 DPC count: 38585_________________________________________________________________________________________________________CPU 8 Interrupt cycle time (s): 18.305371CPU 8 ISR highest execution time (µs): 0.0CPU 8 ISR total execution time (s): 0.0CPU 8 ISR count: 0CPU 8 DPC highest execution time (µs): 116.260CPU 8 DPC total execution time (s): 0.159211CPU 8 DPC count: 39753_________________________________________________________________________________________________________CPU 9 Interrupt cycle time (s): 18.355337CPU 9 ISR highest execution time (µs): 0.0CPU 9 ISR total execution time (s): 0.0CPU 9 ISR count: 0CPU 9 DPC highest execution time (µs): 131.990CPU 9 DPC total execution time (s): 0.188940CPU 9 DPC count: 49086_________________________________________________________________________________________________________CPU 10 Interrupt cycle time (s): 19.385013CPU 10 ISR highest execution time (µs): 0.0CPU 10 ISR total execution time (s): 0.0CPU 10 ISR count: 0CPU 10 DPC highest execution time (µs): 443.50CPU 10 DPC total execution time (s): 0.075587CPU 10 DPC count: 16560_________________________________________________________________________________________________________CPU 11 Interrupt cycle time (s): 19.523611CPU 11 ISR highest execution time (µs): 0.0CPU 11 ISR total execution time (s): 0.0CPU 11 ISR count: 0CPU 11 DPC highest execution time (µs): 122.770CPU 11 DPC total execution time (s): 0.081860CPU 11 DPC count: 19185_________________________________________________________________________________________________________CPU 12 Interrupt cycle time (s): 19.736356CPU 12 ISR highest execution time (µs): 0.0CPU 12 ISR total execution time (s): 0.0CPU 12 ISR count: 0CPU 12 DPC highest execution time (µs): 122.440CPU 12 DPC total execution time (s): 0.068951CPU 12 DPC count: 12837_________________________________________________________________________________________________________CPU 13 Interrupt cycle time (s): 19.935322CPU 13 ISR highest execution time (µs): 0.0CPU 13 ISR total execution time (s): 0.0CPU 13 ISR count: 0CPU 13 DPC highest execution time (µs): 168.420CPU 13 DPC total execution time (s): 0.078943CPU 13 DPC count: 15060_________________________________________________________________________________________________________CPU 14 Interrupt cycle time (s): 19.706024CPU 14 ISR highest execution time (µs): 0.0CPU 14 ISR total execution time (s): 0.0CPU 14 ISR count: 0CPU 14 DPC highest execution time (µs): 151.450CPU 14 DPC total execution time (s): 0.077257CPU 14 DPC count: 9260_________________________________________________________________________________________________________CPU 15 Interrupt cycle time (s): 20.222213CPU 15 ISR highest execution time (µs): 0.0CPU 15 ISR total execution time (s): 0.0CPU 15 ISR count: 0CPU 15 DPC highest execution time (µs): 149.560CPU 15 DPC total execution time (s): 0.109990CPU 15 DPC count: 11827_________________________________________________________________________________________________________CPU 16 Interrupt cycle time (s): 2.509777CPU 16 ISR highest execution time (µs): 0.0CPU 16 ISR total execution time (s): 0.0CPU 16 ISR count: 0CPU 16 DPC highest execution time (µs): 42.740CPU 16 DPC total execution time (s): 0.009770CPU 16 DPC count: 2265_________________________________________________________________________________________________________CPU 17 Interrupt cycle time (s): 2.349135CPU 17 ISR highest execution time (µs): 0.0CPU 17 ISR total execution time (s): 0.0CPU 17 ISR count: 0CPU 17 DPC highest execution time (µs): 42.190CPU 17 DPC total execution time (s): 0.002533CPU 17 DPC count: 519_________________________________________________________________________________________________________CPU 18 Interrupt cycle time (s): 2.639950CPU 18 ISR highest execution time (µs): 0.0CPU 18 ISR total execution time (s): 0.0CPU 18 ISR count: 0CPU 18 DPC highest execution time (µs): 60.830CPU 18 DPC total execution time (s): 0.028742CPU 18 DPC count: 7165_________________________________________________________________________________________________________CPU 19 Interrupt cycle time (s): 2.452921CPU 19 ISR highest execution time (µs): 0.0CPU 19 ISR total execution time (s): 0.0CPU 19 ISR count: 0CPU 19 DPC highest execution time (µs): 69.620CPU 19 DPC total execution time (s): 0.004630CPU 19 DPC count: 1357_________________________________________________________________________________________________________CPU 20 Interrupt cycle time (s): 2.226619CPU 20 ISR highest execution time (µs): 0.0CPU 20 ISR total execution time (s): 0.0CPU 20 ISR count: 0CPU 20 DPC highest execution time (µs): 110.20CPU 20 DPC total execution time (s): 0.015453CPU 20 DPC count: 3580_________________________________________________________________________________________________________CPU 21 Interrupt cycle time (s): 2.304537CPU 21 ISR highest execution time (µs): 0.0CPU 21 ISR total execution time (s): 0.0CPU 21 ISR count: 0CPU 21 DPC highest execution time (µs): 103.040CPU 21 DPC total execution time (s): 0.013336CPU 21 DPC count: 3690_________________________________________________________________________________________________________CPU 22 Interrupt cycle time (s): 2.249564CPU 22 ISR highest execution time (µs): 0.0CPU 22 ISR total execution time (s): 0.0CPU 22 ISR count: 0CPU 22 DPC highest execution time (µs): 83.590CPU 22 DPC total execution time (s): 0.005156CPU 22 DPC count: 1169_________________________________________________________________________________________________________CPU 23 Interrupt cycle time (s): 2.178930CPU 23 ISR highest execution time (µs): 0.0CPU 23 ISR total execution time (s): 0.0CPU 23 ISR count: 0CPU 23 DPC highest execution time (µs): 109.710CPU 23 DPC total execution time (s): 0.001188CPU 23 DPC count: 262_________________________________________________________________________________________________________CPU 24 Interrupt cycle time (s): 2.591746CPU 24 ISR highest execution time (µs): 0.0CPU 24 ISR total execution time (s): 0.0CPU 24 ISR count: 0CPU 24 DPC highest execution time (µs): 120.960CPU 24 DPC total execution time (s): 0.034582CPU 24 DPC count: 8569_________________________________________________________________________________________________________CPU 25 Interrupt cycle time (s): 2.438580CPU 25 ISR highest execution time (µs): 0.0CPU 25 ISR total execution time (s): 0.0CPU 25 ISR count: 0CPU 25 DPC highest execution time (µs): 96.760CPU 25 DPC total execution time (s): 0.027011CPU 25 DPC count: 3868_________________________________________________________________________________________________________CPU 26 Interrupt cycle time (s): 2.680894CPU 26 ISR highest execution time (µs): 0.0CPU 26 ISR total execution time (s): 0.0CPU 26 ISR count: 0CPU 26 DPC highest execution time (µs): 118.510CPU 26 DPC total execution time (s): 0.059311CPU 26 DPC count: 11738_________________________________________________________________________________________________________CPU 27 Interrupt cycle time (s): 2.665433CPU 27 ISR highest execution time (µs): 0.0CPU 27 ISR total execution time (s): 0.0CPU 27 ISR count: 0CPU 27 DPC highest execution time (µs): 104.860CPU 27 DPC total execution time (s): 0.024028CPU 27 DPC count: 4365_________________________________________________________________________________________________________CPU 28 Interrupt cycle time (s): 2.073788CPU 28 ISR highest execution time (µs): 0.0CPU 28 ISR total execution time (s): 0.0CPU 28 ISR count: 0CPU 28 DPC highest execution time (µs): 103.340CPU 28 DPC total execution time (s): 0.003077CPU 28 DPC count: 423_________________________________________________________________________________________________________CPU 29 Interrupt cycle time (s): 2.011566CPU 29 ISR highest execution time (µs): 0.0CPU 29 ISR total execution time (s): 0.0CPU 29 ISR count: 0CPU 29 DPC highest execution time (µs): 67.60CPU 29 DPC total execution time (s): 0.001218CPU 29 DPC count: 126_________________________________________________________________________________________________________CPU 30 Interrupt cycle time (s): 2.104840CPU 30 ISR highest execution time (µs): 0.0CPU 30 ISR total execution time (s): 0.0CPU 30 ISR count: 0CPU 30 DPC highest execution time (µs): 69.330CPU 30 DPC total execution time (s): 0.001108CPU 30 DPC count: 134_________________________________________________________________________________________________________CPU 31 Interrupt cycle time (s): 1.994049CPU 31 ISR highest execution time (µs): 0.0CPU 31 ISR total execution time (s): 0.0CPU 31 ISR count: 0CPU 31 DPC highest execution time (µs): 43.040CPU 31 DPC total execution time (s): 0.000387CPU 31 DPC count: 59_________________________________________________________________________________________________________

Reply

N

naTe_coRe_1084

01-25-2026, 02:13 PM #2

Confirm that the pops happen when others use their microphones.

Reply

A

Awoofshu

01-25-2026, 02:13 PM #3

Yes, correct.

Reply

S

Shadoox

01-25-2026, 02:13 PM #4

Not everyone, not always – right?
I wasn’t able to hear any "pops" in the video clips.
Begin by asking those involved to turn down their microphones. Check if that makes a difference.
Maybe tweak the sensitivities.
A simple solution – turn off Audio Enhancements.
System > Sound > All sound devices > Properties (path may change).
Try working online with someone whose microphone causes popping and explore their settings.
Microsoft includes some built-in microphone tests that can be helpful.

Reply

B

Brother_dog27

01-25-2026, 02:13 PM #5

Occasionally it happens, though it affects everyone. The audio improvements do not make a difference. I've demonstrated to numerous individuals that the popping sound is audible to them but not to others.

Reply

G

GameBoosh

01-25-2026, 02:13 PM #6

Consider that the pops might be happening on the speaker side of the audio setup.
This issue is specific to your device.
Others can only hear the pops if your system captures them.
Search online for "Audio pops, cracks, squeals, buzzes - troubleshooting" and adjust the search as needed.
Review some information and then proceed with troubleshooting.
The goal is to identify possible causes such as the microphone, speakers, amplifier, or power supply.
Further details are required.

Reply

G

Guson

01-25-2026, 02:13 PM #7

People often experience the same problem I do when watching recordings, and it can be heard during live streams too. Audio and ground loops are common issues that affect sound quality. Checking for them involves listening carefully for unusual noises or feedback.

Reply

P

Purplz29

01-25-2026, 02:13 PM #8

Audio and ground loops often emerge when Device A links to Device B, which connects to Device C, and then Device C connects back to Device D, forming a loop again. This can happen through various connections—electrical, audio, video, or peripherals—and typically occurs on your end. The outcome varies depending on the devices and pathways involved. A buildup of charge may cause a spark, resulting in a popping sound. You might notice the spark if you're paying close attention. Try searching online for "audio ground loop computer sound system" to find relevant information. You may need to review and refine your search results to understand what you're dealing with. Look for diagrams or examples that illustrate similar setups, as they can help clarify the issue. The loop might not be immediately clear, but systematically altering connections and observing changes can help identify the source. It’s important to test by swapping components or cables, noting which ones trigger the popping. Ultimately, the goal is to isolate the problem by methodically removing parts and adjusting paths until the issue disappears.

Reply

I

InoueAlice

01-25-2026, 02:13 PM #9

A week or two ago you received a brand new computer, and the only change I made was the graphics card. Not the motherboard, not the CPU, not the power supply, etc...
2) The problem began randomly in December on my old machine and keeps happening even on your new one. I don’t think it’s due to faulty wiring.
I’d like to make sure that the people listening to the pops are also watching the videos I sent them. The actual recorded clips.
Thank you for your help, sorry for the confusion.

Reply

M

mjt2789

01-25-2026, 02:13 PM #10

Troubleshooting might seem tricky. Many small details can interfere.
If you hear the pops in your videos, it usually points to an issue on your end.
When both the old and new systems are affected, the problem is likely shared by a common element.
The only shared part appears to be the graphics card – correct? If yes, then it’s quite suspicious.
After reviewing, you tried a friend’s GPU and the pops persisted – right?
This pattern repeats with headphones, headsets, and microphones too.
It helps to focus on any electrical connections between both computers (old and new).
The pop likely results from an electrical discharge—small enough to affect audio but noticeable.
That sudden surge of electrons (the “spark”) hits the audio circuits, creating a pop or a tiny crack.
⚡ Static electricity is one possible reason. It varies with humidity, movement, and contact. Frequent pops might make static less likely, though fan blades can also generate static that seeks a path to ground through your setup.
Consider when recording: were there periods with more or fewer pops? Those moments could offer insight.
For other possibilities, inspect the electrical connections—outlets, UPS, surge protectors, power strips, monitors, printers, NAS, etc.—as potential sources.
Any device connected to the same circuit could be responsible.
Loose connections, worn plugs, or faulty components can cause sparks.
Check light fixtures, sound systems, monitors, and TVs for issues.

What to do:
Attempt to disconnect the computer from as many devices as possible. Use a different power source or circuit. Switch cords and avoid using multiple outlets.
Maintain distance between cords and other electrical setups. A tangled mess of wires can disrupt the flow.
Also watch for related signs—flickering lights, loose wall plugs, old or damaged power cords, exposed wires.

Reply