Stop: c000021a {Fatal System Error} The session manager initialization system process terminated unexpectedly with a status of 0xc0000022 (0x00000000, 0x0000000) The system has been shut down.

Question

Stop: c000021a {Fatal System Error} The session manager initialization system process terminated unexpectedly with a status of 0xc0000022 (0x00000000, 0x0000000) The system has been shut down.

Anonymous

Getting this message when trying to start up my computer. Windows 7-64 bit.

When I restart a second time, Startup Repair goes through a run and reports "Startup Repair cannot repair this computer automatically.

Problem details are:

Problem Signature:

Problem Event Name: StartupRepairOffline

Proglem Signature 01: 6.1.7600.16385

Proglem Signature 02: 6.1.7600.16385

Proglem Signature 03: unknown

Proglem Signature 04: 20

Proglem Signature 05: Autofailover

Proglem Signature 06: 1

Proglem Signature 07: NoRootCause

OS Version: 6.1.7600.2.0.0.256.1

Locale ID: 1033

The view diagnostic and repair details show that all tests were completed successfully.

Root causes found: Unspecified changes to system configuration might have caused the problem.

Repair action: System files integrity check and repair

Result: Failed. Error code - 0x490

Time taken = 621601 ms

I have tried system restore a number of times and none of the restore points helped. After many different restore attempts, I ran a system image recovery. There was only one system image available from a backup created at the start of the week. The same issues were all still there when I tried to startup the computer.

I am able to boot into safe mode, but any time I try to boot without safe mode, the system always crashes and either reports the error or just stops while Windows is loading.

I have searched other solutions and tried:

a) to see if there were any pending renames

b) disabled all non-Microsoft startup items.

Edit: I have found other c000021a errors reported and other 0x0000022 errors, but now always reported together. Two reported together are. Both are on XP systems though and the first one couldn't boot into safe mode either, so to me it looks like it's not the same symptoms, but what do I know.

1) http://www.techspot.com/vb/topic75410.html

2) http://www.computing.net/answers/windows-xp/stop-c000021a-fatal-system-error/19239.html

The most recent software that I installed were all the utilities that came with my Asus motherboard and were installed one week before this problem. The system image was from after this software was installed. I tried restore points both before and after this install. It is possible that my system wasn't shut down (just hibernated) since the software was installed, so this may have been the first time the system needed to be started, but I'm not 100% sure on that.

I hope I wasn't being too detailed in my question.

Hope someone can help me. Thanks in advance for any replies.

Ray

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

Answer accepted by question author

7 additional answers

Answer 1

Hi,

This is to add some to Sudarshan Bhatt's excellent information :

STOP: 0xC000021A

Can be a difficult problem to solve and you may indeed need technical help from a real computer shop

(not leeks and peeks at a BestBuy or other BigBox stores) or the System maker's Support.

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 WindowsAdvanced Options menu, choose theLast 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.

STOP: 0xC000021A <-- read this linkhttp://www.faultwire.com/solutions-fatal\_error/STATUS-SYSTEM-PROCESS-TERMINATED-0xC000021A-\*1314.html

Look in the Event Viewer to see if anything is reported about those.

http://www.computerperformance.co.uk/vista/vista\_event\_viewer.htm

MyEventViewer - Free - a simple alternative to the standard event viewer of Windows.

TIP - Options - Advanced Filter allows you to see a time frame instead of the whole file.

http://www.nirsoft.net/utils/my\_event\_viewer.html

This is my generic bluescreen troubleshooter - you can try Safe Mode as suggested in the article

above - repeatedly tap F8 as you boot. Vista disks are probably needed - if you do not have to try

repair you can borrow a friends as they are not copy protected. Also you can buy the physical

disks from the system maker cheap as you already own Windows (you will need these to reinstall

if required). You can also make repair disks on another computer.

Here are some methods to possibly fix the blue screen issue. If you could give the Blue Screen

info that would help. Such as the BCC and the other 4 entries on the lower left. And any other

error information such as STOP codes and info such as IRQL_NOT_LESS_OR_EQUAL or PAGE_FAULT_IN_NONPAGED_AREA and similar messages.

As examples :

BCCode: 116

BCP1: 87BC9510

BCP2: 8C013D80

BCP3: 00000000

BCP4: 00000002

or in this format :

Stop: 0x00000000 (oxoooooooo oxoooooooo oxooooooooo oxoooooooo)

tcpip.sys - Address 0x00000000 base at 0x000000000 DateStamp 0x000000000

This is an excellent tool for posting Blue Screen Error Information

BlueScreenView scans all your minidump files created during 'blue screen of death' crashes,

and displays the information about all crashes in one table - Free

http://www.nirsoft.net/utils/blue\_screen\_view.html

Many BlueScreens are caused by old or corrupted drivers, especially video drivers however

there are other causes.

You can do these in Safe Mode if needed or from Command Prompt from Vista DVD or

Recovery Options if your system has that installed by the maker.

How to Boot to the System Recovery Options in Windows 7

http://www.sevenforums.com/tutorials/668-system-recovery-options.html

You can try a System Restore back to a point before the problem started if there is one.

How to Do a System Restore in Windows 7

http://www.sevenforums.com/tutorials/700-system-restore.html

Start - type this in Search Box -> COMMAND find at top and RIGHT CLICK - RUN AS ADMIN

Enter this at the prompt - sfc /scannow

How to Repair Windows 7 System Files with System File Checker

http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

How to analyze the log file entries that the Microsoft Windows Resource Checker (SFC.exe) program

generates in Windows Vista cbs.log (and Windows 7)

http://support.microsoft.com/kb/928228

The log might give you the answer if there was a corrupted driver. (Does not tell all the possible

driver issues).

Also run CheckDisk so we can rule out corruption as much as possible.

How to Run Check Disk at Startup in Windows 7

http://www.sevenforums.com/tutorials/433-disk-check.html

Often updating drivers will help, usually Video, Sound, Network Card (NIC), WiFi, 3rd party

keyboard and mouse, as well as other major device drivers.

Manually look at manufacturer's sites for drivers - and Device Maker's sites.

http://pcsupport.about.com/od/driverssupport/ht/driverdlmfgr.htm

Installing and updating drivers in Windows 7 (updating drivers manually using the methods above

is preferred to ensure the latest drivers from System maker and Device makers are found)

http://www.sevenforums.com/tutorials/43216-installing-updating-drivers-7-a.html

How To Disable Automatic Driver Installation In Windows Vista - Drivers

http://www.addictivetips.com/windows-tips/how-to-disable-automatic-driver-installation-in-windows-vista/

http://technet.microsoft.com/en-us/library/cc730606(WS.10).aspx

How to fix BlueScreen (STOP) errors that cause Windows Vista to shut down or restart

unexpectedly

http://support.microsoft.com/kb/958233

Troubleshooting Vista Blue Screen, STOP Errors (and Windows 7)

http://www.chicagotech.net/vista/vistabluescreen.htm

Understanding and Decoding BSOD (blue screen of death) Messages

http://www.taranfx.com/blog/?p=692

Windows - Troubleshooting Blue Screen Errors

http://kb.wisc.edu/page.php?id=7033

In some cases this might be required.

StartUp Repair from Recovery Options or Windows 7 disk

How to Run a Startup Repair in Windows 7

http://www.sevenforums.com/tutorials/681-startup-repair.html

How to Boot to the System Recovery Options in Windows 7

http://www.sevenforums.com/tutorials/668-system-recovery-options.html

How to Create a Windows 7 System Repair Disc

http://www.sevenforums.com/tutorials/2083-system-repair-disc-create.html

Hope this helps and Happy Holidays!

Rob Brown - Microsoft MVP <- profile - Windows Expert - Consumer : Bicycle - Mark Twain said it right.

Answer 2

Hi Rob -

Thank you for your reply and suggestions as well. Also, thanks you for the explanations of the error codes.

Unfortunately, it could be that the reason Last Know Good Configuration is not working for me is because it's possible that more than one service or driver was added at once. I added all of the software that came on my Asus support CD at once. I haven't yet figured out if this is the culprit though. I have tried to uninstall the software, but this is not possible to do in Safe mode. It appears that the software may no longer be installed though as system restore could have removed it. As I wrote in my last post, system restore reported an error in Windows Recovery Environment, but then when logging in through Safe mode, Windows reported that my system has been restored and the Programs no longer appear in the start menu (but they are still all in the programs folder).

It is also possible that the error is now being caused by Mismatched system files as I did restore my hard disc from a backup after all my initial failed attempt to get the system working after a system restore. The system image was from Windows backup.

I ran both chkdsk and sfc/scannow.

chkdsk resulted in "checkdisk discovered free space marked as allocated in the master file table <MFT> bitmap. checkdisk discovered free space marked as allocated in the volume bitmap. Windows has make corrections to the file system."

Not sure if this rules our anything or even what this means.

sfc/scannow showed no repairs as far as I can tell based on using "findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >%userprofile%\Desktop\sfcdetails.txt" and then looking at the resulting sfcdetails.txt file.

Ray

Answer 3

Hi Sudarshan -

Thank you for your reply and suggestions.

To answer your questions:

1. Do you get blue screen while you boot into your desktop? Yes. Sometimes a Blue screen appears within a few seconds before Windows graphic appears. This is when the Stop error "c000021a" from the title of this post appears. Other times when the blue screen doesn't appear it starts booting into Windows with the Windows graphic and then the computer just stops and restarts.

2. Do you have the Windows Operating System Disc? I have a Win 7 Pro. 64-bit Upgrade disc.

I have tried all of your suggestions. Still can't get into Windows.

Methods 1 and 3 were same as a regular startup.

Method 2 (system restore) resulted in an error stating that: "System restore did not complete successfully. Your computer's system files and settings were not changed. " Details: an unspecified error occurred during system restore. 0x8000ffff"

However, when I logged in to Windows in Safe mode after this message, I got a message saying that my system was restored to the date and time that I had chosen from the Windows Recovery Environment mode.

Also when running system restore from within Windows safe mode, there are no restore points. The restore points only exist in Windows Recovery Environment mode.

Method 4 (chkdsk /r) resulted in: "checkdisk discovered free space marked as allocated in the master file table <MFT> bitmap. checkdisk discovered free space marked as allocated in the volume bitmap. Windows has make corrections to the file system."

There were no other errors reported by checkdisk as far as I can tell.

Ray

Answer 4

Hi,

Use if needed :

You could also back up the data and re-install Windows 7. The hard drive can be put into

another computer as 2nd drive (best) or into an External USB case. Either would allow

you to copy the data to removable media such as CD, DVD, or other USB drives.

Or you could use an Ubuntu boot CD to back up the data.

Use Ubuntu Live CD to Backup Files from Your Dead Windows Computer

http://www.howtogeek.com/howto/windows-vista/use-ubuntu-live-cd-to-backup-files-from-your-dead-windows-computer

Hope this helps and Happy Holidays!

Rob Brown - Microsoft MVP <- profile - Windows Expert - Consumer : Bicycle <- Mark Twain said it right.

Answer 5

Hi,

1. Do you get blue screen while you boot into your desktop?

2. Do you have the Windows Operating System Disc?

Method 1:

a) Unplug all the external device (except the keyboard and mouse) connected to the system.

b) Restart the computer and check if you are able to boot normally.

Use Windows Installation Disc to perform Startup and System Restore to perform these methods. Method 2: Perform System Restore from Windows Recovery Environment mode.

a) Insert the disc.

b) Restart your computer using the computer's power button.

c) If prompted, press any key to start Windows from the installation disc.

d) If your computer isn't configured to start from a CD/DVD, check the information that came with your computer. You may need to change your computer's BIOS settings.

e) Choose your language settings, and then click Next.

f) If you are using the Windows installation disc, click on System Restore. g) Choose a earlier Restore point, which is listed and was working fine. h) Click ok when prompted. Note: Modifying BIOS/ complementary metal oxide semiconductor (CMOS) settings incorrectly can causeserious problems that may prevent your computer from booting properly. Microsoft cannot guarantee that any problems resulting from the configuring of BIOS/CMOS settings can be solved. Modifications of the settings are at your own risk.

Refer the links mentioned below. http://windows.microsoft.com/en-US/windows7/System-Restore-frequently-asked-questions

http://windows.microsoft.com/en-US/windows7/What-is-System-Restore

Method 3: Last Known Good Configuration.

Let’s start the computer by using the last known good configuration. To start the computer by using the last known good configuration, follow the steps mentioned:

a) Restart the computer and tap F8. You will see the Advance Boot options menu.

b) Use the arrow keys to select Last Known Good Configuration, and then press ENTER.

c) NUM LOCK must be off before the arrow keys on the numeric keypad will function.

d) Use the arrow keys to highlight an operating system, and then press ENTER.

Note: Choosing the Last Known Good Configuration startup option provides a way to recover from problems such as a newly added driver that may be incorrect for your hardware. However, it does not solve problems that are caused by corrupted or missing drivers or files.

Refer the link mentioned below and check if it helps.

http://windows.microsoft.com/en-US/windows7/Advanced-startup-options-including-safe-mode

Method 4:

Follow the link mentioned below and run the “chkdsk /r” command from Windows Recovery Environment.

a) Insert the disc.

b) Restart your computer using the computer's power button.

c) If prompted, press any key to start Windows from the installation disc.

d) If your computer isn't configured to start from a CD/DVD, check the information that came with your computer. You may need to change your computer's BIOS settings.

e) Choose your language settings, and then click next.

f) If you are using the Windows installation disc, click on Command prompt.

g) Type **chkdsk /**r in the command prompt and hit Enter.

http://windows.microsoft.com/en-US/windows-vista/What-happened-to-the-Recovery-Console

Let us know if it helps.

Share via

Stop: c000021a {Fatal System Error} The session manager initialization system process terminated unexpectedly with a status of 0xc0000022 (0x00000000, 0x0000000) The system has been shut down.

7 additional answers