BSOD ntoskrnl.exe

Didn't bother with the Macrum backup image since their was a disclaimer that it would not turn off driver verifier. So there was no difference between it and a system restore.
Executing verifier /bootmode resetonbootfail changed the verifier mode from persistent to reset on bootfail, but that did not stick. System would still hang on the spinning circle on startup and the mode was changed back to persistent.
The only difference between this run with driver verifier and my first run was I only selected my display drivers on the first run.
The SSD wipe worked and Windows 10 is installed and running. I've asked on another forum which drivers I should and should not install for my specific machine. Hopefully that will narrow down the misbehaving driver(s).

At this time do not install any drivers and see if the computer is stable or unstable with windows installed default drivers.
Then if there is a day of stability with typical computer use install two to three drivers.
The settings for windows driver verifier can be customized when there are many drives installed.
When there are just a few drivers installed turn on windows driver verifier and test these newly installed drivers.
If there are no BSOD then continue installing drivers.
Repeat checking the drivers each time there are two to three new drivers.
If there are BSOD then you may know the problematic driver as it may be among the last two to three drivers that were installed.
Any time there is a BSOD > post a new BETA log collector zip and memory.dmp

Can I install new drivers with verifier turned on? And each time I install drivers, I will need to go in and update the driver verifier list list, yes?

The driver is not likely to appear in the list. So the driver(s) need to be added first then check the boxes.
If there are no BSOD then check more drivers.
If the system becomes too sluggish or the boots too slow then you can uncheck the earliest non-Microsoft driver(s) installed.

What about the Microsoft update installed drivers for my graphics cards? Update automatically applied drivers for my Intel and Nvidia GPUs. Should I start with this drivers for verification?

Windows may install non-Microsoft drivers. These should be tested with Windows driver verifier.
At sometime you can also perform windows updates and see if there are problematic drivers after an update.

Welp, Driver verifier has been on for one night for all non-Microsoft driver and no issues or lagging. I am confused about one thing. The first link you posted to use driver verifier said to check all settings except DDI compliance checking and randomized low resource simulation. The 2nd link you posted said to only check I/O Verification, Force pending I/O requests, and IRP logging. Should I have all settings but DDF and RLRS enabled or only the other 3?

For the instructions there was one link for the settings and the other link for the methods to turn off or recover from using the tool.
This is the link for the customized settings:
Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community

According to the dump files your CPU's integrated memory controller is overclocked at DDR4-2400. The highest setting officially supported by Intel for your CPU is DDR4-2133. Does your motherboard's BIOS allow you to set the memory to run at DDR4-2133? If so, I'd recommend doing so and testing the system to see if the problems continue.

Also, in my experience, there is no reliable software diagnostic for testing DDR4 memory. The most reliable method has been to use the system as you normally would but with only 1 DIMM installed (for each DIMM) to try and separate the bad from the good DIMMs. I've lost count of how many times I've seen memtest86 and Windows Memory Diagnostic say DDR4 memory is good only to find out in the end the system had a bad DIMM.

zbook said:

For the instructions there was one link for the settings and the other link for the methods to turn off or recover from using the tool.
This is the link for the customized settings:
Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community

So all setting except DDI compliance checking and randomized low resource simulation?

cwsink said:

According to the dump files your CPU's integrated memory controller is overclocked at DDR4-2400. The highest setting officially supported by Intel for your CPU is DDR4-2133. Does your motherboard's BIOS allow you to set the memory to run at DDR4-2133? If so, I'd recommend doing so and testing the system to see if the problems continue.

Also, in my experience, there is no reliable software diagnostic for testing DDR4 memory. The most reliable method has been to use the system as you normally would but with only 1 DIMM installed (for each DIMM) to try and separate the bad from the good DIMMs. I've lost count of how many times I've seen memtest86 and Windows Memory Diagnostic say DDR4 memory is good only to find out in the end the system had a bad DIMM.

RAM came with my system. I know it is not the Dell system memory. The previous owner swore he had no issues with this rig. I will have to look in the BIOS to see if I can reduce the memory clock.