Sign in with
Sign up | Sign in
Your question

Installed new motherboard, now cannot even boot from CD to format HD

Last response: in Systems
Share
a b B Homebuilt system
October 26, 2009 1:46:34 AM

So I finally replaced my crappy Intel board with an Asus P5Q3. I know you usually have to re-install Windows with a new board (I'm using Vista Ultimate 64-bit), but figured I'd boot it up first and see, and if I had to, I could always just boot from the Windows install CD and format the hard drive from there.

Of course, once I got it assembled, not only will Windows not work, it won't even let me boot from the CD. It will get part way and then go to a BSOD with "Stop Error 0x0000007e" displayed. Same thing happens when I try to boot from the HDD into Safe Mode, although at least there it looks like it tried to install a few drivers first.

Is there ANY way I could conceivably solve this without having to 1) Disassemble the system, 2) reassemble with the old motherboard, 3) format the hard drive, 4) disassemble the system again, and 5) reassemble again with the new board. I REALLY would like to avoid doing that, on account of it'll probably take an entire fricking day.
October 26, 2009 10:05:47 AM

Whats ur pc specs? I have to know them to se if they are compable with the motherboard. Here is what I can say for now:

The BSOD usually happens when there is a problem with an hardware or it isnt comptable.
So juding from the BSOD, something isnt comptable.

Some questions I would like to ask:
Does the BSOD come before teh BIOS comes up?
Do you even have a chance to get into the BIOS?

Send me the specs and HOPEFULLY everything will be solved.
m
0
l
a b B Homebuilt system
October 26, 2009 10:49:41 AM

Enter the BIOS and make sure the boot order is to DVD/CD first, HDD second. (Vista install is on a DVD, not a CD) Disable all other boot options for now.
That should let you boot to your install DVD.
If the board is quite different from what you had, it is quite possible that Windows will not boot at all.
If all this is set correctly, remove all but 1 stick of memory and try that. Make certain the memory is running at the correct voltage and settings before going any farther.
m
0
l
Related resources
October 26, 2009 12:50:30 PM

Does the BSOD come before teh BIOS comes up?

i didn't even think it was possible for a BSOD to appear before post?

is it a SATA or IDE hard drive your using? do you get to the point of where you can select your hard drive in windows setup?
m
0
l
October 26, 2009 1:09:30 PM

You can also try running memtest 86+...it boots straight off the cd and will test your memory for errors.
jit is correct on the ram voltage...most new boards have the voltage at 1.8volts alot of high end ram is ment to run at 2.1volts. So you have to manually go in and set it.
Always check the ram specs before changing anything.
Hope this helps....JQ
m
0
l
a b B Homebuilt system
October 26, 2009 3:51:22 PM

I MAY have solved this, but we'll see. Machine was actually booting past BIOS and even sometimes (about 1 time out of 10) partway into Vista in Safe Mode, where it would attempt to auto-install about 30-40 motherboard-related drivers and then crash. But it wouldn't let me boot from CD no matter what I said in the BIOS -- it would still crash.

Anyway, after several cycles of trying to boot into safe mode, it started getting through 4 or 5 drivers before crashing, and eventually apparently succeeded in installing enough of them that it became stable enough to boot from CD and let me format the drive. Vista seemed to install OK and hasn't crashed yet. So I'm crossing my fingers. This has to be one of the weirder situations I've run into while trying to rebuild a system.


On the off chance that it sheds any light on the problem, specs are:

CPU: Intel Q9550 2.83 gHz (not oc'ed yet)
mobo: Asus P5Q3
RAM: 4x2GB Patriot Viper DDR3 7-7-7-20 (requires 1.7V)
HDD: Velociraptor 300GB (SATA, obviously)
GPU: Radeon HD 4870
PSU: NCTZ 850W


m
0
l
a b B Homebuilt system
October 26, 2009 7:48:56 PM

Never mind; the motherboard was DOA.

Once active, it was having other problems like the onboard ethernet showing up but failing to recognize there was a cable plugged in, and eventually it started having power issues.

The mfr said only thing I could do was return it, so I guess it's shop for another board and wait another week, eh.
m
0
l
!