Quantcast
Channel: ASRock Forums
Viewing all articles
Browse latest Browse all 19545

Intel Motherboards : Bios 3.00 and Extreme7+

$
0
0
Author: squawker
Subject: Bios 3.00 and Extreme7+
Posted: 16 Apr 2016 at 11:55am

Hi, 

MyExtreme7+ was running without a glitch with UEFI 2.50, so, against ASRockwebsite advice i did an UEFI update to 3.00 version Tongue. 

Everythingwent smoothly, and even my M.2 raid config survived one more time biosupdating Beer. 

UEFI3.00 description says:

1. Improve FAN compatibility.

2. Support 4k native HDD.

3. Improve DRAM compatibility.

 

Andhow UEFI 3.00 does work in my system?

Item 1 with UEFI 2.50:

IfI set in ''CPU Fan 1 Type''  the setting  ''4 pin''  instead of  ''Auto'',  bootafter PSU being off caused what i called  ''triple attempt to post''  in thisthread:

http://forum.asrock.com/forum_posts.asp?TID=1793&PN=2&title=bios-250-with-microcode-fix-for-extreme-7-out:

''Summary: in my rig, what I called "triple attempt to post", in theabsence of a better name, only occurs in UEFI v. 2.50 when the "CPU Fan 1Type" is set to "4 Pin" and the PSU is off before booting.''

Item1 with UEFI 3.00

Again, If I set in  ''CPU Fan 1Type''  the setting ''4 pin''  instead of  ''Auto'', boot after PSU being off iseven worse, because instead of having the triple attempt to post, and aftergoing to OS, with 3.00 it goes to UEFI Main Menu and stays there!

 

Item3 with UEFI 2.50 and 3.00:

My board did not and does nothave any DRAM issues with both bios versions (it works at stock 2133 MHz).

 

Item2:Support 4k native HDD.

This is what induced me toupdate bios  Smile.

My rig shows in SystemInformation and in Intel Rapid Storage Technology Control Panel that it workswith 512 Bytes/Sector.

I would thanks any input aboutif this new UEFI characteristic could change anything related to SSD's behavioror performance and what is needed to put it to work in actual configs.

Regards

Viewing all articles
Browse latest Browse all 19545

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>