Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. "0x000000D1" Stop error when you fail over a cluster group in Windows Server 2012 or Windows Server 2012 R2

"0x000000D1" Stop error when you fail over a cluster group in Windows Server 2012 or Windows Server 2012 R2

View products that this article applies to.

This article describes a Stop error that occurs in Windows Server 2012 or Windows Server 2012 R2. A hotfix is available to resolve this issue. The hotfix has a prerequisite.

↑ Back to the top

Symptoms

Assume that you have two nodes on a cluster that is running Windows Server 2012 R2. The cluster nodes use asymmetric logical unit access (ALUA) storage array through Multipath I/O (MPIO). When this issue occurs, you receive a Stop error message that resembles the following on the new active node:

STOP: 0x000000D1 (parameter1, parameter2, parameter3, parameter4)

Notes
  • This Stop error indicates 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 "0x000000D1" Stop errors are caused by this issue.

↑ Back to the top

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:

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

To apply this hotfix, you must have April 2014 update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 (2919355) installed in Windows Server 2012 R2.

Registry information

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

Restart requirement

You may have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.
File information
The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.

Windows Server 2012 R2 file information and notes

Important Windows 8.1 hotfixes and Windows Server 2012 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 8.1/Windows Server 2012 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
  • The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:

    VersionProductMilestoneService branch
    6.3.960 0.17 xxxWindows Server 2012 R2RTMGDR
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are

    listed separately in the "Additional file information" section. MUM, MANIFEST, and the associated security catalog (.cat) files, are very important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x64-based versions of Windows Server 2012 R2
File nameFile versionFile sizeDateTimePlatform
Mpio.sys6.3.9600.17670245,05603-Feb-201519:11x64
Msdsm.sys6.3.9600.17671182,08003-Feb-201519:11x64

Windows Server 2012 file information and notes

Important Windows 8 hotfixes and Windows Server 2012 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 8/Windows Server 2012" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
  • The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:

    VersionProductMilestoneService branch
    6.2.920 0.17 xxxWindows Server 2012RTMGDR
    6.2.920 0.21 xxxWindows Server 2012RTMLDR
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are

    listed separately in the "Additional file information" section. MUM, MANIFEST, and the associated security catalog (.cat) files, are very important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x64-based versions of Windows Server 2012
File nameFile versionFile sizeDateTimePlatform
Mpio.sys6.2.9200.17071244,03205-Aug-201409:00x64
Mpio.sys6.2.9200.21190244,03205-Aug-201401:19x64
Msdsm.sys6.2.9200.17329184,12806-Apr-201506:53x64
Msdsm.sys6.2.9200.21442184,12806-Apr-201506:01x64

Additional file information

Additional file information for Windows Server 2012 R2
Additional files for all supported x64-based versions of Windows Server 2012 R2
File propertyValue
File nameAmd64_mpio.inf_31bf3856ad364e35_6.3.9600.17672_none_0df9fae863450859.manifest
File versionNot applicable
File size2,093
Date (UTC)03-Feb-2015
Time (UTC)19:13
PlatformNot applicable
File nameAmd64_msdsm.inf_31bf3856ad364e35_6.3.9600.17672_none_bb0e6101af7c5a68.manifest
File versionNot applicable
File size2,099
Date (UTC)03-Feb-2015
Time (UTC)19:13
PlatformNot applicable
Additional file information for Windows Server 2012
Additional files for all supported x64-based versions of Windows Server 2012
File propertyValue
File nameAmd64_mpio.inf_31bf3856ad364e35_6.2.9200.17329_none_76424e3218e36613.manifest
File versionNot applicable
File size2,093
Date (UTC)06-Apr-2015
Time (UTC)17:21
PlatformNot applicable
File nameAmd64_mpio.inf_31bf3856ad364e35_6.2.9200.21442_none_76af491f32178c5e.manifest
File versionNot applicable
File size2,093
Date (UTC)06-Apr-2015
Time (UTC)17:21
PlatformNot applicable
File nameAmd64_msdsm.inf_31bf3856ad364e35_6.2.9200.17329_none_2356b44b651ab822.manifest
File versionNot applicable
File size2,096
Date (UTC)06-Apr-2015
Time (UTC)06:57
PlatformNot applicable
File nameAmd64_msdsm.inf_31bf3856ad364e35_6.2.9200.21442_none_23c3af387e4ede6d.manifest
File versionNot applicable
File size2,096
Date (UTC)06-Apr-2015
Time (UTC)06:14
PlatformNot applicable

↑ Back to the top

Status

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

↑ Back to the top

Cause

This issue occurs because Microsoft Device Specific Module (MSDSM) does not allocate sufficient memory to fetch the target port group information from the Report Target Port Groups (RTPG) command.

↑ Back to the top

References

See the terminology that Microsoft uses to describe software updates.

↑ Back to the top

Keywords: kbautohotfix, kbqfe, kbhotfixserver, kbfix, kbsurveynew, kbexpertiseinter, kb

↑ Back to the top

Article Info
Article ID : 3036614
Revision : 1
Created on : 1/7/2017
Published on : 5/4/2015
Exists online : False
Views : 158