F5F Stay Refreshed Hardware Desktop Activating XMP profile causes a blue screen error.

Activating XMP profile causes a blue screen error.

Activating XMP profile causes a blue screen error.

F
Falcon_Pilot
Member
62
04-21-2019, 05:16 PM
#1
Hello, your friend’s 14-year-old son reached out for guidance on assembling his first gaming PC. Although I’m not an expert in this area, I’ve assembled six gaming rigs in the past seven months and haven’t faced this issue before, so I’m open to suggestions. I installed all the components listed, powered it up, and everything worked initially. After booting into BIOS, I enabled Auto XMP for the 3200 MHz RAM, saved the settings, and exited. Once logged in, the system would display a blue screen every time. After trying several times, I reverted to disabling XMP, and it functioned properly without any errors. I’m puzzled by this behavior, especially since he recently built a very similar setup using the same motherboard, RAM, PSU, and GPU components—except for the CPU (Ryzen 5 3400G) versus a 3600+ GPU combo. All parts are new. He was told to leave XMP disabled, as it might confuse him since it’s his first PC. I explained the potential risks of leaving it unoptimized, unlike the other rigs he built for friends and family recently. Any advice would be greatly appreciated!
F
Falcon_Pilot
04-21-2019, 05:16 PM #1

Hello, your friend’s 14-year-old son reached out for guidance on assembling his first gaming PC. Although I’m not an expert in this area, I’ve assembled six gaming rigs in the past seven months and haven’t faced this issue before, so I’m open to suggestions. I installed all the components listed, powered it up, and everything worked initially. After booting into BIOS, I enabled Auto XMP for the 3200 MHz RAM, saved the settings, and exited. Once logged in, the system would display a blue screen every time. After trying several times, I reverted to disabling XMP, and it functioned properly without any errors. I’m puzzled by this behavior, especially since he recently built a very similar setup using the same motherboard, RAM, PSU, and GPU components—except for the CPU (Ryzen 5 3400G) versus a 3600+ GPU combo. All parts are new. He was told to leave XMP disabled, as it might confuse him since it’s his first PC. I explained the potential risks of leaving it unoptimized, unlike the other rigs he built for friends and family recently. Any advice would be greatly appreciated!

K
kenjaca
Member
122
04-27-2019, 04:15 PM
#2
Choose a reduced frequency such as 2933MHz when XMP is activated
K
kenjaca
04-27-2019, 04:15 PM #2

Choose a reduced frequency such as 2933MHz when XMP is activated

S
sfajar
Member
183
04-27-2019, 04:39 PM
#3
I thought this could be the best choice, but I wasn’t sure why it functioned well on two other builds with identical components.
S
sfajar
04-27-2019, 04:39 PM #3

I thought this could be the best choice, but I wasn’t sure why it functioned well on two other builds with identical components.

E
elorable
Member
72
04-27-2019, 05:55 PM
#4
This specific CPU might have less memory capacity compared to others.
E
elorable
04-27-2019, 05:55 PM #4

This specific CPU might have less memory capacity compared to others.

T
TheDoubleStack
Junior Member
4
05-04-2019, 01:37 PM
#5
Place RAM in slots 2 and 4, configure the SOC to 1.1 and DRAM to 1.35. Consider trying 3200 if booting is successful. Run memtest86 and OCCT to ensure stability. Good luck!
T
TheDoubleStack
05-04-2019, 01:37 PM #5

Place RAM in slots 2 and 4, configure the SOC to 1.1 and DRAM to 1.35. Consider trying 3200 if booting is successful. Run memtest86 and OCCT to ensure stability. Good luck!

R
Rumbelz
Junior Member
11
05-06-2019, 10:22 AM
#6
The memory controller doesn't handle 3200MHz. It only goes up to 2933MHz, which is below the board's spec. This might be why you're getting a crash—likely because your system is too low-end for that speed. The odd-number latency could be related to the timing settings.
R
Rumbelz
05-06-2019, 10:22 AM #6

The memory controller doesn't handle 3200MHz. It only goes up to 2933MHz, which is below the board's spec. This might be why you're getting a crash—likely because your system is too low-end for that speed. The odd-number latency could be related to the timing settings.