Asrock P67 Extreme4 UEFI & Drivers thread [Extreme6 & Pro3 owners welcome]

[Ket]

Put the jumper, battery and power back as they were

[paschov]

Sorry to disappoint you Ket, followed your instructions, but still the same crap. I tried to load 4.4 Ghz factory presets, same blinking cursor, forget about higher settings. For me it's just plain and simple flawed unfinished product, I mean chipset. Or maybe the chip, who knows. Anyway, I'm extremely disappointed. I think I made a huge mistake not waiting for Bulldozer. But from another side who could imagine this, Intel making a crappy hardware.

[Ket]

Its hard to blame any one component without being able to swap out components and properly test each one. My B2 board is still working without any issue but I am seeing these 2500 and 2600k CPUs seem to degrade quite easily. Your particular problem though happened way too quickly for any component to degrade though it was literally a matter of hours. Shooting from the hip.. maybe one of the heatsinks on the mobo or CPU aren't making proper contact.

[paschov]

Wait a minute... CPU cooler is excluded, I'm using Zalman waterblock with Liquid Metal interface and CPU temperature was within normal limits. MOSFET coolers are also sitting tight. BUT, last time I was checking this ridiculous southbridge "cooler" with V8 on it, if it was sitting properly, it made a kind of clicking sound. I was using your settings from page 46, and all voltages are relatively elevated. So, crappy southbridge cooler, elevated voltages and everything degraded immediately after.... Got the picture? Even now, on default settings, it's very hot. So, what is done, is done. What do you think, should I try an active cooler on southbridge or it's irreversibly damaged and I should RMA the MB? Or it's still CPU?

[mean6]

Hello everybody! I'm reading this forum for months already, but this is my first post. I have P67 Extreme4 B3 with 2600K chip and G.Skill P67 memory. The day before yesterday I found Ket's settings on page 46, tried them, they worked perfect, I even upped clock to 46,ran Intel Burn Test without any problem. Everything was OK, no double boot. I was happy like an elephant, shut down my rig, went to sleep. Next morning, no cold bug (YESSS!), BUT: blinking prompt in left upper corner of display. And since that time, no matter which settings and BIOSes I try (I tried quite a bunch, believe me!) on any multiplier higher than 43 I get a blinking prompt. This chip was working on old B2 MB on 48 multiplier without a problem. What should I do? RMA the MB? The chip? Both of them? Sell RMA'd parts on fleebay and forget about Sandy Bridge? Any help will be highly appreciated. Thank you.

I am experiencing the exact same issue. I thought it was from running my ram at the rated speed of 2133. People on the forum suggested to downclock the memory to 1600. I tried it, and I was able to run @ 4.8, ran IBT, no issues, played games no problem. I thought I had the problem solved. Turned off the computer, turned it on the next morning, and got the blinking cursor. I went out and got another board, and cpu (which happened to have the same batch number as the one I was currently using), and tried to narrow it down, but whatever combination I used, it did the same thing. Also, like you, the 43 multi is the only stable setting I can get. Anything over 43 requires PLL Enabled, just to get into windows. None of the preset overclocks will work past 4.2. From my experimenting, I think that it's just a bad batch of cpu's from intel. Not saying they are faulty cuz they work fine at stock, just not very good overclockers. What batch number is your processor?

[Ket]

Wait a minute... CPU cooler is excluded, I'm using Zalman waterblock with Liquid Metal interface and CPU temperature was within normal limits. MOSFET coolers are also sitting tight. BUT, last time I was checking this ridiculous southbridge "cooler" with V8 on it, if it was sitting properly, it made a kind of clicking sound. I was using your settings from page 46, and all voltages are relatively elevated. So, crappy southbridge cooler, elevated voltages and everything degraded immediately after.... Got the picture? Even now, on default settings, it's very hot. So, what is done, is done. What do you think, should I try an active cooler on southbridge or it's irreversibly damaged and I should RMA the MB? Or it's still CPU?

The settings I screen capped on page 46 are mostly stock voltages, VTT and vcore are the only options which have really had any additional voltage added and even those values haven't been increased by any unrealistically high value.

If you were wiggling the PCH heatsink or something you might of inadvertently damaged the chipset or caused the TIM which is used (which is gum-like stuff) to break some of its contact which would explain the higher temps you are getting now and possibly the instability too.

[Ket]

THIS IS A NOTICE FOR ALL ASROCK Z68 OWNERS!

Good news for all you Z68 Extreme4 owners asking me queries and questions. After talking with one of my contacts Asrock will be sending me a Z68 to bug-test and to further help you guys out. I'll be making a seperate thread for the Z68 Extreme4 so PLEASE POST THERE OR SEND ME A PM!

ASROCK Z68 EXTREME4 THREAD

[pythonse]

im getting error codes 60 and F1 getting triple boot,not double but triple

[Ket]

POST code 60 is DXE core started and POST code F1 is a forced recover condition forced by the user.

[Nw0rb]

Wait a minute... CPU cooler is excluded, I'm using Zalman waterblock with Liquid Metal interface and CPU temperature was within normal limits. MOSFET coolers are also sitting tight. BUT, last time I was checking this ridiculous southbridge "cooler" with V8 on it, if it was sitting properly, it made a kind of clicking sound. I was using your settings from page 46, and all voltages are relatively elevated. So, crappy southbridge cooler, elevated voltages and everything degraded immediately after.... Got the picture? Even now, on default settings, it's very hot. So, what is done, is done. What do you think, should I try an active cooler on southbridge or it's irreversibly damaged and I should RMA the MB? Or it's still CPU?

I find it weird that you didnt know how to do a full cmos reset but yet your moving things around inside the case like you know whats going on.. Stop to think maybe you dont kno whats going on and you shouldnt mess with things you dont know what they do

[Nw0rb]

Ket, what does f1 have to do with ?? because when i put pll over voltage on and go to 4.8 i get 1 or 2 f1's on a cold boot. Just seems weird i wish Asrock would giver you a extreme 6 to work on cause this is booty

[Ket]

I can't be certain, and probably only AMI truely know the full meaning of their POST codes but F1 is probably triggered by a failed OC attempt... or maybe when the UEFI detects applied overclock settings. I'd have to ask my contacts if they know more to give a fuller answer. I've never seen POST code F1 on my Extreme4 unless its been a failed OC attempt. Have you tried lowering your multi to say 46 and seeing if you still get the problem?

[pythonse]

POST code 60 is DXE core started and POST code F1 is a forced recover condition forced by the user.

yes i read that in the manual..any ideas what these mean and how to remedy the problem(s)? thanks in advance btw

[Nw0rb]

I can't be certain, and probably only AMI truely know the full meaning of their POST codes but F1 is probably triggered by a failed OC attempt... or maybe when the UEFI detects applied overclock settings. I'd have to ask my contacts if they know more to give a fuller answer. I've never seen POST code F1 on my Extreme4 unless its been a failed OC attempt. Have you tried lowering your multi to say 46 and seeing if you still get the problem?

Funny thing is I have and it only seems to happen when pll is enabled.... almost seems the extreme6 is having trouble maybe starting with pll over voltage like its not using it properly because even when its enabled i can boot in fine it just seems to happen on a cold boot and its kinda random. thats why i said it might be a problem with pll enabling at post

[Ket]

Hmm.. well by the way you describe your specific problem it could be a issue with the UEFI or the board you have being a bit quirky. Is it possible for you to exchange your Extreme6 for another and see if you still get the problem?

[Nw0rb]

Hmm.. well by the way you describe your specific problem it could be a issue with the UEFI or the board you have being a bit quirky. Is it possible for you to exchange your Extreme6 for another and see if you still get the problem?

Heh funny thing is it was doing it on the b2 board I now have the b3 board i got about a month ago now or more and it has the same problems. So i really think it has to do with the uefi/bios to be honest. Really wish they would give you a board to work with... seeing a lot of people complain of the same problems that you were so kind to help fix on the extreme 4

[Nw0rb]

And f1 means F1 - Recovery condition triggered by user (Forced recovery)
what does that mean exactly ? i wish they had a discription does it mean not enough vcore or is it just an error when tryin to enable pll over voltage during post i really dont know

[Ket]

I have mentioned the Extreme6 problems to one of my contacts, whats done with the information from there is a little out of my hands. I do know R&D are really busy atm so its probably something they have put a pin in on their boards. Think of me as a front-line medic, I'll cure what I can but anything I can't I have to take to higher ups to look at As for the F1 POST code, as I said in my other post beyond what I already said I would have to ask one of my contacts about maybe they know more but its likely only AMI know the full meanings of their UEFI POST codes.

[pythonse]

ami? im assuming since ur the frontline medic ami means advanced medic? let me know if u find anything out

[Ket]

AMI = American Megatrends, their the crazy clever people behind most BIOSes / UEFIs people use I'm good at pretty much anything PC but even I get queasy thinking about how complicated writing UEFI / BIOS code from scratch is

[Ket]

Some information owners of B3 Extreme4/6s might find interesting.

After another of one of my little chats with one of the Asrock contacts I know he was able to offer a perspective I had forgotten about (yes even I forget things sometimes ) With the new B3 stepping of the P67 chipset as I'm sure most will remember intel revised the SATA controller. Its entirely possible that during that revision changes were also made to varying paramaters relating to the SATA controller and as such the blinking cursor problem could be down to trouble detecting devices on the controller under certain OC conditions. To extend on my contacts thoughts users suffering from this problem could try switching to the SATA3 ports and see if that solves the problem.

Hope that helps guys

[mean6]

Some information owners of B3 Extreme4/6s might find interesting.

After another of one of my little chats with one of the Asrock contacts I know he was able to offer a perspective I had forgotten about (yes even I forget things sometimes ) With the new B3 stepping of the P67 chipset as I'm sure most will remember intel revised the SATA controller. Its entirely possible that during that revision changes were also made to varying paramaters relating to the SATA controller and as such the blinking cursor problem could be down to trouble detecting devices on the controller under certain OC conditions. To extend on my contacts thoughts users suffering from this problem could try switching to the SATA3 ports and see if that solves the problem.

Hope that helps guys

Already am using those ports with my current configuration. So, don't think that is the issue.

[Ket]

Have you tried disconnecting your SATA devices and trying a standard HDD? Just trying to narrow down the root cause of the problem

[mean6]

I haven't yet, I would have to install os onto other drive. Will try though, and get back to you.

[Ket]

ok