Help! Do not want to re-install

March 22, 2009 at 08:17:17
Specs: WIN2K Server SP4
Thanks in advance for responses.

I am getting the following BSOD caused by a power failure:
Stop: c0000218 {Registry File Failure}

I have followed all the solutions here (and more) to no avail:

The "Harder Method" in the link above failed completely due to "ACCESS DENIED" error when using the COPY cmd prompt from the RECOVERY CONSOLE. I have been unable to change the privileges from the recovery console (although obviously I logged on as an ADMIN ).

The next solution appeared to be a repair installation using BOOT disks. This also failed despite setting the boot sequence to floppy disk in the BIOS (the boot sequence does not recognize the floppy and jumps straight to HDD 0).

The remaining option appears to be wiping the disk and doing a clean install (data files are keep on a separate drive than the OS drive, so although I can recover data easily, time required to re-install is a problem).

...Unless I can get some pointers here. Thank you.

See More: Help! Do not want to re-install

Report •

March 22, 2009 at 09:10:10
Is the floppy drive an internal drive? Is it configured correctly? I suggest you try to determine what is going on with the floppy drive. Try the disk in a different computer to verify it works.

Report •

March 22, 2009 at 14:44:30
Any problem with the floppy drive would have been identified during regular maintenance-I do not believe that the problem is here.

Report •

March 22, 2009 at 15:28:55
So you aren't going to answer the questions then? The point is that if you have restore floppies they may be your best solution.

Report •

Related Solutions

March 22, 2009 at 17:01:51
The answers to your questions are implicit in my response. (Why would I not answer a question that may be beneficial to solving my problem...? Why would you even suggest that?)

Explicitly, this is an internal drive, configured with manufacturer default settings, regular maintenance did not turn up any issue with this drive, and there has never been any problem with this piece of hardware, or any other hardware on this box.

Report •

March 22, 2009 at 17:10:57
I take it your Win2K disc isn't bootable? I assume you have all 4 boot floppies...are you sure they're good? Do you have any other bootable floppy available (Win98, memtest86) that you can use to test your floppy drive?

Report •

March 22, 2009 at 17:50:14
WIN2K disk is not bootable hence the floppy disks. I have used these boot disks to install all the other servers in the company thus I do not see this to be the problem. Indeed, one of the solutions that I came across suggested creating XP boot disks (WinXP_EN_PRO_BF.EXE) to run the ChkReg.EXE for Windows 2000 (this solution assumes that no Recovery Console is installed). We do have the Recovery Consoles installed on all servers; I tried the solution anyway just in case. The floppy drive starts turning at start up with XP Boot Disk 1 (same as with WIN2K boot disks), but then hangs with an on screen message "Boot from CD: " even though boot sequence is set to floppy drive (the BIOS has 4 boot sequence options, and setting all of them to floppy drive has no impact.)

Report •

March 22, 2009 at 18:59:19
I did suggest you try the DISK in a different computer.

Report •

March 23, 2009 at 05:13:02
A"very" l..o..n..g shot - and no real logic without I spend a little more tyme on your posts various...; and info therein But possibly RAM is an issue?

Can you experiment with RAM; reduce to a single stick (min 128Meg) and try each in turn (if more than one currently installed); likewise try a known to be good set/stick?

As I say it's pure long shot; as in the past RAM has (and doubtless will continue to) produced moore than a few irritating errors such as you appear to have..

Report •

March 23, 2009 at 08:45:48
Thanks for all the helpful suggestions. This is one of those rare events that stumps even the experts, which I am certainly not!

Having followed all the leads provided, we decided to bit the bullet: that is, wipe the disk and do a clean install to save effort and time. As explained in earlier posts, there was no problem with any of the hardware. We are back up and running now.

Sorry that I could not provide any pearls of wisdom as to the actual cause or come up with a unique solution to enhance everyone's knowledge. At the end of the day, it was just a simple re-install (which may have been overdue since the box had been running 6 years plus without any down time)!

Report •

March 23, 2009 at 16:03:22
thanks for the feed back; it might have been nice (from an academic angle) to discover the cause etc...; but then again..

Report •

Ask Question