Blue spinning pin wheel, program not responding?

As long as there is a recent Macrium backup image and a restore point you an use Windows driver verifer.
Please make sure that you understand the methods to turn of or recover from using the tool before using it.

I best go through that tonight and may not enable Driver Verifier until tomorrow.

I have briefly talked about my issues with my computer friend and mentioned the BSOD you picked out of the first log which was 0x124. He said that that is typically a voltage issue so I wonder if I have my voltage set too low at 1.280v for the 8700K at 4.9Ghz. Is this your understanding of that BSOD code?

zbook said:

After each BSOD in order to turn Windows driver verifier off or to recover you will use the Windows advanced troubleshooting menu. On the menu there will be 3 options to use and they should always be used in order. Advanced to the next step only if the prior method failed to turn off or recover from using the tool.
1) startup settings > click restart > select #6 enable safe mode with command prompt > type:
verifier /reset
2) command prompt > Administrator: X:\Windows\system32\cmd.exe > X:\Sources> type:
verifier /bootmode resetonbootfail
3) system restore
Often if system restore is clicked the dump file disappears so this method should be avoided as little progress is made in the troubleshooting.

Just to confirm, these are the Driver Verifier recovery steps correct? One thing that is not 100% clear, am I supposed to perform these recovery steps each time there is a BSOD?

The Windows driver verifier tool is designed to repetitively produce BSOD until misbehaving drivers are fixed.
Each time there is a BSOD you will see a BSOD window.
On the windows will be a and bugcheck. Sometimes there may be a misbehaving driver displayed in the form *.sys,
Each time you will need to reboot and open the Windows advanced troubleshooting menu and turn off the tool so that you can return to the desktop to fix the misbehaving driver.
The posts and the links explained the methods used to turn off the tool.
Once the tool is turned off you will fix the misbehaving driver and when ready you will restart the tool when you are ready to look for the next misbehaving driver.

How soon can Driver Verifier cause a driver to BSOD?

As soon as it is turned on.

Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community

Enable and Disable Driver Verifier in Windows 10 Windows 10 Tutorials

Where in this link does it show methods for turning off and recovering from the driver verifier tool?

BSOD Crashes and Debugging - Windows 10 Forums

See post #21 and #116

So if I can't boot back into Windows I will need to turn off Driver Verifier through Startup Recovery. If it does make back into Windows the easy option is to turn it off through Driver Verifier.

Let's look at this tomorrow (Sat), probably best do it with a fresh start to the day. :)

When the tool is working it should find misbehaving drivers and produce BSODs. It will repetitively produce BSOD until the tool is turned off or all misbehaving drivers have been fixed. Once all misbehaving drivers have been fixed the tool will be run for an additional 36 hours to see if there are any misbehaving drivers. Then the tool will be turned off this part of the troubleshooting will be completed.