Microsoft Knowledge Base Email Alertz

Stop error message on a computer that is running Windows Server 2003 SP2 and that has almost 4 GB or more of physical memory: 0x00000050 or 0x0000000A

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Stop error message on a computer that is running Windows Server 2003 and that has almost 4 GB or more of physical memory: "0x00000050" or "0x0000000A"

Article ID: 975986 - View products that this article applies to.
System TipThis article applies to a different version of Windows than the one you are using. Content in this article may not be relevant to you. Visit the Windows Vista Solution Center

SYMPTOMS

Consider the following scenario:
  • You have a computer that is running an x86 version of Windows Server 2003. 
  • The physical address expansion (PAE) feature is enabled, and the virtual address space that is used is greater than 4 gigabytes (GB). This means the physical memory is usually more than 4 GB.
Note In some cases, the virtual address space that is used is greater than 4GB even if the physical memory volume is less than 4 GB. Some space is reserved by BIOS, and the virtual memory of some session pools are mapped into a range that is greater than 4GB.

In this scenario, you receive one of the following error messages:
STOP: 0x00000050
(parameter1, parameter2, parameter3, parameter4) The PAGE_FAULT_IN_NONPAGED_AREA
STOP: 0x0000000A
(parameter1, parameter2, parameter3, parameter4)
The IRQL_NOT_LESS_OR_EQUAL
Note
  • The four parameters in this error message vary, depending on the configuration of the computer.
  • Because of the generality of memory corruption problems, you are not necessarily affected by this specific problem if a Stop error on this list occurs on the server. We recommend that you contact Microsoft Customer Support Services to determine whether this problem is occurring or not.

CAUSE

On a computer that is running an x86 version of Windows Server 2003 and that has PAE enabled, the page table entry (PTE) and the page directory entry (PDE) are 8 bytes wide. In a specific scenario, a PDE or PTE is not updated in an atomic operation. This behavior leaves the PDE or the PTE in an inconsistent state for a short time. If the PDE or the PTE that is in the inconsistent state is cached or is pre-fetched into a processor, an invalid PDE or PTE is saved into the cache of the processor. When this occurs, any later memory access that relies on the data structures that are cached or that are pre-fetched fail. This behavior causes the symptoms that are mentioned in the "Symptoms" section. 

RESOLUTION

To resolve this problem, apply hotfix 978243. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
978243 A terminal server that is running Windows Server 2003 Service Pack 2 restarts unexpectedly after hotfix 971280 or security update 971486 (MS09-058) is installed

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

Properties

Article ID: 975986 - Last Review: June 20, 2011 - Revision: 5.0
APPLIES TO
  • Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
  • Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
  • Microsoft Windows Server 2003, Standard Edition (32-bit x86)
Keywords: 
kbprb kbqfe kbsurveynew kbexpertiseinter kbbug kbfix KB975986
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate