new system, strange actions...

[minime10203]

so i just finished my first build. specs are as follow:

conroe core 2 duo 2.4, e6600
western digital raptor 10k rpm sata hdd
asus p5b deluxe mobo
700w ocz gamextreme psu
2gb corsair xms2, ddr2 800 (2, 1 gig sticks)
light on 20x dvdrw sata
evga geforce 8800gts 640mb pci-e (superclocked edition)

as far as im aware, all these parts are compatible.

now onto the problems.

A) sometimes on the initial startup, i get no signal. no startup beeps, no video, no nothing. i thought this may be a dying battery (i say dying and not dead becuase sometimes it does startup) i have tried this with juse bare bones components (psu, 1g ram, video car). i have even tried it without a videocard just to see, and got no beep errors. just the sound of my fans running.(NOTE: my case fans, processor fan, videocard fan, and cdrom all work. i just get no beeps or picture) whenever this problem occures, i have to hold the power button in , in order to turn it off (usually like 5-10 seconds, almost like it doesnt have enough strength to do the command right away) during problem B however, 1 simple press shuts it down (coincidentally, during problem B, the computer also boots up to the post , as if it has plenty of power. coincidence?)

B) in this situation, the computer actually started. i recieved the splash screen with the asus logo, the single all systems go beep, then 3 more beeps at post followed by the following errors:

chassis intrusion, fatal error. system halted (all 1 error. i know this is caused when the connector in my chassis intrusion switch is triggered, and i plan to disable the intrusion detection once i access cmos.

over clocking failed! this ones a new one for me, especially when i havent even overlocked it.

CMOS bad checksum this im not 100% sure about. im guessing either something to do with improperly configured cmos settings, or maybe relating back to my battery not having the juice to run it.

then there was another error, which i forgot exactly, something along the similiar lines of the others, relating to my cmos configuration, and suggesting that i manually re-configure them.


my hdd, dvd, and ram are being detected (or so says the bios, it reports me as having 1 or 2g of ram) yet either problem A or B persists. it seems if i let it set for long enough, i get problem B. otherwise i get problem A.

i have already tried reseting the cmos settigns via jumper, but have yet to try replacing the battery with a new one. i suspect im getting the overclock errors and maybe even the cmos errors becuase i reset the cmos then never manually configured the settings (becuase i ran into problem A) so its thinking im using custom settings that were never defined.

the chassis intrustion error i dont understand. i have my cable plugged properly into the chassis intrustion plugs, so its not being tripped at all, yet i still get the error. it is a 3 pin plug, and only pins 2/3 get stuck by the cable. do i need to cap pin 1 when i plug 2/3 in? not a huge deal since i can disable it anyway, just curious.

this IS a fresh install with never before used parts into a never before used case (thermaltake armor). no previous os has been installed (hell i havent even gotten far enough to install one yet)
apologize for the length of this. iv spent a decent chunk of change so far, so id rather not spend more to have a pro install if possible, and thanks for the views.

also, it is less of an annoyance then the others, but when i press my power button, the computer immediatly starts,(all fans and lights kick on) then stops (all fans and lights shut down) then starts back up and continues booting. iv heard this refered to as a ghost boot, but i dont know what causes it. i have a sneaking suspicion that all my problems may be tied into each other somehow.

[liambl]

Try replacing the cmos battery, and make sure to reset the cmos afterwards.

[minime10203]

ok, ill try that after i get home today. im assuming any store that sells watches or watch batteries will have one.

then after i replace it i just re-do the jumper on the mobo to reset the cmos and load into the cmos to manually configure if all boots up.

[glc]

http://forum.pcmech.com/showthread.php?t=132409