Weird booting problem on new system-

[Kyle]

Ok- I just set up a new system with a Asus P4s800D-E mobo and am having weird boot up problems.
Basically, the first time i turn it on after its been sitting for a while it goes to the windows screen and freezes. Reboot and it takes me to the windows screen and restarts itself. Turn off system and when it boots up it says "Over clock failure- F1 to enter setup F2 to resort to default settings". F1 and it reboots after leaving the bios and comes back with "Bios checksum error" and tries to reload the bios from a disk (I have let it reload it- nothing changes).
I then have to turn off the computer, restart it when it hits the checksum error, and then it loads in to windows and is rock stable.
Weird huh.

Any ideas what it is? I havent messed around with overclocking or anything, seems like just a buggy bios or somthin, but I have the latest bios.
Could it be a processor problem? I did buy it used, so thats a possibility I suppose.
Oh ya- used two different power supplies (380, 430 both antec).

Hard drive= Raptor
Thanks
-Kyle

 

[hoov]

Check your memory sticks make sure there seated good or try different slots

 

[Kyle]

thanks for the suggestion, I'll try moving the two sticks to the other two slots...im pretty sure they're seated well though.

 

[Kyle]

doesnt seem to be the problem..any other suggestions?

 

[WhiskeySour]

I have a simular problem with p4c800-E Deluxe, at POST the ASUS logo screen goes on, finds 3.0 GHZ P4, memory test ok, then goes to promise onboard controler, then shuts off. Using Crucial memory...ugh, completely new system, so kinda hard to track things down. I've got everything disconnected except monitor, and keyboard. Won't let me enter bios setup.

 

[Kyle]

ya, I think i'm going to mess around with the ram some more and see if i can track down what the problem is. It just seems weird how stable it is in windows but how its so finicky trying to boot.

 

[WhiskeySour]

Thought I'd do the same, removed one stick of 512MB Crucial ram, put the other stick in a different slot, then powered up.
Well, got a beep this time, then screen said summin 'bout "extreme over clocking" then mobo proceeded to start smoking. Guess the
mobo is the problem ;-)