This hotfix is related to a scenario where a WS2012 Hyper-V hosted virtual machine that is connected to an SR-IOV enabled NIC crashes.
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.
A supported hotfix for the host is available from Microsoft.
This blog post is the property of Aidan Finn (@joe_elway / http://www.aidanfinn.com) and may not be reused in any manner without prior consent of Aidan Finn. You may quote one paragraph from this blog post if you link to the original blog post.
- KB2821052 – "0x000000D1" Stop Error When Opening MPIO Snap-In WS2012 Computer
- KB2776366 – "0x0000000A" Stop Error On W2008 R2 Hyper-V Host That Has Many Passthrough Disks
- Windows Server 2012 R2 Hyper-V – Live Virtual Machine Export/Clone
- Windows Server 2012 NIC Teaming Part 6 – NIC Teaming In The Virtual Machine
- KB2830510 – Creating a Windows Server 2012 Failover Cluster Fails with Error 0xc000005e