It doesn't 100% verify what I think happens, I thought that the BSOD happened at the beginning or the end, but as there is no driver flagged in the dump we'll need to run driver verifier. Most other usual causes are ruled out so that is a good sign
Please follow below instructions.
Please follow this tutorial to 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.
NoteYour 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.
- Memory corruption,
- Hardware (memory in particular),
- Overclocking failure,
- Installing a faulty or mismatched hardware (especially memory) or a failure after installing it,
- 3rd party firewall,
- Device drivers,
- SCSI/network/BIOS updates needed,
- Improperly seated cards,
- Incompatible storage devices,
- Virus scanner,
- Backup tool,
- Bad motherboard,
- Missing Service Pack