Help please..hard drive issue

ejoech

Member
Dec 12, 2000
166
0
0
My motherboard fried a couple of days ago...ESD I believe. Anyway, I replaced the motherboard, set everything back up, reset the CMOS..go to boot up..Everything runs smoothly until I see the Windows XP screen loading...then I hear a couple of beeps, no more display, and a couple more beeps..

I turn it off and turn it back on again - no display to the monitor. Reset the CMOS and it POSTS but once again resets after the windows XP logo.

I put in an old HD and it booted into WinME fine.

Ideas? PLEASE help !!

Thank you very much!


EDIT: Sorry, I'm an idiot. I didn't see the newish "technical support forum" at the bottom. Please move - sorry :/
 

membreya

Member
Jan 17, 2005
56
0
0
Main thing that I can think of is that Windows XP is very hardware specific with its installs.

ie you can't just go and change the motherboard and expect it to work, especially if the chipset has changed...

What type of motherboard did you replace the old one with? was it the same?

Generally speaking though Windows will give you a set amount of time to reinstall/reactivate Windows or it will simply give a stop error.

Have you tried doing a clean install of XP on the old harddrive you have?
 

Blazer

Golden Member
Nov 5, 1999
1,051
0
0
windows can cause that problem,i know first hand.

format and reinstall /a clean install will run faster
 

ejoech

Member
Dec 12, 2000
166
0
0
Thanks for the quick replies. I agree that Windows XP can cause resets like this, however I did not think it could cause the system to not POST , requiring resetting the CMOS?

That's why I didn't try repairing/clean installing XP earlier.

I did not replace the motherboard with the same one - I wish I could give you model numbers but I'm ready for bed and they're next door in my office :)

I believe the old one was a biostar, new one is definitely MSI..661 I believe.

Thanks for the help..it's driving me crazy(I've had about 18 other problems with this PC before this..I've made a lot of progress. First I thought it was the CPU, nope, turns out to be the motherboard...at least it seems to be.)