[SOLVED] DPC latency issues ndis.sys and nvlddmkm.sys

[Maedhros]

Hey, greetings all. I am new to the forum. :wave:

I have been experiencing some crackling sound issues lately when playing online, listening to music or simply doing average tasks on windows like chatting on Skype. Long sotry made short: I did some research on the internet about it and I was thrown to downloading both Latencymon and DPC Latency checker. The first one says the culprits are ndis.sys and nvlddmkm.sys so, my first reaction was to update Nvidia drivers. Nothing happened. And about the first one I don't have slightest idea what to do.

I also downloaded Windos SDK as the tutorial here on how to debug DPC latency issues said, but I am stuck with it, my computer knowledge is plain basic as for my brother used to do all the troubleshooting for me before he moved to another country

So, I humbly come to you asking for help. :smile9:

 

[TomasD]

Dear,

To properly troubleshoot issues with high/frequent DPCs/IRPs, we require a XPERF trace. Please follow these steps to generate one:

1. Download Windows Software Development Kit (SDK) for Windows and run the setup.
2. Select Windows Performance Toolkit feature (all the others can be unchecked) and proceed with the download/installation.
3. Once the installation finishes, open an elevated Command Prompt by right-clicking on CMD.EXE shortcut in your start menu and selecting Run As Administrator from the context menu.
4. Type the following command, which will start tracing, in the Command Prompt window you just opened:
   

   xperf -on PROC_THREAD+LOADER+PROFILE+INTERRUPT+DPC+DRIVERS+POWER+IDLE_STATES -stackwalk Profile -BufferSize 1024 -MinBuffers 256 -MaxBuffers 256 -MaxFile 256 -FileMode Circular

   If you see a yellow warning "xperf: warning: This system is not fully configured for x64 stack tracing" after running the above command, please complete these extra steps (otherwise, proceed to the step #5):
   
   Read More:

   1. Run the following command which will stop the tracing:
      

      xperf -stop

   2. Run the following command to enable stack tracing (by disabling Paging Executive):
      

      REG ADD "HKLM\System\CurrentControlSet\Control\Session Manager\Memory Management" -v DisablePagingExecutive -d 0x1 -t REG_DWORD -f

   3. Reboot the computer
   4. Once computer reboots, proceed from the step #3
   If you see a red error "xperf: error: NT Kernel Logger: A device attached to the system is not functioning. (0x1f)" after running the above command, please complete these extra steps (otherwise, proceed to the step #5):
   
   Read More:

   
   

   1. Run the following command to disable Driver Verifier, which causes the above error:
      

      verifier /reset

   2. Reboot the computer
   3. Once computer reboots, proceed from the step #3
   
   If you see a red error "xperf: error: NT Kernel Logger: Cannot create a file when that file already exists. (0xb7)", please do the following (otherwise, proceed to the step #5):
   
   Read More:

   
   Make sure you do not have any programs that capture ETW data already running. Some examples of these are:
   
   

   • Process Explorer
   • Process Hacker
   • Resource Monitor
   • Process Monitor
   • Latency Monitor
   • Another instance of XPERF or WPR
5. Perform some activities with your computer for few minutes, making sure the issues you reported are reproduced.
6. Run the following command, which will stop the tracing, in the command prompt window you already have opened:
   

   xperf -stop -d C:\CPU.etl

7. Compress file C:\CPU.etl
8. Upload the compressed file to a file sharing service (e.g. OneDrive or DropBox).
9. Share the download link here.

Thank you.

 

[Maedhros]

Hey, Tomas. Thanks for the quick answer :)

I did the first four steps plus the instructions for "xperf: warning: This system is not fully configured for x64 stack tracing" rebooted the computer and proceeded to start again since step 3. Everything was running smoothly then I got a random BSOD after some minutes. What should I do now?

 

[Maedhros]

Nevermind, Apparently the BSoD happened while trying to open Steam the first time. Managed to run it now avoiding steam while the crackling issues appeared. But that random blue screen seemed quite suspicious.

Here is the CPU.etl file. Cheers.

https://www.dropbox.com/s/3x5stdmhfb3qlfe/CPU.rar?dl=0

 

[TomasD]

OK, the issue seems to be with interrupts, not DPCs. High interrupts are caused by the video subsystem (DirectX, nVidia driver). Unfortunately, I have no way to tell what might be the root cause for the issue. Hence, there are few general suggestions in cases like these:

• Install the latest (including Beta) driver for the video card;
• Check GPU temperatures;
• Re-seat the GPU, clearing the contacts/dust (if that's possible);

The BSOD you had using Steam might be cause by nVidia driver and relate to this interrupts issue as well, indicating possible GPU hardware issue (assuming, none of the suggestions listed above helps).

 

[Maedhros]

This is honestly very strange for me. I shall see what I can do in the incoming days with my limited computer knowledge. Otherwise I will take the computer to someone I know for more help, as for I don't dare to manually manipulate the GPU by myself.

Thanks for your help, Tomas. It is much appreciated.

Cheers!

 

[Maedhros]

Tomas, I wanted to thank you for your help. It was indeed the GPU. Now after reinstalling windows the issue has lowered almost completely. I sometimes keep DPC Checker running to monitor if it spikes. Until now the bars have stayed in the green sides with the ocassional spikes of 800 to 900 µs. The highest one I got was yellow and of 1100 µs but it didn't distort the audio or video so far. After disabling the GPU drivers, everything went below 100 µs and stayed there.

I will keep tinkering around with older drivers since the person who reinstalled windows for me updated them to the latest, I will also borrow a GPU from a friend to test it on my puter. Will mark this as solved since as you pointed the GPU has been the only device causing issues so far, think it might be time to get another one.

Many thanks!

 

[thedarkrosi]

Oh hello Thomas i hope i am not too late, but i have the same issues with ndis.sys and nvlddmkm.sys dpc latency problems. I am pretty sure it is something to do with realtek network card and upgrade to windows 10. Any way i hope you could give some help for me. Added the CPU.etl file link Thanks in advance!

Dropbox - CPU.zip