[SOLVED] DCP latency

Mulnore · Dec 11, 2014

To be honest I am terrible at this kind of stuff

... Anyways I have been having trouble with youtube videos not working smoothly and games not running smoothly. I searched a bunch of different things on google and ended up getting process explorer. Process explorer told me system interrupts is giving me problems. So I googled a bunch about that and ended up getting latencymon. Now as far as I can tell latencymon is saying that liveupdate.exe is causing me problems while just browsing the net and that mmc.exe was causing me problems when I was playing urban terror(fps videogame).

This is at the time that mmc.exe was giving the most issues.
_________________________________________________________________________________________________________
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. Also one or more ISR 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:27:42 (h:mm:ss) on all processors.

_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: ACTIVITY
OS version: Windows 8 , 6.2, build: 9200 (x64)
Hardware: X551MA, ASUSTeK COMPUTER INC.
CPU: GenuineIntel Intel(R) Celeron(R) CPU N2815 @ 1.86GHz
Logical processors: 2
Processor groups: 1
RAM: 3967 MB total

_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 1867.0 MHz
Measured CPU speed: 4257.0 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.

_________________________________________________________________________________________________________
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): 134899.797906
Average measured interrupt to process latency (µs): 15.064577

Highest measured interrupt to DPC latency (µs): 25568.375065
Average measured interrupt to DPC latency (µs): 9.141051

_________________________________________________________________________________________________________
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): 3494.540975
Driver with highest ISR routine execution time: ndis.sys - Network Driver Interface Specification (NDIS), Microsoft Corporation

Highest reported total ISR routine time (%): 1.768822
Driver with highest ISR total time: ndis.sys - Network Driver Interface Specification (NDIS), Microsoft Corporation

Total time spent in ISRs (%) 1.813675

ISR count (execution time <250 µs): 166791
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-999 µs): 636
ISR count (execution time 1000-1999 µs): 33132
ISR count (execution time 2000-3999 µs): 299
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): 44203.968934
Driver with highest DPC routine execution time: ndis.sys - Network Driver Interface Specification (NDIS), Microsoft Corporation

Highest reported total DPC routine time (%): 0.687347
Driver with highest DPC total execution time: ndis.sys - Network Driver Interface Specification (NDIS), Microsoft Corporation

Total time spent in DPCs (%) 1.663139

DPC count (execution time <250 µs): 2835216
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 4372
DPC count (execution time 1000-1999 µs): 7516
DPC count (execution time 2000-3999 µs): 4262
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: mmc.exe

Total number of hard pagefaults 2494
Hard pagefault count of hardest hit process: 1315
Highest hard pagefault resolution time (µs): 1089624.521693
Total time spent in hard pagefaults (%): 1.478947
Number of processes hit: 27

_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 134.749092
CPU 0 ISR highest execution time (µs): 3494.540975
CPU 0 ISR total execution time (s): 60.309807
CPU 0 ISR count: 200858
CPU 0 DPC highest execution time (µs): 44203.968934
CPU 0 DPC total execution time (s): 54.681082
CPU 0 DPC count: 2794862
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 8.073368
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): 554.758436
CPU 1 DPC total execution time (s): 0.622977
CPU 1 DPC count: 58556
_________________________________________________________________________________________________________

And this is at the most recent one(just now) showing liveupdate.exe
_________________________________________________________________________________________________________
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. Also one or more ISR 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:52:19 (h:mm:ss) on all processors.

_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: ACTIVITY
OS version: Windows 8 , 6.2, build: 9200 (x64)
Hardware: X551MA, ASUSTeK COMPUTER INC.
CPU: GenuineIntel Intel(R) Celeron(R) CPU N2815 @ 1.86GHz
Logical processors: 2
Processor groups: 1
RAM: 3967 MB total

_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 1867.0 MHz
Measured CPU speed: 4257.0 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.

_________________________________________________________________________________________________________
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): 134899.797906
Average measured interrupt to process latency (µs): 13.731651

Highest measured interrupt to DPC latency (µs): 43615.833094
Average measured interrupt to DPC latency (µs): 8.038441

_________________________________________________________________________________________________________
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): 3494.540975
Driver with highest ISR routine execution time: ndis.sys - Network Driver Interface Specification (NDIS), Microsoft Corporation

Highest reported total ISR routine time (%): 1.350728
Driver with highest ISR total time: ndis.sys - Network Driver Interface Specification (NDIS), Microsoft Corporation

Total time spent in ISRs (%) 1.383596

ISR count (execution time <250 µs): 222544
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-999 µs): 846
ISR count (execution time 1000-1999 µs): 47564
ISR count (execution time 2000-3999 µs): 616
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): 107797.098018
Driver with highest DPC routine execution time: ndis.sys - Network Driver Interface Specification (NDIS), Microsoft Corporation

Highest reported total DPC routine time (%): 0.645617
Driver with highest DPC total execution time: ndis.sys - Network Driver Interface Specification (NDIS), Microsoft Corporation

Total time spent in DPCs (%) 1.513503

DPC count (execution time <250 µs): 5177948
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 10429
DPC count (execution time 1000-1999 µs): 12486
DPC count (execution time 2000-3999 µs): 8069
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: liveupdate.exe

Total number of hard pagefaults 3588
Hard pagefault count of hardest hit process: 1976
Highest hard pagefault resolution time (µs): 1089624.521693
Total time spent in hard pagefaults (%): 0.936601
Number of processes hit: 28

_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 217.698304
CPU 0 ISR highest execution time (µs): 3494.540975
CPU 0 ISR total execution time (s): 86.863460
CPU 0 ISR count: 271570
CPU 0 DPC highest execution time (µs): 107797.098018
CPU 0 DPC total execution time (s): 93.937241
CPU 0 DPC count: 5131321
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 15.353592
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): 625.478307
CPU 1 DPC total execution time (s): 1.081924
CPU 1 DPC count: 80558
_________________________________________________________________________________________________________

TomasD · Dec 11, 2014

Dear,

To properly troubleshoot issues with high/frequent DPCs/IRPs, we require a XPERF trace. Please follow these steps to generate one:

Download Windows Software Development Kit (SDK) for Windows and run the setup.
Select Windows Performance Toolkit feature (all the others can be unchecked) and proceed with the download/installation.
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.
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:
1. Run the following command which will stop the tracing:
  
  Code:
  
  xperf -stop
2. Run the following command to enable stack tracing (by disabling Paging Executive):
  
  Code:
  
  REG ADD "HKLM\System\CurrentControlSet\Control\Session Manager\Memory Management" -v DisablePagingExecutive -d 0x1 -t REG_DWORD -f
3. Reboot the computer
4. Once computer reboots, proceed from the step #3
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:
1. Run the following command to disable Driver Verifier, which causes the above error:
  
  Code:
  
  verifier /reset
2. Reboot the computer
3. Once computer reboots, proceed from the step #3
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:
Make sure you do not have any programs that capture ETW data already running. Some examples of these are:
- Process Explorer
- Process Hacker
- Resource Monitor
- Process Monitor
- Latency Monitor
- Another instance of XPERF or WPR
Perform some activities with your computer for few minutes, making sure the issues you reported are reproduced.
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
```
Compress file C:\CPU.etl
Upload the compressed file to a file sharing service (e.g. OneDrive or DropBox).
Share the download link here.

Thank you.

Mulnore · Dec 11, 2014

'xperf' is not recognized as an internal or external command, operable program or batch file.

I did install it though. It's at C:\Program Files (x86)\Windows Kits\8.1\Windows Performance Toolkit.

Mulnore · Dec 11, 2014

Lol well I thought about it and decided I should restart the computer and see if it kicks in and it did so I'll go a head and do all the stuff you said

Mulnore · Dec 11, 2014

Okay so when I went to do xperf -stop -d C:\CPU.etl I got xperf: error: NT Kernel Logger: The instance name passed was not recognized as valid by a WMI data provider. (0x1069).

TomasD · Dec 11, 2014

Mulnore said:
Okay so when I went to do xperf -stop -d C:\CPU.etl I got xperf: error: NT Kernel Logger: The instance name passed was not recognized as valid by a WMI data provider. (0x1069).

Was the command prompt opened as Administrator?

Mulnore · Dec 11, 2014

Yes. I was looking it up on google and found on another forum saying not to run process explorer or latencymon while wpa collects data. I didn't know at the time but I did run them. Not sure if that is the problem :/

TomasD · Dec 11, 2014

Mulnore said:
Yes. I was looking it up on google and found on another forum saying not to run process explorer or latencymon while wpa collects data. I didn't know at the time but I did run them. Not sure if that is the problem :/

It might. My first post also mentions that:

Code:

Make sure you do not have any programs that capture ETW data already running. Some examples of these are:

Process Explorer
Process Hacker
Resource Monitor
Process Monitor
Latency Monitor
Another instance of XPERF or WPR

Mulnore · Dec 11, 2014

Damn... I'll restart and see if I can try again

Mulnore · Dec 11, 2014

I didn't do as many things during the test this time but I sent it in pm.

TomasD · Dec 12, 2014

There seems to be an issue with your Qualcomm Atheros AR9485 WiFi network adapter or its drivers. Please try the following:

Download the latest driver from download2.dvd-driver.cz/atheros/drivers/ar5xxx/win81-10.0.0.298-whql.zip
Extract the download driver package to C:\Drivers.
Press WIN+R.
Type devmgmt.msc and press ENTER.
Find Qualcomm Atheros AR9485 Wireless Network Adapter under Network adapters.
Right-click on the device and select Update driver software....
Click Browse my computer for driver software.
Enter C:\Drivers in Search for driver software in this location field.
Click Next and wait for the driver to install.

Mulnore · Dec 12, 2014

Alright I did it. I'll go see if the problem is fixed.

TomasD · Dec 12, 2014

Mulnore said:
Alright I did it. I'll go see if the problem is fixed.

Make sure the computer gets rebooted prior.

Mulnore · Dec 12, 2014

That obviously improved things

. Still happens a bit and seems to be because of hard page faults.

TomasD · Dec 12, 2014

Mulnore said:
That obviously improved things . Still happens a bit and seems to be because of hard page faults.

So, can we consider the issue solved? :)

Mulnore · Dec 12, 2014

Yep thanks

Search

Search

[SOLVED] DCP latency

Mulnore

Member

TomasD

Sysnative Staff, BSOD Kernel Dump Senior Analyst

Mulnore

Member

Mulnore

Member

Mulnore

Member

TomasD

Sysnative Staff, BSOD Kernel Dump Senior Analyst

Mulnore

Member

TomasD

Sysnative Staff, BSOD Kernel Dump Senior Analyst

Mulnore

Member

Mulnore

Member

TomasD

Sysnative Staff, BSOD Kernel Dump Senior Analyst

Mulnore

Member

TomasD

Sysnative Staff, BSOD Kernel Dump Senior Analyst

Mulnore

Member

TomasD

Sysnative Staff, BSOD Kernel Dump Senior Analyst

Mulnore

Member