Random POST issues with overclocked DRAM Q-Code 17

[Thoraine]

Hi all, I need help figuring out a really frustrating issue and would appreciate your help.

I have passed multiple stability tests but every time I reboot, there's a chance I fail to POST with Q-code 17 and the CPU error LED lights up. Error code according to the manual, it states it's "Pre-memory System Agent initialization is started". I can no longer boot up or enter BIOS until I clear CMOS, even if I cold boot. Reapplying the exact same overclock settings after clearing CMOS lets me boot up normally.

My system:
7800X3D + Strix B650E-E (AMD AGESA PI 1.2.0.2. latest BIOS)
Curve Optimiser -10
PBO Enhanced -> Target 90C
Trident Z5 RGB DDR5-6400 CL32-39-39-102 1.40V 64GB (2x32GB)
Timings in picture (Buildzoid's easy Hynix timings)
Memory Context Restore Disabled
Fast Boot Disabled

I have passed 5 cycles of TM5 Extreme1 and 40 hours of CoreCycler on Ryzen.yCruncher.BreadPit config, 24 hours on default config.

Things I've tried, which worked on first boot but eventually failed to POST:

• DOCP I 6400 MT/s profile but dropping to 6000 MT/s (UCLK = MCLK/2)
• Same as above but DOCP II
• Curve Optimiser 0 + PBO Default

I've run out of ideas regarding what to try next, please help!

[Nate152]

Hello Thoraine

I would try one thing.

Enter the bios, go to Dram Timing Control. At the top with the primary timings, change the command rate to 2T or 2N, whichever option is available. Hit F10 and Enter to save and exit.

How does it go after changing the command rate?

[Thoraine]

Hi Nate, I'll try that out but it may take some time for me to ascertain whether it is stable or not as it takes a few days to trigger.

While I have you here, what else would you try to tweak? In case it fails to POST a couple days or weeks later. 

[Nate152]

Well, command rate 1T will put alot more strain on the cpu's memory controller. Setting it to 2T/2N may be enough to get you stable. You won't know until you try.

On the other hand, if it still gives you code 17, you may have to do some manual voltage tuning.

[Thoraine]

Is there any point where you'd suggest an RMA of either the mobo or CPU?

Additionally, Buildzoid mentioned that "there seems to be a bug with memory intialization either with the new AGESA or ASUS motherboards" and sometimes the memory training fails until a full power cycle is performed.

It almost sounds like my case, but mine doesn't work even with a power cycle.

[Nate152]

G.Skil Trident Z5 is designed for Intel motherboards, you should have gone with Trident Z5 Neo.

64GB 6400MHz cl32 is a pretty aggressive memory kit. X.M.P. is considered an overclock and is not guaranteed.

Try with the bios at default settings and see how things go. If you have no issues at default settings, then this is a sign you need to do some manual voltage tuning.

Returning the memory kit for Trident Z5 Neo may give you better results.

[Thoraine]

Just to be clear, I have manually set voltages and primary + secondary timings, so I'm not using the DOCP profile. I'm also running at 6000MT/s.

Some background: this kit has been working with the in-built 6400 MT/s XMP profile with my previous 13900k system, and then I brought it over to this new 7800x3d system. I'm even down clocking it to 6000 MT/s for my 7800x3d, so I'm feeling like it's either the mobo or the cpu. Nevertheless thank you for the help I'll continue monitoring it

[Nate152]

You were using your 13900K in an Intel motherboard which the memory kit was designed for, hence you weren't having any issues.

I would still try with the command rate at 2T/2N, this should let you go higher with the frequency and may let you reach 6400MHz.