Here is the output I have from LatencyMon
-----------------------------------_________________________________________________________________________________________________________
CONCLUSION
_________________________________________________________________________________________________________
Your system appears to be suitable for handling real-time audio and other tasks without dropouts.
LatencyMon has been analyzing your system for 0:07:56 (h:mm:ss) on all processors.
_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: TX
OS version: Windows 7 Service Pack 1, 6.1, build: 7601 (x64)
Hardware: MS-7759, MSI, Z77MA-G45 (MS-7759)
CPU: GenuineIntel Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz
Logical processors: 4
Processor groups: 1
RAM: 8145 MB total
_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 3400,0 MHz
Measured CPU speed: 2146,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): 638,176123
Average measured interrupt to process latency (µs): 0,949978
Highest measured interrupt to DPC latency (µs): 516,504036
Average measured interrupt to DPC latency (µs): 0,386753
_________________________________________________________________________________________________________
MEASURED SMI, IPI AND CPU STALLS
_________________________________________________________________________________________________________
The SMI, IPI and CPU stalls value represents the highest measured interval that a CPU did not respond while having its maskable interrupts disabled.
Highest measured SMI or CPU stall (µs) 0,602337
_________________________________________________________________________________________________________
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): 114,327059
Driver with highest ISR routine execution time: ataport.SYS - ATAPI Driver Extension, Microsoft Corporation
Highest reported total ISR routine time (%): 0,095519
Driver with highest ISR total time: hal.dll - Hardware Abstraction Layer DLL, Microsoft Corporation
Total time spent in ISRs (%) 0,229420
ISR count (execution time <250 µs): 852854
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): 707,470588
Driver with highest DPC routine execution time: nvlddmkm.sys - NVIDIA Windows Kernel Mode Driver, Version 320.49 , NVIDIA Corporation
Highest reported total DPC routine time (%): 0,033608
Driver with highest DPC total execution time: nvlddmkm.sys - NVIDIA Windows Kernel Mode Driver, Version 320.49 , NVIDIA Corporation
Total time spent in DPCs (%) 0,092404
DPC count (execution time <250 µs): 1548438
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 15
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: chrome.exe
Total number of hard pagefaults 143
Hard pagefault count of hardest hit process: 60
Highest hard pagefault resolution time (µs): 69777,395882
Total time spent in hard pagefaults (%): 0,013192
Number of processes hit: 4
_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 6,917476
CPU 0 ISR highest execution time (µs): 114,327059
CPU 0 ISR total execution time (s): 4,368309
CPU 0 ISR count: 852854
CPU 0 DPC highest execution time (µs): 707,470588
CPU 0 DPC total execution time (s): 1,597647
CPU 0 DPC count: 1528991
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 0,648682
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): 111,698824
CPU 1 DPC total execution time (s): 0,040535
CPU 1 DPC count: 2593
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 0,536743
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): 74,421176
CPU 2 DPC total execution time (s): 0,058106
CPU 2 DPC count: 4183
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 0,503725
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): 64,154118
CPU 3 DPC total execution time (s): 0,063144
CPU 3 DPC count: 12686
_________________________________________________________________________________________________________
-------------------------------------
Total execution times are very high for nvidia, directx, atapi and hardware abstraction layer, is this a problem???
System:
-Corsair Carbide Series 200r Case (with only default in and out fans)
-Z77ma-g45
-intel i5 3570k -no OC
-asus gtx 660 DirectCu II -no OC
-Kingston genesis hyperx 1600 mhz CL9 2x4096 MB
-Highpower elements 700w 80+ bronze
-Western Digital Caviar Black 500 gb
-THERMALTAKE CONTAC30 LGA775/1155/1156/1366/2011 & AM2/AM2+/AM3/AM3+/FM1 CPU COOLER
I also have a wireless mouse lag/unresponsiveness issue with my logitech m195 and m235 mouses regardless of which usb slot I plug it into. This problem ceases when using a PS2 mouse.
Here is the report after 5 minutes of gaming: (it got worse)
-----------------------------------_________________________________________________________________________________________________________
CONCLUSION
_________________________________________________________________________________________________________
Your system appears to be suitable for handling real-time audio and other tasks without dropouts.
LatencyMon has been analyzing your system for 0:07:56 (h:mm:ss) on all processors.
_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: TX
OS version: Windows 7 Service Pack 1, 6.1, build: 7601 (x64)
Hardware: MS-7759, MSI, Z77MA-G45 (MS-7759)
CPU: GenuineIntel Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz
Logical processors: 4
Processor groups: 1
RAM: 8145 MB total
_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 3400,0 MHz
Measured CPU speed: 2146,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): 638,176123
Average measured interrupt to process latency (µs): 0,949978
Highest measured interrupt to DPC latency (µs): 516,504036
Average measured interrupt to DPC latency (µs): 0,386753
_________________________________________________________________________________________________________
MEASURED SMI, IPI AND CPU STALLS
_________________________________________________________________________________________________________
The SMI, IPI and CPU stalls value represents the highest measured interval that a CPU did not respond while having its maskable interrupts disabled.
Highest measured SMI or CPU stall (µs) 0,602337
_________________________________________________________________________________________________________
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): 114,327059
Driver with highest ISR routine execution time: ataport.SYS - ATAPI Driver Extension, Microsoft Corporation
Highest reported total ISR routine time (%): 0,095519
Driver with highest ISR total time: hal.dll - Hardware Abstraction Layer DLL, Microsoft Corporation
Total time spent in ISRs (%) 0,229420
ISR count (execution time <250 µs): 852854
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): 707,470588
Driver with highest DPC routine execution time: nvlddmkm.sys - NVIDIA Windows Kernel Mode Driver, Version 320.49 , NVIDIA Corporation
Highest reported total DPC routine time (%): 0,033608
Driver with highest DPC total execution time: nvlddmkm.sys - NVIDIA Windows Kernel Mode Driver, Version 320.49 , NVIDIA Corporation
Total time spent in DPCs (%) 0,092404
DPC count (execution time <250 µs): 1548438
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 15
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: chrome.exe
Total number of hard pagefaults 143
Hard pagefault count of hardest hit process: 60
Highest hard pagefault resolution time (µs): 69777,395882
Total time spent in hard pagefaults (%): 0,013192
Number of processes hit: 4
_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 6,917476
CPU 0 ISR highest execution time (µs): 114,327059
CPU 0 ISR total execution time (s): 4,368309
CPU 0 ISR count: 852854
CPU 0 DPC highest execution time (µs): 707,470588
CPU 0 DPC total execution time (s): 1,597647
CPU 0 DPC count: 1528991
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 0,648682
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): 111,698824
CPU 1 DPC total execution time (s): 0,040535
CPU 1 DPC count: 2593
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 0,536743
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): 74,421176
CPU 2 DPC total execution time (s): 0,058106
CPU 2 DPC count: 4183
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 0,503725
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): 64,154118
CPU 3 DPC total execution time (s): 0,063144
CPU 3 DPC count: 12686
_________________________________________________________________________________________________________
-------------------------------------
Total execution times are very high for nvidia, directx, atapi and hardware abstraction layer, is this a problem???
System:
-Corsair Carbide Series 200r Case (with only default in and out fans)
-Z77ma-g45
-intel i5 3570k -no OC
-asus gtx 660 DirectCu II -no OC
-Kingston genesis hyperx 1600 mhz CL9 2x4096 MB
-Highpower elements 700w 80+ bronze
-Western Digital Caviar Black 500 gb
-THERMALTAKE CONTAC30 LGA775/1155/1156/1366/2011 & AM2/AM2+/AM3/AM3+/FM1 CPU COOLER
I also have a wireless mouse lag/unresponsiveness issue with my logitech m195 and m235 mouses regardless of which usb slot I plug it into. This problem ceases when using a PS2 mouse.
Here is the report after 5 minutes of gaming: (it got worse)
Facebook
Twitter
Instagram