Windows 10: High DPC latency (especially ndis.sys and tpip.sys)

I've had a problem with DPC latency for several months (craks/pops/random dropouts when listening to music/sound). I recently found out about LatencyMon and let it run for about 15 minutes. The result is pasted below. I'd appreciate if you could suggest what to do next.
Am I correct in understanding that the latency caused by ndis.sys and tpip.sys happens because I'm using a WiFi network?

Thanks in advance for your help.

LatencyMon result:






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:15:17 (h:mm:ss) on all processors.


____________________________________________________________________________________________________ _____
SYSTEM INFORMATION
____________________________________________________________________________________________________ _____
Computer name: LAPTOP-C6TE2AP4
OS version: Windows 10 , 10.0, build: 15063 (x64)
Hardware: Aspire E5-575, Acer, Ironman_SK
CPU: GenuineIntel Intel(R) Core(TM) i3-6100U CPU @ 2.30GHz
Logical processors: 4
Processor groups: 1
RAM: 6017 MB total


____________________________________________________________________________________________________ _____
CPU SPEED
____________________________________________________________________________________________________ _____
Reported CPU speed: 2304 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): 75946.154715
Average measured interrupt to process latency (µs): 8.786541

Highest measured interrupt to DPC latency (µs): 74260.822879
Average measured interrupt to DPC latency (µs): 4.782860


____________________________________________________________________________________________________ _____
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): 105.132813
Driver with highest ISR routine execution time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation

Highest reported total ISR routine time (%): 0.033725
Driver with highest ISR total time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation

Total time spent in ISRs (%) 0.033726

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

Highest reported total DPC routine time (%): 0.586483
Driver with highest DPC total execution time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation

Total time spent in DPCs (%) 1.143568

DPC count (execution time <250 µs): 3934747
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 4763
DPC count (execution time 1000-1999 µs): 151
DPC count (execution time 2000-3999 µs): 1095
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.


Process with highest pagefault count: none

Total number of hard pagefaults 0
Hard pagefault count of hardest hit process: 0
Highest hard pagefault resolution time (µs): 0.0
Total time spent in hard pagefaults (%): 0.0
Number of processes hit: 0


____________________________________________________________________________________________________ _____
PER CPU DATA
____________________________________________________________________________________________________ _____
CPU 0 Interrupt cycle time (s): 48.232684
CPU 0 ISR highest execution time (µs): 95.488715
CPU 0 ISR total execution time (s): 0.721241
CPU 0 ISR count: 230747
CPU 0 DPC highest execution time (µs): 64763.179688
CPU 0 DPC total execution time (s): 31.977599
CPU 0 DPC count: 3560952
____________________________________________________________________________________________________ _____
CPU 1 Interrupt cycle time (s): 24.089196
CPU 1 ISR highest execution time (µs): 105.132813
CPU 1 ISR total execution time (s): 0.515896
CPU 1 ISR count: 174985
CPU 1 DPC highest execution time (µs): 28784.198785
CPU 1 DPC total execution time (s): 5.299618
CPU 1 DPC count: 152982
____________________________________________________________________________________________________ _____
CPU 2 Interrupt cycle time (s): 12.957132
CPU 2 ISR highest execution time (µs): 5.555556
CPU 2 ISR total execution time (s): 0.000017
CPU 2 ISR count: 6
CPU 2 DPC highest execution time (µs): 19072.513889
CPU 2 DPC total execution time (s): 3.140433
CPU 2 DPC count: 164741
____________________________________________________________________________________________________ _____
CPU 3 Interrupt cycle time (s): 12.520489
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): 19002.136285
CPU 3 DPC total execution time (s): 1.531277
CPU 3 DPC count: 62538

I have had this same issue for ages, no help about other than the usual - update everything. It doesn't work. There is definitely a conflict somewhere between the sound driver and network drivers NDIS and TCIP. Who knows how to fix it, i dont know. I have looked for ages.