I am currently doing the tests using the driver verifier using the settings mentioned in the above post. Will keep you updated.
I also uninstalled ESET. I never thought that it has it is own drivers. I guess you learn something new every day.
Should I try playing the game now, since it is the core cause for the blue screens? Or should I let the driver verifier do its thing?
For Windows verifier if there are no BSOD then increase the number of custom tests.
Add 2 to 4 customized tests every 2 hours to use the same customized tests in this link (approximately 19):
Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community
In the image in the above link you can see multiple ESET drivers.
As long as there are no significant boot or sluggishness problems you can run all customized tests (Don't run DDI or random low resource simulation)
If there are boot or sluggishness problems then you can add some and remove some so that you have all of the non-Microsoft drivers tested with the different tests.
Always maintain the minimum 3 customized tests in this link:
Enable and Disable Driver Verifier in Windows 10 Windows 10 Tutorials
I have been testing the whole week and I had no blue screens.
What should I do next?
In general Windows driver verifier is used for 48 hours with the 19 customized tests and then an additional 36 hours.
Were you able to increase the number of customized tests? Were they all able to run simultaneously?
If there are no more BSOD then the tool is turned off.
Post a new zip into the thread:
log collector v2-beta08.zip > extract > open > post
Here are the logs.
Over course of the week I tried all the customized test as suggested in the links posted.
1) In the left lower corner search type system > open system control panel > on the left pane click advanced system settings > under startup and recovery click settings > view the startup and recovery window and post an image into the thread
2) Open whocrashed > above analyze > click tools > crash dump test > type: ACCEPT
3) Click analyze > post whocrashed results into the thread
4) Run the beta log collector > post a new zip into the thread
5) open file explorer > this PC > C: > in the right upper corner search for:
a) C:\windows\memory.dmp > zip > post link into the thread
b) livekernelreports > look for any dump files > post links into the thread
Quote