This isn’t a Hyper-V bug, but it’s one that those using SAN storage should pay attention to … and that often include Hyper-V admins/engineers: "0x000000D1" Stop error when you open the MPIO snap-in on a computer that is running Windows Server 2012.
Consider the following scenario:
- You connect a storage device that is controlled by Microsoft Multipath I/O (MPIO) to a computer that is running Windows Server 2012.
- You remove all paths to the storage device.
- You open the MPIO snap-in or try to switch to the MPIO tab on the properties window of a disk that is managed by MPIO.
In this scenario, 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.
A supported hotfix is available from Microsoft.