HCT:: Fail in Device path exercise.

NTDEV
1

Dear All,
I have developed USB driver for my device.
While doing HCT my driver is failing in Device path exercise.
I am attaching the log file with this mail.
If I know what portion of my driver code is causing this error, I can
modify my code.

Thanks in Advance,
Regards,
S.

////********************* LOG FILE*****************////

**** NTLOG INITIATED +DATE+04/15/2005 +TIME+10:40:28
**** NtLog date: Thu Feb 17 11:07:23 2005
**** Exe date: Thu Feb 17 11:14:25 2005
**** Processor : Intel CPU, Pentium III (Coppermine core), stepping
3, 256K on-chip cache detected
**** CPUS : 1
**** System : Windows NT 5.1[2600], Retail, Mouse,
**** Build Lab : 2600.xpclient.010817-1148
**** Vid Driver: IntelGFX
**** Chip Type: Intel(R) 82810
**** DAC Type : Internal
**** Adapter : Unknown
**** MiniPort : Unknown
**** VRAM : 4096
**** Hertz : 85
**** X Res : 800
**** Y Res : 600
**** BPP : 24
**** Planes : 1
**** RGB Masks: NA
**** X Pos : 0
**** Y Pos : 0
**** Machine : X
**** User Name : Administrator
**** Language : English
**** KM boundary: 2
**** ProductOptions: None
Proc ID Proc.Name Wrkng.Set PagedPool NonPgdPl Pagefile
Commit Handles Threads UserObj GdiObj
0 Idle Process-> 20 0 0 0
0 0 1 N/A N/A
4 System-> 220 0 0 0
28 217 46 0 0
548 smss.exe-> 348 5 0 164
164 21 3 0 0
612 csrss.exe-> 2696 33 4 1296
1296 291 9 N/A N/A
636 winlogon.exe-> 3456 45 25 5432
5432 445 19 12 38
680 services.exe-> 2696 24 7 1380
1380 281 19 0 4
692 lsass.exe-> 848 36 7 3048
3048 295 20 0 4
864 svchost.exe-> 3356 34 7 1248
1248 221 8 0 4
956 svchost.exe-> 13308 81 30 9160
9160 975 66 5 10
1048 svchost.exe-> 2540 28 3 900
900 72 4 N/A N/A
1076 svchost.exe-> 3116 32 7 1176
1176 154 13 N/A N/A
1244 spoolsv.exe-> 3584 36 4 2620
2620 131 10 0 5
1504 explorer.exe-> 12988 52 8 7828
7828 253 12 85 164
1704 AutoSrv.exe-> 3620 35 5 2096
2096 131 5 1 5
1520 iexplore.exe-> 6284 54 10 5732
5732 307 12 97 203
288 wpabaln.exe-> 1792 28 2 508
508 44 1 4 11
1664 shrtver.exe-> 2556 29 2 2024
2024 28 1 26 24
1888 HCTReboot.exe-> 1788 20 2 1504
1504 60 2 1 4

****
****
680.6C0 : TestName: WHQL Driver Verifier Test - Version 2.0.5.7
680.6C0 : shrtver.exe /i dc2.ini /all /auto /f 0xFB /l devpath.log
/d “C:\WINDOWS\System32\Drivers\MYdrvr.sys” /net \server_ip\share
/rep “Enter path between quotes”
680.6C0 :
680.6C0 : Starting assertion 22.3.1
680.6C0 : Assertion Title: The driver under test must not blue screen
the system while running driver verifier.
680.6C0 : Description: Initializing driver verifier test
680.6D4 : +VAR+INFO 0 : Listing of drivers being verified
680.6D4 : +VAR+INFO 0 : Driver File: Mydrvr.sys
680.6D4 : +VAR+INFO 0 :
680.6C0 : +VAR+INFO 0 : System shutdown initiated
68C.690 :
68C.690 : Starting assertion 22.3.1
68C.690 : Assertion Title: The driver under test must not blue screen
the system while running driver verifier.
68C.690 : Description: Running tests under driver verifier
68C.694 : +VAR+INFO 0 :
68C.694 : +VAR+INFO 0 : Starting test Check NX
68C.694 : +VAR+INFO 0 : Test command line: nxcheck.exe /NX /l nxcheck.log
68C.694 : +VAR+INFO 0 : Starting test Check NX
68C.694 : +VAR+INFO 0 : Test command line: nxcheck.exe /NX /l nxcheck.log
68C.694 : +VAR+INFO 0 :
68C.694 : +VAR+INFO 0 : Check NX: 1 runs, test log(s) saved as dvsv001.log
68C.694 : +VAR+PASS 0 : Check NX completed successfully
68C.694 : +VAR+INFO 1 :
68C.694 : +VAR+INFO 1 : Starting test Check PAE
68C.694 : +VAR+INFO 1 : Test command line: nxcheck.exe /PAE
/FORCE /l paecheck.log
68C.694 : +VAR+INFO 1 : Starting test Check PAE
68C.694 : +VAR+INFO 1 : Test command line: nxcheck.exe /PAE
/FORCE /l paecheck.log
68C.694 : +VAR+INFO 1 :
68C.694 : +VAR+SEV2 1 : Check PAE reported an error in log file
D:\HCT\testbin\paecheck.log
68C.694 : +VAR+INFO 2 : Check PAE: 1 runs, test log(s) saved as dvsv002.log
68C.694 : +VAR+PASS 2 : Check PAE completed successfully
68C.694 : +VAR+INFO 3 :
68C.694 : +VAR+INFO 3 : Starting test Device Path Exerciser
68C.694 : +VAR+INFO 3 : Test command line: devpathexer /hct /dr “Mydrvr”
744.754 :
744.754 : Starting assertion 22.3.1
744.754 : Assertion Title: The driver under test must not blue screen
the system while running driver verifier.
744.754 : Description: Checking log for bugchecks and other driver
verifier failures
744.7A4 : +VAR+SEV2 0 : Test failed to complete last phase
744.7A4 : NTLOG REPORT -------------------------------------------------------
744.7A4 : Tests Total 0 | Variations Total 1
744.7A4 : ------------------------------------------------------------------
744.7A4 : Tests Passed 0 0% | Variations Passed 0 0%
744.7A4 : Tests Warned 0 0% | Variations Warned 0 0%
744.7A4 : Tests Failed sev3 0 0% | Variations Failed sev3 0 0%
744.7A4 : Tests Failed sev2 0 0% | Variations Failed sev2 1 100%
744.7A4 : Tests Failed sev1 0 0% | Variations Failed sev1 0 0%
744.7A4 : Tests Blocked 0 0% | Variations Blocked 0 0%
744.7A4 : Tests Aborted 0 0% | Variations Aborted 0 0%
744.7A4 : --------------------------------------------------------------------

/**** Time/Date/Name WrapUp ****/
HCT Version: 12.1.050216 Release
HCT Shell Date: Feb 16 2005 20:30:24
Test Kit: 58
Test Device: D:\HCT\universl.ini
Test Wrap-up Date: 4-15-2005
Test Wrap-up Time: 11:3:50
Test Name at Wrap-Up: Device Path Exerciser
/**** Time/Date/Name WrapUp ****/

2

mysub mysub wrote:

I have developed USB driver for my device.
While doing HCT my driver is failing in Device path exercise.
I am attaching the log file with this mail.

Well, you attached ONE of the log files. HCT is profligate in its log
file creation.

68C.694 : +VAR+INFO 1 :
68C.694 : +VAR+SEV2 1 : Check PAE reported an error in log file
D:\HCT\testbin\paecheck.log
68C.694 : +VAR+INFO 2 : Check PAE: 1 runs, test log(s) saved as dvsv002.log
68C.694 : +VAR+PASS 2 : Check PAE completed successfully
68C.694 : +VAR+INFO 3 :
68C.694 : +VAR+INFO 3 : Starting test Device Path Exerciser
68C.694 : +VAR+INFO 3 : Test command line: devpathexer /hct /dr “Mydrvr”

Note that second line. That’s where you need to get the detailed error
information. PAE is the Physical Address Extension that allows the use
of more than 4 GB of physical RAM. Are you creating any MDLs by hand in
your driver?

–

3

Tim Roberts wrote:

mysub mysub wrote:

> I have developed USB driver for my device.
> While doing HCT my driver is failing in Device path exercise.
> I am attaching the log file with this mail.
>

Well, you attached ONE of the log files. HCT is profligate in its log
file creation.

> 68C.694 : +VAR+INFO 1 : 68C.694 : +VAR+SEV2 1 : Check PAE
> reported an error in log file
> D:\HCT\testbin\paecheck.log
> 68C.694 : +VAR+INFO 2 : Check PAE: 1 runs, test log(s) saved as
> dvsv002.log
> 68C.694 : +VAR+PASS 2 : Check PAE completed successfully
> 68C.694 : +VAR+INFO 3 : 68C.694 : +VAR+INFO 3 : Starting
> test Device Path Exerciser
> 68C.694 : +VAR+INFO 3 : Test command line: devpathexer /hct /dr
> “Mydrvr”
>
>

Note that second line. That’s where you need to get the detailed
error information. PAE is the Physical Address Extension that allows
the use of more than 4 GB of physical RAM. Are you creating any MDLs
by hand in your driver?

When I saw this message, I realized that it became ambiguous after
Thunderbird decided to reformat it.

Check d:\hct\testbin\paecheck.log for the detailed information.

–