Hi Slarty,
Welcome to the 10blog.
It seems there are 3 windows drivers blamed in the crashes.
Because windows drivers are rarely the real cause I want to try a few things
First we need to be sure there is no corruption, missing files or other problems with the system files.
Please do the following:
- Open an admin command prompt
- Copy/paste "sfc/scannow" (without quotes) and press enter
- When it finished reboot your system
- Open again an admin command prompt
- Enter sfc/scannow again
If sfc/scannow does NOT say"Windows Resource Protection did not find any integrity violation", please upload the cbs.log file located at {windows partition}WindowsLogsCBS, if the file is too large try a 3rd party uploader like dropbox, onedrive, google drive, mediafire etc.
System File Check(SFC a.k.a. Windows Resource Protection) needs to have your system rebooted in order for sfc to try to fix the problems that it finds.
If sfc fixes the problem, then driver verifier may be ignored.
Diagnostic Test
DRIVER VERIFIER
Warning
Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.
Please follow this tutorialto run driver verifier.
Some windows drivers are blamed in a few crashes, but that usually means that a 3rd party driver is actually the cause.
Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.
Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.
If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.
Note
Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.
