How to Troubleshoot a STOP 0xC000021ALast reviewed: March 3, 1998Article ID: Q156669 |
The information in this article applies to:
SYMPTOMSA Windows NT Server or a Windows NT Workstation may stop with the following message:
STOP: c000021a {Fatal System Error} The Windows Logon Process system process terminated unexpectedly with a status of 0xc0000034 (0x00000000 0x0000000) The system has been shutdown.NOTE: The parameters in parenthesis are specific to your system configuration and may differ each time.
CAUSEThe stop 0xC000021A is caused by a user-mode process that causes the Windows NT operating system operations to come to a halt. Windows NT interprets this STOP as a fatal error and the operating system will not continue. A memory dump from this type of STOP does not contain much useful information without the proper preparation.
RESOLUTIONThe solution to the STOP 0xC000021A lies in troubleshooting this STOP from an application stand point. Basic troubleshooting procedures apply. "Was new hardware installed?" "Was new software installed?" And so forth. Any applications loaded in user-mode memory space can cause this STOP. This includes the native user-mode processes of Windows NT. Carefully review the loaded software on this system and try to determine if any one of them may be causing a problem. Follow these steps to help in isolating the cause of these types of errors. First, set up Dr. Watson to trap any user-mode application that may be causing this problem. Dr. Watson for Windows NT is an application error debugger, which is a program that detects application errors, diagnoses the error, and logs the diagnostic information. To properly set up Dr. Watson to trap user-mode problems, perform the following steps:
If a third-party software package was recently installed, and now the system fails on booting with a 0xC000021A, try using the Last Known Good option at start up. After Windows NT has started, remove the faulting application and contact the third-party software vendor. Set the GlobalFlag to 60000 in the registry. To do this, please see the following Microsoft Knowledge Base article:
ARTICLE-ID: Q147314 TITLE : GlobalFlags for Windows NT 3.51After setting this global flag, the systems memory dump will contain more information on the faulting user-mode application. Making any kernel mode memory dump more useful.
MORE INFORMATIONThis information for the global flags can be found in the NTEXAPI.H FLG_ definitions in the Windows NT Software Development Kit (SDK).
|
Additional query words: debugref 21A 21a 0x21a
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |