Beep codes after updating AB350 Pro4 to BIOS 4.20
Printed From: ASRock.com
Category: Technical Support
Forum Name: AMD Motherboards
Forum Description: Question about ASRock AMD motherboards
URL: https://forum.asrock.com/forum_posts.asp?TID=6879
Printed Date: 22 Dec 2024 at 12:23pm Software Version: Web Wiz Forums 12.04 - http://www.webwizforums.com
Topic: Beep codes after updating AB350 Pro4 to BIOS 4.20
Posted By: dilacerated
Subject: Beep codes after updating AB350 Pro4 to BIOS 4.20
Date Posted: 09 Dec 2017 at 9:06am
" rel="nofollow - Updated from 3.30 to 4.20. Previous BIOS had fTPM DISABLED...
Am hearing five beeps repeated twice which according to ASRock's FAQ that means GPU... GPU was fine and is fine.
Anyone know any trick or am I screwed?
|
Replies:
Posted By: parsec
Date Posted: 09 Dec 2017 at 1:02pm
dilacerated wrote:
" rel="nofollow - Updated from 3.30 to 4.20. Previous BIOS had fTPM DISABLED...
Am hearing five beeps repeated twice which according to ASRock's FAQ that means GPU... GPU was fine and is fine.
Anyone know any trick or am I screwed?
|
So you updated from 3.30 to 4.20 and when the PC restarted when the update was complete, that is when you heard the five beeps? Is that right or was it a different sequence of events?
Which UEFI update method did you use?
Which ASRock FAQ said that five short beeps is a GPU problem?
Searching for the AMI UEFI five beep POST error description on the Internet results consistently are a problem with the CPU, as well as add in cards (GPU), and the board itself.
https://www.google.com/search?q=ami+five+beeps&ie=utf-8&oe=utf-8&client=firefox-b
Although the 4.20 UEFI version has been available for less than a week, this is the first post about an issue like this I have seen so far.
What CPU and GPU are you using?
Are you using a TPM?
Is there anything else you can tell us about this situation?
------------- http://valid.x86.fr/48rujh" rel="nofollow">
|
Posted By: dilacerated
Date Posted: 09 Dec 2017 at 1:08pm
" rel="nofollow - FFS. Not since the 90's have I had a BIOS flash (done through DOS or Motherboard built in flash utility) destroy my Motherboard.
This was my second build with this board in the past month. I have been very happy with it and my friend with his but now, after my child goes to sleep, I get to cry beside my system tonight until I decide if I want to buy the same board and return this one for a refund.
Seriously where was the QA
here? Frankly I should have known something was going south with QA after flashing 3.30 as the BIOS "default" per the manual for SVM is enabled and yet it was disabled after updating to 3.30...
|
Posted By: dilacerated
Date Posted: 09 Dec 2017 at 1:20pm
parsec wrote:
So you updated from 3.30 to 4.20 and when the PC restarted when the update was complete, that is when you heard the five beeps? Is that right or was it a different sequence of events?
|
That's correct.
parsec wrote:
Which UEFI update method did you use?
|
The only option available for this BIOS as listed on the download page --> did F6 to http://www.asrock.com/support/BIOSIG.asp%3ccat=BIOS8" rel="nofollow - Instant Flash
parsec wrote:
Which ASRock FAQ said that five short beeps is a GPU problem?
|
https://www.asrock.com/support/faq.asp?id=286
parsec wrote:
Searching for the AMI UEFI five beep POST error description on the Internet results consistently are a problem with the CPU, as well as add in cards (GPU), and the board itself.
https://www.google.com/search?q=ami+five+beeps&ie=utf-8&oe=utf-8&client=firefox-b
|
It's dated but see the above link in my prior answer. The fact that the manual mentions nothing of beep codes is astonishing... I mean sure the board doesn't have a speaker but some of us old dogs have those on hand.
parsec wrote:
Although the 4.20 UEFI version has been available for less than a week, this is the first post about an issue like this I have seen so far.
What CPU and GPU are you using?
|
R5 1600 (under a Noctua NH-D15) and a Sapphie RX 480 4GB with a Prolimatech MK-26. System was flawless up to this moment.
parsec wrote:
Are you using a TPM?
|
No. And as mentioned fTPM was DISABLED in the 3.30 BIOS. Instant Flash was not "grayed out" --> it just had a disclaimer to go to the location of the fTPM setting and make sure that it was disabled which it was so I proceeded to reboot, did F6 and flashed 4.20.
parsec wrote:
Is there anything else you can tell us about this situation?
|
I'm crying and I wish I had a bottle of whiskey to go with these tears.
|
Posted By: datonyb
Date Posted: 09 Dec 2017 at 8:51pm
may i suggest
as of this moment you system isnt working so whatever happens its going to get stripped down
sooooooo
unplug from the wall the power flip out the bios battery (cmos battery) undo the heatsink then pop out the cpu pop out the graphics card and all ram
now make a cuppa tea/coffee
finish the beverage and take a careful look at the cpu pins to check everything is all inline with each other ,then drop it back into the board,with a very slight pressure on top, fasten the lock lever down,pop on some thermal paste and refit the heatsink insert 1 single ram stick into slot a2 and the gpu back into its slot watching carefully for equal amount of insertion into the slot YOU WOULDNT BE THE FIRST TO HAVE THE CASE ACTUALLY STOP THE CARD SITTING PROPERLY ^ive actually had this happen this week to me, on another know tested build when i put it into new case^
now plug it all back into power and keyboard etc and go for the boot
remember it will take up to 2 mins of dead non responsive status on the first cold boot after a cmos clear
------------- [url=https://valid.x86.fr/jpg250][/url]
3800X, powercolor reddevil vega64, gskill tridentz3866, taichix370, evga750watt gold
|
Posted By: dilacerated
Date Posted: 10 Dec 2017 at 1:04am
datonyb wrote:
unplug from the wall the power flip out the bios battery (cmos battery)
|
Already tried this.
datonyb wrote:
undo the heatsink then pop out the cpu
|
This should in no way be required for a BIOS upgrade.
datonyb wrote:
pop out the graphics card
|
Already done to get at the CMOS battery.
datonyb wrote:
and all ram
|
Like removing the CPU this should in no way be required for a BIOS upgrade.
datonyb wrote:
now make a cuppa tea/coffee
finish the beverage and take a careful look at the cpu pins to check everything is all inline with each other ,then drop it back into the board,with a very slight pressure on top, fasten the lock lever down,pop on some thermal paste and refit the heatsink insert 1 single ram stick into slot a2 and the gpu back into its slot watching carefully for equal amount of insertion into the slot YOU WOULDNT BE THE FIRST TO HAVE THE CASE ACTUALLY STOP THE CARD SITTING PROPERLY ^ive actually had this happen this week to me, on another know tested build when i put it into new case^
|
I can't imagine that a BIOS upgrade would have resulted in CPU bent pins. As mentioned the system was flawlessly working until this point. This is also my second rodeo with the AB350 Pro4 this year, third AMD Ryzen system build overall (two for friends), and I built eleven B250 Pro4 systems in March-April (which ASRock support told me couldn't run five GPU's but I got working anyhow).
Regarding the GPU I didn't move my case during the BIOS upgrade as the only contact with the system was putting my USB into one of the top ports which I seriously doubt jostled the GPU but anyhow I had to remove it and put it back to pull the CMOS battery so I'll see what happens with having only one stick of RAM in the A2 slot.
|
Posted By: datonyb
Date Posted: 10 Dec 2017 at 1:09am
im not implying a bios upgrade should involve this
what im trying to do is HELP YOU
ive read several posts from users who found these steps helped them get a boot when they hadnt before
including some weird occurance of reseating the cpu with no visable issue cured it
for all we know the action caused a better conduct from one pin to the board that was borderline
------------- [url=https://valid.x86.fr/jpg250][/url]
3800X, powercolor reddevil vega64, gskill tridentz3866, taichix370, evga750watt gold
|
Posted By: dilacerated
Date Posted: 10 Dec 2017 at 2:02am
datonyb wrote:
im not implying a bios upgrade should involve this
what im trying to do is HELP YOU
ive read several posts from users who found these steps helped them get a boot when they hadnt before
for all we know the action caused a better conduct from one pin to the board that was borderline
|
I know you are trying to help --> I see these suggestions going around here, Newegg and elsewhere for DOA's but this wasn't a DOA case. This was a fully functional system running VMware VM's, handily playing games and all just fine prior to upgrading the BIOS thus my amazement at the notion of having to do a full tear down.
Will start work here shortly. Thank you for the suggestions.
|
Posted By: dilacerated
Date Posted: 10 Dec 2017 at 2:42am
" rel="nofollow - Just to ask since I see it in your sig --> how do you like the X370 Taichi? I specifically went with the AB350 Pro4 because of the rather loud amount of negativity out there with majority of the X370 boards but the Taichi didn't seem to have such negative user reviews.
|
Posted By: datonyb
Date Posted: 10 Dec 2017 at 2:52am
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
------------- [url=https://valid.x86.fr/jpg250][/url]
3800X, powercolor reddevil vega64, gskill tridentz3866, taichix370, evga750watt gold
|
Posted By: dilacerated
Date Posted: 10 Dec 2017 at 4:53am
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.
|
Posted By: dilacerated
Date Posted: 11 Dec 2017 at 4:07am
" rel="nofollow - 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.
|
Posted By: parsec
Date Posted: 11 Dec 2017 at 11:22am
dilacerated wrote:
" rel="nofollow - 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.
------------- http://valid.x86.fr/48rujh" rel="nofollow">
|
Posted By: Vakich
Date Posted: 11 Dec 2017 at 7:45pm
" rel="nofollow -
dilacerated wrote:
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.
|
what exactly model of your corsair are you using?
|
Posted By: dilacerated
Date Posted: 12 Dec 2017 at 2:45pm
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.
|
Posted By: dilacerated
Date Posted: 12 Dec 2017 at 2:47pm
Vakich wrote:
" rel="nofollow -
dilacerated wrote:
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.
|
what exactly model of your corsair are you using? |
CORSAIR Vengeance LPX 16GB (2 x 8GB) PC4 25600 Model CMK16GX4M2Z3200C16.
|
Posted By: Krug
Date Posted: 31 Jan 2018 at 9:58pm
The same issue with my AB350 Pro4.
I had BIOS 3.20 and everything worked fine.
After I have updated BIOS to 4.60 I get 5 beep every time I start PC.
|
|