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

[coolhandluke41]

are C3 and C6 enabled ?
Edit;never mind

[Sam_oslo]

1302 warning! I've got tow random BSOD, at idle with manual vCore.

One with 4.5GHz and one with 4.2GHz. Both using the same settings as 1 hour Prime-tested on 1204. At least I mean I'm using the same settings, and then I've never had any random BSOD.
EDIT (I ran a 10-min Prime and they both seams to be doing OK at load, tho)

Anybody else can confirm we got a really crappy BIOS?.

[st0ned]

1302 warning! I've got tow random BSOD, at idle with manual vCore.

One with 4.5GHz and one with 4.2GHz. Both using the same settings as 1 hour Prime-tested on 1204. At least I mean I'm using the same settings, and then I've never had any random BSOD.
EDIT (I ran a 10-min Prime and they both seams to be doing OK at load, tho)

Anybody else can confirm we got a really crappy BIOS?.

Yes my 5.1Ghz settings with 1.416v aren't satble... They used to pass 25LinX runs with [all], now they give error on the 2nd iteration

[Sam_oslo]

After random-BSOD #3 at idle, I've flashed back to 1024. The back-flash has worked fine in EZ-flash, tho.

[st0ned]

True I also backflashed again back to 1204

[some_one]

I didn't touch the C3, C6 or other power managements, but it's using ~32w at Idle now (VS ~9w before), both according to Real-temp. CPU-temp is up a few degrees too, at Idle.

It was mentioned auto c-state behavior was changed when OC'ing. If before the auto state was enabled sounds like now it is disabled.

I'm still evaluating this, and may enable those manually, but I don't like the Idle power-usage for now. At least if real-temp is right/accurate. Is it?

It would probably be better to say if Intel was accurate. The reading is taken from the CPU itself but may for instance be based on VID rather than Vcore. It also depends on how good the manufacturers info from the VRM is (i.e. current draw).

I'm still wondering if Real-temp is right/accurate tho. That's a big difference for idle power usage. Anybody knows?

Not that big a difference considering and doesn't seem way off. Try disabling all Windows c-states and you might see ~60W while not doing much at 4.5GHz.

[tentp0le]

///1302 WARNING\\\ as well...

Thanks for providing a beta bios which totally f***ed my system.
I updated the bios through EZ-flash as always; after the update my system now hangs on power on with the code "03" on the board, which basically states: "System agent initialization before microcode loading"

Seems kind of serious to me.

I've tried basically everything to fix it, although nothing has worked.

- Reset CMOS with battery, switch on the rear panel
- Power cord out for several minutes
- MemOK! button (this just makes the led mem led blink without anything happening, says in manual it takes aprox. 30 sec. between each test - which clearly didn't happen with me)
- Not even the CRASHfreeBios worked, attempted both USB-pin and MB CD, my CD-ROM is in SATA port 5-6 - spins up correctly and reads the CD, but nothing happens.

Basically sitting with a system, that doesn't work - and just powers up with code "03"

I WOULD NOT recommend updating to this bios, wait for the official 13xx from asus support site.

This sux

///WARNING END\\\

[kidsafe]

Using offset mode and ultra-high LLC, I noticed that my load CPU voltages were basically a notch lower than before. I was running +.03V on the offset (1.195V in AI Suite II) for 1.384V under load. With the 1302 BIOS, I'm now seeing 1.376V under load.

Those of you with borderline stable OCs could probably bump up your CPU voltage by a .005V step.

[st0ned]

My failed overclock crashed with wtv voltage... I went from 1.400v-1.416v(stable before)-1.44v and all of them crashed LinX with error on the 2nd run...

[Sam_oslo]

Do NOT flash to 1003.
What a mess. Clear CMOS is not working after flashing to 1003, after going back to 1204. Either with or without power cord.

But that's not all, I keep getting Post Code 59 on ALL cold boot. That's RAM-related, but I've tested the same setting with memtest before.
Clear CMOS doesn't do a sh*t. If I keep turning it on and off, then if I'm lucky, sometimes I get a double boot with "failed OC message" and can press F1, and save the same setting and then it will boot.

I don't know how they manged to mess up Clear CMOS, that's the last thing you want to mess with. But the bigger question is, how can another BIOS mess up this one so fundamentally.

EDIT:
I thought maybe EZ-flash had messed up the back-flash, so I've flashed (to 1024) again using BUPDATER, but the problem remains.

[bingo13]

Updated 1305 UEFI on First Page

[Splave]

Can you please have better elpida hyper ram support on p8p67 :/ M4E can do it easily

[KGB7]

With 1305 Bios, you can now turn OFF Bluetooth.

It has set my RAM to proper timing and voltage as well.

[KUBA_TM]

Bluetooth could be also turned off in 1302 version

[KGB7]

It wasnt in the release notes and i skipped 1302.

[Skratch]

running new 1305,not any different from 1204

[crazyea]

With 1305 Bios, you can now turn OFF Bluetooth.
It has set my RAM to proper timing and voltage as well.

This is a feature I'm glad they added!!

[Mic]

Would it be possible in the next release to add power fan to the fan control and lower the minimum chassis fan % to 20 instead of 40% ?

[Sam_oslo]

Any alternative way to Clear CMOS on Deluxe ?

I've flashed to 1305, but still getting Post Code 59 at cold boot, after 1003-mess up. I need to Clear CMOS to reset ME inside PCH to resolve it, otherwise I have to go down to 1333Mhz RAM. But 1033 has messed up Clear CMOS too.
It there any other way, a jumper or something, to Clear CMOS on Deluxe ?

[KGB7]

Any alternative way to Clear CMOS on Deluxe ?

I've flashed to 1305, but still getting Post Code 59 at cold boot, after 1003-mess up. I need to Clear CMOS to reset ME inside PCH to resolve it, otherwise I have to go down to 1333Mhz RAM. But 1033 has messed up Clear CMOS too.
It there any other way, a jumper or something, to Clear CMOS on Deluxe ?

Unplug all the power cords, take out the battery and hold the reset button on the mobo for 30sec.

[Peter949]

Anyone see a jump in temps with the new 1304 bios? I never hit 80c or high 70s with my 24/7 oc settings and now they do in stress tests.

[Sam_oslo]

Unplug all the power cords, take out the battery and hold the reset button on the mobo for 30sec.

Thx, it worked
It's not the easiest way, but it's good to know it's there.
Post Code 59 is resolved after a Clear CMOS too so I guess all 1302-mess up is more or less resolved, somehow.

1305 seams to be working fine here, I've tested with just a little 10-min prime tho.

[McLaren__F1]

Anyone see a jump in temps with the new 1304 bios? I never hit 80c or high 70s with my 24/7 oc settings and now they do in stress tests.

Temps upped by 3c for me

[Peter949]

okay...i dont like this bios version. i'm constantly booting into windows at 1.42 volts then it goes to my bios inputted 1.38v when stressed. wtf. then randomly jumps to 1.42v when stressing too.


arg...can't flash back to 1204.

Definitely not a happy camper. Idle/load temps is +6-10c now because the boot in voltage now. Stays like that until speed step kicks in.

[st0ned]

No way back from 1305 to 1204 ?? Guess I'm not updating since the 1302 fiasco...