Question about Corsair Vengeance LPX CMK64GX4M4B3466C16 displaying 4GB modules instead of the expected 16GB.
Question about Corsair Vengeance LPX CMK64GX4M4B3466C16 displaying 4GB modules instead of the expected 16GB.
Hi, I’ve heard similar concerns before. This RAM should work with Intel 300,400,500 series and X299 boards. I tested it on a 300 series motherboard and saw it list as 4GB, which is unusual. Since you have the original packaging and everything else checks out, it’s possible the module isn’t genuine or there’s an issue with the listing. Could be a mislabeling or a faulty component. It’s wise to double-check the product details or contact the seller for confirmation.
Some issues can lead to dram packages stopping while others remain operational and RAM performance stays decent. It’s rare for all dimms to fail in this precise manner.
I remain doubtful about compatibility or hardware issues due to counterfeit parts. My concern stems from testing them (after several years) on my X99 motherboard. All four DIMM slots were inserted in the same way as before, using Corsair 3000MHz modules, and the BIOS only displayed 12GB. When running Thaiphoon, it recognized all four as 4GB each. It seems likely that since this configuration isn’t listed for my motherboard and isn’t intended for it, the BIOS would default to another model instead of failing to boot. I might remove the heatsink to inspect the modules directly, but I’m worried it could complicate any future RMA process. Any advice?
It might shift to another model because the available options aren’t comprehensive enough. The current lists don’t cover all possible configurations, which limits their usefulness. Manufacturing teams typically don’t evaluate every RAM in stock, so excluding certain types doesn’t automatically disqualify them—they could still function properly.
I started by removing all but one RAM stick and checked if it worked properly. Then I swapped it and tested the other one. If everything read correctly, I moved them back in. If not, I tried changing their positions. In my situation, a faulty RAM slot in the motherboard was the cause. This should help with your troubleshooting. And if you've already done this, thank you for your time. Good luck!