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

[radier]

http://www.pctreiber.net/forum/index....0;attach=1442

[papatsonis]

Anyone who hasnt upgraded to IVY support UEFI, and willing to do a small beta testing for the new modded AXTU version, plz pm me ( i need someone with MEI 7.0 to test it)

[papatsonis]

Updated version for newer UEFIs, i still need someone with older UEFI to test it

[GregoryDonner]

Ket, as WillyG noticed on overclock.net, ASRock appears to have dropped both DOS and UEFI-based update mechanisms for their new UEFIs in favor of the Windows-only route. By chance, do you have any idea why this is? (not complaining--just curious)?

It seems a little odd, seeing as ASRock was touting their UEFI-based update as a better/faster way to get it done.

[radier]

Windows flash tool now checks if board is B3.

If it is B2 UEFI update is impossible.

[pkdick]

Hello everyone,

I would like to share one information that you may not be aware of: I succeeded in getting my Rapidstart partition recognized in my P67 extreme6 bios (2.10 version) ! My problem was that I have 12 Gb memory installed and that the Asrock Rapidstart utility is apparently only able to create 8 GB partitions: as soon as I modified the partition size (using Intel Rapidstart manual) to 12 GB, it was recognized in my bios !

I hope this information will useful to you...

[mean6]

Hi, hope someone out there can help. I updated to the new uefi bios on my p67, and now I cannot overclock. In the bios I set the multi to 46, but as soon as I click to change something else, it defaults to 37 which is the highest it will allow for. It does this for any value I try and change. Also now, it only detects 8 gig of the 12 gig that I have. I tried reverting back to an older bios but it will not let me. I have tried the full cmos clear, and no luck. Please help.


Also to add, it only gives me the option to run the ram at 1066 or 1333. Just found another thread where some other people are having the same issue. http://forums.tweaktown.com/asrock/4...-p67-pro3.html. Sounds like I need to replace the bios chip. Any recommendations of where to get one? Ebay?????

[GripS]

Hi, hope someone out there can help. I updated to the new uefi bios on my p67, and now I cannot overclock. In the bios I set the multi to 46, but as soon as I click to change something else, it defaults to 37 which is the highest it will allow for. It does this for any value I try and change. Also now, it only detects 8 gig of the 12 gig that I have. I tried reverting back to an older bios but it will not let me. I have tried the full cmos clear, and no luck. Please help.


Also to add, it only gives me the option to run the ram at 1066 or 1333. Just found another thread where some other people are having the same issue. http://forums.tweaktown.com/asrock/4...-p67-pro3.html. Sounds like I need to replace the bios chip. Any recommendations of where to get one? Ebay?????

Your board should have a 2 year warranty on it. I would suggest an RMA.

[mean6]

Your board should have a 2 year warranty on it. I would suggest an RMA.

I would, but I can't go without a computer while waiting for the replacement. Anyone else have any suggestions?

[bat4]

I would, but I can't go without a computer while waiting for the replacement. Anyone else have any suggestions?

Have you seen papatsonis post on pctreiber.net?

I wanted to "burn" a bit my sb this weekend and just now i realized that i had a max applicable multi of 48.. even if i use 50x for example.. it boots ok.. the small boot info says 5000 but.. the reality is that in windows... i get only 48x... .
One may comment that "48x is fine.. you won't work the cpu everyday at 4800" and might be correct as i use it default all the time.. BUT when I WANT to o/c it to bench.. i want it to work... as it should :p

any other user with P67 Extreme4/6, Fatal1ty Prof/Perf to notice this?

update : it seems as a very strange issue, i started with all power saving options, enabled at 1st.. and booted correctly, disabled them 1 at a time and boot, and finally booted correctly with all these disabled(like my 1st attempts) and with higher multi than 48...

If nothing helps, maybe you can order a new chip from Asrock.
(In case of Asus motherboards I know that it is possible to order BIOS chips, perhaps Asrock does the same.)

[radier]

P67 Pro3 UEFI 3.20
http://www.asrock.com/mb/Intel/P67%2...ownload&o=BIOS

P67 Performance UEFI 2.20
http://www.asrock.com/mb/Intel/Fatal...ownload&o=BIOS

P67 Extreme4 Gen3 UEFI 2.20
http://www.asrock.com/mb/Intel/P67%2...ownload&o=BIOS

1. Add Dehumidifier Function.
2. Modify for Windows8 shut down behavior.

[xdan]

Does anyone have IB on P67 PRO3 and share some information?
I want to know how overclock works with IB...
Because on many old P67/Z68 MB(even Gigabyte/Msi) rumour is that with 3570k/3770k the multiplier it's blocked at 38X

[radier]

I can tell you that on P67 Performance it works without problems.

[FTA7700]

Hi, guys I have a pretty annoying issue on P67 Extreme4 B3 after flashed with 3.10. Mobo was with 1.60 uefi and exept inability sometimes to boot my HDD, and little higher vcore needed for oc, I had no problems. Exactly becasue those two, I decided to flash the new bios (and to see if higher clock is possible of course). And the problem started immediately. PC hangs all the time for a minute or so, on the logo screen. Then for another on a black screen with the blinking dash prior to load windows. I couldn't even reenter my OC back, it will took me all week just to restart several times. And apart from that, such behaviour is not normal. So, I flashed to L3.04 - the same again. Can't flash with 3.12, because the uefi utility can't see the file. Reverted back to 1.60, then 1.62 and 2.10. Everything is fine, exept the error with "HECI pointer mismatch" and the other "error! system cannot get fw version!", but anything else is fine, booting fast, like before. And also, by mine observations the new uefi 3.XX shows incorect frequency and voltage values. I sent all the info to Asrock before 3-4 days, they didn't responded yet, so Im asking here if someone has expirienced similar things. And is it possible to remove the error when rolling back to earlier uefi versions?

P.S. When hanging occur the mobo display shows code 64. Also the CPU is 2500k

[radier]

You f***** you BIOS chip by reverting to older UEFI version after flashing 3.10.
It was said not to do it !!!!!

[FTA7700]

I can always flash to 3.10 again, or something from 3.XX. Did it several times, nothing changing - as I described, the problem is hanging for long time. Actually even with the error messages the old bioses are doing better, than new ones. But Im surprised, the rom can't be actually wiped out completely. Any suggestions?

[Ket]

To start with I would suggest you try flashing to a known good UEFI version for your system but do NOT use instant updated to do it, get the version for pure DOS and update your UEFI like that. After the update is complete, restart your system, load setup defaults, save and exit. Shut the system down and do a full CMOS reset, then power up and update to the latest UEFI.

[FTA7700]

OK, here is what I did. Flashed uefi 2.10 (1.60 is removed from the 1st post), with turnig off, unpluging, clearing cmos, etc. as I always do. Then, powered on and loaded the default settings. Flashed to 3.10 with the win setup, the clearing procedure again, loading defaults.. and still the same hangs with code 64 ~ 45secs on the logo and another 20 with blinking dash. So, of course I rolled back to 2.1, where despite the errors I recive no hangs and such sh*ts. Also in 3.10 the XMP profile is incorect (I saw someone mention that here). Any ideas, what could interfere (if any), so there are hangs in post with v.3.XX? Missing something? And why I can't see the v.3.12 in uefi flash utility from radier's link? Asrock didn't responded for 1 week yet.

[Ket]

It sounds like you probably have some faulty hardware, assuming when you flashed the UEFI you done it flashing from pure DOS and not instant update.

[FTA7700]

Yep, I flashed with dos version of 2.1. And, what kind of hardware, when Im rendering with that system - CPU and GPU both, which means max load, memory too (12GB). But my clock/system never have/had any problems since it passed the last tests year and so ago (24/7 usage since then). CPU is at default right now, first time since I boughted when it came out. So, I don't suspect for any problems, exept the recent - uefi related ones. The situation right now is fast loading system with no problems. The only problem is the HECI error, which make the mouse unusable in uefi. So I think the 3.XX uefis are those with problems for some systems.

[Ket]

Have you tried disconnecting all optical and physical drives along with any non essential devices such as mice and wireless adapters to see if you get the error still? As you are getting errors regardless of UEFI version its unlikely that theres anything wrong with the UEFIs. As a last ditched attempt it may be worth trying a new ROM chip, your issue still deffinately sounds like a hardware problem.

[FTA7700]

I have 1 HDD and no CD/DVD. 1 classic Compaq PS/2 keyboard and MX518 USB mice. 'll try to disconnect the mouse and I have 1 wireless dongle, will disconnect it too and see. Isn't the HECI error about wrong version of MEI on the uefi rom? The error is with 1.XX and 2.XX versions, which otherwise are working flawlessly (exept the mentioned in my case already). The error is not present on 3.XX, but I have mandatory hangs on it, and there are wrong XMP profiles -which doesn't bother me, but there are wrong value readings as well (IMHO). Furthermore, I think Asrock can't be unaware of that, they definately know for the HECI error, after rollbacks to earlier uefis. Probably they don't know how to fix it yet, or don't want to. That's why they don't responded on my problem. And the hangs in 3.XX are (I think) random Incompatibilities with some mobos, pending to be cleared (hopefully) in the next versions.

---
New developments:

First on the advice of unplugging anything to check if the issue with hanging with 3.XX will disapear. There is only the mouse and a wi-fi dongle. I unplugged them and.. same hangs. So, I abandon the 3.XX until those problems are figured out.
The interesting is the development in the problem with the two errors "error! system cannot get fw version!" and "heci pointer mismatch" ater the rollback from 3 to earlier. In the meantime of the fore-mentioned experiments I was with V.2.1, and decided to manualy downgrade the Intel management engine interface driver in windows, just to see what will happen. I was with 7.1.40.1161, which I downgraded from 8.0 earlier. Deleted the old one and Windows installed automatically ver. 7.0.0.1114. Then I flashed uefi to v.2.1H - I already tryed that version, but now just decided to stay with it for now. Restarted, the system turned off, turned on, posted, shuted down again, posted again and after the post screen updated the ME on the rom chip, restarted again and... no more errors with 2.XX uefi. I can't repeat the exact procedure, but obviously it is possible to rollback between 1.xx, 2.xx and 3.xx without errors. After loading windows I noticed, the ME driver version is updated to 7.0.0.1118. Now I have completely normal post and OS loading without any errors. Just a small glich - the mouse directions in uefi are turned upside-down, but don't care. Now Im clocking back.

[mean6]

I have 1 HDD and no CD/DVD. 1 classic Compaq PS/2 keyboard and MX518 USB mice. 'll try to disconnect the mouse and I have 1 wireless dongle, will disconnect it too and see. Isn't the HECI error about wrong version of MEI on the uefi rom? The error is with 1.XX and 2.XX versions, which otherwise are working flawlessly (exept the mentioned in my case already). The error is not present on 3.XX, but I have mandatory hangs on it, and there are wrong XMP profiles -which doesn't bother me, but there are wrong value readings as well (IMHO). Furthermore, I think Asrock can't be unaware of that, they definately know for the HECI error, after rollbacks to earlier uefis. Probably they don't know how to fix it yet, or don't want to. That's why they don't responded on my problem. And the hangs in 3.XX are (I think) random Incompatibilities with some mobos, pending to be cleared (hopefully) in the next versions.

---
New developments:

First on the advice of unplugging anything to check if the issue with hanging with 3.XX will disapear. There is only the mouse and a wi-fi dongle. I unplugged them and.. same hangs. So, I abandon the 3.XX until those problems are figured out.
The interesting is the development in the problem with the two errors "error! system cannot get fw version!" and "heci pointer mismatch" ater the rollback from 3 to earlier. In the meantime of the fore-mentioned experiments I was with V.2.1, and decided to manualy downgrade the Intel management engine interface driver in windows, just to see what will happen. I was with 7.1.40.1161, which I downgraded from 8.0 earlier. Deleted the old one and Windows installed automatically ver. 7.0.0.1114. Then I flashed uefi to v.2.1H - I already tryed that version, but now just decided to stay with it for now. Restarted, the system turned off, turned on, posted, shuted down again, posted again and after the post screen updated the ME on the rom chip, restarted again and... no more errors with 2.XX uefi. I can't repeat the exact procedure, but obviously it is possible to rollback between 1.xx, 2.xx and 3.xx without errors. After loading windows I noticed, the ME driver version is updated to 7.0.0.1118. Now I have completely normal post and OS loading without any errors. Just a small glich - the mouse directions in uefi are turned upside-down, but don't care. Now Im clocking back.

Hey FTA7700, I was having the exact same problems as you after flashing to 3.04 or whatever it was. My previous posts are above. I had those issues, in addition, I was not able to overclock with a multi higher than 37, and the ram options were only 1066/1333. I also had the errors you had after trying to downgrade (which you are told not to). I tried everything, and nothing would get my system to recognize more than 8 gig of ram, or allow for high overclocks. I resolved my issue by purchasing a new bios chip with 2.0 preflashed onto it. It cost me about $16 on ebay. It just arrived, and took 2 seconds to install, and now everything is good. Overclocked, and ram is running as it should be. Hope this helps.

[FTA7700]

So, obviously the 3.XX are problematic in some cases. Although, my problems was with hangs (something like timeouts) with constant duration. Of course, as I mentioned I saw strange readings and fluctuations in frequencies and voltages and wrong XMP. The multiplier selector was fine by my opinion. But, in the memory settings for frequency one could see numbers like 1336mhz, 1674mhz and such nonsence. The thing with the new bios chip is good idea. But as I wrote, my problem is solved I have no error messages anymore. The real problem is Asrock are silent as a fish about that, and official way of rolling back to earlier uefis. Thanks for posting.

[Ket]

New developments:

First on the advice of unplugging anything to check if the issue with hanging with 3.XX will disapear. There is only the mouse and a wi-fi dongle. I unplugged them and.. same hangs. So, I abandon the 3.XX until those problems are figured out.
The interesting is the development in the problem with the two errors "error! system cannot get fw version!" and "heci pointer mismatch" ater the rollback from 3 to earlier. In the meantime of the fore-mentioned experiments I was with V.2.1, and decided to manualy downgrade the Intel management engine interface driver in windows, just to see what will happen. I was with 7.1.40.1161, which I downgraded from 8.0 earlier. Deleted the old one and Windows installed automatically ver. 7.0.0.1114. Then I flashed uefi to v.2.1H - I already tryed that version, but now just decided to stay with it for now. Restarted, the system turned off, turned on, posted, shuted down again, posted again and after the post screen updated the ME on the rom chip, restarted again and... no more errors with 2.XX uefi. I can't repeat the exact procedure, but obviously it is possible to rollback between 1.xx, 2.xx and 3.xx without errors. After loading windows I noticed, the ME driver version is updated to 7.0.0.1118. Now I have completely normal post and OS loading without any errors. Just a small glich - the mouse directions in uefi are turned upside-down, but don't care. Now Im clocking back.

Thats why I suggested flasing the UEFI from pure DOS with the first release UEFI Doing that will "kick" the flash process into downgrading the MEI (or it should do as from pure DOS a complete ROM erase-rewrite happens) so when you then upgrade to the latest UEFI the MEI should also be updated properly. Cases like this are why I keep prodding Asrock to have a backup ROM chip, but thus far its not happened so its always a good idea to have a spare ROM chip handy to just switch to.