New
#11
Hey there.
Apologies this took so long, I don't have much time to test things at the moment.
I ran Latency Mon after doing a clean boot, and the were no issues.
I have not installed the latest version of Latency Mon before running the test, so the reported version is still incorrect, and I also managed to forget to actually plug in and test a headset while the GPU was disconnected, but Latency Mon showed that the latency dropped by about a half (less than it did in a clean boot though).Code:_________________________________________________________________________________________________________ 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:05:00 (h:mm:ss) on all processors. _________________________________________________________________________________________________________ SYSTEM INFORMATION _________________________________________________________________________________________________________ Computer name: NEXUS OS version: Windows 10 , 10.0, build: 17763 (x64) Hardware: ASUSTeK COMPUTER INC., Z170-A CPU: GenuineIntel Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz Logical processors: 8 Processor groups: 1 RAM: 16250 MB total _________________________________________________________________________________________________________ CPU SPEED _________________________________________________________________________________________________________ Reported CPU speed: 4008 MHz 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. WARNING: the CPU speed that was measured is only a fraction of the CPU speed reported. Your CPUs may be throttled back due to variable speed settings and thermal issues. It is suggested that you run a utility which reports your actual CPU frequency and temperature. _________________________________________________________________________________________________________ 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): 219,50 Average measured interrupt to process latency (µs): 2,382541 Highest measured interrupt to DPC latency (µs): 217,80 Average measured interrupt to DPC latency (µs): 0,922613 _________________________________________________________________________________________________________ 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): 178,867515 Driver with highest ISR routine execution time: HDAudBus.sys - High Definition Audio Bus Driver, Microsoft Corporation Highest reported total ISR routine time (%): 0,006468 Driver with highest ISR total time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation Total time spent in ISRs (%) 0,010711 ISR count (execution time <250 µs): 15323 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): 176,206337 Driver with highest DPC routine execution time: ndis.sys - Network Driver Interface Specification (NDIS), Microsoft Corporation Highest reported total DPC routine time (%): 0,005417 Driver with highest DPC total execution time: nvlddmkm.sys - NVIDIA Windows Kernel Mode Driver, Version 418.91 , NVIDIA Corporation Total time spent in DPCs (%) 0,010648 DPC count (execution time <250 µs): 78045 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. 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: ekrn.exe Total number of hard pagefaults 2205 Hard pagefault count of hardest hit process: 1408 Number of processes hit: 20 _________________________________________________________________________________________________________ PER CPU DATA _________________________________________________________________________________________________________ CPU 0 Interrupt cycle time (s): 1,919010 CPU 0 ISR highest execution time (µs): 178,867515 CPU 0 ISR total execution time (s): 0,257086 CPU 0 ISR count: 15323 CPU 0 DPC highest execution time (µs): 176,206337 CPU 0 DPC total execution time (s): 0,211360 CPU 0 DPC count: 54477 _________________________________________________________________________________________________________ CPU 1 Interrupt cycle time (s): 0,109661 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): 48,823603 CPU 1 DPC total execution time (s): 0,003026 CPU 1 DPC count: 1767 _________________________________________________________________________________________________________ CPU 2 Interrupt cycle time (s): 0,144890 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): 147,309381 CPU 2 DPC total execution time (s): 0,004283 CPU 2 DPC count: 2460 _________________________________________________________________________________________________________ CPU 3 Interrupt cycle time (s): 0,139947 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): 62,015968 CPU 3 DPC total execution time (s): 0,004228 CPU 3 DPC count: 2069 _________________________________________________________________________________________________________ CPU 4 Interrupt cycle time (s): 0,152524 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): 80,319361 CPU 4 DPC total execution time (s): 0,021373 CPU 4 DPC count: 12201 _________________________________________________________________________________________________________ CPU 5 Interrupt cycle time (s): 0,125982 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): 104,880739 CPU 5 DPC total execution time (s): 0,002079 CPU 5 DPC count: 866 _________________________________________________________________________________________________________ CPU 6 Interrupt cycle time (s): 0,161630 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): 47,785679 CPU 6 DPC total execution time (s): 0,004977 CPU 6 DPC count: 2321 _________________________________________________________________________________________________________ CPU 7 Interrupt cycle time (s): 0,14010 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): 71,981038 CPU 7 DPC total execution time (s): 0,004239 CPU 7 DPC count: 1884 _________________________________________________________________________________________________________
Code:_________________________________________________________________________________________________________ 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:10:00 (h:mm:ss) on all processors. _________________________________________________________________________________________________________ SYSTEM INFORMATION _________________________________________________________________________________________________________ Computer name: NEXUS OS version: Windows 10 , 10.0, build: 17763 (x64) Hardware: ASUSTeK COMPUTER INC., Z170-A CPU: GenuineIntel Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz Logical processors: 8 Processor groups: 1 RAM: 16250 MB total _________________________________________________________________________________________________________ CPU SPEED _________________________________________________________________________________________________________ Reported CPU speed: 4008 MHz 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. WARNING: the CPU speed that was measured is only a fraction of the CPU speed reported. Your CPUs may be throttled back due to variable speed settings and thermal issues. It is suggested that you run a utility which reports your actual CPU frequency and temperature. _________________________________________________________________________________________________________ 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): 2834,50 Average measured interrupt to process latency (µs): 2,161013 Highest measured interrupt to DPC latency (µs): 2826,10 Average measured interrupt to DPC latency (µs): 0,744220 _________________________________________________________________________________________________________ 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): 2903,960329 Driver with highest ISR routine execution time: HDAudBus.sys - High Definition Audio Bus Driver, Microsoft Corporation Highest reported total ISR routine time (%): 0,012680 Driver with highest ISR total time: HDAudBus.sys - High Definition Audio Bus Driver, Microsoft Corporation Total time spent in ISRs (%) 0,013207 ISR count (execution time <250 µs): 86560 ISR count (execution time 250-500 µs): 0 ISR count (execution time 500-999 µs): 2 ISR count (execution time 1000-1999 µs): 1 ISR count (execution time 2000-3999 µs): 2 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): 2895,987774 Driver with highest DPC routine execution time: ndis.sys - Network Driver Interface Specification (NDIS), Microsoft Corporation Highest reported total DPC routine time (%): 0,009048 Driver with highest DPC total execution time: rspLLL64.sys - Resplendence Latency Monitoring and Auxiliary Kernel Library, Resplendence Software Projects Sp. Total time spent in DPCs (%) 0,030128 DPC count (execution time <250 µs): 1190415 DPC count (execution time 250-500 µs): 0 DPC count (execution time 500-999 µs): 15 DPC count (execution time 1000-1999 µs): 6 DPC count (execution time 2000-3999 µs): 4 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: ekrn.exe Total number of hard pagefaults 35025 Hard pagefault count of hardest hit process: 14611 Number of processes hit: 67 _________________________________________________________________________________________________________ PER CPU DATA _________________________________________________________________________________________________________ CPU 0 Interrupt cycle time (s): 7,449469 CPU 0 ISR highest execution time (µs): 2903,960329 CPU 0 ISR total execution time (s): 0,632595 CPU 0 ISR count: 86533 CPU 0 DPC highest execution time (µs): 2895,987774 CPU 0 DPC total execution time (s): 1,179187 CPU 0 DPC count: 1100042 _________________________________________________________________________________________________________ CPU 1 Interrupt cycle time (s): 1,632037 CPU 1 ISR highest execution time (µs): 148,895459 CPU 1 ISR total execution time (s): 0,001334 CPU 1 ISR count: 24 CPU 1 DPC highest execution time (µs): 296,011727 CPU 1 DPC total execution time (s): 0,028071 CPU 1 DPC count: 9125 _________________________________________________________________________________________________________ CPU 2 Interrupt cycle time (s): 1,795906 CPU 2 ISR highest execution time (µs): 1,488024 CPU 2 ISR total execution time (s): 0,000006 CPU 2 ISR count: 8 CPU 2 DPC highest execution time (µs): 1023,033683 CPU 2 DPC total execution time (s): 0,075737 CPU 2 DPC count: 30683 _________________________________________________________________________________________________________ CPU 3 Interrupt cycle time (s): 1,736178 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): 674,429142 CPU 3 DPC total execution time (s): 0,018273 CPU 3 DPC count: 5677 _________________________________________________________________________________________________________ CPU 4 Interrupt cycle time (s): 1,879017 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): 870,378992 CPU 4 DPC total execution time (s): 0,048207 CPU 4 DPC count: 16464 _________________________________________________________________________________________________________ CPU 5 Interrupt cycle time (s): 1,741878 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): 2169,021707 CPU 5 DPC total execution time (s): 0,027992 CPU 5 DPC count: 8270 _________________________________________________________________________________________________________ CPU 6 Interrupt cycle time (s): 1,876470 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): 938,541168 CPU 6 DPC total execution time (s): 0,040019 CPU 6 DPC count: 12191 _________________________________________________________________________________________________________ CPU 7 Interrupt cycle time (s): 1,787245 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): 210,237525 CPU 7 DPC total execution time (s): 0,028661 CPU 7 DPC count: 7988 _________________________________________________________________________________________________________
Quote
