F5F Stay Refreshed Hardware Desktop 4 DIMM + XMP causing system crash error

4 DIMM + XMP causing system crash error

4 DIMM + XMP causing system crash error

M
MaskeddPig
Member
Find
179
04-22-2019, 05:18 AM
#1
Hello! The relevant details are: i9-9900k @4.8GHz, RTX 2060 and GTX 970, OS on M.2, 860W 80+ Platinum power supply. Recently, I added more than two DIMMs for the first time in my private system. Previously, I had 16GB of 3200MHz CL16 Vengeance LPX modules (two 8GB units) running at full speed with XMP settings. I kept using the same DIMM configuration. After installation, they were recognized and sent to BIOS. When trying to boot the OS, I received an error saying "Previous overclock settings failed." I restarted the PC and returned to the recovery screen repeatedly. My focus was on the CPU, so I switched off the overclock features to auto mode. After a short wait, the system started normally, but within minutes I encountered a BSOD. I tried launching the OS again twice, each time getting a different error. Then I disabled all overclock settings except CPU and XMP, which resolved the issue. Finally, turning on the CPU overclock worked. This suggests something unusual is happening with the new DIMMs or their configuration. Should I adjust BIOS settings to support 4 modules in XMP, or should I request a refund? Thank you for your assistance!
Reply
Reply
M
MaskeddPig
04-22-2019, 05:18 AM #1

Hello! The relevant details are: i9-9900k @4.8GHz, RTX 2060 and GTX 970, OS on M.2, 860W 80+ Platinum power supply. Recently, I added more than two DIMMs for the first time in my private system. Previously, I had 16GB of 3200MHz CL16 Vengeance LPX modules (two 8GB units) running at full speed with XMP settings. I kept using the same DIMM configuration. After installation, they were recognized and sent to BIOS. When trying to boot the OS, I received an error saying "Previous overclock settings failed." I restarted the PC and returned to the recovery screen repeatedly. My focus was on the CPU, so I switched off the overclock features to auto mode. After a short wait, the system started normally, but within minutes I encountered a BSOD. I tried launching the OS again twice, each time getting a different error. Then I disabled all overclock settings except CPU and XMP, which resolved the issue. Finally, turning on the CPU overclock worked. This suggests something unusual is happening with the new DIMMs or their configuration. Should I adjust BIOS settings to support 4 modules in XMP, or should I request a refund? Thank you for your assistance!

Reply
Reply
P
PMX305
Member
Find
183
04-22-2019, 05:53 AM
#2
Operating with four DIMMs places extra strain on the memory controller, which may prevent running all four at 3200 MHz. Consider applying XMP settings and disabling other overclocking options first.
Reply
Reply
P
PMX305
04-22-2019, 05:53 AM #2

Operating with four DIMMs places extra strain on the memory controller, which may prevent running all four at 3200 MHz. Consider applying XMP settings and disabling other overclocking options first.

Reply
Reply
Z
zmanrules987
Member
Find
218
04-22-2019, 08:07 AM
#3
I attempted to boot with full system and only XMP active; it started but then crashed into a BSOD on the desktop.
Reply
Reply
Z
zmanrules987
04-22-2019, 08:07 AM #3

I attempted to boot with full system and only XMP active; it started but then crashed into a BSOD on the desktop.

Reply
Reply
W
WeedMan99
Junior Member
Find
48
05-01-2019, 02:11 AM
#4
9900k is compatible with 2666, but using it at 3200 is an overclock. Consider setting it to 2666 across four slots.
Reply
Reply
W
WeedMan99
05-01-2019, 02:11 AM #4

9900k is compatible with 2666, but using it at 3200 is an overclock. Consider setting it to 2666 across four slots.

Reply
Reply
M
MikeDragon159
Senior Member
Find
661
05-01-2019, 04:43 AM
#5
Hello everyone, I shared the problem on Reddit and received assistance that helped find a reliable fix. Here’s the discussion. Thanks for your time and support!
Reply
Reply
M
MikeDragon159
05-01-2019, 04:43 AM #5

Hello everyone, I shared the problem on Reddit and received assistance that helped find a reliable fix. Here’s the discussion. Thanks for your time and support!

Reply
Reply