Warning to Asus X570 owners, AGESA 1.0.0.4 has almost killed my PC!!!

[Master Disaster]

Computer was working 100% before I updated, has been since I built it on Zen 2's launch day (7/7/19). Board is an ASUS ROG STRIX X570-F Gaming.

 

Noticed the update was out yesterday, upgraded it yesterday, after the update first post was fine. Shut down and went to bed as normal. Turned it on today and now 50% of the time it hangs on POST with an orange LED (GPU) on the board, turn it off and back on it POSTs first time. Turn it off again andnext time it will hang again, next time fine.

 

Even if it posts I'd estimate another 30% of the times Windows refuses to boot. I get the spinning cirlce, screen goes black and nothing happens.

 

I'm not exaggerating, if rebooted my PC 40 times in the last 3 hours.

 

I've tried clearing CMOS, resetting UEFI  to Optimised Defaults, DOCP on and off. There is currently no CPU OC set at all, everything including automatic stuff is set to Disabled.

 

I'm 100% sure it was the UEFI Flash that caused this.

 

AND THE WORST PART.... 

[Guest]

I'm having the same POST issue, but it started with 1.0.0.3 for me on my WS X570 Pro Ace. Been working with Asus on it for a few weeks.

[vanished]

That not downgrading part is typical of almost (all?) BIOS updates afaik, so while problematic and unfortunate in this case, it's not unusual.

 

The other problems though are quite troubling.  It will be interesting to hear over the coming days if this is a widespread issue or an isolated case.  Hopefully for AMD and their users, it's the latter.

[Master Disaster]

1 minute ago, Ryan_Vickers said:

That not downgrading part is typical of almost (all?) BIOS updates afaik, so while problematic and unfortunate in this case, it's not unusual.

Actually not at all. If you watch Jayz2cents he recently did a video where he went back and forth between versions multiple times.

 

That said its also not uncommon for updates to stipulate that you can't go back. Its usually on big revisions to microcode which this update would qualify as.

[Lurick]

I upgraded to this last night myself and the first time it got stuck and didn't POST but after a reboot it posted right away and I didn't have any issues today but I might be in the minority with this though.

[Jurrunio]

Have you updated the chipset drivers before doing this?

[SavageNeo]

Have the same exact issue here. But i cant even get to bios, cause vga led is white and by pc just repoort itself over and over again

[Harry Voyager]

Do you have any other cards in your PCIe slots, besides the GPU? I had an issue when I built my machine that it would not boot with certain PCIe cards installed, when I'd installed the 1.0.0.4 AGESA, and it would hang at the VGA stage in the boot cycle.

 

It is a Gigabyte motherboard, so it may be an unrelated issue. Also, I did not get things up and running with the earlier AGESA, as that one would not boot with all of my RAM in, so updating the BIOS was about the first thing I did after turning booting it the first time. 

[BabaGanuche]

I am having the same problem with my Gigabyte x570 Master. After updating to AGESA 1.0.0.4 my will not post. It just gets stuck at 97.

 

I do have one other PCIe card in the 1x slot.

 

I was able to re-flash the older version via q-flash back the main BIOS.

[GamerDude]

I'd updated my BIOS to AGESA 1.0.0.4 F10a on my GB X570 Aorus Xtreme and it's all good, flashed the BIOS via thumbdrive method without issue. I think my system boot a little faster now, as for everything else, I haven't really tried anything yet as BIOS is new and I didn't wanna push it. Only thing I'd done same as before the update is to manually OC my CPU to 4.475Ghz all core.....

[Harry Voyager]

@BabaGanucheDid you try removing the other PCIe card? I have a theory that its not playing well with either 1.0 or 2.0 cards. 

[BabaGanuche]

1 hour ago, Harry Voyager said:

@BabaGanucheDid you try removing the other PCIe card? I have a theory that its not playing well with either 1.0 or 2.0 cards. 

Just did, and it does work if I remove it. Given the age of the card I would be surprised if it was not a 1.0 or 2.0.

[Harry Voyager]

@BabaGanucheAnd the cards I'm having trouble with are a 1 by 1.0 PCIe sound card from 2014, and an old USB 2.0 hub card. 

 

My 3D card is a PCIe 3.0 card, so newer than those. 

 

I'm definitely wondering if it introduced a backwards compatibility issue. I wonder if we can catalog the various cards that the systems fail to boot with an get them pointed towards a fix? The onboard HD Audio is nice, but the Xonar is better. 

[Master Disaster]

12 hours ago, Harry Voyager said:

Do you have any other cards in your PCIe slots, besides the GPU? I had an issue when I built my machine that it would not boot with certain PCIe cards installed, when I'd installed the 1.0.0.4 AGESA, and it would hang at the VGA stage in the boot cycle.

 

It is a Gigabyte motherboard, so it may be an unrelated issue. Also, I did not get things up and running with the earlier AGESA, as that one would not boot with all of my RAM in, so updating the BIOS was about the first thing I did after turning booting it the first time. 

I do, I have a Gigabyte PCIe x1 WiFi & BT Card.

[raulico]

i had the same results, i did the upgrade on ws pro x570 ace, after upgrade, post in loop, red led on mb, amber for a second then green, and red again….after 15 minutes i force shut down, and reboot again...a message on screen showed the upgrade of bios (award bios), and i saw ram was forced at 2400 (i have a 2x kit hyperx 3200), Windows boot properly, with ram at 2400, so a reboot again to force xmp at 3200, and now is working properly. but i saw a difference on temperatures….before, with wraith prism stock, under stress test, i saw 70-75°C, now i see 10° less, but mhz on cores are still the same 4250mhz at max, with cinebench 20-

gpu pcie 3.0

10gb pcie 3.0 cards on slots

[Dean.P.]

Having issues with 3900x on Asus Crosshair Hero VIII wifi, performance is terrible cpus will not boost higher then 500MHz booting takes forever and my memory will not work over 3200MHz. I really wish I had not upgraded.

[Lurick]

Just an FYI, Asus posted a updated "Patch B" version of this BIOS, pushing it up from 1403 to 1404.

Since my earlier post I've had one POST failure but otherwise it's been good. Maybe 1404 will fix other issues that have been seen by others?

 

@raulico @Master Disaster

 

 

 

[Dean.P.]

5 minutes ago, Lurick said:

Just an FYI, Asus posted a updated "Patch B" version of this BIOS, pushing it up from 1403 to 1404.

Since my earlier post I've had one POST failure but otherwise it's been good. Maybe 1404 will fix other issues that have been seen by others?

 

@raulico @Master Disaster

 

 

 

at least for the crosshair hero viii this did nothing for me

[Master Disaster]

2 hours ago, Lurick said:

Just an FYI, Asus posted a updated "Patch B" version of this BIOS, pushing it up from 1403 to 1404.

Since my earlier post I've had one POST failure but otherwise it's been good. Maybe 1404 will fix other issues that have been seen by others?

 

@raulico @Master Disaster

 

 

 

I'll test it out after this UFO documentary finishes.

[Master Disaster]

3 hours ago, Lurick said:

Just an FYI, Asus posted a updated "Patch B" version of this BIOS, pushing it up from 1403 to 1404.

Since my earlier post I've had one POST failure but otherwise it's been good. Maybe 1404 will fix other issues that have been seen by others?

 

@raulico @Master Disaster

 

 

 

Seems to have fixed my issues *fingers crossed*.

 

Just shut down and restarted 5 times, posted first time every time.

[raulico]

i did the upgrade with 1404, and i had problems...i'm watching too many problems, many cold boot frozen...i wrote to asus support, and i will try to downgrade to previous bios

[R3trosp3kt]

Hey everyone I was having the same issue but I was able to resolve it via these steps:

-Flash BIOS to 1.0.0.4 B again

-reset to optimized defaults

-then I went to onboard devices in the advanced section and toggled my Graphics card PCI-E slot and my m.2 PCI-E slot to gen 3 instead of auto

-after this I was able to change my RAM back to 3200MHz and my fClk back to 1600MHz

 

I was not able to boot before this and to get to the BIOS I had to clear the CMOS.

 

My Specs:

-ASUS X570 TUF Gaming WiFi

-AMD Ryzen 3700x

-EVGA 1080ti SC2

-32GB G.Skill Sniper @ 3200MHz

 

[raulico]

new bios was published….

no more problems

[AyoKeito]

Copying my Reddit post:

I'm getting more buying regrets from my Asus X570 as well. I've been using a beta AGESA 1.0.0.4 1403 BIOS for a little under a month, my Viper Patriot Steel 3733CL17 RAM never managed to work at XMP, but that's fine. I've set it to 3666CL16 or something like that, at 1.43V and it was fine, some cold boots here and there. Then, i've installed a custom water loop and downgraded my frequency further to 3600, to get rid of cold boots, and it was running perfectly... Until i've found new 1405 BIOS with "performance improvements".

Boy, do i regret that.

I've never managed to POST not only at RAM profile i was running before (both 3600 and 3666 at 1.43V), but even at 3400 with auto timings and 1.45V.

It just restarts one time and then gives up training memory: just hangs with stupid DRAM led, making me reset BIOS with a screwdriver.

And the funny thing? If i get to Windows at the default 2133 RAM speed and apply my RAM OC in Ryzen Master, it works! At least before i turn off my PC. As soon as my motherboards thinks "hey! we have a RAM there, let's train it!" i need to: turn off my PC, open the case, short the CMOS jumper, get to BIOS, apply my BIOS profile, boot to Windows, apply DRAM OC with Ryzen Master, reboot.

I'm seriously considering just killing and RMA'ing my mobo because it's well past the return window. I think i'll have no choice but to do that if 1403 downgrade won't work.

Also, it's not me who's doing everything wrong, a minute in Google yields this wonderful thread. There are also a few posts there on Reddit about that issue that i wish i've found earlier. I wonder how this BIOS managed to go public. Do they test it with 2133 RAM?

[nalyDylan]

I was contacting ASUS about this issue and several others I've had with this update and just got jerked around between support people who never read my questions completely to begin attempting an appropriate answer.

 

1) I have an issue where sometimes after a CMOS clear the only way for me to get the computer to do anything (Del or F2 doesn't work, none of the 3 methods described in the manual for accessing BIOS work after clearing CMOS) is to unplug one of my hard drives and break my RAID array so it falls back to an old school AMI BIOS screen where I press F1 to acknowledge the error and enter setup. Other people on the internet seem to be less fortunate and not be in RAID mode for this and have to RMA their boards at this point.

 

2) Saving User profiles in the new build seems to sometimes randomly insert fClk of 666Mhz, even on profiles where previously it was left on Auto

 

3) All these overclocking issues.

 

For other people who encounter a bad BIOS flash (Hello future people on Google):

That is, ASUS CrashFree Bios 3, or if you get to, "Warning! BIOS Recovery Mode has been detected."

• All USB ports on my X570-Plus TUF Gaming are created equal, but, the BIOS Recovery mode I was only able to make work with very specifically a GPT formatted FAT32 USB 3.0 drive. (I rotated between 5 different thumb drives and configurations with the fine people of the LTT Discord for almost 2 hours to scrape this one out)