Windows Xp reboots

[Loretta]

I am putting a new motherboard and processor into an E-Machine. This is the
third replacement on three different emachines.The other two did not give me
this problem.

The hard drive is running Windows XP home with sp2. 256mb memory, 80gb hd,
70gb free. I am installing an Asus K8M-VM main board and sempron 754 socket
processor.

The windows start to boot and then restarts. the error is 0x0000007e (shut
down to protect system.

I may have made it more difficult because I tried to do a repair install
when I couldn't get it to load in safe mode. Now it reboots instead of
finishing the install.

I hope I have given you enough information.
As always my thanks in advance.
Loretta

 

[Mark L. Ferguson]

Some Common reasons for this could be: 1) This is the most common reason.
The Operating System, in this case Windows XP does not have a driver for the
controller card that is being used in this system. this means that the
appropriate driver needs to be downloaded from the vendor's website and
placed on a floppy disk. During Setup you will need to hit the F6 key when
that option is presented during setup to load the driver.
www.highpoint-tech.com 2) Second most common reason This can be caused by
boot sector viruses. So make sure that the system is scanned for viruses
before starting the installation. 3) The volume could be corrupt and is not
readable. When it try's to read the volume it is not finding the data on it
or the data is illegible. 4) Post setup the registry may be corrupted. 5)
Drive Translation is being used that is not being understood.

 

[Anna]

Some Common reasons for this could be: 1) This is the most common reason.
The Operating System, in this case Windows XP does not have a driver for
the controller card that is being used in this system. this means that the
appropriate driver needs to be downloaded from the vendor's website and
placed on a floppy disk. During Setup you will need to hit the F6 key when
that option is presented during setup to load the driver.
www.highpoint-tech.com 2) Second most common reason This can be caused by
boot sector viruses. So make sure that the system is scanned for viruses
before starting the installation. 3) The volume could be corrupt and is
not readable. When it try's to read the volume it is not finding the data
on it or the data is illegible. 4) Post setup the registry may be
corrupted. 5) Drive Translation is being used that is not being
understood.

Loretta:
Well, we'll set aside (at this point-in-time) any driver issues or boot
sector viruses, etc. that may be causing your problem.

Since you're changing the motherboard (I'm assuming it's a different
motherboard than the original one - I'm not at all familiar with that ASUS
K8M-VM ) together with a new processor, in a sense you're building a new
computer even though I take it you'll be using the previously installed RAM,
same HDD, and perhaps one or more optical drives, and the same
graphics/video & sound cards (if present). Is that about it? And there were
no problems with the original system that prevented it from properly
functioning, right? And, if & when you're able to get to a Desktop, you will
have available any necessary drivers for whatever graphics/sound card(s)
that are installed, right? Including, of course, your motherboard's CD
containing any drivers needed by the MB.

I'm assuming you're using either a retail or consumer-OEM version of the XP
installation CD, rather than any eMachine OEM XP installation CD. Am I
correct about this?

Do I understand that you were *never* able to successfully undertake a
Repair install of the OS? That the system "rebooted" on its own before the
Repair install had concluded? So that you've *never* been able to boot to a
Desktop. Is that right?

(I'm assuming, of course, that you're using another functioning computer to
post your messages)

I suppose a fresh install of the XP OS isn't practical at this time since
you want to salvage the programs and your user-created data currently on the
installed 80 GB HDD, right? And I don't suppose you have another HDD at hand
where you could attempt a fresh install of the OS.

Did you try undertaking the Repair install a second or third time? It's
always worth a try in our experience.
Anna

 

[Gerry]

Anna

There's an interesting response to this question in Hardware.

--
Regards.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~

 

[Anna]

Anna

There's an interesting response to this question in Hardware.

--
Regards.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~

Hi Gerry:
I see that Loretta posted the identical query to the XP hardware newsgroup,
but I haven't come across any response to her query in that group. Could you
give me the gist of it or direct me to its precise location in case the
Subject line has changed? Thanks.
Anna

 

[Gerry]

Anna

Strange not in Google

#[email protected]

From Ghost rider

"An e-Machines computer is has components designed and built for it. And
an ASUS K8M-VM machine has components designed and built for it. These
two machines are so entirely different that the Windows XP that came
from
the e-Machines unit is not expected to run when hooked up to the Asus
one.
Moreover, since the version of Windows XP supplied for the e-Machines is
bios-locked specifically for it, it would also be doubtful that it can
be
installed in the Asus unit. Or the e-Machines Windows XP cdrom is a disc
recovery set.

Time to get a new retail version of Windows XP Home or a Microsoft OEM
version for new computers without an OS."



--
Regards.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~

 

[Anna]

Anna
From Ghost rider

"An e-Machines computer is has components designed and built for it. And
an ASUS K8M-VM machine has components designed and built for it. These
two machines are so entirely different that the Windows XP that came from
the e-Machines unit is not expected to run when hooked up to the Asus one.
Moreover, since the version of Windows XP supplied for the e-Machines is
bios-locked specifically for it, it would also be doubtful that it can be
installed in the Asus unit. Or the e-Machines Windows XP cdrom is a disc
recovery set.

Time to get a new retail version of Windows XP Home or a Microsoft OEM
version for new computers without an OS."

--
Regards.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~

Gerry (and Loretta, if she's listening!):
While it is true that the eMachines line of PCs are OEM products - as I
believe I indicated in my response to Loretta's query - we've "rebuilt" a
number of those machines using different motherboards & processors. There's
usually no problem in doing so as long as the user has available a retail
(or consumer-OEM) version of the XP installation CD in order to fresh
install the OS and the necessary drivers for any graphics/video & sound
cards that may be installed. I believe I pointed this out to Loretta as
well.

Admittedly, the success of a Repair install (assuming she has the requisite
XP installation CD and not the OEM "recovery" disk) - which apparently is
Loretta's main objective - can be iffy in this type of situation however
we've successfully undertaken that process in more than a few cases. And
we've found - as I believe I also pointed out to Loretta - that it pays to
retry the Repair install process a number of times should the first or
second Repair not "take". We no longer find it a surprising development when
a repeated Repair install is successful after the original (and even second)
Repair install undertaking was unsuccessful.
Anna

 

[Gerry]

Anna

You made a whole host of provisos in your usual inimitable style. This
post zeroed in on some of your points more directly. However, I suspect
Loretta may have gone away.


--
Regards.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~

 

[Loretta]

Hi Anna,
The motherboard is a k8v-vm, sorry.
Mother board and processor were changed and then I had to change the power
supply as it needed a 24 pin instead of a 20 pin.

I have done a side by side install which works great.
I did then run a virus scan with house call. There was only one low risk
virus.
I would prefer to get the original running as I has a lot of programs on it
that would take a long time to reinstall.
Yes I am using an OEM. On the side by side install it regestered fine.
Yes I have three of my own computers to work with.
I have tried many times to do a repair install. I have a suspicion that
something the registry is trying to load it interfering. Is it possible to
get to that specific registry data from the new install or by slaving it to
another computer?
Thank you for your help.
Loretta

 

[Loretta]

No Loretta has been putting up exterior Christmas lights and displays.
Happy Holidays, Season, but for me Merry Christmas to all.
Loretta

 

[Loretta]

Ps. all of the other components are the original.
The Asus site has a bios up grade. Would that overwrite the E-Machine Bios?
Loretta

 

[Anna]

Hi Anna,
The motherboard is a k8v-vm, sorry.
Mother board and processor were changed and then I had to change the power
supply as it needed a 24 pin instead of a 20 pin.

I have done a side by side install which works great.
I did then run a virus scan with house call. There was only one low risk
virus.
I would prefer to get the original running as I has a lot of programs on
it that would take a long time to reinstall.
Yes I am using an OEM. On the side by side install it regestered fine.
Yes I have three of my own computers to work with.
I have tried many times to do a repair install. I have a suspicion that
something the registry is trying to load it interfering. Is it possible to
get to that specific registry data from the new install or by slaving it
to another computer?
Thank you for your help.
Loretta

And Loretta later adds...

Ps. all of the other components are the original.
The Asus site has a bios up grade. Would that overwrite the E-Machine
Bios?
Loretta

Loretta:
Please understand that now that you have installed a new motherboard, a BIOS
update for that motherboard is for *that* motherboard, not for a "E-Machine
Bios". (I'm assuming, of course, that the new motherboard you installed is a
different make & model of motherboard than the one originally installed in
your E-Machines PC).

In any event I really don't think an updated BIOS for your ASUS board is at
the root of your problem. However there's usually no harm in installing an
updated ASUS BIOS...the process is fairly straightforward & generally
forgiving should anything go amiss during the downloading/installing of the
update. I assume you've done this before. Just take it slowly and have a
complete understanding of the process and steps to be taken based on the
ASUS documentation re this process. My recommendation would be not to
install a *Beta* version of a BIOS update should that be the type you're
contemplating - unless you absolutely know such an update is designed to
correct the *specific* problem you're experiencing.

As I previously indicated it is not uncommon for a Repair install of the XP
OS *not* to "take". It happens despite our best efforts even when we know
the process we're undertaking is correct and we're dealing with
non-defective components. It should work but it doesn't. So there are times
when you'll have no other recourse than to make a fresh install of the XP
OS, then connect the original HDD as a secondary HDD and attempt to get as
much data off it as possible onto the new HDD.

I know of no way of accessing/manipulating registry data to effect a
successful Repair install (if that's the essence of your last query).
Anna

 

[Loretta]

Thank you.
Loretta

And Loretta later adds...



Loretta:
Please understand that now that you have installed a new motherboard, a
BIOS update for that motherboard is for *that* motherboard, not for a
"E-Machine Bios". (I'm assuming, of course, that the new motherboard you
installed is a different make & model of motherboard than the one
originally installed in your E-Machines PC).

In any event I really don't think an updated BIOS for your ASUS board is
at the root of your problem. However there's usually no harm in installing
an updated ASUS BIOS...the process is fairly straightforward & generally
forgiving should anything go amiss during the downloading/installing of
the update. I assume you've done this before. Just take it slowly and have
a complete understanding of the process and steps to be taken based on the
ASUS documentation re this process. My recommendation would be not to
install a *Beta* version of a BIOS update should that be the type you're
contemplating - unless you absolutely know such an update is designed to
correct the *specific* problem you're experiencing.

As I previously indicated it is not uncommon for a Repair install of the
XP OS *not* to "take". It happens despite our best efforts even when we
know the process we're undertaking is correct and we're dealing with
non-defective components. It should work but it doesn't. So there are
times when you'll have no other recourse than to make a fresh install of
the XP OS, then connect the original HDD as a secondary HDD and attempt to
get as much data off it as possible onto the new HDD.

I know of no way of accessing/manipulating registry data to effect a
successful Repair install (if that's the essence of your last query).
Anna