F5F Stay Refreshed Hardware Desktop Noted, RAM compatibility with your MoBo has been identified. Let's explore options for fixing or replacing it.

Noted, RAM compatibility with your MoBo has been identified. Let's explore options for fixing or replacing it.

Noted, RAM compatibility with your MoBo has been identified. Let's explore options for fixing or replacing it.

Pages (2): 1 2 Next
N
nickmill48
Member
165
03-20-2023, 08:24 AM
#1
Hi everyone. Here are the key points: RAM model is G.Skill Ripjaws S5 32 GB (2 x 16 GB) DDR5-6400 CL32. Motherboard uses MSI PRO B650M-A with Wi-Fi, AM5 CPU and AMD Ryzen 5 7600. I noticed RAM isn't listed in the compatibility section, and XMP speed is set higher than the CPU default. I suspect possible instability causing random crashes. Should I lower RAM speed from 6400 to 6000 in BIOS? Are timing adjustments necessary? How can I verify stability? Until I find a fix, should I disable XMP? It seems risky as instability could damage data. Thanks for your help.
N
nickmill48
03-20-2023, 08:24 AM #1

Hi everyone. Here are the key points: RAM model is G.Skill Ripjaws S5 32 GB (2 x 16 GB) DDR5-6400 CL32. Motherboard uses MSI PRO B650M-A with Wi-Fi, AM5 CPU and AMD Ryzen 5 7600. I noticed RAM isn't listed in the compatibility section, and XMP speed is set higher than the CPU default. I suspect possible instability causing random crashes. Should I lower RAM speed from 6400 to 6000 in BIOS? Are timing adjustments necessary? How can I verify stability? Until I find a fix, should I disable XMP? It seems risky as instability could damage data. Thanks for your help.

I
InfinityAnt
Member
53
03-21-2023, 06:11 PM
#2
Lower the clock speed to 6000Mhz, which is ideal for Ryzen 7000. For stability testing, run various stress tests. I usually just let the system run normally; if it crashes, it’s not stable. RAM issues often cause crashes or blue screens and rarely damage files or pose risks. You don’t need to worry much. If possible, return the RAM and install a 6000Mhz CL30 EXPO kit. See if it works without XMP settings. If problems persist, there could be another problem.
I
InfinityAnt
03-21-2023, 06:11 PM #2

Lower the clock speed to 6000Mhz, which is ideal for Ryzen 7000. For stability testing, run various stress tests. I usually just let the system run normally; if it crashes, it’s not stable. RAM issues often cause crashes or blue screens and rarely damage files or pose risks. You don’t need to worry much. If possible, return the RAM and install a 6000Mhz CL30 EXPO kit. See if it works without XMP settings. If problems persist, there could be another problem.

S
sopispink
Member
217
03-22-2023, 01:15 AM
#3
I wouldn't really think so. Reducing speed a bit actually eases the timing a little, which might make things more consistent. Running memory stress tests helps you see how a configuration holds up under pressure. If you want feedback, you can ask ten people and collect varied responses. The method I’ve used works best with TestMem5 using the 1usmus_v3 preset, set to run for 30 cycles. There are many options available, and this one stands out because it’s a bit more unusual to set up. Still, these tests only show instability, not certainty. You can try longer and harder tests to push the limits and see if it holds up, though it’s hard to guarantee 100% stability. It’s possible, but usually you’ll be fine if you only run it briefly while checking stability.
S
sopispink
03-22-2023, 01:15 AM #3

I wouldn't really think so. Reducing speed a bit actually eases the timing a little, which might make things more consistent. Running memory stress tests helps you see how a configuration holds up under pressure. If you want feedback, you can ask ten people and collect varied responses. The method I’ve used works best with TestMem5 using the 1usmus_v3 preset, set to run for 30 cycles. There are many options available, and this one stands out because it’s a bit more unusual to set up. Still, these tests only show instability, not certainty. You can try longer and harder tests to push the limits and see if it holds up, though it’s hard to guarantee 100% stability. It’s possible, but usually you’ll be fine if you only run it briefly while checking stability.

R
Rey_Gordo6
Member
51
03-22-2023, 08:20 AM
#4
Checking at 6000 MHz usually doesn’t require timing adjustments unless you’re targeting specific applications. The XMP settings should remain the same. For a reliable RAM check, use free tools like MemTest86 or CrystalDiskInfo—they’re simple and effective.
R
Rey_Gordo6
03-22-2023, 08:20 AM #4

Checking at 6000 MHz usually doesn’t require timing adjustments unless you’re targeting specific applications. The XMP settings should remain the same. For a reliable RAM check, use free tools like MemTest86 or CrystalDiskInfo—they’re simple and effective.

N
Neuil
Junior Member
32
03-22-2023, 10:01 AM
#5
Timings shouldn't be a concern with an XMP profile. Memtest64 is frequently used to check RAM stability.
N
Neuil
03-22-2023, 10:01 AM #5

Timings shouldn't be a concern with an XMP profile. Memtest64 is frequently used to check RAM stability.

I
IzADerpCookie
Member
228
03-22-2023, 04:02 PM
#6
@RONOTHAN## and @Hinjima Thank you. Is there a relatively easy to understand guide out there that can show me how to use one of these tests? Also, I've been running the system with XMP enabled since I bought it in January. What are the chances, my files get corrupted?
I
IzADerpCookie
03-22-2023, 04:02 PM #6

@RONOTHAN## and @Hinjima Thank you. Is there a relatively easy to understand guide out there that can show me how to use one of these tests? Also, I've been running the system with XMP enabled since I bought it in January. What are the chances, my files get corrupted?

E
EndermanMan18
Senior Member
250
03-22-2023, 08:59 PM
#7
Observe how many mistakes appear during a memory stress test before deciding. A single error in eight hours seems unlikely (possible but not highly probable). With fifty errors in twenty seconds, I could be concerned. Assuming an error occurs during the test is probable, MemTest86+ appears to be the simplest option available. Simply follow the website’s steps to create a USB drive, boot it, start the program, and let it operate. I haven’t experienced a high success rate in actually detecting issues, but if the setup is unstable it might be worth trying. TestMem5 seems unusual, and I haven’t found a clear tutorial, so here’s my approach. Obtain the file from: https://www.overclock.net/threads/memory...s.1751608/ Remove the archive. Open TM5.exe. On launch, you’ll likely see an error prompt—accept all options. Restart after the initial run for proper functioning. Before starting, press “Load Config & Exit.” Move the extracted folder into the bin directory and pick “1usmus_v3.cfg.” Restart your system to resolve the error in step 4. Before using the program, modify “1usmus_v3.cfg,” adjusting line 13 (cycles) to a greater number than three. I usually set it to thirty, which should take roughly three hours and typically uncovers most issues, though you can adjust the duration as needed. Run TM5.exe with administrator privileges and wait until completion, minimizing background processes to maximize memory usage.
E
EndermanMan18
03-22-2023, 08:59 PM #7

Observe how many mistakes appear during a memory stress test before deciding. A single error in eight hours seems unlikely (possible but not highly probable). With fifty errors in twenty seconds, I could be concerned. Assuming an error occurs during the test is probable, MemTest86+ appears to be the simplest option available. Simply follow the website’s steps to create a USB drive, boot it, start the program, and let it operate. I haven’t experienced a high success rate in actually detecting issues, but if the setup is unstable it might be worth trying. TestMem5 seems unusual, and I haven’t found a clear tutorial, so here’s my approach. Obtain the file from: https://www.overclock.net/threads/memory...s.1751608/ Remove the archive. Open TM5.exe. On launch, you’ll likely see an error prompt—accept all options. Restart after the initial run for proper functioning. Before starting, press “Load Config & Exit.” Move the extracted folder into the bin directory and pick “1usmus_v3.cfg.” Restart your system to resolve the error in step 4. Before using the program, modify “1usmus_v3.cfg,” adjusting line 13 (cycles) to a greater number than three. I usually set it to thirty, which should take roughly three hours and typically uncovers most issues, though you can adjust the duration as needed. Run TM5.exe with administrator privileges and wait until completion, minimizing background processes to maximize memory usage.

I
ivan_ghost123
Junior Member
1
03-24-2023, 08:11 AM
#8
You're welcome. I have a few more things to clarify. When you open the BIOS and search for the 6000 MT/s configuration, will the timing and voltage match the 6400 setting, or will they vary depending on a preset? Also, if issues arise, can you still access the BIOS settings to troubleshoot?
I
ivan_ghost123
03-24-2023, 08:11 AM #8

You're welcome. I have a few more things to clarify. When you open the BIOS and search for the 6000 MT/s configuration, will the timing and voltage match the 6400 setting, or will they vary depending on a preset? Also, if issues arise, can you still access the BIOS settings to troubleshoot?

4
4rw3D
Junior Member
24
03-29-2023, 07:25 AM
#9
You have two options. MSI offers a menu feature named "Memory Try It!" which provides ready-made memory configurations based on specific frequency and CAS latency settings. Alternatively, you can manually set the memory speed to 6000MT/s from the default 6400. If the device fails to power on, you can reset the CMOS, which should restore it to the original BIOS state. Common methods include briefly connecting a jumper, removing the CMOS battery for a minute, or using a dedicated reset button on the board. This process will reinitialize the system to factory defaults, erasing any BIOS modifications and allowing a fresh boot.
4
4rw3D
03-29-2023, 07:25 AM #9

You have two options. MSI offers a menu feature named "Memory Try It!" which provides ready-made memory configurations based on specific frequency and CAS latency settings. Alternatively, you can manually set the memory speed to 6000MT/s from the default 6400. If the device fails to power on, you can reset the CMOS, which should restore it to the original BIOS state. Common methods include briefly connecting a jumper, removing the CMOS battery for a minute, or using a dedicated reset button on the board. This process will reinitialize the system to factory defaults, erasing any BIOS modifications and allowing a fresh boot.

C
CloseToToast
Member
125
04-04-2023, 03:43 AM
#10
Thanks all. I'll let you know once I've implemented your ideas.
C
CloseToToast
04-04-2023, 03:43 AM #10

Thanks all. I'll let you know once I've implemented your ideas.

Pages (2): 1 2 Next