Help please GA-X58A-UD5

SC.Jace · 30 Jun 2010 at 13:59

I was wondering if anyone can help with the following issue.

When i power the pc up i get b8 or 68 showing on the LED,i've been told it might be the bios revision,has anyone else experienced this problem? OCUK have supplied me with a replacement board (same revision) but it is still coming up with same error.

Here is the spec,

GA-X58A-UD5 revision 1.0 http://www.overclockers.co.uk/showproduct.php?prodid=MB-236-GI
Intel i980x retail
H50 all in 1 cooler
6GB DDR3 1600mhz Corsair http://www.overclockers.co.uk/showproduct.php?prodid=MY-169-CS
Saphire 5970 http://www.overclockers.co.uk/showproduct.php?prodid=GX-221-SP
Corsair 850w psu
LianLi case
160gb intel ssd ( SSDSA2MH160G2C1 )
Samsung 2TB 5400 F3 drive
Samsung 1TB 7200 F1 drive

Any ideas?,

Jace

EDIT:I've tried each memory stick and still no joy

Tealc · 30 Jun 2010 at 14:10

I wonder if the BIOS Revieion is having trouble recognising your CPU. Was this a full system purchase or a self build?

Edit: After a bit of research it seems that b8 is the Intel MRC code.

Intel MRC Code
This block of code has to be implemented in every Intel based platform BIOS. It initializes and configures the processor and runs bus training and adusting routines. It adjusts clockskews, read/write leveling, signal termination resistors and several chipset timings dynamically depending on the trace length, signal quality, timing and memory installed in the motherboard. If the MRC code hangs or the board cant pas the MRC code and resets it usually points towards memory problems and unsupported multiplier settings or a unsupported combination of multipliers.

b8 Intel Core i7 MRC Code - Memory - check above

Or
68 - Video Init Read CMOS location 14h to find out type of video in use. Detect and Initialize Video Adapter. Test video memory, write sign-on message to screen. Setup shadow RAM - Enable shadow according to Setup.
68 - PM init PM initialization (PSU)

SC.Jace · 30 Jun 2010 at 14:18

hi,

thankyou for reply.
i think i tried with 1 stick of memory but it wouldnt post,i'll check again when i am at home,its a pain not having another cpu i can try it with too

Tealc · 30 Jun 2010 at 14:19

What is the BIOS revision? Also check the edit I made to the previous post.

SC.Jace · 30 Jun 2010 at 14:47

i assumed it was the first revision without 6core support,i didnt look to see if it was written on the board,i'll have to confirm when i'm home from work

Tealc · 30 Jun 2010 at 15:39

According to sites I have read BIOS revision F5 fixes this issue for all complainers.

First release F1 didn't even support the 6 core CPUs, funny that as the board was designed for them.

The 6 core was implemented in BIOS F2 so you'll need at least.

How you get to the BIOS flash utility without a working CPU though is going to be tricky. A return to ocuk for a BIOS flash perhaps? Or locate an older CPU for a quick borrow.

Bit silly of Gigabyte releasing a board without support for the processors it was designed to use. Probably why they now have a Revision 2.0 with a working BIOS.

SC.Jace · 30 Jun 2010 at 15:41

i did return my board for flashing however i was issued with a new board,i dont think it was flashed,someone was going to lend me his i920 but he let me down

SC.Jace · 30 Jun 2010 at 19:57

ok unless i'm being blind all i see on the board is about the board revision and not the bios version :confused:

,ive also tried each stick of memory seperatly and still same error :mad:

Tealc · 30 Jun 2010 at 20:29

The board won't declare the BIOS version until it Posts I guess. The revision 1.0 stamped on the board is the hardware revision, not the software revision. It's initial BIOS F1 didn't support Core i7 980x, probably because it wasn't out at the time.

You will need to use a quad core i7 chip or perhaps another RMA I reckon in the hope they actually fix it this time.

The BIOS is basically telling you that you have installed an incompatible CPU (as far as it's concerned) and will refuse to do anything further.

Maybe someone in your neck of the woods could help. I'm 180 miles from you.

SC.Jace · 30 Jun 2010 at 20:48

thanks for your input ,i agree gigabyte has some explaining to do,i did email them and all they suggested was removing the board from my case and then doing a cmos reset,this has really put me off their boards,ive also left a message in the RMA/Support section of this forum as i cant get to phone during work hours

edit:i now have rma raised