Asus ROG Strix X570-E Gaming Bios update?

[thomson1969]

Hi,

Does anybody knows when there will be a new bios for this motherboard Asus ROG Strix X570-E Gaming.
The latest one is dated 2019-07-05, an there is nothing about which AGESA its using.

[schmak]

Shenny wrote:
What do you mean by clean BIOS update? Does it also reset your CMOS settings?
For me, the BIOS flashback is necessary if the normal update has failed in the middle or the old BIOS does not support your brandnew CPU and you have to update it somehow.

I've found that sometimes using the EZ Flash doesn't do a full update, there are occasionally weird glitches where things are missing or not saving correctly in bios or new AGSEA features not showing up. using the flashback tool guarantees a wipe and restore of the BIOS from the image on the flash drive.

Any bios update should wipe out your BIOS settings, if it doesn't it probably didn't take right. I don't know if using EZ flash saves profiles, because I don't use them. I have everything written down. Using the flashback definitely will clear it all.

If you are having problems with your BIOS, as was stated, its best to use the flashback tool to update the bios.

[simeongg]

dave798 wrote:
my mother board has started showing QCode d3 this will start showing a few minutes after startup when it was initially QCode AA, after checking asus codes it states that it means Some of the architectural protocols are not available, but what does that actually mean in laymans terms?, only change made was updating AMD display driver 6900xt and I dont really want to roll back to previous driver as this latest one has fixes i need for other problems. TIA for any and all advice

It's about latest beta drivers. 20.8.1, latest stable 20.6 are ok. d3 is informational code from what I read and it's nothing to worry about. I face it on my new 6800XT.

[RedSector73]

simeongg wrote:
It's about latest beta drivers. 20.8.1, latest stable 20.6 are ok. d3 is informational code from what I read and it's nothing to worry about. I face it on my new 6800XT.

Qcode D3 means some of the Architectural Protocols are not available. That is information from it.

[simeongg]

RedSector73 wrote:
Qcode D3 means some of the Architectural Protocols are not available. That is information from it.

Thanks.

On reddit people say, that face this problem with Ryzen and Nvidia driver. So may be is CPU dependent, than AMD driver issue. Latter will try latest 4010 beta BIOS.
https://www.reddit.com/r/AMDHelp/comments/mvlxyj/latest_drivers_cause_d3_qcode_error/

Also this is in official notes by AMD:

After updating to the latest Radeon™ Adrenalin software, a D3 information code is seen on some motherboards. However, AMD has not identified any issues pertaining to it – it is an information code and not an error code.

Souce: https://www.amd.com/en/support/kb/release-notes/rn-rad-win-21-7-1

[uprising]

simeongg wrote:
Thanks.

On reddit people say, that face this problem with Ryzen and Nvidia driver. So may be is CPU dependent, than AMD driver issue. Latter will try latest 4010 beta BIOS.
https://www.reddit.com/r/AMDHelp/comments/mvlxyj/latest_drivers_cause_d3_qcode_error/

Also this is in official notes by AMD:

After updating to the latest Radeon™ Adrenalin software, a D3 information code is seen on some motherboards. However, AMD has not identified any issues pertaining to it – it is an information code and not an error code.

Souce: https://www.amd.com/en/support/kb/release-notes/rn-rad-win-21-7-1

I’ve had d3 code on 2 boards maximus vi hero when opening the information tab in Asus Ai suite and on my current crosshair vii hero when running zen timings it seems to be related to reading ram timings maybe other bios settings as well.
I don’t think it has anything to do with drivers my maximus vi hero is 7-8 years old still running it now and never had any problems.

[Erwin05]

Dont use Beta bios 3801

When Bios 3801 Beta came out i had low FPS while gaming. yesterday BFV started with a low 30 FPS and the cpu is also hotter then normal.
Today i started to bench the cpu with cpu-z and i got a very low score single thread 242 muti thread 986.

i flashed back to 3603 and all is normal again so this bios is a very bad one.



Bench score with bios 3603.



I recorded BFV this is what happens when Beta bios 3801 is flashed.
https://youtu.be/-YhVc4uhHdY

Will do a recording with cpu-z open with bios 3801 Beta and 3603 for more proof.

After flashing it takes some time and then the problem is back low FPS and a low cpu-z bench score.



Movie Beta Bios 3801
https://youtu.be/rCwQ1trvRE0

Movie Bios 3603
https://youtu.be/bEOzXMhyJq0

[Shenny]

I would expect that when a vendor posts a beta BIOS, this is kind of a preview for the next non-beta release that will come soon. 3801, however, has been around for almost a month and some people are complaining of it. Are ASUS going to release something final any time soon?

[Erwin05]

I hope then, that my problem is fixed in the next bios. i also did send it to asus support.

Asus has to remove Beta bios 3801 right away from the download site this bios can damage the cpu and maybe the motherboard
The more i use the pc with gaming, internet the slower the cpu works and the hotter it gets.

i dont know why it drops performans less MHZ or cpu cores stop working.

The cpu performans less and has to do the same work en gets very hot.
Gaming isnt posible anymore and the pc gets slow.

[Doogz]

I too have issues with this BIOS - although mine is a brand new build - I never had a previous BIOS, and went straight to 3801 (Beta).

I have an X570-E Gaming with Ryzen 5900x. I cannot get an HP Reverb G2 to work ... I am constantly getting the 7-14 error (could not detect VR headset). It works on a prevous PC. The PC obviously detects it to a point because it starts the install procedure. Unplug/replug - no joy. Different USB sockets - no joy. Also, sometimes when plugging the Reverb in my mouse would dissappear, and would only come back with a hardware restart. FYI, the Reverb works fine when plugged in to an external hub.

I'm also having intermittent (but frequent) issues with a WDD Black SATA HDD not being properly detected. It is showing up in Windows as an unknown device, and in Disk Manager as an uninitialized disk. I cant see it in the BIOS either - all the entries for SATA are blank, although the BIOS detects my 2 x NVMe drives with no issue. The WDD Black has all the content from my old PC, so I'd prefer not to have to blow it away and reinitialize.

I raised a ticket with ASUS Support, and they recommended to go back to 3603.

Question - if I do this do I need to downgrade the AMD chipset driver, or is it ok to leave that at 2.13.27.501?

Cheers

Doogz

[Kirkosism]

Doogz wrote:
I too have issues with this BIOS - although mine is a brand new build - I never had a previous BIOS, and went straight to 3801 (Beta).

I have an X570-E Gaming with Ryzen 5900x. I cannot get an HP Reverb G2 to work ... I am constantly getting the 7-14 error (could not detect VR headset). It works on a prevous PC. The PC obviously detects it to a point because it starts the install procedure. Unplug/replug - no joy. Different USB sockets - no joy. Also, sometimes when plugging the Reverb in my mouse would dissappear, and would only come back with a hardware restart. FYI, the Reverb works fine when plugged in to an external hub.

I'm also having intermittent (but frequent) issues with a WDD Black SATA HDD not being properly detected. It is showing up in Windows as an unknown device, and in Disk Manager as an uninitialized disk. I cant see it in the BIOS either - all the entries for SATA are blank, although the BIOS detects my 2 x NVMe drives with no issue. The WDD Black has all the content from my old PC, so I'd prefer not to have to blow it away and reinitialize.

I raised a ticket with ASUS Support, and they recommended to go back to 3603.

Question - if I do this do I need to downgrade the AMD chipset driver, or is it ok to leave that at 2.13.27.501?

Cheers

Doogz

I've spent 5 days chasing my tail trying to resolve detection issues with the HP Reverb G2 with the same constant error of 7-14, investigating everything from drivers to software. HP sent me a new USB hub, which didn't solve the issue, but it was nice of them to try! lol. A matter of fact after much persistence and fiddling with the connector into the headset, that's where the issue seems to be for me, after gentle inserting a plectrum above the connector to keep it more securely in position, wham, headset and PC communicating with each fine! So, it's as likely to be a fault with the headset or the cable as much as any driver or software issue, (probably the latter by the looks of the streams of forums full of people complaining about their cables as well).