So I am trying to build a decent gaming rig on the cheap and here's what I went with:
AMD Phenom II X4 940 Black 3.0 GHZ Processor
Gigabyte MA790GP-UD4H motherboard
OCZ DDR2 PC6400 Ram (8 gigs in 4 sticks)
(2) ATI 4850's in X-Fire mode
640 Gig WD HD
etc etc
Anyways I throw all the components in and everything comes on but it won't post fully. It gives me 3 long, 1 short and then a pause before repeating 3 long and 1 short ad infinitum with a pause in between each sequence.
Anyways I am digging around and 1 review of the motherboard says it has to use 1066+ mhz for the AMD2+ cpu's but Gigabyte's main page has no such limitation listed except it says that if you use 1066 mhz or better than you're limited to 1 stick per channel.
So... my question is:
Is this post code even at all related to the ram, or what. I can find zero documentation ANYWHERE on that particular post code at all. I'm at a loss, trying to find out what's going on so I know what I should do. Gigabyte itself hasn't answered my question (And of course their tech support is all online so...) yet and I'm just... chomping at the bit here.
I would try with just 2 sticks of RAM and only 1 video card. Aren't you supposed to start off with only 1 card until you install your drivers and enable SLI/CROSSFIRE anyways?
Like you, I couldn't find that post beep sequence for either Award or Phoenix BIOS.
Your manual says 1 long - 3 short is a keyboard error, but no reference to 3 long - 1 short except to say that continuous long beeps = graphics card not inserted properly, and continuous short beeps mean power error. Hmmmm. 2 problems alternating? vid cards causing an error that looks like power error?
Anyhow, have you tried booting up with one stick of memory? one per channel?
Message edited by Twoboxer on 06-19-2009 at 02:25:32 AM
I have tried one stick in each channel as it's dual channel memory, I have tried with one video card, and even using just onboard video card without any video card in the machine at all.
It always results in the same thing with that horrible post code.
I did try researching around for similar issues on the forums which is what prompted me to try the ram in such a funky setup.
I have also tried two sticks in bank 1, and 2 sticks in bank 2. I suppose I could try with zero ram in it at all and see if it changes up... right now I am highly suspecting it might just be a DOA motherboard, or CPU, which I really hope isn't the case.
[quote]
1-7 Configuring an ATI CrossFireXTM System
To enable CrossFireXTM technology, you need two graphics cards that support ATI CrossFireTM technology.
Before You Begin--
A. Power Requirements:
Use a power supply that is able to provide sufficient power to fully support an CrossFireX configuration and other components in your system. We recommend a power supply that provides at least 20A 12V current. The exact power requirements depend on your overall system configurations.
B. Supported Operating Systems:
Windows Vista and Windows XP.
C. BIOS Settings:
Before configuring your system for CrossFireX, make sure to set Init Display First under Advanced BIOS Features in BIOS Setup to PEG first. (Start your system with a single PCIe x16 graphics card and then go to BIOS Setup to set Init Display First to PEG. Then install the second graphics card to enable CrossFire.)
[\quote]
Ok, I've done that. I've pulled video cards completely from the system. OS and Bios is pointless because I cannot get into the bios to set anything and I cannot get past bios to install an OS, this is a clean system with nothing on it. Hard drive has never even been formatted.
I will be putting Vista Ultimate 64 onto it if I can ever get it to start.
The power supply is a Corsair TW750w power supply, with more than enough power on the +12v rails to supply both video cards and everything else in the system.
I have installed all three current MS OSs (XpProx86/64, VistaUltx86/64, and Win7βRC1x86/64) from empty partitions on a system with a pair of ATI GPUs in the slots, and have done it with and without the Xfire bridge installed (took a try to learn that, with the bridge in, it will default to Xfire - which I don't want, as I run four monitors...); what I have not done is installed it to an AMD based system, as, well, homey don' play dat!
I have installed all three current MS OSs (XpProx86/64, VistaUltx86/64, and Win7βRC1x86/64) from empty partitions on a system with a pair of ATI GPUs in the slots, and have done it with and without the Xfire bridge installed (took a try to learn that, with the bridge in, it will default to Xfire - which I don't want, as I run four monitors...); what I have not done is installed it to an AMD based system, as, well, homey don' play dat!
Not sure what that has to do with my issue... but.. thanks?
I'd add that, much as I abhor and preach about 'useless' RMAs, I think this one may be a GB screw-up - I believe I've seen four or five posts in the last few days, all with strange, POST-oriented problems; I were you, I'd try to get an RMA for another (by which I mean 'different') board... May be time for the designers to attempt Rev2!
Yeah it's a PS2 Keyboard, USB mouse, but I've tried booting it with zero USB devices connected too...
Anyways, Bilbat, this obviously isn't an OS issue, this is a hardware issue. It can't be an OS issue since it's never been booted up far enough to put an OS on it.
I am really hoping it's like, a jumper was thrown the wrong way or something at the factory but... Gigabyte isn't even responding to my e-mail yet.
I, too, am thinking hardware - like you say - not yet to the point where OS could be involved! What I was trying to point out is, the GA-MA790GP-UD4H design itself may be the problem... I've re-read the manual to check hardware possibilities - the only conceivable thing I can find is that you received a previously RMAd MOBO, and someone left on the ClearCMOS jumper. Otherwise, if you've reseated the CPU, and 'wiggled' all your power connections, it looks good - and should be! I checked, and the 'shipped' F2 BIOS supports the 'deneb' processor steppings, and having tried it with one RAM stick (and different single sticks) should eliminate that (and the RAM should default to 800) - we're running out of diagnostics... Added to the grief is an 'unknown' beep code - which is inexcuseable, in and of itself! And, as I pointed out - you're not the only one with wierd, boot-related troubles...