STOP: c000021 {Fatal System Error}

RMSistight

Golden Member
Oct 2, 2003
1,740
0
0
Now I know this is suppose to be in the Software forum, but I figured more people are reading the Off Topic sections so I would it would be best to post it here.

This is the second time this has happened to me after I formatted my system the first time. The computer would boot, then the blue screen of death would pop up and my system would restart.

Luckily, Windows now has a function to disable automatic restarts upon system failures so I would able to get this error message:

STOP: c000021a {Fatal System Error}
The Session Manager Initialization system process terminated unexpectly with a status of 0x00000034 (0x00000000 0x00000000)


I'm trying to figure out what the hell is the problem. Any thoughts?
 

Gooose

Banned
Nov 9, 2004
827
0
0
weird seems to be at the beginning of whatever it is running

hdd bad?

and i think this is in the WRONG FORUM
 

zixxer

Diamond Member
Jul 6, 2001
7,326
0
0
being a n00b this is unacceptable. post in the right forum. Only very seasoned members may post in incorrect forums... lol
 

Hammer

Lifer
Oct 19, 2001
13,217
1
81
your system is dead. put it in a box and throw it in the dumpster. go out and buy a new one.
 

poopaskoopa

Diamond Member
Sep 12, 2000
4,836
1
81
What was the last thing that was changed/installed?

From Windbg:

Bug Check 0xC000021A: STATUS_SYSTEM_PROCESS_TERMINATED
The STATUS_SYSTEM_PROCESS_TERMINATED bug check has a value of 0xC000021A. This means that an error has occurred in a crucial user-mode subsystem.

Parameters
This bug check will display a descriptive text message.

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.

Resolving the Problem
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.



 

RMSistight

Golden Member
Oct 2, 2003
1,740
0
0
Originally posted by: Toastedlightly
bad ram potentially. Change RAM, and do a scandisk on your hd.

The RAM is good.

My roommate said it could be my power supply. I'm running a 330W PSU and was wondering if it's not enough juice.
 

Toastedlightly

Diamond Member
Aug 7, 2004
7,215
6
81
test all your ram? Do it one st ick at a time, and you have to have good ram whist installing (sounds like corrupted power supply)
 

RMSistight

Golden Member
Oct 2, 2003
1,740
0
0
Originally posted by: poopaskoopa
What was the last thing that was changed/installed?

From Windbg:

Bug Check 0xC000021A: STATUS_SYSTEM_PROCESS_TERMINATED
The STATUS_SYSTEM_PROCESS_TERMINATED bug check has a value of 0xC000021A. This means that an error has occurred in a crucial user-mode subsystem.

Parameters
This bug check will display a descriptive text message.

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.

Resolving the Problem
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.

The computer won't boot period. Last known configuration doesn't work and safe mode doesn't work either. I'm going to try ERD Commander to see if that will help.

 

GeekDrew

Diamond Member
Jun 7, 2000
9,099
19
81
What are the networking options & installation that you've put on that machine? In particular, have you installed any network clients other than the defaults provided by windows (say, for example, Client for NetWare Networks...)
 

RMSistight

Golden Member
Oct 2, 2003
1,740
0
0
Originally posted by: Toastedlightly
test all your ram? Do it one st ick at a time, and you have to have good ram whist installing (sounds like corrupted power supply)

Well..here is what I'm running in terms of juice:

AMD Athlon 2500+
ECS N2U400-A motherboard
1GB of PC3200 Corsair ValueRAM
Sound Blaster Audigy
GeForce FX 5900 Ultra 256MB
Maxtor 120GB HD
Maxtor 80GB HD
Lite-On DVDRW +-8X
Lite-On CDRW 52X
USB 2.0 5-port PCI card
Vantec 4 fan controller(5.25")
4 port fan controller (3.25")
Belkin front mounted 4 USB 2.0 ports
Vantec Tornado 80mm
4 x 80mm fans
1 x 92mm fan

That's all I can think of for now. I do have a brand new 450W PSU I could install.
 

RMSistight

Golden Member
Oct 2, 2003
1,740
0
0
Originally posted by: GeekDrew
What are the networking options & installation that you've put on that machine? In particular, have you installed any network clients other than the defaults provided by windows (say, for example, Client for NetWare Networks...)

No software client installed.
 

GeekDrew

Diamond Member
Jun 7, 2000
9,099
19
81
Originally posted by: RMSistight
Originally posted by: GeekDrew
What are the networking options & installation that you've put on that machine? In particular, have you installed any network clients other than the defaults provided by windows (say, for example, Client for NetWare Networks...)

No. I only use the onboard NIC the MB is supplied with.

OK... I'm of no further help then. :(
 

maziwanka

Lifer
Jul 4, 2000
10,415
1
0
i would guess if it happened twice it might be something wrong with your copy of the OS.

edit: this is beyond the scope of my pc knowledge so i cannot be made fun of for this response.
 

RMSistight

Golden Member
Oct 2, 2003
1,740
0
0
Originally posted by: maziwanka
i would guess if it happened twice it might be something wrong with your copy of the OS.

edit: this is beyond the scope of my pc knowledge so i cannot be made fun of for this response.

I use a legit copy of Windows XP Professional that I got from attending a Visual Studio.net launch event at my university.