Overclock.net banner
21 - 23 of 23 Posts
Discussion starter · #21 ·
UPDATE:

I returned home yesterday and created a Clonezilla boot USB to try cloning the drive in question to the new SSD I picked up on the way home. Installed new SSD and fired up the rig, manually chose boot override to the Clonezilla USB, and my BIOS decided to boot to the existing Windows install drive in question instead, which took all of 3 seconds, and I was in.

No performance issues, no stuttering while gaming, everything was perfect all night even after several restarts.

I am so thoroughly confused.
 
Discussion starter · #22 ·
If cause uncertain (which it is) I wouldn't even have XMP enabled for initial testing. You mention a 13700K but don't mention board or RAM type (DDR4? DDR5?) so I would recommend going to whatever the lowest JEDEC rating is (2133MHz for DDR4, 4800MHz for DDR5) and running memtest via a bootable image (again, the Ubuntu live image should provide an option to run memtest) to prove the RAM is stable, even at lowest rated speeds. I have no experience with DDR5 right now, so I don't know how the "ECC" in DDR5 handles errors; will it spew errors into a log, will it try to silently correct, will it scream about the problem at boot? If it just tries to silently correct, the problem could be caused by bad RAM and the ECC going crazy. But like I said, I have no idea how DDR5 handles it. Honestly I have no idea how or whether memtest would even show errors in DDR5.
Its an ASROCK PG Sonic motherboard and memory is CORSAIR Vengeance 32GB (2 x 16GB) 288-Pin PC RAM DDR5 6600 (PC5-52800) Desktop Memory Model CMK32GX5M2X6600C32.

Prior to all this, I've run Memtest5 @anta777 Absolut when monkeying with RAM speeds a bit and it throws errors in the same fashion as I saw on DDR4 system. After my issues resolved themselves as I went over in the above post, I did turn XMP back on last night.

I do like the idea of ruling out the RAM having any errors during a stock speed test.
 
Discussion starter · #23 ·
Issue was an old SSD was failing. Not a boot drive, but Windows was having hard time reading it and if effed up the startup process.
 
21 - 23 of 23 Posts