[pnut311]

A couple nights ago we lost power and everything in my office restarted. I had it all on battery backup, so I guess we lost power for quite some time. When I got here the next morning, everything was off. I had one machine running XP. When I tried to turn on the XP machine, I was getting a bad image checksum error for ole32.dll. First I ran a memtest-86 and found no errors. After some searching, I found this post on these forums: Stop error The problem is similar, just with a different file. I followed the steps given by rshaffer61 to replace ole32.dll through the recovery console using the dll from the Servicepackfiles folder. After rebooting, I got the same checksum message but now with Wintrust.dll. I went back and did followed the same steps for replacing wintrust.dll. Now after restarting I no longer get a checksum error, but instead I get a Fatal System Error message. Exact error message:

STOP: c000021a {fatal system error}
The session manager initialization system process terminated unexpectedly with a status of 0xc00026c (0x00000000 0x00000000).
The system has been shut down.

Does anyone have any idea how I can fix this? Normally I would just reinstall Windows and start from scratch, but this computer is for my business and has Point of Sale software on it. All my data is safe on a backup HD, but they want to charge me $300 to reinstall their Point of Sale software on a clean install of Windows So again, any help is greatly appreciated. Thanks!

Steve

[Advertisements]

Please try the following:

1: Start in safe mode and see if the computer is working in this mode.

2: Run Last Known Configuration from the same screen that you run Safe Mode.

3: Run checkdisk /r from recovery console.

3: Run hard disk diagnosis using the tool of the disk manufacturer.

[The Skeptic]

Please try the following:

1: Start in safe mode and see if the computer is working in this mode.

2: Run Last Known Configuration from the same screen that you run Safe Mode.

3: Run checkdisk /r from recovery console.

3: Run hard disk diagnosis using the tool of the disk manufacturer.

[pnut311]

I probably should have mentioned that too. I tried starting up Windows in Safe Mode and it stops half way through loading files. Last Known Good Configuration doesn't help either. I ran a checkdisk from the recovery console and it came back fine. I think I'm just gonna reinstall windows and hope for the best. Hopefully I'll only lose some drivers and not the actual data that i need.

[Broni]

If you have Windows CD...(if you don't have Windows CD, scroll down)

1. Insert your Windows XP CD into your CD and assure that your CD-ROM drive is capable of booting the CD.
2. Once you have booted from CD, do NOT select the option that states: Press F2 to initiate the Automated System Recovery (ASR) tool.
You’re going to proceed until you see the following screen, at which point you will press the “R” key to enter the recovery console:



3. After you have selected the appropriate option from step two, you will be prompted to select a valid Windows installation (typically number “1″).
Select the installation number, and hit Enter.
If there is an administrator password for the administrator account, enter it and hit Enter (if asked for the password, and you don't know it, you're out of luck).
You will be greeted with this screen, which indicates a recovery console at the ready:



4. There are eight commands you must enter in sequence to repair your problem..
NOTE. Make sure, you press Enter after each command. Make sure, all commands are exact, including "spaces".
These commands are as follows:

CD..
ATTRIB -H C:\boot.ini
ATTRIB -S C:\boot.ini
ATTRIB -R C:\boot.ini
del boot.ini
BOOTCFG /Rebuild

Note about the above command.
BOOTCFG /REBUILD command which searches for pre-existing installations of Windows XP and rebuilds sundry essential components of the Windows operating system, recompiles the BOOT.INI file and corrects a litany of common Windows errors.
It is very important that you do one or both of the following two things:
A.) Every Windows XP owner must use /FASTDETECT as OS Load Option when the rebuild process is finalizing.
B.) If you are the owner of a CPU featuring Intel’s XD or AMD’s NX buffer overflow protection, you must also use /NOEXECUTE=OPTIN as an OS Load Option.
For the Enter Load Identifier portion of this command, you should enter the name of the operating system you have installed.
If, for example, you are using Windows XP Home, you could type Microsoft Windows XP Home Edition for the identifier (it's not crucial, however what the name is, as long, as it's meaningful).
Here is your computer screen:



5. Following command verifies the integrity of the hard drive containing the Windows XP installation. While this step is not an essential function in our process, it’s still good to be sure that the drive is physically capable of running windows, in that it contains no bad sectors or other corruptions that might be the culprit:

CHKDSK /R

6. This last command writes a new boot sector to the hard drive and cleans up all the loose ends we created by rebuilding the BOOT.INI file and the system files. When the Windows Recovery Console asks you if you are Sure you want to write a new bootsector to the partition C: ? just hit “Y”, then Enter to confirm your decision:

FIXBOOT

7. It’s time to reboot your PC by typing
EXIT
and pressing Enter.

With any luck, your PC will boot successfully into Windows XP as if your various DLL, Hive, EXE and NTLDR errors never existed.



If you don't have Windows CD...
Download Windows Recovery Console: http://www.thecomput...om/files/rc.iso
Download, and install free Imgburn: http://www.imgburn.c...hp?act=download
Using Imgburn, burn rc.iso to a CD.
Boot to the CD...let it finish loading.
When the "Welcome to Setup" screen appears, press R to start the Recovery Console.
Then, follow instructions from Step #3 above.