dxgkrnl.sys has a really high execution time. Second highest is nvlddmkm.sys.
dxgkrnl.sys : 2.177444ms
nvlddmkm.sys : .677997ms
Here you are:
_________________________________________________________________________________________________________
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 ISR 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 0:09:17 (h:mm:ss) on all processors.
_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: ---
OS version: Windows 7 Service Pack 1, 6.1, build: 7601 (x64)
Hardware: All Series, ASUS, ASUSTeK COMPUTER INC., Z97-A
CPU: GenuineIntel Intel(R) Core(TM) i5-4690 CPU @ 3.50GHz
Logical processors: 4
Processor groups: 1
RAM: 8135 MB total
_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 3506.0 MHz
Measured CPU speed: 4066.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): 978.114363
Average measured interrupt to process latency (µs): 1.159841
Highest measured interrupt to DPC latency (µs): 838.508909
Average measured interrupt to DPC latency (µs): 0.432205
_________________________________________________________________________________________________________
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): 2177.444096
Driver with highest ISR routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Highest reported total ISR routine time (%): 0.167265
Driver with highest ISR total time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Total time spent in ISRs (%) 0.244997
ISR count (execution time <250 µs): 1283990
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): 1
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): 677.996863
Driver with highest DPC routine execution time: nvlddmkm.sys - NVIDIA Windows Kernel Mode Driver, Version 344.11 , NVIDIA Corporation
Highest reported total DPC routine time (%): 0.206706
Driver with highest DPC total execution time: iusb3xhc.sys - Intel(R) USB 3.0 eXtensible Host Controller Driver, Intel Corporation
Total time spent in DPCs (%) 0.429929
DPC count (execution time <250 µs): 4779155
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 42
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.
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: msmpeng.exe
Total number of hard pagefaults 5630
Hard pagefault count of hardest hit process: 4709
Highest hard pagefault resolution time (µs): 12061.241015
Total time spent in hard pagefaults (%): 0.066489
Number of processes hit: 11
_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 24.850877
CPU 0 ISR highest execution time (µs): 2177.444096
CPU 0 ISR total execution time (s): 5.465895
CPU 0 ISR count: 1283991
CPU 0 DPC highest execution time (µs): 677.996863
CPU 0 DPC total execution time (s): 9.130630
CPU 0 DPC count: 4586072
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 4.763897
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): 94.660011
CPU 1 DPC total execution time (s): 0.290238
CPU 1 DPC count: 105309
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 5.413308
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): 85.095836
CPU 2 DPC total execution time (s): 0.080748
CPU 2 DPC count: 35933
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 2.214183
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): 104.825442
CPU 3 DPC total execution time (s): 0.090111
CPU 3 DPC count: 51883
_________________________________________________________________________________________________________
The thing highlighted is new and didn't happen before.
DirectX is a Windows thing. I haven't used Windows Update yet. Don't even know if I can update DirectX. Should I do that?
I should also say that before I even sent in my parts, reinstalling Windows has different results on lag spikes and all. I also need to install an update on my Samsung 840 EVO. Be back on that.
post edited by NarbiusTheGreat - 2014/11/11 17:24:53