"0x0000007E" Stop error when you log off from a Windows Server 2008 R2 SP1-based failover cluster

Applies to: Windows Server 2008 R2 Service Pack 1Windows Server 2008 R2 EnterpriseWindows Server 2008 R2 Datacenter

Not sure if this is the right fix? We've added this issue to our memory dump diagnostic which can confirm.


Consider the following scenario:
  • You have a Windows Server 2008 R2 Service Pack 1 (SP1)-based multi-node failover cluster that has the Hyper-V server role installed.
  • You move the Cluster Shared Volumes (CSV) ownership from the failover cluster to a cluster node by using the Failover Cluster Management snap-in.
  • You log off from the failover cluster immediately after you move the CSV ownership, and then you receive the following message:
    Please wait for the System Event Notification Service...
In this scenario, the failover cluster crashes. Additionally, you receive a Stop error message that resembles the following:
STOP: 0x0000007E (parameter1, parameter2, parameter3, parameter4)
  • This Stop error describes a SYSTEM_THREAD_EXCEPTION_NOT_HANDLED issue.
  • The parameters in this Stop error message vary, depending on the configuration of the computer.
  • Not all "Stop 0x0000007E" errors are caused by this issue.


This issue occurs because the STATUS_NOTIFY_CLEANUP status that is returned by the CSV device for an I/O request packet (IRP) is not handled correctly by the system.


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 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 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.


To apply this hotfix, you must be running Windows Server 2008 R2 SP1.

For more information about how to obtain a Windows 7 or Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

976932 Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2

Registry information

To apply this hotfix, you do not have to make any changes to the registry.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.


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

More Information

For more information about the IRP_MN_NOTIFY_CHANGE_DIRECTORY request, go to the following Microsoft website: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