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

[jumper2high]

Well, I just tried the P67A-UD4, and I have to say that, after having quite high expectations, I'm very disappointed in Gigabyte.

First of all, after installing all the drivers and utilities (ET6 and Intel Tuning Utility) I found that neither of the two function correctly (ET6 tunes the Multi down to non-turbo when started and then doesn't let me get it back up to 45 which it boots with) and Intel Tuning Utility shows an intermittent clock of 6.5GHz (rofl) and displays all the wrong voltages.

Second, I flashed F7 bios and there's no PLL overvoltage option. Logically speaking, when a beta version has something the official release should have it as well (unless otherwise specified). What's up with that???


As much as I liked Gigabyte from previous experiences, my current choice would be an Asus P8P67 board, since it's in-windows overclocking utility actually works and BIOS actually contains all the necessary functions to successfully overclock a good chip.

[Falkentyne]

Well, I just tried the P67A-UD4, and I have to say that, after having quite high expectations, I'm very disappointed in Gigabyte.

First of all, after installing all the drivers and utilities (ET6 and Intel Tuning Utility) I found that neither of the two function correctly (ET6 tunes the Multi down to non-turbo when started and then doesn't let me get it back up to 45 which it boots with) and Intel Tuning Utility shows an intermittent clock of 6.5GHz (rofl) and displays all the wrong voltages.

Second, I flashed F7 bios and there's no PLL overvoltage option. Logically speaking, when a beta version has something the official release should have it as well (unless otherwise specified). What's up with that???


As much as I liked Gigabyte from previous experiences, my current choice would be an Asus P8P67 board, since it's in-windows overclocking utility actually works and BIOS actually contains all the necessary functions to successfully overclock a good chip.

Having PLL override enabled causes a MUCH bigger chance of a boot loop or a power down/power up after shutting down from windows, or changing a setting than having it disabled. It's also difficult to make an overclock setting "stick" with PLL override enabled, even at known stable settings, without getting a failed OC or one loop. This is probably why GB doesn't have it in their official bioses.

In over 30 restarts, I haven't had a single boot loop after changing bios settings (though I think BCLK change causes a power off) or after a restart from windows, with PLL override disabled.

[jumper2high]

Having PLL override enabled causes a MUCH bigger chance of a boot loop or a power down/power up after shutting down from windows, or changing a setting than having it disabled. It's also difficult to make an overclock setting "stick" with PLL override enabled, even at known stable settings, without getting a failed OC or one loop. This is probably why GB doesn't have it in their official bioses.

In over 30 restarts, I haven't had a single boot loop after changing bios settings (though I think BCLK change causes a power off) or after a restart from windows, with PLL override disabled.

Could be - but, NOT having PLL Overvoltage guarantees the overclock won't go past 4.5GHz. I had it fully stable at 4.9GHz on an Asus board, then I took the GA board for a spin and had nothing but disappointment from that point on.

EDIT: Flashed F8b bios - after a few quite random restarts and powerdowns, finally able to boot into windows, I restarted and set 4.8GHz with a slightly higher voltage than on ASUS (was 1.33 on Asus, put 1.345 on GA) and it still kept coming up with an error after several minutes of prime95.

Sad to admit, but first chance I get, I'm putting back the Asus board in.

[simon747]

Could be - but, NOT having PLL Overvoltage guarantees the overclock won't go past 4.5GHz. I had it fully stable at 4.9GHz on an Asus board, then I took the GA board for a spin and had nothing but disappointment from that point on.

EDIT: Flashed F8b bios - after a few quite random restarts and powerdowns, finally able to boot into windows, I restarted and set 4.8GHz with a slightly higher voltage than on ASUS (was 1.33 on Asus, put 1.345 on GA) and it still kept coming up with an error after several minutes of prime95.

Sad to admit, but first chance I get, I'm putting back the Asus board in.

Was F8b at 4.8 with pll off? Seems crazy they can't sort this basic bios stuff out. They need to loosen their criteria when they check for oc at boot; this is just plain ridiculus!

[simon747]

Having PLL override enabled causes a MUCH bigger chance of a boot loop or a power down/power up after shutting down from windows, or changing a setting than having it disabled. It's also difficult to make an overclock setting "stick" with PLL override enabled, even at known stable settings, without getting a failed OC or one loop. This is probably why GB doesn't have it in their official bioses.

In over 30 restarts, I haven't had a single boot loop after changing bios settings (though I think BCLK change causes a power off) or after a restart from windows, with PLL override disabled.

Good to hear....thanks for that...I will test with that off...and let you guys know. Cheers. I need to be a 4.7 to 4.8 though....I hope I can get there with pll off

Simon