Article ID: 973092 - View products that this article applies to.
This article has been archived. It is offered "as is" and will no longer be updated.
Not sure if this is the right fix? We've added this issue to our memory dump diagnostic
(https://home.diagnostics.support.microsoft.com/SelfHelp?knowledgebaseArticleFilter=2027760)which can confirm.
On a computer that is running Windows Server 2003 Service Pack 2 (SP2), you may randomly receive the following Stop error message:
Note Not all "0x00000050" Stop errors are caused by this problem.
0x00000050 (parameter1, 0, parameter3, parameter4) PAGE_FAULT_IN_NONPAGED_AREA
This problem occurs because of a timing issue in the registry system.
The registry system does not increase the reference count when the registry system accesses an internal object that has a nonzero reference count. This behavior causes incorrect reference counts. When the timing issue occurs, an object is freed by a thread even though another thread is accessing the object. Therefore, this other thread accesses the freed memory space, and then the system triggers the Stop error code 0x00000050.
To resolve this problem, apply hotfix 978243. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/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
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/824684/ )Description of the standard terminology that is used to describe Microsoft software updates
Article ID: 973092 - Last Review: January 16, 2015 - Revision: 5.0