X370 Gaming X Bios update. Kills Systems.
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=11450
Printed Date: 30 Jul 2025 at 5:42am
Software Version: Web Wiz Forums 12.04 - http://www.webwizforums.com
Topic: X370 Gaming X Bios update. Kills Systems.
Posted By: Harleyevo
Subject: X370 Gaming X Bios update. Kills Systems.
Date Posted: 09 May 2019 at 11:05pm
|
Was running the 5.20 Bios on my x370 Gaming X, and saw that the 5.40 Bios was available. Flashed the system to 5.40 --- BIG MISTAKE!!! So far 5.40 has broken my Raid Array, If I delete the Array Wipe the Disks, I can add Both Disks in as a Raid 1. After windows Boots it tells me the Array is broken, and Raid Expert confirms this as Only one disk is seen. If I then Revert to AHCI mode, I can See and format both disks, Running the Hatachi Drive tool also confirms that the Disks are fine. So I can confirm that the 5.40 Bios Seriously Dorks your machine. This has been running Rock-Solid for over a year on all of the previous Bioses so I know it's not something Im doing other than trusting that 5.40 was stable. Contacted Support - No Reply... Last time I contacted them It took 3 months and I figured out the problem (Still waiting on support to figure it out.) So I'm not holding out hope here. Also just for fun, my USB3.1(Gen2) card is no longer working either post bios, I cannot see ANY disk inserted into the Attached docking station. This was just Just working prior to the Bios update to 5.40, I know as I cloned my working system Thankfully to the Disks there in case of Issue. Right now I am limping along running on my cloned disk, attached to the SATA port. Asrock, Perhaps you need to do some better QA! Anyone have any ideas how to un-fu*k this giant mess since ASRock in their finite wisdom fixed 5.40 Bios so you cannot downgrade back to the last working version. If you haven't upgraded... DON'T DO IT!!! On a positive note, and the only good thing I can see that this update does for you is the processor scheduling has gotten better, BOINC can now flag the CPU 1700X to 100%, prior it would peak to 100% then fall back to 90% and back and forth so there is that. |
Replies:
Posted By: nky83
Date Posted: 10 May 2019 at 12:56am
|
As a fellow user I share the same sentiment ^^^ New BIOS seems buggy, especially for the 1st Gen Ryzen (x370/B350) Once again DO NOT update to latest bios, they should have capitalize "User will not able to flash previous BIOS once upgrading to this BIOS version" |
Posted By: Harleyevo
Date Posted: 10 May 2019 at 3:41am
|
I swear to god! if their technocal support does not answer my support request I am going to FLOOD their inbox with requests until they either contact me or FIX THIS! |
Posted By: Xaltar
Date Posted: 10 May 2019 at 1:42pm
|
I will pass this info along to my contacts at ASRock. The new version probably contains support for Ryzen 3k and as usual, something probably got messed up. AMD still has a ways to go with their base code (AGESA) programming and troubleshooting. A quick look around shows issues like this popping up every time AM4 has gotten a generation jump/major update, here and on other manufacturer forums. I am not defending anyone here or placing blame, just recommending that it is typically best to avoid the first and probably second BIOS release after a major update unless you absolutely need it (ie. you need the CPU support). Generally by the 3rd round of BIOS releases after a generation jump the issues and kinks have mostly been ironed out. If you take a look around the forums here you will see quite a few threads pressuring ASRock to release updates for the "latest AGESA" and if there are 2 threads on the forums about it you can be sure there have been hundreds of support tickets sent. It's a catch 22, hold off on release till you are sure all is stable and functional, possibly missing a CPU launch and lose a lot of users who feel cheated because X or Y manufacturer has already released updates or rush them out the door and annoy other users with bugs, broken features etc. Personally I prefer the slower release path. This is typically not the case with intel boards so I suspect AMD is still ironing out the kinks in their development cycle and how they coordinate with board partners. ------------- 
|
Posted By: Harleyevo
Date Posted: 12 May 2019 at 9:28am
|
Still nothing from ASR, I wrote them on the EU site the Global site, the Americas site and no response. You would think with problems as glaring as this they would be all over it, but no. So much for customer support. |
Posted By: wardog
Date Posted: 12 May 2019 at 11:44am
| What's everyone running for a processor and OS? |
Posted By: Harleyevo
Date Posted: 13 May 2019 at 2:29am
|
Processor AMD 1700X Os shouldn't matter since it is happening at the bios where the array first shows broken. |
Posted By: wardog
Date Posted: 13 May 2019 at 4:13am
It would have taken less time to say. Nevermind. |
Harleyevo wrote:Posted By: Harleyevo
Date Posted: 14 May 2019 at 12:25am
|
You asked... And had you read the initial thread you would have seen that this issue occurs before the system posts. EG the raid is broken. Therefore the response was appropriate, only the CPU info was valid/warranted. |
Posted By: Harleyevo
Date Posted: 14 May 2019 at 9:59pm
|
Final Update: So I wound up Spamming pretty much every option in every support region, no responses after a few days. Then I spammed every mail address i could find, webmaster, sales etc.. for every region and re-spammed support . Next day, I was contacted by John from ASRock Support. He gave me a BIOS that allowed me to revert to 5.20 The mail on how to do, seemed that it would be complicated and difficult and dangerous, it was not. The reversion ran a bit from within windows, then the system rebooted and UFEI Bios did its thing and self flashed to 5.20 All good. However since the raid was broken by 5.40 I had some issues there. The Bios said there is no raid array but the disks still had a signature on them that they were part of an array. No big worry, I've been down this rabbit hole before. You just need to low-level the disk and all is good. Except the Hitachi tool though able to wipe the disk doesn't apparently touch the area of the disk where the bits are set that indicate the disk is part of an array. The fix. I fired up Dban, and Wiped the disks, I did not let it run fully just long enough that I felt confident the areas in question got zero filled. I then set the disks back to AHCI and initialized them under windows as basic disks. Reboot and reconfigure as RAID and bam I could now initalize the disks and make them part of a new array. A quick boot then off my cloned disk (before all this brouhaha started.) and reclone back to to my Raid1 Array. 24 hours later... everything is back and working as normal. Raid... Working. USB attacked disk Dock (attached via ASRock usb 3.1 Gen2 card). Working Made 2 more new clones of the boot drive (Just in case.) They'll eventually be rotating boot backups, but for now... And Stability testing is underway. So color this solved. 5.40 Bios is problematic, so I'll wait, until the Ryzen3's come out and then flash at that time with whatever bios is out then, and if it doesn't work I have a backout for the thing you apparently cannot backout. John, Kudos to you. |
Posted By: Xaltar
Date Posted: 15 May 2019 at 3:38am
Great to hear Harleyevo. Glad you got it sorted in the end  -------------
|
Posted By: Harleyevo
Date Posted: 15 May 2019 at 5:17am
|
Final - Final update. The 5.20 Downgrade bios, is slightly different in a good way. The Disk Access LED never worked right for me with Raid, is now working as expected. Before was on all the time, now it does the blinky-Blinky like I expect it should. Also Boinc now flags the CPU at 100% steady, prior it was hitting 100% and then dropping to 98% and then bouncing back up again. So there is something different in the Downgrade bios, and it seems by different I mean better. |
Posted By: Harleyevo
Date Posted: 13 Aug 2019 at 11:02am
|
New Update... The 5.5 Bios is stable. And I am currently running on it. The 5.6 Bios, not so much. Problems with the 5.6 bios... You cannot set the raid array as a boot device. The UFEI firmware will see the drives and let you make a raid array, however the only device that shows as boot-able is the CD-Rom. Something is definitely dorked in the 5.6 Bios so I would recommend staying away from it at this juncture. Logged a support ticket but ASR support if back to it's old shenanigans as it's been 48+ hours and not even a by your leave mail, or the ever popular we've received your support request and are ignoring it. Come on kids, this type of support is how you lose customers. |