ASRock.com Homepage
Forum Home Forum Home > Technical Support > Intel Motherboards
  New Posts New Posts RSS Feed - Unsure whether I should update UEFI
  FAQ FAQ  Forum Search Search  Events   Register Register  Login Login

Unsure whether I should update UEFI

 Post Reply Post Reply
Author
Message
hryelle View Drop Down
Newbie
Newbie


Joined: 12 Oct 2016
Status: Offline
Points: 6
Post Options Post Options   Thanks (0) Thanks(0)   Quote hryelle Quote  Post ReplyReply Direct Link To This Post Topic: Unsure whether I should update UEFI
    Posted: 12 Oct 2016 at 12:23pm
My rig: Asrock Z87 Extreme4, i5 4690k, GTX 1080

On Saturday I had a weird problem relating to upgrading my GPU. After much frustration , a mate suggested and assisted with entering my board's back up UEFI and restoring the main UEFI  with the backup, then reloading the restored UEFI. This solved my problem. However, the restored UEFI is now the backup version which I believe is the factory default (p2.6). I was using version p3.0 previously. The Asrock website implies that p2.6 does not support my CPU, yet I am able to post, boot to windows 10, game and do everything normally. The p2.6 UEFI lists i5 4690k as the CPU along with the expected clocks (3.5 GHz stock, 3.9 GHZ turbo), and stress tests confirm this. So, I'm unsure as to whether I should update the UEFI (if so to what version), and if continuing to use p2.6 could cause problems or maybe is not optimal for my current system? I then thought maybe I couldn't instant flash to p3.0 or later because the current version doesn't technically support my CPU. Is this correct? Any advice would be really appreciated!
Back to Top
parsec View Drop Down
Moderator Group
Moderator Group
Avatar

Joined: 04 May 2015
Location: USA
Status: Offline
Points: 4996
Post Options Post Options   Thanks (0) Thanks(0)   Quote parsec Quote  Post ReplyReply Direct Link To This Post Posted: 12 Oct 2016 at 1:10pm
Originally posted by hryelle hryelle wrote:

My rig: Asrock Z87 Extreme4, i5 4690k, GTX 1080

On Saturday I had a weird problem relating to upgrading my GPU. After much frustration , a mate suggested and assisted with entering my board's back up UEFI and restoring the main UEFI  with the backup, then reloading the restored UEFI. This solved my problem. However, the restored UEFI is now the backup version which I believe is the factory default (p2.6). I was using version p3.0 previously. The Asrock website implies that p2.6 does not support my CPU, yet I am able to post, boot to windows 10, game and do everything normally. The p2.6 UEFI lists i5 4690k as the CPU along with the expected clocks (3.5 GHz stock, 3.9 GHZ turbo), and stress tests confirm this. So, I'm unsure as to whether I should update the UEFI (if so to what version), and if continuing to use p2.6 could cause problems or maybe is not optimal for my current system? I then thought maybe I couldn't instant flash to p3.0 or later because the current version doesn't technically support my CPU. Is this correct? Any advice would be really appreciated!


First of all, the UEFI version number from the factory is on a sticker of the UEFI chips, which are just above the board's battery, in the lower right corner of the board.

Also, the backup UEFI version cannot be changed, so if it was 2.60 from the factory, that is what you now have. The Main screen of the UEFI shows the installed UEFI version.

I don't know why you think UEFI 2.60 does not support your processor. It actually does, and I think I might know why you are confused.

An i5-4690K is a Haswell Refresh processor model. If we check the description of UEFI 2.60 we find:

Support New 4th Generation Intel Core Processors. That's your type of processor, New 4th Gen are Haswell Refresh.

Why the CPU support list shows P2.70, I don't know, the description is one fix to a C-State register, might be a typo.

Now check closely the description for UEFI 3.00:

Support i7-4790K, i5-4690K and Intel Pentium G3258 EZ OC.

UEFI 3.00 adds support for the processor listed to the EZ OC feature. It does NOT add basic support for those processors, which was done in UEFI 2.60. This seems to be what you are confused about.

If the UEFI in your board did not support your CPU, the board would appear almost dead when you tried to start it. Nothing will show on the monitor. You'll get a dead CPU code in the Dr Debug display. Your PC functions normally, right?

It looks like the latest UEFI, 3.40, adds compatibility for PCIe (video) cards. Why going back to an earlier version of the UEFI fixed the issue with your video card, is strange.
Back to Top
hryelle View Drop Down
Newbie
Newbie


Joined: 12 Oct 2016
Status: Offline
Points: 6
Post Options Post Options   Thanks (0) Thanks(0)   Quote hryelle Quote  Post ReplyReply Direct Link To This Post Posted: 12 Oct 2016 at 3:04pm
I actually realised I misread it about an hour after submitting hahaha, for the same reasons you mentioned! I feel pretty stupid. However, the CPU list for my mobo does say that i5 4690k is supported since 2.7 - as you saw too. So I guess 2.7 might be optimal/use less power or something? 

Yep, computer functions normally. I was just wondering if I should flash to 2.7 or later, or just stay with 2.6 as it's working fine (so far). 

The full story: I had an r9 280x. I uninstall the driver using control panel. I'll admit I noticed it hung during the uninstall forced restart but thought nothing of it. Power down and unplug components of computer. Install new GTX 1080. Computer won't even post and get codes 4f, 15 and 19. Reseated GPU and replugged in GPU power connectors numerous times to no avail. Tried testing RAM sticks and still no cigar. Now I remember I had a 4.3 GHz overclock to CPU going which I did forget to remove before installing the new GPU so that could have contributed to this debacle. After walking away to get a drink, computer decides to actually post, so I remove the over clock in BIOS. Then it boots! Yay I think, so install new NVIDIA drivers. Then I restart PC to see if it was a fluke. It was. Same problems as before with cycling 4f 15 and 19 error codes. Flatmate now suggests resetting CMOS, did that, but it seemingly made the situation worse and I got code 00. At this point my mate does the backup/restore bios thing and everything is fine. 


Edited by hryelle - 12 Oct 2016 at 3:05pm
Back to Top
 Post Reply Post Reply
  Share Topic   

Forum Jump Forum Permissions View Drop Down

Forum Software by Web Wiz Forums® version 12.04
Copyright ©2001-2021 Web Wiz Ltd.

This page was generated in 0.328 seconds.