Z68xp-ud3 post - no BIOS

wlhaskell

Honorable
Aug 14, 2013
2
0
10,510
I am attempting a new build based on a Gigabyte Z68XP-UD3 (rev 1.0) that was given to me by a coworker. I am using a new Intl Core i5-3570k processor and an Antec Eathwatts 500W power supply from an older build (Approximately 2 years old). Currently, I have nothing else connected to the board.

When I apply power to the unit all case and CPU fans are powered, the phase LEDs on the motherboard are all lit and after a short time the speaker gives a single beep to indicate the POST has completed.

After this the board appears to still be powered, however, I receive no display and the unit powers down after about 15 or 20 seconds (estimated). The unit will then power back up and repeat the process. This will continue until I switch off the power supply.

I have tried clearing the CMOS by both jumping the clear CMOS pins on the mother board and by removing the battery from the board for an hour (secondary question - I read about doing this somewhere along the way, can someone confirm that it is necessary to pull the battery for this long?). I have tried using different RAM sticks in different slots with no change in behavior.

At this point I believe the problem to be either the PSU (which currently can successfully power my brothers HP Pavilion with a nvidia Geforce 560 Ti graphics card) or an issue with the BIOS or Motherboard. At this point I am at a loss. Is there something I can do about the BIOS? Replace the motherboard? New PSU? Any insight would be greatly appreciated!
 
Solution
That bard need a BIOS update to be able to use a Ivy Bridge CPU as it is built for Sandy Bridge. You need a Sandy Bridge CPU to be able to update it. Try to borrow one.

wlhaskell

Honorable
Aug 14, 2013
2
0
10,510


Borrowed a Sandy Bridge and was able to successfully update the BIOS using Q-flash and a USB thumb drive. Works great! Thank you for the assistance.

A side not to any future readers - the thumb drive needs to be bootable - Gigabytes does mention this in their documentation.