I've been experiencing the random resets, WHEA and BSOD for 3 months on a 6-month old build. I'd be gaming, then everything hangs, screen goes black, and all the fans ramp up to the max, requiring a hard reset. Listed as Event ID 41.

But I may have found a solution, hopefully it helps someone else out.

Rysen 5 3600
B550 Aorus Pro AC
RTX 3080 Aorus Master
G.SKill Trident Z Neo 3600 CL18 (4x8GB)
Aorus copper SSD 1TB
Adata SX8200 Pro SSD 1TB
Corsair RM850

I'm convinced the issue is with memory compatibility and the stock XMP profiles, along with BIOS. I spent the last week messing around with different BIOS versions, and RAM settings.

Previously, I could never run the stock XMP profile with this RAM. It would always crash for certain games. Initially, I got around it by just manually changing only the memory speed multiplier to 36.00, and that seemed to work. For awhile, at least. Also, my particular model of RAM is NOT on the QVL list for this mobo, even though it looks the same as other Trident Z RAM.

I started with 16GB, then added another 2 sticks for 32GB, and stability became an issue again. As I began to learn more about RAM, I discovered other settings in the BIOS to tweak, because without the XMP profile on, the timings were very loose (26-25-25-58 @ 3600mhz, 1.20v), and it wasn't delivering enough voltage to sustain 3600 mhz.

I also discovered another setting in Gigabyte BIOS called "XMP High Frequency Support". This is key, because until I messed around with this, it wasn't stable. Did some digging online and on Reddit, found there are 3 levels, which apparently correspond to RAM speed. Level 3 is 3600, 2 is 3400 and 1 is 3200. I chose Level 3 to support the max rated speed of my RAM. If you change your RAM speed, you also have to change your Infinity Fabric speed to half your RAM speed, to maintain 1:1 ratio. Usually, these settings should be done when set on AUTO, but somehow they don't work for me.

Also, I found out that for my particular RAM which is made with Samsung C-die, the max voltage is 1.35v. But when I set it to 1.35, it still crashes and shows about 1.4 in the monitoring apps. So I set it to 1.30v, and got more stability (showing 1.35v in monitoring.)

Right now, I've been pretty stable for a day with no crashes. My recipe:
BIOS F12 (AGESA 1.1.0.0 D)
XMP enabled
XMP High Frequency Support Level 3
Memory Speed multiplier 36.00
DRAM voltage 1.30v
Infinity Fabric speed 1800mhz

I had to manually input all of these in BIOS. Fingers crossed, everything seems fine so far, but it's only been a day with no crashes. I used to get 2-3 crashes a day.

YMMV, because it really depends on the particular combination of BIOS, RAM, mobo and CPU. This worked for my particular rig, might be different for yours. But I hope this helps someone somehow!

This post has been edited by senzr: Feb 2 2021, 06:35 PM

XMP High Frequency Support Level 3 is just a quick way to set the IF but at fixed steps. It’s better to use auto and set it to be coupled instead. 1800mhz IF at 3600mhz ram is not guaranteed to work on zen2 so gotta keep that in mind.

This post has been edited by Bonchi: Feb 2 2021, 09:00 PM

In my case, I only got the system stable if I set High Frequency Support to Level 3 AND manually set the IF speed, memory speed + voltage. Shouldn't have to double confirm like that in AUTO, but that's a quirk of Gigabyte boards, I guess. Got this tip from Gigabyte forums and Reddit, so I'm not the only one who had to do it.

I'm aware the R5 3600 is only officially guaranteed to run RAM at 3200mhz, but many folks are running at 3600mhz, and I already paid for the 3600 kit, so just gatal to get my money's worth. Just didn't anticipate it'd take so much effort to get it working properly...

Another upshot is that my Time Spy scores have improved by 200 points with the current XMP settings (1.30v, 18-22-22-42) compared to when I previously ran the RAM at 3600mhz manually and left everything else at auto (1.20v, 26-25-25-58). The auto settings are pretty loose and safe.

This post has been edited by senzr: Feb 2 2021, 09:40 PM

in most cases, xmp doesnt work out of the box even for 3600 as each board will intepret it slightly differently thus the instability varies, especially on the difference at the subtimming and SoC voltage. So most will require manual input. You can use dram calculator and slowly work you way out of that... I believe you can find lots of guides on ram tweaking in AMD OC thread.

Oh wow...you mean even if a RAM kit is listed in the mobo's QVL, it isn't just plug n play?
I was planning on avoiding this whole hassle in future builds by just checking the QVL...

qvl is just what vendor has tested with their hardware, mainly their cpu sample. Plus they could be halving the IF or not we wont know.. as QVL is just a confirmation that the board can run the RAM at such speeds... not the cpu IF

How high the IF can go is depending on the luck of the silicon in the cpu. So you can take QVL as just an assurance, not a guarantee.

I have used rams from qvl and those that are not. They all have almost similar chances of success and failure at running on xmp however when it comes to overclocking, the qvl status becomes irrelevant.

This post has been edited by Bonchi: Feb 3 2021, 01:01 PM

There is some correlation between CPPC values and voltage, but it's not consistent.

CPPC values, core priority from HWInfo and Curve Optimizer negative offsets below that survived 24hour Prime95 blend test:
127 7/8 13
146 2/3 10
143 3/4 16
150 1/1 10
135 5/6 13
139 4/5 16
150 1/2 8
131 6/7 15

Started with -20 and slowly bumped up the offset for any crashing cores in Prime95.

Now to figure out if it's stable during low power usage... what tools would be best to simulate that?

This post has been edited by yimingwuzere: Feb 3 2021, 08:27 PM

the only tool i know is patience... just wait for it to crash

No WHEA errors so far... then again I didn't test this extensively by adjusting other values like LLC or voltage offset yet.

Haven't figured out what's a good tool to use to test that though. In the meantime, gonna give CTR 2.0 a spin - but I probably won't use it for daily until it supports curve optimizer.
https://www.igorslab.de/en/clock-tuner-for-...-and-much-more/

CTR tells me my CPU is a "silver sample".

This post has been edited by yimingwuzere: Feb 4 2021, 10:01 AM

Haven't played too much with CTR 2.0, but so far... I don't know, I'm mixed about it. Using it means disabling PBO but you potentially get better all-core OC. To me, I'm using the PC for both work and play, so while I do like the all core OC, I do miss the single/dual core PBO.

So far, I think I still prefer curve optimizer as a whole.

Only advantage to using it is that it emulates a hybrid mode similar to the Asus Dark Hero, so it swaps all-core overclocks for max single core mode when low CPU usage is detected.

Curve Optimizer is planned for 2.1 so I'll wait for that. This tool as it stands right now seems best to fish out the quality of your CPU. Mine is a "silver sample", wonder how well "golden samples" work with Curve Optimizer.

How different is the outcome when running the ctr clock/volt recommendation using their profile setup vs setting those clocks/volt in bios?

This post has been edited by Current Events guy: Feb 5 2021, 05:23 PM

New chipset driver out.

https://www.amd.com/en/support/chipsets/amd-socket-am4/x570

Release Highlights
General system stability improvements.

This is important:

AMD PCI Device Driver
1.0.0.81 > 1.0.0.82 - Bug fixes

If this fixes the PCIE4.0 GPUs causing USB/audio drop outs, then that's a golden fix.

It could be finally one of the fix i’ve been waiting since 2019 if it really is.... but then a new agesa might have a chance to mess up the current stability level.. haihhhh

I'm reading mixed response on reddit. Can't confirm it myself because I don't have the issue to begin with. You tried it yet?

I have not tested manual clocks in BIOS. Curve Optimizer tuning is more in line with what I want to achieve, since all manual results in lower clockspeeds than the maximum possible single core turbo speed achievable. CTR of course aims to remedy this by switching off the all core overclock when low CPU utilization is detected (similar to Hybrid OC on the Asus Dark Hero, but with different detection methods), but another aim of Curve Optimizer is that it can potentially reduce power consumption even after hitting max turbo clocks. CTR will only support Curve Optimizer in version 2.1.

This post has been edited by yimingwuzere: Feb 5 2021, 11:08 PM

because it's AMD... im gonna wait it out longer to see responses and review first before proceeding to avoid more complications. Rolling back to an older AGESA is not that simple... need to do USB Qflash/flashback which requires a full system strip down.

This isn't AGESA, it's the AMD driver chipset package.

owh? it's the chipset driver? then maybe I'll give it a try... but it will take about month to find out .