Beep codes after updating AB350 Pro4 to BIOS 4.20

datonyb wrote: ive had it since launch i was one of the first uk guys to get my hands on one its been really painless,i had my ram working at 3200 since day one (and the ram has never been on the qvl ) cpu at 3.9ghz since day one my main reasons for buying the taichi were insane overkill on the vrm and power section, and good reviews on launch my main hopes are good support and ability to use the later ryzen+ and ryzen2 cpus in a year or two time

The AB350 Pro4 was painless for me as well until now.  Had my R5 1600 running just fine at 3.8.  Corsair Vengeance running at 3200.

Tear down/rebuild did nothing.  Same beeps.

Now have to decide if I go back to this board or other.  Original plan with this build was to give it to my son once the new Ryzen's came out.

dilacerated wrote: AAAAAAAAAAAAHAHAHAHAHAHA!!!  FFS really?!??!?!? Problem solved.  Found a friend in my ranks that had a GT 210 (aka an adapter with no external power required). Put that in and presto the system booted up.  Flashed back to BIOS 3.00 using Instant Flash, DOS flashed 3.00, pulled the battery, put it back along with my RX 480 and tada! Flashed up to 3.30 and zero problems.

Glad you have the PC working, but what the true issue with the 4.20 UEFI version remains unknown. We don't know yet if your issue is isolated to the RX 480, or even the VBIOS used in your particular card. I have learned from experience in this forum that it is a mistake to come to a conclusion about an issue based upon the experience of one user. That certainly includes myself as one user's experience.

The main and likely only purpose of the 4.20 UEFI update is stated in its description:

Update AGESA to 1.0.7.2 for upcoming processors.

AGESA 1.0.7.2 is the AMD AM4 processor microcode that is part of the UEFI/BIOS file. It is supplied to mother board manufactures by AMD. This AGESA update is known to require major changes in other UEFI code. That might be the source of the problem, or the AGESA update itself, which is a scary thought.

I don't understand the implication that a video card that does not need extra power from the PSU is the reason it worked with the new UEFI version. If that were true, we would be seeing many other posts about issues like yours with this board and UEFI version. So far, hasn't happened. It also indicates that all video cards are not affected.

But your experience with an RX 480 and the 4.20 UEFI version is one data point that we will remember for future reference.

parsec wrote: Glad you have the PC working, but what the true issue with the 4.20 UEFI version remains unknown. We don't know yet if your issue is isolated to the RX 480, or even the VBIOS used in your particular card. I have learned from experience in this forum that it is a mistake to come to a conclusion about an issue based upon the experience of one user. That certainly includes myself as one user's experience.

Got an email from ASRock's support this morning and offered to provide them the VBIOS of my card.  Haven't heard back.  Whatever the cause maybe I am the lone person to encounter this but other users are not the troubleshooting types (see user reviews on every etailer) so who knows.

parsec wrote: I don't understand the implication that a video card that does not need extra power from the PSU is the reason it worked with the new UEFI version. If that were true, we would be seeing many other posts about issues like yours with this board and UEFI version. So far, hasn't happened. It also indicates that all video cards are not affected. But your experience with an RX 480 and the 4.20 UEFI version is one data point that we will remember for future reference.

My reasoning for trying a card without external power was due to my RX 480 clearly getting power from the PCI-E slot as the fans powered on with the system.

parsec wrote: The main and likely only purpose of the 4.20 UEFI update is stated in its description: Update AGESA to 1.0.7.2 for upcoming processors. AGESA 1.0.7.2 is the AMD AM4 processor microcode that is part of the UEFI/BIOS file. It is supplied to mother board manufactures by AMD. This AGESA update is known to require major changes in other UEFI code. That might be the source of the problem, or the AGESA update itself, which is a scary thought.

I'll work with ASRock support and get them whatever data they need.  I responded to the email from them within five minutes and then five to six business hours went by without a followup...  I'm also going to post this issue in AMD's forum given that the AGESA microcode comes from them (I knew that).  For now, though, I am back to loving my machine that I had feared I'd lost.

The same issue with my AB350 Pro4.