Hi,
I have a softare-only driver. Its a root enumerated function driver(WDM
Driver). It has been written on framework provided by driverworks. My aim is
to apply for WHQL for that I am doing DTM testing for this driver under
unclassified category. This driver is getting failed in “Device Path
Exerciser” test. The system gets crashed while doing “Device Path Exerciser
Test”. Datails of memory dump is:
Microsoft (R) Windows Debugger Version 6.7.0005.1
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Documents and
settings\Nagesh_Kumar\Desktop\crashdump\12dec\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available
Symbol search path is: SRV*C:\WINDOWS\Symbols*
http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Vista Kernel Version 6000 UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6000.16575.x86fre.vista_gdr.071009-1548
Kernel base = 0x81c00000 PsLoadedModuleList = 0x81d08ad0
Debug session time: Fri Dec 14 10:34:15.546 2007 (GMT+5)
System Uptime: 0 days 0:00:18.093
Loading Kernel Symbols
…
Loading User Symbols
*******************************************************************************
*
*
* Bugcheck
Analysis *
*
*
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck C9, {22f, 89510c10, 87d34f20, 0}
*** ERROR: Module load completed but symbols could not be loaded for
CryptOSD.sys
Probably caused by : CryptOSD.sys ( CryptOSD+9c10 )
Followup: MachineOwner
kd> !analyze -v
*******************************************************************************
*
*
* Bugcheck
Analysis *
*
*
*******************************************************************************
DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
The IO manager has caught a misbehaving driver.
Arguments:
Arg1: 0000022f, (Non-fatal error) The caller has completed an untouched
IRP_MJ_PNP (instead of
passing the IRP down), or non-PDO has failed the IRP using illegal value of
STATUS_NOT_SUPPORTED. (IRP specified.)
Arg2: 89510c10
Arg3: 87d34f20
Arg4: 00000000
Debugging Details:
ERROR_CODE: (NTSTATUS) 0xc9 - The operating system cannot run %1.
BUGCHECK_STR: 0xc9_22f
DRIVER_VERIFIER_IO_VIOLATION_TYPE: 22f
FAULTING_IP:
CryptOSD+9c10
89510c10 55 push ebp
IRP_ADDRESS: 87d34f20
DEVICE_OBJECT: 84cf3030
DRIVER_OBJECT: 84ce2040
IMAGE_NAME: CryptOSD.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4761451e
MODULE_NAME: CryptOSD
FAULTING_MODULE: 89507000 CryptOSD
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 2
LOCK_ADDRESS: 81d24ac0 – (!locks 81d24ac0)
Resource @ nt!PiEngineLock (0x81d24ac0) Exclusively owned
Threads: 832b8020-01<*>
1 total locks, 1 locks currently held
PNP_TRIAGE:
Lock address : 0x81d24ac0
Thread Count : 1
Thread address: 0x832b8020
Thread wait : 0x486
LAST_CONTROL_TRANSFER: from 81eca6fb to 81cacf57
STACK_TEXT:
855a80e4 81eca6fb 0000004c 000000c9 855a8104 nt!KeBugCheckEx+0x1e
855a826c 81eca293 00000000 84cbe7e8 87d34f20 nt!ViBugcheckHalt+0xb0
855a8510 81eca1a4 0000022f 855a8520 855a8608
nt!VfBugcheckThrowException+0xd9
855a85f0 81ed2ae8 0000022f 00000009 89510c10
nt!VfBugcheckThrowIoException+0x11b
855a8624 81ecd6cf 84cf3f98 84cf3f98 00000001
nt!VfPnpVerifyIrpStackUpward+0xda
855a863c 81ecb839 84cbe7e8 00000001 00000001
nt!VfMajorVerifyIrpStackUpward+0x3c
855a8678 81ec2c10 87d34f20 855a86f4 87d34fdb nt!IovpCompleteRequest2+0xb2
855a86a8 81c34ae0 00000000 87d34f20 855a8714
nt!IovpLocalCompletionRoutine+0x73
855a86dc 81ec2b53 87d34f20 84cf3030 84b57978 nt!IopfCompleteRequest+0x12d
855a874c 89512d0a 855a8790 84cf30e8 855a8788 nt!IovCompleteRequest+0x11c
WARNING: Stack unwind information not available. Following frames may be
wrong.
855a875c 895115f9 c00000bb 00000000 84cf30e8 CryptOSD+0xbd0a
855a8788 8952102f 87d34f20 ffffffff ffffffff CryptOSD+0xa5f9
855a87e4 8951f93f 87d34f20 ffffffff ffffffff CryptOSD+0x1a02f
855a881c 89510c65 87d34f20 81ecabf6 87d34f20 CryptOSD+0x1893f
855a8830 81ec2681 84cf3030 87d34f20 855a88c8 CryptOSD+0x9c65
855a8854 81c67b80 81d37499 00000000 84cf3030 nt!IovCallDriver+0x252
855a8868 81d37499 00000000 855a8988 8325a5d0 nt!IofCallDriver+0x1b
855a88f4 81ec6ee1 8325a5d0 855a8990 855a8988 nt!IoGetDmaAdapter+0x110
855a8924 8951095e 8325a5d0 855a8990 855a8988 nt!VfGetDmaAdapter+0x78
855a89bc 89510bcb 8325a5d0 0030002e 81f09124 CryptOSD+0x995e
855a89d0 81c0f3e2 84ce2040 8325a5d0 8325a448 CryptOSD+0x9bcb
855a89ec 81d5cab7 84ce2040 89510bb0 00000004 nt!PpvUtilCallAddDevice+0x4a
855a8a14 81d5887b 84ce2040 89510bb0 00000002 nt!PnpCallAddDevice+0x77
855a8af0 81d5dd0e 02000000 00000000 81d23d30 nt!PipCallDriverAddDevice+0x46d
855a8cec 81c0f74a 832519b8 84b86898 855a8d38 nt!PipProcessDevNodeTree+0x157
855a8d44 81c6b7aa 00000000 00000000 832b8020 nt!PnpDeviceActionWorker+0x21b
855a8d7c 81dafbad 00000000 855a3680 00000000 nt!ExpWorkerThread+0xfd
855a8dc0 81c9a346 81c6b6ad 00000001 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
CryptOSD+9c10
89510c10 55 push ebp
SYMBOL_NAME: CryptOSD+9c10
FOLLOWUP_NAME: MachineOwner
FAILURE_BUCKET_ID: 0xc9_22f_VRF_CryptOSD+9c10
BUCKET_ID: 0xc9_22f_VRF_CryptOSD+9c10
Followup: MachineOwner
kd> !irp 87d34f20
Irp is active with 3 stacks 4 is current (= 0x87d34ffc)
No Mdl: No System Buffer: Thread 832b8020: Irp is completed.
cmd flg cl Device File Completion-Context
[0, 0] 0 2 00000000 00000000 00000000-00000000
Args: 00000000 00000000 00000000 c00000bb
[0, 0] 0 10 00000000 00000000 00000000-00000000
Args: 00000000 00000000 00000000 00000000
[1b, 8] 0 2 84cf3030 00000000 00000000-00000000
\Driver\CryptOSD
Args: 81c52088 00010020 855a88a8 00000000
kd> !irp 89510c10
IRP signature does not match, probably not an IRP
kd> !devobj ffffffff84cf3030 f
Device object (84cf3030) is for:
CryptOSDDevice0 \Driver\CryptOSD DriverObject 84ce2040
Current Irp 00000000 RefCount 0 Type 00000022 Flags 000000d0
Dacl 86060830 DevExt 84cf30e8 DevObjExt 84cf3320
ExtensionFlags (0xc0000810) DOE_START_PENDING, DOE_BOTTOM_OF_FDO_STACK,
DOE_DESIGNATED_FDO
Unknown flags 0x00000800
AttachedTo (Lower) 84cef7c8 \DRIVER\VERIFIER_FILTER
Device queue is not busy.
Please suggest me where I am going wrong.
–
Regards,
Nag