- Jan 9, 2025
- 2
- 0
- 10
I've posted this on other forums, trying to get information... But without any luck.
I got several RAM Kits to test. All of them are non-RGB, 64GB (2x32GB / Dual Rank), CL30.
On most of them, I'm having weird SPD issues.
Like, when monitoring them (via HWiNFO, HWMonitor, AIDA64, etc.) they will "disappear" from the system after some time. Anything monitoring them will stop reporting temperature updates or will show show 0.0°C.
When trying to view SPD in AIDA64 or CPU-Z, it will only display 1 stick of RAM, or sometimes 0. It's like the sticks have disappeared. I can no longer query them (no temps, no timings, nothing). The computer seems to work fine, though (it's not like a bad connection and they were pulled).
Kingston KF560C30-32 (Hynix A-Die):
Corsair Vengeance CMK64GX5M2B6000Z30 (Hynix A-Die):
Silicon Power SP064GXLWU60AFD (Hynix M-Die):
G.Skill F5-6000J3040G32G (Hynix M-Die):
I've moved sticks around in 4-stick configuration, and the problems follows the RAM, not the motherboard slot they are in. i.e.:
Kingston in A2 and B2: SPD info for the stick in A2 disappears.
Kingston in A1 and B1 and G.Skill in A2 and B2: SPD info for the stick in A1 disappears.
I can clean boot and just load just 1 monitoring app like HWMonitor, and SPD info still blanks out after a few minutes with the Kingston / Corsair / Silicon Power. Then again, I can load HWiNFO, HWMonitor, AIDA64, and CPU-Z all at the same time and query SPD over and over and the G.Skill keeps showing its info, just fine.
I tested with Windows 11 and a clean install of Windows 10 (installed specifically for testing this to rule-out OS issues).
Since I've had the most luck with the G.Skill, I'll probably be keeping that (it's kinda important to know if a component is getting too hot, you know). These are all NEW sticks of RAM (manufacture dates range from October 2024 to late November 2024), so I'm not sure if it's some new SPD chip incompatibility issue. Thaiphoon seems to read different SPD info on the G.Skill compared to the others, which may have something to do with why it keeps working when the other SPD chips stop.
The Kingston and Silicon Power kits are on the QVL for my motherboard, so I figured they would definitely be fully supported.
I've searched a bunch and found a few other threads where people mentioned SPD info just "disappearing" (or a claim that their RAM doesn't even report their temperatures), but I haven't found any actual causes or fixes.
Does anyone know what the issue could be?
CPU: Ryzen 7 9700X
Motherboard: ASUS X670E-A
BIOS: 2506 (Nov 2024)
I actually have a fifth memory kit (2x24GB) and a replacement motherboard arriving soon that I will be testing.
I figure that if I try multiple sticks of RAM, multiple types of RAM, multiple motherboards, multiple OS installs on multiple SSDs (and eventually multiple CPUs), I might find the issue.
I got several RAM Kits to test. All of them are non-RGB, 64GB (2x32GB / Dual Rank), CL30.
On most of them, I'm having weird SPD issues.
Like, when monitoring them (via HWiNFO, HWMonitor, AIDA64, etc.) they will "disappear" from the system after some time. Anything monitoring them will stop reporting temperature updates or will show show 0.0°C.
When trying to view SPD in AIDA64 or CPU-Z, it will only display 1 stick of RAM, or sometimes 0. It's like the sticks have disappeared. I can no longer query them (no temps, no timings, nothing). The computer seems to work fine, though (it's not like a bad connection and they were pulled).
Kingston KF560C30-32 (Hynix A-Die):
- temps read 0.0°C after a few minutes
- Thaiphoon's info on SPD is "Model: SPD5118, Device Type: SPD0000"
Corsair Vengeance CMK64GX5M2B6000Z30 (Hynix A-Die):
- temps read 0.0°C after a few minutes
- Thaiphoon's info on SPD is "Model: SPD5118, Device Type: SPD0000"
Silicon Power SP064GXLWU60AFD (Hynix M-Die):
- temps read 0.0°C after a few minutes
- "Part Number" is blank, so no name ever shows in apps like ZenTimings, HWiNFO, etc.
- Thaiphoon's info on SPD is "Model: SPD5118, Device Type: SPD0000"
G.Skill F5-6000J3040G32G (Hynix M-Die):
- All SPD seems fine, readings never disappear!
- Thaiphoon's info on SPD is "Model: Unknown, Device Type: SPD5118"
I've moved sticks around in 4-stick configuration, and the problems follows the RAM, not the motherboard slot they are in. i.e.:
Kingston in A2 and B2: SPD info for the stick in A2 disappears.
Kingston in A1 and B1 and G.Skill in A2 and B2: SPD info for the stick in A1 disappears.
I can clean boot and just load just 1 monitoring app like HWMonitor, and SPD info still blanks out after a few minutes with the Kingston / Corsair / Silicon Power. Then again, I can load HWiNFO, HWMonitor, AIDA64, and CPU-Z all at the same time and query SPD over and over and the G.Skill keeps showing its info, just fine.
I tested with Windows 11 and a clean install of Windows 10 (installed specifically for testing this to rule-out OS issues).
Since I've had the most luck with the G.Skill, I'll probably be keeping that (it's kinda important to know if a component is getting too hot, you know). These are all NEW sticks of RAM (manufacture dates range from October 2024 to late November 2024), so I'm not sure if it's some new SPD chip incompatibility issue. Thaiphoon seems to read different SPD info on the G.Skill compared to the others, which may have something to do with why it keeps working when the other SPD chips stop.
The Kingston and Silicon Power kits are on the QVL for my motherboard, so I figured they would definitely be fully supported.
I've searched a bunch and found a few other threads where people mentioned SPD info just "disappearing" (or a claim that their RAM doesn't even report their temperatures), but I haven't found any actual causes or fixes.
Does anyone know what the issue could be?
CPU: Ryzen 7 9700X
Motherboard: ASUS X670E-A
BIOS: 2506 (Nov 2024)
I actually have a fifth memory kit (2x24GB) and a replacement motherboard arriving soon that I will be testing.
I figure that if I try multiple sticks of RAM, multiple types of RAM, multiple motherboards, multiple OS installs on multiple SSDs (and eventually multiple CPUs), I might find the issue.
Facebook
Twitter
Instagram