Fatal System Error (can anything be done?)?

Question

My computer, which uses Windows XP 32 bit operating system, repeatedly recycles the following message during boot-up:

Stop: c0000021a {FATAL SYSTEM ERROR} 
The Session Manager Initiation System process terminated unexpectedly with a status of 
0xc000026c (0x00000000  0x00000000). The System Has Shut Down.

As soon as the above message is displayed the computer restarts again, and repeats the cycle as long as it is on. Can anyone tell me what is going on and if there is anything I can do to alleviate this problem?

Tamim · Accepted Answer

So far, attempting to boot to Safe Mode or any other option on the F8 boot menu has no effect. The initialization error occurs before even safe mode is reached, so it becomes an endless loop of splash screen, reboot, splash screen, reboot, rinse and repeat.

The only solution that has yet worked for me is reloading the operating system from the install CD. Fortunately I have built all my systems from scratch with genuine M$ install CDs, not the big OEM house restore disks. Thus, I can use the repair option in the first screen of the retail install and not lose have the routine reset the partition to the original factory load. 
When the OS is reloaded from the original CD (a 40 minute process that looks exactly like a virgin install, but actually just overwrites the Windows system files without blowing off the registry or any programs or data) TURN OFF Automatic Updates!!!! You may go to the Windoze Updates site manually and let it search for updates, but use the "Custom Install" not the "Express Install." This will allow you select the specific patches to be installed. When I started working on this issue earlier tonight and determined what was happening, I began installing the updates one at a time to find the one that caused the failure. I got halfway through the list of 16 and then got lazy. I did 4 at once and everything was fine. Then I did the last 4 on the list and bang, I'm dead again.

DO NOT INSTALL UPDATE NUMBERS 890859, 891781, 893066, or 893086. It is one of these that killed me. I do not yet know which one.

REVIEWS:

Hotfix number 890859 is the culprit. Another tech in Microsoft's own newsgroup has documented it as well. But I can't find any evidence that Microsoft itself has acknowledged it. The easier solution than my method of reinstalling is outlined here.

http://windowsxp.mvps.org/spuninst.htm

So put out the word - turn off Automatic Updates, install updates manually and do not install # 890859. You may need to check the "hide this update" box so it doesn't get included again in future update cycles.

Anonymous · Answer

obtain Malwarebytes from yet yet another laptop and placed it on a flash stress. Boot your device in guard mode, deploy Malwarebytes from the flash stress, and run a try with it.

Trending News

Fatal System Error (can anything be done?)?

2 Answers