ASRock P67 Extreme4 B3 needs BIOS 3.21A or higher
Printed From: ASRock.com
Category: Technical Support
Forum Name: Intel Motherboards
Forum Description: Question about ASRock Intel Motherboards
URL: https://forum.asrock.com/forum_posts.asp?TID=3973
Printed Date: 23 Jul 2025 at 4:48am
Software Version: Web Wiz Forums 12.04 - http://www.webwizforums.com
Topic: ASRock P67 Extreme4 B3 needs BIOS 3.21A or higher
Posted By: mrtoad
Subject: ASRock P67 Extreme4 B3 needs BIOS 3.21A or higher
Date Posted: 08 Dec 2016 at 8:31am
|
" rel="nofollow - When I go from a GTX 760 to an R9 Fury I get a "console device" error code and black screen, no post. Apparently this is a known issue with p67 boards. Finding lots of posts from people online with MSI boards, Gigabyte boards that were able to download a BIOS update to fix it. For some reason, ASRock has a beta bios update that does fix this (3.21a from what I found online) but the only way to get is to personally request it via their support. Does anyone know where I can download this? Why this can't be posted on their bios page is beyond me. Thank you
|
Replies:
Posted By: wardog
Date Posted: 08 Dec 2016 at 9:24am
|
" rel="nofollow - I have the P67 Extreme4 (non B3 non GE3) L3.21 BIOS here I can link to. All I can Google of the B3 board is it was released due to SATA issues and it was released between the Extreme4 and the Extreme4 GEN3. The GEN3 looks diff in only that it supports PCIe 3.0 If you wish to take full responsibility and understand the risks PM me with your email addy and I'll link you to 3.21A Otherwise, contact ASRock Tech Support and request it: http://event.asrock.com/tsd.asp Also, what CPU is it you're using currently? Be aware of the notice on the official 3.10 BIOS on the boards BIOS page: http://www.asrock.com/mb/Intel/P67%20Extreme4/?cat=Download&os=BIOS |
Posted By: wardog
Date Posted: 08 Dec 2016 at 10:06am
|
I think you're motherboard is running on it's last legs as far as being able to update it component wise. I jut looked in the 3.21A compressed archive file and in it is a txt that states it addresses "Support Nvidia 7xx series VGA". From the 7xx series to the latest R9 Fury might be asking too much of your admittedly older motherboard. Please inquire of ASRock Tech Support. |
Posted By: parsec
Date Posted: 08 Dec 2016 at 10:53am
|
" rel="nofollow - Among other things, wardog is referring to the Sandy Bridge to Ivy Bridge compatibility UEFI/BIOS update. If that is not done correctly, and the newer, required drivers are not installed (Intel IME software is critical!) you'll have problems trying to OC. What BIOS version are you using now? Also, you have the P67 Extreme4 Gen3 board? Which you are calling B3, which I understand, but being exact is important. Your board might not be able to flash to the BIOS wardog has for you. The BIOS update program simply checks the names of the board in the current and new BIOS files, if they don't match, no update will be allowed. A safety feature but a drawback in a very few extreme cases. The UEFI version for the P67 Extreme4 Gen3 that has Ivy Bridge processor support is version 2.10. Check the Ivy Bridge support FAQ on this page: http://www.asrock.com/mb/Intel/P67%20Extreme4/?cat=FAQ OTOH, if the boards are not IDENTICAL in hardware and UEFI options, then flashing a non-matching BIOS version is not a good thing. I'm surprised the P67 Extreme4 does not show PCIe 3.0 support in the specs. That's what an Ivy Bridge i5 or i7 processor brings to the system. Unless there is a bandwidth limitation caused by the build quality of the PCIe slots or PCIe lane traces on the board. ------------- http://valid.x86.fr/48rujh" rel="nofollow"> 
|
Posted By: wardog
Date Posted: 08 Dec 2016 at 11:48am
" rel="nofollow -
Nope. ASRock did introduce a P67 Extreme4 B3 board. Though I don't find it listed among all the links I'm aware of on the ASRock site. http://www.tomshardware.com/forum/299292-30-asrock-extreme-gen3 https://pcpartpicker.com/product/GLmLrH/asrock-motherboard-p67extreme4b3 http://www.newegg.com/Product/Product.aspx?Item=N82E16813157229 |
parsec wrote: