When should I disable driver verifier If I don't get a BSOD?

shadybk

Distinguished
Dec 23, 2015
150
1
18,685
I have another post where people are helping me with BSODs on my gaming pc whenever I play games and they suggested I run driver verifier and send them the two more bsod minidump files. My question is once I enable driver verifier how long should I wait to disable it? If I don't get a bsod within the first 1 hour of it running should I turn it off and assume my drivers are not the problem since when playing games I always get the bsod within the first 15 minutes.

One more questions, they recommend that I turn off auto restart when I get a bsod, but if I do get a bsod with auto restart disabled how would I boot up again during a bsod? would I just press and hold the power button on the pc?

thanks in advance!!!
 
Solution
the simple problems verifier tends to find on bootup or in a hour or two but I have seen verifier find problems hours later when tasks in the task scheduler were run hours after the machine booted, or 4 hours after the machine went to sleep and hibernation kicked in, or when the machine tried to wake. It just depends on the problem.

driver verifier will help find certain kinds of programming mistakes in drivers but it can mask certain types of errors also.
depending on the type of problem you are having, you want to run verifier and change the memory dump type to kernel memory dump. Otherwise the debugging info is just not saved when the system bugchecks.
verifier will cause your system to run slower and use more memory but used...
Hi,

I wouldn't use driver verifier at all. I use "BlueScreenView" for a similar issue and it records the error code and driver responsible every BSOD.

http://www.nirsoft.net/utils/blue_screen_view.html

I can even launch Google to search for the appropriate error or error with driver issue (makes sense) from within the program for the exact error without typing. I have this program linked to my W10 Start Menu.

Other:
I assume people recommended running Memtest86 but I'll link it www.memtest86.com
 
the simple problems verifier tends to find on bootup or in a hour or two but I have seen verifier find problems hours later when tasks in the task scheduler were run hours after the machine booted, or 4 hours after the machine went to sleep and hibernation kicked in, or when the machine tried to wake. It just depends on the problem.

driver verifier will help find certain kinds of programming mistakes in drivers but it can mask certain types of errors also.
depending on the type of problem you are having, you want to run verifier and change the memory dump type to kernel memory dump. Otherwise the debugging info is just not saved when the system bugchecks.
verifier will cause your system to run slower and use more memory but used in conjunction with the kernel memory dump it makes it much easier to debug.

verifier can change the timing on how things are run so it can make finding timing related problem harder to reproduce.
in these cases it is better to provide a kernel memory dump and turn off verifier.

also, kernel memory dumps are required to figure out a lot of problems, like: a processor that is not responding, USB problems, plug and play problems.
 
Solution