Looks like Asrock has posted a new beta BIOS.
http://www.asrock.com/mb/beta.asp?Model=P67%20Extreme4
Looks like Asrock has posted a new beta BIOS.
http://www.asrock.com/mb/beta.asp?Model=P67%20Extreme4
I have a question regarding the E6 & the E4 boards. Looking at the official BIOS download page, are the bugs that are fixed for one board included in the BIOS update for the other board?
Aside from layout & the inclusion of 2 more SATA 3 ports, both boards seem very similar. Both boards seem to have BIOS updates that seem parallel. Can anyone answer this?
Thanks.
Extreme6 doesn't have a UEFI thats as bug-free as the Extreme4 has at present, but theres nothing which should cause any problems.
Extreme 4 purchased :) Just need to wait for my 2600k to arrive and EK Supreme HF block. Hope this board is as good as your making out Ket :) Never had an ASRock before, always thought they were sub standard boards.
On a side note I've been having issues with my 2x 5870's not being fully utilised with my current Q9550 @ 4.4ghz. I'm really hoping its down to this.
@Ket
There is a problem with AXTU software. When you are running for e.g. Prime95 Blend and then you go to IES tab in AXTU, vCore droops down by approximately 0,03V causing BSOD if it's to much for CPU to keep it stable.
There's a bug in the LLC where it limits the voltage on my board depending on what level I have it set at. If set to auto or level 5 I'm limited to 1.392v no matter what is set in the UEFI. I have seen the same behavior on 1.50 - 1.61, didn't test it on the 1.42a.
Other people reported same "problem".
Software bugs: Send in the details to Asrock, I just gave them a hand in fixing UEFI bugs.
LLC thing: Not sure what could be causing that but it doesn't really sound like a bug. When OCing always set LLC to level 2 and go from there (level 1 tends to be too aggressive)
Lvl2 is not really do able i don't think, voltage is waaay too high under load or to low for stability at idle.
My point is that llc should not limit voltage set in bios but help with vdrop under load or at least that's how i thout it was supposed to work?
Something is off in your system then. If I set 1.36v with LLC lvl2 I get 1.36v @ idle and 1.35v with all 4 cores loaded 100%.Quote:
Originally Posted by Mysterfix
I'm using offset voltage not fixed. When using offset the voltage at idle fluctuates a lot and llc acts very different than in fixed mode. If I set lvl4 llc and offset @ .140 that gives me about 1.440v in bios but when I boot into windows idle voltage can range from 1.12v to 1.35v. Under load my voltage will not go above 1.416v using lvl4 llc no matter what is set in the bios. At lvl 5 that limit is 1.392v, the lower your starting offset voltage the lower your idle voltage is. I have found that I need to stay above .110v offset for stability during low power situations like web surfing. Any lower offset @ 50x multi results in bsod during low power situations. The problem is the LLC bug makes it impossible to dial in the voltage using the offset function.
I haven't really played with offset voltage. I prefer the set it and forget it approach. Its not as though 1.36v vs 0.9v or so is going to really add anything to the leccy bill :p:
Just a question for you guys:
What ram slots do you use when using 2 memory modules?
I placed them in white slots (A2 and B2) using the same logic that applied to P55 motherboards (when using only 2 dimms, they should be placed at 2nd and 4th slot)
I saw that his also applies to Asus P67 boards. I haven't found anything for Asrock P67 motherboards, not even in users manual.
I started off using the blue slots, but found my ram wouldn't run at the rated speeds (2133 mhz) stable, when the cpu was overclocked. I moved them over to the white slots, and no problems now. Not sure if this answers your question though.
Thanks for the answer.Quote:
Originally Posted by mean6
You said you moved them from blue to blue slots. I assume you ment from blue to white?
Looks like it is same as on Asus boards, you can use 1st and 3rd slot, but they recommend using 2nd and 4th slot. Probably same applies to Asrock.
Anybody knows for sure?
yes, that's what I meant. Edited post.
Hi guys
Other proud Asrock P67 Extreme 4 owner here, I got the B3 version and it came with the UEFI 1.60, it feels pretty solid so far.
I have paired it with a i5 2500K and some 2x2 G.Skills RipjawsX 2133C9, yeah, I know, memory speed doesn´t mean that much but it feels good have the possibility to run 2133 even though I probably going to run 1600C7 most of the time.
I will say thanks to you guys in this thread and specially to you Ket, it was you guys who made me choose Asrock this time, it feels like it doesn´t have as much problem as the rest of the P67 boards.
@CikaNovo
According to the manual one can use either the blue or white.
I can run my RipjawsX at 2133 in either of them without problem.
max vcore whit bios 1.6 to extreme6 ?
I've only tried white slots so far, but i'll give blue slots a try to see if it gives any improvement overclocking wise (but i highly doubt it).Quote:
Originally Posted by Ghostleader
even though i use the p67 fatality, except from annoying uefi background image (i hope there will be some editor tool which can remove/replace with whatever user want), all these 3 asrock mobos(extreme4/6, fatal1ty, are quite similar ;)), differentiate only in add-on chipsets and a bit weaker vrm department in exteme4 (8+2 vs 16+2), so i suspect all 3 suffer the same bugs.. whenever someone points out some bugs, they fix for all of boards, as its likely all will be affected.. ;). I gathered all the bug list reported in this thread and report the behavior with 1.70 bios
- Pressing [Del] key to enter UEFI setup does not consistently work seem to work ok most of the time
- Saved profiles are not preserved when battery / power cord is removed work OK
- Devices connected to SATA3_M1 & SATA3_M2 ports do not show up in UEFI setup not much of a bug i think, as already stated, just needs enabling bootable
- ODT WR / NOM (channel A&B) do not show current parameters in UEFI Exists in Fatal1ty also, cosmetic bug i think
- Connecting a device to rear USB3.0 ports causes a prompt BSOD (BSOD squarely points at Etrontech driver, tried both 0.89 and 0.91 drivers) work OK at least with 0.96 drivers, possibly was a driver fix
- Full screen logo [Disabled] option is not saved into profiles still there, cosmetic i think
- Using Clear CMOS button results in all saved profiles being wiped! work OK
- Adjusting BCLK frequency results in the board failing to POST work ok (only >105 start problems, not to blame the bios.. ;))
- Disabling Spread Spectrum results in the board failing to POST work OK
in addition to not save in profiles the "Full screen logo [Disabled] option", i found 2 more menus which are not saved in profiles in Fatal1ty(you should check if extreme4/6 has the same "bug")
1) Super I/O config (i always disable all 3, and always find them reset when load profile from a <load UEFI defaults> state
2) Advanced USB Config (i enable USB3 legacy, and always find it reset to disabled when load profile from a <load UEFI defaults> state
p.s.> pardon my ignorance for this question.. when u manual adjust the multiplier, why the Turbo boost Enable/disable option, disappears? (the turbo boost power options do stay though, => is turbo boost forced enabled when o/c? )
^ You must be a Pro3 owner, no such bug exists on the Extreme4/6 ;) To clarify as its been bought up check the first page for a full rundown of fixes. As I stated initially, the etron driver was to blame for BSODs when trying to use a logitech webcam, something which seems to be fixed with the new driver I uploaded on the first page. As others have stated, the Extreme4/6 boards are fantastic and by far the most trouble-free system people can expect to own in a long time. I do not give high praise out lightly, but Asrock truely deserve it for their Extreme4/6 boards.
Quote:
Originally Posted by Ket
as for the bugs itself, to be honest, i find them annoying only, not dysfunctional..Quote:
Originally Posted by papatsonis
i will check it again though. in the meanwhile, try this.
1) disable all in <Super I/O Config>, and enable "USB3 Legacy mode", in <Advanced USB Config>, save reboot
2) get in UEFI, (check that these settings are saved..) save this profile..
3) Load UEFI default,->save-> reboot
4) get in UEFI, load the previous saved profile, and check if these option are loaded.. and report :up:
any concrete explanation for the above?Quote:
Originally Posted by papatsonis
p.s.> agree about Asrock, not only on 1155 platform, but in 1366 has some very very good motherboards ;)
Quote:
Originally Posted by papatsonis
Those bugs still exist and have been there for some time. They are very very minor though and certainly don't cause any problems. I'll remind Asrock about them though as they probably just forgot about them focusing on fixing the serious problems.
I've used my Ripjaws in both white and blue slots. No stability problems here. /hugs mobo/Quote:
Originally Posted by CikaNovo