***Official*** ASUS P67/H67 BIOS Updates

[Daddyjaxx]

Does 1204 have PLL overvoltage or is it still just in 1053?

[Splave]

1204 does have pll overvoltage yes

[Leeghoofd]

anyone can lower PCH voltage on the sabretooth ? Pro and DLx work fine, sabretooth always resets back to 1.05... wicked :p

[Splave]

is this a trick leeghoofd lowering helps?

[Kimi.Rk]

Hi! I wanted to know when Asus plans to release 13xx bios?
I can not use ram-F3-17066CL8D 4Gbps g.skill! very unstable .. hiper chip? This ram is on QVL p8p67 deluxe.
excuse my English.

[Utnorris]

So I have a weird issue with the SATA ports. I originally built my Intel SSD RAID on ports 2 and 3 (SATAII), however, if I move them to ports 0 and 1 (SATAIII) the RAID manager does not see port 0. The bios sees them, but not the RAID manager, so for now I am leaving them on ports 2 and 3. Any ideas? Do you think port 0 is messed up?

Also, I was having an issue with running my PERC5i card in the x4 slot. The system would freeze during the Windows load. If I remove one of my GTX460's it would boot fine. This is only an issue if I let the Windows boot manager load the OS. If I set the boot to my OS drives then all is fine. It's not a big deal since I just point the boot directly to the OS drives, but I find it interesting that the Windows Boot manager would freeze during the windows load and system does not when I point it directly at the OS drives.

[Kimi.Rk]

asus is too slow in releasing new bios! too long and not good.

[Leeghoofd]

I had no problem with the RipjawsX CL9 rams running at CL 7-10-7-24 1T (1.57Vdimm) with the Dlx motherboard (1253 bios ) Kimi.RK. Got them running at the same speed now with the Sabretooth... no issues...

[Kimi.Rk]

I had no problem with the RipjawsX CL9 rams running at CL 7-10-7-24 1T (1.57Vdimm) with the Dlx motherboard (1253 bios ) Kimi.RK. Got them running at the same speed now with the Sabretooth... no issues...

ripjaws uses Hynix chips .. Perfect Storm 2133 cl8 should be hyper if I'm not mistaken.

[Leeghoofd]

Corsair GTX 2 needed 7-8-7-21 1T, but a tad more voltage then with 1366. 1.7 to pass hyperpi 32M...

[TASOS]

Update - Qualification testing is going well on the upcoming 1302 UEFI series.
1. Per Bug Core save problem is fixed
2. HD Performance is a bit better
3. New auto rules for power management is working well
4. USB performance is up
5. Memory tuning profiles and performance enhancements are working well
6. Greater memory compatibility (still fine tuning Elpida Hypers, which will be in the next update, these modules were designed with Bloomfield/Gulftown in mind and expected settings for those platforms in the SPDs do not mesh nicely with Sandy Bridge, especially the VTT requirements)
7. Auto Tuning is improved slightly
8. Improved Resume/Hibernate return times

Issues still Open on my end-
1. MS Wireless Receiver 3.1 and under appears to be causing drift problems in UEFI in certain setups, Wireless Receivers above 4.0 have no issues, checking older wireless mice and keyboards now (3 years or older)
2. Elpida Hyper 2000+ Kits, still fine tuning as mentioned above
3. Still waiting on updated PCH firmware and new RST driver set from Intel to address several minor bugs

Any news ?

[initialised]

Hmm running 1,6v on the ram atm, but did you mean that it'll fix the dual boot problem? Thing is, when I've had the PC off for an amount of time, it starts with a dual boot - and the second reboot it just sits powered on without signal to the monitor, which again forces me to manually hold the power on button to shut it down - and then back on.

The lowering ram voltage may fix that, as you mentioned - will check tonight. Although, the most enoying thing is the dual boot everytime the PC has been off for a longer period

I've currently two PCs doing this in the field and three on the bench. Setting APM/PCIE/Enable as per Mason's post helps but doesn't solve the issue. One system is a Deluxe, two are vanilla. The Deluxe hangs on 59 on the POST indicator. It seems to happen across all ASUS P67 boards on both the 1204 and 1253 BIOSes.

[Splave]

the 1302 doesnt seem much different to me, bclk changes mean you have to get to fail overclocking message then enter bios and f10 and they work this is a bit crazy imo.

[tentp0le]

the 1302 doesnt seem much different to me, bclk changes mean you have to get to fail overclocking message then enter bios and f10 and they work this is a bit crazy imo.

Huh, is there a new UEFI out? since you refer to the 1302?

[Splave]

it will be out soon but doesnt seem to do much as far as I can tell

[kpablo]

Any news for WS Revolution?

[my87csx481]

Has the ability to downgrade BIOS versions been addressed yet?

That is, has anyone figured out an easy/noobish workaround way to do it yet?

[tentp0le]

Has the ability to downgrade BIOS versions been addressed yet?

That is, has anyone figured out an easy/noobish workaround way to do it yet?

Has always been possible with Ezflash, just remember to use an usb pin with a FAT32 format.

[Leeghoofd]

It says file image outdated TentpOle, how do you workaround that ?

[cstkl1]

And this two issues?? M4E
*** IROG firmware Corrupt ****
Bios 1 x951
Bios 2 04xx

Symptom - Stuck at multi 16
Cause - Nada
Fix - Change to Bios 2 which should be ure Default bios mine i think is 04xx
and it will update the Firmware. There will be two boots of update
then enter bios like normal boot. Then switch back to Bios 1 and IROG firmware will be updated again like previous.
Then enter ure profiles etc all should be no prob

Solution that failed
Updating ure Bios 1 will not fix this or reflashing ure bios 1 to 901, 950,951

Sort this out ppl on how to reflash the firmware on a easier level.

*** Dual Boot on high dram clock on Cold Start aka 2200mhz and above ***

[Forceman]

Has always been possible with Ezflash, just remember to use an usb pin with a FAT32 format.

It only works on the Deluxe model, the others don't allow downgrading because they changed the HW ID for those boards.

[crazyea]

So did they stop with the bios updates after the chipset fiasco? He last said they would have another in a week, however its been two weeks since that.

[Praz]

BIOS updates are still being done. It is difficult to pin down how long testing and qualification may take.

[my87csx481]

So did they stop with the bios updates after the chipset fiasco? He last said they would have another in a week, however its been two weeks since that.

That's what I figured might happen....no more support.

I hope not but, .

[initialised]

I'm having to tell customers hit by the Cold Boot POST fail problem to wait for their replacements. Sux