[Bug Report] Trident Z DRAM control and detection

Description of Bug

G. Skill Trident Z DRAM is not controllable when detected. The lights do not respond in any mode but rather stay on the default rainbow setting. Moreover, when attempting a re-scan or restart of openRGB the modules are then not detected at all. Sometimes during the re-scan process my PC hard shuts down with no bluescreen or error, just "click" and black. I have tried this with the 0.9 stable release and a recent pipeline version downloaded 2 days ago with the same behaviour. I have taken care to follow the SMBus instructions, launching openRGB as administrator. I have also made sure that openRGB is the only lighting program installed/running and still get the same behaviour. These dram modules are controllable from other programs, namely the official GSkill lighting control, MSI's mystic light, and signal RGB. None of these 3 seem to have problems with the DRAM (though they have significantly reduced functionality compared to OpenRGB) so I do not think this is a hardware issue.

Attached Log

Here is a log where the modules were initially detected. I tried (unsuccessfully) changing the lighting mode a couple times on all 4 modules, then changed lighting modes on my other system lights which was successful. I then re-scanned devices and the DRAM modules dissapeared. OpenRGB_20250201_130701.log

I am happy to collect/provide any additional info which may help in debugging and resolving this issue.

Operating System

"OS - Windows 11"

Hardware Configuration

Here are some CPU-Z screenshots with info for my whole system in case that is useful. The lights on my motherboard and attached via motherboard's argb plug work without issue. I have updated my mobo to latest available bios and have run windows update just before collecting the attached logs.

Thank you very much for trying to help. I really just want all my lights to work!