[Bug Report] Kingston Fury Beast not detected unless iCue is run first. KF560C30BWEAK2-32 16GB DDR5 6000 CL30 White RGB EXPO

Description of Bug

Boot Windows, start OpenRGB, no Kingston detected. Other supported hardware (motherboard and RGB hub, see below) are detected just fine.

Start the Corsair iCue utility, exit after a couple of seconds, then start OpenRGB. Now the RAM is detected along with the motherboard and the RGB hub. Effects on the RAM stick work, setting individual LEDs in static mode sometimes works, sometimes doesn't, maybe user error.

Attached Log

OpenRGB log before running iCue. openrgb-log-nokingston.txt

OpenRGB log after running iCue. openrgb-log-kingstondetected.txt

I2C log of running iCue, only one RAM stick installed, obtained with a slightly modified i2c_sniffer_piix4 regdump-one.txt

I2C log of running iCue, both RAM sticks installed regdump-both.txt

Operating System

Windows 11 Pro 23H2

Working fine on Linux (Ubuntu Cinnamon 24.10) after sorting out SMBus access issues, i.e. kernel commandline needs "acpi_enforce_resources=lax" and blacklist spd5118 module.

Hardware Configuration

Gigabyte B650E Aorus Elite X AX Ice (single LED below the chipset heatsink works, nothing is connected to the ARGB headers)

AMD Ryzen 5 7600X

2 x Kingston Fury Beast KF560C30BWEAK2-32 16GB DDR5 6000 CL30 White RGB EXPO (kit)

Corsair iCUE Commander CORE XT (iCUE H100i Elite Capellix XT and some case fans, works in static mode only)

Zotac Geforce RTX 4070 Ti Super Trinity OC White (not supported, working on it)

NZXT Function Tenkeyless Keyboard

SPC Gear SPG147 mouse