I upgraded my PC from a single 32GB RAM module to 64GB by adding another 32GB stick. After installing it, the system would not boot until I cleared the CMOS. With the default memory settings, it now boots normally, and Memtest86+ completed without errors. However, enabling EXPO causes the yellow DRAM indicator to remain lit and the system never displays an image, even after waiting more than five minutes for memory training. The modules have the same advertised model, capacity, speed, latency, and part number, but they were purchased separately about four months apart. Is buying a matched 2x32GB kit significantly different from buying two individual sticks of the same model, and why might EXPO fail?
3 Answers
First check the basics: make sure the modules are installed in the motherboard's recommended slots, usually A2 and B2 for two sticks. Also compare them with CPU-Z or a similar utility to see whether the actual memory manufacturer, die type, and module revision match. Two sticks can share the same retail part number while internally using different chips, such as different Hynix, Samsung, or Micron revisions.
Yes, buying a matched 2x32GB kit can make a difference. A kit is validated together for the advertised EXPO settings, while two separately purchased modules may use different memory chips or revisions despite having the same model number. They may work perfectly at default JEDEC settings but fail when overclocked with EXPO. You can try manually tuning the speed, timings, and voltage, but there is no guarantee both sticks will run their rated profile together.
This is likely DDR5 memory training failing at the EXPO settings. Adding a second DIMM increases the load on the CPU's integrated memory controller, so a speed that worked with one stick may no longer be stable with two unmatched modules. Try updating the motherboard BIOS, reseating the RAM, and testing a lower memory speed manually. If you want the best chance of running EXPO, a matched kit is the safer choice.
That makes sense. At least both modules work without errors when EXPO is disabled.