LatencyMon Result

[GoodMan.]

Hello and Good day to you all.​

I need help interpreting these results and what to repair/ignore.

my build:

CPU: Intel i7 8700k

MOBO: Asus Maximus x hero (Wifi-AC)

RAM: Corsair Vengeance LPX 16 GB DDR4-3200

GPU: EVGA GTX 1080 Ti SC2

PSU: EVGA - SuperNOVA G2 750W

OS: WIN 10 x64




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


_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: PC
OS version: Windows 10 , 10.0, version 1903, build: 18362 (x64)
Hardware: ASUSTeK COMPUTER INC., ROG MAXIMUS X HERO (WI-FI AC)
CPU: GenuineIntel Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz
Logical processors: 12
Processor groups: 1
RAM: 16313 MB total


_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 3696 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): 2071.90
Average measured interrupt to process latency (µs): 3.096056

Highest measured interrupt to DPC latency (µs): 2070.20
Average measured interrupt to DPC latency (µs): 1.230796


_________________________________________________________________________________________________________
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): 586.695887
Driver with highest ISR routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

Highest reported total ISR routine time (%): 0.243930
Driver with highest ISR total time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

Total time spent in ISRs (%) 0.286470

ISR count (execution time <250 µs): 92840050
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-999 µs): 11
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): 2827.898810
Driver with highest DPC routine execution time: nvlddmkm.sys - NVIDIA Windows Kernel Mode Driver, Version 431.36 , NVIDIA Corporation

Highest reported total DPC routine time (%): 0.097373
Driver with highest DPC total execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

Total time spent in DPCs (%) 0.230622

DPC count (execution time <250 µs): 173897284
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 276
DPC count (execution time 1000-1999 µs): 22
DPC count (execution time 2000-3999 µs): 4
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 173941
Hard pagefault count of hardest hit process: 74264
Number of processes hit: 182


_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 1992.251865
CPU 0 ISR highest execution time (µs): 586.695887
CPU 0 ISR total execution time (s): 883.739807
CPU 0 ISR count: 92839801
CPU 0 DPC highest execution time (µs): 2827.898810
CPU 0 DPC total execution time (s): 653.111258
CPU 0 DPC count: 164617428
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 348.634024
CPU 1 ISR highest execution time (µs): 46.461580
CPU 1 ISR total execution time (s): 0.003277
CPU 1 ISR count: 260
CPU 1 DPC highest execution time (µs): 240.179113
CPU 1 DPC total execution time (s): 50.031847
CPU 1 DPC count: 7156096
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 136.989660
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): 203.024351
CPU 2 DPC total execution time (s): 2.810776
CPU 2 DPC count: 550848
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 120.837654
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): 191.775433
CPU 3 DPC total execution time (s): 0.185986
CPU 3 DPC count: 68132
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 145.661527
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): 193.856061
CPU 4 DPC total execution time (s): 0.826034
CPU 4 DPC count: 258004
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 127.261935
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): 191.449134
CPU 5 DPC total execution time (s): 0.219231
CPU 5 DPC count: 77661
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 147.947412
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): 191.147186
CPU 6 DPC total execution time (s): 0.681206
CPU 6 DPC count: 221097
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 119.570503
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): 187.454545
CPU 7 DPC total execution time (s): 0.208534
CPU 7 DPC count: 73025
_________________________________________________________________________________________________________
CPU 8 Interrupt cycle time (s): 157.674932
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): 192.794913
CPU 8 DPC total execution time (s): 1.022010
CPU 8 DPC count: 301286
_________________________________________________________________________________________________________
CPU 9 Interrupt cycle time (s): 144.925175
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): 190.758658
CPU 9 DPC total execution time (s): 0.661832
CPU 9 DPC count: 200595
_________________________________________________________________________________________________________
CPU 10 Interrupt cycle time (s): 159.883249
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): 189.706169
CPU 10 DPC total execution time (s): 1.147820
CPU 10 DPC count: 272854
_________________________________________________________________________________________________________
CPU 11 Interrupt cycle time (s): 123.578044
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): 191.382035
CPU 11 DPC total execution time (s): 0.550534
CPU 11 DPC count: 100560
_________________________________________________________________________________________________________

 

[cwsink]

Hi GoodMan. - Are you experiencing symptoms of DPC latency (audio pops, audio/video stutters, etc) ? The way DPCs and ISRs are processed in Windows has changed and it doesn't seem like LatencyMon has kept up with the changes. It has its uses still but if you're looking for help based on what LatencyMon says about the system rather than what you're experiencing while using it this may be a red herring.

 

[GoodMan.]

I am experiencing micro-stutters, mouse latency, and sometime flickering. Graphics in games blurred and pixelated even on ultra settings. and Input delay/lag that Is not due keyboard, mouse, monitor.
Playing on this PC been like playing on my old Dell laptop but the difference is more fps.

 

[cwsink]

Many people have reported such problems with the 1809 and 1903 updates and I've seen people claim it's due to changes in the Window memory manager. I can see that you're having some higher than ideal DPC processing time which could be causing the symptoms you've described but it depends on which core they are running. We'd need to analyze a trace of your system running and experiencing the problems to hopefully see what's causing it. The directions for doing so are here so if you'd like us to have a look please follow those instructions and make the trace available via a cloud drive or file sharing service; they are typically too big to attach to a post. Also, please add "-stop" to the final command so that it looks like this before executing it:

xperf -stop -d "%userprofile%\Desktop\trace.etl"

 

[GoodMan.]

I have been struggling to make the trace; I typed xperf -on DiagEasy waited for like 4 hours then I typed xperf -d %userprofile%\Desktop\trace.etl ( I renamed "userprofile" to my username);
I encounter this error xperf: error: Merge ETL: The system cannot find the path specified. (0x3).
I am stuck at this error; I tried a code I found while trying to troubleshoot the error WPA %userprofile%\Desktop\trace.etl the result was the following files were not found

 

[cwsink]

You should be able to copy and paste the commands without changing anything. You're opening an elevated command prompt terminal window and executing the commands from it? It shows "Administrator" at the beginning of the window title?

 

[GoodMan.]

Thought I had to change it to my username haha, It works but I'll start it again and let it stutter again and will share the trace.
thank you again

 

[GoodMan.]

when I added the final command xperf -stop -d "%userprofile%\Desktop\trace.etl" It showed xperf: error: NT Kernel Logger: The instance name passed was not recognized as valid by a WMI data provider. (0x1069).

 

[cwsink]

Perhaps you have a tool that is also running a trace. If you still have LatencyMon installed please try uninstalling it and rebooting the system. If you have any other performance monitoring tools you should also disable or uninstall those as well. After doing so, please try capturing another trace.

How long does it take for a the issues to happen? I ask because the recording settings from the link might generate a huge file if it takes a while. I'm not sure if it's constantly recording to a file on disk or if it's in memory as a circular buffer. I have a script which can do the latter if needed.

 

[GoodMan.]

Immediately after I typed the code in It showed the error code. Just to get my confusion out of the way; am I supposed to be type in first xperf -d %userprofile%\Desktop\trace.etl then type in xperf -stop -d "%userprofile%\Desktop\trace.etl" ?. Because I did that.

 

[cwsink]

No, just use the:

xperf -stop -d "%userprofile%\Desktop\trace.etl"

to end the trace. "-stop" was left out of the trace instructions at the link for some reason and it may not be necessary but the examples I've seen always include it.

 

[GoodMan.]

trace.etl

 

[cwsink]

I'm not sure if there's a problem with the file or it's just overwhelming my computer but WPA keeps crashing when I try to load the file. It could be that it's just too big. I've got a script that will capture a trace and keep the size between 200 and 300MB. You'll need to extract it from the attached zip and copy it to your Desktop. Right-click that icon and select Run as administrator, Yes to the UAC prompt, and that should bring up a command prompt window. Press a key to start the trace and if it's in the correct state while tracing it should look like this:


Leave it running in the background and use the computer as you normally would. When the problem occurs go back to the command prompt window and press a key to stop the trace (you need to make the command prompt window the active window.) The trace keeps at least the last 30 seconds of activity so there's no rush. The text in the windows should look like this:

if you've successfully told it to stop. The window will close and a new trace.etl file should appear on your Desktop. Please make that new trace available for download.

 

[GoodMan.]

trace.etl

 

[cwsink]

I'll have a look and get back. In the meantime you might want to have a look at this post to see if it's about what you're experiencing. Windows 10 1803 seemed to introduce a stuttering problem for quite a few people and it has supposedly been traced back to how Windows 10 managed standby memory. Things will be fine but then Windows decides it's time to free up standby memory which ends up causing noticeable stuttering until it finishes. I think a person in the thread created a program that supposedly improves the situation but I haven't tried it myself.

 

[cwsink]

Going by the latest trace I don't see any individual DPC problem. Not a single DPC went over 1ms on any core. The highest was .71ms which is not great but not considered glitch inducing. It would be bad if that was the typical amount of time running a DPC but it isn't. I see a few spikes towards the end of the trace where quite a few DPCs took over a core that was previously running a Warframe owned thread. That basically means the Warframe thread would be frozen until the DPCs finished. I don't see any of those individually taking longer than normal but all of them running one after the other might have starved Warframe of CPU time for longer than usual.

The driver iusb3xhc.sys seems to have generated quite a few DPCs during that time period. You might want to check to see if a newer version is available.

 

[GoodMan.]

I tried the memory fixes; Unfortunately It didn't help at all there is still stuttery movement while I'm I am in game and moving my mouse left and right It isn't smooth at all, and there is still the delay in rendering objects.

 

[cwsink]

I really don't see anything that suggests you should be having issues due to DPC latency. General suggestions would be to:

• Update your motherboard to the latest UEFI/BIOS. You're currently a few versions behind.
• Check for and install any driver updates (the Intel USB 3.0 driver, for example)
• Distribute any USB devices/peripherals across the USB controllers; for example, I'd put mouse and keyboard on USB 2.0 ports and other USB devices on the 3.0 and 3.1 ports based on the bandwidth they require. Basically trying to minimize contention for CPU attention on a bus.
• Undo any overclocking if the above doesn't make a difference.

 

[GoodMan.]

Tried all of the above. And the problem still persists... Maybe I will try and RMA the Motherboard and GPU and see how that goes wish me luck!
Thank you cwsink for your input and your effort I appreciate what you have done.

 

[cwsink]

I'm sorry none of my suggestions helped. Does Warframe have a benchmark that tests the GPU and/or CPU? I'm wondering if the stuttering shows up while you're not using any input devices.