Microsoft KB Archive/233214

= "STOP 0xC0000244" Error Message Occurs Even If CrashOnAuditFail Setting Is Disabled =

Article ID: 233214

Article Last Modified on 11/1/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 Q233214



SYMPTOMS
You may receive a "STOP 0xC0000244 (STATUS_AUDIT_FAILED)" error message on a blue screen, even though the CrashOnAuditFail registry value is not set.



CAUSE
This problem occurs because an audit failure has actually occurred, probably because the Security event log has overflowed. Sometimes, Windows then behaves as if the CrashOnAuditFail value is enabled and causes the computer to display the error message.



Windows NT Server or Workstation 4.0
To resolve this problem, obtain the latest service pack for Windows NT 4.0 or the individual software update. For information on obtaining the latest service pack, please go to:


 * http://www.microsoft.com/windows/servicepacks/ -or-


 * 152734 how to obtain the latest windows nt 4.0 service pack

For information on obtaining the individual software update, contact Microsoft Product Support Services. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:

http://support.microsoft.com/directory/overview.asp

Windows NT Server 4.0, Terminal Server Edition
To resolve this problem, obtain the latest service pack for Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

152734 How to Obtain the Latest Windows NT 4.0 Service Pack



WORKAROUND
To work around this problem, clear the Security event log periodically so that it never overflows, or change the Security event log settings to overwrite events as needed.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Windows NT Server version 4.0, Terminal Server Edition Service Pack 6.

Keywords: kbhotfixserver kbqfe kbbug kbfix kbqfe KB233214

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.