PeePeePooP00
New member
- Dec 2, 2022
- 1
Hello, I need help.
In LatencyMon, I found delays appearing after a few minutes of work.
There are no actions in the background, only the included Windows and LatencyMon.
I've been trying to solve this problem for a long time, but it doesn't work.
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
REPORTS
_________________________________________________________________________________________________________
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:07:16 (h:mm:ss) on all processors.
_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: DESKTOP-T5JALJV
OS version: Windows 10, 10.0, version 2009, build: 19042 (x64)
Hardware: A320M-S2H V2, Gigabyte Technology Co., Ltd.
BIOS: F55a
CPU: AuthenticAMD AMD Ryzen 5 3500X 6-Core Processor
Logical processors: 6
Processor groups: 1
Processor group size: 6
RAM: 16308 MB total
_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed (WMI): 360 MHz
Reported CPU speed (registry): 3593 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): 84,70
Average measured interrupt to process latency (µs): 2,892382
Highest measured interrupt to DPC latency (µs): 82,60
Average measured interrupt to DPC latency (µs): 1,282542
_________________________________________________________________________________________________________
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): 2,294461
Driver with highest ISR routine execution time: Wdf01000.sys - Среда выполнения платформы драйвера режима ядра, Microsoft Corporation
Highest reported total ISR routine time (%): 0,000009
Driver with highest ISR total time: Wdf01000.sys - Среда выполнения платформы драйвера режима ядра, Microsoft Corporation
Total time spent in ISRs (%) 0,000009
ISR count (execution time <250 µs): 442
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): 213,745616
Driver with highest DPC routine execution time: ntoskrnl.exe - NT Kernel & System, Microsoft Corporation
Highest reported total DPC routine time (%): 0,003917
Driver with highest DPC total execution time: rspLLL64.sys - Resplendence Latency Monitoring and Auxiliary Kernel Library, Resplendence Software Projects Sp.
Total time spent in DPCs (%) 0,011884
DPC count (execution time <250 µs): 278103
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-10000 µs): 0
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: system
Total number of hard pagefaults 3
Hard pagefault count of hardest hit process: 1
Number of processes hit: 2
_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 7,30260
CPU 0 ISR highest execution time (µs): 0,0
CPU 0 ISR total execution time (s): 0,0
CPU 0 ISR count: 0
CPU 0 DPC highest execution time (µs): 213,745616
CPU 0 DPC total execution time (s): 0,255121
CPU 0 DPC count: 254920
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 0,410114
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): 15,129418
CPU 1 DPC total execution time (s): 0,001156
CPU 1 DPC count: 970
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 0,382090
CPU 2 ISR highest execution time (µs): 2,294461
CPU 2 ISR total execution time (s): 0,000244
CPU 2 ISR count: 442
CPU 2 DPC highest execution time (µs): 32,833844
CPU 2 DPC total execution time (s): 0,050183
CPU 2 DPC count: 20069
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 0,506160
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): 12,093515
CPU 3 DPC total execution time (s): 0,000892
CPU 3 DPC count: 663
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 0,509279
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): 12,39410
CPU 4 DPC total execution time (s): 0,001144
CPU 4 DPC count: 631
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 0,542573
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): 9,738937
CPU 5 DPC total execution time (s): 0,002468
CPU 5 DPC count: 850
_________________________________________________________________________________________________________
In LatencyMon, I found delays appearing after a few minutes of work.
There are no actions in the background, only the included Windows and LatencyMon.
I've been trying to solve this problem for a long time, but it doesn't work.
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
REPORTS
_________________________________________________________________________________________________________
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:07:16 (h:mm:ss) on all processors.
_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: DESKTOP-T5JALJV
OS version: Windows 10, 10.0, version 2009, build: 19042 (x64)
Hardware: A320M-S2H V2, Gigabyte Technology Co., Ltd.
BIOS: F55a
CPU: AuthenticAMD AMD Ryzen 5 3500X 6-Core Processor
Logical processors: 6
Processor groups: 1
Processor group size: 6
RAM: 16308 MB total
_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed (WMI): 360 MHz
Reported CPU speed (registry): 3593 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): 84,70
Average measured interrupt to process latency (µs): 2,892382
Highest measured interrupt to DPC latency (µs): 82,60
Average measured interrupt to DPC latency (µs): 1,282542
_________________________________________________________________________________________________________
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): 2,294461
Driver with highest ISR routine execution time: Wdf01000.sys - Среда выполнения платформы драйвера режима ядра, Microsoft Corporation
Highest reported total ISR routine time (%): 0,000009
Driver with highest ISR total time: Wdf01000.sys - Среда выполнения платформы драйвера режима ядра, Microsoft Corporation
Total time spent in ISRs (%) 0,000009
ISR count (execution time <250 µs): 442
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): 213,745616
Driver with highest DPC routine execution time: ntoskrnl.exe - NT Kernel & System, Microsoft Corporation
Highest reported total DPC routine time (%): 0,003917
Driver with highest DPC total execution time: rspLLL64.sys - Resplendence Latency Monitoring and Auxiliary Kernel Library, Resplendence Software Projects Sp.
Total time spent in DPCs (%) 0,011884
DPC count (execution time <250 µs): 278103
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-10000 µs): 0
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: system
Total number of hard pagefaults 3
Hard pagefault count of hardest hit process: 1
Number of processes hit: 2
_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 7,30260
CPU 0 ISR highest execution time (µs): 0,0
CPU 0 ISR total execution time (s): 0,0
CPU 0 ISR count: 0
CPU 0 DPC highest execution time (µs): 213,745616
CPU 0 DPC total execution time (s): 0,255121
CPU 0 DPC count: 254920
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 0,410114
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): 15,129418
CPU 1 DPC total execution time (s): 0,001156
CPU 1 DPC count: 970
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 0,382090
CPU 2 ISR highest execution time (µs): 2,294461
CPU 2 ISR total execution time (s): 0,000244
CPU 2 ISR count: 442
CPU 2 DPC highest execution time (µs): 32,833844
CPU 2 DPC total execution time (s): 0,050183
CPU 2 DPC count: 20069
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 0,506160
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): 12,093515
CPU 3 DPC total execution time (s): 0,000892
CPU 3 DPC count: 663
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 0,509279
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): 12,39410
CPU 4 DPC total execution time (s): 0,001144
CPU 4 DPC count: 631
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 0,542573
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): 9,738937
CPU 5 DPC total execution time (s): 0,002468
CPU 5 DPC count: 850
_________________________________________________________________________________________________________
