LatencyMon fix

[stmp]

the delay of my drivers is considered the norm, why, then, in "main" such indicators?





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:00:23 (h:mm:ss) on all processors.


_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: DESKTOP-RCKD3V0
OS version: Windows 10 , 10.0, build: 19042 (x64)
Hardware: ASRock, AB350 Pro4
CPU: AuthenticAMD AMD Ryzen 5 2600 Six-Core Processor
Logical processors: 12
Processor groups: 1
RAM: 16315 MB total


_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 340 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.

WARNING: the CPU speed that was measured is only a fraction of the CPU speed reported. Your CPUs may be throttled back due to variable speed settings and thermal issues. It is suggested that you run a utility which reports your actual CPU frequency and temperature.



_________________________________________________________________________________________________________
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): 545.10
Average measured interrupt to process latency (µs): 5.724977

Highest measured interrupt to DPC latency (µs): 543.30
Average measured interrupt to DPC latency (µs): 3.549018


_________________________________________________________________________________________________________
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): 22.330
Driver with highest ISR routine execution time: HDAudBus.sys - High Definition Audio Bus Driver, Microsoft Corporation

Highest reported total ISR routine time (%): 0.000789
Driver with highest ISR total time: HDAudBus.sys - High Definition Audio Bus Driver, Microsoft Corporation

Total time spent in ISRs (%) 0.000789

ISR count (execution time <250 µs): 399
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-999 µs): 0
ISR count (execution time 1000-1999 µs): 0
ISR count (execution time 2000-3999 µ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): 50.460
Driver with highest DPC routine execution time: tcpip.sys - TCP/IP Driver, Microsoft Corporation

Highest reported total DPC routine time (%): 0.003377
Driver with highest DPC total execution time: ntoskrnl.exe - NT Kernel & System, Microsoft Corporation

Total time spent in DPCs (%) 0.006010

DPC count (execution time <250 µs): 5929
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 0
DPC count (execution time 1000-1999 µs): 0
DPC count (execution time 2000-3999 µ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: chrome.exe

Total number of hard pagefaults 1
Hard pagefault count of hardest hit process: 1
Number of processes hit: 1


_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 0.790879
CPU 0 ISR highest execution time (µs): 22.330
CPU 0 ISR total execution time (s): 0.002180
CPU 0 ISR count: 399
CPU 0 DPC highest execution time (µs): 50.460
CPU 0 DPC total execution time (s): 0.014940
CPU 0 DPC count: 5565
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 0.011811
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): 0.0
CPU 1 DPC total execution time (s): 0.0
CPU 1 DPC count: 0
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 0.016818
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): 14.090
CPU 2 DPC total execution time (s): 0.000335
CPU 2 DPC count: 72
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 0.011218
CPU 3 ISR highest execution time (µs): 0.0
CPU 3 ISR total execution time (s): 0.0
CPU 3 ISR count: 0
CPU 3 DPC highest execution time (µs): 0.0
CPU 3 DPC total execution time (s): 0.0
CPU 3 DPC count: 0
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 0.014379
CPU 4 ISR highest execution time (µs): 0.0
CPU 4 ISR total execution time (s): 0.0
CPU 4 ISR count: 0
CPU 4 DPC highest execution time (µs): 8.340
CPU 4 DPC total execution time (s): 0.000026
CPU 4 DPC count: 6
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 0.011824
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): 1.060
CPU 5 DPC total execution time (s): 0.000001
CPU 5 DPC count: 1
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 0.014155
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): 46.810
CPU 6 DPC total execution time (s): 0.000124
CPU 6 DPC count: 19
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 0.012031
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): 0.0
CPU 7 DPC total execution time (s): 0.0
CPU 7 DPC count: 0
_________________________________________________________________________________________________________
CPU 8 Interrupt cycle time (s): 0.038447
CPU 8 ISR highest execution time (µs): 0.0
CPU 8 ISR total execution time (s): 0.0
CPU 8 ISR count: 0
CPU 8 DPC highest execution time (µs): 44.350
CPU 8 DPC total execution time (s): 0.000879
CPU 8 DPC count: 209
_________________________________________________________________________________________________________
CPU 9 Interrupt cycle time (s): 0.023492
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): 43.350
CPU 9 DPC total execution time (s): 0.000211
CPU 9 DPC count: 44
_________________________________________________________________________________________________________
CPU 10 Interrupt cycle time (s): 0.013599
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): 17.40
CPU 10 DPC total execution time (s): 0.000082
CPU 10 DPC count: 13
_________________________________________________________________________________________________________
CPU 11 Interrupt cycle time (s): 0.011641
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): 0.0
CPU 11 DPC total execution time (s): 0.0
CPU 11 DPC count: 0
_________________________________________________________________________________________________________

 

[xrobwx71]

the delay of my drivers is considered the norm, why, then, in "main" such indicators?

Can you give us more detail, please?

 

[stmp]

Can you give us more detail, please?

I speak bad English, so I apologize. There are people in YouTube who understand this and they say that the value in drivers 0.05-0.06 is normal

 

[stmp]

Can you give us more detail, please?

I don't understand where such a big delay comes from, because the drivers are fine. it seems to me because of the incompatibility of my devices. Can motherboard and RAM. Delays in the system I can say not feel, except in PUBG, but recently I reduced the delay drivers and the game has become much smoother.

 

[xrobwx71]

I speak bad English, so I apologize. There are people in YouTube who understand this and they say that the value in drivers 0.05-0.06 is normal

Use a translater like Google or DeePL.

You have people on Youtube saying it's normal. Unless someone else has an opinion, Your Latanecy Mon is good (green).

The only thing I see that's inaccurate is the CPU speed.

 

[stmp]

Используйте переводчик, например Google или DeePL .

У вас есть люди на Youtube, которые говорят, что это нормально. Если у кого-то еще нет мнения, ваш Latanacy Mon хорош (зеленый).

Единственное, что я вижу неточным, это скорость процессора.

Он должен быть до 100, а у меня 500, что не круто и означает, что в моей системе проблемы. Со скоростью процессора все нормально, стабильно 3.73 в простом, наверное программа не точно отображает, возможно это как-то связано с SMT. То есть она не считает скорость всех ядер моего процессора, а только одного, если увеличить эти данные на 12 (и столько же ЦП от моего процессора) получим те же 3.70+

It should be up to 100, and I have 500, which is not cool and means that my system has a problem. With the CPU speed is fine, stable 3.73 in simple, probably the program does not accurately display, maybe it has something to do with SMT. That is, it does not count the speed of all cores of my CPU, but only one, if you increase this data by 12 (and the same amount of CPU from my CPU) get the same 3.70+

Translated with www.DeepL.com/Translator (free version)