AMD Crashes following clocking

[jouleskeys]

Unsure of the reason as have applied the relevant numbers in the bios to get the ram up to speed. Can someone please check on this and tell me if I am applying the wrong numbers into the Calculator?
Am just tweaking up to the ram's suggested (3600mhz) amount. By default the bios thinks it should be running at 2666, hence the clocking up.

I have also checked this via scanning with MemTest in Safemode, which scrashes and reboots. I finally had an error. Perhaps someone can tell em what this error means?

Thank you

 

[TheoneandonlyMrK]

Unsure of the reason as have applied the relevant numbers in the bios to get the ram up to speed. Am just tweaking up to the ram's suggested amount on the package, which is weird.
Can anyone suggest what this error means?

Your overclocking your memory via oneusmus calculated figure's.
That's what's wrong.

Are you sure you're memory is the type you think it is.

Is your Integrated memory controller capable of those speeds (always unknown until Proven).

Or do you need more Volta somewhere.

1usmus calc isn't infallible.

 

[jouleskeys]

Your overclocking your memory via oneusmus calculated figure's.
That's what's wrong.

Are you sure you're memory is the type you think it is.

Is your Integrated memory controller capable of those speeds (always unknown until Proven).

Or do you need more Volta somewhere.

1usmus calc isn't infallible.

@TheoneandonlyMrK Maybe, perhaps you could tell me if I have this wrong?

"oneusmus figures" - I see...

When I purchased the ram, it showed up as 2x 16gb @ 3600mhz. Here is the ram attached.
Furthermore, it seems it just does not allow me to clock to the rams numbers, so I guess I should either just sell this one and get another for the Asrock Extreme4 x570 mb or just settle with 2666mhz.
Thought I would try here to see if there's anything I am missing or got wrong...?

 

[chrcoluk]

Are these Samsung B die?

I have found that tool to be too aggressive to non B-die chips. Typically either non post or instability.

First reply was good, forget the tool, configure XMP, if its stable leave it there, if not stable drop the MHZ by one notch until its stable.

 

[TheoneandonlyMrK]

@TheoneandonlyMrK Maybe, perhaps you could tell me if I have this wrong?
When I purchased the ram, it showed up as 2x 16gb @ 3600mhz. Here is the ram

Well the pack say's 3600 Cl1 18,22,22,22,42 one assumption made for athird 22 , like mine.
You should be able to set DCOP dram Oc profile in bios under the heading of CPU profile, usually auto or default.

You shouldn't Need to set every timing it'll auto set them with the DCOP profile.

It is possible your IMC won't do 1800 MHz though so first try that then try manually setting the primary main four or five, leave everything else automatically set and try 3200 manually set as a memory frequency.

 

[GerKNG]

I have found that tool to be too aggressive to non B-die chips. Typically either non post or instability.

not just B-Die. 95% of all ICs.

 

[eidairaman1]

Reset the cmos to defaults, put ram in Slots 2 and 4 from the left (CPU 1,2,3,4), then turn on XMP/DOCP

We need complete detailed system specs

Unsure of the reason as have applied the relevant numbers in the bios to get the ram up to speed. Can someone please check on this and tell me if I am applying the wrong numbers into the Calculator?
Am just tweaking up to the ram's suggested (3600mhz) amount. By default the bios thinks it should be running at 2666, hence the clocking up.

I have also checked this via scanning with MemTest in Safemode, which scrashes and reboots. I finally had an error. Perhaps someone can tell em what this error means?

Thank you

Slots 1, 3 are only used when all 4 slots are occupied

 

[jouleskeys]

The ram is in slots 2 and 4.
@eidairaman1 The board is an Asrock Extreme x570, AMD 3950x CPU, Asus 6500XT graphics on x16 PCIe (Gen Auto), FireWire TI x16 PCIe, 2x M.2 drives onboard.
Currently all set at default, which means ram timings are out and 2666mhz.

XMP timings crash the system even when all set at auto and to the Corsair numbers.

Help

 

[TheoneandonlyMrK]

The ram is in 2 and 4 slots.
The board is an Asrock Extreme x570, AMD 3950x CPU, Asus 6500XT graphics on x16 PCIe (Gen Auto), FireWire TI x16 PCIe, 2x M.2 drives onboard.
Currently all set at default, which means ram timings are out and 2666mhz.

XMP timings crash the system even when all set at auto and to the Corsair numbers.

Help

Well, I would try 3200 manually set with those primary timings ,the rest on auto , set your memory voltage to 1.38 a safe bet voltage, and retry , if it boots you can up it a step at a time and see where you get, and go from there.

 

[damric]

From your first screenshot it looks like you are trying to jam CL12 into a low-end bin of Micron E-die (CL18 according to your Thaiphoon). That's just not going to work.

 

[jouleskeys]

Well, I would try 3200 manually set with those primary timings ,the rest on auto , set your memory voltage to 1.38 a safe bet voltage, and retry , if it boots you can up it a step at a time and see where you get, and go from there.

Thank you, though did this at 3200 with the v at 1.38, and then have done a memtest in safe mode and had another error, as seen.
Where to next?

 

[oobymach]

You probably need to set ram voltage along with xmp, some are for intel only and run @ 1.2v where you may need 1.4 on an amd board for the same ram, set yours to 1.35v (the sticker value from your ram) and see if xmp will boot then.

If xmp is still a no go, set everything to auto except the primary 18-22 etc and after booting restart and go into bios and see what it sets timings at for auto, and post a screenshot of zen timings if you can.

If still getting errors set the trfc manually to your rams value, I can't remember how to find the rams trfc I think it's in the bios just check for one of your sticks and set the trfc value to a multiple of 16.

I have rubbish hynix mjr rams and this is the best I can do without errors.

 

[TheoneandonlyMrK]

You can up memory voltage to 1.85 and I tend to change vcsoc or soc and CPU voltage to optimize + and if it still crashes try vcsoc 1.15

 

[jouleskeys]

From your first screenshot it looks like you are trying to jam CL12 into a low-end bin of Micron E-die (CL18 according to your Thaiphoon). That's just not going to work.

@damric please give me some direction on what to do to resolve this issue if you can

Tried upping voltage and still rebooting.
Also tried a memtest usb, which comes back with 0 errors.

Here are default numbers in the BIOS at 3600mhz - in hope that someone will notice an issue that I can tweak to fix the issue.

 

[damric]

@damric please give me some direction on what to do to resolve this issue if you can

Tried upping voltage and still rebooting.
Also tried a memtest usb, which comes back with 0 errors.

Here are default numbers in the BIOS at 3600mhz - in hope that someone will notice an issue that I can tweak to fix the issue.

Ok
1) lower your expectations. Ryzen memory controller is only specified to work at 3200MT/s with JEDEC timings. Start there. Anything faster than that consider a success.

2) You might just have a crummy kit. Corsair is notorious for poor compatibility with Ryzen. Return it and get some Crucial Ballistics or G.Skill FlareX if you want easy drop-in overclocking.

3) There is no "one size fits all" approach to memory overclocking. The 1usmus calculator is an ok guideline but it's outdated and has poor compatibility for ICs other than Samsung B-die.

 

[Chomiq]

Correct me if I'm wrong but from I remember and just tested the values on the right show your current timings:

My timings for completely different kit:

So your screenshot shows that you're running the memory at CL12 and not CL16.

VDDG needs to be 0.05 below the SoC VID:

Paging @The King since he's got more experience with OC'ing E-die.