Re: High DPC latency from NDIS.sys, storport.sys causing audio issues
FORGOT TO ADD: The rest of my information from LatencyMon
_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: JACK-PC
OS version: Windows 8 , 6.2, build: 9200 (x64)
Hardware: ASUSTeK COMPUTER INC., MAXIMUS IX HERO
CPU: GenuineIntel Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz
Logical processors: 8
Processor groups: 1
RAM: 16314 MB total
_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 4008.0 MHz
Measured CPU speed: 4442.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): 100604.794308
Average measured interrupt to process latency (µs): 13.272134
Highest measured interrupt to DPC latency (µs): 100603.005883
Average measured interrupt to DPC latency (µs): 12.168925
_________________________________________________________________________________________________________
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): 169.813373
Driver with highest ISR routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Highest reported total ISR routine time (%): 0.130820
Driver with highest ISR total time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Total time spent in ISRs (%) 0.175379
ISR count (execution time <250 µs): 42955
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-999 µs): 0
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): 100605.728792
Driver with highest DPC routine execution time: storport.sys - Microsoft Storage Port Driver, Microsoft Corporation
Highest reported total DPC routine time (%): 1.044303
Driver with highest DPC total execution time: storport.sys - Microsoft Storage Port Driver, Microsoft Corporation
Total time spent in DPCs (%) 1.353271
DPC count (execution time <250 µs): 161913
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 1
DPC count (execution time 1000-1999 µs): 1
DPC count (execution time 2000-3999 µs): 0
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.
Process with highest pagefault count: none
Total number of hard pagefaults 0
Hard pagefault count of hardest hit process: 0
Highest hard pagefault resolution time (µs): 0.0
Total time spent in hard pagefaults (%): 0.0
Number of processes hit: 0
_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 1.848425
CPU 0 ISR highest execution time (µs): 169.813373
CPU 0 ISR total execution time (s): 0.213931
CPU 0 ISR count: 36125
CPU 0 DPC highest execution time (µs): 100605.728792
CPU 0 DPC total execution time (s): 1.779832
CPU 0 DPC count: 117705
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 0.216796
CPU 1 ISR highest execution time (µs): 103.313872
CPU 1 ISR total execution time (s): 0.039533
CPU 1 ISR count: 6666
CPU 1 DPC highest execution time (µs): 100340.835329
CPU 1 DPC total execution time (s): 0.146228
CPU 1 DPC count: 7937
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 0.077867
CPU 2 ISR highest execution time (µs): 40.669162
CPU 2 ISR total execution time (s): 0.000581
CPU 2 ISR count: 134
CPU 2 DPC highest execution time (µs): 46.0
CPU 2 DPC total execution time (s): 0.023640
CPU 2 DPC count: 32814
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 0.045343
CPU 3 ISR highest execution time (µs): 3.514471
CPU 3 ISR total execution time (s): 0.000029
CPU 3 ISR count: 30
CPU 3 DPC highest execution time (µs): 58.888473
CPU 3 DPC total execution time (s): 0.001887
CPU 3 DPC count: 555
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 0.050103
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): 34.458333
CPU 4 DPC total execution time (s): 0.002499
CPU 4 DPC count: 906
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 0.049370
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): 26.509481
CPU 5 DPC total execution time (s): 0.001932
CPU 5 DPC count: 614
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 0.053046
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): 26.072355
CPU 6 DPC total execution time (s): 0.003076
CPU 6 DPC count: 952
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 0.042133
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): 15.846307
CPU 7 DPC total execution time (s): 0.001416
CPU 7 DPC count: 448
_________________________________________________________________________________________________________
Here are Screenshots as well of the Processes, Drivers, and CPU's data
CPU:
Imgur: The most awesome images on the Internet
Processes:
Imgur: The most awesome images on the Internet
Drivers:
Imgur: The most awesome images on the Internet
ALSO:
For some reason all of the latencymon-related software says I'm running Windows 8. I don't know why this is, I am running Windows 10 Home Edition. All of the other info seems to be accurate though.