Blue Screen error message Stop: c000021a {Fatal System Error}

It is too bad that we know absolutely nothing about your system, but that is the way they choose to run the MS Answers forums.

If you are seeing a message like this:

STOP: c000021a {Fatal System Error}

The Session Manager Initialization system process terminated unexpectedly with a status of 0xc000026c (0x00000000 0x00000000).

The system has been shut down.

That indicates that the win32k.sys file has somehow become corrupted.

If the win32k.sys file was missing, you would see a message like this:

STOP: c000021a {Fatal System Error}

The Session Manager Initialization system process terminated unexpectedly with a status of 0xc0000034 (0x00000000 0x00000000).

The system has been shut down.

Notice the similarities and the differences in the status values...  either way, the win32k.sys file needs replacing.

Your 0xc000026c indicates the file is not missing, but somehow corrupted, so you can see about booting into the XP Recovery Console and replacing it with backup copies that should already be on your system.

Since you have already tried to do a repair with a borrowed CD, there is no telling what shape things are in now, but I would see about just replacing the suspicious win32k.sys file.

To do that, you need to be in the XP Recovery Console entering it by booting from a genuine bootable XP installation CD or from a bootable XP Recovery Console CD you can make yourself (no XP media required).  Instructions are available if you need them. 

It would not hurt to run a chkdsk /r from the XP Recovery Console first, but you may be able to just replace the suspicious file.

We know that XP keeps backup copies of important files in this folder (assuming XP is installed on your C drive):

c:\windows\system32\dllcache

Once you get into the XP Recovery Console, I would enter this command to copy the backup copy of the file to the right place:

copy c:\windows\system32\dllcache\win32k.sys   c:\windows\system32

Respond in the affirmative if asked to overwrite the existing file and then you should see a message that 1 file(s) was copied.

If the file is not found in the dllcache folder, depending on your installation, this command may work:

copy c:\windows\ServicePackFiles\i386\win32k.sys   c:\windows\system32

Respond in the affirmative if asked to overwrite the existing file and then you should see a message that 1 file(s) was copied.

After you have replaced the file, remove the bootable CD and enter 'exit' and your system will restart.

I appreciate all the assistance you've provided so far.  If I only knew what the contents of the file should be, I could attempt to go in and see what's missing, or what files needed repaired, with another cd that contains a mini xp system.

I followed your instructions by making two separtate Bootable XP Recovery Console CD's, one as a backup in case the first one had a scratch on the dvd.  Neither one would bring my computer into the Recovery Console.  I used the cd I borrowed again, and was able to get into the computer recovery screen.  I tried   copy c:\windows\system32\dllcache\win32k.sys c:\windows\system32

but the computer still had the same issue, continue to boot in the loop of the same BSOD error.  I tried     copy c:\windows\ServicePackFiles\i386\win32k.sys c:\windows\system32

   again the computer still has the same issue, continues to boot in the loop with the same BSOD error.  I've tried the     chkdsk C: /r      approximately three times Tuesday,to times again Wednesday, and three times Thursday.    This was before I received  assistance from this site.  I'm tring it again now.   Will advise how things go after a few more attempts.

Here are instructions to make a bootable XP Recovery Console CD from scratch (no XP media required):

If you have no bootable XP media (or are not sure what you have) create a bootable XP Recovery Console CD and be sure what you have (no XP media required).

This is not the same as any recovery disks that might have come with a store bought system. 

You can make a bootable Recovery Console CD by downloading an ISO file and burning it to a CD.

The bootable ISO image file you need to download is called:

xp_rec_con.iso 

Download the ISO file from here:

http://www.mediafire.com/?ueyyzfymmig

Use a new CD and this free and easy program to burn your ISO file and create your bootable CD (do not install UniBlue or the Ask Toolbar - ever!):

http://www.imgburn.com/

Here are some instructions for ImgBurn:

http://forum.imgburn.com/index.php?showtopic=61

It would be a good idea to test your bootable CD on a computer that is working.

You may need to adjust the computer BIOS settings to use the CD ROM drive as the first boot device instead of the hard disk.  These adjustments are made before Windows tries to load.  If you miss it, you will have to reboot the system again.

When you boot on the CD, follow the prompts:

Press any key to boot from CD...

The Windows Setup... will proceed.

Press 'R' to enter the Recovery Console.

Select the installation you want to access (usually  1: C:\WINDOWS)

You may be asked to enter the Administrator password (usually empty).

You should be in the C:\WINDOWS folder.  This is the same as the 

C:\WINDOWS folder you see in explorer.

The Recovery Console allows basic file commands like: copy, rename, replace, delete, cd, chkdsk, fixboot, fixmbr, etc.

For a list of Recovery Console commands, enter help at the prompt or read about the XP Recovery Console here:

http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/recovery_console_cmds.mspx?mfr=true

A good idea before starting things is to first verify the integrity of your file system using the chkdsk command.

From the command prompt window run the chkdsk command on the drive where Windows is installed to try to repair any problems on the afflicted drive.

Running chkdsk is fine even if it doesn't find any problems.  It will not hurt anything to run it.

Assuming your boot drive is C, run the following command:

chkdsk C: /r

Let chkdsk finish and correct any problems it might find.  

It may take a long time for chkdsk to complete or it may appear to be 'stuck'.  Be patient.  If the HDD light is still flashing, chkdsk is doing something.  Keep an eye on the percentage amount to be sure it is still making progress.  It may even appear to go backwards sometimes.

You should run chkdsk /r again until it finds no errors to correct.