• Happy holidays, folks! Thanks to each and every one of you for being part of the Tom's Hardware community!

Question Corsair Vengeance LPX with Ryzen 5600X - System Hanging

biscuits99

Distinguished
Aug 17, 2016
14
0
18,510
I've just built a new PC based on
  • 5600X
  • MSI B550 Tomahawk
  • 1060 6GB SC (From old system)
  • 2x 8GB Corsair Vengeance LPX 16GB - CMK16GX4M2B32

The system runs rock solid at the stock speeds of 2133, but when I set to 3200 in the bios using XMP, I get a couple of hours or so, then the system hangs.
The mouse responds, but the applications and windows are unresponsive. Task Manager doesnt come up with ctrl-alt-del either

Here is my RAM:
thumb_show.php


I also ran memtest, which came back with 0 errors. So I think the memory is technically fine, but for some reason has issues with XMP on this hardware combination?
It also looks like a lot of people on the forums seem to comment on issues Corsair Vengance has with Ryzen? Should I just cut my losses and get different RAM?

I have seen some memory from Corsair, basically the same model as the one I bought, being "Ryzen optmimised" whatever that means. Does some memory simply not like being overclocked?
The JEDEC rating for the RAM seems to say it can support 3200 (as opposed to needing XMP), but I'm struggling to work out which bios options to change.

I think this is the correct readout for my config?



I guess my question is, do you think this memory can run at 3200 in my system, XMP or otherwise?
 
You forgot to mention the make and model of your PSU and it's age. If the OS installation has been carried over from the older system like the GTX 1060, then you're advised to reinstall the OS. Which BIOS version are you on at the moment for your motherboard? OS version?

As with rams that have an issue with X.M.P, use the manual setting in BIOS, whereby you manually input your ram's timings, frequency and voltage in BIOS.
 
Hi,

Its a new Corsair RMx650.
Its a new Win10 installation.

I have the latest non-beta bios (Early Nov 2020).

Yes, it looks like I'll have to try manual settings in the BIOS.