Had to change motherboard

G

Guest

I had a motherboard and processor failure. Of course the motherboard is no
longer in production, so I had to buy a different brand. I install all the
motherboard and new processor with all the old hardware. Windows Xp will
start to boot,flash a blue screen with an error message for about a billionth
of a second, then reboot. There is not enough time to read the message. I
have booted with boot logging, and there is no ntbtlog.txt. I performed the
repair install with no change in the boot results. The symptoms are the
same. If I boot in safe mode, NDIS.SYS is the last loaded entity before the
hang and reboot. It is not faulty hardware, I have linux installed on another
drive that boots and performs without a problem.
 
P

philo

Harry Paratestes said:
I had a motherboard and processor failure. Of course the motherboard is no
longer in production, so I had to buy a different brand. I install all
the
motherboard and new processor with all the old hardware. Windows Xp will
start to boot,flash a blue screen with an error message for about a
billionth
of a second, then reboot. There is not enough time to read the message. I
have booted with boot logging, and there is no ntbtlog.txt. I performed
the
repair install with no change in the boot results. The symptoms are the
same. If I boot in safe mode, NDIS.SYS is the last loaded entity before
the
hang and reboot. It is not faulty hardware, I have linux installed on
another
drive that boots and performs without a problem.


you need to boot off your XP cd and perform a repair installtion...

basicially you go to install XP...
(do not use the recovery console option)
it should detect an existing version and ask you if you want to repair it,,,
just say "yes"
 
B

Bruce Chambers

Harry said:
I had a motherboard and processor failure. Of course the motherboard is no
longer in production, so I had to buy a different brand. I install all the
motherboard and new processor with all the old hardware. Windows Xp will
start to boot,flash a blue screen with an error message for about a billionth
of a second, then reboot. There is not enough time to read the message. I
have booted with boot logging, and there is no ntbtlog.txt. I performed the
repair install with no change in the boot results. The symptoms are the
same. If I boot in safe mode, NDIS.SYS is the last loaded entity before the
hang and reboot. It is not faulty hardware, I have linux installed on another
drive that boots and performs without a problem.


Normally, and assuming a retail license (many factory-installed OEM
installations are BIOS-locked to a specific chipset and therefore not
transferable to a new motherboard - check yours before starting), unless
the new motherboard is virtually identical (same chipset, same IDE
controllers, same BIOS version, etc.) to the one on which the WinXP
installation was originally performed, you'll need to perform a repair
(a.k.a. in-place upgrade) installation, at the very least:

How to Perform an In-Place Upgrade of Windows XP
http://support.microsoft.com/directory/article.asp?ID=KB;EN-US;Q315341

Changing a Motherboard or Moving a Hard Drive with WinXP Installed
http://www.michaelstevenstech.com/moving_xp.html

The "why" is quite simple, really, and has nothing to do with
licensing issues, per se; it's a purely technical matter, at this point.
You've pulled the proverbial hardware rug out from under the OS. (If
you don't like -- or get -- the rug analogy, think of it as picking up a
Cape Cod style home and then setting it down onto a Ranch style
foundation. It just isn't going to fit.) WinXP, like Win2K before it,
is not nearly as "promiscuous" as Win9x when it comes to accepting any
old hardware configuration you throw at it. On installation it
"tailors" itself to the specific hardware found. This is one of the
reasons that the entire WinNT/2K/XP OS family is so much more stable
than the Win9x group.

As always when undertaking such a significant change, back up any
important data before starting.

This will also probably require re-activation, unless you have a
Volume Licensed version of WinXP Pro installed. If it's been more than
120 days since you last activated that specific Product Key, you'll most
likely be able to activate via the Internet without problem. If it's
been less, you might have to make a 5 minute phone call.



--

Bruce Chambers

Help us help you:



They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety. -Benjamin Franklin

Is life so dear or peace so sweet as to be purchased at the price of
chains and slavery? .... I know not what course others may take, but as
for me, give me liberty, or give me death! -Patrick Henry
 
P

philo

Harry Paratestes said:
I have done that already, repaired the installation, and the problem
persists.
:


Although the repair instalaltion usually works...
if the H/W is just too much different, it will fail.

If there is important data on the drive,
you'd need to put the drive in another machine and back it up,

If the data is "somewhat" important..but not critical...
then you can just install windows in another folder...
your data *should* still be there but of course you'd have to reinstall all
apps...

and of course if nothing on the drive is important at all...
just format and perform a clean install
 
G

Guest

This is a retail version of Xp, so it is not bios locked. I was looking at
having to perform a clean install as a last resort, but was not looking
forward to it. This is not a very impressive feature of this operating
system.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top