woerts
asked on
XP STOP error c000021a
Hi,
I started to get error messages when starting XP. I can`t remember the exact message, but it was something like WINDOWS recovered from a serious error, the registry was restored........
That happened a few times, and now I get the following:
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.
Using ERD commander, it says that the system hive is missing or corrupt.
I`ve renamed the system file in Windows\system32\config to config.old, and copied the one in the Windows\repair directory, but that doesn`t work either. (The sizes of these two files differs with almost 1MB, and it also quickly gives a BSOD -no time to read-and the loops in a reboot)
Is there any way to recover from this? I don`t have the time to reinstall and configure all the apps,
Thank you,
Woerts
I started to get error messages when starting XP. I can`t remember the exact message, but it was something like WINDOWS recovered from a serious error, the registry was restored........
That happened a few times, and now I get the following:
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.
Using ERD commander, it says that the system hive is missing or corrupt.
I`ve renamed the system file in Windows\system32\config to config.old, and copied the one in the Windows\repair directory, but that doesn`t work either. (The sizes of these two files differs with almost 1MB, and it also quickly gives a BSOD -no time to read-and the loops in a reboot)
Is there any way to recover from this? I don`t have the time to reinstall and configure all the apps,
Thank you,
Woerts
Although this is for Win2000 what it says pretty much is the same for XP and this what MS has to say about the error
Stop 0xC000021A or STATUS_SYSTEM_PROCESS_TERM
This Stop message occurs when a user-mode subsystem, such as Winlogon or the Client Server Runtime Subsystem (CSRSS), is fatally compromised and security can no longer be guaranteed. The operating system switches into kernel-mode and generates this error. Because Windows 2000 cannot run without Winlogon or CSRSS, this is one of the few situations where the failure of a user-mode service can bring down the system. Running the kernel debugger is not useful in this situation because the actual error occurred in a user-mode process.
Interpreting the Message
The first three parameters listed in the message are defined in order of appearance as follows:
Status code
(zero)
(zero)
For information about all possible status codes that might be returned, see the file Ntstatus.h of the Windows 2000 Device Driver Kit (DDK).
Resolving the Problem
Device drivers, system services, and third-party applications. Because Stop 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-mode menu that displays the operating system choices. At the resulting Windows 2000 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 FAT, use an MS-DOS startup disk to gain access to the computer's hard disk. If the system partition is formatted with NTFS, 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.
Try running the Emergency Recovery Disk (ERD) and allow the system to repair any errors that it detects.
Mismatched system files. Mismatched system files can also cause this error. Running a full system restore from tape might generate this error (some restore programs might skip restoring system files they determine are in use). Check if there is an updated version of the Backup/Restore program available from the manufacturer.
Microsoft periodically releases a package of product improvements and problem resolutions for Windows 2000 called a Service Pack. Because many problems are resolved by installing the latest Service Pack, it is recommended that all users install them as they become available. To check which Service Pack, if any, is installed on your system, click Start, click Run, type winver, and then press ENTER. The About Windows 2000 dialog box displays the Windows version number and the version number of the Service Pack, if one has been installed.
Occasionally, remedies to specific problems are developed after the release of a Service Pack. These remedies are called hotfixes. Microsoft does not recommend that you install a post-Service Pack hotfix unless the specific problem it addresses has been encountered. Service Packs include all of the hotfixes released since the release of the previous Service Pack. The status of hotfix installations is not indicated in the About Windows 2000 dialog box.
Stop 0xC000021A or STATUS_SYSTEM_PROCESS_TERM
This Stop message occurs when a user-mode subsystem, such as Winlogon or the Client Server Runtime Subsystem (CSRSS), is fatally compromised and security can no longer be guaranteed. The operating system switches into kernel-mode and generates this error. Because Windows 2000 cannot run without Winlogon or CSRSS, this is one of the few situations where the failure of a user-mode service can bring down the system. Running the kernel debugger is not useful in this situation because the actual error occurred in a user-mode process.
Interpreting the Message
The first three parameters listed in the message are defined in order of appearance as follows:
Status code
(zero)
(zero)
For information about all possible status codes that might be returned, see the file Ntstatus.h of the Windows 2000 Device Driver Kit (DDK).
Resolving the Problem
Device drivers, system services, and third-party applications. Because Stop 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-mode menu that displays the operating system choices. At the resulting Windows 2000 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 FAT, use an MS-DOS startup disk to gain access to the computer's hard disk. If the system partition is formatted with NTFS, 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.
Try running the Emergency Recovery Disk (ERD) and allow the system to repair any errors that it detects.
Mismatched system files. Mismatched system files can also cause this error. Running a full system restore from tape might generate this error (some restore programs might skip restoring system files they determine are in use). Check if there is an updated version of the Backup/Restore program available from the manufacturer.
Microsoft periodically releases a package of product improvements and problem resolutions for Windows 2000 called a Service Pack. Because many problems are resolved by installing the latest Service Pack, it is recommended that all users install them as they become available. To check which Service Pack, if any, is installed on your system, click Start, click Run, type winver, and then press ENTER. The About Windows 2000 dialog box displays the Windows version number and the version number of the Service Pack, if one has been installed.
Occasionally, remedies to specific problems are developed after the release of a Service Pack. These remedies are called hotfixes. Microsoft does not recommend that you install a post-Service Pack hotfix unless the specific problem it addresses has been encountered. Service Packs include all of the hotfixes released since the release of the previous Service Pack. The status of hotfix installations is not indicated in the About Windows 2000 dialog box.
Greetings, woerts!
Perform a System Restore
How to Restore Windows XP to a Previous State (System Restore)
http://www.microsoft.com/windowsxp/pro/using/itpro/managing/restore.asp
Best wishes, war1
Perform a System Restore
How to Restore Windows XP to a Previous State (System Restore)
http://www.microsoft.com/windowsxp/pro/using/itpro/managing/restore.asp
Best wishes, war1
ASKER
Ok,
With the help of another copy of XP on a diferent partition and ERD commander I am past the blue screen.
I am now stuck with the following error:
lsass.exe
Security accounts manager initialization failed because of the following error: a device attached to the system is not functioning. Error State 0xc0000001.
When I hit OK, the machine restarts.
Any ideas on this?
Thank you
Woerts
With the help of another copy of XP on a diferent partition and ERD commander I am past the blue screen.
I am now stuck with the following error:
lsass.exe
Security accounts manager initialization failed because of the following error: a device attached to the system is not functioning. Error State 0xc0000001.
When I hit OK, the machine restarts.
Any ideas on this?
Thank you
Woerts
"Security Accounts Manager Initialization Failed" Error Message When You Start Windows XP
http://support.microsoft.com/default.aspx?scid=kb;en-us;316751
http://support.microsoft.com/default.aspx?scid=kb;en-us;316751
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
"Security Accounts Manager Initialization Failed" Error Message When You Start Windows XP
http://support.microsoft.com/default.aspx?scid=kb;en-us;316751
http://support.microsoft.com/default.aspx?scid=kb;en-us;316751
I had a similar stop error recently. It was the RAM. I first tried it with some known good RAM and it booted immediately. I then put it's own DDR in another slot and it's worked without a problem ever since. Have you tried CrazyOne's suggestion yet?
If you can swap out the RAM with known good modules for testing first if you can't do that then test the machine with one RAM module at a time until you tested every module. Other wise run the the following RAM testers.
--------------------------
NOTE IF THIS DOESN'T FIND ANYTHING WRONG WITH THE RAM THIS DOESN'T MEAN THE RAM IS GOOD you would need to swap out the RAM with known good modules for testing. However if it does find something wrong then chances are the RAM is bad.
DocMemory PC RAM
Diagnostic Software
http://www.simmtester.com/PAGE/products/doc/docinfo.asp
or
http://www.memtest86.com/
or
GoldMemory
http://www.goldmemory.cz/