BSOD's With Ryzen 9 5900x and GSkill RAM

Logger entries are beyond me I'm afraid

OldNavy said:

Logger entries are beyond me I'm afraid

Click to expand...

You need to go to Event Viewer and select on the left-hand-side, "Event Viewer (Local)".
Then you should see categories of messages.

OldNavy said:

CPU temperature always below 65C, i have a noctua cooler

Click to expand...

Always? You've stressed the CPU?

The free CPU-Z can do that.

Always, yes i stressed the crap out of it.

OldNavy said:

Always, yes i stressed the crap out of it.

Click to expand...

I presume that you mean that you monitored the CPU temperature while you beat on it.

Yes, i used HWInfo

OldNavy said:

Thank everyone for your suggestions.
The two sticks are good at default bios settings and memtest86 (3 separate tests).
Catnip - by loosen to do mean a larger number or a smaller number for the timing?
Here are the screenshots from cpu-z..
View attachment 115414 View attachment 115415

Click to expand...

It shows your RAM as running on JEDEC #6 or 2133 MHz. That RAM should be just humming along with no problems at all at that speed, so that is good. The question is why won't the RAM run at its rated speed? Don't forget to set the voltage when you set the timings, unless you are using XMP, then it does it for you.

Loosening the timings means going to a larger number. So if your CL (CAS latency) is 15, you could try it at 16 and see if that stabilizes things for you. Only adjust one parameter at once though and maybe don't touch the parameters that are not mentioned in CPU-Z. And try not to overvolt the RAM. I wouldn't go any higher than 1.36V if you were thinking of doing that. Better yet, leave it at 1.35V and don't mess with the voltage too much. It can break the RAM if it is too high.

I just got rid of some GSkill 3600 RAM in an upgrade, and those timings for the XMP mode were the same as mine. My PC was running flawlessly with those timings at 3600 MHz. I would assume that yours should as well.

At this point I am wondering if there is a bad memory stick, or as RJARRRPCGP is suggesting, a machine check error. To rule out a bad stick, run Memtest86+ for a few passes with the RAM set at default (2133 MHz - the way it is now), and then at 3600 MHz to see if there is a difference. If it fails at 3600 MHz, try loosening the CL timing by one and try again. This can be a long process.

But before you do that, do the check on the machine check error in Event manager. It may not be your RAM that is the problem here. What is your CPU voltage? And are you overclocking?

​

Thanks Catnip.
No overclocking and i have not touched the CPU voltage.
All memtests were done with default bios settings so 2133MHz and these two sticks have not failed.I will try loosening the CL and see how it goes.
Cheers

I have tried a range of different latency values, changing the command rate (1T and 2T) and the range of memory frequencies.
All fail in the end.
I also tried a fresh install of win 11 24H2 and it also failed when setting the bios to DOCP.
I will have to admit defeat and swap back to my 5600X CPU> I'll try it with this ram and if it fails i will revert tob my previous set of F4 3600C18Q-32GTZN which was rock solid.
Thank you to all who contributed to this topic.
To paraphrase Donald Rumsfeld this is a "known unknown".

I would revert to your previous RAM before swapping out the CPU.

Just me though.

The initial ram was there when I put in the new cpu. Bsod’s began.
I then purchased the new ram. New cpu with new ram gives Bsod’s
The old cpu with the old ram should give me a rock solid setup again.

Ahh. I see. It seemed to me that you were saying that the old RAM was stable. Now I understand what you mean.

OldNavy said:

The initial ram was there when I put in the new cpu. Bsod’s began.
I then purchased the new ram. New cpu with new ram gives Bsod’s
The old cpu with the old ram should give me a rock solid setup again.

Click to expand...

Looks like a faulty CPU.

RJARRRPCGP said:

Looks like a faulty CPU.

Click to expand...

Bent pins?

bobkn said:

Bent pins?

Click to expand...

I sometimes would wish that it was just a pin that I can straighten out, LOL. Unless it's a Zen+ (second-gen Ryzen) or older, there's no "2933 MT/s limit". With a Vermeer, it's more likely a bad IMC in the CPU. Based on my experience with a Ryzen 7 5800X that I got in 2022, IIRC, which is the one where I suddenly got "MEMORY_MANAGEMENT" BSOD from 11 22H2 under a light load on May 18, 2023.

I suspect it's that chip, because I popped the same RAM into a new Ryzen that's the X3D variant of the 5800X in 2024, and no signs of RAM corruption, even at 3600 MT/s!

The 5800X that I last used in May, 2023, is the regular variant. (not the X3D)

Did not see any.
I have put the 5600X back in with the new ram F4 3600C16-16GTZNC and I'll see how it goes.
when i pluck up the enthusiasm again i will try the Ryzen 9 5900X again

Please run the V2 log collector > post a share link

zbook,
Thank you for the instructions.
Here is the link..

Please post a link that does not require sign in.

You need access​

Request access, or switch to an account with access.

Sign in​

to continue to Google Drive

I apologise,
Try this link