stop error

[--------daz---------]

i have just put in a new motherboard,it gets past the post
stage ok and the bios bit but i end up with the following
blue screen message 0x0000007b
(0xf894d640,0x0000034,0x0000000,0x0000000)

[Dan DeStefano]

was this motherboard replaced in a machine with a current wxp installation?
unfortunately i have never been able to get wxp to boot properly after
replacing a motherboard. i can only assume that this is due to windows
product activation. when replacing major hardware components (namely an
ethernet adapter, processor or mobo) the wpa wizard will detect this change
and prompt you to re-activate. however, since the motherboard controls
pretty much the whole machine, when replacing it, wpa gets too "confused"
as, essentially, all the hardware on the machine is changed due to the new
chipset in the mobo. and, since windows no longer has a frame of reference
with which to compare these hardware changes, it just crashes. note: this is
just a wild speculation as i have been unable to find any technical resource
that discusses the reason for this. maybe someone on the ng will have more
info.
i have also tried uninstalling all chipset drivers and system components
that are bound to the mobo and its chipset, then shutting down, replacing
mobo and booting, but with the same result. so, as far as i have been able
to find, replacing a motherboard in xp will require a reinstallation. this
is why having a separate partition/disk for your data is a good idea. if
your data was not installed on a separate partition or a separate disk, then
in order to access it you will have to reinstall windows over the previous
installation (you can try a repair too). then, once you have backed up your
data, format and reinstall windows onto its own partition, leaving enough
room to create a second partition for your data.

hope this helps

Dan DeStefano


"--------daz---------" > wrote in message
...
> i have just put in a new motherboard,it gets past the post
> stage ok and the bios bit but i end up with the following
> blue screen message 0x0000007b
> (0xf894d640,0x0000034,0x0000000,0x0000000)

[Walter Clayton]

To be expected.

Do a repair reinstall. This will insure that the hardware is enumerated
properly while leaving your installed applications alone.

--
Walter Clayton - MS MVP(WinXP)
Associate Expert
http://www.microsoft.com/windowsxp/expertzone
Any technology distinguishable from magic is insufficiently advanced.
http://www.dts-l.org
http://support.microsoft.com/servicedesks/fileversion/default.asp


"--------daz---------" > wrote in message
...
> i have just put in a new motherboard,it gets past the post
> stage ok and the bios bit but i end up with the following
> blue screen message 0x0000007b
> (0xf894d640,0x0000034,0x0000000,0x0000000)

[Walter Clayton]

The issue has nothing to do with WPA. ;-)

--
Walter Clayton - MS MVP(WinXP)
Associate Expert
http://www.microsoft.com/windowsxp/expertzone
Any technology distinguishable from magic is insufficiently advanced.
http://www.dts-l.org
http://support.microsoft.com/servicedesks/fileversion/default.asp


"Dan DeStefano" <ddestefanoATwinmarcompaniesDOTcom> wrote in message
...
> was this motherboard replaced in a machine with a current wxp
installation?
> unfortunately i have never been able to get wxp to boot properly after
> replacing a motherboard. i can only assume that this is due to windows
> product activation. when replacing major hardware components (namely an
> ethernet adapter, processor or mobo) the wpa wizard will detect this
change
> and prompt you to re-activate. however, since the motherboard controls
> pretty much the whole machine, when replacing it, wpa gets too "confused"
> as, essentially, all the hardware on the machine is changed due to the new
> chipset in the mobo. and, since windows no longer has a frame of reference
> with which to compare these hardware changes, it just crashes. note: this
is
> just a wild speculation as i have been unable to find any technical
resource
> that discusses the reason for this. maybe someone on the ng will have more
> info.
> i have also tried uninstalling all chipset drivers and system components
> that are bound to the mobo and its chipset, then shutting down, replacing
> mobo and booting, but with the same result. so, as far as i have been able
> to find, replacing a motherboard in xp will require a reinstallation. this
> is why having a separate partition/disk for your data is a good idea. if
> your data was not installed on a separate partition or a separate disk,
then
> in order to access it you will have to reinstall windows over the previous
> installation (you can try a repair too). then, once you have backed up
your
> data, format and reinstall windows onto its own partition, leaving enough
> room to create a second partition for your data.
>
> hope this helps
>
> Dan DeStefano
>
>
> "--------daz---------" > wrote in message
> ...
> > i have just put in a new motherboard,it gets past the post
> > stage ok and the bios bit but i end up with the following
> > blue screen message 0x0000007b
> > (0xf894d640,0x0000034,0x0000000,0x0000000)
>
>

[Dan DeStefano]

then what is the reason for this? i have never had a problem with other
versions of windows after replacing a motherboard, which is why i theorized
it was due to wpa. is there a way to replace a mobo on a wxp machine without
having to reinstall?

Dan DeStefano


"Walter Clayton" > wrote in message
...
> The issue has nothing to do with WPA. ;-)
>
> --
> Walter Clayton - MS MVP(WinXP)
> Associate Expert
> http://www.microsoft.com/windowsxp/expertzone
> Any technology distinguishable from magic is insufficiently advanced.
> http://www.dts-l.org
> http://support.microsoft.com/servicedesks/fileversion/default.asp
>
>
> "Dan DeStefano" <ddestefanoATwinmarcompaniesDOTcom> wrote in message
> ...
> > was this motherboard replaced in a machine with a current wxp
> installation?
> > unfortunately i have never been able to get wxp to boot properly after
> > replacing a motherboard. i can only assume that this is due to windows
> > product activation. when replacing major hardware components (namely an
> > ethernet adapter, processor or mobo) the wpa wizard will detect this
> change
> > and prompt you to re-activate. however, since the motherboard controls
> > pretty much the whole machine, when replacing it, wpa gets too
"confused"
> > as, essentially, all the hardware on the machine is changed due to the
new
> > chipset in the mobo. and, since windows no longer has a frame of
reference
> > with which to compare these hardware changes, it just crashes. note:
this
> is
> > just a wild speculation as i have been unable to find any technical
> resource
> > that discusses the reason for this. maybe someone on the ng will have
more
> > info.
> > i have also tried uninstalling all chipset drivers and system components
> > that are bound to the mobo and its chipset, then shutting down,
replacing
> > mobo and booting, but with the same result. so, as far as i have been
able
> > to find, replacing a motherboard in xp will require a reinstallation.
this
> > is why having a separate partition/disk for your data is a good idea. if
> > your data was not installed on a separate partition or a separate disk,
> then
> > in order to access it you will have to reinstall windows over the
previous
> > installation (you can try a repair too). then, once you have backed up
> your
> > data, format and reinstall windows onto its own partition, leaving
enough
> > room to create a second partition for your data.
> >
> > hope this helps
> >
> > Dan DeStefano
> >
> >
> > "--------daz---------" > wrote in message
> > ...
> > > i have just put in a new motherboard,it gets past the post
> > > stage ok and the bios bit but i end up with the following
> > > blue screen message 0x0000007b
> > > (0xf894d640,0x0000034,0x0000000,0x0000000)
> >
> >
>
>

[Walter Clayton]

All operating systems, including non-MS ones, have the same potential issue.
When you change a motherboard, especially when the change involves a chipset
change, you are potentially making a major difference in the motherboard
resources and devices as well as how the motherboard/BIOS enumerates
devices. If the difference in the base hardware architecture is sufficiently
"small", then the OS will adjust fairly easily without resorting to an over
the top install. Odds are though that if you do something major like pull a
MVP AGP3 chipset out and replace it with a NVidia NForce 2 board then you
will probably have to reinstall. Note however that all that is required is a
repair reinstall. It's just as easy as reinstalling 9x over the top of
itself and has virtually no affect on the installed application base.

WPA has nothing to do with any of this. WPA will, potentially, request an
activation. Odds are it won't though on just a motherboard change assuming
all other peripherals are carried over. In this specific instance WPA is
definitely not a player since the boot strap sequence hasn't even gotten far
enough to run WPA.

--
Walter Clayton - MS MVP(WinXP)
Associate Expert
http://www.microsoft.com/windowsxp/expertzone
Any technology distinguishable from magic is insufficiently advanced.
http://www.dts-l.org
http://support.microsoft.com/servicedesks/fileversion/default.asp


"Dan DeStefano" <ddestefanoATwinmarcompaniesDOTcom> wrote in message
...
> then what is the reason for this? i have never had a problem with other
> versions of windows after replacing a motherboard, which is why i
theorized
> it was due to wpa. is there a way to replace a mobo on a wxp machine
without
> having to reinstall?
>
> Dan DeStefano
>
>
> "Walter Clayton" > wrote in message
> ...
> > The issue has nothing to do with WPA. ;-)
> >
> > --
> > Walter Clayton - MS MVP(WinXP)
> > Associate Expert
> > http://www.microsoft.com/windowsxp/expertzone
> > Any technology distinguishable from magic is insufficiently advanced.
> > http://www.dts-l.org
> > http://support.microsoft.com/servicedesks/fileversion/default.asp
> >
> >
> > "Dan DeStefano" <ddestefanoATwinmarcompaniesDOTcom> wrote in message
> > ...
> > > was this motherboard replaced in a machine with a current wxp
> > installation?
> > > unfortunately i have never been able to get wxp to boot properly after
> > > replacing a motherboard. i can only assume that this is due to windows
> > > product activation. when replacing major hardware components (namely
an
> > > ethernet adapter, processor or mobo) the wpa wizard will detect this
> > change
> > > and prompt you to re-activate. however, since the motherboard controls
> > > pretty much the whole machine, when replacing it, wpa gets too
> "confused"
> > > as, essentially, all the hardware on the machine is changed due to the
> new
> > > chipset in the mobo. and, since windows no longer has a frame of
> reference
> > > with which to compare these hardware changes, it just crashes. note:
> this
> > is
> > > just a wild speculation as i have been unable to find any technical
> > resource
> > > that discusses the reason for this. maybe someone on the ng will have
> more
> > > info.
> > > i have also tried uninstalling all chipset drivers and system
components
> > > that are bound to the mobo and its chipset, then shutting down,
> replacing
> > > mobo and booting, but with the same result. so, as far as i have been
> able
> > > to find, replacing a motherboard in xp will require a reinstallation.
> this
> > > is why having a separate partition/disk for your data is a good idea.
if
> > > your data was not installed on a separate partition or a separate
disk,
> > then
> > > in order to access it you will have to reinstall windows over the
> previous
> > > installation (you can try a repair too). then, once you have backed up

> > your
> > > data, format and reinstall windows onto its own partition, leaving
> enough
> > > room to create a second partition for your data.
> > >
> > > hope this helps
> > >
> > > Dan DeStefano
> > >
> > >
> > > "--------daz---------" > wrote in message
> > > ...
> > > > i have just put in a new motherboard,it gets past the post
> > > > stage ok and the bios bit but i end up with the following
> > > > blue screen message 0x0000007b
> > > > (0xf894d640,0x0000034,0x0000000,0x0000000)
> > >
> > >
> >
> >
>
>

[Dan DeStefano]

dont mean to keep harping on the same issue, but i have changed out mobos in
all previous ms os and rarely had any problems, but every time i have
changed out a mobo in xp, it blue screens. is this just by chance that i
have had this experience? what about uninstalling all mobo chipset drivers
prior to replacing the mobo? would that mitigate this problem?

Dan DeStefano


"Walter Clayton" > wrote in message
...
> All operating systems, including non-MS ones, have the same potential
issue.
> When you change a motherboard, especially when the change involves a
chipset
> change, you are potentially making a major difference in the motherboard
> resources and devices as well as how the motherboard/BIOS enumerates
> devices. If the difference in the base hardware architecture is
sufficiently
> "small", then the OS will adjust fairly easily without resorting to an
over
> the top install. Odds are though that if you do something major like pull
a
> MVP AGP3 chipset out and replace it with a NVidia NForce 2 board then you
> will probably have to reinstall. Note however that all that is required is
a
> repair reinstall. It's just as easy as reinstalling 9x over the top of
> itself and has virtually no affect on the installed application base.
>
> WPA has nothing to do with any of this. WPA will, potentially, request an
> activation. Odds are it won't though on just a motherboard change
assuming
> all other peripherals are carried over. In this specific instance WPA is
> definitely not a player since the boot strap sequence hasn't even gotten
far
> enough to run WPA.
>
> --
> Walter Clayton - MS MVP(WinXP)
> Associate Expert
> http://www.microsoft.com/windowsxp/expertzone
> Any technology distinguishable from magic is insufficiently advanced.
> http://www.dts-l.org
> http://support.microsoft.com/servicedesks/fileversion/default.asp
>
>
> "Dan DeStefano" <ddestefanoATwinmarcompaniesDOTcom> wrote in message
> ...
> > then what is the reason for this? i have never had a problem with other
> > versions of windows after replacing a motherboard, which is why i
> theorized
> > it was due to wpa. is there a way to replace a mobo on a wxp machine
> without
> > having to reinstall?
> >
> > Dan DeStefano
> >
> >
> > "Walter Clayton" > wrote in message
> > ...
> > > The issue has nothing to do with WPA. ;-)
> > >
> > > --
> > > Walter Clayton - MS MVP(WinXP)
> > > Associate Expert
> > > http://www.microsoft.com/windowsxp/expertzone
> > > Any technology distinguishable from magic is insufficiently advanced.
> > > http://www.dts-l.org
> > > http://support.microsoft.com/servicedesks/fileversion/default.asp
> > >
> > >
> > > "Dan DeStefano" <ddestefanoATwinmarcompaniesDOTcom> wrote in message
> > > ...
> > > > was this motherboard replaced in a machine with a current wxp
> > > installation?
> > > > unfortunately i have never been able to get wxp to boot properly
after
> > > > replacing a motherboard. i can only assume that this is due to
windows
> > > > product activation. when replacing major hardware components (namely
> an
> > > > ethernet adapter, processor or mobo) the wpa wizard will detect this
> > > change
> > > > and prompt you to re-activate. however, since the motherboard
controls
> > > > pretty much the whole machine, when replacing it, wpa gets too
> > "confused"
> > > > as, essentially, all the hardware on the machine is changed due to
the
> > new
> > > > chipset in the mobo. and, since windows no longer has a frame of
> > reference
> > > > with which to compare these hardware changes, it just crashes. note:
> > this
> > > is
> > > > just a wild speculation as i have been unable to find any technical
> > > resource
> > > > that discusses the reason for this. maybe someone on the ng will
have
> > more
> > > > info.
> > > > i have also tried uninstalling all chipset drivers and system
> components
> > > > that are bound to the mobo and its chipset, then shutting down,
> > replacing
> > > > mobo and booting, but with the same result. so, as far as i have
been
> > able
> > > > to find, replacing a motherboard in xp will require a
reinstallation.
> > this
> > > > is why having a separate partition/disk for your data is a good
idea.
> if
> > > > your data was not installed on a separate partition or a separate
> disk,
> > > then
> > > > in order to access it you will have to reinstall windows over the
> > previous
> > > > installation (you can try a repair too). then, once you have backed
up
>
> > > your
> > > > data, format and reinstall windows onto its own partition, leaving
> > enough
> > > > room to create a second partition for your data.
> > > >
> > > > hope this helps
> > > >
> > > > Dan DeStefano
> > > >
> > > >
> > > > "--------daz---------" > wrote in message
> > > > ...
> > > > > i have just put in a new motherboard,it gets past the post
> > > > > stage ok and the bios bit but i end up with the following
> > > > > blue screen message 0x0000007b
> > > > > (0xf894d640,0x0000034,0x0000000,0x0000000)
> > > >
> > > >
> > >
> > >
> >
> >
>
>

[Walter Clayton]

I'm not even going to touch statistical anomalies. :-)

Uninstalling motherboard specific chipset drivers might work under some
circumstances and may be required if changing between VIA, ALi, Intel and
NVidia chipsets. Although typically changing the chipset vendor will in fact
generally require a reinstall to get all the devices playing together well.
There is also the fact that starting about a year ago (maybe a bit longer),
most single processor motherboards are being built with APICs rather than
standard PICs. That can prove to be interesting if the BIOS happens to set a
device on an IRQ higher than 15 and the XP HAL in use can only handle the
standard 16 IRQs.

--
Walter Clayton - MS MVP(WinXP)
Associate Expert
http://www.microsoft.com/windowsxp/expertzone
Any technology distinguishable from magic is insufficiently advanced.
http://www.dts-l.org
http://support.microsoft.com/servicedesks/fileversion/default.asp


"Dan DeStefano" <ddestefanoATwinmarcompaniesDOTcom> wrote in message
...
> dont mean to keep harping on the same issue, but i have changed out mobos
in
> all previous ms os and rarely had any problems, but every time i have
> changed out a mobo in xp, it blue screens. is this just by chance that i
> have had this experience? what about uninstalling all mobo chipset drivers
> prior to replacing the mobo? would that mitigate this problem?
>
> Dan DeStefano
>
>
> "Walter Clayton" > wrote in message
> ...
> > All operating systems, including non-MS ones, have the same potential
> issue.
> > When you change a motherboard, especially when the change involves a
> chipset
> > change, you are potentially making a major difference in the motherboard
> > resources and devices as well as how the motherboard/BIOS enumerates
> > devices. If the difference in the base hardware architecture is
> sufficiently
> > "small", then the OS will adjust fairly easily without resorting to an
> over
> > the top install. Odds are though that if you do something major like
pull
> a
> > MVP AGP3 chipset out and replace it with a NVidia NForce 2 board then
you
> > will probably have to reinstall. Note however that all that is required
is
> a
> > repair reinstall. It's just as easy as reinstalling 9x over the top of
> > itself and has virtually no affect on the installed application base.
> >
> > WPA has nothing to do with any of this. WPA will, potentially, request
an
> > activation. Odds are it won't though on just a motherboard change
> assuming
> > all other peripherals are carried over. In this specific instance WPA is
> > definitely not a player since the boot strap sequence hasn't even gotten
> far
> > enough to run WPA.
> >
> > --
> > Walter Clayton - MS MVP(WinXP)
> > Associate Expert
> > http://www.microsoft.com/windowsxp/expertzone
> > Any technology distinguishable from magic is insufficiently advanced.
> > http://www.dts-l.org
> > http://support.microsoft.com/servicedesks/fileversion/default.asp
> >
> >
> > "Dan DeStefano" <ddestefanoATwinmarcompaniesDOTcom> wrote in message
> > ...
> > > then what is the reason for this? i have never had a problem with
other
> > > versions of windows after replacing a motherboard, which is why i
> > theorized
> > > it was due to wpa. is there a way to replace a mobo on a wxp machine
> > without
> > > having to reinstall?
> > >
> > > Dan DeStefano
> > >
> > >
> > > "Walter Clayton" > wrote in message
> > > ...
> > > > The issue has nothing to do with WPA. ;-)
> > > >
> > > > --
> > > > Walter Clayton - MS MVP(WinXP)
> > > > Associate Expert
> > > > http://www.microsoft.com/windowsxp/expertzone
> > > > Any technology distinguishable from magic is insufficiently
advanced.
> > > > http://www.dts-l.org
> > > > http://support.microsoft.com/servicedesks/fileversion/default.asp
> > > >
> > > >
> > > > "Dan DeStefano" <ddestefanoATwinmarcompaniesDOTcom> wrote in message
> > > > ...
> > > > > was this motherboard replaced in a machine with a current wxp
> > > > installation?
> > > > > unfortunately i have never been able to get wxp to boot properly
> after
> > > > > replacing a motherboard. i can only assume that this is due to
> windows
> > > > > product activation. when replacing major hardware components
(namely
> > an
> > > > > ethernet adapter, processor or mobo) the wpa wizard will detect
this
> > > > change
> > > > > and prompt you to re-activate. however, since the motherboard
> controls
> > > > > pretty much the whole machine, when replacing it, wpa gets too
> > > "confused"
> > > > > as, essentially, all the hardware on the machine is changed due to
> the
> > > new
> > > > > chipset in the mobo. and, since windows no longer has a frame of
> > > reference
> > > > > with which to compare these hardware changes, it just crashes.
note:
> > > this
> > > > is
> > > > > just a wild speculation as i have been unable to find any
technical
> > > > resource
> > > > > that discusses the reason for this. maybe someone on the ng will
> have
> > > more
> > > > > info.
> > > > > i have also tried uninstalling all chipset drivers and system
> > components
> > > > > that are bound to the mobo and its chipset, then shutting down,
> > > replacing
> > > > > mobo and booting, but with the same result. so, as far as i have
> been
> > > able
> > > > > to find, replacing a motherboard in xp will require a
> reinstallation.
> > > this
> > > > > is why having a separate partition/disk for your data is a good
> idea.
> > if
> > > > > your data was not installed on a separate partition or a separate
> > disk,
> > > > then
> > > > > in order to access it you will have to reinstall windows over the
> > > previous
> > > > > installation (you can try a repair too). then, once you have
backed
> up
> >
> > > > your
> > > > > data, format and reinstall windows onto its own partition, leaving
> > > enough
> > > > > room to create a second partition for your data.
> > > > >
> > > > > hope this helps
> > > > >
> > > > > Dan DeStefano
> > > > >
> > > > >
> > > > > "--------daz---------" > wrote in message
> > > > > ...
> > > > > > i have just put in a new motherboard,it gets past the post
> > > > > > stage ok and the bios bit but i end up with the following
> > > > > > blue screen message 0x0000007b
> > > > > > (0xf894d640,0x0000034,0x0000000,0x0000000)
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>