Question Strange Problem When Overclocking RAM
Question Strange Problem When Overclocking RAM
I have a Ryzen 7 1700 overclocked at 3.7 GHz with 1.35v and it operates without issues, but whenever I touch the RAM it immediately stops functioning. I own 32 GB of Corsair 3000 Mhz RAM in dual channel on a B350 PC-MATE motherboard. I have experimented with underclocking and overclocking the base CPU, yet the problem persists. I've adjusted voltages, flashed the BIOS, tested it on another CPU, RAM, and motherboard, but nothing works. Removing two sticks didn't help either. My PSU is 750 watts, so power isn't the concern. I'm not changing timing settings, only trying to increase the MHz speed. What could I be doing incorrectly?
It would be helpful to have the model numbers for your RAM, as well as additional details about your system. I’m looking for information on the type of power supply unit you’re using.
I prefer an 80+ Bronze certified PSU as a minimum.
I’d begin by resetting your CPU to its default configuration and employing a diagnostic program to assess your memory. Windows includes a built-in memory checker, or I suggest using MemTest86. Execute this to verify the integrity of your RAM. If any problems are detected, I hope you can initiate a return or obtain a replacement.
I’m not certain about the age of your hardware, but it’s common for components to still be covered under warranty. Here are relevant links:
MemTest86 - Official Site of the x86 Memory Testing Tool
https://www.memtest86.com
You can also verify compatibility on the MSI website. Although I don’t own this specific board, I haven’t encountered major issues with standard RAM. Others have reported problems that are discussed in various forums. Here’s the relevant page:
https://www.msi.com/Motherboard/support/...ort-mem-12
Regarding the BIOS update, do you have the latest version installed for your board? I believe it’s version 7A34vAJ. You can find the update instructions here:
https://www.msi.com/Motherboard/support/...#down-bios
Have you experimented with XMP profiles in the BIOS for your RAM? I achieved positive outcomes with those settings. Would you like to know if they work for your configuration?
RAM is often the most difficult aspect to overclock at the moment. This is just my perspective; CPU and GPU overclocking are generally straightforward in many cases. Ryzen systems perform well with faster RAM, and I’ve observed excellent results from RAM overclocking. Nevertheless, slight deviations in timings or voltages can lead to boot failures. Some MSI boards include a memory feature that permits multiple boot retries before reverting to a bootable state. I assume you need to enable the expert OC option under Memory Try It.
I routinely test new parts to confirm proper functionality. Although I’m new to this forum today, I’ve read extensively here, but haven’t participated before. I’m sharing a process I follow, and anyone with additional insights is welcome. Please share your experience and any further details you can provide.
The model number of the RAM isn't clear and I'm not bothering to find it. I own a Corsair RM750x 80+ Gold Fully Modular PSU with 5 rails. I adjusted my clock speeds back to stock, reached 2400 MHz (1.3v), and memory tests restored CPU speeds. Other settings cause crashes. The system is about 3 months old despite regular upgrades. I'm using that BIOS version and haven't succeeded with XMP this time either. You should check that setting—it seems familiar. I'm currently busy but will keep you updated.
Just to confirm, you ran Memtest86 and it passed. It would still be helpful to have the RAM model number. This assists anyone who used it or read about it to ensure it doesn’t have a common issue. It also aids in confirming the stock voltage for that RAM so you can adjust the BIOS settings accordingly. Have you attempted removing two sticks again after resetting the BIOS, making sure the remaining ones are in the right DIMMs, then trying an XMP profile or manual overclock? I understand this process feels repetitive, but it’s often about trial and error. I hope someone else has encountered this problem and can quickly recognize it.