STOP: C000021A {FATAL SYSTEM ERROR} THE SESSION MANAGER INITIALIZATION SYSTEM TERMINATED UNEXPECTEDLY WITH A STATUS OF 0X0000022 (0X00000000 0X00000000). THE SYSTEM HAS BEEN SHUT DOWN This is an error message that windows give to me after I install IIS for windows XP pro, this error means nothing to me as I know nothing about error messages. When this error occures I can not gain access to windows by any means, safe mode/command prompt/debug mode all produce this error. Current System Asus A7M266 m/board with 1005 bios 512MB DDR (2x256) (266) AMD T-bird 1.2GHZ (266) Asus AGP V7700 GeForce 2 Hercules Game Theater XP sound 2x maxtor HDDs (30GB + 80GB) CD-RW DVD-Rom 2xNIC I have been through all the standard checks like replacing the componants one at a time, using only one of the DDR block (tried both), boot off a different HDD. The only things that I could not change were the CPU, both DDRs and the m/board. I did manage to place the HDD into another PC with a different m/board and then place all my componants into it excluding the CPU and DDRs (SD board) and the same problem occured. I am also using 2 completely different XP Pro CDs in an attempt to get it working. Does anyone have any ideas about this error and how to stop it (not installing IIS is not an option,) I will be greatful of any help. Thankyou

This also seems to apply to Win 2000 (by extension WinXP) because of code base. Terminating Login Process to Crash System Reported By: Michael Hines, Katherine Price, and Tugkan Tuglular Affects: Windows NT 4.0 Type: Denial of Service Status: Appears to have been corrected Description The Windows NT 4.0 system can be crashed by shutting down the resident login process WINLOGON. The resident login process is normally protected from shutdown through the Task Manager, however if the debugger is attached to the resident login process and then the debugger is closed, the process is also terminated. This results in a blue screen with the error message: STOP C000021a. Fatal System Error The Windows Logon Process terminated unexpectedly with a status of 0x00000000 (0x00000000 0x00000000). The system has been shut down. Beginning dump of physical memory. The system then automatically does a warm boot. At startup, while logging in, you get a message ``System Process - Out of Virtual Memory'' with text ``Your system is running low in virtual memory.'' You can click OK and continue login processing. Once the system is restarted, you use the Event Viewer to find traces of the blue screen event. There is nothing recorded in the application log, nor in the security log. There is an entry in the system log that says: The computer has rebooted from a bugcheck. The bugcheck was 0x000021a (0xe13dff28, 0x00000000, 0x00000000). Microsoft Windows NT (v15.1381). A dump was saved in: C:\WINNT\MEMORY.DMP. The Windows NT 4.0 documentation indicates ``Windows NT is a secure operating environment, designed to meet the requirements of C-2 level (U.S. Department of Defense) security.'' Requirements that Windows NT claims to meet include: Access to system resources can be discretely controlled. All system access can be recorded and audited. Access to the system requires a password and leaves an audit trail. Hope this helps.

STOP Msg: c000021a Logging on a Second Time to WinNT 3.51 w/ SP2 (Q126689) This might also help explain: Terminating Login Process to Crash System Reported By: Michael Hines, Katherine Price, and Tugkan Tuglular Affects: Windows NT 4.0 Type: Denial of Service Status: Appears to have been corrected Description The Windows NT 4.0 system can be crashed by shutting down the resident login process WINLOGON. The resident login process is normally protected from shutdown through the Task Manager, however if the debugger is attached to the resident login process and then the debugger is closed, the process is also terminated. This results in a blue screen with the error message: STOP C000021a. Fatal System Error The Windows Logon Process terminated unexpectedly with a status of 0x00000000 (0x00000000 0x00000000). The system has been shut down. Beginning dump of physical memory. The system then automatically does a warm boot. At startup, while logging in, you get a message ``System Process - Out of Virtual Memory'' with text ``Your system is running low in virtual memory.'' You can click OK and continue login processing. Once the system is restarted, you use the Event Viewer to find traces of the blue screen event. There is nothing recorded in the application log, nor in the security log. There is an entry in the system log that says: The computer has rebooted from a bugcheck. The bugcheck was 0x000021a (0xe13dff28, 0x00000000, 0x00000000). Microsoft Windows NT (v15.1381). A dump was saved in: C:\WINNT\MEMORY.DMP. The Windows NT 4.0 documentation indicates ``Windows NT is a secure operating environment, designed to meet the requirements of C-2 level (U.S. Department of Defense) security.'' Requirements that Windows NT claims to meet include: Access to system resources can be discretely controlled. All system access can be recorded and audited. Access to the system requires a password and leaves an audit trail. Due to common code base NT/W2k/WinXP, it likely is the answer.

Thanks for the help, but there is no way of me getting back into windwos because that error occurs just as windows loads and so I cant get in. Safe mode and so on also cause this error so I am stuck.

Go to msconfig and see if your win.ini file for xp is normall.I also got the screen of death!by deleating a file called alic,with a subfolder called?anyway I hope you get it fixed I did.system restore trough the key board,good luck! Gary

I pounded on the f8 key as windows comes up.This may get you in where you can do something.again hope the best for you Gary gmupson@kpunet.net Let me know

use an NT boot disk to reformat the drive if you have no other way to get back into the system. This is the only way i can think of to reformat the computer. Go into your bios and change your boot, to boot to 1.4 floopy. when it loads, run the format program. you might want to read up on it before going at it. laterz ^^^This is just to get your system reinstalled again and starting fresh.