I think I've stated that this persists through Windows installs previously.
The theory I was testing was if OpenRGB would trigger the RAM to disappear. It did not, it only does this when HWINFO is open for a little while. It can be only HWINFO open with no other apps (including MSI BIOS...
Update: I've recently been trying to figure out what makes this happen, as I've stated before, a fresh install of W10 with only HWInfo causes this to happen.
I've been messing with OpenRGB and HWInfo a little - I can use the PC for hours with OpenRGB even polling and 'communicating' for lack of...
I'm using the computer as we speak and yeah, after about 30 - 40mins of mostly idlying and light usage, one of the modules switched to YES, PMIC over voltage to be exact. Is there a way I can send a log?
And about 2 minutes after writing this, all of them went to YES, so PMIC overvoltage, PMIC...
Hey update: I've installed a fresh copy of Windows, everything running dandy again, I've also downgraded the BIOS to the one I mentioned (released Dec 24), and this still happens. I've actually gone ahead and ran ycruncer for about 30mins and all seems well, no errors.
The only thing installed...
I turned off the MSI app in BIOS, and I've turned off the RGB controls in the BIOS. the only other thing I can think of is Radeon Adrenalin, the actual drivers for the GPU side of things. As I said it's a fresh install.
Thanks for the quick answer.
Excuse the mess of a title.
I've recently reinstalled Windows and have updated my BIOS (from an earlier one released in Oct/Nov 24), and I seem to have issues (?) reading out all the sensors in the RAM panels.
When Windows starts up, everything is fine in HWINFO, it shows normal readings from...