Asus Strix X470-F Gaming owners thread

[AniChatt]

Hello guys, I am starting this thread for all Stix X470-F owners to discuss their overclock settings, issues etc. So that everyone get help quickly in a organised way. Installed my old 1600x in this mobo with 4011 bios and flareX 3200 with default docp and it works just fine without any issues so far. One thing to mention The board pushes 1.15v soc default docp profile. Is it normal seems a bit high for me as I have upgraded from B350-F gaming.
However a small issue I believe, the asus lighting control is not behaving normal. I mean just after login to windows it is taking a bit time to start (5min) before that if I try to on Lighting Control by clicking it, program crash window appears after few seconds. But when it starts on it's own then I can open asus lighting control. Anyone experiencing similar issue???
Also tried to use older version.

[andrewtjb12]

Theres a new bios update out finally.

Seems to fix the issues I was having with 3600x and the rx 5700xt

[fragande]

andrewtjb12 wrote:
Theres a new bios update out finally.

Seems to fix the issues I was having with 3600x and the rx 5700xt

It's 1.0.0.3AB not 1.0.0.3ABB, right? AMD and their software version management ... If so still no fix for WHEA, Destiny 2 or sleep issues. Seems a bit odd to release 1.0.0.3AB at this time when ABB is released, but maybe it's been in testing for a while.

[andrewtjb12]

fragande wrote:
It's 1.0.0.3AB not 1.0.0.3ABB, right? AMD and their software version management ... If so still no fix for WHEA, Destiny 2 or sleep issues. Seems a bit odd to release 1.0.0.3AB at this time when ABB is released, but maybe it's been in testing for a while.

Yeah its AB which does seem a bit strange. I'm just glad to have a working bios finally cause my computer was pretty much unusable on the previous bios.

I only tested out this new bios briefly and seemed stable for me but I only run a few benchmarks.

[raistlin65]

fragande wrote:
It's 1.0.0.3AB not 1.0.0.3ABB, right? AMD and their software version management ... If so still no fix for WHEA, Destiny 2 or sleep issues. Seems a bit odd to release 1.0.0.3AB at this time when ABB is released, but maybe it's been in testing for a while.

The new AMD chipset drivers have a fix for Destiny 2. Information about it and links to the new chipsets at the bottom of AMD's announcement this week: https://community.amd.com/community/gaming/blog/2019/07/30/community-update-5-let-s-talk-clocks-volt...

[Xploder270]

Here's the link: https://dlcdnets.asus.com/pub/ASUS/mb/SocketAM4/ROG_STRIX-X470-F-GAMING/ROG-STRIX-X470-F-GAMING-ASUS...

[xeizo]

It's available for Prime Pro as well on the server, but yet not published on the product page.

[Xploder270]

First impressions not great - my previously rockstable RAM settings are not stable anymore. I've made screenshots of the trained timings and they are the same.
Loosening secondary timings seems to get me booting. WIP

[xeizo]

Xploder270 wrote:
First impressions not great - my previously rockstable RAM settings are not stable anymore. I've made screenshots of the trained timings and they are the same.
Loosening secondary timings seems to get me booting. WIP

Which cpu and ram do you have?

[Xploder270]

xeizo wrote:
Which cpu and ram do you have?

3700X
Was running Samsung E-Die DualRank Kit at 3600 CL16-17-17-36 rockstable.
This is extremely unstable now with the new Bios, I dropped Timings to 16-18-18-36 for now. Karhu is running.

EDIT: It trained to Command Rate 2T. I've never seen that before. There's no stability at all with 1T even at loosened timings. Flashing back 5007.
EDIT2: With 5007 I'm back running at 3600 16-17-17-36-1T immediately. Definitely gonna skip that one.

[xeizo]

Xploder270 wrote:
3700X
Was running Samsung E-Die DualRank Kit at 3600 CL16-17-17-36 rockstable.
This is extremely unstable now with the new Bios, I dropped Timings to 16-18-18-36 for now. Karhu is running.

EDIT: It trained to Command Rate 2T. I've never seen that before. There's no stability at all with 1T even at loosened timings. Flashing back 5007.

Not entirely surprising, AMD seems to be regressing with their AGESA:s currently, maybe some stressed co-workers.

I went back to 2501 from 2602 on the Crosshair VII, for me it wasn't memory(it worked) but 2602 has terrible boost and worse performance.