A server that is running Windows Server 2008 R2 crashes, and Stop error 0xD1 occurs

Article translations Article translations
Article ID: 978500 - View products that this article applies to.

Additional file information for Windows Server 2008 R2

Additional files for all supported x64-based versions of Windows Server 2008 R2

Collapse this tableExpand this table
File nameAmd64_msdsm.inf_31bf3856ad364e35_6.1.7600.20611_none_270d833f0e250949.manifest
File versionNot Applicable
File size2,079
Date (UTC)07-Jan-2010
Time (UTC)10:35
File namePackage_1_for_kb978500~31bf3856ad364e35~amd64~~6.1.1.0.mum
File versionNot Applicable
File size2,252
Date (UTC)07-Jan-2010
Time (UTC)12:16
File namePackage_for_kb978500_rtm~31bf3856ad364e35~amd64~~6.1.1.0.mum
File versionNot Applicable
File size1,860
Date (UTC)07-Jan-2010
Time (UTC)12:16

Additional files for all supported IA-64-based versions of Windows Server 2008 R2

Collapse this tableExpand this table
File nameIa64_msdsm.inf_31bf3856ad364e35_6.1.7600.20611_none_caf08bb155c5a10f.manifest
File versionNot Applicable
File size2,077
Date (UTC)07-Jan-2010
Time (UTC)10:51
File namePackage_1_for_kb978500~31bf3856ad364e35~ia64~~6.1.1.0.mum
File versionNot Applicable
File size1,835
Date (UTC)07-Jan-2010
Time (UTC)12:16
File namePackage_for_kb978500_rtm~31bf3856ad364e35~ia64~~6.1.1.0.mum
File versionNot Applicable
File size1,444
Date (UTC)07-Jan-2010
Time (UTC)12:16
Expand all | Collapse all

On This Page

SYMPTOMS

A server that runs Windows Server 2008 R2 crashes. When you perform a stack trace, you find that the crash was caused by Stop error 0x000000D1 in MSDSM!DsmpParseDeviceID.

CAUSE

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). A transient error on the storage subsystem can cause a failure to obtain any data from the SCSI Inquiry page 0x83. This failure causes MPIO.sys to send a NULL pointer to MSDSM.sys.

RESOLUTION

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 the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

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, contact 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 Web site:
http://support.microsoft.com/contactus/?ws=support
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.

Prerequisites

There are no prerequisites for installing this hotfix package.

Restart requirement

You do not have to restart the computer after you apply this hotfix package.

Hotfix replacement information

This hotfix does not replace a previously released hotfix package.

File information

The English (United States) version of this hotfix uses a Microsoft Windows Installer package to install the hotfix. The dates and the times for these files are listed in Coordinated Universal Time (UTC) in the following table. When you view the file information, the date is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Windows Server 2008 R2 file information

The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately. MUM and MANIFEST files, and the associated security catalog (.cat) files, are critical to maintaining the state of the updated component. The security catalog files (attributes not listed) are signed with a Microsoft digital signature.

For all supported x64-based versions of Windows Server 2008 R2

Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Msdsm.sys6.1.7600.20611140,68007-Jan-201009:50x64

For all supported IA-64-based versions of Windows Server 2008 R2

Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Msdsm.sys6.1.7600.20611348,04007-Jan-201010:37IA-64

STATUS

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, 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

Properties

Article ID: 978500 - Last Review: October 7, 2011 - Revision: 3.0
APPLIES TO
  • Windows Server 2008 R2 Datacenter
  • Windows Server 2008 R2 Enterprise
  • Windows Server 2008 R2 Standard
Keywords: 
kbautohotfix kbexpertiseinter kbsurveynew kbbug kbfix kbqfe KB978500

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com