One of your RAM modules isn't working properly and shows a red indicator after restarting the system.
One of your RAM modules isn't working properly and shows a red indicator after restarting the system.
Hey all, Ever since a month or so ago I've had a weird issue where one of my sticks of ram (Corsair Vengeance RGB 2x16gb 3600mhz) hasn't been lighting up properly after I reboot my pc. If I reseat the ram stick or unplug my pc from the wall it works perfectly and then as soon as I reboot the pc the issue happens again. Most of the time the RGB just won't work at all, and occasionally (like shown in the video below) there will be a single red light on the bottom and the top of the stick. The actual ram is still detected so it's not an issue with the entire stick, just the lighting part of it. It has happened on the 2 most latest bios versions of my motherboard as I updated my bios as one of the troubleshooting steps. Video showing the issue: Breakdown of what I have in my ram slots: Slot 1: Corsair Vengeance RGB Lighting Kit Slot 2 (The faulty one): Corsair Vengeance RGB 16gb 3600mhz Slot 3: Corsair Vengeance RGB Lighting Kit Slot 4: Corsair Vengeance RGB 16gb 3600mhz Also it might be worth noting that I use SignalRGB and the ram stick just doesn't show up in there either. ^ Image of the devices tab in SignalRGB showing 3 sticks instead of 4 ^ Image of the layout tab in SignalRGB which shows that the 2nd ram stick is gone from the layout. (Again, if I reseat it or unplug my pc from the wall and turn it back on then it works completely fine, but breaks again after a restart/shutdown) Full PC Specs: https://uk.pcpartpicker.com/b/gPnLrH I wanted to know if anyone else has had the same issue and has fixed it or if anyone has anything that might be a good idea to try Thanks!
Consider the possibility of a faulty RAM. Try booting the system using only that stick, testing each slot until you're ready to respond.
It seems quite unusual since the problem has stopped occurring after you reported it. The RAM sticks are now functioning properly, and the issue appears to resolve itself when you ask for assistance. I haven’t marked it as solved yet, as I’m concerned it might happen again soon. I’ll give it another try once that happens.