BSOD - Gaming PC is getting old  

Please run driver verifier using the following settings for 48 hours.

• I/O Verification
• IRP Logging

Warning: driver verifier could cause boot issues and/or performance issues.

• Make sure that you have recovery media, if needed you can create it.
• Configure a restore point prior enabling driver verifier.

Resetting driver verifier options (recommended in this order)

1. In normal mode open an administrator command prompt and enter the below command
2. In safe mode open an administrator command prompt and enter the below command
3. On 3 boot failures, you'll boot automatically to the recovery options,
   
   • click Troubleshoot
   • go to the advanced options
   • choose command prompt
   • enter the below command
   
   
4. Boot with the recovery media, see above 4 steps in option 3.
5. Via the recovery options or recovery media, select a restore point prior enabling driver verifier

Code:

verifier /reset

Crashed when running driver verifier

1. Reset driver verifier
2. Boot in normal mode if necessary
3. Follow Blue Screen of Death (BSOD) Posting Instructions to provide the requested logs

Extra information about driver verifier
When you run driver verifier, there are two things you're looking out for
1. Driver verifier won't find any driver violating something and thus in the time you need to run it there won't be a crash
2. Driver verifier will find a driver violating something and thus the system will crash.

The end result of driver verifier is either of the two, but when driver verifier finds something your system will BSOD.


Driver verifier essentially validates selected drivers on selected actions, this validation adds some delay to actions performed in the background which results in a performance decrease that many people notice. This is called stress testing drivers and depending on quite a few factors this performance decrease is worse for some than for others, and some won't even notice a difference.

Depending on the drivers selected, it is possible that some of the selected drivers are so-called 'boot' drivers, meaning they load when your system is booting. If these drivers don't pass a validation check, your system will crash, but since the drivers are loading at boot, your system will basically be in a boot loop. That is one of the risks involved and the most important one. Of course, there are various methods to recover from it.

If you want visual confirmation that driver verifier is actually running, copy/paste the following command in powershell or command prompt

Code:

verifier /query

If the command gives a result similar to this, it means driver verifier is running.

Driver verifier is running properly yes.

Please be aware, any sluggishness may not start immediately but could start to occur whilst working or gaming for example, it's completely normal with driver verifier enabled.

tbone3969 said:

Got it. Thanks. So the idea here is to see if it crashes while running this verifier and if it does there will be a log to help diagnose the issue?

Unlike what many might be used to from other programs, driver verifier doesn't create any logs besides a dump file.
If driver verifier catches a driver doing something bad, driver verifier will crash the system with a BSOD and a dump will be generated. Nothing else will be done, i.e. no text file will be generated of what driver verifier did.

From the screencapture image, the 0x9F with parameter 1 =3 suggests the problem is a 3rd party driver. You need to upload the .dmp file so someone can analyse it further to see if they can determine which driver is at fault.

I also suggest following the steps posted in post #6.