| Author |
Topic: Help needed with fresh XP install on new motherboard |
Mitch Drumm
From:
Frostbite Falls, hard by Veronica Lake
|
Posted 18 Nov 2007 8:34 pm |
|
I am at my wit's end.
Had an Asus P5B motherboard failure 3 or 4 days ago. Purchased an Intel DG965RY to replace it. Note that these boards have the same chipset.
Installed the new board and was able to get to my desktop, but figured I had best do a clean install.
I have a XP home edition upgrade disc and a XP service pack 1 disc. Both are legit. I figured I would start with the upgrade disc and would probably be asked to insert the SP 1 disc. I have the product key for the home edition upgrade dic.
About 3 minutes into the install, I get a blue screen Stop Error Stop 0x0000007E, also listing 4 other parameters, pci.sys, and a datestamp. Setup will not proceed.
Talked to MS techs for over an hour. They accepted my product key as valid. Tech had me try each memory stick separately. Also disconnect all peripherals. Also try F7 early in the install process (not F6).
None of the above worked. Googling and searching at MS will turn up info on stop errors, some info on this particular error, MS Knowledge Base article 330182, etc. None of that has helped yet. The implication of my research is that Stop Errors are often hardware or driver-related.
System is deliberately minimal at this point: 2
Corsair 1 gig memory sticks, 2 HDs, 1 DVD burner, keyboard, mouse, onboard sound and video. Nothing in the slots. Processor is Intel Core 2 Duo 6600.
I have tried original bios and drivers on the Intel board CD and have also updated to the latest drivers and bios. It makes no difference--still get the same error.
Of course, I can still use the existing system: C drive as installed on the Asus P5B, now sitting on an Intel DG965RY board. Things seem to be working pretty good, probably because of identical chipsets. No yellow bangs in Device Manager. The "found new hardware" wizard is no longer hounding me.
I have always been advised to do a clean install for any new mobo, and thus am concerned about the longer term effects of not reinstalling.
I don't have a bunch of spare parts that I can swap in until the problem disappears.
For all I know, if I went downtown and bought Vista, I couldn't install it.
Two questions:
Is there a floppy disc-based method that might get around this or do you have any other suggestions?
Your best guess on what happens if I do nothing? Will I ever be able to install a MS OS on this hardware? |
|
|
 |
Jack Stoner
From:
Kansas City, MO
|
Posted 19 Nov 2007 3:21 am
|
|
Usually, if you run an install from an "upgrade" CD it will ask for a "qualified" version (e.g. a Windows 98 full version CD) that is loaded on a CD drive that it checks before continuing.
The pci.sys error would suggest a missing chipset driver, but chipset drivers are not installed until after the OS is installed... Since you are able to run the system, check for an Intel chipset driver and install that, then try the install and see what happens. The Intel chipset drivers define what is on or attached to the motherboard.
Normally, on motherboards that require chipset drivers, the install sequence is (1) install OS (2) Install chipset drivers (3) install device drivers. |
|
|
|
Mitch Drumm
From:
Frostbite Falls, hard by Veronica Lake
|
Posted 19 Nov 2007 4:25 am
|
|
Jack:
A few more details.
Since my original post, research at Intel tells me that the pci.sys error is acknowledged with this board and can occur when an install is attempted WITHOUT SP2. It may be that PCI Express requires SP2 to install. Googling implies there are other possibilities as well.
I do NOT have an SP2 disc per se. My SP 2 is in download form from MS site (file name like KB935835ENU.exe)
Intel site recommends using a slipstream disc, combining SP1 and SP2, which is what I used before calling MS yesterday. I had used the same disc successfully last winter on the Asus board.
My retail discs are XP SP1 full and XP home edition upgrade, which i think is also SP 1 only. I have the product key for the latter, but no longer for the former. I cannot recall which of my two retail discs i used for the slipstream. I assume it was the upgrade, figuring I would be asked for SP1 full during installation and it would be accepted even though i did not have product key for it--only for home upgrade.
All my web research confirms that an upgrade disc is perfectly OK for a slipstream disc.
Since i don't have the product key for SP1 full, there is no point in starting with it.
The slipstream attempt yesterday did ask for a legit disk. I honestly cannot recall which disk i inserted (full or upgrade), but I got a blue screen saying the disc could not be read or may not be valid. At that point, I called microsoft. I would assume i inserted the full retail XP SP1 disc.
My install attempts on the phone with microsoft all began with the home edition upgrade as the tech was suspicious of any slipstreamed disc. That was fine with me. I only attempted to install by slipstream once. All other attempts have begun with the upgrade disc, hoping to be asked for SP1 full. Each and every attempt has been met with the 7E stop error/pci.sys blue screen.
The tech apparently was not aware of Intel's acknowledgment of problems when an SP1 disc is used.
I can't explain why my SP1/SP2 slipstream did not work on this board when it did work last winter on the Asus board.
I can't confirm that Intel's comment about the pci.sys error and lack of SP2 means anything in my case, particularly since there are hundreds of net posts about general 7E blue screens.
It is speculation that a MS XP SP 2 disc, Vista, or anything else would work at this point.
Any other suggestions appreciated. I am now making a fresh slipstream disc in case that is the source of the problem.
My other ideas are turning off anything related to PCI in the bios before install or trying a repair install of the existing C partition.
What has been your experience when a user does NOT reinstall following a new mobo? I may be stuck with that.
[/quote] |
|
|
|
Jack Stoner
From:
Kansas City, MO
|
Posted 19 Nov 2007 5:20 am
|
|
If the MB is identical there are no problems. The issues with a different motherboard is the Operating System and the fact it's "setup" for a certain MB hardware configuration and if it's different usually a reinstall or at least in the case of XP a "repair" is needed. But, in your case since it appears to be working - "if it ain't broke don't fix it" would seem to apply.
With all the problems, if there is a problem with the new board, the XP "Repair" may work and all you need. Have you considered the "Repair" option, if needed. This doesn't fix the install problems but since SP2 did change a lot of things maybe that is what is needed. |
|
|
|
Mitch Drumm
From:
Frostbite Falls, hard by Veronica Lake
|
Posted 19 Nov 2007 7:56 pm
|
|
Jack:
After dozens of hours, I finally resolved this.
According to the Intel site, Windows XP SP 1 may balk during an install attempt on the DG965RY board. You have to dig pretty deep into the documentation to discover that.
The Microsoft tech was not aware of that and had me repeatedly try with XP Home Edition, which is SP 1.
Intel says to use SP 2 directly or a slipstream disc, combining SP 1 and SP 2. I had originally tried a slipstream disc and failed, before calling MS.
I can only assume that my slipstream disc went bad or had some peculiarity that made the install fail, even though I had used that very disc on the Asus board install last winter.
I burned a new slipstream disc and the install went through.
If you ever have to make a slipstream disc, try "Autostreamer" to automate the process of making the slipstream ISO. It saved me in this case. It is available on the net as a free download. |
|
|
|
Jack Stoner
From:
Kansas City, MO
|
Posted 20 Nov 2007 3:24 am
|
|
I have a splipstreamed copy of XP Pro with SP2, but fortunately I haven't had to use it. My XP machine has been relegated to my "backup and test" PC. My main PC has Vista installed on it.
But it's interesting that a motherboard would require that version of XP. I've been dealing with vendor boards that are proprietary (e.g. Dell) so I haven't come up with this issue. But, I'll keep it in mind. Thanks for the tip. |
|
|
|
