XP won't boot; no Windows CD

Greetings,

My sweetie completely cut the power to her desktop before it was completely shut down. Now we are stuck in an endless loop with an error message or two and no Windows CD to boot from.

She's running XP Pro (with the most recent SP).

We get the Windows splash screen, then it zips past a "Please select the OS to start" screen (we solved some kind of problem ages ago and now have two "Miscrosft Windows XP Professional" to choose from; this has been working fine for years even though there are two choices).

After zipping past that screen (which I got it to stop on by tapping the up arrow button, otherwise I can't read that fast), it goes to the "...did not start successfully" screen with Safe Mode, Safe + Networking, and Safe w/cmd prompt options...along with Start Normally....ALL of these cycle back to this same screen.

On the "please select OS" screen, selecting MS Win Recovery Console gives us this error message: "Windows could not start because the following file is missing or corrupt: <Windows root>\system32\hal.dll Please re-install a copy of the above file"

Elsewhere (I forget how we got it), there was a BsD with the following Stop message: STOP 0x00000024 (0x00190203, 0x86BC9DE8, 0xC0000102, 0x00000000)

I tried following the instructions mentioned elsewhere on this site which took me to a German site: http://www.chip.de/downloads/c1_downloads_hs_getfile_v1_35181966.html?t=1330298964&v=3600&

The "install" of this 30 day trial (boot disc) onto my good machine failed because I'm running Win7 64, and failed on a laptop because it's running Vista - both non x86 OSs.

While I scour the internet for an answer, I thought I'd beg for help here.

I am thinking that if I can get it to at least boot, then somehow I might be able to find that .dll file and stick a copy into the system32 folder (once I figure out how to do that)...that's my hunch.

Of course, I invite (beg for) your expert guidance.

Best,

drcarl

 

UPDATE: meanwhile, I'm downloading and burning Ubuntu to one disc (did not open on first try) and another CD with The Ultimate Boot CD and a folder containing something I found called "HAL FIXER"

 

I'd try running a chkdsk /r on the Windows partition. That would rule out file system corruption. If after running chkdsk you still get a missing hal.dll message you can consider other options but hal.dll is rarely actually missing.

The UBCD you are downloading should have that option available.

Or you can download a recovery console ISO which will get you to command prompt to try the chkdsk command.

 

more UPDATE...

Neither boot discs worked on her machine.
(Boot order did try to read the CD before reading the HD)
It went to that same place it always goes now. Same loop. Same loop.

Wondering if I made the boot discs properly, I tried booting my machine from them.
UBCD failed on my machine as well as hers. UBCDWinV360.exe is in the CD's root, and I have the "halfixer" program (dffsetup_hal.exe) in a folder, not the root of the CD so I am thinking only UBCD is seen at first to boot from.

The Ubuntu booted on my machine just fine. Took a while, yet operates correctly.

On her machine, it's hung at this screen:

http://drcarl.smugmug.com/photos/i-wFHvJTq/0/XL/i-wFHvJTq-XL.jpg

 

First, I believe you are burning the ISO file (Ubuntu) correctly as an image file since it boots on your machine. You are using something like imgburn and the "Write Image File to Disc" option--correct? Ubuntu can be a tricky flavor of Linux and doesn't run well on many machines. You can try a different version of Linux to see if you have better luck booting to the CD. What were you going to use Linux to do?

The UBCD has to be created as far as I know. You would run the UBCDwinv360.exe on a working computer but you need an XP CD to copy files. Maybe someone else who has used that program recently can jump in?

Try the recovery console iso file and burn it to a blank CD as an image file to make a bootable CD. Then try running chkdsk C: /r on the PC.

 

thanks sach2 - will try, yet probably tomorrow because I gave up for the night and have learned that a couple of cocktails and troubleshooting computers is not a good combination - lol?

Also, what to do with the rc.iso once I download it? How do I run it?

TIA

drcarl

 

It is there in my post #3. Download the file and use Imgburn's "Write Image File to Disc" option to burn it to a blank CD. Guide: http://forum.imgburn.com/index.php?showtopic=61

Then boot from the CD. It is a stripped down XP disc that only allows you to get to recovery console so when you get installation options you choose "R" for repair. Then sign into your XP installation. And you get a command prompt where you will type chkdsk c: /r and hit <enter> to try to fix any errors in the file system. If it is file system corruption that is causing the hal.dll problem then if it is fixed you may then be able to boot into XP without the CD. If you get Safe Mode options again after trying to boot without the CD then try Last Known Good Configuration. See if it goes any further than before.

 

sach2 - thank you for the clear instructions. sorry to have jumped the gun re-asking something you already answered - lol? - you know how it is.

I am running chkdsk C: /r now and will report back.

Thank you again

drxcarl

 

no love. succeeded with chkdsk c: /r, restarted without Recovery CD and am still stuck in the same loop. Selecting Recovery console from the machine (without the CD) still says to install hal.dll

 

The recovery console on HD is no different than the one you downloaded so that is not a problem that it won't run from HD. Since the first Windows option gets to the boot loop, you're hal.dll must be there or it wouldn't get that far. It also tells you that your boot.ini file is good.

The boot loop is the problem. I don't have an answer for how to fix that. I hope someone can jump in with a suggestion.

 

sach - recovery console on the HD does not do anything but return to the boot loop. The recovery console on the CD got me to a command prompt. I tried entering "C:\windows\system32\restore\rstrui.exe" but nothing happened (well, I got a 'doesn't recognize the command" kind of thing).

My DOS days are pretty far behind me, yet I started to wonder if I was entering that restore line correctly. "D:" got me to the D:\ but from C:\ it seemed that C:\windows (the <windows> directory) was not available, nor much of anything else when I took a look at "DIR" which used to return gobs of files. I'm guessing the Recovery Console has something to do with the limitations? Feels like a pretend 'cmd' prompt.

From that prompt, I also tried to run "bootcfg /rebuild" and was greeted with the following:

Failed to successfully scan for Windows installations. This may be caused by a corrupt file system which would prevent Bootcfg from suiccessfully scanning. Use chkdsk to detect errors​

We already did chkdsk with a /r switch

standing-by....and you better answer fast or I'll demand my money back! (lol?)

~drcarl


PS - note to any new geeks...although my 'signature', below, might suggest otherwise, the machine that's in trouble is older and running XP Pro....

 

Seeing that fixboot is one of the supported commands of the Recovery Console, I typed that at the C:\ (they system drive) and got this message:

"Target of Partition is D:. Are you sure you want to write a new bootsector to the partition of D?"​

I'm not sure of anything and don't want to risk losing that data on "D:" (data drive/partition) so I chickened-out and said n <enter>, er "no."

I'm sitting on my hands now so I don't destroy anything ... and because they are cold.

TIA

~drcarl

 

I don't think you are having trouble with the MBR or the boot sector because windows is getting to the safe mode options. If the MBR or boot sector was messed up you would just get an underscore blinking cursor at the top left corner of the screen.

Now that you mention it, I do remember that recovery console only allows you into certain folders/directories. The command cd is for change directory so from C:\> cd windows would get you into Windows folder (if allowed).

The screen with the two choices of operating systems is from your boot.ini so that is what bootcfg would try to rebuild. As far as I can tell it is written correctly already. Try bootcfg /scan just to verify that it can find the XP you are signed into C:\Windows

It is the boot loop, where no matter which safe mode option you select, it goes back to that list that is the troublesome error. I've never seen a fix that someone actually posts back that it worked.

 

thanks --will check this in a bit (phone call now) - and look forward to more, hopefully...

TIA

~drcarl

 

From booting with the Recovery Console CD...

Tried cd windows - no can do

Tried bootcfg /scan - and got "Failed to successfully scan discs for Windows...." and something about that has to be a success before it's able to /add or /rebuild...as well as (like before) "This may be caused by a corrupt file system"

 

Do a chkdsk C: /f and note if it fnds errors or fixes anything in the results.

 

From booting with the Recovery Console CD...

Tried chkdsk C: /f and got "The parameter is not valid..."

thanks for the idea...

 

I'm not sure it will do anything with the original error but I am wondering why it can't scan for OS's. It must see your Windows installation as you are signed into it?

Go ahead and do another chkdsk c: /r
I don't think you have any problem with the HD since this started with a hard shutdown but I'd just like to completely rule it out. The /f parameter was just to skip the HD scan part of chkdsk but since that won't run that way I'd go ahead and do another /r.

 

...funny....I just started another chkdsk /r then read this...I failed to type "exit" aftr thje last chkdsk ran and am not sure if that's important

 

Exit is used to close the command prompt in Windows. It has no effect in Recovery console.

 

typed "exit" this time...and...well....a picture is worth 20 or 30 words?

(follow link below for image of the screen)

boo hoo

http://drcarl.smugmug.com/photos/i-8nJBpjt/0/X2/i-8nJBpjt-X2.jpg

 

Where did everything go?

I know you are probably done for today but do a quick dir at the C:\> prompt and let me know what files/folders are listed. Are there just a few--just type a basic list of anything relevant? No Windows folder and no Documents and Settings folder(dir)?

I can't see how a hard shutdown could so severely damage the file system that those folders are missing. I'll think about any options left and post something tomorrow.

 

I'll go grab a screen shot (photo) of dir at C:>

 

Recovery CD > cmd > dir

click this http://drcarl.smugmug.com/photos/i-83mbHS5/0/X3/i-83mbHS5-X3.jpg

and thanks

 

Wow, that is a very strange list.

Some basic files like boot.ini are still there from 2007 and yet no Windows, no Documents and Settings and Program files is empty.

System Volume Information which is an index to your files is also empty (actually this may be a false size since it is a super-hidden folder). Chkdsk should have been able to fix that in most instances.

I'm really not sure where to go from here. A partition program like Partition Wizard could search for lost partitions but your partition seems to be there with some files available but no Windows files. I don't think it is a partition problem but an index problem. Chkdsk would have been my only thought on fixing an index.

I'll take a look around to see if I can find anything similar. Just never see this.

 

see post #12 - would I risk anything by proceeding with a "yes" instead of a "no"? I don't want to risk her data in case it's new system time...

 

I don't think writing a new bootsector is necessary but it shouldn't do any harm to any data files. Go ahead if you like.

I've been thinking about this and realize I made a few assumptions. Particularly that Windows was on C: drive. You didn't actually get a prompt asking you to sign into Windows like in my post #3 but were just presented with a C:\> prompt rather than signing in and getting a C:\Windows> prompt. It is possible that you have your Windows folder on a different partition since you had "some trouble years ago".

At your C:\> prompt try type boot.ini and let me know what number it has for partition in your XP Professional entry. If it isn't 1 then your XP files may still be there on D: or another letter.

 

Greetings,

>HERE< --is the thread on the "some trouble years ago." I have not re-read it slowly ... perhaps post #30, 31, 32 and the images might offer a clue? I'm glad I took photos ... "...1000 words..." and all that.

I ran type boot.ini and it looks like partition(1) to me >HERE< is the screenshot.

Please note that there is a choice of TWO entries for Windows XP Pro as seen >HERE< (maybe we need a third? lol?) ... this screen is usually only up for a fraction of a second before proceeding now to the Safe Mode options, and usually proceeding to a good Windows start up. That there are two is the result of our efforts "some time ago" and --we could live with that because at least Windows started!

As you know, >THIS< is the screen we are seeing for too much of...

And, >THIS< is what we see fly by when selecting Safe Mode, and, however irrelevant, >HERE< is where the loop ends and cycles back through everything again.

What next?


:confused

 

So you have two HD in the computer?

Let's try to find the drive letter for Windows folder (It is there somewhere)
D: <enter>
dir <enter>
If not there then
E:
dir
F:
dir
G:
dir

One of those letters should have a Windows directory/folder. When you find the letter go back to C: and use the chkdsk D: /r command to check the proper drive for errors. You'll substiture the proper letter in the chkdsk command below:
C: (to get back to C: prompt)
chkdsk X: /r (sub correct drive letter probably D: )

 

No Windows folder/directory.

Probably irrelevant, though I do see Windows at least mentioned halfway down >this screen< (shot earlier)

I checked the alphabet for directories. Besides the floppy (remember those?) and other peripherals, the only HD DIRs were C:> and D:>

D:>\dir yielded "An error occurred during directory enumeration"

I am running a chkdsk /r on D:>

(thanks again for brainstorming this)

 

I think D: is your Windows drive and it is corrupted.

Your safe mode screen with the list of files says that the Windows\System32 folder exists and all those files were loaded. Then it stops at mup.sys which again is one of those errors that has no true fixes other than reloading the OS.

We'll see what chkdsk can do.

If you get to a Safe Mode screen when rebooting please try Last Know Good Configuration before any other choice. (You really only get one chance at that.)

 

60% complete - you know it takes a while...wait...that was stage 2 I think...now 53% on the third stage...

Can the OS be reloaded without losing the data?

She might have her company buy a new machine (this one is quite old) as well as one of those external HD (what's it called) docks? (The box that will accept a HD and allow access, perhaps USB? so she can move her data)

 

I'm unsure on rebuilding without losing data. It is technically possible http://www.informationweek.com/news/windows/operatingsystems/189400897 with a Windows CD matching your Service pack (SP) but I have never actually tried it.

I'm reading your old thread now. I don't know anything about RAID settings, so I'm not sure how it will go. I haven't finished the thread yet.

From what I see from your recent pics the only thing on C: are a couple of boot files ntldr, ntdetect and boot.ini. They point over to the D: drive to load up the rest of Windows. An unusual setup for such a large partition but not a problem in itself.

Once chkdsk gets finished then the files should be accessible even if XP won't boot. A linux CD could be used to copy data files to another HD or to a flash drive and then over to another HD for safe keeping. If XP had to be reinstalled then of course programs would have to be freshly installed as well. Only data files can be saved. ie. If she runs Turbotax, she could save the data files of previous years returns to later access on a new install. But Turbotax itself would have to reinstalled and then she would copy the previous years data to the appropriate folder so Turbotax could access it.

I'll finish your old thread but I may not get back here for a couple of hours.

 

:cool thanks sach, um, we got a >BINGO!< <-- go ahead, try your luck...click on the Bingo link!

Looks like chkdsk /r on D:\> was just what the doctor ordered!

Thank you so much for your energy and efforts and for helping me think through this!!!

:major MajorGeeks pulls through again! :major

~drcarl

:wave

 

I beg of you to forgive me for resurrecting this thread, but I have this EXACT SAME PROBLEM. With the same stop code. and the same everything.

the computer is recognizing my second hard drive (the one without windows) as the C drive. going down the list of drives doesn't find it.

it appears that my computer is not detecting the windows drive at all; chkdsk /r on c: did nothing of importance.

BIOS still recognizes both hard drives are there, so it's not a connection issue.

Please help!

 

In future I suggest you start a new thread and link to any previous one, but let's solve your problem here for now.

I assume that you have two hard drives in your computer? If so it is possible the main drive has failed whilst still "talking" to the BIOS.

A good place to start would be to download http://www.ultimatebootcd.com/ and burn it to a CD. Then boot from it and run the disk check that is most appropriate for your hard drive. If you need help running this let us know.