The information in this article applies to:
SYMPTOMSIf the CrashOnAuditFail registry key is set to 1 and the Security Event log is full on a computer running Windows NT, the following blue screen error message may be displayed:
CAUSEThis problem occurs if the Security Log has reached the Maximum Log Size specified, and Event Log Wrapping is set for "Overwrite Events Older than (X) Days." This can also occur if "Do Not Overwrite Events" is selected. Because the Security Event Log is full, and the CrashOnAuditFail registry key is set, Windows NT generates a STOP 0xC0000244 blue screen error message and cannot log audit information. RESOLUTIONTo work around this problem, use one of the following options:
STATUSMicrosoft has confirmed this to be a problem in the Microsoft products listed
at the beginning of this article. MORE INFORMATIONIn some instances, the server may not bugcheck, but may instead run very slowly after administrator logon. The system may also report continuous RPC errors after logon. Non-administrators will not be able to log on as a result of the CrashOnAuditFail key being set to 0x1. REFERENCESFor more information on the CrashOnAuditFail key, please see the following Microsoft Knowledge Base article: Q140058 How To Prevent Auditable Activities When Security Log Is Full Q178208 CrashOnAuditFail with Logon/Logoff Auditing Causes Blue Screen Additional query words:
Keywords : ntstop ntsecurity |
Last Reviewed: January 25, 2000 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |