This article has been archived. It is offered "as is" and will no longer be updated.
Consider the following scenario:
You have a computer that is running Windows Server 2003 Service Pack 2 (SP2) that supports the Intelligent Platform Management Interface (IPMI) standard.
The computer writes a memory dump file because of a stop error (blue screen) issue.
When the computer is writing the dump file, the memory that is available is low.
In this scenario, the computer stops responding while it is writing the dump file. If you attach a debugging tool to the computer, you find that the stop error code is 0x000000D1 when the computer stops responding.
In this case, the computer that is running Windows Server 2003 cannot recover automatically. Additionally, the computer cannot write a memory dump file for stop error issues. Therefore, you have to force shutdown the computer or restart the computer.
This problem is caused by an error in the IPMIdrv.sys driver.
Code running at the elevated IRQ level (HIGH_LEVEL) should not be pageable. However, in the IPMIdrv.sys driver, some code that runs at the elevated IRQ level (HIGH_LEVEL) is pageable. If the code is paged out when the system tries to run the code, the code cannot be paged in because, at the elevated IRQ level, the system cannot process a page in request or page out request. Therefore, the computer cannot access the code, and the computer triggers the second stop code (0x000000D1) mentioned in the "Symptoms" section.
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 Web site:
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.
To apply this hotfix, your computer must be running Windows Server 2003 Service Pack 2.
You must restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace any other previously released hotfixes.
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it 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.
For all supported x86-based versions Windows Server 2003 SP2
For all supported Itanium-based versions of Windows Server 2003 SP2
For all supported x64-based versions Windows Server 2003 SP2
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
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