Extreme9 BIOS bugs in 1.70

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

   990FX Extreme 9                           P1.70                      MOD P1.70
_____________________________________________________
OROM AMD ACHI 4391                  3.0.5                        3.3.0.0
OROM AMD RAID MISC 4392         3.2.1540.6               3.3.1540.19
OROM AMD RAID MISC 4393         3.3.1540.11             3.3.1540.19
EFI AMD RAID                               1.0.0.49                   1.0.0.49
EFI AMD Utility                              1.0.0.49                   1.0.0.49
LAN OROM Intel PXE                    1.3.95                       1.5.72
LAN EFI Intel UNDI                       4.8.01                       6.6.04
ASMEDIA OROM 1061                   0.93                          0.951
EFI AMD AGESA OrochiPI              1.2.9.0                      1.2.9.0

Feel free to use a MOD BIOS that I use. 
The file is InstantFlash, and I use it on a daily base.
You can always revert to normal P1.70,
but I doubt You will ever do this.

The AMD AHCI 4391 does make the most difference in SATA3 speed when using a SSD.
If also fixes the BUG when You use a Samsung 840 EVO/850 EVO, and have a
cold-boot "black screen" BUG, and after a hot-restart, everything works fine.

BIOS:
https://app.box.com/s/2nnqqe4274fx4v5uy1bmm46l6t0eqemv

CRC check:
https://app.box.com/s/hxpg29663diu3v6j918xalpc9ki18d6w

So to sum up, it is an Official P1.70 BIOS with updated manufacturers ROM's.
Nothing else is moded.

Edited by ASRock Expert - 29 Nov 2015 at 4:36am

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
ASRock Expert Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 04 Oct 2015 Location: Croatia Status: Offline Points: 220	Post Options Post Reply Quote ASRock Expert Report Post Thanks(1) Quote Reply Posted: 31 Oct 2015 at 5:27pm
	990FX Extreme 9 P1.70 MOD P1.70 _____________________________________________________ OROM AMD ACHI 4391 3.0.5 3.3.0.0 OROM AMD RAID MISC 4392 3.2.1540.6 3.3.1540.19 OROM AMD RAID MISC 4393 3.3.1540.11 3.3.1540.19 EFI AMD RAID 1.0.0.49 1.0.0.49 EFI AMD Utility 1.0.0.49 1.0.0.49 LAN OROM Intel PXE 1.3.95 1.5.72 LAN EFI Intel UNDI 4.8.01 6.6.04 ASMEDIA OROM 1061 0.93 0.951 EFI AMD AGESA OrochiPI 1.2.9.0 1.2.9.0 Feel free to use a MOD BIOS that I use. The file is InstantFlash, and I use it on a daily base. You can always revert to normal P1.70, but I doubt You will ever do this. The AMD AHCI 4391 does make the most difference in SATA3 speed when using a SSD. If also fixes the BUG when You use a Samsung 840 EVO/850 EVO, and have a cold-boot "black screen" BUG, and after a hot-restart, everything works fine. BIOS: https://app.box.com/s/2nnqqe4274fx4v5uy1bmm46l6t0eqemv CRC check: https://app.box.com/s/hxpg29663diu3v6j918xalpc9ki18d6w So to sum up, it is an Official P1.70 BIOS with updated manufacturers ROM's. Nothing else is moded. Edited by ASRock Expert - 29 Nov 2015 at 4:36am
	990FX Extreme 9 MOD P1.70 AMD FX 8120 4GHz 1.25V Thermalright HR-02 Patriot Viper 2x4GB 2133MHz Samsung 850 EVO 250GB MSI R7970 TFIII 3GB CORSAIR VX550W LanCool K62 Dragonlord ASUS Xonar D2X

parsec Members Profile Send Private Message Find Members Posts Add to Buddy List Moderator Group Joined: 04 May 2015 Location: USA Status: Offline Points: 4996	Post Options Post Reply Quote parsec Report Post Thanks(0) Quote Reply Posted: 31 Oct 2015 at 3:13pm
	Don't worry about the wrong forum, many other people have done the same thing. As long as you are aware of it, I'm happy. I'm not up to speed on the UEFI bugs you listed, and just want to review them with you. 1. Reversed LLC setting vs result. I don't have your board but I believe you about this. I've seen this before in general with the UEFI of other ASRock boards, Intel processor boards in my experience. The bug is the lowest or zero LLC compensation setting is actually the highest LLC compensation, correct? Conversely, the highest LLC setting is actually the lowest or zero LLC compensation. This bug seems to stay with ASRock like a bad, lingering cold, very hard to get over and never seems to go away. I suppose the thinking about this is as long as the user knows what the result of a setting is, the name for it is not important. Or it is thought that you and others are wrong. The former is no excuse IMO, and could damage an inexperienced users processor. No one wants a car with a speedometer that reads 0 when the car is at 100MPH, and vice versa. I also think you would like more than just fixing the setting vs actual value situation. The spikes in voltage you mention could be caused by a benchmark starting a particular test, like AVX instructions. What is AOD, that acronym is not expanding in my mind. 2. Wake from Sleep clock and voltage changes. This is another fairly common issue that affects all hardware platforms. I know of fixes for this for Intel boards by ASRock and other manufactures. Do you have AXTU running when you start the PC, and when you go into Sleep mode? 3. What are you using as the VCore mode and value? Such as, manual VCore at 1.500V. Do you have CPU power saving options enabled? What is the processor minimum state set to in your Windows Power Plan?


DedEmbryonicCe11 Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 31 Oct 2015 Status: Offline Points: 6	Post Options Post Reply Quote DedEmbryonicCe11 Report Post Thanks(0) Quote Reply Posted: 31 Oct 2015 at 1:18pm
	Sorry wrong forum by accident. Could a mod move this to Technical support please?

DedEmbryonicCe11 Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 31 Oct 2015 Status: Offline Points: 6	Post Options Post Reply Quote DedEmbryonicCe11 Report Post Thanks(0) Quote Reply Posted: 31 Oct 2015 at 12:00pm
	FX990 Extreme9 This has always been a solid board but there are still nagging bugs that hurt overclockers. Is ASRock willing to update the BIOS and perfect it? The platform is "dead" to future updates from AMD, but some people like myself would love to continue using it into 2016 when AMD releases their new socket/platform. 1) Countless negative experiences with the LLC bug in the BIOS. The options are mislabeled. I've submitted a report to support but no response after quite some time and the issue has been known for a year... The "100%" LLC option is actually Disabled. "Disabled" is either 75% or 100%... can't tell which. I just know that "Disabled" has CRAZY HIGH LLC voltage spikes. I'm talking set 1.425v in the BIOS with LLC at "Disabled" and it will spike as high as 1.6v running AOD stability test. It shouldn't be hard at all to rename these options correctly, right? 2) CPU-NB overclocks (and sometimes voltages!) do not persist after power state suspends in Windows. I have recently switched from Windows 7 to Windows 10 and reenabled the suspend state. This is great for a power hungry chip like a FX-9590 because the system will shut off to a trickle and I just have to click the mouse and retype my password and I'm back where I left off. The problem is that my CPU-NB overclock drops from 2400 MHz to 2200 MHz and sometimes the CPU-NB voltage drops from 1.25 to 1.125v as well! Raising the CPU-NB multiplier is not possible inside of Windows with AOD and the only way that I know of is to reboot the system. Is this a OS limitation, or is it possible for the motherboard to correctly revert to the overclock it had before suspend? 3) (see 1) With LLC disabled the core voltage sometimes dips below BIOS settings. I have 1.525v set. After a fresh reboot CPU-Z and ASRock's AXTU (v1.381.2) reports 1.520v at the moment. Half of the time I boot the voltage will be at ~1.49v and stay below the set voltage even if I try to raise it with AOD or AXTU. To clarify, any time it has dropped to ~1.49v if I set say 1.55v it won't be 1.55v... it will be 1.515v or something like that. The voltage just gets stuck some percentage below whatever you want it set at. I have seen this bug reported elsewhere (Anandtech forums for example) from last year. It should be pretty well known. Anyway, I want to reiterate that I love my system. I certainly wouldn't switch to another AM3+ motherboard since there are no new processors coming out for it anyway. I just wish these year-old bugs could be squashed by some generous BIOS engineers.