This problem occurs when the Windows Server 2008 R2-based system has a storage solution that uses Microsoft Multipath I/O (MPIO) with the Microsoft Device Specific Module (MSDSM) together with Asymmetric Logical Unit Assignment (ALUA).

Fixes an issue in which a computer that is running Windows Server 2008 crashes, and a Stop error occurs when you use the Microsoft Device Specific Module for MPIO to control a storage device, and Asymmetric Logical Unit Assignment is enabled for this device.

You configure the storage device as a multipath disk by using Microsoft Multipath I/O (MPIO) and Microsoft Device Specific Module (MSDSM). Heavy I/O operations are performed on the multipath disk. A path to the multipath disk fails.

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) Notes.

This issue occurs because of a race condition that occurs in the Msdsm.sys file. Resolution Update information for Windows Server 2012. To resolve this issue in Windows Server 2012, install update rollup 2889784.

Symptoms. Consider the following scenario: You have a Windows Server 2012 R2, Windows Server 2012, or Windows Server 2008 R2 Service Pack 1 (SP1) Failover Cluster that is attached to a storage array. This configuration is running native Microsoft Multipath I/O (MPIO) and Microsoft Device Specific Module (MSDSM) functionality.

Note If the Microsoft Device Specific Module (MSDSM.sys) is being used with the MPIO solution, you should also apply hotfix 972797. A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article.

Fixes an issue in which you receive a Stop error message when you try to open the MPIO console on a computer that is running Windows Server 2008 SP2. This issue occurs after you remove all the paths to a SAN storage device.

Symptoms. Consider the following scenario: You have a server that is running Windows Server 2008 or Windows Server 2008 R2. You connect the server to a SAN by using Microsoft Multipath I/O (MPIO). You use Microsoft Device Specific Module (DSM) for MPIO. You assign at least one logical unit number (LUN) that is located on the SAN to the server.

Symptoms. Consider the following scenario: You configure a computer that is running Windows Server 2008 R2 Service Pack 1 (SP1) to use Microsoft Multipath I/O (MPIO). You connect a storage device that is configured to use Asymmetric Logical Unit Access (ALUA) to the computer that has multiple active paths. Multiple active paths fail.