[Meta-Thread] DDR5 Detection / SPD Corruption / Boot Issues

Description of Bug

This is a meta-thread to collate all the similar DDR5 issues that are currently occurring with OpenRGB, the worst case leading to a corrupt SPD on the DDR5 modules themselves and leading to boot failures.

This seems like a pretty severe issue, but there doesn't seem to be much traction on these threads.

See:

• #3755
• #3821
• #4582
• #3895
• #4671
• #4135
• #3753
• #3728
• #4441
• https://github.com/ubihazard/ddr5-spd-recovery
• https://www.reddit.com/r/OpenRGB/comments/10ep934/failure_to_warm_boot_due_to_openrgb_using_gskill/
• https://www.reddit.com/r/OpenRGB/comments/1lqwrp1/im_not_sure_what_i_need_to_do_to_make_my_ram_for/
• https://www.overclock.net/posts/29162261/
• https://www.overclock.net/posts/28920648/

The general issue is:

• OpenRGB detects DDR5 on the first run after boot
• On subsequent restarts of OpenRGB OR "rescan" OR after sleep/wake, the DDR5 does NOT get detected
• At this point, SPD data shows as missing / corrupt on tools like CPU-Z / HwInfo
• Doing a "warm restart" (as in clicking reboot in Windows) causes the machine to fail to post, usually with a Memory error code indicator, and it needs to be forced off
• Eventually this can lead to a corrupt SPD that does not allow the PC to boot at all

My Hardware Details

• OS: Windows 11
• Motherboard: ASUS PRIME B760M-K
• RAM: A-DATA XPG Lancer Blade RGB 2x16GB (AX5U6000C3016G-DTLABRBK)

I had tested the exact same kit of DDR5 with another motherboard - MSI B850 GAMING PLUS WIFI, with OpenRGB and that worked fine with no issues, so it would seem that the way OpenRGB interacts with DDR5 on certain motherboards is causing the issue, may potentially be fixed with !2548