High latency causing audio and video lag

jldkrocks

New member
Joined
Aug 27, 2015
Posts
2
So i upgraded to windows 10 and started having this problem

Here are the results from latency mon(I know it says windows 8 but thats a problem with latencymon)

_________________________________________________________________________________________________________
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. At least one detected problem appears to be network related. In case you are using a WLAN adapter, try disabling it to get better results. 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:04:31 (h:mm:ss) on all processors.




_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: DESKTOP-PREPIJL
OS version: Windows 8 , 6.2, build: 9200 (x64)
Hardware: GA-78LMT-USB3, Gigabyte Technology Co., Ltd.
CPU: AuthenticAMD AMD FX(tm)-4100 Quad-Core Processor
Logical processors: 4
Processor groups: 1
RAM: 8189 MB total




_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 3616 MHz
Measured CPU speed: 19 MHz (approx.)


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): 54580.540264
Average measured interrupt to process latency (µs): 9.748752


Highest measured interrupt to DPC latency (µs): 38178.315959
Average measured interrupt to DPC latency (µs): 3.960919




_________________________________________________________________________________________________________
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): 369.851493
Driver with highest ISR routine execution time: ataport.SYS - ATAPI Driver Extension, Microsoft Corporation


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


Total time spent in ISRs (%) 0.454655


ISR count (execution time <250 µs): 466002
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-999 µs): 110
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): 53997.761062
Driver with highest DPC routine execution time: ndis.sys - Network Driver Interface Specification (NDIS), Microsoft Corporation


Highest reported total DPC routine time (%): 0.198931
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.644909


DPC count (execution time <250 µs): 1253701
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 151
DPC count (execution time 1000-1999 µs): 33
DPC count (execution time 2000-3999 µs): 5
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 242
Hard pagefault count of hardest hit process: 112
Highest hard pagefault resolution time (µs): 318461.282909
Total time spent in hard pagefaults (%): 0.155351
Number of processes hit: 10




_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 19.130286
CPU 0 ISR highest execution time (µs): 369.851493
CPU 0 ISR total execution time (s): 4.822631
CPU 0 ISR count: 444780
CPU 0 DPC highest execution time (µs): 53997.761062
CPU 0 DPC total execution time (s): 6.494742
CPU 0 DPC count: 1199651
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 2.908814
CPU 1 ISR highest execution time (µs): 296.499447
CPU 1 ISR total execution time (s): 0.094658
CPU 1 ISR count: 11692
CPU 1 DPC highest execution time (µs): 400.824668
CPU 1 DPC total execution time (s): 0.201285
CPU 1 DPC count: 16142
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 2.423557
CPU 2 ISR highest execution time (µs): 60.238938
CPU 2 ISR total execution time (s): 0.005292
CPU 2 ISR count: 2202
CPU 2 DPC highest execution time (µs): 113.320243
CPU 2 DPC total execution time (s): 0.167613
CPU 2 DPC count: 21409
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 2.728221
CPU 3 ISR highest execution time (µs): 12.535122
CPU 3 ISR total execution time (s): 0.007317
CPU 3 ISR count: 7438
CPU 3 DPC highest execution time (µs): 108.000553
CPU 3 DPC total execution time (s): 0.129207
CPU 3 DPC count: 16707
_________________________________________________________________________________________________________

Thats after around 5 minutes but after 10 minutes the up got over 600000 ups

Thanks in advance :D
 
I would like to look into a ETL trace:

  1. Download Windows Software Development Kit (SDK) for Windows and run the setup.
  2. Select Windows Performance Toolkit feature (all the others can be unchecked) and proceed with the download/installation.
  3. Once the installation finishes, open an elevated Command Prompt by right-clicking on CMD.EXE shortcut in your start menu and selecting Run As Administrator from the context menu.
  4. Type the following command, which will start tracing, in the Command Prompt window you just opened:
    Code:
    xperf -on PROC_THREAD+LOADER+PROFILE+INTERRUPT+DPC+DRIVERS+POWER+IDLE_STATES -stackwalk Profile -BufferSize 1024 -MinBuffers 256 -MaxBuffers 256 -MaxFile 256 -FileMode Circular
    If you see a yellow warning "xperf: warning: This system is not fully configured for x64 stack tracing" after running the above command, please complete these extra steps (otherwise, proceed to the step #5):
    Read More:
    If you see a red error "xperf: error: NT Kernel Logger: A device attached to the system is not functioning. (0x1f)" after running the above command, please complete these extra steps (otherwise, proceed to the step #5):
    Read More:

    If you see a red error "xperf: error: NT Kernel Logger: Cannot create a file when that file already exists. (0xb7)", please do the following (otherwise, proceed to the step #5):
    Read More:
  5. Perform some activities with your computer for few minutes, making sure the issues you reported are reproduced.
  6. Run the following command, which will stop the tracing, in the command prompt window you already have opened:
    Code:
    xperf -stop -d C:\CPU.etl
  7. Compress file C:\CPU.etl
  8. Upload the compressed file to a file sharing service (e.g. OneDrive or DropBox).
  9. Share the download link here.
 

Thank you. I can see that there are huge DPCs in the network subsystem. Anyhow, I cannot get the call stack for the CPU (0), which is experiencing these issue. It is really strange, and it is possible there is some issue with the latest version of XPERF I am using. I will try checking the trace using an older version of the tool later today. Meanwhile, if you could generate a new trace to rule out the issue being with the trace itself, I would appreciate is as well.
 

Thank you. I can see that there are huge DPCs in the network subsystem. Anyhow, I cannot get the call stack for the CPU (0), which is experiencing these issue. It is really strange, and it is possible there is some issue with the latest version of XPERF I am using. I will try checking the trace using an older version of the tool later today. Meanwhile, if you could generate a new trace to rule out the issue being with the trace itself, I would appreciate is as well.

Just tried it with the older version of the WPA, anyhow, the information is still missing
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top