[Bug Report] TeamGroup DDR5 RAM Detection Issue due to OpenRGB Release Candidate 1.0rc1
Description of Bug
Whenever OpenRGB is opened and then closed, DDR5 RAM from TeamGroup is no longer detected by other software such as HWInfo, RAMMon, or even OpenRGB itself. The only way to resolve this issue is by rebooting the system. This behavior seems exclusive to OpenRGB and occurs only with TeamGroup RAM. Other brands tested (Viper, G.Skill) do not exhibit this issue. It appears the SMBus becomes inaccessible.
Steps to reproduce:
Open OpenRGB.
Close OpenRGB.
Attempt to detect RAM using HWInfo, RAMMon, or OpenRGB after second startup.
The issue is consistent across Windows and ArchLinux systems, regardless of OpenRGB version (0.9, RC1 or the latest Git build).
Similar to discord link, but without any warning messages from HWInfo.
Attached Log
Logs attached were captured with the verbose logging mode (--loglevel 6) using the RC1 build of OpenRGB. First log is when it's detected properly.
Operating System
OS - Windows 11: Issue occurs.
OS - Linux (ArchLinux, up-to-date): Issue occurs.
Hardware Configuration
Motherboard: MSI Z790 Carbon WiFi
RAM: TeamGroup DDR5 (two tested models)