I'm not 100% - though there has been mention of potential BIOS issues with 3rd Gen Ryzen and FCLK set for anything above 1600mhz currently. May give it a try and see if it clears up.

There's been one mention that it's potentially very sensitive to SOC and lowering it may give some relief - however I haven't found it to resolve the issue just yet.

Currently waiting on new BIOS releases to see if it clears the issue up. Early adopter headaches perhaps...

(edit - sorry just noticed you mentioned it happens at stock too... Which may already be lower than 1600mhz FCLK... The one individual that mentioned SOC mentioned setting it for 1.0v?)

 

You can see it happening over with a aorus xtreme on another thread.

Replaced 3950X with 5950X = WHEA and reboots

Hello, Please vote on the pool only if your system is not stable with BIOS defaults, memory at 2133 Mhz without XMP, without any CPU or RAM overclocking, without PBO or any voltage tweaks and of course, if you do not have any issues with your Ryzen 5000 or your problem has been fixed. * you can...

www.overclock.net

 

If you check the minidump file, it's caused by the processor (cpu)

 

Set your FCLK to 1600Mhz and DDR mhz to 3200.
This need to fixed by board manufactors with bios updates.

 

I have my 3800X stable with 1900fclk and 3800mhz memory, 2502 BIOS. It took some time. 1900 requires 1.125v SOC, VDDP 0.9v, VDDG's 0.95v, anything lower on the SOC and I get WHEA's in OCCT. 1800fclk required 1.1 SOC same on the other voltages.
But yeah the post above is 100% right. I start and have with all three BIOS I have used with this new CPU at 1600/3200. Firstly F5 load optimised defaults. I set the memory to DOCP (in my case 4000 18-19-19-39), I then set the frequency to 3200mhz and the FCLK to 1600mhz, a SOC voltage of 1.1v and DRAM voltage of 1.45v. I then work my way up, not touching memory timings which will be extremely loose with that DOCP at 3200,3400 ect. Increasing the memory frequency and FCLK 1:1, experimenting with SOC, VDDP and VDDG's to achieve stability. No other settings are changed. I use OCCTs large data set test, it will give you WHEAs very quickly if your settings are off. Try exactly that.
Once that's stable you can then tighten timings and add a PBO overclock or whatever takes your fancy overclock wise.
I have the non WiFi Crosshair VIII, Noctua NH-D15, Micron E-Die Crucial Max 4000 16GB, 850W EVGA, 2080TI

 

Exactly same boat as me.... i think this is quite common

WHEA 0x00000124

Tried multiple BIOS versions

Bloody nuisance!!

Basically this motherboard and AMD 5800x have issues, pending vendor to resolve this.

 

#meetoo

Asus X570-E WHEA and memory errors at both stock and XMP profiles with my 5950x - I did NOT have any issues with same setup on my former 5800x though.

I got this error on the 2 latest beta bioses which worries me:

"
A fatal hardware error has occurred.

Reported by component: Processor Core
Error Source: Machine Check Exception
Error Type: Cache Hierarchy Error
Processor APIC ID: 0
"

Cache hierarchy sounds internal CPU related so not sure if bios update / new RAM solves it..

Waiting for new RAM to test out shortly though

C

 

EDIT - There are a fair amount of Gigabyte X570 users reporting similar issues as well. If the issue is strictly something with the FCLK they do have a release that states improved FCLK capability on revision F31I. However, one thing I noticed is despite that mention it's using AMD AGESA 1.1.0.0 C - which are the same revisions the ASUS beta's are using that have issues. The ASUS revision that works for me uses AMD AGESA 1.1.0.0 B (if that's playing a role in all of this).


Was having issues with WHEA with Zen 3 on my X570 board with FCLK set above 1600mhz.

After working with ASUS flashing 2802 resolved that issue for me. I never crashed - but perhaps it will assist with this issue as well?

I'm currently OC'd to 3666/1833 CL15 using settings based off DRAM Calc with no WHEA/crashing.

https://dlcdnets.asus.com/pub/ASUS/mb/SocketAM4/ROG_STRIX_X570-E_GAMING/ROG-STRIX-X570-E-GAMING-ASUS-2802.ZIP

 

I has similar issues but downgrading from two latest patch-C bios versions (which are beta) from Asus to Patch-B 2802 version cleared all the problems.

 

I can inform you that my 5950x on an Aorus Xtreme was working fine for over a week straight under all kinds of heavy work loads with no issues until today.

Rewind to where i built the machine, i built my computer around a week ago, i started doing a lot of stress testing and initially found that 3600mhz/1800flck was 100% stable for my system without doing anything to any of the voltages.

I've been running all kinds of stuff on my computer doing rendering, gaming and a ton of stress testing with aida64, memtest etc, the only thing i didn't do was leave my computer running at idle until last night.

I left my computer rendering a video project at the evening, it completed around 1am. After that i was sleeping for another 7+ hours, so the computer was idle for 7 hours or more. During this time (the first time i've really left this new system to idle) it appears the WHEA errors started appearing in my event log, i had zero of these errors until now.

I started looking into it and realized it is directly related to the heavy boosting the cpu does under idle load, the cpu actually spikes the core with 1.5v instead of under heavy load the cpu usually consumes around 1,25v. The sad thing is now my cpu that was fully functional at 3600mhz/1800flck for over a week is no longer stable at stock speeds 2666mhz/1333flck, i'm getting WHEA errors left and right and nothing i do seems to get rid of them.

My theory is that the CPU silicone was actually degraded during the night while the computer was idle and the "boost algoritm" was serving it 1.5v of power for those smaller workloads like keeping windows services and whatever running boosting the cpu to 5050ghz for those small tasks.

I've initiated a RMA case and i won't be getting any new cpu until january, we'll see what i do here, i am using this computer for my profession so it annoys the hell out of me that i somehow missed the fact that to stability test new computers you must also include idle, i never though this was a thing. I stresstested this thing for almost a 4 days straight before i decided to start moving my work over to it, and now this. Oh well... you live you learn.