DTM test failure "Driver - Disable Verifier"

I am facing two issues while running WLK 1.5 Unclassified Driver Reliability tests on Win7 64bit client:

Device Path Exerciser test case failures:

  1. Driver- Disable Verifier
    The Execute Task with Commandline

cmd /c verifier /reset

Failed with ExitCode 0

  1. Device - Ensure verifier mode and system mode
    The Execute Task with Commandline

cmd /c cscript.exe C:\WTT\JobsWorkingDir\Tasks\WTTJobRun17C4E2E6-7543-434A-AC84-281209A72BDB\9014D081-3393-4BE1-8B4A-BA1B31542BA2\script.vbs “”

Failed with ExitCode 1

I am using Windows 2003 Server as DTM controller, Win7 home premium 64-bit as DTM client, I installed WLK QFE 001 up to QFE 006, also installed the latest WLK filter dated 12/8/2010. Still have the same error.

I did run manually driver verifier disable and enable commands on the command line window, and the system reboots without problem.

Could any one please let me know how can I solve it? Very much appreciated any input.

xxxxx@yahoo.com wrote:

I am facing two issues while running WLK 1.5 Unclassified Driver Reliability tests on Win7 64bit client:

Device Path Exerciser test case failures:

  1. Driver- Disable Verifier
    The Execute Task with Commandline

cmd /c verifier /reset

Failed with ExitCode 0

  1. Device - Ensure verifier mode and system mode
    The Execute Task with Commandline

cmd /c cscript.exe C:\WTT\JobsWorkingDir\Tasks\WTTJobRun17C4E2E6-7543-434A-AC84-281209A72BDB\9014D081-3393-4BE1-8B4A-BA1B31542BA2\script.vbs “”

Failed with ExitCode 1

I am using Windows 2003 Server as DTM controller, Win7 home premium 64-bit as DTM client, I installed WLK QFE 001 up to QFE 006, also installed the latest WLK filter dated 12/8/2010. Still have the same error.

What kind of a driver is this? There was an errata issued on March 15
for an “Ensure verifier mode and system mode” failure. I don’t know if
it is the same problem or not. If it is the same issue, you can submit
the package with this failure and a note saying so. Perhaps you should
contact WHQL about it.

Did you see actually the machine reboot normally when this came up?


Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.

It’s a WinUSB based driver. I will check to see if the machine rebooted when the test failed.
What’s the WHQL contact information?
Thanks very much for your input.

xxxxx@yahoo.com wrote:

It’s a WinUSB based driver. I will check to see if the machine rebooted when the test failed.
What’s the WHQL contact information?

Do you already have a Winqual account for submitting your driver package?

If you go to http://winqual.microsoft.com, there’s a “contact us” page
with addresses.


Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.