OK, looks like 3600 of 32 GB isn't worth it, maybe my Ryzen 7 5800X is poop!

[RJARRRPCGP]

I got a BSOD out of the blue, Windows 11 22H2 suddenly said "MEMORY_MANAGEMENT" after looking at the weather.

OK, I tried Linpack Extreme in max-RAM mode and it also failed with the G.Skill Trident Z Neo at 2133! Linpack apparently failed at 2133, as well!

I now have an XPG 16 GB kit in for now.

 

[Hyderz]

dont rule out the cpu yet, could be the motherboard that is the culprit

 

[RJARRRPCGP]

dont rule out the cpu yet, could be the motherboard that is the culprit

Most likely, it failed at only about the 12 GB region, when I got the sudden BSOD! (11 still has blue screens like 10, at least 22H2 does, not black screens like what people were reporting)
I had Firefox with a lot of tabs and I opened up Edge with one tab to check the weather. That BSOD, sure looks like RAM corruption!

I was able to play Hogwarts Legacy fine with 16 GB of RAM. Just don't have major extras opened. Then it will be in the 12 GB to 14 GB ballpark. Possibly less than 14 GB much of the time.

 

[Dr. Dro]

Most likely, it failed at only about the 12 GB region, when I got the sudden BSOD! (11 still has blue screens like 10, at least 22H2 does, not black screens like what people were reporting)
I had Firefox with a lot of tabs and I opened up Edge with one tab to check the weather. That BSOD, sure looks like RAM corruption!

I was able to play Hogwarts Legacy fine with 16 GB of RAM. Just don't have major extras opened. Then it will be in the 12 GB to 14 GB ballpark. Possibly less than 14 GB much of the time.

With an insanely high paging rate due to extreme commit charge... yeah, experience won't be as good. Does your Adata kit cause the same BSOD symptoms?

 

[RJARRRPCGP]

With an insanely high paging rate due to extreme commit charge... yeah, experience won't be as good. Does your Adata kit cause the same BSOD symptoms?

I have yet to get a BSOD. It was my first BSOD and it was out-of-the-blue with the G.Skill Trident Z Neo 2x16GB 3600 kit. With that RAM in, suddenly, I couldn't even do 2133 without Linpack Extreme reporting an error!

I'm at 2666 and still no error so far with the AData XPG kit. And it looked like my single core scores went up after changing the RAM, even with a lower frequency!
Wonder if that slowness with the 32GB kit, was one of the symptoms of the hardware instability.

 

[Dr. Dro]

I have yet to get a BSOD. It was my first BSOD and it was out-of-the-blue with the G.Skill Trident Z Neo 2x16GB 3600 kit. With that RAM in, suddenly, I couldn't even do 2133 without Linpack Extreme reporting an error!

I'm at 2666 and still no error so far with the AData XPG kit.

Yeah looks like your G.Skills might need an RMA. I don't think it's the processor but if it fails in a consistent manner, kit is just busted.

That density or frequency you are running should be a cinch for a 5800X.

 

[RJARRRPCGP]

Yeah looks like your G.Skills might need an RMA. I don't think it's the processor but if it fails in a consistent manner, kit is just busted.

That density or frequency you are running should be a cinch for a 5800X.

Got the BSOD unexpectedly as if I were a PC noob, LOL. That was at 3600 then I turn it down and still an error in Linpack Extreme in the testing mode designed to test as much RAM as possible. Even that, may be broken and cause false errors. But this time, I doubt there was a false error, as I got a "MEMORY_MANAGEMENT" BSOD in my face!

And IIRC, this is the same motherboard where it passed flying colors with TestMem5, with the Ryzen 5 5600X, with the G.Skill Rip Jaws V 3200 sticks! (C14, IIRC) Those are 2x8 GB.

Been using the Trident Z Neo sticks for 1 year or almost 1 year. It's the only one I have that's a 32 GB kit. (2x16 GB)

And the 32 GB kit is from 2022, thus looks faulty to me, unless my Ryzen 7 5800X or ASRock B550 PG Velocita is faulty somehow!

 

[Dr. Dro]

Only way to know is testing same kit with another mobo or CPU. But its possible it went bad somehow.

 

[eidairaman1]

Only way to know is try different ram, if still bsods, could be motherboard or cpu.

 

[freeagent]

Been running 4x8 G.Skill 3200C14 on 3 different CPUs for 2.5 years, no problems hombre. Maybe clear the CMOS and re enter your settings and do some testing.

 

[RJARRRPCGP]

The only setting I applied, was the usual XMP profile. And that reminds me, could have forgotten, that clearing the CMOS (and even updating the UEFI-BIOS) is a pain when you have Windows 11 as the OS.
If Windows 11 loads before I apply Secure Boot, then I definitely expect Windows 11 to get sus!

 

[freeagent]

I don't like XMP/DOCP.. but I also cant help you to tune because all I know is this B-Die

 

[GamerGuy]

Though I have a different CPU, it's of the same generation, an R9 3900X in my 2nd rig on a GB X570S Aorus Elite AX and it's fine with 2x 16GB RAM. When I had the 3900X in my main, the mobo is the GB X570 Aorus Xtreme, it ran just fine with 4x 8GB DDR4 3200MHz XPG RAM (which I still have as kinda backup should my present ram gimme issues.

 

[Toothless]

It could be the board. Not sure if reviews show memory at 3600 or beyond but I've got 32GB kits to hit 3600 and 3800 on x570. That's with a 5950x and 3900x.

Even a 4x16 kit on 3600 but man was that not stable.

 

[eidairaman1]

It could be the board. Not sure if reviews show memory at 3600 or beyond but I've got 32GB kits to hit 3600 and 3800 on x570. That's with a 5950x and 3900x.

Even a 4x16 kit on 3600 but man was that not stable.

My GFs rig I built is using a Crucial Ballistix Gaming Red 32GB 3600 Kit on the AsRock B550 Steel Legend on a 5800 OEM.

 

[RJARRRPCGP]

With the major instability incident, should I say "F-it" and get my first Raphael build?! I wouldn't mind starting out with a Ryzen 5 7600X(?) or similar. Then, I bet it won't give me hell with 32 GB of RAM capacity!

If I do get my first Raphael build, looks like it means no OLED for me!

 

[ir_cow]

It could be the board. Not sure if reviews show memory at 3600 or beyond but I've got 32GB kits to hit 3600 and 3800 on x570. That's with a 5950x and 3900x.

Even a 4x16 kit on 3600 but man was that not stable.

Yeah 4x dual rank is quite hard. Half the FCLK it might be stable, but what's the point. It will perform worse than 2933

With the major instability incident, should I say "F-it" and get my first Raphael build?! I wouldn't mind starting out with a Ryzen 5 7600X(?) or similar. Then, I bet it won't give me hell with 32 GB of RAM capacity!

If I do get my first Raphael build, looks like it means no OLED for me!

Well if you go with AM5 high frequency and density memory support will be questionable if you aren't willing to play around with voltages yourself.

Just using EXPO/XMP below is what you should expect. Some motherboards really have a low VDDIO-mem voltage. If you don't manually change it, pretty much your limited to a single 2x SR Kit of DDR5-6000 and what I listed below. 6400 is unlikely to be stable for 99% of users. That is unless you want to pump the voltages and go into meltdown mode

2x Single Rank - DDR5-6000
4x Single Rank - DDR5-5200-5600
2x Dual Rank - DDR5-5600-6000
4x Dual Rank - DDR5-4400-4800

 

[TheoneandonlyMrK]

With the major instability incident, should I say "F-it" and get my first Raphael build?! I wouldn't mind starting out with a Ryzen 5 7600X(?) or similar. Then, I bet it won't give me hell with 32 GB of RAM capacity!

If I do get my first Raphael build, looks like it means no OLED for me!

It's not the capacity, it's the speed and timing, I too have both had issues hitting 3600,, and got it.

The CPU will hit a infinity fabric wall every time because usually you can stabilise memory with timings but that wall can't be climbed.

Try enabling XMP then reboot and manually set all the same primary memory timings.

Now reduce the fabric clock manually to 200mhz less, so 1600 for 3200buss rate.

Then run hwinfo64 and a test, if it shows no whea errors at the bottom of the "Sensor" page it should be stable.

If so keep nudging up your fabric clock by 33/66/100 until you see errors in hwinfo64.

At that point you could try upping.some voltages like soc Vram etc and retest.

Once you find your highest fabric clock, set your memory to that.

But you need to get to the root of your symptoms limit here.

Buying new to mitigate this , I mean it's new, you think it's Stabler than your five year old platform?!, That's not what I am seeing.

 

[RJARRRPCGP]

It's not the capacity, it's the speed and timing, I too have both had issues hitting 3600,, and got it.

The CPU will hit a infinity fabric wall every time because usually you can stabilise memory with timings but that wall can't be climbed.

Try enabling XMP then reboot and manually set all the same primary memory timings.

Now reduce the fabric clock manually to 200mhz less, so 1600 for 3200buss rate.

Then run hwinfo64 and a test, if it shows no whea errors at the bottom of the "Sensor" page it should be stable.

If so keep nudging up your fabric clock by 33/66/100 until you see errors in hwinfo64.

At that point you could try upping.some voltages like soc Vram etc and retest.

Once you find your highest fabric clock, set your memory to that.

But you need to get to the root of your symptoms limit here.

Buying new to mitigate this , I mean it's new, you think it's Stabler than your five year old platform?!, That's not what I am seeing.

I ironically didn't get any WHEA errors and I found out that if I enabled XMP previously and change it to "Auto", the only other option, then the Fclk stayed at 1800 MHz while the RAM was at 1333(x2), (2666) LOL. I noticed that I ran Linpack Xtreme in that state by accident and Linpack Xtreme didn't error out, LOL. With the UEFI-BIOS of the ASRock B550 PG Velocita, you must set Fclk manually, when dropping the RAM frequency. (At least with the recent one (P2.40) ) I didn't notice that until I ran HWInfo64.