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.

"0x00000050" Stop error after a registry hive that contains many registry entries and subkeys is loaded in Windows Server 2008 SP2


View products that this article applies to.

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

↑ Back to the top


Symptoms

Assume that you install one of the following hotfix or security update on a computer that is running Windows Server 2008 Service Pack 2 (SP2):

  • The hotfix that is described in Microsoft Knowledge Base (KB) article 2709236 .
  • The security update that is described in KB 2724197 , which is documented in security bulletin MS12-068.
When a registry hive that has many registry entries and subkeys is loaded, the computer crashes. Additionally, you receive a Stop error message that resembles the following: 
STOP: 0x00000050 (parameter1, parameter2, parameter3, parameter4)
Notes
  • This Stop error describes a PAGE_FAULT_IN_NONPAGED_AREA issue.
  • The parameters in this Stop error message vary, depending on the configuration of the computer.
  • Not all "Stop 0x00000050" errors are caused by this issue.

↑ Back to the top


Cause

This issue is caused by an overflow of counter variables.

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

Prerequisites

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

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

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.
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 file information notes
Important Windows Vista hotfixes and Windows Server 2008 hotfixes are included in the same packages. However, only "Windows Vista" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows Vista" 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, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.
    VersionProductSR_LevelService branch
    6.0.600
    2.
    23xxx
    Windows Server 2008SP2LDR
  • 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 maintaining the state of the updated component. 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 nameFile versionFile sizeDateTimePlatform
Ntkrnlpa.exe6.0.6002.230303,604,34429-Jan-201313:46Not applicable
Ntoskrnl.exe6.0.6002.230303,553,12829-Jan-201313:46Not applicable
For all supported x64-based versions of Windows Server 2008
File nameFile versionFile sizeDateTimePlatform
Ntoskrnl.exe6.0.6002.230304,681,57629-Jan-201313:39x64
For all supported IA-64-based versions of Windows Server 2008
File nameFile versionFile sizeDateTimePlatform
Ntoskrnl.exe6.0.6002.230309,470,82429-Jan-201313:31IA-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

Additional file information

Additional file information for Windows Server 2008

Additional files for all supported x86-based versions of Windows Server 2008
File nameX86_279f5283dfe29b41101753d6d4502356_31bf3856ad364e35_6.0.6002.23030_none_2741a9a513c9cf82.manifest
File versionNot applicable
File size717
Date (UTC)29-Jan-2013
Time (UTC)13:53
PlatformNot applicable
File nameX86_f85911112d2327c7ed145e981f33f797_31bf3856ad364e35_6.0.6002.23030_none_e4bff30f2ba59f6a.manifest
File versionNot applicable
File size697
Date (UTC)29-Jan-2013
Time (UTC)13:53
PlatformNot applicable
File nameX86_microsoft-windows-os-kernel_31bf3856ad364e35_6.0.6002.23030_none_6e7fed93ca7f6f18.manifest
File versionNot applicable
File size18,682
Date (UTC)29-Jan-2013
Time (UTC)13:53
PlatformNot applicable
File nameX86_microsoft-windows-r..gistry-trustedtypes_31bf3856ad364e35_6.0.6002.23030_none_864d858644c479b2.manifest
File versionNot applicable
File size7,654
Date (UTC)29-Jan-2013
Time (UTC)03:07
PlatformNot applicable
Additional files for all supported x64-based versions of Windows Server 2008
File nameAmd64_146334c37d8ca3d6a651eedea58e35fb_31bf3856ad364e35_6.0.6002.23030_none_80bc6b53db8662ab.manifest
File versionNot applicable
File size701
Date (UTC)29-Jan-2013
Time (UTC)13:53
PlatformNot applicable
File nameAmd64_b4511aa49ac5b08da64c7c3613da7e8b_31bf3856ad364e35_6.0.6002.23030_none_34bcce1fa460ee2a.manifest
File versionNot applicable
File size721
Date (UTC)29-Jan-2013
Time (UTC)13:53
PlatformNot applicable
File nameAmd64_microsoft-windows-os-kernel_31bf3856ad364e35_6.0.6002.23030_none_ca9e891782dce04e.manifest
File versionNot applicable
File size17,282
Date (UTC)29-Jan-2013
Time (UTC)13:53
PlatformNot applicable
File nameAmd64_microsoft-windows-r..gistry-trustedtypes_31bf3856ad364e35_6.0.6002.23030_none_e26c2109fd21eae8.manifest
File versionNot applicable
File size7,656
Date (UTC)29-Jan-2013
Time (UTC)03:51
PlatformNot applicable
Additional files for all supported IA-64-based versions of Windows Server 2008
File nameIa64_7853f1ed03cd693a3ee4a29d1889af01_31bf3856ad364e35_6.0.6002.23030_none_5700ec508ac41830.manifest
File versionNot applicable
File size719
Date (UTC)29-Jan-2013
Time (UTC)13:53
PlatformNot applicable
File nameIa64_e07af5cdb363f34b343329882ee3782d_31bf3856ad364e35_6.0.6002.23030_none_fac2b6a404a5857f.manifest
File versionNot applicable
File size699
Date (UTC)29-Jan-2013
Time (UTC)13:53
PlatformNot applicable
File nameIa64_microsoft-windows-os-kernel_31bf3856ad364e35_6.0.6002.23030_none_6e819189ca7d7814.manifest
File versionNot applicable
File size17,606
Date (UTC)29-Jan-2013
Time (UTC)13:53
PlatformNot applicable
File nameIa64_microsoft-windows-r..gistry-trustedtypes_31bf3856ad364e35_6.0.6002.23030_none_864f297c44c282ae.manifest
File versionNot applicable
File size7,655
Date (UTC)29-Jan-2013
Time (UTC)02:24
PlatformNot applicable

↑ Back to the top


Keywords: kb, kbmdd, kbautohotfix, kbqfe, kbhotfixserver, kbfix, kbsurveynew, kbexpertiseadvanced

↑ Back to the top

Article Info
Article ID : 2795491
Revision : 1
Created on : 1/7/2017
Published on : 10/9/2014
Exists online : False
Views : 263