"0x000000D1" Stop error on a virtual machine in Windows Server 2012

Not sure if this is the right fix? We've added this issue to our memory dump diagnostic which can confirm.


Assume that you have the Hyper-V server role installed on a computer that is running Windows Server 2012. Additionally, assume that you have a third-party single root I/O virtualization (SR-IOV) network adapter installed on the computer. In this situation, the virtual machine that is running on the computer crashes. Additionally, you receive a Stop error message that resembles the following: 
STOP: 0x000000D1 (parameter1, parameter2, parameter3, parameter4)
  • This Stop error describes a DRIVER_IRQL_NOT_LESS_OR_EQUAL issue.
  • The parameters in this Stop error message vary, depending on the configuration of the computer.
  • Not all "Stop 0x000000D1" errors are caused by this issue.


This issue occurs because of a race condition that occurs between the PnP manager call and the VMBus thread.


This hotfix is also available at Microsoft Update Catalog.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix Download Available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website: Note The "Hotfix Download Available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.


To apply this hotfix, you must be running Windows Server 2012.

Registry information

To use the hotfix in this package, you do not have to make any changes to the registry.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.
File information


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

More Information

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.

Additional file information

Additional file information for Windows Server 2012

Additional files for all supported x64-based versions of Windows Server 2012
File nameAmd64_wvpci.inf_31bf3856ad364e35_6.2.9200.16519_none_d67131516e71713b.manifest
File versionNot applicable
File size1,749
Date (UTC)05-Feb-2013
Time (UTC)07:19
PlatformNot applicable
File nameAmd64_wvpci.inf_31bf3856ad364e35_6.2.9200.20624_none_d6eafcbe879bae43.manifest
File versionNot applicable
File size1,749
Date (UTC)05-Feb-2013
Time (UTC)07:20
PlatformNot applicable

ID articolo: 2806542 - Ultima revisione: 09 ott 2014 - Revisione: 1