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 on a Windows Server 2012-based cluster

"0x000000D1" Stop error on a Windows Server 2012-based cluster

View products that this article applies to.

Symptoms

When this issue occurs, you receive a Stop error message that resembles the following:

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

Cause

This issue occurs because of an issue in the Netft.sys cluster driver.

↑ Back to the top

Hotfix information

Important If you install a language pack after you install this hotfix, you must reinstall this hotfix. Therefore, we recommend that you install any language packs that you need before you install this hotfix. For more information, see Add language packs to Windows.

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

There is no prerequisite to install this hotfix.

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 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.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
Netft.sys6.2.9200.2148389,60015-May-201513:13x64

Additional file information

Additional file information for Windows Server 2012
Additional files for all supported x64-based versions of Windows Server 2012
File propertyValue
File nameAmd64_netft.inf_31bf3856ad364e35_6.2.9200.21483_none_161a48b0dad4d7bf.manifest
File versionNot applicable
File size1,745
Date (UTC)15-May-2015
Time (UTC)23:21
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

References

See the terminology that Microsoft uses to describe software updates.

↑ Back to the top

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

↑ Back to the top

Article Info
Article ID : 3062586
Revision : 1
Created on : 1/7/2017
Published on : 7/14/2015
Exists online : False
Views : 137