[SOLVED] ASUS ROG Strix X570-F Gaming POST errors

[IceWolf75]

Hi

I post this issue in many places but no one seems to have a solution.
From time to time, quite often - now 1 in 4-5 start ups - my motherboard refuse to post. This started after I installed the new memory sticks, G.Skill F4-3600C16Q-32GTZN. They are listed as QVL by G.Skill and by ASUS .
DOCP is set on auto and it perfectly recognizes the timings 16-16-16-36. I only changed the tRC from 87 to 52 (as is it normal for my memory) but the errors appeared before changing this.
Some times, the PC starts normally, no issues at all.
Some times, it resets itself once and then continues, again, no issues afterwards.
And some times, it restart itself three times, resets the memory ti JEDEC standard settings and force me to enter BIOS. I just save and exit, it announce me I made no modifications and then... boot up without any other issue afterwards.
It's very strange and very annoying. Regardless of the way it started up, there is no issue at all with the stability or performance and I'm gaming quite a lot, hours each day. No applications or Windows crashes, no artefacts, no blue screens.
What can it be the problem?
As I mentioned in the title, I'm using an ASUS ROG Strix X570-F with AMD Ryzen 7 5800x. There is no heavy overclocking, everything is on "Optimized Defaults" and DOCP. I've hard reset the BIOS after installing the memory and I'm using latest BIOS version.

 

[I7 i7i7]

RMA mobo

 

[Lutfij]

When posting a thread of troubleshooting nature, it's customary to include your full system's specs. Please list them like so:
CPU:
Motherboard: include BIOS version as well
Ram:
SSD/HDD:
GPU:
PSU: make and model and age
Chassis:
OS: version of Windows 10

You might want to see if breadboarding the system with bare minimum hardware changes your experience of the system's POST.

RMA mobo

So you won't help troubleshoot, just recommend RMA?

 

[IceWolf75]

When posting a thread of troubleshooting nature, it's customary to include your full system's specs. Please list them like so:
CPU:
Motherboard: include BIOS version as well
Ram:
SSD/HDD:
GPU:
PSU: make and model and age
Chassis:
OS: version of Windows 10

You might want to see if breadboarding the system with bare minimum hardware changes your experience of the system's POST.


So you won't help troubleshoot, just recommend RMA?

Sorry, I will post the specs now.
The motherboard worked fine with the other memory I had though not at 3200 MHz, only at 3000 MHz but that memory never worked at 3200, not even on my old i7 7700K with a Z270. Somehow it was stuck on 3000, it never worked well. And even now, if it managed to post, no problems will occur until another power off and even then, not always.

CPU: AMD Ryzen 7 5800x
Motherboard: ASUS ROG Strix X570-F Gaming (BIOS version 3405 AGESA V2 PI 1.2.0.0, latest)
Ram: 32 GB 3600 MHz 4 x 8 GB G.Skill F4-3600C16Q-32GTZN
SSD/HDD: primary 1 TB Kingston A2000 M.2 NVMe PCI-E 3.0, secondary: 2 x 500 GB SSD SATA (Kingston + ADATA) + 3 x 1 TB HDD SATA (Western Digital + Seagate)
GPU: ASUS ROG Strix RTX 3080 OC O10G
PSU: Corsair RM850x, 850W, approx. 1 year old
Chassis: ASUS TUF Gaming GT501
OS: Windows 10 Pro 64 bit (20H2) but I don't think the OS matters in this case

 

[Zerk2012]

Sorry, I will post the specs now.
The motherboard worked fine with the other memory I had though not at 3200 MHz, only at 3000 MHz but that memory never worked at 3200, not even on my old i7 7700K with a Z270. Somehow it was stuck on 3000, it never worked well. And even now, if it managed to post, no problems will occur until another power off and even then, not always.

CPU: AMD Ryzen 7 5800x
Motherboard: ASUS ROG Strix X570-F Gaming (BIOS version 3405 AGESA V2 PI 1.2.0.0, latest)
Ram: 32 GB 3600 MHz 4 x 8 GB G.Skill F4-3600C16Q-32GTZN
SSD/HDD: primary 1 TB Kingston A2000 M.2 NVMe PCI-E 3.0, secondary: 2 x 500 GB SSD SATA (Kingston + ADATA) + 3 x 1 TB HDD SATA (Western Digital + Seagate)
GPU: ASUS ROG Strix RTX 3080 OC O10G
PSU: Corsair RM850x, 850W, approx. 1 year old
Chassis: ASUS TUF Gaming GT501
OS: Windows 10 Pro 64 bit (20H2) but I don't think the OS matters in this case

Bump your voltage up to 1.4 or lower the speed to 3200.

 

[IceWolf75]

Bump your voltage up to 1.4 or lower the speed to 3200.

Even if the memory is 1.35V? I wouldn't want to lower so much the frequency.

 

[Zerk2012]

Even if the memory is 1.35V? I wouldn't want to lower so much the frequency.

Try it @ 3600 but increase the voltage to 1.4 that could solve everything if not lower the speed to 3200 @ 1.35 volts.
And yes 1.4 volts @ 3600 even though the memory says 1.35.

Your memory is not stable!

 

[IceWolf75]

Try it @ 3600 but increase the voltage to 1.4 that could solve everything if not lower the speed to 3200 @ 1.35 volts.
And yes 1.4 volts @ 3600 even though the memory says 1.35.

Your memory is not stable!

I agree is not stable, but why only when I'm powering the PC? Why it is perfectly stable after?
I will try 1.4v, of course.

 

[IceWolf75]

Ok, I've set the DRAM voltage to 1.4. It boots ok after restarting and I will do some tests for stability in Windows and applications. I will come back after a few days with more info because as I said, this only occurs once in a day, at the first start up and not even at every first start up.

 

[Zerk2012]

I agree is not stable, but why only when I'm powering the PC? Why it is perfectly stable after?
I will try 1.4v, of course.

The OC of the memory is failing on cold boot after the memory warms up some it's fine up the voltage.

 

[IceWolf75]

The OC of the memory is failing on cold boot after the memory warms up some it's fine up the voltage.

Reasonable answer, thank you.

 

[IceWolf75]

Absolutely no issues since I increased the voltage to 1.4 V, five days ago. A simple solution for a very annoying problem.
Every POST was successful and the memory and system as a whole is stable one hundred percent. Thank you both for the suggestion, @Lutfij and @Zerk2012. Your answers are the first ones of real help. On ASUS and AMD forums I got only something like "something is wrong, one of your parts is faulty"...