Asus ROG Strix X570-E Gaming Bios update?

[Cybersim]

Wow......what a sh1t show

Nothing but problems with this f7cking board.....my chipset temps are at 81!

Wtf?!

Thanks to the guy above me, there's just too much sh1t to read. Will flashback to bios mentioned above and test for another day. If no go. Im returning all my asus ****.

Gonna go dragon center and leave this armoury bullsh1t...F0CK 1T!

Hi. Check chipset fan. maybe dead. my chipset temp 50-61C.
In HWinfo64 check speed fan chipset.

So about the bios. I on beta 2812. one shutdown and restart per 10 days. most stability.

[Sinistercr0c]

Any feedback on the 2816 Beta BIOS yet? 2812 was a sh*tshow for me with random reboots/shutdowns so rolled back to the last stable version 2606. I'm interested to hear what 2816 is like before attempting to flash to it.

[Shenny]

Do you have a 5000 series Ryzen CPU?
If yes, you should care about those updates, since they carry essential functions. And of course they are beta, this is new hardware that has to be supported. Do you want to wait additional 3 months for the launch to get a non-beta BIOS? Or do you want the products to be released on time and BIOS support rolls out the following weeks?
I prefer the 2nd approach.

On topic: just installed the latest BIOS, testing with the 5800X now.

Nope, I don't have Ryzen 5000 CPU (I have placed several pre-orders but the supply is virtually nil but this is another topic for discussion). Still, "beta" label implies to me that there is something unfinished that developers have left in this release, all known bugs are not cleared yet and they cannot guarantee the stability or that there will be no negative consequences to your system if you go ahead with the update. Not that the same is not possible to happen with a non-beta version but in this case the developers put it bluntly into your face: "Do it at your own risk!"
If my current system is stable and performant enough, I don't see why I should take this risk.

[Dan69]

@ Sinistercr0c

The 2816 build is basically the same. Don't bother with it. Also has random shutdowns and reboots.

[cryonicangel]

Tested the 2816 BIOS with the curve optimizer on a 5800X.

Does not much for me.

Yes, i was able to get the +200Mhz boost on the singlecore load (up to 5050Mhz peak) but the all-core frequency still stays at 4650 at best (cinebench R20/R23).
I managed to drop like 4°C by using Negative 10 on all cores with the curve optimizer.
Increased the PPT, TDC and EDC a bit just to give the CPU headroom - nope, still the same, not sure what limit i'm hitting here, there is enough power budget and temps are in the mid 80's (hot as hell - i know, but even with a custom watercooling i can't get much out of that).

But the BIOS is rock solid, i only had freezes and restarts when pushing the curve optimizer over 10 or doing weird stuff with the overclock in general.

Will try to bump the memory frequency higher, let's see if the 5000 is better than my 3900X - that one refused to go higher than 3200 CL16 - minor changes - crash.

But who ever complains - the BIOS is rocksolid.

[Board Monkey]

With 2812 and a 5950X and Windows 10, I get very consistent compile times, but not with 2802 or 2816.

Using either 2802 or 2816 I see 30-50% slower performance 4 minutes after boot when compiling a C++ project in a RAM disk.

I upgraded from 2812 to 2816 last night and my first compile took 85 seconds, whereas compiles with 2812 have *always* been in the 60-64 second range. I reproduced this slowdown after 2 reboots.

I rolled back to 2802 and builds and build times were slow again: 98 and 86 seconds for the first builds after booting. The second build, after deleting output folder, took 62 seconds, which is consistent for 2812.

I was benchmarking memory configurations with a 3900X and upgraded to 2812 when I received the 5950X and have very consistent results over the course of 15 project compiles. My procedure is: reboot, compile exactly 4 minutes after the POST "beep", delete the output folder and build again after another 4 minutes, and delete temp files and rebuild one more time.

My conclusion is that some process is active 4 minutes after boot that is not active at 8 minutes after boot. Why the BIOS revision would make a difference makes no sense to me and I only repeated the test 2 with 2802 and 2816, but 2812 compile times were always consistent in their timings.

BTW, compiling in a RAM disk ranges 60-64 seconds with the median being 62 seconds, compiling from a Samsung 960 Pro SSD took 76 seconds for each of the 3 compiles I tested. RAM disk compiles with a 3900X were in the 78-86 second range with a median of 82 seconds. The C++ project includes single-threaded stages as well as multithreaded stages.

[Atomic7431]

Just got one of these motherboards as my gigabyte x570 was falling apart lol

i have a 5900x and currently im on the 2802 bios as the 2606 would restart every time i loaded up Apex legends. This behaviour stopped when i upgraded bios to the 2802.

I see in benchmarks lower results with this board than with the Gigabyte, do i need to try one of these Beta bios or are they not in very good shape currently?

Thanks

[Atomic7431]

No one with an ounce of information or knowledge?

[Steelo]

I have 3700x and 2802, 2812, 2816 has random reboot issue. But i fixed the problem with these adjustment ;

*Cpu Soc Voltage 1.1v
*Vddg iod 950v
*Vddg ccd 900v

I didnt want to go back older versions because 2802> has better performance and thermal result.
And this settings totaly safe and stable. No restart anymore.

[qwrty]

Hello,

did someone achieve to POST with 4*8GB Stick with 3800 / 1900 FCLK ?

thank you