BSOD Attempted switch from DPC & KMODE exception not handled on Win10

Hi,
I have since a couple of days constant issues with BSOD's on my Win10 (1809) System, most of the time "Attempted switch from DPC", but sometimes also "KMODE exception not handled"

The strange thing is that I didn't really change something on the system!?
I already tried to uninstall the tipical candidates, like an old Acronis TrueImage Version and also my Norton AntiVirus Package, but no luck. Updated the Graphics driver and removed some unneccary old programms. I also tried to restore some previous SystemRecoverypoint, but that crashed as well (even when booting from WIN10 DVD, this resulted in the Recoverypoint being gone now as the system said it was corupted). In the meantime with all the crashes my Windows Office installation is also ruined and a reinstallation failes because I always get another BSOD whilse installing...

I also checked my SSD for Firmware etc, all fine accoring to the provided tool.
I even tried to kill nearly all non-windows programms running in taskmanager details, but that didn't prevent the BSOD either...

So I hope someone here has an idea how to fix this!?
Unfortunately when I ran the forum script I saw that there is no Dump written in the Drive!
I attached the Zip file as instruced, so I hope I provided all details necessary?

Thanks for the quick reply, I will try to run this driver verfifier, but so far I was not successfull as the system crashes often even before I can start to do the setup
There was so far no specific point where it crashed, sometimes before even entering the singon pw, sometimes after some minutes.
With both BSOD messages sometimes one sometimes the other...

PS: Restore a previous Restore-point was also not successful, I tried at least 10 times, with Boot from DVD as well as out of the system... no success...

Now I finally made it, but now when booting I straigt get the BSOD Driver Verifier Detected Violation
Any ideas?
Does it make sense to run the logs again even if I didn't reach login?

Yes, I tried via running the verifier application and selecting "delete settings" and also via the reset command on command line and also the command in the linked post (/bootmode resetonbootfail). But I still keep getting the mentioned Verifier BSOD, I'm currently trying to run the restore-point restore out of the troubleshoot-bootup . Lets hope that one works...

Ok, that one worked, so I'm back to the previous situation (before trying verifier).
Did that kill the logs as well or can I still run the script?

Ahh... Now I'm not able to get in anymore.. I get another BSOD "Critical Process died", even when I start in save mode

Additional info:
As I also have an old Win7 installation on the PC which I checked now and it's running ok, so I expect the whole story not be some hardware related error.

As I don't reach desktop in any mode (safe mode or debugging mode) I will try to install win10 from DVD again "over" the existing installation...