Jeff Wouters's Blog

As I repeated several times in my last post, it is adviced to remove the configuration you’ve put into Driver Verifier when you are done troubleshooting.

That’s why I write this post in order to show you howto “clean you’re shit when you’re done”.
Trust me on this one, the end-users will thank you later. Especially on Terminal Servers if Driver Verifier has been fully configured…

Alright… here we go:

The Driver Verifier can be found at %windir%\system32\verifier.exe
You’ll momentarily see a Command Prompt window and then the Driver Verifier Manager will launch and display wizard-like GUI:

When selecting the “Delete existing settings” option, beware that ALL configurations you have made in Driver Verifier will be removed. So if you’ve created some previous configurations in it they will also be deleted, not just the ones you’ve put in the last time.
So perhaps you will want to configure those settings back when you’ve done.
But as I explained in my previous post, it is recommended to only configure Driver Verifier when needed and not just to get some more information in a MemoryDump just in case you get a BSOD.

Why? Performance loss!!
I just feel that I can’t mention it enough, but configuring Driver Verifier will create some performance loss.
Yes, even with custom settings, I shall explain those in future posts. It will not be much of a performance loss with custom settings, but still I would think you would make full use of your resources.

Back to the screen from Driver Verifier.
Click on “Finish”.

Next you will see this popup:

Now this is just a “Are you very sure you want to do this”-popup.

Click “Yes”, reboot the system and you’re done!