Blue spinning pin wheel, program not responding?

I've uninstalled the Logi gaming software and Logitech Gaming Virtual Bus Enumerator has been removed.

Will start a new Driver Verifier run soon.

All of my restore points were missing when I woke the computer from sleep today, is that a bad sign?

There should be a restore point when using Windows driver verifier.
Please create a new restore point.

I'm in Driver Verifier, no BSOD right at startup as with the Logi driver..

M-MAXIMUSXHERO (2018-04-09 14 28).zip

Nice.
So far there have been 3 misbehaving drivers identified.
1) Malwarebytes driver
2) Logitech keyboard: Lgbusunum
3) Nvidia GPU drivers

There were 2 bugchecks: 7E and WHEA 0x124
The WHEA 0x124 was reported in the logs however there has been no mini dump or memory dump displaying WHEA 0x124.

If WHEA 0x124 occurs the next steps will be to test the CPU and GPU.

If there are no BSOD running Windows driver verifier for an additional 36 hours (continuous) then you can turn off Windows driver verifier and that will complete the troubleshooting using the tool.

A support ticket needs to be submitted to Logitech to find a replacement driver.

For Malwarebytes a follow up needs to be done this week for the prior support request (Malwarebytes registry remnants after using the Malwarebytes uninstall tool)

For the rotating blue circle if it still is problematic then after the completion of Windows driver verifier place the computer in clean boot. Report into the thread the impact of clean boot on the blue circle duration and frequency in clean boot in comparison to normal boot.

Please do not use clean boot while continuing the Windows driver verifier testing. Only use it after the testing has completed.
Perform a Clean Boot in Windows 10 to Troubleshoot Software Conflicts Windows 10 Tutorials

Unfortunately Malwarebyte's have not replied to my support ticket. I'm going to raise the issue on the forum.

Perhaps we will need to see if WHEA 0x124 occurs once overclocking has been enabled again...

There are multiple reports of LGBusEnum.sys causing BSoD at the Logi forum. I need to sift through more threads to find a solution.

Are you sure the Malwarebyte's log indicates that the tool has failed to clean any remaining MB files?

mb-clean-results.txt

They will interpret the results.
If the cannot delete are okay then there is nothing to do.
If the cannot delete means that there is something to do they should be able to communicate that in the customer support.

A Malwarebyte's staff member has replied to my thread and said the log's imply all of the files are gone. He said what made you think there were any leftover?

That's great news.
So with 2 weeks of no BSOD you can reinstall the software.
When you reinstall any of the software please skip a day or two so that if there is a recurrent BSOD there is a cause and effect related to the reinstall.

Now its customer support to find a driver for the Logitech keyboard that does not BSOD.