stop 0xc000021a (schwerer system fehler)

windows logon process unerwartet beendet
status 0xc0000135 (0x00000000, 0x00000000)
"Stop C000021a (schwerer Systemfehler) Der Systemprozeß Windows Logon Process wurde unerwartet beendet Status 0XC0000135 (0x00000000 0x00000000)
Cause

The STOP 0xC000021A error occurs when either Winlogon.exe or Csrss.exe fails. When the Windows NT kernel detects that either of these processes has stopped, it stops the system and raises the STOP 0xC000021A error. This error may have several causes. Among them are the following:

• 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.

==============
Source
Winlogon is trying to load a DLL and failing. Your machine won't run without Winlogon, it's a fundamental part of the OS, so it crashes.
Barte PE Builder starten und alle DLLs von Barts PE system32 (nur die DLLs) in Windows/system32 auf der Platte reinkopieren (nichts überschrieben, nur fehlende ersetzen!)

support.microsoft.com/kb/156669
Note Most STOP 0xC000021A errors occur because Winlogon.exe fails. This typically occurs because of a faulty third-party Graphical Identification and Authentication (GINA) DLL.
The GINA is a replaceable DLL component that Winlogon.exe loads. The GINA implements the authentication policy of the interactive logon model. The GINA performs all identification and authentication user interactions.
Bug Check 0xC000021A: STATUS_SYSTEM_PROCESS_TERMINATED
Cause

This error occurs when a user-mode subsystem, such as WinLogon or the Client Server Run-Time Subsystem (CSRSS), has been fatally compromised and security can no longer be guaranteed.
In response, the operating system switches to kernel mode. Microsoft Windows cannot run without WinLogon or CSRSS.
Therefore, this is one of the few cases where the failure of a user-mode service can shut down the system.

Mismatched system files can also cause this error. This can occur if you have restored your hard disk from a backup. Some backup programs might skip restoring system files that they determine are in use.

Running the kernel debugger is not useful in this situation because the actual error occurred in a user-mode process.

Resolving an error in a user-mode device driver, system service, or third-party application:  

Because bug check 0xC000021A occurs in a user-mode process, the most common culprits are third-party applications.

If the error occurred after the installation of a new or updated device driver, system service, or third-party application, the new software should be removed or disabled. Contact the manufacturer of the software about a possible update.

If the error occurs during system startup, restart your computer, and press F8 at the character-based menu that displays the operating system choices. At the resulting Windows Advanced Options menu, choose the Last Known Good Configuration option. This option is most effective when only one driver or service is added at a time. If this does not resolve the error, try manually removing the offending software. If the system partition is formatted with file allocation table (FAT), use an MS-DOS startup disk to gain access to the computer's hard disk. If the system partition is formatted with NTFS file system, you might be able to use Safe Mode to rename or delete the faulty software. If the faulty software is used as part of the system startup process in Safe Mode, you need to start the computer using the Recovery Console in order to access the file. If a newly installed piece if hardware is suspected, remove it to see if this resolves the issue.

Try running the Emergency Recovery Disk (ERD) and allow the system to repair any errors that it detects.

Resolving a mismatched system file problem: If you have recently restored your hard disk from a backup, check if there is an updated version of the Backup/Restore program available from the manufacturer. Make sure the latest Windows Service Pack is installed.
==================  ===================
Boote mit der Win XP-CD und führe eine Reparatur-Installation durch. Ich denke deaktivieren von Diensten und treibern in der Reparaturkonsole wird zu kompliziert.
==================  ===================
0xC0000135: UNABLE TO LOCATE DLL
Windows attempted to load a DLL file and encountered some error condition. Among the many possible causes are that the file is missing or damaged, or that there is Registry corruption. mögliche Lösungen dafür:
http://support.microsoft.com/?kbid=173309&sd=RMVP
http://support.microsoft.com/?kbid=318159&sd=RMVP
==================  ===================

MSDN Article

Cause This error occurs when a user-mode subsystem, such as WinLogon or the Client Server Run-Time Subsystem (CSRSS), has been fatally compromised and security can no longer be guaranteed. In response, the operating system switches to kernel mode. Microsoft Windows cannot run without WinLogon or CSRSS. Therefore, this is one of the few cases where the failure of a user-mode service can shut down the system.

Mismatched system files can also cause this error. This can occur if you have restored your hard disk from a backup. Some backup programs might skip restoring system files that they determine are in use.

This error occurs when a user-mode subsystem, such as WinLogon or the Client Server Run-Time Subsystem (CSRSS), has been fatally compromised and security can no longer be guaranteed. In response, the operating system switches to kernel mode. Microsoft Windows cannot run without WinLogon or CSRSS. Therefore, this is one of the few cases where the failure of a user-mode service can shut down the system.

Mismatched system files can also cause this error. This can occur if you have restored your hard disk from a backup. Some backup programs might skip restoring system files that they determine are in use.

Resolution
Running the kernel debugger is not useful in this situation because the actual error occurred in a user-mode process.

Resolving an error in a user-mode device driver, system service, or third-party application: Because bug check 0xC000021A occurs in a user-mode process, the most common culprits are third-party applications. If the error occurred after the installation of a new or updated device driver, system service, or third-party application, the new software should be removed or disabled. Contact the manufacturer of the software about a possible update.

If the error occurs during system startup, restart your computer, and press F8 at the character-based menu that displays the operating system choices. At the resulting Windows Advanced Options menu, choose the Last Known Good Configuration option. This option is most effective when only one driver or service is added at a time. If this does not resolve the error, try manually removing the offending software. If the system partition is formatted with file allocation table (FAT), use an MS-DOS startup disk to gain access to the computer's hard disk. If the system partition is formatted with NTFS file system, you might be able to use Safe Mode to rename or delete the faulty software. If the faulty software is used as part of the system startup process in Safe Mode, you need to start the computer using the Recovery Console in order to access the file. If a newly installed piece if hardware is suspected, remove it to see if this resolves the issue.

Try running the Emergency Recovery Disk (ERD) and allow the system to repair any errors that it detects.

Resolving a mismatched system file problem: If you have recently restored your hard disk from a backup, check if there is an updated version of the Backup/Restore program available from the manufacturer. Make sure the latest Windows Service Pack is installed.

0xC000021A: STATUS_SYSTEM_PROCESS_TERMINATED

Source

0xC000021A: STATUS_SYSTEM_PROCESS_TERMINATED

Diese Nachricht tritt auf, wenn Windows in den Kernelmodus wechselt und dadurch ein Subsystem gefährdet ist und die Sicherheit nicht mehr garantiert werden kann. Weitere Ursache könnten fehlerhafter Grafikkartentreiber und/oder Systemdienst eines Drittanbieters sein.

 Mögliche Ursache:

1. Fehlerhafter Gerätetreiber
2. Fehlerhafter Systemdienst eines Drittanbieters

Mögliche Lösungsansätze:

1. Melde Dich als Admin an und führe folgende Befehle aus:
       Start/Ausführen - cmd              [Enter] drücken
    hier dann folgendes eintippen
        sfc /scannow                             [Enter] drücken

2. Start | Ausführen - msconfig.exe
    Gehe dann zu Dienste und setze zuerst einen Haken bei Alle Microsoft-Dienste ausblenden.
    Jetzt schalte alle übrigen ab und boote Dein Rechner neu. Schaue jetzt, ob eine Besserung
    eingetreten ist.

3. Treiber und Programme von Drittanbietern, die Probleme bereiten deinstallieren.

GoBack verursacht Abbruchfehler C000021a 

  (WinXP)
Nach der Installation von GoBack von Roxio (in Norton System Works enthalten) wird Ihnen möglicherweise sinngemäß
folgende Fehlermeldung angezeigt:
C000021a (schwerer Systemfehler). Der Systemprozess für die Sitzungs-Manager-Initialisierung wurde unerwartet mit Status 0xc000003a (0x00000000, 0x00000000) beendet (The Session Manager Initialization system process terminated unexpectedly
with a status of 0xc000003a).

Internet Explorer Maintenance Policies May Cause an Access Violation in Winlogon

  (WinXP Pro)

How to troubleshoot a "STOP 0xC000021A" error

 (WinNT4.0/Win2000,/WinXP Pro/Server2003)
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.

mcseboard.de/ winlogon-process-wurde-unerwartet-beendet

Lesen 

0xC000021A: STATUS_SYSTEM_PROCESS_TERMINATED
How to troubleshoot a "STOP 0xC000021A" error

http://www.jasik.de/shutdown/stop_fehler.htm#21A 

Q156669

=================  =================

How to troubleshoot a "STOP 0xC000021A" error

Solution of error

To troubleshoot this problem, you must determine which of these processes failed and why.
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:

1. 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.
2. At a command prompt, type
   System Root\System32\Drwtsn32.exeand then select the following options:
   Append to existing log file
   Create crash dump
   Visual Notification
3. After the computer restarts from the STOP 0xC000021A error, run Dr. Watson (Drwtsn32.exe).
4. View the Dr. Watson log to determine what user mode process may be causing the problem.
5. 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 file
   Note 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:
   • Winlogon.exe
   • Csrss.exe
   Note Most STOP 0xC000021A errors occur because Winlogon.exe fails. This typically occurs because of a faulty third-party Graphical Identification and Authentication (GINA) DLL. The GINA is a replaceable DLL component that Winlogon.exe loads. The GINA implements the authentication policy of the interactive logon model. The GINA performs all identification and authentication user interactions.

It is very common for certain types of remote control software to replace the default Windows GINA DLL (Msgina.dll). Therefore, a good first step is to examine the system to see if it has a third-party GINA DLL. To do this, locate the following registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon

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.

If this error first occurred after the installation of a new or updated device driver, system service, or third-party program, the new software should be removed or disabled. Contact the manufacturer of the software to see if an update is available. For more information about hardware and software vendor contact information, visit the following Microsoft Web site: -

  http://support.microsoft.com/gp/vendors  

Last known good configuration  

If 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.

1. Click Start, and then click Shut Down.
2. Click Restart, and then click OK.
3. 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.
4. 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.
5. Use the arrow keys to highlight an operating system, and then press ENTER.

Notes

• 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 upgrade 

If 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:

292175  How to perform an in-place upgrade of Windows 2000

315341  How to perform an in-place upgrade (reinstallation) of Windows XP

816579  How to perform an in-place upgrade of Windows Server 2003

Remove incompatible software by using the Recovery Console 

If 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.

313670  How to replace a driver by using Recovery Console in Windows 2000

816104  How to replace a driver by using Recovery Console in Windows Server 2003

326215  How to use the Recovery Console on a Windows Server 2003-based computer that does not start

229716  Description of the Windows 2000 Recovery Console

307654  How to install and use the Recovery Console in Windows XP

307545  How to recover from a corrupted registry that prevents Windows XP from starting

216417  How to install the Windows Recovery Console
=================   ==================
Fehlermeldung: Die Anwendung konnte nicht richtig initialisiert werden (0xc0000135).
Das Microsoft .NET Framework Version 2.0 Redistributable Package muss installiert werden !

mcseboard.de/stop-0xc000021a-waehrend-ausfuehrung-xp-setup
Speicherzugriffsverletzung: Status 0xc0000005 das ist schliesslich auch möglich..Speicher raus ... . 
Speicher raus ...