Audio Dropouts Since Win11 Upgrade
-
- KVRist
- 52 posts since 5 Sep, 2018
I suffer from discontinuities in the signal since the forced upgrade to Win11. Gladly my exported audio turns out fine, but everything that depends on realtime playback, like watching videos, making music, recording with OBS etc., has occasional dropouts. I hope someone else here has encountered this problem and found a solution, because I have spent too much money on this machine to switch to Mac for such a stupid reason now.
- KVRian
- 672 posts since 24 Feb, 2008 from Germany
Hey,
Have you optimized your Windows 11 for audio yet? Power plan at highest? Does the windows event viewer show something obvious? Maybe there is a faulty component. Do you run a antivirus software in the background? Maybe you run a demo version of a vst? Audio interface or line out? Driver? Buffer size? Daw?
The possibilities are endless. I fear we need a bit more information to be helpful
Have you optimized your Windows 11 for audio yet? Power plan at highest? Does the windows event viewer show something obvious? Maybe there is a faulty component. Do you run a antivirus software in the background? Maybe you run a demo version of a vst? Audio interface or line out? Driver? Buffer size? Daw?
The possibilities are endless. I fear we need a bit more information to be helpful
“The biggest crime of a musician is to play notes instead of making music.”
Isaac Stern
Isaac Stern
-
- KVRist
- Topic Starter
- 52 posts since 5 Sep, 2018
I didn't add information on purpose, so that suggestions are random and more likely to add a new perspective. but since you're asking:
I have optimized Win11 with the help of this video:
Yes, power plan at full performance. No antivirus software. No demo versions of plugins. Audio interface is still pretty new. DAW-independent. No buffer size issue (I am not close to running out of cpu performance when it happens)
How do I use the event viewer to troubleshoot this problem?
I have optimized Win11 with the help of this video:
Yes, power plan at full performance. No antivirus software. No demo versions of plugins. Audio interface is still pretty new. DAW-independent. No buffer size issue (I am not close to running out of cpu performance when it happens)
How do I use the event viewer to troubleshoot this problem?
-
- KVRist
- Topic Starter
- 52 posts since 5 Sep, 2018
Here is an example of the audio dropouts I'm suffering from. I just recorded my DAW's playback with OBS and as you can hear, it happens a lot.
- KVRAF
- 16881 posts since 8 Mar, 2005 from Utrecht, Holland
Best tool for finding out the cause:
https://www.resplendence.com/latencymon
https://www.resplendence.com/latencymon
We are the KVR collective. Resistance is futile. You will be assimilated. 
My MusicCalc is served over https!!
My MusicCalc is served over https!!
-
- KVRist
- Topic Starter
- 52 posts since 5 Sep, 2018
the tool confirms my observation. apparently i have to solve it in the BIOS. kinda don't like how low level it gets already, but I mean, I'll try.BertKoor wrote: Wed Nov 05, 2025 10:19 am Best tool for finding out the cause:
https://www.resplendence.com/latencymon
---
Edit: I checked the power settings in the control panel and BIOS and both seem to be as good as possible already. But here's the rest of the test's diagnosis text, in case anyone here is good at reading that:
Code: Select all
_________________________________________________________________________________________________________
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 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:18:53 (h:mm:ss) on all processors.
_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: DESKTOP-UR9B46F
OS version: Windows 11, 10.0, version 2009, build: 26100 (x64)
Hardware: MS-7D32, Micro-Star International Co., Ltd.
BIOS: 1.80
CPU: GenuineIntel 12th Gen Intel(R) Core(TM) i7-12700K
Logical processors: 20
Processor groups: 1
Processor group size: 20
RAM: 32587 MB total
_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed (WMI): 360 MHz
Reported CPU speed (registry): 3610 MHz
Note: 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): 1923,60
Average measured interrupt to process latency (µs): 10,737963
Highest measured interrupt to DPC latency (µs): 850,20
Average measured interrupt to DPC latency (µs): 5,613483
_________________________________________________________________________________________________________
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): 90,842659
Driver with highest ISR routine execution time: Wdf01000.sys - Kernelmodustreiber-Frameworklaufzeit, Microsoft Corporation
Highest reported total ISR routine time (%): 0,002992
Driver with highest ISR total time: Wdf01000.sys - Kernelmodustreiber-Frameworklaufzeit, Microsoft Corporation
Total time spent in ISRs (%) 0,002993
ISR count (execution time <250 µs): 1993673
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-1000 µs): 0
ISR count (execution time 1000-2000 µs): 0
ISR count (execution time 2000-4000 µs): 0
ISR 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): 939,168975
Driver with highest DPC routine execution time: nvlddmkm.sys - NVIDIA Windows Kernel Mode Driver, Version 580.97 , NVIDIA Corporation
Highest reported total DPC routine time (%): 0,119626
Driver with highest DPC total execution time: Wdf01000.sys - Kernelmodustreiber-Frameworklaufzeit, Microsoft Corporation
Total time spent in DPCs (%) 0,226043
DPC count (execution time <250 µs): 5765140
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-10000 µs): 49
DPC count (execution time 1000-2000 µs): 0
DPC count (execution time 2000-4000 µs): 0
DPC 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: obs64.exe
Total number of hard pagefaults 19077
Hard pagefault count of hardest hit process: 3157
Number of processes hit: 69
_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 111,231146
CPU 0 ISR highest execution time (µs): 90,842659
CPU 0 ISR total execution time (s): 0,558653
CPU 0 ISR count: 1627939
CPU 0 DPC highest execution time (µs): 939,168975
CPU 0 DPC total execution time (s): 41,001718
CPU 0 DPC count: 4615684
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 23,241337
CPU 1 ISR highest execution time (µs): 0,0
CPU 1 ISR total execution time (s): 0,0
CPU 1 ISR count: 0
CPU 1 DPC highest execution time (µs): 23,100277
CPU 1 DPC total execution time (s): 0,003803
CPU 1 DPC count: 758
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 28,469235
CPU 2 ISR highest execution time (µs): 0,0
CPU 2 ISR total execution time (s): 0,0
CPU 2 ISR count: 0
CPU 2 DPC highest execution time (µs): 133,785596
CPU 2 DPC total execution time (s): 0,126460
CPU 2 DPC count: 21176
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 27,073252
CPU 3 ISR highest execution time (µs): 71,428255
CPU 3 ISR total execution time (s): 0,021836
CPU 3 ISR count: 62988
CPU 3 DPC highest execution time (µs): 247,478116
CPU 3 DPC total execution time (s): 1,551480
CPU 3 DPC count: 168955
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 39,069882
CPU 4 ISR highest execution time (µs): 80,041551
CPU 4 ISR total execution time (s): 0,075107
CPU 4 ISR count: 234245
CPU 4 DPC highest execution time (µs): 470,044321
CPU 4 DPC total execution time (s): 5,580737
CPU 4 DPC count: 603678
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 23,789123
CPU 5 ISR highest execution time (µs): 0,0
CPU 5 ISR total execution time (s): 0,0
CPU 5 ISR count: 0
CPU 5 DPC highest execution time (µs): 104,180055
CPU 5 DPC total execution time (s): 0,011381
CPU 5 DPC count: 1597
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 28,146699
CPU 6 ISR highest execution time (µs): 0,0
CPU 6 ISR total execution time (s): 0,0
CPU 6 ISR count: 0
CPU 6 DPC highest execution time (µs): 111,367313
CPU 6 DPC total execution time (s): 0,077824
CPU 6 DPC count: 10878
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 24,098324
CPU 7 ISR highest execution time (µs): 2,080886
CPU 7 ISR total execution time (s): 0,000577
CPU 7 ISR count: 1746
CPU 7 DPC highest execution time (µs): 156,139612
CPU 7 DPC total execution time (s): 0,047626
CPU 7 DPC count: 5525
_________________________________________________________________________________________________________
CPU 8 Interrupt cycle time (s): 28,911998
CPU 8 ISR highest execution time (µs): 29,777839
CPU 8 ISR total execution time (s): 0,006110
CPU 8 ISR count: 16273
CPU 8 DPC highest execution time (µs): 473,350139
CPU 8 DPC total execution time (s): 0,617752
CPU 8 DPC count: 78915
_________________________________________________________________________________________________________
CPU 9 Interrupt cycle time (s): 25,481394
CPU 9 ISR highest execution time (µs): 0,0
CPU 9 ISR total execution time (s): 0,0
CPU 9 ISR count: 0
CPU 9 DPC highest execution time (µs): 144,400554
CPU 9 DPC total execution time (s): 0,095859
CPU 9 DPC count: 14149
_________________________________________________________________________________________________________
CPU 10 Interrupt cycle time (s): 27,111272
CPU 10 ISR highest execution time (µs): 0,0
CPU 10 ISR total execution time (s): 0,0
CPU 10 ISR count: 0
CPU 10 DPC highest execution time (µs): 143,793352
CPU 10 DPC total execution time (s): 0,252019
CPU 10 DPC count: 38637
_________________________________________________________________________________________________________
CPU 11 Interrupt cycle time (s): 24,537110
CPU 11 ISR highest execution time (µs): 0,0
CPU 11 ISR total execution time (s): 0,0
CPU 11 ISR count: 0
CPU 11 DPC highest execution time (µs): 112,47590
CPU 11 DPC total execution time (s): 0,080446
CPU 11 DPC count: 11729
_________________________________________________________________________________________________________
CPU 12 Interrupt cycle time (s): 30,800155
CPU 12 ISR highest execution time (µs): 12,575623
CPU 12 ISR total execution time (s): 0,016229
CPU 12 ISR count: 50482
CPU 12 DPC highest execution time (µs): 185,142382
CPU 12 DPC total execution time (s): 1,167244
CPU 12 DPC count: 123031
_________________________________________________________________________________________________________
CPU 13 Interrupt cycle time (s): 24,132755
CPU 13 ISR highest execution time (µs): 0,0
CPU 13 ISR total execution time (s): 0,0
CPU 13 ISR count: 0
CPU 13 DPC highest execution time (µs): 79,288089
CPU 13 DPC total execution time (s): 0,006645
CPU 13 DPC count: 1156
_________________________________________________________________________________________________________
CPU 14 Interrupt cycle time (s): 28,164867
CPU 14 ISR highest execution time (µs): 0,0
CPU 14 ISR total execution time (s): 0,0
CPU 14 ISR count: 0
CPU 14 DPC highest execution time (µs): 110,939612
CPU 14 DPC total execution time (s): 0,055161
CPU 14 DPC count: 8487
_________________________________________________________________________________________________________
CPU 15 Interrupt cycle time (s): 23,749239
CPU 15 ISR highest execution time (µs): 0,0
CPU 15 ISR total execution time (s): 0,0
CPU 15 ISR count: 0
CPU 15 DPC highest execution time (µs): 103,942936
CPU 15 DPC total execution time (s): 0,005386
CPU 15 DPC count: 559
_________________________________________________________________________________________________________
CPU 16 Interrupt cycle time (s): 9,654676
CPU 16 ISR highest execution time (µs): 0,0
CPU 16 ISR total execution time (s): 0,0
CPU 16 ISR count: 0
CPU 16 DPC highest execution time (µs): 102,481994
CPU 16 DPC total execution time (s): 0,172296
CPU 16 DPC count: 20688
_________________________________________________________________________________________________________
CPU 17 Interrupt cycle time (s): 9,55780
CPU 17 ISR highest execution time (µs): 0,0
CPU 17 ISR total execution time (s): 0,0
CPU 17 ISR count: 0
CPU 17 DPC highest execution time (µs): 95,414404
CPU 17 DPC total execution time (s): 0,100301
CPU 17 DPC count: 11279
_________________________________________________________________________________________________________
CPU 18 Interrupt cycle time (s): 9,975134
CPU 18 ISR highest execution time (µs): 0,0
CPU 18 ISR total execution time (s): 0,0
CPU 18 ISR count: 0
CPU 18 DPC highest execution time (µs): 105,103601
CPU 18 DPC total execution time (s): 0,137573
CPU 18 DPC count: 13952
_________________________________________________________________________________________________________
CPU 19 Interrupt cycle time (s): 9,378866
CPU 19 ISR highest execution time (µs): 0,0
CPU 19 ISR total execution time (s): 0,0
CPU 19 ISR count: 0
CPU 19 DPC highest execution time (µs): 97,726870
CPU 19 DPC total execution time (s): 0,145871
CPU 19 DPC count: 14356
_________________________________________________________________________________________________________
You do not have the required permissions to view the files attached to this post.
- KVRian
- 1188 posts since 21 Aug, 2017 from Brasil
Nvidia drive is a bitch!Eine Alte Oma wrote: Wed Nov 05, 2025 7:26 am I suffer from discontinuities in the signal since the forced upgrade to Win11. Gladly my exported audio turns out fine, but everything that depends on realtime playback, like watching videos, making music, recording with OBS etc., has occasional dropouts. I hope someone else here has encountered this problem and found a solution, because I have spent too much money on this machine to switch to Mac for such a stupid reason now.
Remove the current driver with DDU https://www.wagnardsoft.com/display-dri ... taller-ddu
and install the older 572.60, do not install the Nvidia ShadowPlay!
Better use https://www.techpowerup.com/nvcleanstall/ to create a de-bloated NVIDIA driver.
Make sure to set "Power management mode" from Adaptive to Maximum Performance.
https://nvidia.custhelp.com/app/answers ... erformance


Enable MSI(Message Signaled-Based Interrupts) with this utility.
You can not enable MSI for USB 2, FireWire and some WiFi, but it is a must for the GPU.
https://forums.guru3d.com/threads/windo ... ol.378044/

And look at this
viewtopic.php?t=621326
- KVRian
- 672 posts since 24 Feb, 2008 from Germany
Hearing crackling is running out of cpu performanceEine Alte Oma wrote: Wed Nov 05, 2025 8:51 am No buffer size issue (I am not close to running out of cpu performance when it happens)
And this is in fact what the test with latencymon then told you, and showed. Audio gets processed differently. It's not that your cpu jumps at 100% when it is dealing with it. It can look like your cpu is completely idling, but it can be that you can already hear crackles from running out of buffer. Doubling the buffer size can already help. I run my Motu audio interface with 6ms / a buffer size of 256. And with the Motu Asio driver.
It is of course also a good idea to check for the trouble sources from the test. The result looks indeed not really healthy. Pictus gave already some good advice. Just to repeat my question:
Does the windows event viewer show something obvious? In Deutsch, Ereignisanzeige.
“The biggest crime of a musician is to play notes instead of making music.”
Isaac Stern
Isaac Stern
-
- KVRist
- 75 posts since 8 Nov, 2008 from Cambodia
Looks like there is a problem with your drivers, including GPU drivers, Pictus posted a full guide above you can follow.
I would also update my BIOS if i were you, download the latest and the version you have installed now and if you do not like the performance you can flash back, *just save/note your bios settings. I would also try to do a fresh install of W11, (you can use a old ssd to test if format is t much) forced updates sometimes fail.
I would also update my BIOS if i were you, download the latest and the version you have installed now and if you do not like the performance you can flash back, *just save/note your bios settings. I would also try to do a fresh install of W11, (you can use a old ssd to test if format is t much) forced updates sometimes fail.
