When using two Kingston Fury Beast DDR5 modules, OpenRGB detects and controls RGB lighting for only one of them. The second DIMM is detected on the SPD bus but its RGB controller is not recognized, so no lighting control is possible. **Hardware setup:** ``` Motherboard: ASUS ROG Strix B650E-F Gaming WiFi (latest BIOS) CPU: AMD Ryzen 9 7900 Memory: 2X32 GB Kingston Fury Beast DDR5-6000 CL30 (KF560C30BBEA-32) OS: Windows 11 OpenRGB version: Commit id 8813c9936d86f87d92781c1cb5a033097981b8f0 ``` **Observed log snippet:** ``` ------------------------------------------------------ | Detecting I2C DIMM modules | ------------------------------------------------------ [ResourceManager] Calling detection progress callbacks. [SPDDetector] Probing DRAM older than DDR4 on bus -1, address 0x50 [DDR5DirectAccessor] SPD Hub Magic: 0x51 0x18 [SPDDetector] Probing DRAM using DDR5 Direct Accessor on bus -1, address 0x51 [ResourceManager] Detected occupied slot 2, bus 2, type DDR5 [ResourceManager] Jedec ID: 0x0117 [SPDDetector] Memory type could not be determined for bus -1, address 0x52 [DDR5DirectAccessor] SPD Hub Magic: 0x51 0x18 [SPDDetector] Probing DRAM using DDR5 Direct Accessor on bus -1, address 0x53 [ResourceManager] Detected occupied slot 4, bus 2, type DDR5 [ResourceManager] Jedec ID: 0x0117 [SPDDetector] Memory type could not be determined for bus -1, address 0x54 [SPDDetector] Memory type could not be determined for bus -1, address 0x55 [SPDDetector] Memory type could not be determined for bus -1, address 0x56 [SPDDetector] Memory type could not be determined for bus -1, address 0x57 [Kingston Fury DDR5 DRAM] is enabled [ResourceManager] Calling detection progress callbacks. [Kingston Fury DDR4/5 DRAM] looking at 0x61 [Kingston Fury DDR4/5 DRAM] 61 beginning transaction; res=00 [Kingston Fury DDR4/5 DRAM] Testing address 61 register 01, res=0708 [Kingston Fury DDR4/5 DRAM] 61 ending transaction; res=00 [Kingston Fury DDR4/5 DRAM] looking at 0x63 [Kingston Fury DDR4/5 DRAM] 63 beginning transaction; res=00 [Kingston Fury DDR4/5 DRAM] Testing address 63 register 01, res=465A [Kingston Fury DDR4/5 DRAM] Testing address 63 register 02, res=555A [Kingston Fury DDR4/5 DRAM] Testing address 63 register 03, res=525A [Kingston Fury DDR4/5 DRAM] Testing address 63 register 04, res=595A [Kingston Fury DDR4/5 DRAM] Reading model code at address 63 register 06, res=155A [Kingston Fury DDR4/5 DRAM] 63 ending transaction; res=00 [Kingston Fury DDR4/5 DRAM] detected at slot index 3 [Kingston Fury DDR5 RGB] Registering RGB controller [ResourceManager] Calling device list change callbacks. [ResourceManager] Calling device list change callbacks. [Kingston Fury DDR5 DRAM] detection end [SPDDetector] Probing DRAM older than DDR4 on bus -1, address 0x50 [SPDDetector] Probing DRAM older than DDR4 on bus -1, address 0x51 [SPDDetector] Probing DRAM older than DDR4 on bus -1, address 0x52 [SPDDetector] Probing DRAM older than DDR4 on bus -1, address 0x53 [SPDDetector] Probing DRAM older than DDR4 on bus -1, address 0x54 [SPDDetector] Probing DRAM older than DDR4 on bus -1, address 0x55 [SPDDetector] Probing DRAM older than DDR4 on bus -1, address 0x56 [SPDDetector] Probing DRAM older than DDR4 on bus -1, address 0x57 ``` **Expected behavior:** Both DIMMs should be detected and listed as “Kingston Fury DDR5 RGB” devices, allowing independent or synchronized RGB control. **Actual behavior:** Only one DIMM is detected with RGB capability. The second DIMM (I²C address 0x61) responds but does not pass the “FURY” signature check, so it is ignored. Other RGB software (Armoury Crate, SignalRGB) also fails to control the second stick. OpenRGB debug log shows address 0x61 and 0x63 being probed; only one responds with the “FURY” signature. **Supported Devices:** ``` Name Enabled HyperX Fury Ultra true Kingston Fury DDR4 DRAM true Kingston Fury DDR5 DRAM true Kingston JEDEC2 Fury DDR4 DRAM true Kingston JEDEC2 Fury DDR5 DRAM true ``` **Additional notes:** - Tested swapping DIMMs and slots: Whichever DIMM is in slot A2 works, slot B2 does not - FURY CTRL is capable of control both RGB modules - This issue occurs even when running OpenRGB as Administrator. - AMD SMBus is installed and shows no errors in Device Manager - No other RGB software is running in the background (FURY CTRL, Armoury Crate, Aura Sync, etc.). Could I be overlooking something?