mikhsoj

I turned on my computer today to find that my computer wont boot past the asus logo.... basically, i think, that the raid drivers or raid controllers on the bios is all messed up.

when i boot, i see the asus ai life logo, then i hit delete, the screen says "entering bios" but then it freezes. the HDD led's are solid and the computer doesnt move past that.

so i tried to reset the cmos. nothing...
i tried unplugging all my hdd. nothing

any ideas?

__________________
This is my rig. Take a look if you wanna.

Arkle

Same thing just happened to me, but with a Gigabyte board. Read down the threads to see my previous post as well as others having the same issue. Is it so freaking difficult for motherboard manufacturers to make a CLEAR CMOS routine that actually works like it's supposed to? Apparently not.

I'm not sure I should be doling out advice to you as I ended up RMAing my own board, but here is a list of things to try:

1) power off and unplug your computer
2) press your power switch on the front once to ground and clear the capacitors
3) short appropriate jumpers to clear CMOS, wait with jumper in place for about 30 seconds or so.
4) remove or reposition jumper to normal operating position, plug your computer back in and try to boot

Does it work? If not, repeat steps 1-3 and continue below

5) remove CMOS battery (leaving jumper in place) Let everything sit for a couple of hours, replace battery, repeat step 4.

Does it work? If not, repeat steps 1-3 and 5, but wait for several more hours with the battery out. Replace battery and repeat step 4.

Working? If not, repeat steps 1-3 and 5, but this time leave your CMOS battery out overnight. Remove all of your ram modules and then reinsert only one of the modules (if you have two or more) in a slot not previously occupied if possible. If you only have one RAM module, remove it and switch to a different slot. Replace battery and repeat step 4.

Does it work? If not, there are those that condone leaving the CMOS battery out for 24-48 hrs at a time and then giving it another whirl, but one begins to believe there is such a thing as overkill (IMHO).

I'm actually going to start a new thread here on this subject as A LOT of folks like you and I are experiencing boot hangs due to unclearable/corrupted BIOS. This is ridiculous to have to put up with. Look, if board manufacturers are going to build products with rich overclocking features, they need to make a simple, reliable way to clear the CMOS by doing the same procedure for the same amount of time, EVERY time. Why should there be any variables at all?

Gigabyte touts a Virtual Dual Bios with their newest motherboards (including the one I had), that's supposed to recover when the normal BIOS hangs at boot. Cool idea! Oh, wait, except for the part it doesn't work.......

On my board I had adjusted settings just barely out of range of known stability before getting a boot hang and could not reset the damn Bios for the life of me. I know darn well I didn't fry any hardware because at settings I was using it would have been impossible. It's the stupid freaking BIOS and the inability to properly clear it on boot hang that's the culprit, over and over.

How many other boards are routinely RMA'd because of this 'feature'????

The Duke

First try a new or spare HDD cable, if notta then ....
This is where I love having a Knoppix Live CD.
Try booting from it with th HDDs installed... no go... try with out. Either way, if you get the Knoppix to work you have either a HDD, or controler or controler driver issue.

__________________

xdaseinx

Not the raid, as you should be able to get into bios if it were issues with raid. The raid controller does not initialize until after a post. Also, reseting cmos will most likely kill your array (I have the same board).

__________________