Can't get into windows with this motherboard

[overclockingoodness]

I have a Epox EP-4PDA5+ that I recently purchased. Please note my sys. specs:

P4 2.4GHz "C"
1GB (512x2) Corsair PC3200XL
Radeon 9800 Pro
Western Digital WD800 8MB cache Hard Drive
Plextor 712A DVD Drive
OCZ 520W Powerstream PSU


Now my problem: I can't easily boot with the above stated specifications and I can install windows, but as soon as the windows XP start-up screen appears, my hard drive spins down and my system restarts. I have tested all components and they all work fine with my two other machines. Besides, if I plug the above stated things on my Asus P4C800-E Deluxe motherboard, everything is good to go.

Can someone tell me why I can't get into windows with the Epox motherboard? Is the hard drive not getting enough power?

Thx.

 

[overclockingoodness]

*Bump*

 

[chocoruacal]

Strange. Installing Windows is pretty intensive...usually if there's a hardware problem it shows up there. My suggestion would be to boot into Safe Mode and see if you can work from there. If that doesn't work, you might be stuck RMAing the board.

 

[wetcat007]

Do some troubleshooting, did it work with a different motherboard? Your PSU shouldnt be the problem...

 

[overclockingoodness]

Yes, everything works with other systems. I did all the troubleshooting that I could think of so I don't know what the problem could be.

 

[NesuD]

sounds like something going on with the Ram. have you tried it with just 1 stick of ram? maybe try ram in different slots?

 

[mechBgon]

If the hard drive is on its own IDE cable, then jumper it as Single Drive if it isn't already... but usually that solves slow-POST issues, not boot-up problems.

Also, is this a brand-new mobo or used? Tried the other IDE channel yet? Maybe it's faulty.

 

[bobsmith1492]

I returned a hard drive 'cause it was doing that - a raptor, actually. I should have kept it... it turns out I didn't have the AGP/PCI locked and was overclocking the FSB to like 200.... NOT a good idea. I don't know if you're overclocking any, but try setting the AGP to 66MHz and see if it helps.

 

[bobsmith1492]

Then again, it was a WD serial drive, and I locked the AGP AND replaced with a Maxtor IDE drive all at the same time, so there are too many variables to say for sure. Perhaps it's just an issue with WDs? Also I've heard serial hdd interfaces have problems with bus speed changes, so who knows... Try the lock though.

 

[mechBgon]

I just noticed that the system also has Corsair 3200XL memory. Make sure it's getting a decent amount of voltage, I'd start with 2.7 volts if it were me.

 

[overclockingoodness]

Yep. I have done all of the things you guys kindly suggested. This is a brand new motherboard.


Now I am having another problem. I am getting the same error with my Asus P4C800-E Deluxe motherboard and it was working fine before I disconnected it.

I was first using an image of the hard drive I made an image with Norton Ghost 2003 with all the applications and stuff. And now I am trying to do a clean install with with Windows XP Pro original disk and the problem is that when I put the CD in and when it is copying files to the hard drive, I get "error copying file". I know the CD is not scratched because I have used this CD to install OS on my computers.

I am all confused as to what I should do. Please help.

 

[mechBgon]

Could it be a bad or poorly-seated IDE cable? Tried a fresh 80-wire flat IDE cable yet as a fact-finding step? That wouldn't take too long to test, at least. Memtest86 is another idea, you could run it overnight.

 

[overclockingoodness]

Don't know but I will definitely give it a try. After all, I have got nothing to lose.

 

[CP5670]

I had similar problems a few months ago (windows installed fine but was rebooting the computer while loading) and it turned out to be a bad memory stick. I guess it could be any of a number of things though.

 

[salaku]

If you have already exhausted all the suggestions above try to install any other OS other than XP. any there OS. Just for testing and rule out any bad component issues try to install windows 2000 and see how it goes.