One compliant configuration passes another doesn't




I am currently testing a Virtual COM port device as a Universal Device
under HCT 11.2 for XP. The problem is that, while using two different
host controllers the test passes using one but not the other. The host
controller that the test fails under is a Intel 82801DB/DBM USB 2.0
Enhanced Host controller. The test fails under the Driver Verifier
test while running the Device Path Exerciser. It is not just this
machine either, our customer has an XP test machine they are running
under and it fails on there machine as well.

However, if I use an NEC USB 2.0 EHCI controller card on the PCI bus
the test passes no issue. My question is why would two different XP
compliant controller card behave differently testing the same device?


Gene Ziegler [MSFT]


Unfortunately, there are not enough details provided to indicate a cause for
failure. Provided the failure is not caused by Intel USB or NEC USB drivers
(WHQL recommends the Microsoft USB driver stack), you should be able to
debug Device Path Exerciser failures. Here are some WHQL recommendations:

For Device Path Exerciser test or Driver Verifier test issues, you can do a
couple of things to troubleshoot driver bugchecks:

1) For the most detailed instructions and step by step troubleshooting,
please refer to the HCT Help Docs section for the Device Path Exerciser test
titled "Device Path Exerciser Test: Troubleshooting Information"

2) These tests will detect all unsigned drivers on the test system. WHQL
recommends that you run device tests on a test system with a fully signed
build of the operating system. Furthermore, all extraneous devices should
be removed from the system or should have signed drivers installed. The
only unsigned driver(s) that should exist on the test system should be the
driver(s) for the device under test.
3) Please ensure that your test system is configured to issue a 'Complete
Memory Dump' when it encounters a bugcheck.
a) Right click My-Computer, select Properties.
b) Click the Advanced tab. Under 'Startup and Recovery' select Settings.
c) Under the 'Write debugging information' select 'Complete Memory Dump'
from the list.
d) Configure the 'Dump file' directory and 'Overwrite any existing file' to
suite your needs.

After your test system bugchecks during the test and reboots, find the
memory dump in the directory you configured and review it. This will
provide you with additional information regarding which driver bugchecked
and why. You can also elect to disable the 'Automatically restart' feature.
This will allow you to view the 'blue screen' error and disable the
automatic reboots.

4) Run the test with a debugger attached to the test system. You can find
information regarding Windows Debuggers here: After you determine
which driver bugchecks, you can use a 'checked build' of the driver and the
symbol files for the driver to obtain additional information. For
assistance with the Windows DDK or the Windows Debugging tools, please
contact DDK Developer Support:

5) Device Path Exerciser - there is a way you can run DPE against just your
driver service, for troubleshooting purposes only. You will need to have a
clean test system and submit test logs from the HCT test manager shell for a
Self-Test submission. For a Full-Test submission, you are not required to
submit logs as we will run a Full-Test pass here in our labs. The command
line syntax would be something like this: 'DC2.exe [switches] [/dr {driver
service name}]' without the quotes of course. Use DC2.exe /? for more
details. You should also enable Driver Verifier before running DC2.exe by
using the following instructions:
a) Click Run -> type 'verifier'
b) Choose Create custom settings (for code developers), Next
c) Choose Select individual settings from a full list, Next
d) Enable Special pool, Pool Tracking, Force IRQL checking, I/O
Verification, Enhanced I/O verification, Deadlock detection, DMA checking.
e) Choose Select driver name from a list, Next.
f) Check the box next to each and every one of your drivers to add them to
the list.
g) Reboot the system.
h) Run the DC2.exe syntax.

Gene Ziegler

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question