Fatal Error c000021a

  • Thread starter Thread starter avsfan0801
  • Start date Start date
A

avsfan0801

I have a Dell Insprion 1525 laptop running Windows Vista. Yesterday, I came
home and turned it on and this is the error message that came up on a blue
screen:

STOP: c000021a {Fatal System Error}
The verification of a knownDLL failed. system process terminated
unexpectedly wtih a status of 0xc0000000 (0xc0000034 0x0010037c). The system
has been shut down.

I got this error message when I tried to use the startup disk to repair it.

STOP: c000021a {Fatal System Error}
The verification of a knownDLL failed. system process terminated
unexpectedly wtih a status of 0xc000012f (0x8aa37e50 0x000000000). The system
has been shut down.

I searched online and apparently there's an update that is causing this
problem. I can't seem to fix it though. My computer will not boot.

Now when I turn it off and restart, I get the black screen telling me start
in safe mode and repair or start in regular mode. I've chosen both. Repair
mode takes me to blue screen, regular mode just comes up black screen with
microsoft and the loading bar, and it just keeps trying to load and does
nothing.

Can anyone help me fix this?

Thank you!! :)
 
It seems you have a corrupted core system file (all executables and dlls
start with the initials MZ [the initials of a programmer who developedthe
Dos executable format]).

If you can't boot then there is nothing you can do to repair. See if you can
boot with Vista's DVD and Repair using setup.


*******************************************************************************
From NTStatus.h
*******************************************************************************
//
// MessageId: STATUS_INVALID_IMAGE_NOT_MZ
//
// MessageText:
//
// The specified image file did not have the correct format, it did not have
an initial MZ.
//
#define STATUS_INVALID_IMAGE_NOT_MZ ((NTSTATUS)0xC000012FL)

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

Parameters
The error message includes the following three parameters, in order of
appearance:

Parameter Description
1 Status code
2 0
3 0


For information about all possible status codes that might be returned, see
the file ntstatus.h in the Windows DDK.

Cause
This error occurs when a user-mode subsystem, such as WinLogon or the Client
Server Runtime 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 a Microsoft 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
*******************************************************************************
 
Back
Top