The issue with the Ryzen 5 5600X on the MSI MAG B550 TOMAHAWK has become more severe following BIOS modifications.
The issue with the Ryzen 5 5600X on the MSI MAG B550 TOMAHAWK has become more severe following BIOS modifications.
Hello everyone,
I’m an IT technician working on a Ryzen 5 5600X build that’s consistently encountering BSODs and freezes. At first, the system would freeze and trigger a BSOD after just a few days of normal operation, especially when the load was low. We made some BIOS adjustments that others reported helped stabilize things, but instead of bringing the problem under control, the system now experiences BSODs almost immediately after booting, even under minimal stress.
I’m trying to understand what’s happening and if there are better solutions. Here’s a quick summary of the hardware and changes:
Hardware:
- Motherboard: MSI MAG B550 TOMAHAWK (MS-7C56)
- CPU: AMD Ryzen 5 5600X
- RAM: DDR4 3200MHz (16-20-20-39 via XMP, 2x8GB kit)
Changes made:
- Adjusted CPU core voltage to Offset Mode with +0.0125V.
- Updated CPU and SoC voltage to Offset Mode with +0.0125V.
- Enabled A-XMP profile for DDR4 at 3200MHz.
- Set FCLK frequency to 1600MHz.
Current issues:
- The system now freezes and shows BSOD within minutes of startup, regardless of load.
- Performance has deteriorated rather than improved.
- Previous stability issues have worsened.
What we’ve ruled out:
- RAM passed MemTest86 without errors.
- Storage passed CHKDSK and SMART checks.
- Temperatures remain below 80°C under load.
Questions for you:
- Are these voltage adjustments exacerbating the problem?
- Would it help to experiment with different values?
- Does this pattern point to a hardware fault (CPU, motherboard, PSU)?
- Are there other BIOS settings we should adjust before considering an RMA?
We’re at a stage where an RMA might be necessary, but I’d value any advice or experiences from others who’ve faced similar issues first. Any suggestions would be very helpful. Thank you in advance!
Welcome to the forums, newcomer!
These voltage settings seem to be causing more issues? Should we explore other options?
Is there any reason you need to adjust the voltages? What is the current condition of the platform when using stock values or voltages?
Motherboard:
MSI MAG B550 TOMAHAWK (MS-7C56)
What BIOS version are you running on your motherboard?
RAM:
Passed
MemTest86: no errors after 10 passes.
Temperatures: keep below 80°C under load.
Taxed by what?
System Specs:
Motherboard: MSI MAG B550 TOMAHAWK (MS-7C56)
CPU: AMD Ryzen 5 5600X
RAM: DDR4 3200MHz (16-20-20-39 via XMP, 2x8GB kit)
When sharing a troubleshooting thread, it's standard to provide your full system specifications. List them clearly as follows:
CPU:
CPU cooler:
Motherboard:
RAM:
SSD/HDD:
GPU:
PSU:
Chassis:
OS:
Monitor:
Please include the age of the PSU along with its make and model. Also, provide the current BIOS version for your motherboard.
There are no fixed rules for adjusting a system's speed without affecting its reliability. Any modifications outside standard configurations must undergo detailed testing to confirm stability.
Indeed, the voltage discrepancies seem to be exacerbating the issue.
If this occurs during factory settings, proceed directly to RMA.
Hi all - here’s a brief update on things.
The situation involved upgrading a client’s computer with an old Sandy bridge Intel processor. We moved his SSD to the new machine, changed the boot sector to support UEFI, and then copied the setup to an NVMe drive. All driver references were removed, and the latest BIOS drivers were installed. Despite this, occasional crashes still occurred.
We tried running the RAM through memtest x86 and using Windows’ built-in tool, both indicating the RAM was functioning well. NVMe tests also confirmed the drive was healthy.
Once we tried to stabilize the system, things deteriorated quickly, and we reset the BIOS back to factory defaults right away. The client should not experience blue screens.
I only entered overclocking settings after being advised to make changes, which unfortunately made matters worse.
The client has been very patient with me; I’ve paused billing until I resolve this. If I’m uncertain about anything, I prefer not to rush while charging others.
I received a message earlier saying:
"BSOD overnight (left my computer on); hasn’t happened for 2 or 3 days."
This suggests the issue is occurring even when the system is idle.
It appears this problem is fairly common with this CPU type, but there’s no clear, direct solution. The priority is resolving it rather than focusing on a quick fix.
If an RMA becomes necessary, I’m unsure whether it should be for the RAM or the CPU—though NVMe was ruled out after thorough testing.
Thanks in advance for your understanding.
Paul
The person who suggested this was advising the client to move from an old Intel to a new Ryzen without fully reinstalling Windows. They emphasized that no changes should be made to the BIOS when dealing with these problems. The client was told that Windows and all software must be reinstalled due to major hardware differences, and then proceed accordingly.
For diagnostic reasons, I recommend removing the client's drive(s) from the build and using an SSD from your own system as the boot drive. Then install W11 from a brand-new, bootable USB stick. Now, check if the issues continue during this fresh installation.
Client moved the drive to a new machine and was worried about losing data. He wasn't an IT expert, so he feared it might not boot and had tried installing GRUB to fix the bootloader. He was really concerned about data loss.
Luckily, I managed to rebuild the boot sector and confirmed there was no data loss.
I often swap drives, and even with major hardware changes, it usually works out. It’s simpler and more convenient than a full reinstall, since apps don’t need to be reinstalled. This is the first time in about 16 years I’ve faced something like this.
As a freelancer working remotely, I have to explain things to clients in NZ who are based in the USA. They’re patient and open to more detailed IT support as long as I guide them through it.
I recommended a full reinstall, and I’ll walk them through every step. I’ll keep you updated.