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. A Windows Server 2008 Failover Cluster that has a MPIO solution may encounter stop code 0x0000007E or 0x000000D5 during a path failover

A Windows Server 2008 Failover Cluster that has a MPIO solution may encounter stop code 0x0000007E or 0x000000D5 during a path failover

View products that this article applies to.

Symptoms

Consider the following scenario:
  • Windows Server 2008 Failover Cluster is installed on a computer that has the Microsoft Multipath I/O (MPIO) solution.
  • Many logical unit numbers (LUNs) are attached to this computer. For example, more than 30 LUNs are attached.
  • An MPIO path failover occurs under stress conditions when there is no available MPIO path.
In this scenario, you receive one of the following error messages:
  • Stop code 0x0000007E SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
  • Stop code 0x000000D5 DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL

↑ Back to the top

Cause

This problem occurs because persistent reservations (PR) in Windows Server 2008 Failover Cluster are set to use a critical work item. Under stress conditions, it causes the MPIO.sys driver to be delayed in handling a device object. When the MPIO.sys driver has an opportunity to handle the device object, it is freed. Therefore, the Windows Server 2008 system triggers stop code 0x0000007E or 0x000000D5.

↑ Back to the top

Resolution

Hotfix information

Important Windows Vista and Windows Server 2008 hotfixes are included in the same packages. However, only one of these products may be listed on the “Hotfix Request” page. To request the hotfix package that applies to both Windows Vista and Windows Server 2008, just select the product that is listed on the page.

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

To apply this hotfix, you must have Windows Server 2008 with the Failover Cluster role enabled.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

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.

Windows Vista and Windows Server 2008 file information notes

  • Service Pack 1 is integrated into Windows Server 2008.
  • The MANIFEST files (.manifest) and MUM files (.mum) 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 x86-based versions of Windows Server 2008 and Windows Vista
File nameFile versionFile sizeDateTimePlatform
Clusdisk.infNot Applicable4,44827-Jan-200900:41Not Applicable
Clusdisk.sys6.0.6001.2236226,11227-Jan-200903:03x86

For all supported x64-based versions of Windows Server 2008 and Windows Vista
File nameFile versionFile sizeDateTimePlatform
Clusdisk.infNot Applicable4,44827-Jan-200900:42Not Applicable
Clusdisk.sys6.0.6001.2236231,74427-Jan-200903:33x64

For all supported Itanium-based versions of Windows Server 2008
File nameFile versionFile sizeDateTimePlatform
Clusdisk.infNot Applicable4,44826-Jan-200923:38Not Applicable
Clusdisk.sys6.0.6001.2236276,28827-Jan-200902:11IA-64

↑ 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

More Information

For more information about software update terminology, 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

↑ Back to the top

Additional file information for Windows Server 2008

Additional files for all supported x86-based versions of Windows Server 2008 and Windows Vista

File nameFile versionFile sizeDateTimePlatform
Package_for_kb963702_sc_0~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,42128-Jan-200923:53Not Applicable
Package_for_kb963702_sc~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,42228-Jan-200923:53Not Applicable
Package_for_kb963702_server_0~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,42528-Jan-200923:53Not Applicable
Package_for_kb963702_server~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,43028-Jan-200923:53Not Applicable
X86_clusdisk.inf_31bf3856ad364e35_6.0.6001.22362_none_eddf07741d9b2d97.manifestNot Applicable1,67928-Jan-200923:55Not Applicable

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

File nameFile versionFile sizeDateTimePlatform
Amd64_clusdisk.inf_31bf3856ad364e35_6.0.6001.22362_none_49fda2f7d5f89ecd.manifestNot Applicable1,68128-Jan-200923:57Not Applicable
Package_for_kb963702_sc_0~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,42928-Jan-200923:53Not Applicable
Package_for_kb963702_sc~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,43028-Jan-200923:53Not Applicable
Package_for_kb963702_server_0~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,43328-Jan-200923:53Not Applicable
Package_for_kb963702_server~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,43828-Jan-200923:53Not Applicable

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

File nameFile versionFile sizeDateTimePlatform
Ia64_clusdisk.inf_31bf3856ad364e35_6.0.6001.22362_none_ede0ab6a1d993693.manifestNot Applicable1,68028-Jan-200923:53Not Applicable
Package_for_kb963702_sc_0~31bf3856ad364e35~ia64~~6.0.1.0.mumNot Applicable1,42528-Jan-200923:53Not Applicable
Package_for_kb963702_sc~31bf3856ad364e35~ia64~~6.0.1.0.mumNot Applicable1,42628-Jan-200923:53Not Applicable
Package_for_kb963702_server_0~31bf3856ad364e35~ia64~~6.0.1.0.mumNot Applicable1,42928-Jan-200923:53Not Applicable
Package_for_kb963702_server~31bf3856ad364e35~ia64~~6.0.1.0.mumNot Applicable1,43428-Jan-200923:53Not Applicable

↑ Back to the top

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

↑ Back to the top

Article Info
Article ID : 963702
Revision : 1
Created on : 1/7/2017
Published on : 10/7/2011
Exists online : False
Views : 170