Corsair Dominator Platinum RAM keep disappearing

[Alberos]

Hi,

I've a Corsair Dom Plat RAM module. It keep disappearing from the system. When it disappear everything that's reading its info went dark. AIDA64 sensor panel temps readout blank, SignalRGB stop RGBing (stop update RGB), even iCUE also didn't see the RAM too. Any idea or where to even begin collecting info to troubleshoot this? Only way to get it back is to power cycle. Restart won't work. Need shutdown, wait for lights out, then turn on again.

Thanks

[Fiery]

23 hours ago, Alberos said:

Hi,

I've a Corsair Dom Plat RAM module. It keep disappearing from the system. When it disappear everything that's reading its info went dark. AIDA64 sensor panel temps readout blank, SignalRGB stop RGBing (stop update RGB), even iCUE also didn't see the RAM too. Any idea or where to even begin collecting info to troubleshoot this? Only way to get it back is to power cycle. Restart won't work. Need shutdown, wait for lights out, then turn on again.

Thanks

Do you overclock your memory?

[Alberos]

3 hours ago, Fiery said:

Do you overclock your memory?

Technically XMP is an overclock and it is on... So.. Yes, I overclocked the memory? Should I start by disabling it?

Edit: Forgot to mention, PC works fine and I never notice the moment the RAM disappear (other than when I glance at my sensor panel and see blank memory temps).

[Fiery]

17 hours ago, Alberos said:

Technically XMP is an overclock and it is on... So.. Yes, I overclocked the memory? Should I start by disabling it?

Edit: Forgot to mention, PC works fine and I never notice the moment the RAM disappear (other than when I glance at my sensor panel and see blank memory temps).

I know it's not technically overclocking in case the memory module is rated at that speed that you choose as an XMP profile, but it may worth a try to check if the issue goes away once you lower the memory speed to a more conservative value like DDR5-4800.

[Alberos]

20 hours ago, Fiery said:

I know it's not technically overclocking in case the memory module is rated at that speed that you choose as an XMP profile, but it may worth a try to check if the issue goes away once you lower the memory speed to a more conservative value like DDR5-4800.

Alright, I have turn off XMP, it's now running at 4800 MT/s, I never touch timing tuning, so no change there. The problem still persist. It's still disappear.

I was about to say I'll report back after 1 month long term testing, we're not even making 2 hours in and it's doing again. It is very random, sometimes I can go multiple days without this happening, sometimes it happen a few hours in. I only do cold boot once a day, if it broke on that day, it stay broken until tomorrow.

Does AIDA might has logs that I can check? Or Windows might know something?

[Fiery]

4 hours ago, Alberos said:

Alright, I have turn off XMP, it's now running at 4800 MT/s, I never touch timing tuning, so no change there. The problem still persist. It's still disappear.

I was about to say I'll report back after 1 month long term testing, we're not even making 2 hours in and it's doing again. It is very random, sometimes I can go multiple days without this happening, sometimes it happen a few hours in. I only do cold boot once a day, if it broke on that day, it stay broken until tomorrow.

Does AIDA might has logs that I can check? Or Windows might know something?

I'm afraid AIDA64 won't be able to help you about this issue 😞 The SPD chip on your memory modules seem be unstable, no matter of the clock frequency.

[Alberos]

3 hours ago, Fiery said:

I'm afraid AIDA64 won't be able to help you about this issue 😞 The SPD chip on your memory modules seem be unstable, no matter of the clock frequency.

No worries, I can live with that, it has been like this for very long time now. Hope it doesn't started developing new issue because you know.... RAM is.... yeah... that... "a little pricing issues"

Thanks for the help anyway