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

Symptoms

Consider the following scenario:

  • You configure a failover cluster on some computers that are running Windows Server 2008 or Windows Server 2008 R2.

  • You install at least one third-party volume manager on these cluster nodes. For example, you install the volume manager from Vertias.

  • You fail over some disk resource from one node to the other node.

In this scenario, you receive the following Stop error message on the two cluster nodes that are involved in the failover:

Stop 0x00000050 (parameter1, 0, parameter3, parameter4)

PAGE_FAULT_IN_NONPAGED_AREA

Note

  • The parameters in this Stop error message vary, depending on the configuration of the computer.

  • Not all "0x00000050" Stop error messages are caused by this problem.

  • The node that has the disk resource encounters this Stop code error message first. After a while, the node that receives the disk resource encounters this Stop code error message.

Cause

This issue occurs because of a timing issue in Partition Manager (Partmgr.sys) if more than one volume manager are installed. When this timing issue occurs, some disk device objects and some file objects in memory are incorrectly freed.

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 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=supportNote 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 be running one of the following operating systems:

  • Windows Server 2008 Service Pack 2

  • Windows Server 2008 R2



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

968849 How to obtain the latest service pack for Windows Server 2008

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The English (United States) 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 file information notes
  • The files that apply to a specific product, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.

    Version

    Product

    SR_Level

    Service branch

    6.0.600
    2.
    22xxx

    Windows Vista and Windows Server 2008

    SP2

    LDR

  • Service Pack 1 is integrated into the release version of Windows Server 2008. Therefore, RTM milestone files apply only to Windows Vista. RTM milestone files have a 6.0.0000.xxxxx version number.

  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008" section. MUM files and MANIFEST files, and the associated security catalog (.cat) files, are extremely 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 x86-based versions of Windows Server 2008

File name

File version

File size

Date

Time

Platform

Partmgr.sys

6.0.6002.22405

53,128

14-May-2010

18:53

x86

For all supported x64-based versions of Windows Server 2008

File name

File version

File size

Date

Time

Platform

Partmgr.sys

6.0.6002.22405

72,064

14-May-2010

18:59

x64

For all supported IA-64-based versions of Windows Server 2008

File name

File version

File size

Date

Time

Platform

Partmgr.sys

6.0.6002.22405

153,992

14-May-2010

18:36

IA-64

Windows Server 2008 R2 file information 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 MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 R2" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely 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 name

File version

File size

Date

Time

Platform

Partmgr.mof

Not applicable

1,945

10-Jun-2009

20:44

Not applicable

Partmgr.sys

6.1.7600.20757

75,136

17-Jul-2010

08:11

x64

For all supported IA-64-based versions of Windows Server 2008 R2

File name

File version

File size

Date

Time

Platform

Partmgr.mof

Not applicable

1,945

10-Jun-2009

20:49

Not applicable

Partmgr.sys

6.1.7600.20757

169,352

17-Jul-2010

06:52

IA-64

Status

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

Additional file information

Additional file information for Windows Server 2008

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

File name

Update.mum

File version

Not applicable

File size

3,078

Date (UTC)

18-May-2010

Time (UTC)

04:49

Platform

Not applicable

File name

X86_89389cb3d770c3c0c03b0ba313fee8f6_31bf3856ad364e35_6.0.6002.22405_none_2d7aeb4d81e63f66.manifest

File version

Not applicable

File size

704

Date (UTC)

18-May-2010

Time (UTC)

04:49

Platform

Not applicable

File name

X86_microsoft-windows-partitionmanager_31bf3856ad364e35_6.0.6002.22405_none_e4112f14d0aef31e.manifest

File version

Not applicable

File size

9,532

Date (UTC)

14-May-2010

Time (UTC)

20:00

Platform

Not applicable

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

File name

Amd64_22ab313fc80e6a5c44ba5ffc92a3847a_31bf3856ad364e35_6.0.6002.22405_none_99e3038c4e69dbbd.manifest

File version

Not applicable

File size

708

Date (UTC)

18-May-2010

Time (UTC)

04:49

Platform

Not applicable

File name

Amd64_microsoft-windows-partitionmanager_31bf3856ad364e35_6.0.6002.22405_none_402fca98890c6454.manifest

File version

Not applicable

File size

9,542

Date (UTC)

14-May-2010

Time (UTC)

20:04

Platform

Not applicable

File name

Update.mum

File version

Not applicable

File size

3,102

Date (UTC)

18-May-2010

Time (UTC)

04:49

Platform

Not applicable

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

File name

Ia64_ea6daab3e52f5da82b5bec78be795a69_31bf3856ad364e35_6.0.6002.22405_none_0320580d4e85f187.manifest

File version

Not applicable

File size

706

Date (UTC)

18-May-2010

Time (UTC)

04:49

Platform

Not applicable

File name

Ia64_microsoft-windows-partitionmanager_31bf3856ad364e35_6.0.6002.22405_none_e412d30ad0acfc1a.manifest

File version

Not applicable

File size

9,537

Date (UTC)

14-May-2010

Time (UTC)

19:23

Platform

Not applicable

File name

Update.mum

File version

Not applicable

File size

2,255

Date (UTC)

18-May-2010

Time (UTC)

04:49

Platform

Not applicable

Additional file information for Windows Server 2008 R2

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

File name

Amd64_d7775d3067064348de9be1c3dafdb679_31bf3856ad364e35_6.1.7600.20757_none_eba7c882f01fa396.manifest

File version

Not applicable

File size

708

Date (UTC)

19-Jul-2010

Time (UTC)

13:08

Platform

Not applicable

File name

Amd64_microsoft-windows-partitionmanager_31bf3856ad364e35_6.1.7600.20757_none_3e3d1807ed240d54.manifest

File version

Not applicable

File size

8,992

Date (UTC)

17-Jul-2010

Time (UTC)

09:02

Platform

Not applicable

File name

Update.mum

File version

Not applicable

File size

2,114

Date (UTC)

19-Jul-2010

Time (UTC)

13:08

Platform

Not applicable

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Any additional feedback? (Optional)

Thank you for your feedback!

×