RAM Auro Sync Failure, QCode 53 on Restart

[connlost]

System Specs:

CPU: Intel i9-13900K

Motherboard: ROG Z790 HERO

RAMs: I have tried two different RAM kits, both running into the same issue, one is Gloway(a Chinese brand) 2*16GB 6000mhz Hynix A-Die CL28 kit, and the other one is a CORSAIR VENGEANCE RGB 2*16GB 7200 CL34 kit. (The system is stable, had never run into BSOD or anything like that during stress tests)

Issue Description:

I am experiencing an issue with Aura Sync RGB control. Occasionally, the RGB lighting for the RAM sticks stops responding, and the lights remain on in their last state. When this occurs, Aura Sync can no longer detect the RAM sticks, and the lighting cannot be controlled.

More critically, upon restarting the system after this issue arises, the motherboard gets stuck on QCode 53. To resolve this, I am forced to perform a full cold shutdown before the system can start properly.

I’ve attached a photo of the motherboard during the issue. Notice that only the RAM lighting remains on, as it is frozen in the last state before the reboot. Since Aura Sync is not functioning at this point, the lights do not turn off, even after a restart.

[Silent_Scone]

Hi @connlost 

Are you able to confirm if this issue occurs at Optimised Defaults (NO XMP Overclocking)?

[connlost]

I honestly don't know, this happens randomly like 1-2 times per week... I am running the XMP II profile.

[Jiaszzz_ROG]

Hello @connlost 

Could you kindly share the complete RAM module part number, such as CMH32GX5M2X7200C34?
Based on the situation you described, we recommend clearing CMOS and testing whether the issue persists without any manual adjustments in the BIOS, including when XMP is not enabled.
Additionally, please ensure that all items in the Armoury Crate Update Center are correctly updated. If there is other lighting control software installed on your system, we suggest temporarily removing it, if applicable.
And also try uninstalling via the uninstall tool, reinstalling, and updating Armoury Crate to ensure proper functionality, if needed.

If the problem persists, could you help record and provide the relevant logs for us to verify further?
For log operation steps, please refer to "Q5: What is App Diagnostics? (New Feature)" and ensure that you have confirmed and checked the "Record Log" option before proceeding with the steps to replicate the issue.
And kindly record a video simultaneously and provide it to us, allowing us to better correlate the log with the actual scenario. After recording the log, please upload it to the cloud, approve access, and DM me the link.

Thank you.