Get yourself back to square 1. Go into BIOS and load Optimized defaults
First of all, your Machine check is a Hardware error, so stop messing with Software. The only thing you should look into with the Software is Windows Power Management policy, and make sure that Maximum Processor state and Minimum processor state is normal (Max-100) (Min 10-15%)
Machine check is a phrase that has been used for decades in Data processing. It does Not mean that your processor chip is broken. It does mean that somehow, it was told to do something it could not. For example (Divide by zero, Execute the next instruction but the data at that location is garbage and it doesn't form an instruction, Grab a piece of data at a location this task does not own, store some data at location 84 billion but there is no Ram covering that address, Add the number 458 to the number "Cow".
The voltage range, along with the corresponding frequencies is the normal culprit for these crashes. Having these specified incorrectly lead to data corruption. If you look at all they examples of Machine check that I laid out, you will notice that they are in one form or another, data corruption. Most times machine checks come from Data Corruption. Why people don't use Error Correcting memory is beyond me I guess they would rather run fast than reliable.
So Stop overclocking your DIMMs along with the Internal Memory controller. Your Memory should be brought down to 3200MHz.
Yes your Memory might be able to support that speed, but the internal Memory controller in the Ryzen Processor is only spec'd for 3200MHz (in the best case!) (I see that you are running DTX, so its good you are not trying to cram in 4 sticks)
The faster you run your Memory, the less time it has to store and retrieve the information. The fewer wait states the you give your memory, the less time you have to store and retrieve the information. The faster you run the cores, the less time the memory subsystem has. This is very much like the game "hide and go seek". You remember the phrase in that game? After counting down its "ready or not here I come"! Two parties (working somewhat independently) have an agreed amount of time to complete a task, if the memory isn't ready in time (we all lose).
People just overlook the clue that one of these type of errors is specifically mentioning "Cache Hierarchy", and the other error is resulting from some sort of corruption.
================= Recommendations:
You mentioned that your system crashes while idle after some load. When the processor goes idle, it will reduce it's frequency, and also down volt itself. However, this minute amount of voltage might not be enough when the silicon is hot. Remember it takes more voltage to push current through a hot chip than a cold one.
For this case, lets increase the voltage to the cores and the internal memory controller by the smallest amount possible. Change VCore from Auto to Normal. A displacement field should open up, set it to +0.006 Likewise change VSoc from Auto to Normal. Another displacement field should open up. Set the displacement to +0.006 A little goes a long way.
Doing the above keeps the same Voltage curve as Auto, but it increases the Low end and the High end of the curve by 0.006 V
We were not looking to increase the high end, as the high voltages are enticing the system to use higher frequencies that the internal memory controller can not handle.
So: We will cut back on the Power(PPT) to discourage the system from using the Highest frequencies.
Set PBO to advanced.
Set Limits to Manual
Set PPT down from 142 to 120 (watts)
==========================
If you want, some people have problems with Temperature. Don't mess with Voltages to try to get temps under control.
It is better to have Ryzen control the Temps.
(The following is optional)
Set Thermal Limit to Manual.
In the new field that opens up ("Thermal Limit") set it to what you consider a decent value in Cesius (I like 70)
=======================
Making the changes above, should have resulted in a system that raises the floor just a bit, pushes the ceiling down a bit and runs more reliably and cooler.
