******Gigabyte GA-P67A-UD4 Discussion Thread******

[SeMbEr]

Kinda funny that i cant even flash mine bios on this board Can som1 tell me what im doing wrong...?

I have now F3 bios inside it. I downloadet newest version of @Bios program and installed it, tryed to flash F7h and F7 bioses on it. It just reads the bios file and then it crashes, have tryed many many times!

Then i tryed with Q-flash and put bios filesh on FAT32 usb stick and it finds bioses well but it keep saying: "Bad Bios Image".

[Falkentyne]

Use the MS DOS flasher. That's always the safest way.
Use a USB boot disk (you can make one with the HP format tool), format a usb flash drive as fat 32, stick SPIflash (the DOS flasher) on it and the raw bios image (NOT the exe) file, and just flash away. I think the command was spiflash /z whatever.bin

I don't trust windows flashers, so avoid @bios.
And the Qflash BIOS won't read the dos files until you flash one with spiflash first, apparently.

[Jupiler]

Sorry to hear!

When you get time try it a few times just to be sure, sometimes it's tricky and you have to time it just right.

If you are unsure about the socket pins post a few pics.

Does it loop if you boot it with no memory? Try it a few times, it should error, then put back in a stick and try booting again, this should clear the DMI and might get it booting again.

Get a beep message with no memory installed.
After plugging back one in it boots but I get no beep messages.
I presume it would beep if something's wrong with the board.

After I tried your trick with the power switch and PSU switch, the first time, it gave a short beep, like when it powers on normally, but after several tries, no beep or post.

[Lsdmeasap]

Thanks for the socket pics, it's always good to have new eyes look just to be sure. Looks 100% perfect to me, so it's not a bent pin at all that I can see.

Terrible you can't get this sorted out. Have you tested the CPU on another board to be sure it's not a problem. Sorry to ask if you already mentioned that.

You may have to RMA, sounds like you've tried all you can and then some. Sorry this board has been such a hassle for you!

[SeMbEr]

I got bios in with spiflash, thanks Now it seems i can do 55x99.5bclk and lilbit more but not 55x100, looks like it is actually my cpu's limit since mine asus board was able to do 5.4-5.44GHz too :/
Had no luck trying 55x100 multi only on one core with turbo multi..
What is absolute max voltages with air what u guys have been given ur cpu while testinb above 5.4GHz ht on or off?

Here is somthing that i have used:
vcore = 1.6v (1.58v full load)
vtt = 1.2v
I/O = 1.13v
mem = 1.7v
PLL = 1.95v

Dont know if i can push somthing more or am i using too much volt for somthing already?

[Jupiler]

I think I found the reason why it wouldn't boot :

Apparently, my 5850 is dead.
I don't know how this might have happened, I've been very careful when I uninstalled the waterblock from the cpu.

Before heading to a store and buy another board, I thought about 1 option I forgot to test :
Try another videocard.

Plugged in an old X1900XT and it booted straight away.
I thought, WTF? How can this be.
Retried the 5850 but it wouldn't boot.
X1900XT back in and it booted without any problems.

I don't understand why the board doesn't give a beep error when the videocard is broken or something like that.

Gonna remove the card this weekend and check it for any physical damage.
Got a spare 280GTX, which should cover my needs for the time the 5850 is RMA'ed (if an RMA is in order)


Thanks for the help everyone, I guess this was a user's fault and probably not the board. Unless, for some reason the board would have taken out the videocard.

[Lsdmeasap]

Awesome to hear!! Sorry about the GFX card though!

So, it's been booting the whole time probably right

Kinda sucks this board does not have debug LED, then you would have seen it boot to FF and knew it was running. At least sometimes that would work, I just booted last week with a dead 570 and it went right to FF so I assume windows was loading, and same without a card installed too.

You are right, it should at least beep and they don't, also on UD7 same applies and no error beep or debug code with dead or missing GFX.

Glad to hear you got it up and running! Now, just have to try and save your 5850

[[XC] Hicks121]

I think I found the reason why it wouldn't boot :

Apparently, my 5850 is dead.

I told ya you need to shave. All that fur you have prolly got into the vc & caused all of your problems.

[LeetMiniWheat]

yeah these really do need a debug LED. it's a shame gigabyte didn't include one, when other boards in this price range have it. or at least a friggin CMOS reset button.

[Falkentyne]

I think I found the reason why it wouldn't boot :

Apparently, my 5850 is dead.
I don't know how this might have happened, I've been very careful when I uninstalled the waterblock from the cpu.

Before heading to a store and buy another board, I thought about 1 option I forgot to test :
Try another videocard.

Plugged in an old X1900XT and it booted straight away.
I thought, WTF? How can this be.
Retried the 5850 but it wouldn't boot.
X1900XT back in and it booted without any problems.

I don't understand why the board doesn't give a beep error when the videocard is broken or something like that.

Gonna remove the card this weekend and check it for any physical damage.
Got a spare 280GTX, which should cover my needs for the time the 5850 is RMA'ed (if an RMA is in order)


Thanks for the help everyone, I guess this was a user's fault and probably not the board. Unless, for some reason the board would have taken out the videocard.

Did you try the 5850 in a different computer?

[Jupiler]

I told ya you need to shave. All that fur you have prolly got into the vc & caused all of your problems.

Ha, look at yourself ,captain Bluebeard.

yeah these really do need a debug LED. it's a shame gigabyte didn't include one, when other boards in this price range have it. or at least a friggin CMOS reset button.

I'm thinking the same.
For a board in this price range, they might have included way more options, compared to other brands.

Did you try the 5850 in a different computer?

Nope, not yet.
I checked the card with a magnifying glass but I can't seem to find any physical damage on it.
Tried installing the card again but it wouldn't post.
After that, I installed the 280GTX and it works fine.

Although I had a scary moment.
After installing the nvidia drivers, I rebooted and entered the bios.
I made a small change in the Voltage settings menu, saved and exit.
After restart, I got the same crap, endless reboots.
Unplugged the cables and let it rest for 1 hour.
Restarted and it was back alive. Thank god, I already thought something went wrong with my 280GTX.

Backup'd the bios using an old PS/2 keyboard, worked without a problem.

Only thing I hope for now is no more trouble.

[LeetMiniWheat]

Although I had a scary moment.
After installing the nvidia drivers, I rebooted and entered the bios.
I made a small change in the Voltage settings menu, saved and exit.
After restart, I got the same crap, endless reboots.
Unplugged the cables and let it rest for 1 hour.
Restarted and it was back alive. Thank god, I already thought something went wrong with my 280GTX.

Backup'd the bios using an old PS/2 keyboard, worked without a problem.

Only thing I hope for now is no more trouble.

I've experienced this too while changing something minor in the BIOS. even changing to a known-good setting. definitely very finicky... a flip of the PSU power switch and a screwdriver in the clear CMOS jumper fixes it usually.

and speaking of lack of features, that is why I probably won't be staying with gigabyte after the new P67 boards are released... I hope gigabyte wakes up and revises these!

[miahallen]

Endless reboots and double posts are MUCH less common if the backup and primary BIOS match each other.

Thank you SO much!

[Falkentyne]

Eh? You mean flashing the backup to the main bios version helped? If so, excellent.

[miahallen]

Correct....I was on the verge of throwing this thing out the window....but I read your post and flashed the backup.....things aren't perfect now, but much much better

edit - well....that victory was short lived. It's back to it's old ways again .....out the window it goes

[TASOS]

Correct....I was on the verge of throwing this thing out the window....but I read your post and flashed the backup.....things aren't perfect now, but much much better

edit - well....that victory was short lived. It's back to it's old ways again .....out the window it goes

When your system is unstable or close to the edge ... the UD4 board behaves strange on reboots.

Flashing the backup bios with version F5 or later , helped a bit , but not quite enough.

For benchmarking , an instant power-off from the PSU , always helps and it's definetely the quickest way to boot again after an oc failure.

[miahallen]

When your system is unstable or close to the edge ... the UD4 board behaves strange on reboots.

Flashing the backup bios with version F5 or later , helped a bit , but not quite enough.

For benchmarking , an instant power-off from the PSU , always helps and it's definetely the quickest way to boot again after an oc failure.

Even when booting after a reset cmos proceedure, the board exibits poor posting behavior....not just when overclocked

[HelixPC]

Even when booting after a reset cmos proceedure, the board exibits poor posting behavior....not just when overclocked

I agree, ive had this board since launch, and its been nothing but problem after problem, it even has an issue with the Creative Labs Titanium HD sound card, which had no issues in my x58 sabertooth. I expected more from gigabyte.

[dinos22]

Even when booting after a reset cmos proceedure, the board exibits poor posting behavior....not just when overclocked

Sounds like you may have bios corruption issues. When you push it hard it happens sometimes and you need to reflash.

what was the bios you used? Can you test the latest official bios from the website and also do the B_BIOS backup with it

http://download.gigabyte.us/FileList...67a-ud4_f7.exe

[HelixPC]

Sounds like you may have bios corruption issues. When you push it hard it happens sometimes and you need to reflash.

It happens even with a new bios flash. I flashed to F7 and my board went on an endless reboot messing up all my components by turning them on and off about 20 times, and finally restored F3 on its own, this board is garbage, so is every P67 Gigabyte board out now. How they could release this POS board is amazing and i didnt expect it from gigabyte, usually my 1st choice for a motherboard, not anymore.

[dinos22]

It happens even with a new bios flash. I flashed to F7 and my board went on an endless reboot messing up all my components by turning them on and off about 20 times, and finally restored F3 on its own.

This makes sense. You really should not be leaving the F3 bios as backup if you are going to use the newer bios files. Make sure you flash to F7, load defaults and clear cmos (take the battery and PSU plugs out for a minute) and then use ALT+F12 on startup to copy main bios to backup bios. This way it will be more stable and you will not see bios recovery springing up quickly.

[TASOS]

Gigabyte people read this thread , and i forgot to ask the other day ...

Why Gigabyte i-Ram doesn't work with these boards ???

[dinos22]

someone PMd me with a monster 2500K asking if i can get multies higher than 57

here is a bios with multies up to 59x

i couldnt test it as i dont have the board handy let me know if you are able to key it in bios

http://filefactory.com/file/b55ced9/n/p67aud4.f8b

[C-N]

Hi guys,

I remember someone on this thread saying something along the lines of how unhappy they were GB were to cheap to include a POST code thingy on the UD4. I recently purchased a PCI Diagnostic card from ebay, it cost nothing £1.50 delivered from Hong Kong looks like this http://www.xtremesystems.org/forums/...30&postcount=2 & works a treat

No need to do without for the sort of change I have down the back of my sofa

[Balb0wa]

new bios out F8b:

http://forums.tweaktown.com/gigabyte...test-bios.html

just tried it, one thing ive noticed with this , is that my speaker on my motherboard beeps when booting, on the others it didnt, lol , very odd