STOP: c000021a {Fatal System Error}

[Tripredacus]

Here we go! Looks to be the first Windows 7 topic about this dreaded error. This happens at boot up on one board only. It works fine on about 5 other configs I have tried it on. Now this is being deployed from Win PE and I can't post the script I use. Knowing that in the past, this error generally means either a hardware problem on the client, or a delivery method problem (bad/scratched optical media) I attempted a reimage but the results are the same.

The first thing that comes up is "Autochk program not found - skipping Autocheck"

As far as I can tell the image deployed properly. Also, I can put XP or Vista on it instead and that works fine. If you don't know this legendary error, here is the full thing:

STOP: C000021A {Fatal System Error}

The Session Manager Initialization system process terminated unexpectedly with a status of 0xC000003A (0x0 0x0). The System has been shutdown

Here is the config it is happening on:

Intel DG45FC (with BIOS v0087*)

2GB DDR2-667 (PC2-5300, 2x1GB)

E5200 2.5GHz CPU

160GB Toshiba Mobile SATA 300 5400RPM

Any ideas would be keen!

*This BIOS version is the latest stable version for the DG45FC. The DG45FC and DG45ID use the same BIOS. The latest version I have tried, v0113, works fine on the DG45ID, but on the FC board it breaks the PXE ROM. All versions after v0087 break the PXE ROM, which effectively means that it gets the Boot ROM via TFTP from the PXE Server, but does not give you the F12 option to boot to the network.

[TheReasonIFail]

Is this an OEM PC? A client just purchased 10 new Dell Vostro 420's and out of the 5 I got up and running, 2 have exhibited this error. The PC's are running XP but they're using the Vista bootloader which I find extremely dumb, but I digress.

Have you looked at the RAM?

[MagicAndre1981]

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.

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.

Could you create a dump and share it, so that cluberti can look at it.

[Tripredacus]

Is this an OEM PC? A client just purchased 10 new Dell Vostro 420's and out of the 5 I got up and running, 2 have exhibited this error. The PC's are running XP but they're using the Vista bootloader which I find extremely dumb, but I digress.

Have you looked at the RAM?

It is an OEM PC but it does not have any proprietary components. I will have it run a memtest since right now its just sitting there doing nothing.

Bug Check 0xC000021A: STATUS_SYSTEM_PROCESS_TERMINATED

Could you create a dump and share it, so that cluberti can look at it.

Andre, I do not have access to the system. It cannot boot into Windows normal or Safe Mode. At first boot, it should be "Setting up your computer for first use" as this is the message you get if you were to, say, Sysprep /audit /generalize /reboot. So that is the state the machine is in at the time of boot.

[cluberti]

Does it repro in audit mode?

[Tripredacus]

The computer, after the deployment from WinPE, should be booting as if Syprep was set as /generalize /audit /reboot. So I guess that answers your question. I have not tried to do a hand-load on that particular computer.

I can say that the computer failed the memtest at pass 5. Tomorrow I'll get the memory replaced and we'll see what happens then.

You know, I really hate this DG45FC board. I've had 3 SRs with Microsoft about it and currently 2 quads with Intel too. Its horrible! I can't wait for it to go EOL.

[Tripredacus]

I have resolved this issue on my own. I cannot go through the steps of resolution, but it turned out the partition type was incorrect. It may be possible that other people may get this error for other reasons, so I'll leave the topic open.

Thanks for your input!