Ndis.sys very high latency Windows 10 Acer Aspire (log in comments)

_________________________________________________________________________________________________________ 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. 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:02:30 (h:mm:ss) on all processors.

_________________________________________________________________________________________________________ SYSTEM INFORMATION _________________________________________________________________________________________________________ Computer name: HARRYPC OS version: Windows 8 , 6.2, build: 9200 (x64) Hardware: Aspire E5-551G, Acer, EA50_KV CPU: AuthenticAMD AMD A8-7100 Radeon R5, 8 Compute Cores 4C+4G Logical processors: 4 Processor groups: 1 RAM: 7114 MB total

_________________________________________________________________________________________________________ CPU SPEED _________________________________________________________________________________________________________ Reported CPU speed: 1797 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 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): 8275.145894 Average measured interrupt to process latency (µs): 9.704171

Highest measured interrupt to DPC latency (µs): 592.181044 Average measured interrupt to DPC latency (µs): 3.708639

_________________________________________________________________________________________________________ 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): 125.229827 Driver with highest ISR routine execution time: USBPORT.SYS - USB 1.1 & 2.0 Port Driver, Microsoft Corporation

Highest reported total ISR routine time (%): 0.013756 Driver with highest ISR total time: USBPORT.SYS - USB 1.1 & 2.0 Port Driver, Microsoft Corporation

Total time spent in ISRs (%) 0.016280

ISR count (execution time <250 µs): 14529 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): 1137.716750 Driver with highest DPC routine execution time: ndis.sys - Network Driver Interface Specification (NDIS), Microsoft Corporation

Highest reported total DPC routine time (%): 0.240660 Driver with highest DPC total execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

Total time spent in DPCs (%) 0.820938

DPC count (execution time <250 µs): 480244 DPC count (execution time 250-500 µs): 0 DPC count (execution time 500-999 µs): 724 DPC count (execution time 1000-1999 µs): 1 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 958 Hard pagefault count of hardest hit process: 417 Highest hard pagefault resolution time (µs): 110597.124096 Total time spent in hard pagefaults (%): 0.673826 Number of processes hit: 12

_________________________________________________________________________________________________________ PER CPU DATA _________________________________________________________________________________________________________ CPU 0 Interrupt cycle time (s): 7.956011 CPU 0 ISR highest execution time (µs): 125.229827 CPU 0 ISR total execution time (s): 0.087312 CPU 0 ISR count: 12892 CPU 0 DPC highest execution time (µs): 479.811909 CPU 0 DPC total execution time (s): 3.759267 CPU 0 DPC count: 417059 _________________________________________________________________________________________________________ CPU 1 Interrupt cycle time (s): 1.784714 CPU 1 ISR highest execution time (µs): 70.725097 CPU 1 ISR total execution time (s): 0.007391 CPU 1 ISR count: 1132 CPU 1 DPC highest execution time (µs): 868.975515 CPU 1 DPC total execution time (s): 0.674955 CPU 1 DPC count: 36271 _________________________________________________________________________________________________________ CPU 2 Interrupt cycle time (s): 1.369076 CPU 2 ISR highest execution time (µs): 11.473567 CPU 2 ISR total execution time (s): 0.001033 CPU 2 ISR count: 153 CPU 2 DPC highest execution time (µs): 926.596550 CPU 2 DPC total execution time (s): 0.310532 CPU 2 DPC count: 16148 _________________________________________________________________________________________________________ CPU 3 Interrupt cycle time (s): 1.239792 CPU 3 ISR highest execution time (µs): 11.529215 CPU 3 ISR total execution time (s): 0.002096 CPU 3 ISR count: 352 CPU 3 DPC highest execution time (µs): 1137.716750 CPU 3 DPC total execution time (s): 0.188557 CPU 3 DPC count: 11491 _________________________________________________________________________________________________________

From my limited knowledge, this is related to the wifi drivers yeah?

Windows already tells me I have the newest ones, should I look to older drivers?

The log report was from LatencyMon - funny it reads my system as windows 8? It's certainly 10.

Thanks in advance team