Arrow Lake weird memory behavior
I'm primarily on Linux, so excuse the lack of timings screenshot, I'll add one if this frustrates me enough to set up Windows to stabilize the OC. Tertiaries omitted in photos, as they're all Auto.
First of all, let me preface this by saying I got the 270K because I wanted decent gaming performance but my 7800X3D wasn't doing it for the work I do on the same machine, so I'm hoping to get a solid middle ground.
Unfortunately, my 6000 16 Gbit M-Die kit (32-38-38-96) really doesn't like anything above 6000, even with loose timings, so I figured I'd focus on sub timings instead. I didn't have a lot of hope, because D2D took 1.35V to get stable at 32 multiplier - so my chip may be a dud either way.
What I noticed is that any tertiaries will basically lead to no POST and the only way to recover isn't even setting timings back to Auto, but loading a pre-existing profile that I know is stable, even if the only change has been 1-2 tertiary timings.
From what I remember RDRD_sg and WRWR_sg on DDR5 should pretty much always be 8, with *_dg between 12 and 16. None of that works. Sometimes even setting the same timings as the BIOS is showing for the auto setting seems to no POST right after (I did this purely out of desperation).
In general, it's been really weirdly unstable/inconsistent. I haven't even touched the cores at all, one because I'm on air, but also because the second I've even attempted to change LLC or power limits, it would no POST again.
And to be clear, I am not at the edge of stability here. Loading the stable profile and stress testing Prime95 or OCCT (memory, mixed) for hours isn't a problem.
Has anyone else experienced any of this? Is there some weird BIOS setting I'm missing? I haven't done much OCing on Intel since Coffee Lake, besides some quick and dirty Alder Lake ones.