ndis.sys causing really high DPC latency

[KusoH]

My audio has been cracking for a while, I saw that LatencyMon would help me to identify the problem and the driver that causes the highest latency... I really need help with this.

 

[KusoH]

By the way, here's the LatencyMon log

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




_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: OSCAR
OS version: Windows 10 , 10.0, build: 14393 (x64)
Hardware: ASUSTeK Computer INC., P5N-E SLI
CPU: GenuineIntel Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz
Logical processors: 4
Processor groups: 1
RAM: 8190 MB total




_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 240 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): 42329,125936
Average measured interrupt to process latency (µs): 10,020414


Highest measured interrupt to DPC latency (µs): 20647,865005
Average measured interrupt to DPC latency (µs): 3,650880




_________________________________________________________________________________________________________
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): 233,5650
Driver with highest ISR routine execution time: storport.sys - Microsoft Storage Port Driver, Microsoft Corporation


Highest reported total ISR routine time (%): 0,072675
Driver with highest ISR total time: storport.sys - Microsoft Storage Port Driver, Microsoft Corporation


Total time spent in ISRs (%) 0,141963


ISR count (execution time <250 µs): 2078719
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): 45307,350
Driver with highest DPC routine execution time: ndis.sys - Especificación de interfaz de controlador de red (NDIS), Microsoft Corporation


Highest reported total DPC routine time (%): 0,31660
Driver with highest DPC total execution time: ndis.sys - Especificación de interfaz de controlador de red (NDIS), Microsoft Corporation


Total time spent in DPCs (%) 1,130381


DPC count (execution time <250 µs): 10374927
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 53254
DPC count (execution time 1000-1999 µs): 529
DPC count (execution time 2000-3999 µs): 36
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: tiworker.exe


Total number of hard pagefaults 47789
Hard pagefault count of hardest hit process: 30903
Highest hard pagefault resolution time (µs): 1026107,265417
Total time spent in hard pagefaults (%): 1,802359
Number of processes hit: 34




_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 159,005093
CPU 0 ISR highest execution time (µs): 233,5650
CPU 0 ISR total execution time (s): 11,047162
CPU 0 ISR count: 1897935
CPU 0 DPC highest execution time (µs): 45307,350
CPU 0 DPC total execution time (s): 82,757061
CPU 0 DPC count: 9828644
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 39,620647
CPU 1 ISR highest execution time (µs): 172,20750
CPU 1 ISR total execution time (s): 1,381585
CPU 1 ISR count: 172625
CPU 1 DPC highest execution time (µs): 10199,43750
CPU 1 DPC total execution time (s): 11,254105
CPU 1 DPC count: 385667
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 32,523636
CPU 2 ISR highest execution time (µs): 38,40750
CPU 2 ISR total execution time (s): 0,035825
CPU 2 ISR count: 8131
CPU 2 DPC highest execution time (µs): 1692,93750
CPU 2 DPC total execution time (s): 2,831512
CPU 2 DPC count: 111618
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 29,555742
CPU 3 ISR highest execution time (µs): 7,29750
CPU 3 ISR total execution time (s): 0,000108
CPU 3 ISR count: 28
CPU 3 DPC highest execution time (µs): 1771,38750
CPU 3 DPC total execution time (s): 2,407617
CPU 3 DPC count: 102835
_________________________________________________________________________________________________________

 

[xilolee]

Preamble

Read More:

In case you don't know how to open an elevated command prompt in windows 10, these are the available methods:

• Right-click windows start, click command prompt (admin), click yes on the user account control window that should appear (if you didn't disabled UAC)
• click start, click windows system, right-click the command prompt in the list, click run as administrator, click yes on the user account control window that should appear (if you didn't disabled UAC)
• click start, type directly cmd (or prompt), right-click the command prompt in the list of results, click run as administrator, click yes on the user account control window that should appear (if you didn't disabled UAC)
• The same of above is valid if you do it in the searchbox (Cortana)
• click start, type directly cmd (or prompt), (the command prompt should already be the first hit in the list of results), press and keep pressed (hold) ctrl + shift Keys on your keyboard, then press enter, click yes on the user account control window that should appear (if you didn't disabled UAC)
• The same of above is valid if you do it in the searchbox (Cortana)

Would you try these steps?

• Left-click on Start, type directly msconfig, press enter.
  Is the radio button on normal startup?
• Advanced disk cleanup with cleanmgr:
  • Open an elevated command prompt
  • Type cleanmgr /sageset:1 and press enter.
  • Select all the options, or leave unticked the ones you prefer.
  • Type cleanmgr /sagerun:1 and press enter
  • Let it work until it finishes.
• Launch this command from an elevated command prompt:

  dism /online /cleanup-image /checkhealth

  Do you get my same result?
  Read More:

  C:\>dism /online /cleanup-image /checkhealth
  Deployment Image Servicing and Management tool
  Version: 10.0.14393.0
  Image Version: 10.0.14393.0
  No component store corruption detected.
  The operation completed successfully.

  If yes, go to the next point.
  If no:
  Read More:

  try to run this command from an elevated command prompt and let it work until it finishes (it could last from 10 to 60 minutes):

  dism /online /cleanup-image /restorehealth

• Launch this command from an elevated command prompt and let it work until it finishes (it could last from 10 to 60 minutes):

  sfc /scannow

  If you get the following message:

  Windows Resource Protection found corrupt files but was unable to fix some of them. Details are included in the CBS.Log %WinDir%\Logs\CBS\CBS.log

  Read Windows Update Forum Posting Instructions (click) and provide the necessary (and missing) informations to the experts. I.e., you should:
  • export and zip/compress the entire CBS folder on your desktop
  • open a new topic in the windows update sub-forum (in sysnative.com)
  • attach that zipped file to that new topic
  If the CBS compressed folder will be too large, you can check the second post on that thread (to use the sfcfix tool with a script) or you can use a (possibly fast) web service like MS OneDrive, Google Drive, DropBox, Box, Mega, Apple iCloud, Amazon Cloud Drive, and so forth...
  Instead if you get the following messages, go to the next step:

  Windows Resource Protection did not find any integrity violations
  Windows Resource Protection found corrupt files and successfully repaired them. Details are included in the CBS.Log %WinDir%\Logs\CBS\CBS.log

• Defragment your system drive (using windows default defragmenter). Steps:
  • Open an elevated command prompt
  • Type defrag c: /h and press enter
  • Wait until it finishes
• Check your system partition, then post the result here. Steps:
  • Open an elevated command prompt.
  • Type chkdsk c: /b and press enter.
  • You'll get:

    The type of the file system is NTFS.
    Cannot lock current drive.
    Chkdsk cannot run because the volume is in use by another
    process. Would you like to schedule this volume to be
    checked the next time the system restarts? (Y/N)

  • Type Y and press enter.
  • Then restart/reboot and wait until it finishes this check.
  • To find chkdsk result:
    • Open an elevated command prompt
    • Copy/paste this command and press enter:

      wevtutil qe application /c:1 /rd:true  /f:text /q:"*[System[Provider[(@Name='Microsoft-Windows-Wininit')]]]" > "%userprofile%\desktop\ChkDskLOG.txt" & notepad "%userprofile%\desktop\ChkDskLOG.txt"

    • It should create chkdsklog.txt on your desktop and open it: paste its content here.
    • If the command won't work, type eventvwr, press enter, in the event viewer window double-left-click Windows Logs to expand it, left-click Application, double-left-click the information event with source wininit, copy its content and post it here.

---

If the problem persists:

• Please provide answers for (answer the best that you can):
  • System Manufacturer?
  • Laptop or Desktop?
  • Exact model number (if laptop, check label on bottom)
  • OS ? (Windows 10, 8.1, 8, 7, Vista)
  • x86 (32bit) or x64 (64bit)?
  • Service pack?
  • What was original installed OS on system?
  • Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)?
  • Age of system? (hardware)
  • Age of OS installation?
  • Have you re-installed the OS?
  • CPU
  • RAM (brand, model, which slots are you using?)
  • Video Card
  • MotherBoard - (if NOT a laptop)
  • Power Supply - brand & wattage (if laptop, skip this one)
  • What security software are you using? (Firewall, antivirus, antimalware, antispyware, and so forth)
  • Are you using proxy, vpn, ipfilters or similar software?
  • Are you using Disk Image tools? (like daemon tools, alcohol 52% or 120%, virtual CloneDrive, roxio software)
  • Are you currently under/overclocking? Are there overclocking software installed on your system?

• Retrieve System Information, using speccy
  1. Download Speccy portable - current version 1.30.730 (click), unzip/decompress it and put it on your desktop.
  2. When the program opens, it will retrieve some information regarding your system.
  3. Once it's done, select the File menu and choose Publish snapshot. Answer Yes to the confirmation message.
     (Or generate a log in your pc, if you prefer to not publish the snapshot for some reason)
  4. On the next screen that comes up, choose the Copy to Clipboard button and paste this link in your next reply.
     (Or upload here the generated log, in case you didn't publish the snapshot)

• Provide the SysnativeFileCollectionApp.zip
  Check the first four steps in Blue Screen of Death (BSOD) Posting Instructions (click).
  You can skip the perfmon report, if it shows problems (it is problematic for many users, starting from windows 8 to 10).

• Facultative System information log (if previous point fails for some obscure reason)
  The following command should generate a log, named MsInfo.nfo, on your desktop, after some time (few seconds or minutes).
  Upload it here when windows finished its creation.
  It obviously should be run from an elevated command prompt:

  msinfo32 /nfo msinfo32 /nfo "%userprofile%\desktop\MsInfo.nfo"

• Download and install the Windows Performance Toolkit on dev.windows.com - Windows Software Development Kit (SDK) for Windows 10 - sdksetup.exe 1.12MB (click):
  Read More:

  Click Download (adksetup.exe), save/run it and you'll see for first Specify location: leave it default or choose your preferred location, then click Next.

  Read More:

  

  Then you'll see Windows kits privacy: Niemiro said "you may opt in to CEIP if you so wish - it is not necessary, but you may wish to do so". Then click Next.

  Read More:

  

  Then you'll see License agreement: click Accept.

  Read More:

  

  Then you'll see Select the features you want to install: select only Windows Performance Toolkit and click Install.

  Read More:

  
  Then open an elevated command prompt and launch these commands:
  Read More:

  
  

  1. Set the path environment variable adding the windows performance toolkit path:

     SET PATH=%PATH%;C:\Program Files (x86)\Windows Kits\10\Windows Performance Toolkit\

     If you have chosen another path in specify location, you should provide THAT ONE.
  2. You can generate a new trace with this command:

     xperf -on DiagEasy

     Wait some time (Niemiro said: "Wait until the computer has gone through a period of stuttering slowness") and then:

     xperf -d "%userprofile%\Desktop\trace.etl"

  3. Upload/post the files. You can attach them here through GoogleDrive, OneDrive, DropBox or similar services.
  
  You can also read the original tutorial/guide and its following posts for more information:
  
  How to Diagnose and Fix High DPC Latency Issues with WPA (Windows Vista/7/8) (click) (by Niemiro)