[Bug Report] system hard reboot on attempt to detect on XPG Lancer Blade

Description of Bug

On Windows:

• run openrgb -> mentions that wasn't run as Administrator yet, shows other devices
• run openrgb as Administrator -> once reaches HW detection phase, whole PC hard reboots; further, it doesn't POST, and debug LEDs show issue with memory (orange light)
• do full power down, power up -> things come back
• run openrgb --nodetect > then disable "ENE SMBus DRAM" in "Supported Devices"
• run openrgb as Administrator -> comes up no problem (naturally mem rgb not detected)

The above was with latest pipeline too (did this today)

Same on Linux:

• run openrgb -> complains that need udev script, for access
• install udev script, restart openrgb -> same failure mode
• run openrgb --nodetect + disable ENE SMBus DRAM -> openrgb runs fine

Attached Log

I can attach these, but my impression would be that they would be truncated, since system does hard reboot.

Operating System

OS - Linux - Linux Mint 21.2 (whatever current "stable" is) OS - Windows - Win 10 Pro

Hardware Configuration

The memory in question is: XPG Lancer Blade RGB 32GB (2x16GB) DDR5 6000MHz CL30

Running this with EXPO/XMP turned off (was initially worried about general mem stability), on ASUS ROG STRIX B650E-F mobo, latest BIOS, latest drivers / firmware for everything.

For comparison (to point out it is unlikely to be faulty mem stick):

• SignalRGB can fully control the mem stick RGB
• Armoury Crate does not recognize the mem (does not list as controllable), but no crashes/hiccups in any detection stage