XP startup hangs after BIOS update

  • Thread starter Thread starter Bill
  • Start date Start date
B

Bill

On another machine here at home, I installed
a BIOS update. The settings defaulted when
the update was complete and I got the famous
"NTLDR is missing" message when I tried to boot
up. I F2'd to the BIOS and changed the boot
priorities to select the correct disk but then
found that XP Home SP2 startup hangs after
several seconds of watching the progress bar.
Is there another Intel BIOS setting peculiar
to XP that needs to be set?

I Googled the problem, but couldn't find anything.

Thanks,
Bill
 
Bill said:
On another machine here at home, I installed
a BIOS update. The settings defaulted when
the update was complete and I got the famous
"NTLDR is missing" message when I tried to boot
up. I F2'd to the BIOS and changed the boot
priorities to select the correct disk but then
found that XP Home SP2 startup hangs after
several seconds of watching the progress bar.
Is there another Intel BIOS setting peculiar
to XP that needs to be set?

I Googled the problem, but couldn't find anything.

Thanks,
Bill

When you did the BIOS upgrade you more that likely did it from a floppy
disk. Did you remove the floppy disk from the drive?

Danny,
 
Danny Kile said:
When you did the BIOS upgrade you more that likely did it from a floppy
disk. Did you remove the floppy disk from the drive?

Danny,

Yes, the boot proceeds to the point where
one sees the "Windows XP Home" screen and
the progress bar scrolling from left to right.
The progress bar cycles several times before
it stops and everything hangs at that point.
Bill
 
Bill said:
Yes, the boot proceeds to the point where
one sees the "Windows XP Home" screen and
the progress bar scrolling from left to right.
The progress bar cycles several times before
it stops and everything hangs at that point.
Bill

Try checking all BIOS settings, to make sure they haven't changed
since the update. Also, try starting in safe mode. If that works,
reinstall the motherboard drivers in safe mode.
 
Ian D said:
Try checking all BIOS settings, to make sure they haven't changed
since the update. Also, try starting in safe mode. If that works,
reinstall the motherboard drivers in safe mode.

Can't boot completely even in Safe Mode.

I'm at a loss to know if BIOS settings have changed
or not. Un-fortunately, I don't usually get involved
with BIOS issues, so I'm a bit out of my area when
it comes to some of the more criptic items in the BIOS.

Bill
 
Bill said:
On another machine here at home, I installed
a BIOS update. The settings defaulted when
the update was complete and I got the famous
"NTLDR is missing" message when I tried to boot
up. I F2'd to the BIOS and changed the boot
priorities to select the correct disk but then
found that XP Home SP2 startup hangs after
several seconds of watching the progress bar.
Is there another Intel BIOS setting peculiar
to XP that needs to be set?

I had a similar problem a few months back. What worked for me was to
clear the NVRAM (I was working on a Dell). This is the procedure I used:

http://en.community.dell.com:80/forums/t/18671704.aspx

What is the make and model of your PC?

Why did you update the BIOS? The rule of thumb is to leave it alone
unless there is a need to update it. Also, before you make any changes
at all to the BIOS, it is a good idea to note *all* the settings. For
instance, you may have a SATA hard drive and in order for it to be
recognized, the correct BIOS setting (e.g., standard IDE instead of
AHCI) needs to be selected.

Also, if there was a problem shutting down, you may need to perform a
manual System Restore:

http://support.microsoft.com/kb/307545

Do you have a Windows XP installation CD? (That would be helpful!)

But hopefully all you need to do is clear the NVRAM.
 
Bill said:
Can't boot completely even in Safe Mode.

I'm at a loss to know if BIOS settings have changed
or not. Un-fortunately, I don't usually get involved
with BIOS issues, so I'm a bit out of my area when
it comes to some of the more criptic items in the BIOS.

Uh, then why did you update the BIOS?

Just askin'.
 
On another machine here at home, I installed
a BIOS update.


Why?

It's too late now, but for the future, you should always avoid doing
this unless you need to. Certainly don't do it just because it's X
years old and there are upgrades available. Although a BIOS upgrade
normally goes well, it is not without danger. If something goes wrong
while the upgrade is an progress (for example, a lapse in power) you
can be left with no BIOS at all, and an unbootable computer.

Do a BIOS upgrade if you need to--because you are having a problem
that the new version is known to fix--not just because one is
available.
 
Yes, the boot proceeds to the point where
one sees the "Windows XP Home" screen and
the progress bar scrolling from left to right.
The progress bar cycles several times before
it stops and everything hangs at that point.
Can't boot completely even in Safe Mode.

I'm at a loss to know if BIOS settings have changed
or not. Un-fortunately, I don't usually get involved
with BIOS issues, so I'm a bit out of my area when
it comes to some of the more criptic items in the BIOS.

Bill


Bill:
It's entirely possible a relatively simple Repair install of the XP OS will
resolve your problem.

I'm assuming you have either a retail version of the XP OS installation CD
or a non-branded OEM version of such, i.e., you're not working with an OEM
machine (Dell, Gateway, etc.) and therefore either of those two types of OS
installation CDs are unavailable to you.

I further assume you're not particularly familiar with that process so here
are a few details...

Basically a Repair install of the OS is a relatively straightforward &
relatively simple process roughly akin to making a fresh install of the OS.
Hopefully a successful Repair install will return your system to a
bootable/functional state. And in nearly every case your existing programs &
user-created data would be retained. Notice I said "nearly". While it would
be a rather rare situation where data would be lost or corrupted as a result
of the Repair install, and as unlikely as it may be, it *could* happen.

So if there are any programs and/or other data on your present drive that
are absolutely crucial to you and you could not tolerate their loss, then I
would strongly suggest that before undertaking this Repair install operation
that you first either make a "clone" of your existing HDD (using a disk
imaging or disk-cloning program) or, if that's not practical and you can
install the HDD as a secondary HDD in some other machine, pull off whatever
data you want onto some removable media, e.g., flash drive, CD, etc. before
proceeding with the Repair install.

Again, it's a relatively rare event that a loss or corruption of data will
occur even when the Repair install is unsuccessful, but it *can* happen. So
I want you to be aware of this.

Here are the step-by-step instructions that can be found at Microsoft's site
at...
http://www.microsoft.com/windowsxp/using/setup/support/nostart.mspx#2

<quote>
Before performing a repair installation of Windows XP, you should have both
your Windows XP CD and your product key available.

To perform a repair installation of Windows XP...

1. Insert your Windows XP CD into your computer.

2. Restart your computer. If prompted, press a key to start from the CD-ROM.

3. When the Welcome to Setup page appears, press ENTER on your keyboard.

4. On the Windows XP Licensing Agreement page, read the licensing agreement.
Press the PAGE DOWN key to scroll to the bottom of the agreement. Then,
press F8.

5. When prompted, press R to have Windows XP attempt to repair Windows by
reinstalling important Windows components.

The repair and reinstallation process might take more than an hour.
Eventually, Setup prompts you to answer questions just as if you were
installing Windows XP for the first time. For detailed instructions, read
"Install Windows XP" at...
http://www.microsoft.com/windowsxp/using/setup/winxp/install.mspx"
</quote>

Also, here are a number of websites that contain detailed step-by-step
instructions for undertaking a Repair install. Let me assure you that it's
not a difficult process and not terribly time-consuming. As I've indicated,
it's roughly similar to making a fresh install of the XP OS. There's really
not too much to it.
http://www.michaelstevenstech.com/XPrepairinstall.htm#RI
http://www.webtree.ca/windowsxp/repair_xp.htm
http://www.geekstogo.com/forum/index.php?showtopic=138
http://www.windowsreinstall.com/winxppro/installxpcdrepair/indexfullpage.htm
http://support.microsoft.com/default.aspx?scid=kb;en-us;315341

Assuming the Repair install is successful, you should use your A-V program
to immediately check out your PC for any malware infestation. Also, you will
need to download/install *all* the MS critical updates since SP3. I'm
assuming that if you undertake this Repair install of the XP OS, you will be
doing so with a "slipstreamed" XP installation CD that contains SP3. On the
other hand if you decide to undertake the Repair install with your current
XP installation CD that contains an earlier SP you'll probably want to later
install SP3 after determining all went well with the Repair install assuming
the Repair install was successful.

The fact that this problem arose (apparently) following a failed attempt to
update the BIOS complicates matters in terms of undertaking a successful
Repair install of the OS. But it's worth a try since you've indicated the
system is attempting a boot to the OS and you're not dealing with a
completely dead machine at this point.

Should the Repair install prove unsuccessful see if there's any info in your
motherboard's user manual dealing with any process to revert to an earlier
(usable) BIOS or somehow salvaging/resurrecting the failed latest BIOS
attempt. You may want to contact the MB's manuf. on this as well.
Anna
 
Anna,

The BIOS upgrade completed successfully. What I
failed to do in my "un-thinking" haste was to save the
current CMOS as the default. So, subsequently when
the machine re-booted following the BIOS upgrade,
the mfg default took effect. Obviously, there were
CMOS settings that XP was depending upon and
so effectively I "shot a hole in my foot".

The only reason I updated the BIOS in the first place
is that there were fixes to USB that hopefully would
solve a severe performance problem with an external
WD 1TB HD.

The XP product disc pre-dates even SP2, so I'll
take one more look at the BIOS settings to see if I
can pin-point where the problem might be. Failing
success there, I'll run a XP repair and install SP3.

You post suggests that a XP repair would somehow
resolve a BIOS setting issue, is that correct?

Thanks,
Bill
 
Anna,

I booted from a 3-1/2 floppy formatted with a
system. At the DOS prompt, I attempted to set
the current directory to the "C" drive, (dir c:\)
and get the message "invalid drive letter". If XP
is failing to start because of a reference to a
folder on the "c" drive, perhaps that's where the
problem is??? I know of nothing in the BIOS
that references hardware by letters???

Bill
 
Anna,

I booted from a 3-1/2 floppy formatted with a
system. At the DOS prompt, I attempted to set
the current directory to the "C" drive, (dir c:\)
and get the message "invalid drive letter".


Probably because C: is NTFS. DOS can't access NTFS.
 
Bill said:
Anna,
The BIOS upgrade completed successfully. What I
failed to do in my "un-thinking" haste was to save the
current CMOS as the default. So, subsequently when
the machine re-booted following the BIOS upgrade,
the mfg default took effect. Obviously, there were
CMOS settings that XP was depending upon and
so effectively I "shot a hole in my foot".

The only reason I updated the BIOS in the first place
is that there were fixes to USB that hopefully would
solve a severe performance problem with an external
WD 1TB HD.

The XP product disc pre-dates even SP2, so I'll
take one more look at the BIOS settings to see if I
can pin-point where the problem might be. Failing
success there, I'll run a XP repair and install SP3.

You post suggests that a XP repair would somehow
resolve a BIOS setting issue, is that correct?

Thanks,
Bill


Bill:
No, an XP Repair installation would not really have any relevant effect on a
BIOS setting as such. But I really don't think that's the pertinent issue
here, i.e., the BIOS setting(s) - at least in terms of how you described the
problem you're experiencing.

Again, based upon your description of the current problem I do not think any
tinkering of the BIOS setting(s) will resolve your problem. But obviously if
you think otherwise it's fine to review your BIOS settings in conjunction
with your motherboard's user manual.

My own view is that you should go ahead and undertake a Repair install of
the OS. It probably would be best if you would "slipstream" your XP OS
installation CD to include at least SP2, but there's no real harm in going
ahead with your current CD. In any event, should the Repair install prove
successful you would then install SP2 - work with it to determine all is
well - and then subsequently install SP3.
Anna
 
PROGRESS!!

It looks as though I'm "out of the woods", as the
Repair completed, Windows re-activated and
SP3 re-installed.

Not being familiar with the internals of XP and
its interface to BIOS functions, I'm at a loss to
explain exactly what got resolved with a repair
operation. I can only guess that XP somehow
adjusted itself to whatever it found in the BIOS
properties, assuming such properties exist as
such.

Thanks for your help.
Bill
 
Back
Top