Ground loop, white noise, micro stuttering, latency : All thoses things we loooooove so much

[Poltopi]

Hi ! Thanks if anybody have a clue or a solution and sorry for my bad english I'm not a native speaker.

I'm quite a newbie here but I've been looking for a solution to this problem :

I've got a terrible ground loop sound when my asus screen is plug with the display port, and when I unplugged the display port cable sound is gone (but there's still a really low with noise when my preamp is set really really loud)

Quite all my cable (expect for the 3.5 to RCA) are really good quality cables.

Here's my setup :

I''ve also have micro stuttering when using youtube or things like that. I've checked latency and performed quite everything I could fine to lower it and now I don't know what to do...

Here my complete configuration :

Here a some latencymon results :

_________________________________________________________________________________________________________
CONCLUSION
_________________________________________________________________________________________________________
Your system appears to be suitable for handling real-time audio and other tasks without dropouts.
LatencyMon has been analyzing your system for 0:30:28 (h:mm:ss) on all processors.


_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: PC-BRUNO
OS version: Windows 10, 10.0, version 2009, build: 19044 (x64)
Hardware: System Product Name, System manufacturer
BIOS: BIOS Date: 04/28/22 21:51:35 Ver: 05.00011
CPU: AuthenticAMD AMD Ryzen 5 2600 Six-Core Processor
Logical processors: 12
Processor groups: 1
Processor group size: 12
RAM: 16297 MB total


_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed (WMI): 40 MHz
Reported CPU speed (registry): 40 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): 330,90
Average measured interrupt to process latency (µs): 5,748012

Highest measured interrupt to DPC latency (µs): 327,90
Average measured interrupt to DPC latency (µs): 3,166826


_________________________________________________________________________________________________________
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): 69,030
Driver with highest ISR routine execution time: Wdf01000.sys - Runtime de l’infrastructure de pilotes en mode noyau, Microsoft Corporation

Highest reported total ISR routine time (%): 0,010504
Driver with highest ISR total time: Wdf01000.sys - Runtime de l’infrastructure de pilotes en mode noyau, Microsoft Corporation

Total time spent in ISRs (%) 0,010504

ISR count (execution time <250 µs): 4461296
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): 440,30
Driver with highest DPC routine execution time: ntoskrnl.exe - NT Kernel & System, Microsoft Corporation

Highest reported total DPC routine time (%): 0,273254
Driver with highest DPC total execution time: Wdf01000.sys - Runtime de l’infrastructure de pilotes en mode noyau, Microsoft Corporation

Total time spent in DPCs (%) 0,372523

DPC count (execution time <250 µs): 7932138
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-10000 µs): 19
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: microsoft.photos.exe

Total number of hard pagefaults 8796
Hard pagefault count of hardest hit process: 3163
Number of processes hit: 35


_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 101,129243
CPU 0 ISR highest execution time (µs): 67,040
CPU 0 ISR total execution time (s): 0,880281
CPU 0 ISR count: 1801295
CPU 0 DPC highest execution time (µs): 440,30
CPU 0 DPC total execution time (s): 61,158345
CPU 0 DPC count: 6013170
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 49,105791
CPU 1 ISR highest execution time (µs): 69,030
CPU 1 ISR total execution time (s): 0,447395
CPU 1 ISR count: 772257
CPU 1 DPC highest execution time (µs): 263,060
CPU 1 DPC total execution time (s): 17,739312
CPU 1 DPC count: 1466381
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 6,428446
CPU 2 ISR highest execution time (µs): 13,280
CPU 2 ISR total execution time (s): 0,080557
CPU 2 ISR count: 113373
CPU 2 DPC highest execution time (µs): 235,790
CPU 2 DPC total execution time (s): 1,648327
CPU 2 DPC count: 189311
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 3,655907
CPU 3 ISR highest execution time (µs): 4,350
CPU 3 ISR total execution time (s): 0,001624
CPU 3 ISR count: 1762
CPU 3 DPC highest execution time (µs): 235,010
CPU 3 DPC total execution time (s): 0,162185
CPU 3 DPC count: 45831
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 4,625646
CPU 4 ISR highest execution time (µs): 4,130
CPU 4 ISR total execution time (s): 0,000434
CPU 4 ISR count: 371
CPU 4 DPC highest execution time (µs): 234,870
CPU 4 DPC total execution time (s): 0,345453
CPU 4 DPC count: 86333
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 3,653525
CPU 5 ISR highest execution time (µs): 2,110
CPU 5 ISR total execution time (s): 0,000048
CPU 5 ISR count: 45
CPU 5 DPC highest execution time (µs): 233,280
CPU 5 DPC total execution time (s): 0,076822
CPU 5 DPC count: 21842
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 4,155185
CPU 6 ISR highest execution time (µs): 3,380
CPU 6 ISR total execution time (s): 0,000053
CPU 6 ISR count: 24
CPU 6 DPC highest execution time (µs): 231,90
CPU 6 DPC total execution time (s): 0,170895
CPU 6 DPC count: 32386
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 3,328140
CPU 7 ISR highest execution time (µs): 0,0
CPU 7 ISR total execution time (s): 0,0
CPU 7 ISR count: 0
CPU 7 DPC highest execution time (µs): 46,740
CPU 7 DPC total execution time (s): 0,016792
CPU 7 DPC count: 4384
_________________________________________________________________________________________________________
CPU 8 Interrupt cycle time (s): 6,709549
CPU 8 ISR highest execution time (µs): 15,50
CPU 8 ISR total execution time (s): 0,810376
CPU 8 ISR count: 1652193
CPU 8 DPC highest execution time (µs): 220,960
CPU 8 DPC total execution time (s): 0,251358
CPU 8 DPC count: 48540
_________________________________________________________________________________________________________
CPU 9 Interrupt cycle time (s): 3,203606
CPU 9 ISR highest execution time (µs): 6,090
CPU 9 ISR total execution time (s): 0,013350
CPU 9 ISR count: 20463
CPU 9 DPC highest execution time (µs): 42,090
CPU 9 DPC total execution time (s): 0,020711
CPU 9 DPC count: 4244
_________________________________________________________________________________________________________
CPU 10 Interrupt cycle time (s): 4,283730
CPU 10 ISR highest execution time (µs): 8,240
CPU 10 ISR total execution time (s): 0,037556
CPU 10 ISR count: 51603
CPU 10 DPC highest execution time (µs): 229,660
CPU 10 DPC total execution time (s): 0,104746
CPU 10 DPC count: 14337
_________________________________________________________________________________________________________
CPU 11 Interrupt cycle time (s): 3,622824
CPU 11 ISR highest execution time (µs): 9,10
CPU 11 ISR total execution time (s): 0,033062
CPU 11 ISR count: 47910
CPU 11 DPC highest execution time (µs): 53,210
CPU 11 DPC total execution time (s): 0,039191
CPU 11 DPC count: 5398
_________________________________________________________________________________________________________

 

[wwenze]

Micro-stuttering... this is why I don't like using USB. Especially the earlier-gen Ryzens.

Check that if you have the latest BIOS. Specifically, AGESA 1.2.0.2 or newer
Set PCIe mode from Gen4/Auto to Gen 3 in the BIOS
Disable Global C-State in the BIOS.

Ground loop, just to confirm, if you disconnect your 3.5mm to RCA cable, it is also gone, right?
I can see an issue where if your Roland Quad is designed to have USB ground separated from output ground, but you link them together via the ASUS monitor screen anyway, it will be noisy.
One trick you can try is to connect a 3.5mm from the PC to the preamp. Don't have to actually use it, it is just there for the ground connection.

 

[Poltopi]

Yes ! Everything is updated, PCIe mod is allready set to Gen 3, Global C-State is disable too.

I've been looking for a solution for months and there's no solution, it's still stuttering...

Yeap when I unplugged the cable ground loop is gone but there's still white noise when preamp is set really loud.

I can't do that cause I'm getting the Nintendo switch audio from the Asus monitor...

 

[Lambda]

I've been looking for a solution for months and there's no solution, it's still stuttering...

boot a Linux system. if it's still the same problem you have a hardware issue.

I can't do that cause I'm getting the Nintendo switch audio from the Asus monitor...

you need to use a isolator/transformer for that.

there's still white noise when preamp is set really loud.

from what input?

 

[Poltopi]

Ok don't know how to test it with Linux, but I'll learn lol

That kind of isolator ? https://www.amazon.fr/gp/product/B0171PQLB8/ref=ox_sc_act_image_4?smid=A3D9XII2AYP2O3&psc=1

From Video 1, Video 2 and that's all if I remember well

 

[AnalogSteph]

Yes ! Everything is updated, PCIe mod is allready set to Gen 3, Global C-State is disable too.

You never want to disable C-States entirely. Just package C6 (or higher), which is known problematic on Ryzen (I suspect it might have something to do with XMP, or possibly it can be enabled while PCIe links are still active - turn on ASPM for PCIe). Idle power consumption can be quite high for Ryzen, apparently Infinity Fabric clock and SoC settings are playing a role in this. If I ever get my hands on a system like that I'll have to playing around with it to get the hang of this.

I see you seem to have the latest BIOS (so the most major USB issues ought to be solved), and your DPC latency looks fine, too. A bit of a head-scratcher.

Have you tried the onboard audio output to see whether it is stuttering as well? You have presumably tried a range of different USB ports already (and possibly another cable)? Bus-powered interfaces can be a bit touchy. Another suggestion I found for the Roland was disabling "Game Mode". Also, check what buffer size is set to (this should normally affect ASIO only but you just never know). Are the graphics drivers up to date?

That kind of isolator ? https://www.amazon.fr/gp/product/B0171PQLB8/ref=ox_sc_act_image_4?smid=A3D9XII2AYP2O3&psc=1

Kind of, that thing is very cheap and looks tiny. I dread to think of what the bass response is going to look like. (Good audio transformers are neither cheap nor tiny. You can easily spend 70€ for a good unit.) Unfortunately I don't know a good reliable candidate either, aside from the trusty Behringer HD400, and that's a bit awkward to use in a consumer audio context. Mind you, you probably don't have the highest demands for audio from the Switch anyway.

 

[wwenze]

What I *think* or *I hope* helps with USB stuttering (I do video capture with my Elgato so you can bet that is way more stressful than just USB audio) is:

- If you look in device manager and sort by connection, you can see how your USB controllers / USB root hubs are connected. You should see one or two USB root hubs that are given to you by your AMD platform, and at the same time another 3rd-party USB controller will be providing another root hub. Usually it would be the one that provides the 10Gbps, I think.

Make sure that whatever device that you require time-critical performance from, in your case your USB DAC, you provide one whole root hub / one whole USB controller to it, and connect nothing else to that USB root hub. You can dump the rest of keyboard/mouse/HDD and whatever onto another root hub. Note that many things like bluetooth and LED are also connect via USB.

As for which root hub is better, the 3rd-party USB controller connected via PCIE, or the AMD platform's own USB controller, I have never gotten a certain conclusion.

 

[raindance]

How would a digital isolator affect the bass??????

 

[AnalogSteph]

How would a digital isolator affect the bass??????

The product in question is an analog transformer-based line isolator, not a USB isolator.

That would be the better option if it works... which may prove a bit tricky with a potentially finicky bus-powered interface (a powered USB hub might sort that out but not every audio interfaces likes to be operated on a hub).

 

[Poltopi]

Hi ! I've re installed windows two times on my NVME with UEFI Usb key made with Rufus, I've also blocked windows update to proceed by myself to driver's installation.
I've done some bios tweak yesterday when I re installed windows for the first time and everything was working without those stuttering or drops (I really don't know how to name those). But I've experienced awfull latency so I've decide to re installed it again. Now stuttering are back.

Here's latency tweaking I've done : https://docs.google.com/document/d/1kq1LSJfyrIGcOUopcOIVZPbZL8OPgFXtpUM9PT3Q47w/edit#
I've made a restauration point for every step and when it began to stutter again on step 4 I've rolled back to step 3 and it was stuterring too (before I get to step 4 it wasn't)
It's not writte on my sheet but I've made changes in device manager to keep USB port powered.

Here's my last latencymon test (latencymon shut down by itself during some test, don't know why) and it's also not seeing my real CPU speed.

Don't know what to do and I'm not sure to be understanding all your answers...

_________________________________________________________________________________________________________
CONCLUSION
_________________________________________________________________________________________________________
Your system appears to be suitable for handling real-time audio and other tasks without dropouts.
LatencyMon has been analyzing your system for 0:12:35 (h:mm:ss) on all processors.


_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: PC-BRUNO
OS version: Windows 10, 10.0, version 2009, build: 19044 (x64)
Hardware: System Product Name, System manufacturer
BIOS: 3802
CPU: AuthenticAMD AMD Ryzen 5 2600 Six-Core Processor
Logical processors: 12
Processor groups: 1
Processor group size: 12
RAM: 16296 MB total


_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed (WMI): 40 MHz
Reported CPU speed (registry): 40 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): 247,20
Average measured interrupt to process latency (µs): 3,974999

Highest measured interrupt to DPC latency (µs): 243,10
Average measured interrupt to DPC latency (µs): 1,864146


_________________________________________________________________________________________________________
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): 28,670
Driver with highest ISR routine execution time: Wdf01000.sys - Runtime de l’infrastructure de pilotes en mode noyau, Microsoft Corporation

Highest reported total ISR routine time (%): 0,093644
Driver with highest ISR total time: Wdf01000.sys - Runtime de l’infrastructure de pilotes en mode noyau, Microsoft Corporation

Total time spent in ISRs (%) 0,093644

ISR count (execution time <250 µs): 19682860
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): 323,550
Driver with highest DPC routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

Highest reported total DPC routine time (%): 0,380691
Driver with highest DPC total execution time: Wdf01000.sys - Runtime de l’infrastructure de pilotes en mode noyau, Microsoft Corporation

Total time spent in DPCs (%) 0,461706

DPC count (execution time <250 µs): 13420938
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-10000 µs): 21
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: msmpeng.exe

Total number of hard pagefaults 2882
Hard pagefault count of hardest hit process: 1010
Number of processes hit: 38


_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 53,429702
CPU 0 ISR highest execution time (µs): 27,310
CPU 0 ISR total execution time (s): 4,824537
CPU 0 ISR count: 10646919
CPU 0 DPC highest execution time (µs): 312,660
CPU 0 DPC total execution time (s): 38,050987
CPU 0 DPC count: 12761684
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 14,736056
CPU 1 ISR highest execution time (µs): 28,330
CPU 1 ISR total execution time (s): 0,145604
CPU 1 ISR count: 384974
CPU 1 DPC highest execution time (µs): 323,550
CPU 1 DPC total execution time (s): 3,264360
CPU 1 DPC count: 557765
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 2,476932
CPU 2 ISR highest execution time (µs): 8,330
CPU 2 ISR total execution time (s): 0,006568
CPU 2 ISR count: 7237
CPU 2 DPC highest execution time (µs): 146,520
CPU 2 DPC total execution time (s): 0,198090
CPU 2 DPC count: 24144
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 2,135970
CPU 3 ISR highest execution time (µs): 2,630
CPU 3 ISR total execution time (s): 0,000120
CPU 3 ISR count: 104
CPU 3 DPC highest execution time (µs): 25,480
CPU 3 DPC total execution time (s): 0,013954
CPU 3 DPC count: 3808
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 2,077667
CPU 4 ISR highest execution time (µs): 2,570
CPU 4 ISR total execution time (s): 0,000049
CPU 4 ISR count: 36
CPU 4 DPC highest execution time (µs): 135,760
CPU 4 DPC total execution time (s): 0,060484
CPU 4 DPC count: 13799
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 1,925320
CPU 5 ISR highest execution time (µs): 2,110
CPU 5 ISR total execution time (s): 0,000007
CPU 5 ISR count: 4
CPU 5 DPC highest execution time (µs): 36,30
CPU 5 DPC total execution time (s): 0,046927
CPU 5 DPC count: 8962
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 2,075095
CPU 6 ISR highest execution time (µs): 3,970
CPU 6 ISR total execution time (s): 0,000016
CPU 6 ISR count: 6
CPU 6 DPC highest execution time (µs): 99,260
CPU 6 DPC total execution time (s): 0,037496
CPU 6 DPC count: 7431
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 1,845326
CPU 7 ISR highest execution time (µs): 0,0
CPU 7 ISR total execution time (s): 0,0
CPU 7 ISR count: 0
CPU 7 DPC highest execution time (µs): 26,420
CPU 7 DPC total execution time (s): 0,002348
CPU 7 DPC count: 562
_________________________________________________________________________________________________________
CPU 8 Interrupt cycle time (s): 6,930554
CPU 8 ISR highest execution time (µs): 28,670
CPU 8 ISR total execution time (s): 3,245151
CPU 8 ISR count: 8079745
CPU 8 DPC highest execution time (µs): 207,910
CPU 8 DPC total execution time (s): 0,104664
CPU 8 DPC count: 30823
_________________________________________________________________________________________________________
CPU 9 Interrupt cycle time (s): 2,274282
CPU 9 ISR highest execution time (µs): 9,490
CPU 9 ISR total execution time (s): 0,056218
CPU 9 ISR count: 126301
CPU 9 DPC highest execution time (µs): 44,730
CPU 9 DPC total execution time (s): 0,009184
CPU 9 DPC count: 2185
_________________________________________________________________________________________________________
CPU 10 Interrupt cycle time (s): 2,497029
CPU 10 ISR highest execution time (µs): 6,680
CPU 10 ISR total execution time (s): 0,085476
CPU 10 ISR count: 174551
CPU 10 DPC highest execution time (µs): 206,250
CPU 10 DPC total execution time (s): 0,029208
CPU 10 DPC count: 4520
_________________________________________________________________________________________________________
CPU 11 Interrupt cycle time (s): 2,600290
CPU 11 ISR highest execution time (µs): 11,350
CPU 11 ISR total execution time (s): 0,126058
CPU 11 ISR count: 262983
CPU 11 DPC highest execution time (µs): 205,70
CPU 11 DPC total execution time (s): 0,040541
CPU 11 DPC count: 5276
_________________________________________________________________________________________________________

 

[Sweater]

Hi ! I've re installed windows two times on my NVME with UEFI Usb key made with Rufus, I've also blocked windows update to proceed by myself to driver's installation.
I've done some bios tweak yesterday when I re installed windows for the first time and everything was working without those stuttering or drops (I really don't know how to name those). But I've experienced awfull latency so I've decide to re installed it again. Now stuttering are back.

Here's latency tweaking I've done : https://docs.google.com/document/d/1kq1LSJfyrIGcOUopcOIVZPbZL8OPgFXtpUM9PT3Q47w/edit#
I've made a restauration point for every step and when it began to stutter again on step 4 I've rolled back to step 3 and it was stuterring too (before I get to step 4 it wasn't)
It's not writte on my sheet but I've made changes in device manager to keep USB port powered.

Here's my last latencymon test (latencymon shut down by itself during some test, don't know why) and it's also not seeing my real CPU speed.

Don't know what to do and I'm not sure to be understanding all your answers...

_________________________________________________________________________________________________________
CONCLUSION
_________________________________________________________________________________________________________
Your system appears to be suitable for handling real-time audio and other tasks without dropouts.
LatencyMon has been analyzing your system for 0:12:35 (h:mm:ss) on all processors.


_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: PC-BRUNO
OS version: Windows 10, 10.0, version 2009, build: 19044 (x64)
Hardware: System Product Name, System manufacturer
BIOS: 3802
CPU: AuthenticAMD AMD Ryzen 5 2600 Six-Core Processor
Logical processors: 12
Processor groups: 1
Processor group size: 12
RAM: 16296 MB total


_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed (WMI): 40 MHz
Reported CPU speed (registry): 40 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): 247,20
Average measured interrupt to process latency (µs): 3,974999

Highest measured interrupt to DPC latency (µs): 243,10
Average measured interrupt to DPC latency (µs): 1,864146


_________________________________________________________________________________________________________
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): 28,670
Driver with highest ISR routine execution time: Wdf01000.sys - Runtime de l’infrastructure de pilotes en mode noyau, Microsoft Corporation

Highest reported total ISR routine time (%): 0,093644
Driver with highest ISR total time: Wdf01000.sys - Runtime de l’infrastructure de pilotes en mode noyau, Microsoft Corporation

Total time spent in ISRs (%) 0,093644

ISR count (execution time <250 µs): 19682860
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): 323,550
Driver with highest DPC routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

Highest reported total DPC routine time (%): 0,380691
Driver with highest DPC total execution time: Wdf01000.sys - Runtime de l’infrastructure de pilotes en mode noyau, Microsoft Corporation

Total time spent in DPCs (%) 0,461706

DPC count (execution time <250 µs): 13420938
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-10000 µs): 21
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: msmpeng.exe

Total number of hard pagefaults 2882
Hard pagefault count of hardest hit process: 1010
Number of processes hit: 38


_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 53,429702
CPU 0 ISR highest execution time (µs): 27,310
CPU 0 ISR total execution time (s): 4,824537
CPU 0 ISR count: 10646919
CPU 0 DPC highest execution time (µs): 312,660
CPU 0 DPC total execution time (s): 38,050987
CPU 0 DPC count: 12761684
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 14,736056
CPU 1 ISR highest execution time (µs): 28,330
CPU 1 ISR total execution time (s): 0,145604
CPU 1 ISR count: 384974
CPU 1 DPC highest execution time (µs): 323,550
CPU 1 DPC total execution time (s): 3,264360
CPU 1 DPC count: 557765
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 2,476932
CPU 2 ISR highest execution time (µs): 8,330
CPU 2 ISR total execution time (s): 0,006568
CPU 2 ISR count: 7237
CPU 2 DPC highest execution time (µs): 146,520
CPU 2 DPC total execution time (s): 0,198090
CPU 2 DPC count: 24144
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 2,135970
CPU 3 ISR highest execution time (µs): 2,630
CPU 3 ISR total execution time (s): 0,000120
CPU 3 ISR count: 104
CPU 3 DPC highest execution time (µs): 25,480
CPU 3 DPC total execution time (s): 0,013954
CPU 3 DPC count: 3808
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 2,077667
CPU 4 ISR highest execution time (µs): 2,570
CPU 4 ISR total execution time (s): 0,000049
CPU 4 ISR count: 36
CPU 4 DPC highest execution time (µs): 135,760
CPU 4 DPC total execution time (s): 0,060484
CPU 4 DPC count: 13799
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 1,925320
CPU 5 ISR highest execution time (µs): 2,110
CPU 5 ISR total execution time (s): 0,000007
CPU 5 ISR count: 4
CPU 5 DPC highest execution time (µs): 36,30
CPU 5 DPC total execution time (s): 0,046927
CPU 5 DPC count: 8962
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 2,075095
CPU 6 ISR highest execution time (µs): 3,970
CPU 6 ISR total execution time (s): 0,000016
CPU 6 ISR count: 6
CPU 6 DPC highest execution time (µs): 99,260
CPU 6 DPC total execution time (s): 0,037496
CPU 6 DPC count: 7431
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 1,845326
CPU 7 ISR highest execution time (µs): 0,0
CPU 7 ISR total execution time (s): 0,0
CPU 7 ISR count: 0
CPU 7 DPC highest execution time (µs): 26,420
CPU 7 DPC total execution time (s): 0,002348
CPU 7 DPC count: 562
_________________________________________________________________________________________________________
CPU 8 Interrupt cycle time (s): 6,930554
CPU 8 ISR highest execution time (µs): 28,670
CPU 8 ISR total execution time (s): 3,245151
CPU 8 ISR count: 8079745
CPU 8 DPC highest execution time (µs): 207,910
CPU 8 DPC total execution time (s): 0,104664
CPU 8 DPC count: 30823
_________________________________________________________________________________________________________
CPU 9 Interrupt cycle time (s): 2,274282
CPU 9 ISR highest execution time (µs): 9,490
CPU 9 ISR total execution time (s): 0,056218
CPU 9 ISR count: 126301
CPU 9 DPC highest execution time (µs): 44,730
CPU 9 DPC total execution time (s): 0,009184
CPU 9 DPC count: 2185
_________________________________________________________________________________________________________
CPU 10 Interrupt cycle time (s): 2,497029
CPU 10 ISR highest execution time (µs): 6,680
CPU 10 ISR total execution time (s): 0,085476
CPU 10 ISR count: 174551
CPU 10 DPC highest execution time (µs): 206,250
CPU 10 DPC total execution time (s): 0,029208
CPU 10 DPC count: 4520
_________________________________________________________________________________________________________
CPU 11 Interrupt cycle time (s): 2,600290
CPU 11 ISR highest execution time (µs): 11,350
CPU 11 ISR total execution time (s): 0,126058
CPU 11 ISR count: 262983
CPU 11 DPC highest execution time (µs): 205,70
CPU 11 DPC total execution time (s): 0,040541
CPU 11 DPC count: 5276
_________________________________________________________________________________________________________

Did you found a fix? Also, your google document required for login, you should change permissions in the settings