Boot Critical File Corrupt Windows 7
Bugcheck c000021a. Parameters= 0xfffff8a00828f190, 0x0, 0xffffffffc0000001, 0x100610 Boot critical file corrupt Repair action: File repair Result: Failed. Error Code= 0x2
March 9th, 2011 7:52am

Bug Check 0xC000021A: STATUS_SYSTEM_PROCESS_TERMINATED This means that an error has occurred in a crucial user-mode subsystem. http://msdn.microsoft.com/en-us/library/ff560177%28VS.85%29.aspx 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. Resolution 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. 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."A programmer is just a tool which converts caffeine into code" Want to install RSAT on Windows 7 Sp1? Check my HowTo: http://www.msfn.org/board/index.php?showtopic=150221
Free Windows Admin Tool Kit Click here and download it now
March 9th, 2011 7:55am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics