4x sticks of DDR4 all bad at once?

[Spork3245]

Hi, everyone, google brought me here after finding this thread of a similar issue: https://www.techpowerup.com/forums/...ddenly-have-errors-bsod-startup.315391/page-2

Seeing that thread was both recent and active with educated replies I wanted to post my situation: I debated on posting in that thread but thought maybe it’d be best to make my own. Apologies in advance for the length of this post btw!

SPECS:
CPU: AMD Ryzen 5900x
Mobo: ASUS ROG Crosshair VIII Dark Hero x570
RAM: 4x Corsair Vengeance RGB PRO 8GB (32gb total) DDR4 3000MHz C15
Video Card: MSI RTX 4090
PSU: EVGA 1300w G2
Various fans, AIO, multiple HDD + SSD + 2x m.2 drives.

A few months ago (early August) I started having an issue where after rebooting my PC Windows wouldn’t load, it would just hang at the spinning dots prior to Windows actually loading and do the same thing with the “repair” start up after a failed boot. The dots would either spin infinitely (I once left it on overnight to see if it would eventually boot: woke up to it still spinning) or the dots would freeze after a few seconds.
I tried reinstalling Windows, however the same issue would occur when booting the Windows installer from USB. I also tried (in no particular order)… disconnecting all HDD/SSD + removing non-boot m.2s as well as changing the port used for my boot m.2, disconnecting all USB devices except my keyboard (also trying a different USB for the keyboard), taking out all 4 RAM sticks and trying them 1 at a time, resetting CMOS, removing the motherboards battery to reset CMOS, and probably 5 other things I don’t remember. There were no Q Code errors.
I had the idea to flash the BIOS and lo-and-behold the system booted! After a few reboots the problem reoccurred but reflashing the BIOS (to the same version already installed) would fix the issue and I’d be able to get into Windows each time (simply resetting CMOS would not work, only a BIOS flash would). Windows would be completely stable once in, gaming and everything else was also fine. All voltages good, temperatures great, etc.

I thought “must be a motherboard issue” so I checked my mobo warranty to see if it is still covered, called ASUS, got an RMA. Installed the new mobo, problem seemed to have mostly gone away: could reboot the system without needing to flash the BIOS each time, once in a while Windows would lock on boot like before but after a manual restart it would load fine (no need to flash the BIOS or troubleshoot). I replaced the motherboard with the RMA in mid-September.

Flash forward to 2 weeks ago, problem began again; did the BIOS flash trick from before and it worked. Yesterday my PC needed to reboot after an app update (I should mention I rarely turn off or reboot my PC outside of software/OS updates and/or issues arising ) but flashing the BIOS didn’t work this time (I tried multiple times). On one of the reboot attempts I received no video signal for POST and had a Q Code (I can’t remember but I want to say “0d” which (regardless of if it was actually 0d or not) when I googled indicated a memory training or initializing issue), even after getting a video signal again by reseating the RAM I eventually received another Q Code that indicated RAM as well as a blue screen during a Windows boot attempt that stated “Driver_PNP_WatchDog” stop code. This time, I remembered that I had an old pair of 2400mhz Geil Ripjaw DDR4 from an old X99 build in storage. Plugged it in, system booted right up. “Okay”, I thought, “one of the Corsair sticks must be bad”, so I took the Geil out and put two of the Corsair in DIMMs 2 and 4, system booted properly, put the remaining two back into 1 and 3, previous boot issue occurred, removed 2 and 4 to confirm and still had the boot issue. I proceeded to remove the two Corsair RAM sticks still in the system and replace it with the two Corsair sticks that booted, still using DIMMs 1 and 3 to confirm that it’s not a DIMM issue… no boot. “Oh… a bad DIMM?” so I moved those two sticks back to 2 & 4… no boot again. “Did I somehow mix up the Corsair sticks?” switched to my other two, still DIMMs 2 & 4, no boot… Back to the Geil, booted no problem. Restarted the computer from Windows 3+ times with no issue with the Geil installed.

I went ahead and ordered 2x 32gb DDR4 3600mhz C18 RAM to replace these 4x Corsair sticks as I’m wondering if running 4x sticks with such low latency (C15) caused the IMC to burn out the sticks overtime. However, I’ve had this RAM since August 2019 with no issues running all 4 in an X99 mobo for quad channel before upgrading to and moving all 4 sticks to the current X570 AM4 build approximately a year later in August of 2020. There’s been no issues until a few months ago. RAM was always run with its XMP/DOCP profile active in BIOS.

I’d love some thoughts on this as 4x sticks of DDR4 that have been fine for roughly 4 years suddenly going bad seems, at best, highly improbable.

 

[VuurVOS]

Hi, everyone, google brought me here after finding this thread of a similar issue: https://www.techpowerup.com/forums/...ddenly-have-errors-bsod-startup.315391/page-2

Seeing that thread was both recent and active with educated replies I wanted to post my situation: I debated on posting in that thread but thought maybe it’d be best to make my own. Apologies in advance for the length of this post btw!

SPECS:
CPU: AMD Ryzen 5900x
Mobo: ASUS ROG Crosshair VIII Dark Hero x570
RAM: 4x Corsair Vengeance RGB PRO 8GB (32gb total) DDR4 3000MHz C15
Video Card: MSI RTX 4090
PSU: EVGA 1300w G2
Various fans, AIO, multiple HDD + SSD + 2x m.2 drives.

A few months ago (early August) I started having an issue where after rebooting my PC Windows wouldn’t load, it would just hang at the spinning dots prior to Windows actually loading and do the same thing with the “repair” start up after a failed boot. The dots would either spin infinitely (I once left it on overnight to see if it would eventually boot: woke up to it still spinning) or the dots would freeze after a few seconds.
I tried reinstalling Windows, however the same issue would occur when booting the Windows installer from USB. I also tried (in no particular order)… disconnecting all HDD/SSD + removing non-boot m.2s as well as changing the port used for my boot m.2, disconnecting all USB devices except my keyboard (also trying a different USB for the keyboard), taking out all 4 RAM sticks and trying them 1 at a time, resetting CMOS, removing the motherboards battery to reset CMOS, and probably 5 other things I don’t remember. There were no Q Code errors.
I had the idea to flash the BIOS and lo-and-behold the system booted! After a few reboots the problem reoccurred but reflashing the BIOS (to the same version already installed) would fix the issue and I’d be able to get into Windows each time (simply resetting CMOS would not work, only a BIOS flash would). Windows would be completely stable once in, gaming and everything else was also fine. All voltages good, temperatures great, etc.

I thought “must be a motherboard issue” so I checked my mobo warranty to see if it is still covered, called ASUS, got an RMA. Installed the new mobo, problem seemed to have mostly gone away: could reboot the system without needing to flash the BIOS each time, once in a while Windows would lock on boot like before but after a manual restart it would load fine (no need to flash the BIOS or troubleshoot). I replaced the motherboard with the RMA in mid-September.

Flash forward to 2 weeks ago, problem began again; did the BIOS flash trick from before and it worked. Yesterday my PC needed to reboot after an app update (I should mention I rarely turn off or reboot my PC outside of software/OS updates and/or issues arising ) but flashing the BIOS didn’t work this time (I tried multiple times). On one of the reboot attempts I received no video signal for POST and had a Q Code (I can’t remember but I want to say “0d” which (regardless of if it was actually 0d or not) when I googled indicated a memory training or initializing issue), even after getting a video signal again by reseating the RAM I eventually received another Q Code that indicated RAM as well as a blue screen during a Windows boot attempt that stated “Driver_PNP_WatchDog” stop code. This time, I remembered that I had an old pair of 2400mhz Geil Ripjaw DDR4 from an old X99 build in storage. Plugged it in, system booted right up. “Okay”, I thought, “one of the Corsair sticks must be bad”, so I took the Geil out and put two of the Corsair in DIMMs 2 and 4, system booted properly, put the remaining two back into 1 and 3, previous boot issue occurred, removed 2 and 4 to confirm and still had the boot issue. I proceeded to remove the two Corsair RAM sticks still in the system and replace it with the two Corsair sticks that booted, still using DIMMs 1 and 3 to confirm that it’s not a DIMM issue… no boot. “Oh… a bad DIMM?” so I moved those two sticks back to 2 & 4… no boot again. “Did I somehow mix up the Corsair sticks?” switched to my other two, still DIMMs 2 & 4, no boot… Back to the Geil, booted no problem. Restarted the computer from Windows 3+ times with no issue with the Geil installed.

I went ahead and ordered 2x 32gb DDR4 3600mhz C18 RAM to replace these 4x Corsair sticks as I’m wondering if running 4x sticks with such low latency (C15) caused the IMC to burn out the sticks overtime. However, I’ve had this RAM since August 2019 with no issues running all 4 in an X99 mobo for quad channel before upgrading to and moving all 4 sticks to the current X570 AM4 build approximately a year later in August of 2020. There’s been no issues until a few months ago. RAM was always run with its XMP/DOCP profile active in BIOS.

I’d love some thoughts on this as 4x sticks of DDR4 that have been fine for roughly 4 years suddenly going bad seems, at best, highly improbable.

Could be configuration issue. Can you share the output of ZenTimings when those sticks are installed?

 

[Spork3245]

Could be configuration issue. Can you share the output of ZenTimings when those sticks are installed?

That’s the thing, it has worked without issue for almost 3 years (in the AMD build, and an additional 1+ year in the old Intel build) with the XMP/DOCP profile active. I also forgot to mention that I tried running them at default (auto) settings which put it at 2666mhz and I believe 18-20 CL timings.

Here are the settings that changed with the Geil RAM if it helps (left is what the XMP/DOCP was for the Corsair, right is what was changed for the Geil’s profile):

https://i.postimg.cc/437dBc38/IMG-8387.jpg

For the full timings I’ll check in a couple hours as I’m currently replying between sets at the gym, and I’ll need to put the Corsair RAM back into the mobo when I get home.

Update (this forum keeps automatically combining my new post as an edit into this reply? Not used to this style but whatever lol):

Could be configuration issue. Can you share the output of ZenTimings when those sticks are installed?

Here’s the XMP/DOCP timings from the BIOS:
Corsair: https://i.postimg.cc/hjB03WkJ/IMG-8390.jpg
Corsair: https://i.postimg.cc/FHwp3JGV/IMG-8391.jpg
Geil: https://i.postimg.cc/bNNmhPsk/IMG-8392.jpg

As mentioned in my OP, I cannot get into Windows with any of the Corsair RAM installed (I retried all 4 sticks just now in groups of two - going back to the Geil gave me a problem-free boot), so I cannot use the ZenTimings app to check in Windows.

 

[VuurVOS]

Even with bios defaults timings (2133/2400/2666MHz) with the Corsair modules you are unable to boot into Windows?

Can you confirm there is no corrosion on the pins of the DIMM's? Can you make a picture of the memory?

 

[Ferrum Master]

Why have you imagined primary timings are the the most important factor, especially when booting up? Don't use XMP/DOCP crap. For most of time it is meant for Intel and DOES NOT WORK on AM4.

Seek your motherboard specific timings, there are forums with ZenTimings screenshots. Full settings and voltages. Pay attention to at clock drive strengths and ProcODT, RttNom, RttWr, RttPark values, those are crucial for booting up that crap ASUS, they are not compatible with other boards, only yours. Set very loose timings as start, and then vary those values till you understand the mid range. Only then tighten up timings. Those values differ on each RAM frequency you use. You have to do manual everything if you want your system stable.

 

[Spork3245]

Even with bios defaults timings (2133/2400/2666MHz) with the Corsair modules you are unable to boot into Windows?

Can you confirm there is no corrosion on the pins of the DIMM's? Can you make a picture of the memory?

Correct, default timings cannot boot into Windows

Pictures of modules:

https://i.postimg.cc/RhJ3KGdM/IMG-8393.jpg%0A

https://i.postimg.cc/TP2JgMDf/IMG-8394.jpg%0A

https://i.postimg.cc/fbHjv2cX/IMG-8395.jpg%0A

Why have you imagined primary timings are the the most important factor, especially when booting up? Don't use XMP/DOCP crap. For most of time it is meant for Intel and DOES NOT WORK on AM4.

Seek your motherboard specific timings, there are forums with ZenTimings screenshots. Full settings and voltages. Pay attention to at clock drive strengths and ProcODT, RttNom, RttWr, RttPark values, those are crucial for booting up that crap ASUS, they are not compatible with other boards, only yours. Set very loose timings as start, and then vary those values till you understand the mid range. Only then tighten up timings. Those values differ on each RAM frequency you use. You have to do manual everything if you want your system stable.

Motherboard specific timings? Aren't timings dependent on the RAM modules?
Regardless, the system will not boot even with XMP/DOCP disabled and timings at default settings. It was stable for roughly 3 years on this motherboard prior to this issue.

 

[VuurVOS]

Correct, default timings cannot boot into Windows

Pictures of modules:

https://i.postimg.cc/RhJ3KGdM/IMG-8393.jpg%0A

https://i.postimg.cc/TP2JgMDf/IMG-8394.jpg%0A

https://i.postimg.cc/fbHjv2cX/IMG-8395.jpg%0A

Motherboard specific timings? Aren't timings dependent on the RAM modules?
Regardless, the system will not boot even with XMP/DOCP disabled and timings at default settings. It was stable for roughly 3 years on this motherboard prior to this issue.

I noticed the Corsair set isn't quad kit but a dual kit. Can you also show us the labels of the other two modules? There is a chance you have two different version of memory kits.

Can you install the Geil modules in A2&B2 and confirm it is booting? Then add the Corsair modules with version number 5.32 in A1&B1.
I am curious if the system will boot with the lowest SPD timings.

 

[Spork3245]

I noticed the Corsair set isn't quad kit but a dual kit. Can you also show us the labels of the other two modules? There is a chance you have two different version of memory kits.

Can you install the Geil modules in A2&B2 and confirm it is booting? Then add the Corsair modules with version number 5.32 in A1&B1.
I am curious if the system will boot with the lowest SPD timings.

Yes, I purchased two dual kits when I bought this RAM in 2019, but I verified they were the same model numbers when purchasing:
https://i.postimg.cc/rpvVDCgT/IMG-8396.jpg

I tried combining two of the Corsair with the Geil models (in A2 + B2) but still could not get into Windows. I then tried the other two Corsair sticks (swapping for the two Corsair sticks in A1 + B1) and still no luck.

It’s somewhat weird that the PC boots, POSTs, and I’m able to get into the BIOS without issue, but loading Windows is where the issue occurs with the Corsair sticks. It almost makes me question if it’s some sudden weird Windows driver issue with the RGB on the RAM or something?

 

[Ferrum Master]

Motherboard specific timings? Aren't timings dependent on the RAM modules?

In 2000 maybe, but mostly the primary row, secondary is partial. You cannot have settings that exceed IMC capabilities also. You get that RAM can be too fast also even by default. AMD and Intel do differ.

All the bits and specifics moved into secondary, third and tertiary row and those are IMC/Motherboard specific. It has been like that for decades now. The first row is for marketing and get the rough idea, how fast the RAM is. To ensure stability or even boot, that's not writeable into some mojo XMP settings and hoping that enabling that will turn everything good. Considering you had X99 you should have known that thing, that much performance was really hidden in RTL and IOL values on that platform.

The options manufacturers do are overvolting everything using AUTO. Nowadays CPU's have no headroom, you have to be careful or you will fry the CPU... and many OEMs did that. No RAM stick is actually made equal. You should number them and then conduct tests, pick out best pairs, that are less picky to changes. ProcODT actually will show that. Start from lower resistances to upper. You will get range of 3-4 values that boot and they differ with each stick combination in some times. You must arrange so it is the same for both pairs, thus not f*ing the autistic ASUS boot logic(I have also ASUS, so I learned the hard way and have my right to call things what's what). I had also old quad Corsair DDR4 RAM kit... that was unbootable on stock... (reminded of DFI Lanparty times, it booted only on OC, not stock). But in the end I find out timings that were OK, those were completely different from the stock timings. Meanwhile I sold the kit and it lives in MSI Mortar B550, it booted those sticks without problems. Okay, it wasn't PRIME stable, but it picked all the tertiaries right without screwing around, so doing timing fixes was easy. The RAM kit is 6 years old, runs without issues up to day. Checked last week while drinking beer with the guy I sold them.

Silicon does get worse... ESPECIALLY when doing auto... why? Because XPM sometimes enables stupid voltages. Now you have to rise VSOC to at least 1.2V for starters with one module you can boot, then put all 4. Also environmental temperatures change, thus resistance, thus ohms law dictates for changes.

Okay... if you ain't in the mood seeking timings for your exact fellow users that have managed to OC the board... then I cannot help. Here is a link to leaderboards where you can look for similar timing settings, but most of those are not PRIME stable, but you should figure out a pattern at least.

Zen RAM OC Leaderboards

docs.google.com

You understand that failure to boot windows means that the settings are unstable... ? You can corrupt windows and bootloader using unstable RAM tho. But it should stay permanent, no driver is involved running RAM, it is a core kernel function and RAM agnostic, it is just a address table.

 

[Spork3245]

You understand that failure to boot windows means that the settings are unstable... ? You can corrupt windows and bootloader using unstable RAM tho. But it should stay permanent, no driver is involved running RAM, it is a core kernel function and RAM agnostic, it is just a address table.

Yes, I understand that, however, as per my OP, this exact RAM has been running stable for 4 years in two different systems, upon RMAing the motherboard in September it ran fine for roughly two months, also, regardless of the timings of the Corsair RAM the system will not boot with the Corsair sticks in. The old Geil sticks work, however. If the Windows bootloader was corrupted, would the Geil work, and would swapping out the motherboard work for ~2 months? (I'm genuinely asking)

 

[VuurVOS]

Can you make an usb with memtest86 on it?

MemTest86 - Official Site of the x86 Memory Testing Tool

MemTest86 is the original self booting memory testing software for x86 and ARM computers. Supporting both BIOS and UEFI, with options to boot from USB.

www.memtest86.com

Then let memtest86 run to find out if the system is unstable. If memtest doesn't show any errors, there is still a chance the memory is still bad.
Do you have Corsair iCUE or other RGB control software installed?

 

[Spork3245]

Can you make an usb with memtest86 on it?

MemTest86 - Official Site of the x86 Memory Testing Tool

MemTest86 is the original self booting memory testing software for x86 and ARM computers. Supporting both BIOS and UEFI, with options to boot from USB.

www.memtest86.com

Then let memtest86 run to find out if the system is unstable. If memtest doesn't show any errors, there is still a chance the memory is still bad.
Do you have Corsair iCUE or other RGB control software installed?

I have iCue installed, yes. I can try memtest in a bit.

BUT, NEW ISSUE: the new Corsair RAM ( https://a.co/d/5NnZBkW ) I ordered arrived a few minutes ago, installed it and… same issue as the old Corsair RAM. I’m at a total loss on this one. Makes me think this definitely isn’t an issue with the RAM at all.
I think I’m going to try refreshing Windows with the Geil RAM installed then attempt the Corsair again.

 

[VuurVOS]

I have iCue installed, yes. I can try memtest in a bit.

BUT, NEW ISSUE: the new Corsair RAM ( https://a.co/d/5NnZBkW ) I ordered arrived a few minutes ago, installed it and… same issue as the old Corsair RAM. I’m at a total loss on this one. Makes me think this definitely isn’t an issue with the RAM at all.
I think I’m going to try refreshing Windows with the Geil RAM installed then attempt the Corsair again.

Or first uninstall iCue before refreshing?

 

[Ferrum Master]

Could you export BIOS values when booted of Corsair RAM and and post no phone screenshots... export BIOS settings txt file and post it here to quit the guessing games.

 

[Spork3245]

Or first uninstall iCue before refreshing?

I tried both (Windows Refresh where I keep apps and settings, and uninstalling iCue), no luck on either, even with the new RAM.

Could you export BIOS values when booted of Corsair RAM and and post no phone screenshots... export BIOS settings txt file and post it here to quit the guessing games.

I’d love to but I don’t see an option to do this anywhere?

 

[Ferrum Master]

I’d love to but I don’t see an option to do this anywhere?

Click [Tool] - [ASUS User Profile],Then save to USB at the bottom. You need a USB flash drive inserted obviously.

 

[A Computer Guy]

RAM: 4x Corsair Vengeance RGB PRO 8GB (32gb total) DDR4 3000MHz C15

I remember Corsair DDR4 3000 kits being notoriously incompatible running on AM4 platform and bumping up tRC a few points could fix it.
The same with my Corsair RGB DDR4-3200 kit before UEFI/BIOS fixes generally solved the problem somehow.

 

[Ferrum Master]

I remember Corsair DDR4 3000 kits being notoriously incompatible running on AM4 platform and bumping up tRC a few points could fix it.

I remember using values around 600 . Who said Corsairs are fast boats?

 

[thesmokingman]

It's hyper rare for all four sticks to go bad. That said I've seen this exact thing on an Asus x570 Strix-E where over time it started to get unstable. At first I thought it was the cpu, then this or that, the memory. No way it could have been the board right? After swapping this or that, there was nothing left but the board. After more pain in the ass logistics I was able to get a 2nd board to test and sure enough it was the motherboard.

 

[A Computer Guy]

I remember using values around 600 . Who said Corsairs are fast boats?

I was referring to tRC <> tRFC but I think I understood your referring to tRFC.

 

[VuurVOS]

I tried both (Windows Refresh where I keep apps and settings, and uninstalling iCue), no luck on either, even with the new RAM.

I think you need to try to boot into safe mode with Windows. If that works with Corsair memory then there is still an iCUE service on the background screwing things up.

1. Press the Windows key + R to open the Run window.
2. In the text box, type msconfig and press Enter.
3. At the top of the System Configuration window, click the Boot tab.
4. Underneath Boot options, make sure that Safe boot is checked. Then click OK and restart your computer.

Maybe it is wise to cleanup leftover files of iCUE?

How to perform a clean reinstallation of iCUE

If iCUE runs into performance or behavior issues due to corrupted local files, you can perform a clean re-installation to try and resolve the problem. Before uninstalling, make sure to back up any ...

help.corsair.com

 

[Ferrum Master]

I was referring to tRC <> tRFC but I think I understood your referring to tRFC.

Ah yes yes... I didn't screw around with that as it is basically the sum of the first timings, maybe with added +2.

But we need to see the full BIOS setting list, then it would more clear.

 

[A Computer Guy]

I found some old notes of mine a few years ago and I wrote...
"With 4.32 kits it seems to be a thing that tRC needs a bump somewhere between +2 to +8 over stock for some reason"

Since then I hear Corsair got much worse with swapping IC's in their models so the version of the kit may not represent the IC used.

Like Ferrum Master suggested let's get those screenshots and info posted here to better understand the situation.

 

[Spork3245]

Click [Tool] - [ASUS User Profile],Then save to USB at the bottom. You need a USB flash drive inserted obviously.

Got it, it only seems to be saving my profiles as .CMO files, is there a way to change it to a text doc? It did automatically save a "default _setting" txt file on there though, considering leaving things on default gives me no boot with the Corsair RAM as well I've gone ahead and attached it.

I remember Corsair DDR4 3000 kits being notoriously incompatible running on AM4 platform and bumping up tRC a few points could fix it.
The same with my Corsair RGB DDR4-3200 kit before UEFI/BIOS fixes generally solved the problem somehow.

I found some old notes of mine a few years ago and I wrote...
"With 4.32 kits it seems to be a thing that tRC needs a bump somewhere between +2 to +8 over stock for some reason"

Since then I hear Corsair got much worse with swapping IC's in their models so the version of the kit may not represent the IC used.

Like Ferrum Master suggested let's get those screenshots and info posted here to better understand the situation.

I'm running the latest BIOS on my X570 Dark Hero and the RAM was working for quite awhile with no issues up until recently, but I'll give it a shot!

It's hyper rare for all four sticks to go bad. That said I've seen this exact thing on an Asus x570 Strix-E where over time it started to get unstable. At first I thought it was the cpu, then this or that, the memory. No way it could have been the board right? After swapping this or that, there was nothing left but the board. After more pain in the ass logistics I was able to get a 2nd board to test and sure enough it was the motherboard.

Oddly enough, I figured it was the motherboard back when this initially started happening a few months ago, I RMA'd the motherboard to ASUS and this is a new X570 Dark Hero from them.

I think you need to try to boot into safe mode with Windows. If that works with Corsair memory then there is still an iCUE service on the background screwing things up.

1. Press the Windows key + R to open the Run window.
2. In the text box, type msconfig and press Enter.
3. At the top of the System Configuration window, click the Boot tab.
4. Underneath Boot options, make sure that Safe boot is checked. Then click OK and restart your computer.

View attachment 323575

Maybe it is wise to cleanup leftover files of iCUE?

How to perform a clean reinstallation of iCUE

If iCUE runs into performance or behavior issues due to corrupted local files, you can perform a clean re-installation to try and resolve the problem. Before uninstalling, make sure to back up any ...

help.corsair.com

I'll try this now. Thanks!

 

[Ferrum Master]

I'll try this now. Thanks!

You are running everything AUTO... no wonder nothing works, I'll remind you are using ASUS board. Don't do AUTO. Welcome to setting up your first real PC.

There is an example of my BIOS. Pretty set up... and that's how it should be. Now start looking up at the link I gave, it seems ASUS likes RZQ 7/3/1. Look into your full SPD rise the voltages, disable all AUTO ASUS OC bullshit.

[2023/11/30 21:08:27]
Ai Overclock Tuner [Manual]
BCLK Frequency [100.0000]
SB Clock Spread Spectrum [Disabled]
Performance Enhancer [Default]
Memory Frequency [DDR4-3800MHz]
FCLK Frequency [1900MHz]
CPU Core Ratio [Auto]
Core VID [Auto]
CCX0 Ratio [Auto]
CCX0 Ratio [Auto]
TPU [Keep Current Settings]
Performance Bias [None]
PBO Fmax Enhancer [Disabled]
Precision Boost Overdrive [Auto]
Precision Boost Overdrive Scalar [Auto]
Curve Optimizer [Auto]
Max CPU Boost Clock Override [Auto]
Platform Thermal Throttle Limit [Auto]
DRAM CAS# Latency [14]
Trcdrd [16]
Trcdwr [10]
DRAM RAS# PRE Time [14]
DRAM RAS# ACT Time [30]
Trc [44]
TrrdS [4]
TrrdL [4]
Tfaw [18]
TwtrS [4]
TwtrL [12]
Twr [12]
Trcpage [Auto]
TrdrdScl [4]
TwrwrScl [4]
Trfc [244]
Trfc2 [122]
Trfc4 [61]
Tcwl [14]
Trtp [8]
Trdwr [8]
Twrrd [3]
TwrwrSc [1]
TwrwrSd [5]
TwrwrDd [6]
TrdrdSc [1]
TrdrdSd [3]
TrdrdDd [4]
Tcke [1]
ProcODT [32 ohm]
Cmd2T [1T]
Gear Down Mode [Enabled]
Power Down Enable [Disabled]
RttNom [RZQ/7]
RttWr [RZQ/3]
RttPark [RZQ/1]
MemAddrCmdSetup [Auto]
MemCsOdtSetup [Auto]
MemCkeSetup [Auto]
MemCadBusClkDrvStren [24.0 Ohm]
MemCadBusAddrCmdDrvStren [24.0 Ohm]
MemCadBusCsOdtDrvStren [24.0 Ohm]
MemCadBusCkeDrvStren [24.0 Ohm]
Mem Over Clock Fail Count [2]
Voltage Monitor [Die Sense]
VDDCR CPU Load Line Calibration [Auto]
VDDCR CPU Current Capability [120%]
VDDCR CPU Switching Frequency [Auto]
VRM Spread Spectrum [Disabled]
VDDCR CPU Power Duty Control [Extreme]
VDDCR CPU Power Phase Control [Extreme]
VDDCR SOC Load Line Calibration [Auto]
VDDCR SOC Current Capability [120%]
VDDCR SOC Switching Frequency [Auto]
VDDCR SOC Power Phase Control [Extreme]
VDDCR CPU Voltage [Offset mode]
VDDCR CPU Offset Mode Sign [+]
VDDCR CPU Offset Voltage [0.01250]
VDDCR SOC Voltage [Manual]
VDDCR SOC Voltage Override [1.18750]
DRAM Voltage [1.54000]
VDDG CCD Voltage Control [0.998]
VDDG IOD Voltage Control [0.998]
CLDO VDDP Voltage [0.934]
1.0V SB Voltage [1.00000]
1.2V SB Voltage [1.20000]
CPU 1.80V Voltage [1.80500]
VTTDDR Voltage [Auto]
VPP_MEM Voltage [Auto]
VDDP Standby Voltage [Auto]
CPU Core Current Telemetry [Auto]
CPU SOC Current Telemetry [Auto]
Security Device Support [Enable]
SHA-1 PCR Bank [Disabled]
SHA256 PCR Bank [Enabled]
Pending operation [None]
Platform Hierarchy [Enabled]
Storage Hierarchy [Enabled]
Endorsement Hierarchy [Enabled]
TPM 2.0 UEFI Spec Version [TCG_2]
Physical Presence Spec Version [1.3]
Disable Block Sid [Disabled]
Selects TPM device [Enable Firmware TPM]
Erase fTPM NV for factory reset [Disabled]
PSS Support [Enabled]
NX Mode [Enabled]
SVM Mode [Enabled]
SMT Mode [Auto]
Core Leveling Mode [Automatic mode]
CCD Control [Auto]
SATA Port Enable [Enabled]
SATA Mode [AHCI]
NVMe RAID mode [Disabled]
SMART Self Test [Enabled]
Hot Plug [Disabled]
Hot Plug [Disabled]
Hot Plug [Disabled]
Hot Plug [Disabled]
Hot Plug [Disabled]
Hot Plug [Disabled]
Hot Plug [Disabled]
Hot Plug [Disabled]
HD Audio Controller [Disabled]
PCIEX16_1 Mode [GEN 4]
PCIEX16_2 Mode [Auto]
PCIEX16_3 Mode [GEN 3]
PCIEX1_1 Mode [GEN 1]
PCIEX1_2 Mode [GEN 1]
M.2_1 Link Mode [GEN 4]
M.2_2 Link Mode [GEN 4]
SB Link Mode [GEN 4]
CPU PCIE ASPM Mode Control [Auto]
PCIEX16_1 Bandwidth Bifurcation Configuration [Auto Mode]
PCIEX16_2 Bandwidth Bifurcation Configuration [Auto Mode]
PCIEX16_3 4X-2X Switch [4X]
When system is in working state [All On]
Q-Code LED Function [POST Code Only]
When system is in sleep, hibernate or soft off states [All On]
Realtek 2.5G LAN Controller [Enabled]
Intel LAN Controller [Disabled]
Wi-Fi Controller [Enabled]
Bluetooth Controller [Enabled]
USB power delivery in Soft Off state (S5) [Disabled]
ErP Ready [Enable(S4+S5)]
Restore AC Power Loss [Last State]
Power On By PCI-E [Disabled]
Power On By RTC [Disabled]
Above 4G Decoding [Enabled]
Resize BAR Support [Auto]
SR-IOV Support [Enabled]
Legacy USB Support [Enabled]
XHCI Hand-off [Enabled]
USB Device Enable [Enabled]
U32G2_4 [Enabled]
U32G2_1 [Enabled]
U32G2_2 [Enabled]
U32G1_11 [Enabled]
U32G2_C9 [Enabled]
USB3 [Enabled]
USB4 [Enabled]
U32G2_C8 [Enabled]
U32G2_5 [Enabled]
U32G2_6 [Enabled]
USB_1_2 [Enabled]
Network Stack [Disabled]
Device [Samsung SSD 750 EVO 500GB]
CPU Temperature [Monitor]
CPU Package Temperature [Monitor]
MotherBoard Temperature [Monitor]
T_Sensor Temperature [Monitor]
CPU Fan Speed [Monitor]
CPU Optional Fan Speed [Monitor]
Chassis Fan 1 Speed [Monitor]
Chassis Fan 2 Speed [Monitor]
M.2 Fan Speed [Monitor]
W_PUMP+ Speed [Monitor]
AIO PUMP Speed [Monitor]
PCH Fan Speed [Monitor]
CPU Core Voltage [Monitor]
3.3V Voltage [Monitor]
5V Voltage [Monitor]
12V Voltage [Monitor]
CPU Q-Fan Control [PWM Mode]
CPU Fan Step Up [0 sec]
CPU Fan Step Down [0 sec]
CPU Fan Speed Lower Limit [Ignore]
CPU Fan Profile [Manual]
CPU Upper Temperature [78]
CPU Fan Max. Duty Cycle (%) [100]
CPU Middle Temperature [70]
CPU Fan Middle. Duty Cycle (%) [35]
CPU Lower Temperature [50]
CPU Fan Min. Duty Cycle (%) [20]
Chassis Fan 1 Q-Fan Control [PWM Mode]
Chassis Fan 1 Q-Fan Source [CPU]
Chassis Fan 1 Step Up [12 sec]
Chassis Fan 1 Step Down [51 sec]
Chassis Fan 1 Speed Low Limit [Ignore]
Chassis Fan 1 Profile [Manual]
Chassis Fan 1 Upper Temperature [80]
Chassis Fan 1 Max. Duty Cycle (%) [100]
Chassis Fan 1 Middle Temperature [70]
Chassis Fan 1 Middle. Duty Cycle (%) [50]
Chassis Fan 1 Lower Temperature [50]
Chassis Fan 1 Min. Duty Cycle (%) [20]
Chassis Fan 2 Q-Fan Control [DC Mode]
Chassis Fan 2 Q-Fan Source [CPU]
Chassis Fan 2 Step Up [0 sec]
Chassis Fan 2 Step Down [0 sec]
Chassis Fan 2 Speed Low Limit [Ignore]
Chassis Fan 2 Profile [Manual]
Chassis Fan 2 Upper Temperature [78]
Chassis Fan 2 Max. Duty Cycle (%) [100]
Chassis Fan 2 Middle Temperature [75]
Chassis Fan 2 Middle. Duty Cycle (%) [65]
Chassis Fan 2 Lower Temperature [67]
Chassis Fan 2 Min. Duty Cycle (%) [60]
Allow Fan Stop [Enabled]
WATER PUMP+ Control [PWM Mode]
W_PUMP+ Fan Q-Fan Source [CPU]
WATER PUMP+ Upper Temperature [76]
WATER PUMP+ Max. Duty Cycle (%) [100]
WATER PUMP+ Middle Temperature [70]
WATER PUMP+ Middle. Duty Cycle(%) [60]
WATER PUMP+ Lower Temperature [40]
WATER PUMP+ Min. Duty Cycle (%) [20]
AIO PUMP Control [PWM Mode]
AIO PUMP Fan Q-Fan Source [CPU]
AIO PUMP Upper Temperature [55]
AIO PUMP Max. Duty Cycle (%) [100]
AIO PUMP Middle Temperature [50]
AIO PUMP Middle. Duty Cycle(%) [80]
AIO PUMP Lower Temperature [40]
AIO PUMP Min. Duty Cycle (%) [50]
M.2 Fan Q-Fan Control [PWM Mode]
M2 Q-Fan Source [CPU]
M.2 Fan Step Up [0 sec]
M.2 Fan Step Down [0 sec]
M.2 Fan Speed Low Limit [Ignore]
M.2 Fan Profile [Manual]
M.2 Fan Upper Temperature [65]
M.2 Fan Max. Duty Cycle (%) [100]
M.2 Fan Middle Temperature [60]
M.2 Fan Middle. Duty Cycle (%) [63]
M.2 Fan Lower Temperature [50]
M.2 Fan Min. Duty Cycle (%) [36]
Above 4GB MMIO Limit [39bit (512GB)]
Fast Boot [Disabled]
Boot Logo Display [Disabled]
POST Report [5 sec]
Bootup NumLock State [On]
Wait For 'F1' If Error [Enabled]
Option ROM Messages [Force BIOS]
Interrupt 19 Capture [Disabled]
AMI Native NVMe Driver Support [Enabled]
Setup Mode [Advanced Mode]
Launch CSM [Disabled]
OS Type [Other OS]
Flexkey [Reset]
Load from Profile [1]
Profile Name [V33]
Save to Profile [1]
DIMM Slot Number [DIMM_A1]
Download & Install ARMOURY CRATE app [Disabled]
Overclock [Enabled ]
Memory Clock Speed [Auto]
Tcl [Auto]
Trcdrd [Auto]
Trcdwr [Auto]
Trp [Auto]
Tras [Auto]
Trc Ctrl [Auto]
TrrdS [Auto]
TrrdL [Auto]
Tfaw Ctrl [Auto]
TwtrS [Auto]
TwtrL [Auto]
Twr Ctrl [Auto]
Trcpage Ctrl [Auto]
TrdrdScL Ctrl [Auto]
TwrwrScL Ctrl [Auto]
Trfc Ctrl [Auto]
Trfc2 Ctrl [Auto]
Trfc4 Ctrl [Auto]
Tcwl [Auto]
Trtp [Auto]
Tcke [Auto]
Trdwr [Auto]
Twrrd [Auto]
TwrwrSc [Auto]
TwrwrSd [Auto]
TwrwrDd [Auto]
TrdrdSc [Auto]
TrdrdSd [Auto]
TrdrdDd [Auto]
ProcODT [Auto]
Power Down Enable [Auto]
Cmd2T [Auto]
Gear Down Mode [Auto]
CAD Bus Timing User Controls [Auto]
CAD Bus Drive Strength User Controls [Auto]
Data Bus Configuration User Controls [Auto]
Infinity Fabric Frequency and Dividers [Auto]
ECO Mode [Disable]
Precision Boost Overdrive [Advanced]
PBO Limits [Manual]
PPT Limit [W] [142]
TDC Limit [A] [95]
EDC Limit [A] [140]
Precision Boost Overdrive Scalar [Manual]
Precision Boost Overdrive Scalar [6X]
Curve Optimizer [Per Core]
Core 0 Curve Optimizer Sign [Negative]
Core 0 Curve Optimizer Magnitude [18]
Core 1 Curve Optimizer Sign [Negative]
Core 1 Curve Optimizer Magnitude [12]
Core 2 Curve Optimizer Sign [Negative]
Core 2 Curve Optimizer Magnitude [18]
Core 3 Curve Optimizer Sign [Negative]
Core 3 Curve Optimizer Magnitude [18]
Core 4 Curve Optimizer Sign [Negative]
Core 4 Curve Optimizer Magnitude [18]
Core 5 Curve Optimizer Sign [Negative]
Core 5 Curve Optimizer Magnitude [12]
Core 6 Curve Optimizer Sign [Negative]
Core 6 Curve Optimizer Magnitude [12]
Core 7 Curve Optimizer Sign [Negative]
Core 7 Curve Optimizer Magnitude [18]
Core 8 Curve Optimizer Sign [Negative]
Core 8 Curve Optimizer Magnitude [12]
Core 9 Curve Optimizer Sign [Negative]
Core 9 Curve Optimizer Magnitude [18]
Core 10 Curve Optimizer Sign [Negative]
Core 10 Curve Optimizer Magnitude [18]
Core 11 Curve Optimizer Sign [Negative]
Core 11 Curve Optimizer Magnitude [14]
Core 12 Curve Optimizer Sign [Negative]
Core 12 Curve Optimizer Magnitude [18]
Core 13 Curve Optimizer Sign [Negative]
Core 13 Curve Optimizer Magnitude [12]
Core 14 Curve Optimizer Sign [Negative]
Core 14 Curve Optimizer Magnitude [18]
Core 15 Curve Optimizer Sign [Negative]
Core 15 Curve Optimizer Magnitude [18]
CPU Boost Clock Override [Disabled]
Platform Thermal Throttle Limit [Manual]
Platform Thermal Throttle Limit [95]
LN2 Mode [Auto]
SoC/Uncore OC Mode [Disabled]
VDDP Voltage Control [Auto]
VDDG Voltage Control [Auto]
NUMA nodes per socket [Auto]
LCLK Frequency Control [Auto]
LCLK DPM [Auto]
LCLK DPM Enhanced PCIe Detection [Auto]
Core Performance Boost [Auto]
Global C-state Control [Auto]
IOMMU [Auto]
TSME [Auto]
Custom Pstate0 [Auto]
L1 Stream HW Prefetcher [Auto]
L2 Stream HW Prefetcher [Auto]
Core Watchdog Timer Enable [Auto]
Power Supply Idle Control [Auto]
SEV ASID Count [Auto]
SEV-ES ASID Space Limit Control [Auto]
Streaming Stores Control [Auto]
Local APIC Mode [Auto]
ACPI _CST C1 Declaration [Auto]
MCA error thresh enable [Auto]
PPIN Opt-in [Auto]
Fast Short REP MOVSB [Enabled]
Enhanced REP MOVSB/STOSB [Enabled]
IBS hardware workaround [Auto]
DRAM scrub time [Auto]
Poison scrubber control [Auto]
Redirect scrubber control [Auto]
Redirect scrubber limit [Auto]
NUMA nodes per socket [Auto]
Memory interleaving [Auto]
Memory interleaving size [Auto]
1TB remap [Auto]
DRAM map inversion [Auto]
ACPI SRAT L3 Cache As NUMA Domain [Auto]
ACPI SLIT Distance Control [Auto]
ACPI SLIT remote relative distance [Auto]
GMI encryption control [Auto]
xGMI encryption control [Auto]
CAKE CRC perf bounds Control [Auto]
4-link xGMI max speed [Auto]
3-link xGMI max speed [Auto]
xGMI TXEQ Mode [Auto]
PcsCG control [Auto]
Disable DF to external downstream IP SyncFloodPropagation [Auto]
Disable DF sync flood propagation [Auto]
CC6 memory region encryption [Auto]
Memory Clear [Auto]
Overclock [Auto]
Power Down Enable [Auto]
Disable Burst/Postponed Refresh [Auto]
DRAM Maximum Activate Count [Auto]
Cmd2T [Auto]
Gear Down Mode [Auto]
CAD Bus Timing User Controls [Auto]
CAD Bus Drive Strength User Controls [Auto]
Data Bus Configuration User Controls [Auto]
Data Poisoning [Auto]
DRAM Post Package Repair [Default]
RCD Parity [Auto]
DRAM Address Command Parity Retry [Auto]
Write CRC Enable [Auto]
DRAM Write CRC Enable and Retry Limit [Auto]
Disable Memory Error Injection [True]
DRAM ECC Symbol Size [Auto]
DRAM ECC Enable [Auto]
DRAM UECC Retry [Auto]
Data Scramble [Auto]
DFE Read Training [Auto]
FFE Write Training [Auto]
PMU Pattern Bits Control [Auto]
MR6VrefDQ Control [Auto]
CPU Vref Training Seed Control [Auto]
Chipselect Interleaving [Auto]
BankGroupSwap [Auto]
BankGroupSwapAlt [Auto]
Address Hash Bank [Auto]
Address Hash CS [Auto]
Address Hash Rm [Auto]
SPD Read Optimization [Enabled]
MBIST Enable [Disabled]
Pattern Select [PRBS]
Pattern Length(VMR) [6]
Aggressor Channel [1 Aggressor Channel]
Aggressor Static Lane Control [Disabled]
Target Static Lane Control [Disabled]
Worst Case Margin Granularity [Per Chip Select]
Read Voltage Sweep Step Size [1]
Read Timing Sweep Step Size [1]
Write Voltage Sweep Step Size [1]
Write Timing Sweep Step Size [1]
Precision Boost Overdrive [Auto]
Precision Boost Overdrive Scalar [Auto]
FCLK Frequency [Auto]
SOC OVERCLOCK VID [0]
UCLK DIV1 MODE [Auto]
VDDP Voltage Control [Auto]
VDDG Voltage Control [Auto]
SoC/Uncore OC Mode [Auto]
LN2 Mode [Auto]
ACS Enable [Auto]
PCIe ARI Support [Auto]
PCIe ARI Enumeration [Auto]
PCIe Ten Bit Tag Support [Auto]
cTDP Control [Auto]
EfficiencyModeEn [Auto]
Package Power Limit Control [Auto]
APBDIS [Auto]
DF Cstates [Auto]
CPPC [Auto]
CPPC Preferred Cores [Auto]
NBIO DPM Control [Auto]
Enable AER Cap [Auto]
Early Link Speed [Auto]
Presence Detect Select mode [Auto]
Preferred IO [Auto]
CV test [Auto]
Loopback Mode [Auto]
SRIS [Auto]
Data Link Feature Exchange [Disabled]