LatencyMon indicates elevated delays, and gameplay is experiencing stuttering and lag?
LatencyMon indicates elevated delays, and gameplay is experiencing stuttering and lag?
During the repair of my main computer, I brought out my laptop to try playing games and it kept freezing unexpectedly, which was quite bothersome. I reinstalled Windows and even upgraded to Windows 11 version 2009 (build 22621), but I haven’t noticed any audio issues. I’m really hoping for any advice on fixing this problem. If you need more details to help diagnose, please let me know.
_________________________________________________________________________________________________________
CONCLUSION
_________________________________________________________________________________________________________
Your system appears to be having trouble handling real-time audio and other tasks. You are likely to experience buffer underruns appearing as drop outs, clicks or pops. 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:08:34 (h:mm
s) on all processors._________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: LAPTOP-OB7RPSSD
OS version: Windows 11, 10.0, version 2009, build: 22631 (x64)
Hardware: TUF Gaming FX505DT_FX505DT, ASUSTeK COMPUTER INC.
BIOS: FX505DT.316
CPU: AuthenticAMD AMD Ryzen 5 3550H with Radeon Vega Mobile Gfx
Logical processors: 8
Processor groups: 1
Processor group size: 8
RAM: 8001 MB total
_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed (WMI): 210 MHz
Reported CPU speed (registry): 2096 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): 973.90
Average measured interrupt to process latency (µs): 9.773857
Highest measured interrupt to DPC latency (µs): 948.50
Average measured interrupt to DPC latency (µs): 5.119205
_________________________________________________________________________________________________________
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): 79.701813
Driver with highest ISR routine execution time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation
Highest reported total ISR routine time (%): 0.003030
Driver with highest ISR total time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation
Total time spent in ISRs (%) 0.003035
ISR count (execution time <250 µs): 48313
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): 9799.706107
Driver with highest DPC routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Highest reported total DPC routine time (%): 0.081010
Driver with highest DPC total execution time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation
Total time spent in DPCs (%) 0.223401
DPC count (execution time <250 µs): 1071518
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-10000 µs): 1351
DPC count (execution time 1000-2000 µs): 2
DPC count (execution time 2000-4000 µs): 0
DPC count (execution time >=4000 µs): 1
_________________________________________________________________________________________________________
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: svchost.exe
Total number of hard pagefaults 46941
Hard pagefault count of hardest hit process: 12773
Number of processes hit: 130
_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 19.185323
CPU 0 ISR highest execution time (µs): 38.633588
CPU 0 ISR total execution time (s): 0.085573
CPU 0 ISR count: 28085
CPU 0 DPC highest execution time (µs): 9799.706107
CPU 0 DPC total execution time (s): 6.359687
CPU 0 DPC count: 645582
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 4.104458
CPU 1 ISR highest execution time (µs): 9.968989
CPU 1 ISR total execution time (s): 0.002848
CPU 1 ISR count: 1432
CPU 1 DPC highest execution time (µs): 1012.448473
CPU 1 DPC total execution time (s): 0.730761
CPU 1 DPC count: 100365
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 3.120721
CPU 2 ISR highest execution time (µs): 10.710401
CPU 2 ISR total execution time (s): 0.002598
CPU 2 ISR count: 1478
CPU 2 DPC highest execution time (µs): 688.852099
CPU 2 DPC total execution time (s): 0.424375
CPU 2 DPC count: 74451
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 2.83720
CPU 3 ISR highest execution time (µs): 11.281489
CPU 3 ISR total execution time (s): 0.002436
CPU 3 ISR count: 1395
CPU 3 DPC highest execution time (µs): 525.651240
CPU 3 DPC total execution time (s): 0.318873
CPU 3 DPC count: 38462
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 2.654769
CPU 4 ISR highest execution time (µs): 79.701813
CPU 4 ISR total execution time (s): 0.002639
CPU 4 ISR count: 1375
CPU 4 DPC highest execution time (µs): 490.394084
CPU 4 DPC total execution time (s): 0.338092
CPU 4 DPC count: 61478
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 2.174295
CPU 5 ISR highest execution time (µs): 11.121183
CPU 5 ISR total execution time (s): 0.002489
CPU 5 ISR count: 1281
CPU 5 DPC highest execution time (µs): 387.027195
CPU 5 DPC total execution time (s): 0.330932
CPU 5 DPC count: 50032
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 3.515165
CPU 6 ISR highest execution time (µs): 13.425573
CPU 6 ISR total execution time (s): 0.005644
CPU 6 ISR count: 2850
CPU 6 DPC highest execution time (µs): 380.494752
CPU 6 DPC total execution time (s): 0.414431
CPU 6 DPC count: 56764
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 2.443656
CPU 7 ISR highest execution time (µs): 13.625954
CPU 7 ISR total execution time (s): 0.020778
CPU 7 ISR count: 10417
CPU 7 DPC highest execution time (µs): 277.428435
CPU 7 DPC total execution time (s): 0.285578
CPU 7 DPC count: 45738
_________________________________________________________________________________________________________
Mr__Rabbit
05-19-2021, 02:44 PM #3okay i believe my os is upto date. thanks for quick response. but problem seems to persist. if u think i shouldnt post the whole report every time just let me know.
_________________________________________________________________________________________________________
CONCLUSION
_________________________________________________________________________________________________________
Your system appears to be having trouble handling real-time audio and other tasks. You are likely to experience buffer underruns appearing as drop outs, clicks or pops. 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:08:34 (h:mms) on all processors.
_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: LAPTOP-OB7RPSSD
OS version: Windows 11, 10.0, version 2009, build: 22631 (x64)
Hardware: TUF Gaming FX505DT_FX505DT, ASUSTeK COMPUTER INC.
BIOS: FX505DT.316
CPU: AuthenticAMD AMD Ryzen 5 3550H with Radeon Vega Mobile Gfx
Logical processors: 8
Processor groups: 1
Processor group size: 8
RAM: 8001 MB total
_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed (WMI): 210 MHz
Reported CPU speed (registry): 2096 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): 973.90
Average measured interrupt to process latency (µs): 9.773857
Highest measured interrupt to DPC latency (µs): 948.50
Average measured interrupt to DPC latency (µs): 5.119205
_________________________________________________________________________________________________________
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): 79.701813
Driver with highest ISR routine execution time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation
Highest reported total ISR routine time (%): 0.003030
Driver with highest ISR total time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation
Total time spent in ISRs (%) 0.003035
ISR count (execution time <250 µs): 48313
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): 9799.706107
Driver with highest DPC routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Highest reported total DPC routine time (%): 0.081010
Driver with highest DPC total execution time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation
Total time spent in DPCs (%) 0.223401
DPC count (execution time <250 µs): 1071518
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-10000 µs): 1351
DPC count (execution time 1000-2000 µs): 2
DPC count (execution time 2000-4000 µs): 0
DPC count (execution time >=4000 µs): 1
_________________________________________________________________________________________________________
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: svchost.exe
Total number of hard pagefaults 46941
Hard pagefault count of hardest hit process: 12773
Number of processes hit: 130
_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 19.185323
CPU 0 ISR highest execution time (µs): 38.633588
CPU 0 ISR total execution time (s): 0.085573
CPU 0 ISR count: 28085
CPU 0 DPC highest execution time (µs): 9799.706107
CPU 0 DPC total execution time (s): 6.359687
CPU 0 DPC count: 645582
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 4.104458
CPU 1 ISR highest execution time (µs): 9.968989
CPU 1 ISR total execution time (s): 0.002848
CPU 1 ISR count: 1432
CPU 1 DPC highest execution time (µs): 1012.448473
CPU 1 DPC total execution time (s): 0.730761
CPU 1 DPC count: 100365
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 3.120721
CPU 2 ISR highest execution time (µs): 10.710401
CPU 2 ISR total execution time (s): 0.002598
CPU 2 ISR count: 1478
CPU 2 DPC highest execution time (µs): 688.852099
CPU 2 DPC total execution time (s): 0.424375
CPU 2 DPC count: 74451
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 2.83720
CPU 3 ISR highest execution time (µs): 11.281489
CPU 3 ISR total execution time (s): 0.002436
CPU 3 ISR count: 1395
CPU 3 DPC highest execution time (µs): 525.651240
CPU 3 DPC total execution time (s): 0.318873
CPU 3 DPC count: 38462
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 2.654769
CPU 4 ISR highest execution time (µs): 79.701813
CPU 4 ISR total execution time (s): 0.002639
CPU 4 ISR count: 1375
CPU 4 DPC highest execution time (µs): 490.394084
CPU 4 DPC total execution time (s): 0.338092
CPU 4 DPC count: 61478
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 2.174295
CPU 5 ISR highest execution time (µs): 11.121183
CPU 5 ISR total execution time (s): 0.002489
CPU 5 ISR count: 1281
CPU 5 DPC highest execution time (µs): 387.027195
CPU 5 DPC total execution time (s): 0.330932
CPU 5 DPC count: 50032
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 3.515165
CPU 6 ISR highest execution time (µs): 13.425573
CPU 6 ISR total execution time (s): 0.005644
CPU 6 ISR count: 2850
CPU 6 DPC highest execution time (µs): 380.494752
CPU 6 DPC total execution time (s): 0.414431
CPU 6 DPC count: 56764
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 2.443656
CPU 7 ISR highest execution time (µs): 13.625954
CPU 7 ISR total execution time (s): 0.020778
CPU 7 ISR count: 10417
CPU 7 DPC highest execution time (µs): 277.428435
CPU 7 DPC total execution time (s): 0.285578
CPU 7 DPC count: 45738
_________________________________________________________________________________________________________
ISR (Interrupt Service Routine) is the front-end of device interrupts, these execute whenever the device interrupt occurs and are designed to run quickly, less than 25 microseconds ideally. Your latencymon output is showing that the longest running ISR ran for over 79 microseconds - this was the ISR for the Wdf01000.sys driver.
DPC (Deferred Procedure Call) is the back-end of device interrupts, these are queued (by the ISR) and they execute as a group when a processor is otherwise idle. A DPC should ideally run for no longer than 100 microseconds, but your latencymon output shows that your longest running DPC ran for almost 9800 microseconds (so this DPC is contributing most to your latency) - this was the DPC for the Wdf01000.sys driver.
You're also seeing a total of 46941 page faults in the 8 minutes and 34 seconds that latencymon was monitoring. - this is a much bigger number than would be expected. Hard page faults happen when a wanted page in RAM has been stolen (to make room for some other page) and copied out to the pagefile. When a thread references that page again it has to be paged back in - this is called a hard page fault - and that takes time (which you see as latency). This high number of hardpage faults indicates that you probably don't have enough RAM installed for the workload you're running. This is most likely the cause of the long running DPC if it's having to page in its pages.
How much RAM do you have installed? Can you open up Task Manager, click on the Performance tab, then click on the Memory icon on the left. Do this both at idle and when you have your maximum workload running. Post a screenshot of both displays.
FWIW. The Wdf01000.sys driver is the root driver for the Windows Driver Foundation (WDF). Many third-party drivers are written using WDF library calls and the Wdf01000.sys driver is called to manage these. Thus the long running DPC is probably a third-party driver that you don't see by name in the latencymon output.
I assume you know what latencymon does? It's looking at the longest ISR/DPC run times...
ISR (Interrupt Service Routine) is the front-end of device interrupts, these execute whenever the device interrupt occurs and are designed to run quickly, less than 25 microseconds ideally. Your latencymon output is showing that the longest running ISR ran for over 79 microseconds - this was the ISR for the Wdf01000.sys driver.
DPC (Deferred Procedure Call) is the back-end of device interrupts, these are queued (by the ISR) and they execute as a group when a processor is otherwise idle. A DPC should ideally run for no longer than 100 microseconds, but your latencymon output shows that your longest running DPC ran for almost 9800 microseconds (so this DPC is contributing most to your latency) - this was the DPC for the Wdf01000.sys driver.
You're also seeing a total of 46941 page faults in the 8 minutes and 34 seconds that latencymon was monitoring. - this is a much bigger number than would be expected. Hard page faults happen when a wanted page in RAM has been stolen (to make room for some other page) and copied out to the pagefile. When a thread references that page again it has to be paged back in - this is called a hard page fault - and that takes time (which you see as latency). This high number of hardpage faults indicates that you probably don't have enough RAM installed for the workload you're running. This is most likely the cause of the long running DPC if it's having to page in its pages.
How much RAM do you have installed? Can you open up Task Manager, click on the Performance tab, then click on the Memory icon on the left. Do this both at idle and when you have your maximum workload running. Post a screenshot of both displays.
FWIW. The Wdf01000.sys driver is the root driver for the Windows Driver Foundation (WDF). Many third-party drivers are written using WDF library calls and the Wdf01000.sys driver is called to manage these. Thus the long running DPC is probably a third-party driver that you don't see by name in the latencymon output.
I’m not sure how to upload photos here, though.
Here are some screenshots:
- Idle: https://prnt.sc/zyABZiWLqdr1
- Under load: https://prnt.sc/PrnAdUJsqtMC
For reference, the game I’ve been experiencing issues with is Path of Exile. It was the only one I downloaded after resetting my PC. There were some stutters, especially on YouTube, but that seems to have stopped before the reset. If you have any benchmarks or similar tests you think I should run, I’d be happy to do it.
I thought the RAM might be the problem, but I discounted it because it wasn’t listed in the diagnostics on whysoslow and latencymon. If this is true, fixing it should be straightforward.
I’m not sure how to upload photos here, though.
Here are some screenshots:
- Idle: https://prnt.sc/zyABZiWLqdr1
- Under load: https://prnt.sc/PrnAdUJsqtMC
For reference, the game I’ve been experiencing issues with is Path of Exile. It was the only one I downloaded after resetting my PC. There were some stutters, especially on YouTube, but that seems to have stopped before the reset. If you have any benchmarks or similar tests you think I should run, I’d be happy to do it.
CheeseHead_007
06-09-2021, 01:11 PM #8When RAM is insufficient, the 'under load' display will show two figures under the Committed section; 18.3/22.3GB. Committed bytes represent the memory Windows confirms processes can utilize, all of which must reside either in RAM or on the pagefile. The upper value indicates the maximum committed size at any given moment—the 22.3GB listed there equals the installed RAM (8GB) plus the current pagefile size (14.3GB). The lower figure shows how much memory Windows has already committed right now. This 18.3GB exceeds your installed RAM by 10.3GB, meaning 10.3GB remains actively used on the pagefile. When processes access this memory, those pages must be loaded from disk, contributing to latency.