F5F Stay Refreshed Hardware Desktop Error triggered by XMP settings on a new motherboard

Error triggered by XMP settings on a new motherboard

Error triggered by XMP settings on a new motherboard

C
CaptainRex
Junior Member
6
12-04-2021, 03:32 AM
#1
Information about the build:
Motherboard model: MSI MAG B550 Tomahawk
CPU: Ryzen 5600x
RAM: Corsair Vengeance RGB Pro (32GB, 2x16GB) DDR4 3600
GPU: XFX Merc319 Radeon 6900XT
Power supply: Corsair RM850x
Storage: Samsung 970 Evo 1TB M.2
HDD: Western Digital Blue 1TB

Background: I’ve been eager to upgrade and replace parts, but it seems the process has its downsides. In the past six months, I swapped nearly every component from a pre-built unit I originally owned. The only unchanged items are the CPU and the hard drive. About two months ago, I completely rebuilt everything, swapping the GPU from an RTX 3060 to my 6900XT. After uninstalling and updating drivers, I also refreshed the BIOS—everything functioned properly.

Now, after two months, I decided to replace the motherboard (Gigabyte B550 UD AC), which was originally intended for pre-built systems. I installed the B550 Tomahawk and initially everything seemed normal. After reinstalling GPU drivers, updating chipset and BIOS, I encountered several problems:

- BSOD errors appeared
- Screen split into four sections with a distorted appearance
- Chrome would crash unexpectedly during sessions
- Page reloads were necessary
- Fortnite would crash after just 30 seconds of play
- Screen saver caused repeated crashes and restarts
- BIOS XMP profile disabled triggered more issues

I tried reinstalling Windows, removing all drivers, booting in safe mode, repairing the C: drive (now M.2 SSD), and adjusting CPU boost settings. Eventually, I turned off CPU overclocking in BIOS. Once that was done, Fortnite downloads and gameplay ran smoothly.

Later, when changing my background (screen saver), the BSOD recurrence began again—every five minutes after logging in. In BIOS, I disabled XMP profile after reading about it online.

Previously, with identical RAM, I always used XMP at the same speed and timings as the new setup. Both boards support 3600 MHz, so confusion remains. My main concern is why XMP seems to be responsible for the crashes on this new board, despite working perfectly before.

I’m hoping this helps clarify the situation!
C
CaptainRex
12-04-2021, 03:32 AM #1

Information about the build:
Motherboard model: MSI MAG B550 Tomahawk
CPU: Ryzen 5600x
RAM: Corsair Vengeance RGB Pro (32GB, 2x16GB) DDR4 3600
GPU: XFX Merc319 Radeon 6900XT
Power supply: Corsair RM850x
Storage: Samsung 970 Evo 1TB M.2
HDD: Western Digital Blue 1TB

Background: I’ve been eager to upgrade and replace parts, but it seems the process has its downsides. In the past six months, I swapped nearly every component from a pre-built unit I originally owned. The only unchanged items are the CPU and the hard drive. About two months ago, I completely rebuilt everything, swapping the GPU from an RTX 3060 to my 6900XT. After uninstalling and updating drivers, I also refreshed the BIOS—everything functioned properly.

Now, after two months, I decided to replace the motherboard (Gigabyte B550 UD AC), which was originally intended for pre-built systems. I installed the B550 Tomahawk and initially everything seemed normal. After reinstalling GPU drivers, updating chipset and BIOS, I encountered several problems:

- BSOD errors appeared
- Screen split into four sections with a distorted appearance
- Chrome would crash unexpectedly during sessions
- Page reloads were necessary
- Fortnite would crash after just 30 seconds of play
- Screen saver caused repeated crashes and restarts
- BIOS XMP profile disabled triggered more issues

I tried reinstalling Windows, removing all drivers, booting in safe mode, repairing the C: drive (now M.2 SSD), and adjusting CPU boost settings. Eventually, I turned off CPU overclocking in BIOS. Once that was done, Fortnite downloads and gameplay ran smoothly.

Later, when changing my background (screen saver), the BSOD recurrence began again—every five minutes after logging in. In BIOS, I disabled XMP profile after reading about it online.

Previously, with identical RAM, I always used XMP at the same speed and timings as the new setup. Both boards support 3600 MHz, so confusion remains. My main concern is why XMP seems to be responsible for the crashes on this new board, despite working perfectly before.

I’m hoping this helps clarify the situation!

E
emstay26
Senior Member
441
12-04-2021, 12:28 PM
#2
Every vendor's memory setup varies by board, with unique BIOS settings and configurations. Some include the specific XMP profile for your RAM model in their QVL, while others may lack it, leading to reduced performance. It’s best to avoid unnecessary spending on upgrades that don’t add value. If something functions, let go of the urge to upgrade; simply reconfigure XMP, test a 3200 MHz frequency, and check stability. Then adjust the DRAM voltage for XMP—try 1.2V, 1.3V or 1.35V—to see what works best.
E
emstay26
12-04-2021, 12:28 PM #2

Every vendor's memory setup varies by board, with unique BIOS settings and configurations. Some include the specific XMP profile for your RAM model in their QVL, while others may lack it, leading to reduced performance. It’s best to avoid unnecessary spending on upgrades that don’t add value. If something functions, let go of the urge to upgrade; simply reconfigure XMP, test a 3200 MHz frequency, and check stability. Then adjust the DRAM voltage for XMP—try 1.2V, 1.3V or 1.35V—to see what works best.

B
Bogokasa
Junior Member
17
12-04-2021, 02:22 PM
#3
You'll have to adjust RAM voltage, SOC voltage, and memory timings to get it to function properly. Even after booting, instability can lead to crashes, file damage, and may ruin your Windows setup. It's important to invest time in testing for reliability so you don't experience frequent failures.
B
Bogokasa
12-04-2021, 02:22 PM #3

You'll have to adjust RAM voltage, SOC voltage, and memory timings to get it to function properly. Even after booting, instability can lead to crashes, file damage, and may ruin your Windows setup. It's important to invest time in testing for reliability so you don't experience frequent failures.

P
PedroO_
Senior Member
522
12-08-2021, 06:57 AM
#4
In my defense, I battled the lizard brain for a couple of months before giving up, lol. Appreciate the help! I set XMP to 3200 MHz and everything seems fine so far. Voltage around 1.3, so I'm just letting it run and observe. Thanks again!
P
PedroO_
12-08-2021, 06:57 AM #4

In my defense, I battled the lizard brain for a couple of months before giving up, lol. Appreciate the help! I set XMP to 3200 MHz and everything seems fine so far. Voltage around 1.3, so I'm just letting it run and observe. Thanks again!

C
Camiloute
Member
52
12-13-2021, 06:53 PM
#5
It makes sense that RAM can be unstable. Thanks for the response—I'll keep exploring and testing it out.
C
Camiloute
12-13-2021, 06:53 PM #5

It makes sense that RAM can be unstable. Thanks for the response—I'll keep exploring and testing it out.

S
Star_Lars
Member
175
12-19-2021, 04:44 PM
#6
Ensure you understand safe voltage levels; excessive voltage may cause lasting harm.
S
Star_Lars
12-19-2021, 04:44 PM #6

Ensure you understand safe voltage levels; excessive voltage may cause lasting harm.

B
Ballenknijper
Member
80
12-19-2021, 07:00 PM
#7
Confirmed settings at 3200. If it doesn’t work, record the XMP profile details and test manually. Occasionally, typing the same values can resolve issues for many users.
B
Ballenknijper
12-19-2021, 07:00 PM #7

Confirmed settings at 3200. If it doesn’t work, record the XMP profile details and test manually. Occasionally, typing the same values can resolve issues for many users.

S
superbolt30
Junior Member
10
12-19-2021, 08:08 PM
#8
I tried adjusting it to 3600 again and it crashed once more. 3200 appears to work without issues so far!
S
superbolt30
12-19-2021, 08:08 PM #8

I tried adjusting it to 3600 again and it crashed once more. 3200 appears to work without issues so far!

Q
Queffect
Member
219
12-20-2021, 02:21 AM
#9
Based on the specifications and conditions, you should achieve more performance than expected. I successfully ran 3400 on my 2700X, likely due to favorable circumstances. My RAM is set to 1.4 volts for C18 timings with a safe 1.125V SOC level. The system is designed for 3600 C19 at 1.35V, but this is currently the best it will run until I upgrade to a 3800X. Performance remains limited compared to Ryzen options, though I managed decent results with compatible memory.
Q
Queffect
12-20-2021, 02:21 AM #9

Based on the specifications and conditions, you should achieve more performance than expected. I successfully ran 3400 on my 2700X, likely due to favorable circumstances. My RAM is set to 1.4 volts for C18 timings with a safe 1.125V SOC level. The system is designed for 3600 C19 at 1.35V, but this is currently the best it will run until I upgrade to a 3800X. Performance remains limited compared to Ryzen options, though I managed decent results with compatible memory.