When you use a server or a workstation that is running one of the operating systems that is listed in the "Applies to" section, you may receive the following error message:
The Windows Logon Process system process terminated unexpectedly with a status of 0xc0000034 (0x00000000 0x0000000)
The system has been shut down.
- Mismatched system files have been installed.
- A Service Pack installation has failed.
- A backup program that is used to restore a hard disk did not correctly restore files that may have been in use.
- An incompatible third-party program has been installed.
To determine which process failed, register Dr. Watson as the default system debugger (if it is not already the default debugger). Dr. Watson for Windows NT logs diagnostic information about process failures to a log file (Drwtsn32.log). Also, you can configure this program to produce memory dump files of failed processes that you can analyze in a debugger to determine why a process fails.
To set up Dr. Watson to trap user-mode program errors, follow these steps:
- At a command prompt, type System Root\System32\Drwtsn32.exe -I, and then press ENTER.
This command configures Dr. Watson as the default system debugger.
- At a command prompt, type System Root\System32\Drwtsn32.exe, and then select the following options:Append to existing log file
Create crash dump
- After the computer restarts from the STOP 0xC000021A error, run Dr. Watson (Drwtsn32.exe).
- View the Dr. Watson log to determine what user mode process may be causing the problem.
- If the Dr. Watson log does not contain sufficient information to determine the cause of the problem, analyze the User.dmp file to determine the cause of the STOP 0xC000021A error.
If Dr. Watson did not create a User.dmp file for either Winlogon.exe or Csrss.exe, you may have to use a different tool to generate a memory dump file of the process that fails. For more information, click the following article number to view the article in the Microsoft Knowledge Base:241215 How to use the Userdump.exe tool to create a dump fileNote Follow the instructions in the Knowledge Base article to troubleshoot a process that shuts down with an exception. While you follow these instructions, monitor the following processes to troubleshoot the STOP 0xC000021A error:
Value = GinaDLL REG_SZ
- If the Gina DLL value is present and if it is anything other than Msgina.dll, it probably means that a third-party product has changed this value.
- If this value is not present, the system uses Msgina.dll as the default GINA DLL.
Last known good configurationIf the previous steps in this article do not resolve the problem, start the computer by using the last known good configuration. To start the computer by using the last known good configuration, follow these steps.
Note Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.
- Click Start, and then click Shut Down.
- Click Restart, and then click OK.
- Press F8 at the indicated time:
- For an x86-based computer: When a screen of text appears and then disappears , press F8. (The screen of text may include a memory test, lines about the BIOS, and other lines.) There may also be a prompt that tells you when to press F8.
- For an Itanium architecture-based computer: After you make your selection from the boot menu, press F8. There may be a prompt that tells you when to press F8.
- Use the arrow keys to select Last Known Good Configuration, and then press ENTER.
NUM LOCK must be off before the arrow keys on the numeric keypad will function.
- Use the arrow keys to highlight an operating system, and then press ENTER.
- Choosing the Last Known Good Configuration startup option provides a way to recover from problems such as a newly added driver that may be incorrect for your hardware. However, it does not solve problems that are caused by corrupted or missing drivers or files.
- When you choose the Last Known Good Configuration option, only the information in registry key HKLM\System\CurrentControlSet is restored. Any changes you have made in other registry keys remain.
In-place upgradeIf the previous steps in this article do not resolve the problem, perform an in-place upgrade. For more information about how to do this,, click the following article numbers to view the articles in the Microsoft Knowledge Base:
Remove incompatible software by using the Recovery ConsoleIf the previous steps in this article do not resolve the problem, remove incompatible software by using the Recovery Console. Complete steps that describe how to do this are beyond the scope of this article. However, you may be able to use the following articles as guidelines for performing this procedure.
Article ID: 156669 - Last Review: Jan 20, 2016 - Revision: 1