Stop: c000021a Fatal system error?
I am writing this for my sister. She is having problems with her Gateway laptop. Her computer is giver her a error message. She does not have the infomation or the disks that came with the computer. What can she do? She does not want to lose any of the data on her computer?
Comments
Since you didn't mention what operating system is on the Gateway, use extreme caution with any of the above suggestions. The Microsoft KB article referenced by Unknown Friend applies to the following systems:
Microsoft Windows NT Workstation 4.0 Developer Edition
Microsoft Windows NT Workstation 4.0
Microsoft Windows NT Server 4.0 Standard Edition
Microsoft Windows NT 4.0 Service Packs 1 - 6a
If the Gateway isn't running Windows NT any of the "fixes" could cause major problems.
Likewise with the suggestion by John O to run the "Repair" Console. I believe he's referring to something called a Recovery Console. This is quite different from a Repair Install or the Repair function. The Recovery Console is best used when a repair technician is talking you through the steps.
If you can get a friend's copy of your operating system's install CD, I'd recommend you try running a System File Check. Click start > run > type in "sfc /scannow" > OK (no quotes and notice the space between sfc and /scannow.) If any damaged or missing system files are located, you'll be prompted to insert the install disk. Files will then be repaired or replaced as needed. The scan could take over an hour depending on what it finds.
If the SFC doesn't fix it, you can try a Repair Install. In addition to the install CD you'll also need Microsoft's 25 digit alpha numeric Product Key assigned to the Gateway. You won't lose any personal settings or programs except for Windows Updates that came out after your install disk was manufactured (including SP2 if it's not on the install disk.) This link will give you instructions and screen shots of what you'll actually see:
http://www.windowsxpprofessional.windowsreinstall....
I selected XP Pro but the steps are identical for XP Home. If you have a different Windows OS this same web site will guide you through those:
http://www.windowsreinstall.com/
wwbgd
Try last known good configuration first . At boot before operating system loads you press f8 and select last known good configuration (it may work and its the least trouble) If it didnt work Go to microsoft data base and look up articles156669 & 315241 to see what your dealing with. Get your hands on a friends disk Prefferable of the same value ex> xp home,sp1 ,sp2 , xp pro, sp1, sp2, and load repair console The directions from there are quite simple and they work with out losing programs other than ones which caused the problem. It takes a little effort but it usually solves the problem with out an in place reinstall of the os where all data could be lost The two methods I've listed both work on certain conditions and the user does not have to be more than just a home user Simpler and less time consuming. Unknown Friend has given you a method that should work if you follow all her directions and those of the articles she listed. They can be intimidating but just calm down and follow through. It just takes more time and concentration
Error Message: Stop c000021a {Fatal System Error} The Session Manager Initialization System Process...
View products that this article applies to.
Article ID : 317189
Last Review : November 1, 2006
Revision : 2.1
This article was previously published under Q317189
IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 (http://support.microsoft.com/kb/256986/EN-US/) Description of the Microsoft Windows Registry
SYMPTOMS
When you start your Windows NT 4.0-based computer, you may receive the following error message:
Stop c000021a {Fatal System Error}
The session manager initialization system process terminated unexpectedly with a status of 0xc0000017 (0x00000000, 0x0000000) The system has been shut down.
After you receive this error message, your computer may restart so quickly that you are unable to obtain the details of the memory address. This symptom may prevent Windows NT from being able to write a valid Memory.dmp file. You may be unable to resolve this issue by disabling all third-party services, or by repairing your Windows NT installation by using an ERD.
Back to the top
CAUSE
The error message that is listed in the "Symptoms" section of this article is often caused by pending file-rename operations that are scheduled in the Windows NT registry, but that cannot be completed.
Programs or Setup programs may schedule a file to be renamed on the next restart of Windows NT if the program is prevented from renaming a file because the file is in memory.
Windows NT checks a registry key for file-rename operations to be completed early in the boot process. If the file-rename operation cannot be completed because the file or folder does not exist, the error message that is listed in the "Symptoms" section of this article is generated.
Back to the top
RESOLUTION
WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
To resolve this issue: 1. Create a parallel installation of Windows NT.For additional information how to do so, click the article number below to view the article in the Microsoft Knowledge Base:
259003 (http://support.microsoft.com/kb/259003/EN-US/) How and Why to Perform a Parallel Installation of Windows NT 4.0
2. Start your computer to the parallel installation of Windows NT, and then start Registry Editor.
3. On the Window menu, click HKEY_LOCAL_MACHINE on Local Machine.
4. On the Registry menu, click Load Hive.
5. Type the path to the System hive of the prior installation, typically %systemroot%\system32\config\system, and then click Open.
6. When you are prompted for the name of the key, type TEST, and then view the following registry entry:
HKEY_LOCAL_MACHINE\TEST\Select
7. Note the setting for the Current DWord value in the preceding registry key. This is typically 0x1, and is represented as CURRENT:Reg_Dword:0x1. This value indicates that the "CurrentControlSet" for your original Windows NT installation corresponds to ControlSet001 in this window. A value of 2 would indicate that the "CurrentControlSet" for your original Windows NT installation would correspond to ControlSet002, and so on.
8. Locate the following registry key
HKEY_LOCAL_MACHINE\TEST\ControlSetXXX\Control\Session Manager
where XXX is the CurrentControlSet that you identified in the preceding step.
9. Under the Session Manager key, note and then delete any PendingFileRenameOperations entries.
10. Click the TEST hive, and then click Unload Hive on the Registry menu.
11. On the Registry menu, click Load Hive.
12. Type the path to the Software hive of the prior installation, typically %systemroot%\system32\config\Software, and then click Open.
13. When you are prompted for the name of the key, type TEST2.
14. Remove any PendingFileRenameOperations entries in the following registry keys:
HKEY_LOCAL_MACHINE\TEST2\Microsoft\Windows\CurrentVersion\RunOnce
HKEY_LOCAL_MACHINE\TEST2\Microsoft\Windows\CurrentVersion\RunOnceEx
15. Click the TEST2 hive, and then click Unload Hive on the Registry menu.
16. Quit Registry Editor, and then restart your original installation.