Microsoft KB Archive/326189

From BetaArchive Wiki
Knowledge Base


"Stop" Errors Occur in ObpDestroySecurityDescriptorHeader

Article ID: 326189

Article Last Modified on 10/27/2006



APPLIES TO

  • Microsoft Windows NT Server 4.0, Terminal Server Edition
  • Microsoft Windows NT Server 4.0 Standard Edition
  • Microsoft Windows NT Server 4.0 Enterprise Edition



This article was previously published under Q326189

SYMPTOMS

"Stop 0xA" or "Stop 0x50" errors may occur when the system is under stress.

CAUSE

The error is caused by a race condition on the security descriptor of the System process.

RESOLUTION

A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem.

To resolve this problem, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:

NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this fix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

   Date         Time   Size     File name
   -----------------------------------------
   29-Jul-2002  11:28  957,376  Ntkrnlmp.exe
   29-Jul-2002  11:27  937,152  ntoskrnl.exe
                

NOTE: Because of file dependencies, this hotfix requires Microsoft Windows NT 4.0 Service Pack 6a.


STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

Keywords: kbhotfixserver kbqfe kbbug kbfix kbqfe KB326189