'CMOS ERROR' - How to fix without display?

Hi, I've just put together a custom rig using an Asus Crosshair 3 Formula mobo, I'm using a Sapphire Vapor-X ATI 4890 2GB. When started up there is no video output (screen stays blank) but the LCD starts going through tests.

Initially I was getting an 'INNIT ROM' error - someone advised a CMOS reset and so after wiping the CMOS I get a 'CMOS ERR' message on the LCD. I can't see anything because for some reason there is no video output, and even after resetting the CMOS by using the CLR_CMOS button I get the same 'CMOS ERR' message.

I am using 4GB of DDR3, already tried one stick and in different slots.

Full specs:

Corsair HX 1000 PSU
AMD Phenom 2 X4 965 Black Edition
Sapphire Vapor-X ATI 4890 HD 2GB
Corsair Dominator DDR3 4GB
and it's hooked up to an optical drive, two SATA drives and a cosmos S.

I'm not sure whether no video output is a seperate problem or it will resolve itself once the mobo passes all of it's initial tests.

Help much appreciated!!

Try building outside the case on a piece of cardboard with only beeper, power, mobo and cpu. Listen for beeps. Keep adding components and listen for beeps.

"New build won't boot" checklist

http://www.tomshardware.com/forum/ [...] -checklist

When building a new system, always CLR_CMOS. To enter BIOS on your particular board, hold the 'DEL' key. If you can't get there after 30 seconds, lets do the rundown:

First, ensure all power connectors are fully seated (including both EATXPWR 24 pin and EATX12V 8 pin)

Second, install the DIMMs properly (see the manual) and see if they are in the QVL list at: http://usa.asus.com/product.aspx?P_ID=2Y4dQFaJ6gPN18cQ

Third, ensure your videocard is in the first x16 PCIe slot (labeled PCIEX16_1, properly seated, and both PCIe power are connected)

Fourth, check the CLRTC_SW jumper on the mobo. In order to use the CLR_CMOS button on the I/O backplane the switch must have pins 1&2 shorted otherwise the CLR_CMOS button does not function.

Only have the proc, memory, and video installed at this point, that will at least ensure the least possible points of failure.

When you boot the system, are there any beeps? See the manual for an explanation (page 2-43)

Hope this helps!

You hit the tack on the head with a slegehammer! But for the neophyte, gotta start somewhere, lucky for him he came here and not somewhere else. I'm new to these forums and I've noticed some good info being traded.