Tech Support > Microsoft Windows > Repair Install Fails
Repair Install Fails
Posted by Gerald Fay on December 6th, 2005


Moving from an Asus Intel based MB to an Asus AMD board (939 with dual
core). Tried moving the hard drive to the new system and doing a repair
install. All seems to go well until reboot time with the Install CD out then
a quick blue screen, which I cannot read.

Suggestions besides a complete reinstall?

Thanks


Posted by Eric on December 6th, 2005


Windows XP doesn't take well to changing the motherboard because the chipset,
etc., is different.

Instead of repair install, I would have changed all of the drivers to the
standard Windows XP drivers and then installed the new board. Or started up
in Safe Mode and deleted all of the devices that will be different in the
Device Manager and then installed the new board.

But since you have already done a repair install you probably will have to
perform a clean installation.

Eric,
PC Buyer Beware!
http://www.pcbuyerbeware.co.uk/

"Gerald Fay" wrote:

> Moving from an Asus Intel based MB to an Asus AMD board (939 with dual
> core). Tried moving the hard drive to the new system and doing a repair
> install. All seems to go well until reboot time with the Install CD out then
> a quick blue screen, which I cannot read.
>
> Suggestions besides a complete reinstall?
>
> Thanks
>
>
>

Posted by Gerald Fay on December 6th, 2005


Fortunately, I've been "around the block" with computer systems, and in fact
did not try the repair on the original disk, but an Acronis Image.

Any suggestions on which device drivers to change?
IDE ?
USB ?
Video ?
Also do you think this will work going from Intel to AMD?

Also in my reading I've seen some indications that if before the motherboard
change you set the IDE driver back to the Standard, repair install may then
work. Is this true?

Thanks

"Eric" <Eric@discussions.microsoft.com> wrote in message
news:1EBF1036-0B54-4130-A315-9BE42F6541DE@microsoft.com...
> Windows XP doesn't take well to changing the motherboard because the
> chipset,
> etc., is different.
>
> Instead of repair install, I would have changed all of the drivers to the
> standard Windows XP drivers and then installed the new board. Or started
> up
> in Safe Mode and deleted all of the devices that will be different in the
> Device Manager and then installed the new board.
>
> But since you have already done a repair install you probably will have to
> perform a clean installation.
>
> Eric,
> PC Buyer Beware!
> http://www.pcbuyerbeware.co.uk/
>
> "Gerald Fay" wrote:
>
>> Moving from an Asus Intel based MB to an Asus AMD board (939 with dual
>> core). Tried moving the hard drive to the new system and doing a repair
>> install. All seems to go well until reboot time with the Install CD out
>> then
>> a quick blue screen, which I cannot read.
>>
>> Suggestions besides a complete reinstall?
>>
>> Thanks
>>
>>
>>



Posted by Steve N. on December 6th, 2005


Gerald Fay wrote:

> Moving from an Asus Intel based MB to an Asus AMD board (939 with dual
> core). Tried moving the hard drive to the new system and doing a repair
> install. All seems to go well until reboot time with the Install CD out then
> a quick blue screen, which I cannot read.
>
> Suggestions besides a complete reinstall?
>
> Thanks
>
>


Boot into Safe Mode, Right click My Copmuter, Properties, Advanced,
Startup and Recovery, uncheck Automatically restart. Reboot, the blues
screen will persist, write down the entire error and post it.

Steve N.

Posted by Steve N. on December 6th, 2005


Eric wrote:

> Windows XP doesn't take well to changing the motherboard because the chipset,
> etc., is different.
>
> Instead of repair install, I would have changed all of the drivers to the
> standard Windows XP drivers and then installed the new board. Or started up
> in Safe Mode and deleted all of the devices that will be different in the
> Device Manager and then installed the new board.
>
> But since you have already done a repair install you probably will have to
> perform a clean installation.
>
> Eric,
> PC Buyer Beware!
> http://www.pcbuyerbeware.co.uk/


A repair install is the way to update the OS for a new motherboard. What
you would've done was wasted a lot of time and still had to do a repair
install when it wa all over.

There's no need for a clean install a this point. It's most likely a
driver or hardware issue and once the BSOD error is determined then a
course of action can be decided.

Steve N.


>
> "Gerald Fay" wrote:
>
>
>>Moving from an Asus Intel based MB to an Asus AMD board (939 with dual
>>core). Tried moving the hard drive to the new system and doing a repair
>>install. All seems to go well until reboot time with the Install CD out then
>>a quick blue screen, which I cannot read.
>>
>>Suggestions besides a complete reinstall?
>>
>>Thanks
>>
>>
>>

Posted by Gerald Fay on December 8th, 2005


It is 0x0000007E (pandora's box)
Any suggestions?


"Steve N." <Steve_N@nunya.biz.nes> wrote in message
news:OHfvcrq%23FHA.2156@TK2MSFTNGP10.phx.gbl...
> Eric wrote:
>
>> Windows XP doesn't take well to changing the motherboard because the
>> chipset, etc., is different.
>>
>> Instead of repair install, I would have changed all of the drivers to the
>> standard Windows XP drivers and then installed the new board. Or started
>> up in Safe Mode and deleted all of the devices that will be different in
>> the Device Manager and then installed the new board.
>>
>> But since you have already done a repair install you probably will have
>> to perform a clean installation.
>>
>> Eric,
>> PC Buyer Beware!
>> http://www.pcbuyerbeware.co.uk/

>
> A repair install is the way to update the OS for a new motherboard. What
> you would've done was wasted a lot of time and still had to do a repair
> install when it wa all over.
>
> There's no need for a clean install a this point. It's most likely a
> driver or hardware issue and once the BSOD error is determined then a
> course of action can be decided.
>
> Steve N.
>
>
>>
>> "Gerald Fay" wrote:
>>
>>
>>>Moving from an Asus Intel based MB to an Asus AMD board (939 with dual
>>>core). Tried moving the hard drive to the new system and doing a repair
>>>install. All seems to go well until reboot time with the Install CD out
>>>then a quick blue screen, which I cannot read.
>>>
>>>Suggestions besides a complete reinstall?
>>>
>>>Thanks
>>>
>>>



Posted by Mike Hall \(MS-MVP\) on December 8th, 2005


A Google search of that error code reveals..

http://support.microsoft.com/?kbid=330182&sd=RMVP

--
Mike Hall
MVP - Windows Shell/User


"Gerald Fay" <gejfay@comcast.net> wrote in message
news:Ozl4%23M7%23FHA.2324@TK2MSFTNGP11.phx.gbl...
> It is 0x0000007E (pandora's box)
> Any suggestions?
>
>
> "Steve N." <Steve_N@nunya.biz.nes> wrote in message
> news:OHfvcrq%23FHA.2156@TK2MSFTNGP10.phx.gbl...
>> Eric wrote:
>>
>>> Windows XP doesn't take well to changing the motherboard because the
>>> chipset, etc., is different.
>>>
>>> Instead of repair install, I would have changed all of the drivers to
>>> the standard Windows XP drivers and then installed the new board. Or
>>> started up in Safe Mode and deleted all of the devices that will be
>>> different in the Device Manager and then installed the new board.
>>>
>>> But since you have already done a repair install you probably will have
>>> to perform a clean installation.
>>>
>>> Eric,
>>> PC Buyer Beware!
>>> http://www.pcbuyerbeware.co.uk/

>>
>> A repair install is the way to update the OS for a new motherboard. What
>> you would've done was wasted a lot of time and still had to do a repair
>> install when it wa all over.
>>
>> There's no need for a clean install a this point. It's most likely a
>> driver or hardware issue and once the BSOD error is determined then a
>> course of action can be decided.
>>
>> Steve N.
>>
>>
>>>
>>> "Gerald Fay" wrote:
>>>
>>>
>>>>Moving from an Asus Intel based MB to an Asus AMD board (939 with dual
>>>>core). Tried moving the hard drive to the new system and doing a repair
>>>>install. All seems to go well until reboot time with the Install CD out
>>>>then a quick blue screen, which I cannot read.
>>>>
>>>>Suggestions besides a complete reinstall?
>>>>
>>>>Thanks
>>>>
>>>>

>
>




Similar Posts