this is what DPC latency said:
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): 1634.494396
Average measured interrupt to process latency (µs): 8.223537
Highest measured interrupt to DPC latency (µs): 264.877622
Average measured interrupt to DPC latency (µs): 3.002724
_________________________________________________________________________________________________________
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): 56.978024
Driver with highest ISR routine execution time: HDAudBus.sys - High Definition Audio Bus Driver, Microsoft Corporation
Highest reported total ISR routine time (%): 0.112855
Driver with highest ISR total time: hal.dll - Hardware Abstraction Layer DLL, Microsoft Corporation
Total time spent in ISRs (%) 0.139656
ISR count (execution time <250 µs): 186923
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): 144.744449
Driver with highest DPC routine execution time: netbt.sys - MBT Transport driver, Microsoft Corporation
Highest reported total DPC routine time (%): 0.256292
Driver with highest DPC total execution time: USBPORT.SYS - USB 1.1 & 2.0 Port Driver, Microsoft Corporation
Total time spent in DPCs (%) 0.510596
DPC count (execution time <250 µs): 952624
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 0
DPC count (execution time 1000-1999 µs): 0
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: latmon.exe
Total number of hard pagefaults 59
Hard pagefault count of hardest hit process: 19
Highest hard pagefault resolution time (µs): 1792.760761
Total time spent in hard pagefaults (%): 0.002957
Number of processes hit: 5
