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.

"0x000000D1" Stop error occurs on a Windows Server 2008 R2-based server


View products that this article applies to.

This article describes an issue in which a "0x000000D1" Stop error occurs on a server in Windows Server 2008 R2 Service Pack 1 (SP1). A hotfix is available to resolve this issue. The hotfix has a prerequisite.

↑ Back to the top


Symptoms

A Windows Server 2008 R2-based server crashes, and 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


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 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: 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 update, you must have Service Pack 1 installed on Windows Server 2008 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 2008 R2 file information and notes

Important Windows 7 hotfixes and Windows Server 2008 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 7/Windows Server 2008 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.1.760 1.18xxxWindows Server 2008 R2SP1GDR
    6.1.760 1.22xxxWindows Server 2008 R2SP1LDR
  • GDR service branches contain only those fixes that are widely released to address widespread, critical issues. LDR service branches contain hotfixes in addition to widely released fixes.
  • 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 2008 R2
File nameFile versionFile sizeDateTimePlatform
Srv2.sys6.1.7601.18701410,62413-Dec-201401:49x64
Srv2.sys6.1.7601.22909406,01613-Dec-201401:51x64
For all supported IA-64-based versions of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Srv2.sys6.1.7601.18701786,94413-Dec-201401:28IA-64
Srv2.sys6.1.7601.22909799,23213-Dec-201401:27IA-64

Additional file information

Additional files for all supported x64-based versions of Windows Server 2008 R2
File propertyValue
File nameAmd64_0676e69d16b4e346bbafb2ae154158e1_31bf3856ad364e35_6.1.7601.22909_none_15bd507cb674e52b.manifest
File versionNot applicable
File size704
Date (UTC)16-Dec-2014
Time (UTC)01:44
PlatformNot applicable
File nameAmd64_a8717c2b4fcbbe10f284de786cc058d0_31bf3856ad364e35_6.1.7601.18701_none_48fc4cc628d723c0.manifest
File versionNot applicable
File size704
Date (UTC)16-Dec-2014
Time (UTC)01:44
PlatformNot applicable
File nameAmd64_microsoft-windows-smbserver-v2_31bf3856ad364e35_6.1.7601.18701_none_381a5af00d15ea00.manifest
File versionNot applicable
File size2,657
Date (UTC)13-Dec-2014
Time (UTC)03:46
PlatformNot applicable
File nameAmd64_microsoft-windows-smbserver-v2_31bf3856ad364e35_6.1.7601.22909_none_38abfbf1262c51a9.manifest
File versionNot applicable
File size2,657
Date (UTC)13-Dec-2014
Time (UTC)03:56
PlatformNot applicable
Additional files for all supported IA-64-based versions of Windows Server 2008 R2
File propertyValue
File nameIa64_758bd6ab4f5110a3240d66eccf14dd57_31bf3856ad364e35_6.1.7601.18701_none_9e5bd2ac7ab951e5.manifest
File versionNot applicable
File size702
Date (UTC)16-Dec-2014
Time (UTC)01:44
PlatformNot applicable
File nameIa64_91ff7da1151f593bdab9eb703dc2b9f5_31bf3856ad364e35_6.1.7601.22909_none_d8282f9824aaae03.manifest
File versionNot applicable
File size702
Date (UTC)16-Dec-2014
Time (UTC)01:44
PlatformNot applicable
File nameIa64_microsoft-windows-smbserver-v2_31bf3856ad364e35_6.1.7601.18701_none_dbfd636254b681c6.manifest
File versionNot applicable
File size2,656
Date (UTC)13-Dec-2014
Time (UTC)02:57
PlatformNot applicable
File nameIa64_microsoft-windows-smbserver-v2_31bf3856ad364e35_6.1.7601.22909_none_dc8f04636dcce96f.manifest
File versionNot applicable
File size2,656
Date (UTC)13-Dec-2014
Time (UTC)03:24
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, kbautohotfix, kbqfe, kbhotfixserver, kbfix, kbsurveynew, kbexpertiseadvanced

↑ Back to the top

Article Info
Article ID : 3025980
Revision : 1
Created on : 1/7/2017
Published on : 2/25/2015
Exists online : False
Views : 332