My audio was working before updating windows (update released on Oct 27 apparently). Afterwards, I would get static and popping. Audio would quickly desync from the video. I tried updating sound driver, uninstalling and restarting etc.. I did some research and found latencymon to identify which drivers are causing the latency.
The highest on the ISR + DPC count is USBPORT.SYS, dxgkrnl.sys, ataport.sys, and ndis.sys (in that order highest to lowest).
The highest execution column has ndis.sys, nvlddmkm.sys, dxgkrnl.sys, USBPORT.SYS, in that order.
I really don't know what all this means beyond that these drivers appear to be causing the issues, which didn't occur before I updated windows. I don't know how to fix these issues. Should I simply uninstall the updates? (for some reason the PC doesn't have restore state enabled)
Could there be a virus that windows defender is simply missing? I'll try running a different anti-virus in the meantime. Below is the stats tab in the spoiler.
The highest on the ISR + DPC count is USBPORT.SYS, dxgkrnl.sys, ataport.sys, and ndis.sys (in that order highest to lowest).
The highest execution column has ndis.sys, nvlddmkm.sys, dxgkrnl.sys, USBPORT.SYS, in that order.
I really don't know what all this means beyond that these drivers appear to be causing the issues, which didn't occur before I updated windows. I don't know how to fix these issues. Should I simply uninstall the updates? (for some reason the PC doesn't have restore state enabled)
Could there be a virus that windows defender is simply missing? I'll try running a different anti-virus in the meantime. Below is the stats tab in the spoiler.
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:24 (h:mm:ss) on all processors.
_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: BLUE
OS version: Windows 8 , 6.2, build: 9200 (x64)
Hardware: G31M-ES2L, Gigabyte Technology Co., Ltd., G31M-S2L
CPU: GenuineIntel Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz
Logical processors: 2
Processor groups: 1
RAM: 4094 MB total
_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 30 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.
_________________________________________________________________________________________________________
MEASURED INTERRUPT TO DPC LATENCIES
_________________________________________________________________________________________________________
The interrupt to DPC latency reflects the measured interval in which a DPC could execute in response to a hardware request from the moment the interrupt service routine started execution.
Highest measured interrupt to DPC latency (µs): 12737.870812
Average measured interrupt to DPC latency (µs): 2.893017
_________________________________________________________________________________________________________
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): 12787.1610
Driver with highest ISR routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Highest reported total ISR routine time (%): 0.139639
Driver with highest ISR total time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Total time spent in ISRs (%) 0.159360
ISR count (execution time <250 µs): 115089
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-999 µs): 270
ISR count (execution time 1000-1999 µs): 91
ISR count (execution time 2000-3999 µs): 47
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): 23033.5050
Driver with highest DPC routine execution time: ndis.sys - Network Driver Interface Specification (NDIS), Microsoft Corporation
Highest reported total DPC routine time (%): 0.049682
Driver with highest DPC total execution time: nvlddmkm.sys - NVIDIA Windows Kernel Mode Driver, Version 342.00 , NVIDIA Corporation
Total time spent in DPCs (%) 0.264250
DPC count (execution time <250 µs): 848040
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 56
DPC count (execution time 1000-1999 µs): 15
DPC count (execution time 2000-3999 µs): 7
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 372
Hard pagefault count of hardest hit process: 256
Highest hard pagefault resolution time (µs): 100002.030
Total time spent in hard pagefaults (%): 0.166318
Number of processes hit: 4
_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 7.913307
CPU 0 ISR highest execution time (µs): 12787.1610
CPU 0 ISR total execution time (s): 1.958982
CPU 0 ISR count: 108518
CPU 0 DPC highest execution time (µs): 23033.5050
CPU 0 DPC total execution time (s): 3.050806
CPU 0 DPC count: 805952
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 0.781754
CPU 1 ISR highest execution time (µs): 10716.3540
CPU 1 ISR total execution time (s): 0.032914
CPU 1 ISR count: 7028
CPU 1 DPC highest execution time (µs): 11745.0930
CPU 1 DPC total execution time (s): 0.252157
CPU 1 DPC count: 42183
_________________________________________________________________________________________________________
_________________________________________________________________________________________________________
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:24 (h:mm:ss) on all processors.
_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: BLUE
OS version: Windows 8 , 6.2, build: 9200 (x64)
Hardware: G31M-ES2L, Gigabyte Technology Co., Ltd., G31M-S2L
CPU: GenuineIntel Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz
Logical processors: 2
Processor groups: 1
RAM: 4094 MB total
_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 30 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.
_________________________________________________________________________________________________________
MEASURED INTERRUPT TO DPC LATENCIES
_________________________________________________________________________________________________________
The interrupt to DPC latency reflects the measured interval in which a DPC could execute in response to a hardware request from the moment the interrupt service routine started execution.
Highest measured interrupt to DPC latency (µs): 12737.870812
Average measured interrupt to DPC latency (µs): 2.893017
_________________________________________________________________________________________________________
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): 12787.1610
Driver with highest ISR routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Highest reported total ISR routine time (%): 0.139639
Driver with highest ISR total time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Total time spent in ISRs (%) 0.159360
ISR count (execution time <250 µs): 115089
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-999 µs): 270
ISR count (execution time 1000-1999 µs): 91
ISR count (execution time 2000-3999 µs): 47
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): 23033.5050
Driver with highest DPC routine execution time: ndis.sys - Network Driver Interface Specification (NDIS), Microsoft Corporation
Highest reported total DPC routine time (%): 0.049682
Driver with highest DPC total execution time: nvlddmkm.sys - NVIDIA Windows Kernel Mode Driver, Version 342.00 , NVIDIA Corporation
Total time spent in DPCs (%) 0.264250
DPC count (execution time <250 µs): 848040
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 56
DPC count (execution time 1000-1999 µs): 15
DPC count (execution time 2000-3999 µs): 7
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 372
Hard pagefault count of hardest hit process: 256
Highest hard pagefault resolution time (µs): 100002.030
Total time spent in hard pagefaults (%): 0.166318
Number of processes hit: 4
_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 7.913307
CPU 0 ISR highest execution time (µs): 12787.1610
CPU 0 ISR total execution time (s): 1.958982
CPU 0 ISR count: 108518
CPU 0 DPC highest execution time (µs): 23033.5050
CPU 0 DPC total execution time (s): 3.050806
CPU 0 DPC count: 805952
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 0.781754
CPU 1 ISR highest execution time (µs): 10716.3540
CPU 1 ISR total execution time (s): 0.032914
CPU 1 ISR count: 7028
CPU 1 DPC highest execution time (µs): 11745.0930
CPU 1 DPC total execution time (s): 0.252157
CPU 1 DPC count: 42183
_________________________________________________________________________________________________________
Facebook
Twitter
Instagram