BSOD with no consistency

Are those dumps in the zip the dumps of all crashes you had since RMA'ing the motherboard?
If not, please provide all dumps, preferably by using the beta log collector from the posting instructions.

Thanks for providing the logs.
I checked the eventlog, in the past month 5 crashes occured which are mostly different. 1 I can't recall to have ever seen before which indicates that software used to run virtual machines had crashed, i.e. the built-in virtualization software crashed for example. There is unfortunately very little information about it as it one of many that rarely occur (if ever).
Strangely enough, your system doesn't really want to keep information either.

Code:

2019-01-19T06:18:29.423		The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000003b (0x00000000c0000005, 0xfffff804be532c63, 0xffffef046d14ebb0, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 733daa90-5b01-405b-987f-f613e83c4a34.
2019-01-19T06:18:07.691		Dump file creation failed due to error during dump creation.
2019-01-16T03:53:50.596		The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000ef (0xffffa20865a82540, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 59300755-ed6c-46c2-b026-884573744820.
2019-01-16T03:53:29.982		Dump file creation failed due to error during dump creation.
2019-01-07T01:03:36.116		The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000003b (0x00000000c0000005, 0xfffff8066504f0fd, 0xffffd80a2f591f00, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 2128318a-8183-40bf-8a63-500826af8616.
2019-01-07T01:03:16.621		Dump file creation failed due to error during dump creation.
2018-12-27T08:48:50.246		The computer has rebooted from a bugcheck.  The bugcheck was: 0x00020001 (0x0000000000000026, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 7803c6c2-f2d7-4f3b-8481-dbae3d7788db.
2018-12-27T08:48:28.139		Dump file creation failed due to error during dump creation.
2018-12-25T03:17:52.372		The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000050 (0xffffe9006a20d6e4, 0x0000000000000002, 0xfffff8073a40d91d, 0x0000000000000002). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: b8cdc734-fdd6-44db-8739-021d8ee4023f.
2018-12-25T03:17:32.902		Dump file creation failed due to error during dump creation.

Considering the possibility that a replacement may be faulty, have you done any hardware tests/checks to find this out after you received the replacement?

The latest is a 0xEF or a critical process died which implies that a process Windows can't live without had to shutdown to prevent any issues. Windows marks some processes as critical that it can't live without, if the file is being replaced or the process is somehow being manipulated, the process will shutdown. Unfortunately this is one of the few exceptions where a usermode problem causes a crash, as a protection mechanism Windows goes into kernel mode to be able to shut everything down, but because it all happened in user mode and memory dumps are usually configured to only save kernel mode information I don't think a memory dump will be of much use.

Could you answer my question in my previous post please.

badconduct said:

Not since replacing, no. I RMA'd just the motherboard. Haven't done any memory tests.
I'll have to do another memory check. It's considerably less frequent than the original BSOD errors, and I have not reinstalled Windows, which I may do.

I recommend this. It may very well fix the problem