F5F Stay Refreshed Hardware Desktop The system that functioned properly for years now fails to boot when RAM is configured at XMP speeds.

The system that functioned properly for years now fails to boot when RAM is configured at XMP speeds.

The system that functioned properly for years now fails to boot when RAM is configured at XMP speeds.

Pages (2): 1 2 Next
D
Dreeezzyyweed
Junior Member
29
02-13-2021, 03:43 AM
#1
My setup looks like this:
CPU: 11700K
Motherboard: Gigabyte Z490 Aorus Pro AX
RAM: G.Skill Ripjaws V 64 GB (F4-3600C18D-64GVK)
I’ve been assembling this system since early 2021. Budget limits have kept me from completing it fully, but it’s been working in a usable way for some time now.
Recently, after months of stable operation, I attempted to add more components—rewiring drives, installing a sound card, reinstalling a RAID card that had been disconnected but was originally present. I also updated the BIOS.
Eventually, I began encountering BIOS warnings about a boot error, preventing me from continuing without either entering the BIOS or resetting it.
I tested my connections, removed the sound card, and ran various checks, eventually narrowing the issue to the RAM. It fails the JEDEC standard of 2666.
Sometimes it boots normally with XMP enabled, but most of the time it doesn’t. When it does, it can run for months without issues, yet every restart risks a boot error or complete failure.
I adjusted the CAS latency from 18 to 19, changed voltage manually from 1.35 to 1.4 in steps of 0.01, but nothing helped. I also tried changing the memory speed manually—anything above 2666, even at 2700, won’t boot.
This strict requirement for the RAM speed at 2666 is puzzling. It can sometimes boot fine at 3600 and remain stable for months, despite all the stability tests I perform. This makes me suspect the motherboard might be the problem rather than the RAM. It’s strange it can work at 3600 but fail above 2666. I’m really hoping it’s not the motherboard, as rebuilding it would be a huge hassle and I doubt I can find another board at a fair price.
Anyone have insights on what might be going wrong? Or suggestions on how to proceed? I’m desperate to get the RAM back to XMP performance again—it worked well until recently.
D
Dreeezzyyweed
02-13-2021, 03:43 AM #1

My setup looks like this:
CPU: 11700K
Motherboard: Gigabyte Z490 Aorus Pro AX
RAM: G.Skill Ripjaws V 64 GB (F4-3600C18D-64GVK)
I’ve been assembling this system since early 2021. Budget limits have kept me from completing it fully, but it’s been working in a usable way for some time now.
Recently, after months of stable operation, I attempted to add more components—rewiring drives, installing a sound card, reinstalling a RAID card that had been disconnected but was originally present. I also updated the BIOS.
Eventually, I began encountering BIOS warnings about a boot error, preventing me from continuing without either entering the BIOS or resetting it.
I tested my connections, removed the sound card, and ran various checks, eventually narrowing the issue to the RAM. It fails the JEDEC standard of 2666.
Sometimes it boots normally with XMP enabled, but most of the time it doesn’t. When it does, it can run for months without issues, yet every restart risks a boot error or complete failure.
I adjusted the CAS latency from 18 to 19, changed voltage manually from 1.35 to 1.4 in steps of 0.01, but nothing helped. I also tried changing the memory speed manually—anything above 2666, even at 2700, won’t boot.
This strict requirement for the RAM speed at 2666 is puzzling. It can sometimes boot fine at 3600 and remain stable for months, despite all the stability tests I perform. This makes me suspect the motherboard might be the problem rather than the RAM. It’s strange it can work at 3600 but fail above 2666. I’m really hoping it’s not the motherboard, as rebuilding it would be a huge hassle and I doubt I can find another board at a fair price.
Anyone have insights on what might be going wrong? Or suggestions on how to proceed? I’m desperate to get the RAM back to XMP performance again—it worked well until recently.

L
lzwarrior
Member
52
02-13-2021, 11:46 AM
#2
You may consider swapping out the CMOS battery to test its impact.
It's possible your motherboard is the source of the problem. Try removing your processor and ram kit, installing them on a different board with the newest BIOS, and check if the same issues persist. If they do, switch to another ram kit paired with the processor to determine if the issue lies in the integrated memory controller.
I also updated the BIOS.
L
lzwarrior
02-13-2021, 11:46 AM #2

You may consider swapping out the CMOS battery to test its impact.
It's possible your motherboard is the source of the problem. Try removing your processor and ram kit, installing them on a different board with the newest BIOS, and check if the same issues persist. If they do, switch to another ram kit paired with the processor to determine if the issue lies in the integrated memory controller.
I also updated the BIOS.

A
AndyGamerFTW
Junior Member
17
02-13-2021, 03:45 PM
#3
I don't have another motherboard to fit the CPU in, and the only other DDR4 desktop I own is likely only compatible with EEC Memory, even if it doesn't support speeds higher than 2133. I was running BIOS version F20 since early 2021, and after updating to F23, I tried flashback to revert to F20 because I believed that was the issue. However, the same boot errors appeared on F20 as well, so I'm now back on F23.
A
AndyGamerFTW
02-13-2021, 03:45 PM #3

I don't have another motherboard to fit the CPU in, and the only other DDR4 desktop I own is likely only compatible with EEC Memory, even if it doesn't support speeds higher than 2133. I was running BIOS version F20 since early 2021, and after updating to F23, I tried flashback to revert to F20 because I believed that was the issue. However, the same boot errors appeared on F20 as well, so I'm now back on F23.

L
lilycotterill
Senior Member
656
02-13-2021, 05:03 PM
#4
Maybe the XMP adjustment increased the voltages slightly too much.
L
lilycotterill
02-13-2021, 05:03 PM #4

Maybe the XMP adjustment increased the voltages slightly too much.

F
FladaHD
Member
222
02-15-2021, 05:15 PM
#5
You haven't tried without the raid card yet? That's something you added too.
F
FladaHD
02-15-2021, 05:15 PM #5

You haven't tried without the raid card yet? That's something you added too.

S
srope
Member
147
02-17-2021, 02:13 AM
#6
It seems unrelated to RAM at all.
The drive on the OS is more likely the issue.
Please share a photo of the error, you're experiencing?
(Upload to imgur.com and post the link)
Also, display a screenshot from Disk Management.
S
srope
02-17-2021, 02:13 AM #6

It seems unrelated to RAM at all.
The drive on the OS is more likely the issue.
Please share a photo of the error, you're experiencing?
(Upload to imgur.com and post the link)
Also, display a screenshot from Disk Management.

_
_HawkyShark_
Member
59
02-17-2021, 03:44 PM
#7
It was recently added and previously functioning correctly. The only change was the inclusion of a sound card, which I attempted to remove without success. I suspect the issue isn't related to the OS drive, as the motherboard is already complaining before attempting to boot. It even resists pressing F12, forcing the boot menu to appear when that error occurs. I’m uncertain about capturing a screenshot, so here’s the image:
https://imgur.com/BemjuXn
View: https://i.imgur.com/BemjuXn.jpg
The storage devices appear disorganized due to the temporary configuration, but I tried to keep the files as clear as possible. Usually, I have two other USB drives connected that aren’t used for booting:
https://imgur.com/PkhTG1h
View: https://i.imgur.com/PkhTG1h.png
_
_HawkyShark_
02-17-2021, 03:44 PM #7

It was recently added and previously functioning correctly. The only change was the inclusion of a sound card, which I attempted to remove without success. I suspect the issue isn't related to the OS drive, as the motherboard is already complaining before attempting to boot. It even resists pressing F12, forcing the boot menu to appear when that error occurs. I’m uncertain about capturing a screenshot, so here’s the image:
https://imgur.com/BemjuXn
View: https://i.imgur.com/BemjuXn.jpg
The storage devices appear disorganized due to the temporary configuration, but I tried to keep the files as clear as possible. Usually, I have two other USB drives connected that aren’t used for booting:
https://imgur.com/PkhTG1h
View: https://i.imgur.com/PkhTG1h.png

M
Mega_Man_7
Member
77
02-17-2021, 10:36 PM
#8
you referred to updating bios, it's possible the current version doesn't support your RAM, you might want to revert to an earlier bios release to eliminate hardware issues
M
Mega_Man_7
02-17-2021, 10:36 PM #8

you referred to updating bios, it's possible the current version doesn't support your RAM, you might want to revert to an earlier bios release to eliminate hardware issues

K
kaaskotskikker
Posting Freak
795
02-18-2021, 06:23 PM
#9
I attempted it, but the identical issue resurfaced in the previous BIOS which had functioned properly for two years prior.
K
kaaskotskikker
02-18-2021, 06:23 PM #9

I attempted it, but the identical issue resurfaced in the previous BIOS which had functioned properly for two years prior.

I
Ic3Cr3amTV
Junior Member
36
02-25-2021, 12:26 PM
#10
Your storage setup doesn't align with the pcpartpicker list. What is the model name of the 120GB OS drive? Also, there seems to be an unusual situation with the OS drive. The active "System Reserved" partition should appear as "System", yet you have an OS partition labeled "System". Have you possibly altered the screenshot? Or did you activate the "System Reserved" partition after turning on your PC? It would be best to recreate the bootloader. Run from an elevated command prompt—regular prompts may fail at the final step. If you encounter any issues, stop immediately and provide a screenshot.
I
Ic3Cr3amTV
02-25-2021, 12:26 PM #10

Your storage setup doesn't align with the pcpartpicker list. What is the model name of the 120GB OS drive? Also, there seems to be an unusual situation with the OS drive. The active "System Reserved" partition should appear as "System", yet you have an OS partition labeled "System". Have you possibly altered the screenshot? Or did you activate the "System Reserved" partition after turning on your PC? It would be best to recreate the bootloader. Run from an elevated command prompt—regular prompts may fail at the final step. If you encounter any issues, stop immediately and provide a screenshot.

Pages (2): 1 2 Next