Question LatencyMon shows high latency, and games are stuttering and lagging ?

[TiltedOne]

as my main pc has been put in for repairs i have brought out my laptop to try to play games to pass the time but it has been experiencing random freezes while playing and is very annoying. i have reinstalled windows and even upgraded to win 11. havent been seeming to have any audie troubles. would love any help in diagnosing/fixing the problem. if anymore information is needed in helping diagnose the problem would be happy to provide.

_________________________________________________________________________________________________________
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:15:17 (h:mm:ss) on all processors.


_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: LAPTOP-OB7RPSSD
OS version: Windows 11, 10.0, version 2009, build: 22621 (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): 1579.0
Average measured interrupt to process latency (µs): 16.937159

Highest measured interrupt to DPC latency (µs): 1565.90
Average measured interrupt to DPC latency (µs): 9.352748


_________________________________________________________________________________________________________
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): 367.379771
Driver with highest ISR routine execution time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation

Highest reported total ISR routine time (%): 0.025973
Driver with highest ISR total time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation

Total time spent in ISRs (%) 0.025984

ISR count (execution time <250 µs): 369459
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-1000 µs): 3
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): 8659.424141
Driver with highest DPC routine execution time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation

Highest reported total DPC routine time (%): 0.349177
Driver with highest DPC total execution time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation

Total time spent in DPCs (%) 0.782121

DPC count (execution time <250 µs): 2205062
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-10000 µs): 26036
DPC count (execution time 1000-2000 µs): 57
DPC count (execution time 2000-4000 µs): 4
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: memory compression

Total number of hard pagefaults 240284
Hard pagefault count of hardest hit process: 153805
Number of processes hit: 189


_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 82.483433
CPU 0 ISR highest execution time (µs): 367.379771
CPU 0 ISR total execution time (s): 0.332110
CPU 0 ISR count: 65673
CPU 0 DPC highest execution time (µs): 8659.424141
CPU 0 DPC total execution time (s): 25.924004
CPU 0 DPC count: 1200766
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 40.638209
CPU 1 ISR highest execution time (µs): 268.711832
CPU 1 ISR total execution time (s): 0.785253
CPU 1 ISR count: 124031
CPU 1 DPC highest execution time (µs): 3278.033874
CPU 1 DPC total execution time (s): 21.099520
CPU 1 DPC count: 376962
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 13.248165
CPU 2 ISR highest execution time (µs): 88.197996
CPU 2 ISR total execution time (s): 0.165892
CPU 2 ISR count: 29111
CPU 2 DPC highest execution time (µs): 1367.324427
CPU 2 DPC total execution time (s): 4.491871
CPU 2 DPC count: 166149
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 7.948725
CPU 3 ISR highest execution time (µs): 115.520038
CPU 3 ISR total execution time (s): 0.042953
CPU 3 ISR count: 10102
CPU 3 DPC highest execution time (µs): 480.875954
CPU 3 DPC total execution time (s): 1.200240
CPU 3 DPC count: 127562
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 9.122828
CPU 4 ISR highest execution time (µs): 100.631679
CPU 4 ISR total execution time (s): 0.045119
CPU 4 ISR count: 9369
CPU 4 DPC highest execution time (µs): 737.695134
CPU 4 DPC total execution time (s): 0.936656
CPU 4 DPC count: 99368
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 8.403714
CPU 5 ISR highest execution time (µs): 96.774332
CPU 5 ISR total execution time (s): 0.046771
CPU 5 ISR count: 10076
CPU 5 DPC highest execution time (µs): 728.407443
CPU 5 DPC total execution time (s): 0.899923
CPU 5 DPC count: 84295
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 8.322350
CPU 6 ISR highest execution time (µs): 87.446565
CPU 6 ISR total execution time (s): 0.084974
CPU 6 ISR count: 20799
CPU 6 DPC highest execution time (µs): 666.860210
CPU 6 DPC total execution time (s): 0.902364
CPU 6 DPC count: 81379
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 10.608196
CPU 7 ISR highest execution time (µs): 167.198473
CPU 7 ISR total execution time (s): 0.403649
CPU 7 ISR count: 100301
CPU 7 DPC highest execution time (µs): 1451.895515
CPU 7 DPC total execution time (s): 1.937429
CPU 7 DPC count: 94679
_________________________________________________________________________________________________________

 

[Lutfij]

Welcome to the forums, newcomer!

First,
BIOS: FX505DT.316
You seem to be on the latest BIOS version.

Second,
OS version: Windows 11, 10.0, version 2009, build: 22621 (x64)
you have an update pending for your OS.

 

[TiltedOne]

okay 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:mm:ss) 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
_________________________________________________________________________________________________________

 

[Phillip Corcoran]

okay 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.

Please don't keep posting that long report with your replies. No need. It will only make this thread ridiculously long.

 

[TiltedOne]

Please don't keep posting that long report with your replies. No need. It will only make this thread ridiculously long.

will do.

 

[ubuysa]

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.

 

[TiltedOne]

hmm i thought ram could be the issue but guess i discounted it due to it not being in any of the diagnostics in whysoslow and latencymon. if this is the case will be easy enough to fix.

not really sure how to put photos on here so.

idle screenshot: https://prnt.sc/zyABZiWLqdr1
under load screenshot: https://prnt.sc/PrnAdUJsqtMC

ohh and for reference the game i have been having troubles with. since its the only thing i have downloaded since resetting the pc is Path of Exile. although it was also having some troubles/ expierencing some stuttering on something as simple as youtube. albiet that was before the reset i believe. if there is any benchmarks or anything like that you believe i should download/run. would be more than willing to do that.

 

[ubuysa]

You are short of RAM. If you look at the 'under load' screen shot you'll see two numbers under the Committed heading; 18.3/22.3GB. Committed bytes is memory that Windows has confirmed that processes can use, and all that memory must either be in RAM or on the pagefile. The right-hand number is the maximum number of bytes that can be committed at any one time in this system - the 22.3GB shown there is the installed RAM (8GB) plus the current size of the pagefile (14.3GB). The left-hand number is the key one; this is the amount of memory that Windows has committed at the moment. That 18.3GB is 10.3GB larger than your installed RAM, so 10.3GB of actively used memory is on the pagefile. When processes reference that memory those pages will have to be paged in, and that's what causes your latency.

Adding another 8GB will help, but even then you'll have 2.3GB of active memory bytes on the pagefile, so you'll still be paging (though much less so). For the workload you have you really need 24GB or even 32GB of RAM, but I wouldn't recommend you install that because your CPU is also bottle-necked.

You're simply running more work that the PC can cope with.