Is it possible to get a memory dump from event viewer?

So on the 18th I was playing Rust and got a System Service Exception BSOD. It happened again on the 25th when I purchased and started playing Sense.

Long story short me and my friends think I have a bum memory controller and in turn it is bricking my RAM. So to be sure I am RMA'ing the Mobo, RAM, CPU, and PSU this should fix the issue hardware side.

During the course of trying to troubleshoot this issue I've gotten a couple of System Service Exception BSODs and one Paged fault in nonpaged area BSOD (I believe that was the exact wording) here's my current problem. The most recent BSOD overwrote the original BSOD so I no longer have it. I can RMA everything and reassemble the system but I need the original BSOD info before I can troubleshoot it. I know Windows sends a report to Event Viewer when a BSOD occurs. Is there anyway to get another memory dump from event viewer for the now overwritten dump?

I can't post Windows version number because I can't get into Windows on the Problem PC, I have it half taken apart due to preparing to RMA hardware, and I don't remember off hand as I never thought much of it. But I can tell you I was fanatical about keeping Windows and it's components upgraded So whatever was the latest version up to August 18, 2020 should be it.

I gotta wait till I get my PC parts back and reassemble it. Is there anyway to make Windows create dumps in the minilog folder where the dumps filenames are timestamps?

The original BSOD was a System Service Exception... It didn't list a driver on the BSOD screen itself and I couldn't stay in Windows long enough to move the original dump file... *Sigh* I hope replacing the hardware fixes the issue then. Since it seems I can't troubleshoot it.

Can I ask a question why doesn't Windows put the dump in the old minidump folder where the filenames are timestamps? It would be much more convenient.

EDIT: Assuming it created the event viewer entry like it should have. Is there any chance the report for the original BSOD would list the module where the fault occurred? That's all I really want to so I can see what was happening when the issue occurred.

Ok I'll set it for small memory dumps when I put the PC together.

Just curious if I had a faulty CPU or memory controller like my friends think could that trigger a System Service Exception and Paged Fault in Nonpaged Area? I'm just trying to connect all the dots. I know a bad CPU or Mem controller can brick RAM but can it explain the BSODs I encountered. At the time of the first BSOD on the 18th I had not installed any new drivers recently. It just happened while playing Rust as if playing the game somehow uncovered an unknown, hidden issue.