Ask a new question

Windows 10 DPC latency issue with ndis & tcpip.sys

I'm going crazy here.

I have tried contacting both realtek and msi in case they knew something which they didn't. Through MS support it got escalated to their tier 2. A guy had a 30min remote session with my machine, and couldn't find anything wrong at all. He even told me that it was very rare for him to remote a machine that felt so responsive for him, he was used to SFC /scannow taking up to 45min, but my machine did it in like 10min.

But the stuttering from the DPC issue continues. Clean installs have been made multiple times, system file checks, driver updates and downgrades, BIOS CPU settings disabling c-states, throttling, HPET on & off and more.

Yesterday i even installed a new network adapter hoping that would fix it, but nope. Still having DPC issues with ndis & tcpip.sys. The onboard network adapter is realtek, the new one is intel. So 2 different brands.

Searching threads like:

http://www.tenforums.com/drivers-hardware/28578-random-stuttering-dpc-latency-nightmare.html

http://answers.microsoft.com/en-us/windows/forum/windows_10-performance/very-high-dpc-latency-on-win10-in-ndissys/2c523e49-e2a0-45f0-8233-b6435dbbe905

http://answers.microsoft.com/en-us/insider/forum/insider_wintp-insider_perf/win10x64-dpc-latency-issue-ndissys-tcpipsys/1d49821b-7e21-4498-82e2-3d36926d3a3a

And many more yields no results, only people with the same problem and no solution, besides knowing that it is defiantly network related.

The only conclusion i can come to, is that there is a software issue in windows 10 with their network drivers. Their support does not appear to be aware of the problem. And from talking to MS support several times, i've learned they have no clue as to what, how or why.

Problem didn't exist in windows 7, for me at least. This is specific to windows 10. I've tried almost everything and it's driving me nuts.

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

After I'm done with the testing. How about creating a Github project and share it with the community to test and verify the issue? This would draw more attention on the issue. Maybe you want to participate that would be great :)

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

After I'm done with the testing. How about creating a Github project and share it with the community to test and verify the issue? This would draw more attention on the issue. Maybe you want to participate that would be great :)

I'm having the exact same issue, narrowing it down to the network interface was no small matter. 

I have multiple nics from different manufacturers on my motherboard and both are having this issue so it can't be hardware - related.

I don't know how to fix it so far, if i find a solution (except using another OS) i will try to report here.

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

If it's the same issue I'm facing / I faced. It's unfixable because it's an issue of the OS network stack / driver. Only MS can acutally fix it.

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.


Try this update:

https://support.microsoft.com/en-in/help/4077525/windows-10-update-kb4077525

It can be found at:

https://www.catalog.update.microsoft.com/Search.aspx?q=KB4077525

I worked with Microsoft on a support ticket for this exact issue (DPC Latency in the call to tcpip.sys!LruCleanupDpcRoutine), and it seems to have been resolved by this update. Report back whether this fixes the problem for you as well.

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

@GravitationalAnemon Mhm the linked KB is not intended for the latest Windows 10 build. It's for the 1607 build and not for 1709, I also can't find an equivalent Update for 1709. So I'm unable to test it but it's seemingly part of the montly rollout and therefore it might already been fixed but I didn't find the same bug fix note for 1709 in the latest KBs.

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

We were seeing this same issue, specifically when we were listening to multicast UDP traffic. The PC would lock up almost instantly and one CPU core would spike to 100%, while the other cores didn't carry any load whatsoever. This was not happening at all for us on Windows 7, only on Windows 10 (with the same exact hardware as the Windows 7 PC). 

We tried tons of stuff (Enabling/disabling RSS, making sure MSI was enabled, updating drivers, power settings, etc) with no luck. Finally we tried booting the Windows 10 PC in Safe Mode with Networking, and the issue was immediately fixed. No more network latency, and we were able to listen to the multicast UDP traffic without any issues. This time no CPU cores spiked, and the load was balanced among all of them.

Obviously now we have to determine why it works in Safe Mode and not when booting into the normal OS, but it's a start. Just wanted to pass this along in case it helps anyone else, or if anyone may have an idea as to why this is the case.

Also, regarding the KB that was mentioned in the earlier post, I found the following list for each version of Windows 10 (see below). This is not a list I found from Microsoft, but based on what I saw on other forums. We did try the 1709 patch, but we actually found that it was throttling our network traffic down, so we uninstalled it.

KB4089848 - 1709 Build 16299.334

https://support.microsoft.com/en-us/help/4089848

Download

https://www.catalog.update.microsoft.com/Search.aspx?q=KB4089848

KB4088891 - 1703 Build 15063.994

https://support.microsoft.com/en-us/help/4088891

Download

https://www.catalog.update.microsoft.com/Search.aspx?q=KB4088891

KB4088889 - 1607 Build 14393.2155

https://support.microsoft.com/en-us/help/4088889

Download

https://www.catalog.update.microsoft.com/Search.aspx?q=KB4088889

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

@MR658 Thanks for pointing that out. It seems that in the meantime there is a KB for 1709 and 1703. If I last checked there wasn't one for these builds. The update timestamp also suggests that (22 / 24.03.2018). I will try that one and report back. Thanks for mentioning this now.

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

@thexyz Just as a follow up to my last post, we found out what was causing the issue for us. It happens to be the "Windows Defender Firewall" service.

Even though we had it turned off in Control Panel, the "Windows Defender Firewall" service (MpsSvc) was still running in the background and causing issues. We completely disabled the service via the registry (key below) and rebooted. Once we did that, our networking latency/crashing issues disappeared. Hopefully this is helpful for you as well. 

  • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MpsSvc
    • Change "Start" from "2" to "4"
    • Reboot the PC

8 people found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Just to let you know - KB4089848 - 1709 Build 16299.334 - has been rolled out this week for my machines so it also part of the standard update plan for Windows 10. Thanks for keeping us up to date with your additional discoveries concerning disabling the "Windows Defender Firefall". However, I'm still not 100% sure if your issue has the same origin like the DPC Latency problem which I face(d). Will have to invest some time in investigation and report back if the latest KB finally fixed the issue I had.

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

I have the solution for my computer (Windows 7).  It solves it.

1. Go to Network Connections

2. Go to Local Area Connection

3. Click Properties

4. Under Networking, uncheck "Internet Protocol Version 6 (TCP/IPv6)"

5. Click OK.

It solves the stuttering immediately.

Enjoy

4 people found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

 
 

Question Info

Last updated April 22, 2024 Views 22,766 Applies to: