wdftester bugcheck

NTDEV
1

Hi All,

I got a bug check when I was testing with my wdf driver with WdfTester. The crash dump shows the crash due to a DbgPrint in wdftester. Somebody please help me with some suggestions as to what could be the reason?

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 86e00265, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 82a99b1e, address which referenced memory

Debugging Details:

READ_ADDRESS: 86e00265

CURRENT_IRQL: 2

FAULTING_IP:
nt!RtlUnicodeToMultiByteN+f2
82a99b1e 8a1c33 mov bl,byte ptr [ebx+esi]

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: System

TRAP_FRAME: 8078a4b0 – (.trap 0xffffffff8078a4b0)
ErrCode = 00000000
eax=8078a54c ebx=00000043 ecx=8078a7ca edx=00000001 esi=86e00222 edi=00000001
eip=82a99b1e esp=8078a524 ebp=8078a530 iopl=0 nv up ei ng nz ac po cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010293
nt!RtlUnicodeToMultiByteN+0xf2:
Page 28842 not present in the dump file. Type “.hh dbgerr004” for details
82a99b1e 8a1c33 mov bl,byte ptr [ebx+esi] ds:0023:86e00265=??
Resetting default scope

LAST_CONTROL_TRANSFER: from 82a99b1e to 8287e82b

STACK_TEXT:
8078a4b0 82a99b1e badb0d00 00000001 8078a4f8 nt!KiTrap0E+0x2cf
8078a530 828412c4 8078a7d8 00000006 8078a560 nt!RtlUnicodeToMultiByteN+0xf2
8078a554 82841250 8078a5a0 00000001 00000006 nt!_wctomb_s_l+0x6a
8078a570 828fbfd7 8078a5a0 8078a7d8 00000006 nt!wctomb_s+0x18
8078a7e4 828fc611 8078a808 a9d9fc1a 00000000 nt!_output_l+0x833
8078a828 828fc11a 8078a8a8 000001ff a9d9fc18 nt!_vsnprintf_l+0x72
8078a844 828fc66e 8078a8a8 000001ff a9d9fc18 nt!_vsnprintf+0x18
8078a864 828fb525 a9d9fc18 8078aaf4 acaa0b9e nt!RtlStringCbVPrintfA+0x30
8078aac8 8283928e 00000065 00000003 a9d9fc18 nt!vDbgPrintExWithPrefixInternal+0x88
8078aae8 a9d91608 a9d9fc18 a9691da8 a9d9b29e nt!DbgPrint+0x1d
8078ab28 81e02fe6 84b8f9d0 769f65f8 8078ab6c wdftester!wdftester_WdfWorkItemEnqueue+0x6a
8078ab38 81e0a900 769f65f8 00220004 8078ab74 SrBtPort!WdfWorkItemEnqueue+0x16 [tools\wdk\7600.16385.0\inc\wdf\kmdf\1.9\wdfworkitem.h @ 136]
8078ab6c 84248317 70574d38 590f0c90 84b9ffa4 SrBtPort!EvtSrSendIoctlToRemoteIOTargetCompletionRoutineForRx+0x490
8078ab98 8422cc36 b0130e90 a6f0f368 00000000 Wdf01000!FxRequestBase::CompleteSubmitted+0xf6
8078abb4 8422ccde 01a8b2c0 a6f2f140 8078abec Wdf01000!FxIoTarget::RequestCompletionRoutine+0x12d
8078abc4 828c18b6 00000000 b0130e90 8fa8b2c0 Wdf01000!FxIoTarget::_RequestCompletionRoutine+0x35
8078abec 82b67cd4 00000000 b0130e90 a6f2f140 nt!IopUnloadSafeCompletion+0x45
8078ac1c 828a0b33 00000000 b0130e90 8078ac94 nt!IovpLocalCompletionRoutine+0x14b
8078ac64 82b67b64 00000000 95f13970 8427bc00 nt!IopfCompleteRequest+0x128
8078accc 84245d6b 95f13970 0000000d 00000000 nt!IovCompleteRequest+0x133
8078acf4 84238757 00000000 00000000 95f13a48 Wdf01000!FxRequest::CompleteInternal+0x379
8078ad10 92cd1c79 00000002 95f13970 00000000 Wdf01000!imp_WdfRequestComplete+0x108
WARNING: Stack unwind information not available. Following frames may be wrong.
8078ad44 84248317 6a0ec688 6dc4f928 86db939c srusb+0x2c79
8078ad70 8422cc36 b0130e90 923b06d0 00000000 Wdf01000!FxRequestBase::CompleteSubmitted+0xf6
8078ad8c 8422ccde 01f13970 923f5d10 8078adc4 Wdf01000!FxIoTarget::RequestCompletionRoutine+0x12d
8078ad9c 828c18b6 922e8020 b0130e90 95f13970 Wdf01000!FxIoTarget::_RequestCompletionRoutine+0x35
8078adc4 82b67cd4 922e8020 b0130e90 923f5d10 nt!IopUnloadSafeCompletion+0x45
8078adf4 828a0b33 922e8020 b0130e90 8078ae68 nt!IovpLocalCompletionRoutine+0x14b
8078ae38 82b67b64 8c5900f0 84bbe1f8 8c590028 nt!IopfCompleteRequest+0x128
8078aea0 8f1ac868 82878354 84bbe1f8 00000000 nt!IovCompleteRequest+0x133
8078aed0 8f1ad178 89638258 b0130e90 86db93e4 USBPORT!USBPORT_Core_iCompleteDoneTransfer+0x6e0
8078aefc 8f1b09af 8c590028 8c5900f0 8c590a98 USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x33b
8078af24 8f1aad18 8c590028 8c590a98 8c590002 USBPORT!USBPORT_Core_UsbIocDpc_Worker+0xbc
8078af48 828a03b5 8c590aa4 8c590002 00000000 USBPORT!USBPORT_Xdpc_Worker+0x173
8078afa4 828a0218 82961d20 8fbe23b8 00000000 nt!KiExecuteAllDpcs+0xf9
8078aff4 8289f9dc acea44fc 00000000 00000000 nt!KiRetireDpcList+0xd5
8078aff8 acea44fc 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2c
8289f9dc 00000000 0000001a 00d6850f bb830000 0xacea44fc

STACK_COMMAND: kb

FOLLOWUP_IP:
wdftester!wdftester_WdfWorkItemEnqueue+6a
a9d91608 83c40c add esp,0Ch

SYMBOL_STACK_INDEX: a

SYMBOL_NAME: wdftester!wdftester_WdfWorkItemEnqueue+6a

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: wdftester

IMAGE_NAME: wdftester.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc82f

FAILURE_BUCKET_ID: 0xA_VRF_wdftester!wdftester_WdfWorkItemEnqueue+6a

BUCKET_ID: 0xA_VRF_wdftester!wdftester_WdfWorkItemEnqueue+6a

Followup: MachineOwner

2

The same driver if I run WDF log test in a DTM client I get almost similar bugcheck but at different wdf function but again in wdftester and in a DbgPrint.

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it’s a trap of a kind
that the kernel isn’t allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 00000008, EXCEPTION_DOUBLE_FAULT
Arg2: 80dc6750
Arg3: 00000000
Arg4: 00000000

Debugging Details:

*** ERROR: Symbol file could not be found. Defaulted to export symbols for wdftester.sys -

BUGCHECK_STR: 0x7f_8

TSS: 00000028 – (.tss 0x28)
eax=80e481ec ebx=00000000 ecx=000001ff edx=80e484d8 esi=80e4828c edi=80e4828c
eip=828f3ccb esp=80e47f78 ebp=80e481c8 iopl=0 nv up ei ng nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010282
nt!_output_l+0x1b:
828f3ccb 53 push ebx
Resetting default scope

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 828f4692 to 828f3ccb

STACK_TEXT:
80e481c8 828f4692 80e481ec 84e4f27e 00000000 nt!_output_l+0x1b
80e4820c 828f4728 80e4828c 000001ff 84e4f27e nt!_vsnprintf_l+0x72
80e48228 828f5f3a 80e4828c 000001ff 84e4f27e nt!_vsnprintf+0x18
80e48248 828f5073 84e4f27e 80e484d8 a8cb7f6a nt!RtlStringCbVPrintfA+0x30
80e484ac 828571a7 00000065 00000003 84e4f27e nt!vDbgPrintExWithPrefixInternal+0x88
80e484cc 84e30d7d 84e4f27e 9a6e68c8 828136ee nt!DbgPrint+0x1d
WARNING: Stack unwind information not available. Following frames may be wrong.
80e4850c 8bc01b76 885796f8 7dff7540 80e4855c wdftester!CvRegisterHookProvider+0xdc1b
80e4851c 8bc06568 7dff7540 00000000 9a5ff030 SrBtPort!WdfIoQueueGetDevice+0x16 [c:\winddk\7600.16385.0\inc\wdf\kmdf\1.9\wdfio.h @ 749]
80e4855c 8bc06972 7dff7540 6e5f4da0 80dc3120 SrBtPort!SrBtPort_PdoEvtIoDefault+0x18
80e48594 84e06edc 7dff7540 6e5f4da0 0000000c SrBtPort!SrBtPort_PdoEvtIoDeviceControl+0x2c2
80e485c4 84dd0072 7dff7540 6e5f4da0 0000000c Wdf01000!VfEvtIoDeviceControl+0x5f
80e485e8 84dd13d0 7dff7540 6e5f4da0 0000000c Wdf01000!FxIoQueueIoInternalDeviceControl::Invoke+0x30
80e48618 84dd39ac 6e5f4da0 91a0b258 82008ab8 Wdf01000!FxIoQueue::DispatchRequestToDriver+0x31d
80e48634 84dd4a36 82008a00 00000000 9194aae8 Wdf01000!FxIoQueue::DispatchEvents+0x3be
80e48654 84dd6824 91a0b258 9c851400 94b8ee70 Wdf01000!FxIoQueue::QueueRequest+0x1ec
80e48678 84dc5a3f 94b8ee70 80e486a8 82b686c3 Wdf01000!FxPkgIo::Dispatch+0x27d
80e48684 82b686c3 9194a990 94b8ee70 7df231c8 Wdf01000!FxDevice::Dispatch+0x7f
80e486a8 82873efb 00000000 00000000 9194a990 nt!IovCallDriver+0x258
80e486bc 84db7164 61e07b50 7df231c8 00000000 nt!IofCallDriver+0x1b
80e486d4 927ba4d1 00000005 9e1f84a8 820dce30 Wdf01000!imp_WdfRequestSend+0x2de
80e486f8 927bb72f 9e1f9c08 61e07b50 91960594 csrserial!SerialSendReadIoctl+0x9d
80e48714 84dc6317 61e07b50 7df231c8 91960594 csrserial!EvtIoctlReadCompletionRoutine+0xe7
80e48740 84daac36 94b8ee70 820dce30 00000000 Wdf01000!FxRequestBase::CompleteSubmitted+0xf6
80e4875c 84daacde 011f84a8 820c0590 80e48794 Wdf01000!FxIoTarget::RequestCompletionRoutine+0x12d
80e4876c 828a9bed 00000000 94b8ee70 9e1f84a8 Wdf01000!FxIoTarget::_RequestCompletionRoutine+0x35
80e48794 82b68cd4 00000000 94b8ee70 820c0590 nt!IopUnloadSafeCompletion+0x45
80e487c4 8289af60 00000000 94b8ee70 80e48838 nt!IovpLocalCompletionRoutine+0x14b
80e48808 82b68b64 00000000 91a0b6f8 84df9c00 nt!IopfCompleteRequest+0x115
80e48870 84dc3d6b 91a0b6f8 8d600478 c0000184 nt!IovCompleteRequest+0x133
80e48898 84dd496e c0000184 00000000 8d600478 Wdf01000!FxRequest::CompleteInternal+0x379
80e488bc 84dd6824 91a0b6f8 82046280 94b8ee70 Wdf01000!FxIoQueue::QueueRequest+0x124
80e488e0 84dc5a3f 94b8ee70 80e48910 82b686c3 Wdf01000!FxPkgIo::Dispatch+0x27d
80e488ec 82b686c3 8859f020 94b8ee70 7df22128 Wdf01000!FxDevice::Dispatch+0x7f
80e48910 82873efb 00000000 80e489bc 8859f020 nt!IovCallDriver+0x258
80e48924 84db70da 885796f8 8211ba80 84e60358 nt!IofCallDriver+0x1b
80e4893c 84e39be4 918778e8 91a0bbe8 820dded0 Wdf01000!imp_WdfRequestSend+0x254
80e48984 8bc0665d 885799d0 6e5f4410 7df22128 wdftester!CvRegisterHookProvider+0x16a82
80e4899c 8bc065b2 6e5f4410 7df22128 80e489bc SrBtPort!WdfRequestSend+0x1d [c:\winddk\7600.16385.0\inc\wdf\kmdf\1.9\wdfrequest.h @ 661]
80e489e4 8bc06972 7dff7540 6e5f4410 80dc3120 SrBtPort!SrBtPort_PdoEvtIoDefault+0x62
80e48a1c 84e06edc 7dff7540 6e5f4410 0000000c SrBtPort!SrBtPort_PdoEvtIoDeviceControl+0x2c2
80e48a4c 84dd0072 7dff7540 6e5f4410 0000000c Wdf01000!VfEvtIoDeviceControl+0x5f
80e48a70 84dd13d0 7dff7540 6e5f4410 0000000c Wdf01000!FxIoQueueIoInternalDeviceControl::Invoke+0x30
80e48aa0 84dd39ac 6e5f4410 91a0bbe8 82008ab8 Wdf01000!FxIoQueue::DispatchRequestToDriver+0x31d
80e48abc 84dd4a36 82008a00 00000000 9194aae8 Wdf01000!FxIoQueue::DispatchEvents+0x3be
80e48adc 84dd6824 91a0bbe8 82328d18 94b8ee70 Wdf01000!FxIoQueue::QueueRequest+0x1ec
80e48b00 84dc5a3f 94b8ee70 80e48b30 82b686c3 Wdf01000!FxPkgIo::Dispatch+0x27d
80e48b0c 82b686c3 9194a990 94b8ee70 7df231c8 Wdf01000!FxDevice::Dispatch+0x7f
80e48b30 82873efb 00000000 00000000 9194a990 nt!IovCallDriver+0x258
80e48b44 84db7164 61e07b50 7df231c8 00000000 nt!IofCallDriver+0x1b
80e48b5c 927ba4d1 00000005 9e1f84a8 820dce30 Wdf01000!imp_WdfRequestSend+0x2de
80e48b80 927bb72f 9e1f9c08 61e07b50 91960594 csrserial!SerialSendReadIoctl+0x9d
80e48b9c 84dc6317 61e07b50 7df231c8 91960594 csrserial!EvtIoctlReadCompletionRoutine+0xe7
80e48bc8 84daac36 94b8ee70 820dce30 00000000 Wdf01000!FxRequestBase::CompleteSubmitted+0xf6
80e48be4 84daacde 011f84a8 8205b3a8 80e48c1c Wdf01000!FxIoTarget::RequestCompletionRoutine+0x12d
80e48bf4 828a9bed 00000000 94b8ee70 9e1f84a8 Wdf01000!FxIoTarget::_RequestCompletionRoutine+0x35
80e48c1c 82b68cd4 00000000 94b8ee70 8205b3a8 nt!IopUnloadSafeCompletion+0x45
80e48c4c 8289af60 00000000 94b8ee70 80e48cc0 nt!IovpLocalCompletionRoutine+0x14b
80e48c90 82b68b64 00000000 91a0b048 84df9c00 nt!IopfCompleteRequest+0x115
80e48cf8 84dc3d6b 91a0b048 8d600478 c0000184 nt!IovCompleteRequest+0x133
80e48d20 84dd496e c0000184 00000000 8d600478 Wdf01000!FxRequest::CompleteInternal+0x379
80e48d44 84dd6824 91a0b048 822627b8 94b8ee70 Wdf01000!FxIoQueue::QueueRequest+0x124
80e48d68 84dc5a3f 94b8ee70 80e48d98 82b686c3 Wdf01000!FxPkgIo::Dispatch+0x27d
80e48d74 82b686c3 8859f020 94b8ee70 7df22128 Wdf01000!FxDevice::Dispatch+0x7f
80e48d98 82873efb 00000000 80e48e44 8859f020 nt!IovCallDriver+0x258
80e48dac 84db70da 885796f8 8211ba80 84e60358 nt!IofCallDriver+0x1b
80e48dc4 84e39be4 918778e8 91bc1628 820dded0 Wdf01000!imp_WdfRequestSend+0x254
80e48e0c 8bc0665d 885799d0 6e43e9d0 7df22128 wdftester!CvRegisterHookProvider+0x16a82
80e48e24 8bc065b2 6e43e9d0 7df22128 80e48e44 SrBtPort!WdfRequestSend+0x1d
80e48e6c 8bc06972 7dff7540 6e43e9d0 80dc3120 SrBtPort!SrBtPort_PdoEvtIoDefault+0x62
80e48ea4 84e06edc 7dff7540 6e43e9d0 0000000c SrBtPort!SrBtPort_PdoEvtIoDeviceControl+0x2c2
80e48ed4 84dd0072 7dff7540 6e43e9d0 0000000c Wdf01000!VfEvtIoDeviceControl+0x5f
80e48ef8 84dd13d0 7dff7540 6e43e9d0 0000000c Wdf01000!FxIoQueueIoInternalDeviceControl::Invoke+0x30
80e48f28 84dd39ac 6e43e9d0 91bc1628 82008ab8 Wdf01000!FxIoQueue::DispatchRequestToDriver+0x31d
80e48f44 84dd4a36 82008a00 00000000 9194aae8 Wdf01000!FxIoQueue::DispatchEvents+0x3be
80e48f64 84dd6824 91bc1628 821dfcf8 94b8ee70 Wdf01000!FxIoQueue::QueueRequest+0x1ec

STACK_COMMAND: .tss 0x28 ; kb

FOLLOWUP_IP:
wdftester!CvRegisterHookProvider+dc1b
84e30d7d c704243e15e584 mov dword ptr [esp],offset wdftester!CvRegisterHookProvider+0x2e3dc (84e5153e)

SYMBOL_STACK_INDEX: 6

SYMBOL_NAME: wdftester!CvRegisterHookProvider+dc1b

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: wdftester

IMAGE_NAME: wdftester.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4b07ac4e

FAILURE_BUCKET_ID: 0x7f_8_VRF_wdftester!CvRegisterHookProvider+dc1b

BUCKET_ID: 0x7f_8_VRF_wdftester!CvRegisterHookProvider+dc1b

Followup: MachineOwner

3

The second bugcheck (EXCEPTION_DOUBLE_FAULT) points to kind of memory corruption. It happened to me when I got stack overflow in my driver. It might be your case too, if you send requests recursively while you should fail them (looks like send-complete-send-complete-send) in your case.

Look at the following threads, they helped me to analyze and solve my problem:

http://www.osronline.com/showThread.cfm?link=70190
http://www.osronline.com/showThread.cfm?link=70180
http://www.osronline.com/showThread.cfm?link=66817

Good luck,
S.

4

I agree with this assessment (I was about to say the same when I saw this, and it says it better, anyway ;]).

The first bugcheck is a bug in the tool (printing unicode at dispatch level), which I know has been fixed, but I’m still checking on availability. I’m fairly sure a WDK and a WLK release have occurred since it was fixed, though. I may have to wait out a vacation [by the tool’s owner] for the definitive answer.

-----Original Message-----
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] wdftester bugcheck

The second bugcheck (EXCEPTION_DOUBLE_FAULT) points to kind of memory corruption. It happened to me when I got stack overflow in my driver. It might be your case too, if you send requests recursively while you should fail them (looks like send-complete-send-complete-send) in your case.

Look at the following threads, they helped me to analyze and solve my problem:

http://www.osronline.com/showThread.cfm?link=70190
http://www.osronline.com/showThread.cfm?link=70180
http://www.osronline.com/showThread.cfm?link=66817

Good luck,
S.

5

Hi There,

Could you please try setting the registry value Default under “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Debug Print Filter” to 0x1? [Update DEFAULT: REG_DWORD to 0x1] This can help as a workaround for the problem below. Please let me know this helps.

Thanks,
Neslihan

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@csr.com
Sent: Monday, October 11, 2010 11:24 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] wdftester bugcheck

Hi All,

I got a bug check when I was testing with my wdf driver with WdfTester. The crash dump shows the crash due to a DbgPrint in wdftester. Somebody please help me with some suggestions as to what could be the reason?

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 86e00265, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 82a99b1e, address which referenced memory

Debugging Details:

READ_ADDRESS: 86e00265

CURRENT_IRQL: 2

FAULTING_IP:
nt!RtlUnicodeToMultiByteN+f2
82a99b1e 8a1c33 mov bl,byte ptr [ebx+esi]

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: System

TRAP_FRAME: 8078a4b0 – (.trap 0xffffffff8078a4b0) ErrCode = 00000000 eax=8078a54c ebx=00000043 ecx=8078a7ca edx=00000001 esi=86e00222 edi=00000001
eip=82a99b1e esp=8078a524 ebp=8078a530 iopl=0 nv up ei ng nz ac po cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010293
nt!RtlUnicodeToMultiByteN+0xf2:
Page 28842 not present in the dump file. Type “.hh dbgerr004” for details
82a99b1e 8a1c33 mov bl,byte ptr [ebx+esi] ds:0023:86e00265=??
Resetting default scope

LAST_CONTROL_TRANSFER: from 82a99b1e to 8287e82b

STACK_TEXT:
8078a4b0 82a99b1e badb0d00 00000001 8078a4f8 nt!KiTrap0E+0x2cf
8078a530 828412c4 8078a7d8 00000006 8078a560 nt!RtlUnicodeToMultiByteN+0xf2
8078a554 82841250 8078a5a0 00000001 00000006 nt!_wctomb_s_l+0x6a
8078a570 828fbfd7 8078a5a0 8078a7d8 00000006 nt!wctomb_s+0x18
8078a7e4 828fc611 8078a808 a9d9fc1a 00000000 nt!_output_l+0x833
8078a828 828fc11a 8078a8a8 000001ff a9d9fc18 nt!_vsnprintf_l+0x72
8078a844 828fc66e 8078a8a8 000001ff a9d9fc18 nt!_vsnprintf+0x18
8078a864 828fb525 a9d9fc18 8078aaf4 acaa0b9e nt!RtlStringCbVPrintfA+0x30
8078aac8 8283928e 00000065 00000003 a9d9fc18 nt!vDbgPrintExWithPrefixInternal+0x88
8078aae8 a9d91608 a9d9fc18 a9691da8 a9d9b29e nt!DbgPrint+0x1d
8078ab28 81e02fe6 84b8f9d0 769f65f8 8078ab6c wdftester!wdftester_WdfWorkItemEnqueue+0x6a
8078ab38 81e0a900 769f65f8 00220004 8078ab74 SrBtPort!WdfWorkItemEnqueue+0x16 [tools\wdk\7600.16385.0\inc\wdf\kmdf\1.9\wdfworkitem.h @ 136] 8078ab6c 84248317 70574d38 590f0c90 84b9ffa4 SrBtPort!EvtSrSendIoctlToRemoteIOTargetCompletionRoutineForRx+0x490
8078ab98 8422cc36 b0130e90 a6f0f368 00000000 Wdf01000!FxRequestBase::CompleteSubmitted+0xf6
8078abb4 8422ccde 01a8b2c0 a6f2f140 8078abec Wdf01000!FxIoTarget::RequestCompletionRoutine+0x12d
8078abc4 828c18b6 00000000 b0130e90 8fa8b2c0 Wdf01000!FxIoTarget::_RequestCompletionRoutine+0x35
8078abec 82b67cd4 00000000 b0130e90 a6f2f140 nt!IopUnloadSafeCompletion+0x45 8078ac1c 828a0b33 00000000 b0130e90 8078ac94 nt!IovpLocalCompletionRoutine+0x14b
8078ac64 82b67b64 00000000 95f13970 8427bc00 nt!IopfCompleteRequest+0x128 8078accc 84245d6b 95f13970 0000000d 00000000 nt!IovCompleteRequest+0x133
8078acf4 84238757 00000000 00000000 95f13a48 Wdf01000!FxRequest::CompleteInternal+0x379
8078ad10 92cd1c79 00000002 95f13970 00000000 Wdf01000!imp_WdfRequestComplete+0x108
WARNING: Stack unwind information not available. Following frames may be wrong.
8078ad44 84248317 6a0ec688 6dc4f928 86db939c srusb+0x2c79
8078ad70 8422cc36 b0130e90 923b06d0 00000000 Wdf01000!FxRequestBase::CompleteSubmitted+0xf6
8078ad8c 8422ccde 01f13970 923f5d10 8078adc4 Wdf01000!FxIoTarget::RequestCompletionRoutine+0x12d
8078ad9c 828c18b6 922e8020 b0130e90 95f13970 Wdf01000!FxIoTarget::_RequestCompletionRoutine+0x35
8078adc4 82b67cd4 922e8020 b0130e90 923f5d10 nt!IopUnloadSafeCompletion+0x45
8078adf4 828a0b33 922e8020 b0130e90 8078ae68 nt!IovpLocalCompletionRoutine+0x14b
8078ae38 82b67b64 8c5900f0 84bbe1f8 8c590028 nt!IopfCompleteRequest+0x128
8078aea0 8f1ac868 82878354 84bbe1f8 00000000 nt!IovCompleteRequest+0x133
8078aed0 8f1ad178 89638258 b0130e90 86db93e4 USBPORT!USBPORT_Core_iCompleteDoneTransfer+0x6e0
8078aefc 8f1b09af 8c590028 8c5900f0 8c590a98 USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x33b
8078af24 8f1aad18 8c590028 8c590a98 8c590002 USBPORT!USBPORT_Core_UsbIocDpc_Worker+0xbc
8078af48 828a03b5 8c590aa4 8c590002 00000000 USBPORT!USBPORT_Xdpc_Worker+0x173
8078afa4 828a0218 82961d20 8fbe23b8 00000000 nt!KiExecuteAllDpcs+0xf9
8078aff4 8289f9dc acea44fc 00000000 00000000 nt!KiRetireDpcList+0xd5
8078aff8 acea44fc 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2c 8289f9dc 00000000 0000001a 00d6850f bb830000 0xacea44fc

STACK_COMMAND: kb

FOLLOWUP_IP:
wdftester!wdftester_WdfWorkItemEnqueue+6a
a9d91608 83c40c add esp,0Ch

SYMBOL_STACK_INDEX: a

SYMBOL_NAME: wdftester!wdftester_WdfWorkItemEnqueue+6a

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: wdftester

IMAGE_NAME: wdftester.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc82f

FAILURE_BUCKET_ID: 0xA_VRF_wdftester!wdftester_WdfWorkItemEnqueue+6a

BUCKET_ID: 0xA_VRF_wdftester!wdftester_WdfWorkItemEnqueue+6a

Followup: MachineOwner

NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

6

In order to receive the traces you can still use Traceview, for more information please see this: http://msdn.microsoft.com/en-us/library/ff556122(VS.85).aspx

Thanks,
Neslihan

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Neslihan Bulut
Sent: Tuesday, October 12, 2010 3:24 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] wdftester bugcheck

Hi There,

Could you please try setting the registry value Default under “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Debug Print Filter” to 0x1? [Update DEFAULT: REG_DWORD to 0x1] This can help as a workaround for the problem below. Please let me know this helps.

Thanks,
Neslihan

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@csr.com
Sent: Monday, October 11, 2010 11:24 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] wdftester bugcheck

Hi All,

I got a bug check when I was testing with my wdf driver with WdfTester. The crash dump shows the crash due to a DbgPrint in wdftester. Somebody please help me with some suggestions as to what could be the reason?

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 86e00265, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 82a99b1e, address which referenced memory

Debugging Details:

READ_ADDRESS: 86e00265

CURRENT_IRQL: 2

FAULTING_IP:
nt!RtlUnicodeToMultiByteN+f2
82a99b1e 8a1c33 mov bl,byte ptr [ebx+esi]

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: System

TRAP_FRAME: 8078a4b0 – (.trap 0xffffffff8078a4b0) ErrCode = 00000000 eax=8078a54c ebx=00000043 ecx=8078a7ca edx=00000001 esi=86e00222 edi=00000001
eip=82a99b1e esp=8078a524 ebp=8078a530 iopl=0 nv up ei ng nz ac po cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010293
nt!RtlUnicodeToMultiByteN+0xf2:
Page 28842 not present in the dump file. Type “.hh dbgerr004” for details
82a99b1e 8a1c33 mov bl,byte ptr [ebx+esi] ds:0023:86e00265=??
Resetting default scope

LAST_CONTROL_TRANSFER: from 82a99b1e to 8287e82b

STACK_TEXT:
8078a4b0 82a99b1e badb0d00 00000001 8078a4f8 nt!KiTrap0E+0x2cf
8078a530 828412c4 8078a7d8 00000006 8078a560 nt!RtlUnicodeToMultiByteN+0xf2
8078a554 82841250 8078a5a0 00000001 00000006 nt!_wctomb_s_l+0x6a
8078a570 828fbfd7 8078a5a0 8078a7d8 00000006 nt!wctomb_s+0x18
8078a7e4 828fc611 8078a808 a9d9fc1a 00000000 nt!_output_l+0x833
8078a828 828fc11a 8078a8a8 000001ff a9d9fc18 nt!_vsnprintf_l+0x72
8078a844 828fc66e 8078a8a8 000001ff a9d9fc18 nt!_vsnprintf+0x18
8078a864 828fb525 a9d9fc18 8078aaf4 acaa0b9e nt!RtlStringCbVPrintfA+0x30
8078aac8 8283928e 00000065 00000003 a9d9fc18 nt!vDbgPrintExWithPrefixInternal+0x88
8078aae8 a9d91608 a9d9fc18 a9691da8 a9d9b29e nt!DbgPrint+0x1d
8078ab28 81e02fe6 84b8f9d0 769f65f8 8078ab6c wdftester!wdftester_WdfWorkItemEnqueue+0x6a
8078ab38 81e0a900 769f65f8 00220004 8078ab74 SrBtPort!WdfWorkItemEnqueue+0x16 [tools\wdk\7600.16385.0\inc\wdf\kmdf\1.9\wdfworkitem.h @ 136] 8078ab6c 84248317 70574d38 590f0c90 84b9ffa4 SrBtPort!EvtSrSendIoctlToRemoteIOTargetCompletionRoutineForRx+0x490
8078ab98 8422cc36 b0130e90 a6f0f368 00000000 Wdf01000!FxRequestBase::CompleteSubmitted+0xf6
8078abb4 8422ccde 01a8b2c0 a6f2f140 8078abec Wdf01000!FxIoTarget::RequestCompletionRoutine+0x12d
8078abc4 828c18b6 00000000 b0130e90 8fa8b2c0 Wdf01000!FxIoTarget::_RequestCompletionRoutine+0x35
8078abec 82b67cd4 00000000 b0130e90 a6f2f140 nt!IopUnloadSafeCompletion+0x45 8078ac1c 828a0b33 00000000 b0130e90 8078ac94 nt!IovpLocalCompletionRoutine+0x14b
8078ac64 82b67b64 00000000 95f13970 8427bc00 nt!IopfCompleteRequest+0x128 8078accc 84245d6b 95f13970 0000000d 00000000 nt!IovCompleteRequest+0x133
8078acf4 84238757 00000000 00000000 95f13a48 Wdf01000!FxRequest::CompleteInternal+0x379
8078ad10 92cd1c79 00000002 95f13970 00000000 Wdf01000!imp_WdfRequestComplete+0x108
WARNING: Stack unwind information not available. Following frames may be wrong.
8078ad44 84248317 6a0ec688 6dc4f928 86db939c srusb+0x2c79
8078ad70 8422cc36 b0130e90 923b06d0 00000000 Wdf01000!FxRequestBase::CompleteSubmitted+0xf6
8078ad8c 8422ccde 01f13970 923f5d10 8078adc4 Wdf01000!FxIoTarget::RequestCompletionRoutine+0x12d
8078ad9c 828c18b6 922e8020 b0130e90 95f13970 Wdf01000!FxIoTarget::_RequestCompletionRoutine+0x35
8078adc4 82b67cd4 922e8020 b0130e90 923f5d10 nt!IopUnloadSafeCompletion+0x45
8078adf4 828a0b33 922e8020 b0130e90 8078ae68 nt!IovpLocalCompletionRoutine+0x14b
8078ae38 82b67b64 8c5900f0 84bbe1f8 8c590028 nt!IopfCompleteRequest+0x128
8078aea0 8f1ac868 82878354 84bbe1f8 00000000 nt!IovCompleteRequest+0x133
8078aed0 8f1ad178 89638258 b0130e90 86db93e4 USBPORT!USBPORT_Core_iCompleteDoneTransfer+0x6e0
8078aefc 8f1b09af 8c590028 8c5900f0 8c590a98 USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x33b
8078af24 8f1aad18 8c590028 8c590a98 8c590002 USBPORT!USBPORT_Core_UsbIocDpc_Worker+0xbc
8078af48 828a03b5 8c590aa4 8c590002 00000000 USBPORT!USBPORT_Xdpc_Worker+0x173
8078afa4 828a0218 82961d20 8fbe23b8 00000000 nt!KiExecuteAllDpcs+0xf9
8078aff4 8289f9dc acea44fc 00000000 00000000 nt!KiRetireDpcList+0xd5
8078aff8 acea44fc 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2c 8289f9dc 00000000 0000001a 00d6850f bb830000 0xacea44fc

STACK_COMMAND: kb

FOLLOWUP_IP:
wdftester!wdftester_WdfWorkItemEnqueue+6a
a9d91608 83c40c add esp,0Ch

SYMBOL_STACK_INDEX: a

SYMBOL_NAME: wdftester!wdftester_WdfWorkItemEnqueue+6a

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: wdftester

IMAGE_NAME: wdftester.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc82f

FAILURE_BUCKET_ID: 0xA_VRF_wdftester!wdftester_WdfWorkItemEnqueue+6a

BUCKET_ID: 0xA_VRF_wdftester!wdftester_WdfWorkItemEnqueue+6a

Followup: MachineOwner

NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

7

Just to be clear, that’s a value named ‘DEFAULT,’ not the default value in
the registry sense (default).

mm

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Neslihan Bulut
Sent: Tuesday, October 12, 2010 6:24 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] wdftester bugcheck

Hi There,

Could you please try setting the registry value Default under
“HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Debug
Print Filter” to 0x1? [Update DEFAULT: REG_DWORD to 0x1] This can help as a
workaround for the problem below. Please let me know this helps.

Thanks,
Neslihan

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@csr.com
Sent: Monday, October 11, 2010 11:24 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] wdftester bugcheck

Hi All,

I got a bug check when I was testing with my wdf driver with WdfTester. The
crash dump shows the crash due to a DbgPrint in wdftester. Somebody please
help me with some suggestions as to what could be the reason?

****************************************************************************
***
*
*
* Bugcheck Analysis
*
*
*
****************************************************************************
***

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at
an interrupt request level (IRQL) that is too high. This is usually caused
by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 86e00265, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation
(only on chips which support this level of status)
Arg4: 82a99b1e, address which referenced memory

Debugging Details:

READ_ADDRESS: 86e00265

CURRENT_IRQL: 2

FAULTING_IP:
nt!RtlUnicodeToMultiByteN+f2
82a99b1e 8a1c33 mov bl,byte ptr [ebx+esi]

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: System

TRAP_FRAME: 8078a4b0 – (.trap 0xffffffff8078a4b0) ErrCode = 00000000
eax=8078a54c ebx=00000043 ecx=8078a7ca edx=00000001 esi=86e00222
edi=00000001
eip=82a99b1e esp=8078a524 ebp=8078a530 iopl=0 nv up ei ng nz ac po
cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000
efl=00010293
nt!RtlUnicodeToMultiByteN+0xf2:
Page 28842 not present in the dump file. Type “.hh dbgerr004” for details
82a99b1e 8a1c33 mov bl,byte ptr [ebx+esi]
ds:0023:86e00265=??
Resetting default scope

LAST_CONTROL_TRANSFER: from 82a99b1e to 8287e82b

STACK_TEXT:
8078a4b0 82a99b1e badb0d00 00000001 8078a4f8 nt!KiTrap0E+0x2cf
8078a530 828412c4 8078a7d8 00000006 8078a560 nt!RtlUnicodeToMultiByteN+0xf2
8078a554 82841250 8078a5a0 00000001 00000006 nt!_wctomb_s_l+0x6a
8078a570 828fbfd7 8078a5a0 8078a7d8 00000006 nt!wctomb_s+0x18
8078a7e4 828fc611 8078a808 a9d9fc1a 00000000 nt!_output_l+0x833
8078a828 828fc11a 8078a8a8 000001ff a9d9fc18 nt!_vsnprintf_l+0x72
8078a844 828fc66e 8078a8a8 000001ff a9d9fc18 nt!_vsnprintf+0x18
8078a864 828fb525 a9d9fc18 8078aaf4 acaa0b9e nt!RtlStringCbVPrintfA+0x30
8078aac8 8283928e 00000065 00000003 a9d9fc18
nt!vDbgPrintExWithPrefixInternal+0x88
8078aae8 a9d91608 a9d9fc18 a9691da8 a9d9b29e nt!DbgPrint+0x1d
8078ab28 81e02fe6 84b8f9d0 769f65f8 8078ab6c
wdftester!wdftester_WdfWorkItemEnqueue+0x6a
8078ab38 81e0a900 769f65f8 00220004 8078ab74
SrBtPort!WdfWorkItemEnqueue+0x16
[tools\wdk\7600.16385.0\inc\wdf\kmdf\1.9\wdfworkitem.h @ 136] 8078ab6c
84248317 70574d38 590f0c90 84b9ffa4
SrBtPort!EvtSrSendIoctlToRemoteIOTargetCompletionRoutineForRx+0x490
8078ab98 8422cc36 b0130e90 a6f0f368 00000000
Wdf01000!FxRequestBase::CompleteSubmitted+0xf6
8078abb4 8422ccde 01a8b2c0 a6f2f140 8078abec
Wdf01000!FxIoTarget::RequestCompletionRoutine+0x12d
8078abc4 828c18b6 00000000 b0130e90 8fa8b2c0
Wdf01000!FxIoTarget::_RequestCompletionRoutine+0x35
8078abec 82b67cd4 00000000 b0130e90 a6f2f140 nt!IopUnloadSafeCompletion+0x45
8078ac1c 828a0b33 00000000 b0130e90 8078ac94
nt!IovpLocalCompletionRoutine+0x14b
8078ac64 82b67b64 00000000 95f13970 8427bc00 nt!IopfCompleteRequest+0x128
8078accc 84245d6b 95f13970 0000000d 00000000 nt!IovCompleteRequest+0x133
8078acf4 84238757 00000000 00000000 95f13a48
Wdf01000!FxRequest::CompleteInternal+0x379
8078ad10 92cd1c79 00000002 95f13970 00000000
Wdf01000!imp_WdfRequestComplete+0x108
WARNING: Stack unwind information not available. Following frames may be
wrong.
8078ad44 84248317 6a0ec688 6dc4f928 86db939c srusb+0x2c79
8078ad70 8422cc36 b0130e90 923b06d0 00000000
Wdf01000!FxRequestBase::CompleteSubmitted+0xf6
8078ad8c 8422ccde 01f13970 923f5d10 8078adc4
Wdf01000!FxIoTarget::RequestCompletionRoutine+0x12d
8078ad9c 828c18b6 922e8020 b0130e90 95f13970
Wdf01000!FxIoTarget::_RequestCompletionRoutine+0x35
8078adc4 82b67cd4 922e8020 b0130e90 923f5d10 nt!IopUnloadSafeCompletion+0x45
8078adf4 828a0b33 922e8020 b0130e90 8078ae68
nt!IovpLocalCompletionRoutine+0x14b
8078ae38 82b67b64 8c5900f0 84bbe1f8 8c590028 nt!IopfCompleteRequest+0x128
8078aea0 8f1ac868 82878354 84bbe1f8 00000000 nt!IovCompleteRequest+0x133
8078aed0 8f1ad178 89638258 b0130e90 86db93e4
USBPORT!USBPORT_Core_iCompleteDoneTransfer+0x6e0
8078aefc 8f1b09af 8c590028 8c5900f0 8c590a98
USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x33b
8078af24 8f1aad18 8c590028 8c590a98 8c590002
USBPORT!USBPORT_Core_UsbIocDpc_Worker+0xbc
8078af48 828a03b5 8c590aa4 8c590002 00000000
USBPORT!USBPORT_Xdpc_Worker+0x173
8078afa4 828a0218 82961d20 8fbe23b8 00000000 nt!KiExecuteAllDpcs+0xf9
8078aff4 8289f9dc acea44fc 00000000 00000000 nt!KiRetireDpcList+0xd5
8078aff8 acea44fc 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2c
8289f9dc 00000000 0000001a 00d6850f bb830000 0xacea44fc

STACK_COMMAND: kb

FOLLOWUP_IP:
wdftester!wdftester_WdfWorkItemEnqueue+6a
a9d91608 83c40c add esp,0Ch

SYMBOL_STACK_INDEX: a

SYMBOL_NAME: wdftester!wdftester_WdfWorkItemEnqueue+6a

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: wdftester

IMAGE_NAME: wdftester.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc82f

FAILURE_BUCKET_ID: 0xA_VRF_wdftester!wdftester_WdfWorkItemEnqueue+6a

BUCKET_ID: 0xA_VRF_wdftester!wdftester_WdfWorkItemEnqueue+6a

Followup: MachineOwner

NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

8

> UNEXPECTED_KERNEL_MODE_TRAP (7f)

Arg1: 00000008, EXCEPTION_DOUBLE_FAULT

Kernel stack overflow.

–
Maxim S. Shatskih
Windows DDK MVP
xxxxx@storagecraft.com
http://www.storagecraft.com

9

Thank you Skaramush, Bob, Neslihan & Maxim.

The second one was indeed a Kernel stack overflow.

The first one was happening when I was using wdftester from DDK. But with the one from the DTM was not causing any issues.

Thank you all once again.