Boot problem after BIOS upgrade

  • Thread starter Thread starter Deesto
  • Start date Start date
D

Deesto

In order to take advantage of BIOS fixes for my Chaintech 7NJS Zenith
motherboard, I was forced to upgrade my BIOS. The update was completed
successfully; however, my machine will now no longer boot into Windows XP
Pro SP1. With each reboot, I'm faced with the SafeMode/Last Good Config
option menu, and no matter which choice I select, the same thing happens:
the screen goes black for a few seconds, and then the infamous blue screen
appears with white text, but only for a fraction of a second and not long
enough to read any error text. It then reboots, and the process repeasts
infinitely.
There were no hardware or software changes of any kind in between.
What can I do to restore my system, without losing any of my data
(especially My Documents, etc., which tend to get destroyed when doing a
reinstall?).
Thank you.
John
 
Deesto said:
In order to take advantage of BIOS fixes for my Chaintech 7NJS Zenith
motherboard, I was forced to upgrade my BIOS. The update was
completed successfully; however, my machine will now no longer boot
into Windows XP Pro SP1. With each reboot, I'm faced with the
SafeMode/Last Good Config option menu, and no matter which choice I
select, the same thing happens: the screen goes black for a few
seconds, and then the infamous blue screen appears with white text,
but only for a fraction of a second and not long enough to read any
error text. It then reboots, and the process repeasts infinitely.
There were no hardware or software changes of any kind in between.
What can I do to restore my system, without losing any of my data
(especially My Documents, etc., which tend to get destroyed when
doing a reinstall?).
Thank you.
John
Click to expand...

You can try a repair install, but do not reinstall, until you save your data
you do not have backed up.
Pay close attention to the warning links.
Click on the link below, or copy and paste the link into the address box
if using the web based newsgroup.
Repair Install
http://michaelstevenstech.com/XPrepairinstall.htm

Are you sure the bios flash was the correct one for your motherboard and was
successful? Sometimes the same MB will have different revisions. The bios
must be for the exact MB and version.
--

Michael Stevens MS-MVP XP
(e-mail address removed)
http://michaelstevenstech.com
For a better newsgroup experience. Setup a newsreader.
http://michaelstevenstech.com/outlookexpressnewreader.htm
 
You can try a repair install, but do not reinstall, until you save
your data you do not have backed up.
Pay close attention to the warning links.
Click on the link below, or copy and paste the link into the address
box if using the web based newsgroup.
Repair Install
http://michaelstevenstech.com/XPrepairinstall.htm

Are you sure the bios flash was the correct one for your motherboard
and was successful? Sometimes the same MB will have different
revisions. The bios must be for the exact MB and version.
Click to expand...

Hi Michael:
Yes; I've actually got a tri-boot machine, with 98, XP, and BSD
installed. The machine boots fine generically, and the other two OSes
were unaffected by the BIOS upgrade.
Thanks,
John
 
Seen the below links?

http://www.badflash.com/

http://www.ozflash.com.au/oz_remove.htm

Good luck,
-Lawrence in Seattle
Click to expand...

Thanks Lawrence, but I think the BIOS is fine. As I mentioned below,
two other operating systems (Win98 and FreeBSD) have no trouble with the
BIOS and boot just fine. This is not a bad hardware problem, but, I
assume, a problem with Windows XP's hardware activation scheme. I can
boot into these 2 OSes, into DOS using a floppy disk, and probably any
other OS except for XP.

I'll try the link Mr. Stevens offered to his site below, but I do recall
trying it once before and not being able to follow it completely because
a "repair" option was never offered; thus, everything ended up being
restored correctly, _except_ for files and folders related to my profile
(My Documents, My Settings, My Favorites, etc.), which were obliterated
during the process.

Thanks,
John
 
Unfortunately, successfully completing this procedure did not produce
improved results. Luckily, the partition appeared recoverable in WinXP
install, so I selected it, the initial stage of the repair install
completed successfully, and the computer rebooted. Of course, that was
the end of my luck.
When it rebooted, just as the Windows XP logo should have
appeared, the blue screen appeared instead. The only difference between
before the attempted recovery and now is that now, instead of
dissappearing before it could be read, the blue screen stays up and does
not go away at all until the computer is shut down or rebooted. It says
"A problem has been detected" and Windows has been shut down to protect
the computer. It also says to check for viruses, check hard drives and
controllers, run CHKDSK /F, and restart. Of course, I can't do any of
these things in XP. It then gives a STOP code as follows:

STOP: 0x0000007B (0xF8951640, 0xC0000034, 0x00000000, 0x00000000)
(I hope that helps with something, because it wasn't fun to write down
or retype here ;)

Again, the other OSes are just fine.

Please help. Thank you.
John
 
Deesto said:
Unfortunately, successfully completing this procedure did not produce
improved results. Luckily, the partition appeared recoverable in
WinXP install, so I selected it, the initial stage of the repair
install completed successfully, and the computer rebooted. Of
course, that was the end of my luck.
When it rebooted, just as the Windows XP logo should have
appeared, the blue screen appeared instead. The only difference
between before the attempted recovery and now is that now, instead of
dissappearing before it could be read, the blue screen stays up and
does not go away at all until the computer is shut down or rebooted.
It says "A problem has been detected" and Windows has been shut down
to protect the computer. It also says to check for viruses, check
hard drives and controllers, run CHKDSK /F, and restart. Of course,
I can't do any of these things in XP. It then gives a STOP code as
follows:

STOP: 0x0000007B (0xF8951640, 0xC0000034, 0x00000000, 0x00000000)
(I hope that helps with something, because it wasn't fun to write down
or retype here ;)

Again, the other OSes are just fine.

Please help. Thank you.
John
Click to expand...

I couldn't find the exact stop error, but check this one for a starter.
http://support.microsoft.com/default.aspx?scid=kb;en-us;314082

What controller do you have the XP installation on, and did you load the
raid drivers during the repair install?
I would flash back to the original bios if it was working.
Also check in the alt newsgroup.
alt.comp.periphs.mainboard.chaintech
--

Michael Stevens MS-MVP XP
(e-mail address removed)
http://michaelstevenstech.com
For a better newsgroup experience. Setup a newsreader.
http://michaelstevenstech.com/outlookexpressnewreader.htm
 
Hi All,

0x0000007B: INACCESSIBLE_BOOT_DEVICE
Typical causes: Installing incorrect device drivers when installing or
upgrading storage adapter hardware, or a virus.

That's according to: (bookmark this one) :
http://aumha.org/win5/kbestop.php#0x8e
Scroll about half-way down, or cut&paste 0x0000007B into a ctrl+f search box

So... device drivers, hardware... or a virus.... hmmm.. which one would I
choose.

Good luck,
-Lawrence in Seattle

<snip snip>
 
If I am missing something here, feel free to offer an explanation... but I
see the original post, and all of the nested replies... nothing pertinent
has been lost.

I posted it like a note in a margin.... and it remains in context because I
nested it after yours -- since it refers to the Stop message that you could
not find....

I would think you would be more concerned had I edited the post's title....
as that would affect Subject queries. But instead, I did what we should all
be trying to do: I appended pertinent information to the thread.

-Lawrence in Seattle
 
Hi All,

0x0000007B: INACCESSIBLE_BOOT_DEVICE
Typical causes: Installing incorrect device drivers when installing or
upgrading storage adapter hardware, or a virus.

That's according to: (bookmark this one) :
http://aumha.org/win5/kbestop.php#0x8e
Scroll about half-way down, or cut&paste 0x0000007B into a ctrl+f
search box

So... device drivers, hardware... or a virus.... hmmm.. which one
would I choose.
Click to expand...
Well I don't know what you would choose, but I wouldn't choose any of
those.
"Typical causes: Installing incorrect device drivers when installing or
upgrading storage adapter hardware, or a virus."
I didn't install or upgrade any new hardware, and my system was virus-
free minutes before I performed the BIOS flash.
Also please keep in mind that page lists "typical" causes and does not
claim to be an end-all for relevent info.
Thanks.
John
 
Lawrence,
Please don't <snip> all relevant information to the post you are
replying until the OP responds.

I couldn't find the exact stop error, but check this one for a
starter.
http://support.microsoft.com/default.aspx?scid=kb;en-us;314082

What controller do you have the XP installation on, and did you load
the raid drivers during the repair install?
Click to expand...

The XP installation is on the first partition of the primary IDE drive
(IDE0), which is the only hard drive installed on this box. The board
does come with a RAID controller, but this has its own BIOS driver and,
as far as I know, does not get loaded unless RAID drives are attached.
I would flash back to the original bios if it was working.
Click to expand...

That would be a shame, since the other OSes have already adapted to the
new BIOS without trouble, but if you confirm this would work, I guess I
don't have much choice.

Also check in the alt newsgroup.
alt.comp.periphs.mainboard.chaintech
Click to expand...

Will do. Thanks Michael.
John
 
Lawrence,
Please don't <snip> all relevant information to the post you are
replying until the OP responds.

I couldn't find the exact stop error, but check this one for a
starter.
http://support.microsoft.com/default.aspx?scid=kb;en-us;314082

What controller do you have the XP installation on, and did you load
the raid drivers during the repair install?
I would flash back to the original bios if it was working.
Also check in the alt newsgroup.
alt.comp.periphs.mainboard.chaintech
Click to expand...

Sadly, this newsgroup contains nothing but a few SPAM messages, such as
"ATTRACT WOMEN INSTANSTLY (PHEROMONES)".
:(
More help needed if you can. Thanks.
John
 
Yes. I know.... I never said it was the bible.

I shot the link out to aid in your search for the solution. Or, more
precisely, to clarify what that Stop Message commonly means. Not
conclusively means... but commonly means.

Keep in mind. I was *sincerely* trying to HELP you.

In flashing your BIOS, you executed a procedure that has been known to give
users potential grief in even the most basic of circumstances. You have a
tri-boot system. And now XP, known for delving deeper into hardware than
any previous OS, is not happy about your choice in BIOSs.

If you had only an XP single-boot system, and were getting the same results,
you would conclude that the BIOS was bad, would you not? Well, from XPs
point of view, maybe the BIOS is bad.

Which version of BIOS (of two) did you flash? 3.0? 4.0?.... And how could
you tell which to use? Their website doesn't say. Even in other languages.
I know because I tried running its FAQs & BIOS Download pages through the
online translator at Worldlingo.com, to see if the Chinese versions offered
more information... no dice. (although that technique has worked for me
before, for tracking down drivers).

Maybe the difference between the version you needed, and the one you
installed, is manifesting itself in your present situation. The other OSs
may not care so much. But since XP is so sophisticated, if it, in
communicating with your board during your repair installation, determined
what driver to use based features and commands the BIOS claimed to have, and
is now trying to use 4.0-speak (for example), when it should really be
speaking "3.0", then you could easily get BSODs.


But good luck anyway,
-Lawrence in Seattle
 
Back
Top