ASRock AB350(M) Pro4 UEFI (Newest 4.50)

[VirtualLarry]

I saw that there was new UEFIs for my board. So I downloaded 3.40, and 4.30, and then unzipped them (on a laptop), and put them both on a flash drive. I installed 3.40 using instant flash, rebooted, cleared settings, rebooted, installed 4.30, and then let it reboot, and then... I can't get into UEFI any more. Even with using the Windows 10 feature to get to UEFI on next reboot. I just get a black screen. I have two video cards, but I've never had a problem accessing the UEFI on the primary card. Not quite sure what's going on here, unless I've been trojaned, and thus, blocking me from installing any other UEFI from now on, and stealing my passwords, etc.

 

[XavierMace]

Have you cleared the CMOS after the 4.30 update?

 

[VirtualLarry]

I seem to have gotten access again to the UEFI.

I tried clearing the CMOS, after removing both video cards, no go. Then, I tried unplugging my USB wired gaming keyboard / mouse, and used a wireless KBD/MSE that I knew worked, and that didn't work, so then I swapped the HDMI output from my primary card (which I DID switch to a "mining BIOS" setting, some time ago, although it was also my primary video output in Windows 10), and then hit C-A-D, and then it finally came up.

Not sure if it were the keyboard, or the HDMI output / VGA card BIOS setting / interacting with the new UEFI 4.30.

I noticed for overclocking, it now gives you two options.

 

[XavierMace]

I'd say this "mining BIOS" would likely be the cause.

 

[VirtualLarry]

I'd say this "mining BIOS" would likely be the cause.

Maybe... but it was working fine for all of the UEFIs before 4.30.

 

[XavierMace]

Yeah, but your motherboards UEFI has to communicate with that BIOS. So without knowing what that "mining BIOS" changed, that would seem to be a likely cause. Can you flash it back to a normal BIOS and see if that resolves the issue?

 

[VirtualLarry]

This isn't an $8 ebay-special "mining BIOS mod", this is XFX's Official dual-BIOS, one switch for Gaming, one for Mining. I switched the switch to Mining, in an attempt to lower temps, as the Gaming setting is way overvolted / overclocked. Didn't help too much, but it overclocked the VRAM instead.

 

[DrMrLordX]

If you are using the AGESA 1.0.0.7.2 or whatever BIOS that ASRock rolled out for their B350 boards, please be advised that that is buggy. They had to pull some files because of it, and they haven't updated all their boards yet.

1.0.0.7.1 is stable.

 

[Ratman6161]

I think what we have here is another failed attempt at a BIOS from Asrock. I've got an AB350 Pro4. A while back they came out with the 4.2 which I rolled back to 3.3 because it was so buggy. On Friday I did the 3.4 "bridge bios" then the latest 4.3 (guess it was 4.2 for the M this time ... on the non-M it was 4.3). Once again buggy. A number of weird things but mainly having to do with memory overclocking. My DDR4 2400 is able to do 3066 no problem on 3.3 but had to dial it back to 2933 on 4.3. Hacked at it all weekend until this afternoon when I found the trouble. When I set the RAM voltage to my usual 1.4, no matter what I did it wasn't saving it. It kept going back to 1.2. A couple of times it mysteriously worked, but then it was running at the speed I set...but not the timings I set. Instead of the CAS 18 I set, it was running at 24. The RAM will do 2933 at 1.2 but needs the 1.4 to get higher. There were a lot of other little things as well that didn't make any sense.

So I'm back on 3.3 and all is well again.

 

[DrMrLordX]

The new AGESA versions are buggy. That may be one reason why AMD is waiting until April to launch Ryzen 2.

 

[XavierMace]

This isn't an $8 ebay-special "mining BIOS mod", this is XFX's Official dual-BIOS, one switch for Gaming, one for Mining. I switched the switch to Mining, in an attempt to lower temps, as the Gaming setting is way overvolted / overclocked. Didn't help too much, but it overclocked the VRAM instead.

Doesn't mean it's not a bad BIOS.

 

[VirtualLarry]

The new AGESA versions are buggy.

You can say that again. 4.50 is the pits! BSOD galore! (Not even overclocking CPU or RAM.)

 

[Insert_Nickname]

You can say that again. 4.50 is the pits! BSOD galore! (Not even overclocking CPU or RAM.)

Thanks for the heads up Larry. Will avoid.

(just gotten an AB350M Pro4)

 

[misuspita]

Sooo... Which one is most stable? I am waiting for a AB350M myself and would have flashed the latest, of course...

 

[VirtualLarry]

I'm running the latest 3.x0 series UEFI. The 4.x0 series seems buggy, for "classic" Ryzen CPUs. (Maybe the 4.x0 works for the APUs.)

 

[misuspita]

Thanks. I will try 3.xx when it arrives. I am pairing it with a R5 1600 and a single 8gb stick of 3000 cl16 ram because prices of ram is killing me. I will save money for another one later...

 

[VirtualLarry]

New UEFI/BIOS version 4.90 out, not beta, PinnaclePI 1.0.0.4 apparently. Running it now.

(Still won't work reliable with my 16GB Team Group Dark DDR4-2400 in XMP/2400 mode. Must be really bad-quality RAM or something.)

 

[Insert_Nickname]

(Still won't work reliable with my 16GB Team Group Dark DDR4-2400 in XMP/2400 mode. Must be really bad-quality RAM or something.)

Ryzen apparently just dislikes certain memory. I couldn't get my Crucial 2666MHz past 2400MHz on my Crosshair VI, no matter what I tried.

 

[alexruiz]

New UEFI/BIOS version 4.90 out, not beta, PinnaclePI 1.0.0.4 apparently. Running it now.

(Still won't work reliable with my 16GB Team Group Dark DDR4-2400 in XMP/2400 mode. Must be really bad-quality RAM or something.)

Wow, that is not good.
Maybe it is the RAM itself?

I have flashed 4.90 to 2 boards, and it seems very solid. In fact, DDR4-3000 finally runs now at 3000, not 2933.
Ironically, the DDR4-3000 RAM used is Team Dark... and has performed flawlessly

 

[misuspita]

I will have to test it. I have a G-Skill 3000 and could not make it work over 2666. Plus it restarts many times a day. I could not return it because I am in a middle of a project and can't stay without my pc, but is really frustrating. I hope the new BIOS rezolves that, or else I will get it to warranty