F5F Stay Refreshed Hardware Desktop Problem detected, system fails to start with dual RAM modules. Please check connections and configuration.

Problem detected, system fails to start with dual RAM modules. Please check connections and configuration.

Problem detected, system fails to start with dual RAM modules. Please check connections and configuration.

Pages (2): Previous 1 2
B
Beau_Henderson
Junior Member
12
08-06-2022, 11:13 AM
#11
I also tested the newest releases, but it didn’t work. I can still start up with just one stick, though not both.
B
Beau_Henderson
08-06-2022, 11:13 AM #11

I also tested the newest releases, but it didn’t work. I can still start up with just one stick, though not both.

J
JBN11
Junior Member
41
08-09-2022, 09:28 PM
#12
It seems unusual. The main thought is the sticks don't match and you're facing memory problems. You can verify using CPU-Z or a tool called Thaiphoon Burner. CPU-Z works faster but isn't as detailed—look for the SPD tab under DRAM Manufacturer, which should list Samsung, Micron, or SK Hynix (though DDR5 readings might be tricky). Check both DIMMs; they should match unless one is M die and the other A die, which would need further investigation. In Thaiphoon Burner, open the unit, run a read SPD command, and take screenshots of each DIMM report. If they appear identical, the problem likely lies elsewhere. I'm running out of ideas here, but nothing seems to block power-on completely.
J
JBN11
08-09-2022, 09:28 PM #12

It seems unusual. The main thought is the sticks don't match and you're facing memory problems. You can verify using CPU-Z or a tool called Thaiphoon Burner. CPU-Z works faster but isn't as detailed—look for the SPD tab under DRAM Manufacturer, which should list Samsung, Micron, or SK Hynix (though DDR5 readings might be tricky). Check both DIMMs; they should match unless one is M die and the other A die, which would need further investigation. In Thaiphoon Burner, open the unit, run a read SPD command, and take screenshots of each DIMM report. If they appear identical, the problem likely lies elsewhere. I'm running out of ideas here, but nothing seems to block power-on completely.

Pages (2): Previous 1 2