ROG STRIX X870E-E GAMING WIFI Code 15

[KraZy_SkitZy]

I've been pulling my hair out for months with this issue. Every boot/reboot I have to wait out a code 15. Yes I know its memory training.  It seems ridiculous to have 2-3min boot times. I've tried context restore, but i get crashes and blue screens. If i don't turn on XPO boot times are fine. I've tried 4x 16gb corsair 6000mhz, I've tried 4x 16gb Gskill 6000mhz, i've tried 2x 32 corsair 6000mhz, and even tried a single stick. Enabling any xpo results in a long boot time.  I've reseated the cpu even.

The only reason I tried the Gskill was cause a buddy has a gigabyte x670 board with a 9800x3d and he has fine boot times with that set.

My specs:

ROG STRIX X870E-E GAMING

7950x3d

7900xtx

I've never despised a system more than this one. I haven't bought an asus board since amd bulldozer days, and been a gigabyte guy through and through, and this board has done nothing but make me crazy. 

[Silent_Scone]

Hi @KraZy_SkitZy 

After initial training, subsequent reboots / power-ons should be significantly reduced. It's possible that the overclock is unstable, which is why you're unable to enable context restore successfully.

Ensure you're on the latest BIOS, as newer AGESA has improved some of the training process times significantly in my case.

[KraZy_SkitZy]

i have the latest bios. 3 different ram types and i cannot get a faster boot with xpo on, on any of the 3 ram configurations is pretty silly. Given ive tried the exact same g skill set as friend of mine who has a gigabyte x670 board with a 9800x3d..

[Silent_Scone]

It's not typical, for sure. You'd also need to rule out the CPU, though.

Could you please list the full system specs, as well as the kits you're using? 4x16 6000MHz is less than typical, hence why there's only one validated kit on the QVL.

If the system is still unstable with EXPO using a single module, I'd consider firstly inspecting the CPU and mount, as well as the socket and pin-pad for any damage or debris.

Ensure consistent mounting pressure. If using a third-party CPU contact frame, remove and reinstall the stock retention mechanism. Report back if the behaviour is the same.

[KraZy_SkitZy]

CMH64GX5M2B6000Z30

CMH32GX5M2N6000Z30

F5-6000J3038F16GX2-TZ5NR

Using stock mount, socket appears fine. Everything is stable in windows, only becomes unstable with context restore. Its just the irritatingly long boot times