KB2905412 – Stop Error 0xD1 On Windows-Based Computer With Multiple Processors

Not strictly a Hyper-V issue, but you’ll understand why I am blogging about this one; A hotfix has been released for when a stop error 0xD1 on a Windows-based computer with multiple processors.


Your multiprocessor Windows-based computer crashes every two to three days. Additionally, Stop error 0xD1 is generated when the computer crashes.


This problem occurs because of a race condition that exists in the TCP/IP driver in a multiprocessor environment. If duplicate TCP segments are received on different processors, they may be sequenced incorrectly, and this triggers the crash.

A hotfix is available

Please follow and like us:

2 Comments on KB2905412 – Stop Error 0xD1 On Windows-Based Computer With Multiple Processors

  1. I realize the article SAYS it’s for Win8/Server2012, but whenever I go to request the Hotfix, it only shows versions for Win7/2008R2..??

  2. For what it’s worth, I’ll put my thoughts in and also answer the previous post regarding the hotfix listed as W7/2008. First, the hotfix for W7/2008 should do the trick.

    Now for my feedback on this. I’ve been crashing for about 5 days now and, oddly enough, it started just after two simultaneous changes I made to my network (as in, the two things I changed were done on the same day) which is making the repair quite daunting it seems.

    Change 1; I locked down my router with a few security implementations and increased the number of allowable IP’s as assigned by the DHCP server of the router itself (I do not have a dedicated DHCP windows server).

    Change 2; I upgraded a client connected workstation from Windows 7 to Windows 10.

    The result of those two changes is where I’m at now which is this;

    The client was the first to behave strangely, the client BSOD was the beginning of my challenges because it showed that the video drivers were at fault. I used an application specific to the removal of display drivers which not only removes the display drivers but removes any trace of said drivers from all folders and the registry. This is all done while booted in Safe Mode. That done, I blocked Windows update (W10 hotfix specific to the issue) from installing the hardware drivers, I then used device manager to remove the basic display adapter drivers. The workstation continued to BSOD only this time with the error of ntoskrnl.exe & ntkrnlmp.exe, the code with and without the display drivers was 0x116 on the workstation.

    The Server then began it’s exact version of events only the display adapter in the server was a different chipset manufacturer than the client and its error was 0xD1, the ntoskrnl.exe and ntkrnlmp.exe were exhibited after the removal of the display drivers.

    Things that seem to trigger the crashes;

    – Workstation accessing the server via network causes server to crash
    – Workstation crashes randomly on it’s own without any user initiated communication to server
    – Server crashing randomly without user initiated communication from workstation
    – File transfer to and from server via network and directly from server to a connected USB drive
    – When server crashes, (in all crash instances) the entire network suffers from internet access drop even though the server is only a client connected device to the physical router

    Nothing I have done to this point has resolved the issue but here’s a quick look at what’s been done;

    – Removal of drivers and adapter for a secondary NIC card in server
    – Removal of display drivers from both server and workstation
    – Scanned server for virus and also disk checker and file system checker done along with mem test, all of which result in passes with no issues found
    – Implemented a different hotfix for Network adapter conditions causing server 2012 to crash, no effect, still crashing with same error.
    – Have not yet performed more thorough check on workstations, simply took it offline until server is resolved then I’ll head back to it.

    If anybody has a clue, feel free post back here and advise me

Leave a comment

Your email address will not be published.