new motherboard et al

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I am using the microsoft recommended method for reinstalling windows after
installing new motherboard. It works fine until it comes time to restat
Windows after the repair and then I get a stop 0X0000007E error. after
researching I think its because I have switched from an intel cpu to AMD
(Athelon 64 x2) Shoudl i go ahead and do a parallel installation of windows
from the CD and if so what do I do with the old installation, anything I need
to save or should I delete it if the new one works OK??

Thanks
 
I doubt that microsoft recommended that nonsence for a new MB.
For any new MB,install xp cd,boot to xp cd,select install xp,new copy,delete
the partition (xp),create one,then let xp format and do a clean install.
Even if you replaced a vrd with the same chipset,xp wouldnt work with a
"repair"......
 
Sorry I wasn't clear..I am using the same drives etc. the info came from KB
824125 I am most concerned with the effect of doing a parallel or seperate
install on the same drive and how to reconcile them...it is not a blank drive
so I don't understand why deleting a partition would not lose some data
Thanks
 
If the old mobo is still available, boot the computer with a minimal
complement (sit it on an insulatinfg surface such as a wooden board, no need
to put everything in the case)

Now go to Control Panel>System >Device Manager and change the IDE driver to
"Standard PCI IDE Controller."

The disk should now boot on the new mobo. In most cases, anyway.

Unfortunately despite experimentation with WinPE, etc I don't know of any
way of doing this unless you can get the OS itself to boot on something.
 
Andrew E. said:
I doubt that microsoft recommended that nonsence for a new MB.
For any new MB,install xp cd,boot to xp cd,select install xp,new copy,delete
the partition (xp),create one,then let xp format and do a clean install.
Even if you replaced a vrd with the same chipset,xp wouldnt work with a
"repair"......
Click to expand...

Andrew, you are totally out to lunch as usual. Please go away and
stay there.

Ron Martell Duncan B.C. Canada
--
Microsoft MVP (1997 - 2006)
On-Line Help Computer Service
http://onlinehelp.bc.ca
Syberfix Remote Computer Repair

"Anyone who thinks that they are too small to make a difference
has never been in bed with a mosquito."
 
pmmdoc said:
I am using the microsoft recommended method for reinstalling windows after
installing new motherboard. It works fine until it comes time to restat
Windows after the repair and then I get a stop 0X0000007E error. after
researching I think its because I have switched from an intel cpu to AMD
(Athelon 64 x2) Shoudl i go ahead and do a parallel installation of windows
from the CD and if so what do I do with the old installation, anything I need
to save or should I delete it if the new one works OK??

Thanks
Click to expand...

Can you provide the full details, including all 4 parameters and any
file or module names mentioned for the STOP 0X0000007E?

That may provide some clues as to the underlying cause.

Can you boot into Safe Mode okay? If so, and you have the new drivers
for your new motherboard on CD, try installing the drives while
running in Safe Mode and then rebooting.

Good luck

Ron Martell Duncan B.C. Canada
--
Microsoft MVP (1997 - 2006)
On-Line Help Computer Service
http://onlinehelp.bc.ca
Syberfix Remote Computer Repair

"Anyone who thinks that they are too small to make a difference
has never been in bed with a mosquito."
 
I am not sure taht we are experiencing teh same thing>

My situation:

I have an older machine running an AMD 1600 chip. I have in the recent past
upgraded the HDD to a 250GB drive from an older 40GB Drive. I just recently
got a newer 2.8Ghz Intel system and I wanted to move my crive from one
machine to the other so that I would not have to go through the process of
re-installing. I ran into a similar problem except my bluescreen at boot was
0X0000007B.

I found this article on Microsofts website
http://support.microsoft.com/kb/314082/
This worked liek a champ. Obviously I have to reinstall drivers and suck but
this article did help me get my system up and running.

I hope this helps!
 
Back
Top