How to fix NTLDR is missing error

Bman123

Supreme [H]ardness
Joined
Dec 19, 2007
Messages
5,086
The neighbors have a store bought hp pc that is a little old. It has windows xp on it, the power went out during a storm while they were using the pc. Now when you turn the pc on you get a NTLDR is missing error and it wont boot into windows.

From what I've seen and heard I need a windows xp disc to fix this and we dont have one. I'd appreciate any help guys Thanx
 
First thing. Hook the drive up to another system or use a linux live disc and save all important data to a USB drive.

We'll do the simple stuff first.

Start by making sure the hard drive/optical drive are seen in the system bios and that the boot order is configured properly.

You likely need an XP OEM (either Home or Pro) disc to work on this computer after this point.

Boot to an XP CD and press R to go into the recovery console and and run

chkdsk c: /p /r

Try loading into the OS.

If it still doesn't work, replace the ntldr and ntdetect files from the recovery console (d: is optical drive)

Launch back into the recovery console and type in

copy d:\i386\ntldr c:\

then

copy d:\i386\ntdetect.com c:\

If this doesn't work, you may need to try to do a Windows XP repair. You do this like you are installing XP, when you get to the choice to press 'R', don't do that, rather select to install XP, choose the partition and you should see an option to attempt to repair existing installation. If you don't see it, the repair is not possible. If it is possible and you try it, you may end up with two XP installation options. If this is the case we can walk you through deleting one of them.

If it still is not working right at this point I would just reinstall the OS. If it was my computer I would reinstall the OS before any of these steps but it's not always that easy with someone else's computer due to disc/software etc. Since it's a oem computer, you'll need an OEM disc (like I pointed out earlier). With XP, the key on the sticker may or may not work to reinstall. In my experience with XP, the key has always worked but other people have not been so lucky. Your other option may be to build an XP oem activated install CD, using the oem files on the existing install. You'll just have to pull them off the drive.

If you reach the point that you feel you may have to do that, just reply that you want to try that and I'm sure the person here who explains that best will let you know how to do it.
 
Last edited:
It sounds like a dying hard drive. As bigdogchris said, first step is to get all important data off the drive.
 
If the hard drive was toast, he wouldn't get the NTLDR error; the boot loader is providing that info, not the BIOS, so the hard drive is functional at least to the point of getting up to speed, etc.

The simplest solution to this is find an XP CD of some kind, any kind be it Home or Pro, Retail or OEM, it doesn't matter. Boot off it, choose the Recovery Console option (not Repair) and then - if things are working, of course - you'll get to a Command Prompt where fixing this issue requires two commands in this sequence:

fixmbr (and then press Enter)

It'll ask to confirm so press Y and then Enter and when it says the command completed successfully, do the next command:

fixboot (and then press Enter)

and again confirm with Y and Enter and then eject the CD, reboot the PC by typing:

exit (and then press Enter)

Don't just hit the power switch after you eject the CD, that tends to cause things to stay broken, experience has taught me. While there potentially are ways to fix this issue with NTLDR without an XP CD handy, it'll be a far more complicated process.

Hope this helps.
 
If the hard drive was toast, he wouldn't get the NTLDR error; the boot loader is providing that info, not the BIOS, so the hard drive is functional at least to the point of getting up to speed, etc.
We said dying, not dead. Dying hard drives start losing/being unable to access random files. Random bluescreens in files that shouldn't crash and bootloader errors are a good indication of this.
 
Bad RAM would cause the problem(s) mentioned, and far more often BSODs/etc are caused by bad RAM. Did the OP mention BSODs or did I miss something?

Regardless, the recommended course of action would be:

- run memtest86+ for at least 3 complete cycles on the RAM to check that first
- run the manufacturer's diagnostic on the hard drive second to make sure it's at least functional
- find an XP CD and get that thing operational again even if a full complete reinstall is required third

If it's an older HP as noted, it's probably still got the factory restore installation on there someplace in a hidden partition. Just getting it to get past the NTLDR point could provide access to that functionality as well (pressing F11 or F12 usually turns over the boot process to the secondary hidden partition and runs the recovery app).
 
I had this multiple times.
-Set harddrive priority in bios to correct setting or move it around.
-remove ram and replace or if you have 2 sticks switch them.

Switching ram sticks allways works for me.
 
Save the files like above, then run a drive diag before going into all that other stuff. This is a bad drive issue. Not RAM
9.5 out of 10 drives ive had show this error are bad.
 
fixmbr (and then press Enter)

It'll ask to confirm so press Y and then Enter and when it says the command completed successfully, do the next command:

fixboot (and then press Enter)

and again confirm with Y and Enter and then eject the CD, reboot the PC by typing:

exit (and then press Enter)
I would definitely recommend doing this before trying a repair install (last option if you can't reinstall).
 
Back
Top