I just upgraded recently to an Alder Lake non-K processor (i5 12600) with a H670 PG Riptide ASRocK motherboard. I initially put some Corsair Vengeance DDR 3600 RAM into it. It was set by default to the slow JEDEC profile, so I set the XMP profile and it seemed to run fine during install of Windows, etc.
However, after Windows install I tried some games, I was having Blue Screens, crashes, etc. So I reverted to the JEDEC 2133 default profile (turned off XMP). It was less prone to crashes, but still had the frequent BSOD, crashes.
I then switched to using non-XMP 3200 Team memory and still had issues. I tried updating the BIOS, GPU bios, etc, but no luck.
Then I ran Prime95 Torture Test with large FFTs. It would fail with a rounding error constantly within seconds. Suggestions online included resetting the CMOS. I didn't see why this would have any issue since the only thing I ever really changed in the BIOS was XMP profile and then I reverted it.
However, after shorting the CMOS jumpers on the motherboard, and starting it up, everything ran perfectly and no more crashes. Prime95 no longer fails, etc. I don't know why that would make such a big difference but it totally seems to have fixed it.
Maybe this ASRocK MB had some bad voltage value saved into it that didn't reset? Maybe it is buggy. It is kind of a cheaper motherboard.
Anyways, I am happy now, totally stable no matter what game or test I throw at it.
Was it just a simple reset of the CMOS? Why would that make such a difference? Any ideas? In any case, it would be nice to know, and if anyone has the same issue, hope this post helps.
However, after Windows install I tried some games, I was having Blue Screens, crashes, etc. So I reverted to the JEDEC 2133 default profile (turned off XMP). It was less prone to crashes, but still had the frequent BSOD, crashes.
I then switched to using non-XMP 3200 Team memory and still had issues. I tried updating the BIOS, GPU bios, etc, but no luck.
Then I ran Prime95 Torture Test with large FFTs. It would fail with a rounding error constantly within seconds. Suggestions online included resetting the CMOS. I didn't see why this would have any issue since the only thing I ever really changed in the BIOS was XMP profile and then I reverted it.
However, after shorting the CMOS jumpers on the motherboard, and starting it up, everything ran perfectly and no more crashes. Prime95 no longer fails, etc. I don't know why that would make such a big difference but it totally seems to have fixed it.
Maybe this ASRocK MB had some bad voltage value saved into it that didn't reset? Maybe it is buggy. It is kind of a cheaper motherboard.
Anyways, I am happy now, totally stable no matter what game or test I throw at it.
Was it just a simple reset of the CMOS? Why would that make such a difference? Any ideas? In any case, it would be nice to know, and if anyone has the same issue, hope this post helps.
Facebook
Twitter
Instagram