BSOD on running CHAOS-WDF Preview test

NTDEV
1

On running the WHQL test case I get the following bugcheck for my wdf driver, this bug check is a random one. On Calling WdfIoQueuePurgeSynchronously from the EvtDeviceSurpriseRemoval I am getting this issue.

What could be the possible senarios in which this bug check is happening? Somebody please help me with some suggestions?

0: kd> ! analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffff80000003, The exception code that was not handled
Arg2: fffff80002a84f40, The address that the exception occurred at
Arg3: fffff88002fd60b8, Exception Record Address
Arg4: fffff88002fd5910, Context Record Address

Debugging Details:

EXCEPTION_CODE: (HRESULT) 0x80000003 (2147483651) - One or more arguments are invalid

FAULTING_IP:
nt!DbgBreakPoint+0
fffff800`02a84f40 cc int 3

EXCEPTION_RECORD: fffff88002fd60b8 – (.exr 0xfffff88002fd60b8)
ExceptionAddress: fffff80002a84f40 (nt!DbgBreakPoint)
ExceptionCode: 80000003 (Break instruction exception)
ExceptionFlags: 00000000
NumberParameters: 1
Parameter[0]: 0000000000000000

CONTEXT: fffff88002fd5910 – (.cxr 0xfffff88002fd5910)
rax=0000000000000000 rbx=0000057ffdddef78 rcx=18987f349c080000
rdx=0000000000000008 rsi=fffffa8002a3a660 rdi=fffff88000ea0150
rip=fffff80002a84f40 rsp=fffff88002fd62f8 rbp=fffff88002fd6390
r8=0000000000000001 r9=fffff80002ac9ec0 r10=fffffffffffffffe
r11=fffff88002fd62f8 r12=0000057ffdfc0f78 r13=0000000000000000
r14=fffffa8003769490 r15=fffff88000e960f0
iopl=0 nv up ei pl nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00000202
nt!DbgBreakPoint:
fffff800`02a84f40 cc int 3
Resetting default scope

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x7E

PROCESS_NAME: System

CURRENT_IRQL: 0

ERROR_CODE: (NTSTATUS) 0x80000003 - {EXCEPTION} Breakpoint A breakpoint has been reached.

EXCEPTION_PARAMETER1: 0000000000000000

LAST_CONTROL_TRANSFER: from fffff88000e76a8b to fffff80002a84f40

STACK_TEXT:
fffff88002fd62f8 fffff88000e76a8b : fffff88000ea1308 fffffa8000ceb040 fffff88000ea0150 0000057ffdddef78 : nt!DbgBreakPoint
fffff88002fd6300 fffff88000e5ff26 : 0000057ffdddef78 0000000000000000 0000000000000000 0000000000000101 : Wdf01000!_FX_DRIVER_GLOBALS::WaitForSignal+0x53
fffff88002fd6350 fffff88000e5adbf : fffffa8002a3a660 0000000000000000 0000000000000101 0000000000000101 : Wdf01000!FxIoQueue::QueuePurgeSynchronously+0xd6
fffff88002fd63c0 fffff88002001d9b : fffffa8002221080 fffffa8003907380 0000000042727300 0000000000000004 : Wdf01000!imp_WdfIoQueuePurgeSynchronously+0x10b
fffff88002fd6410 fffff880020040c9 : 0000057ffdddef78 fffff880021c09d8 0000000000000000 0000000000000000 : BtPort!WdfIoQueuePurgeSynchronously+0x1b [c:\winddk\7600.16385.0\inc\wdf\kmdf\1.9\wdfio.h @ 980]
fffff88002fd6440 fffff88000eb36b6 : 0000057ffdfc0f78 fffff88002fd6538 0000000000000004 fffff88002fd6540 : BtPort!CsrBtPort_EvtDeviceSurpriseRemoval+0x89 [d:\harmony_test\rel_01_00\kernel\bt\csrbtport\csrbtportdriver\btport.c @ 1913]
fffff88002fd64a0 fffff88000e8878c : fffffa8001af2640 0000000000000127 0000000000000127 fffffa8001af2640 : Wdf01000!VfEvtDeviceSurpriseRemoval+0x5e
fffff88002fd64d0 fffff88000e87841 : 0000000000000127 fffff88002fd6630 0000000000000119 0000000000000000 : Wdf01000!FxPkgPnp::PnpEventSurpriseRemoveIoStarted+0x2c
fffff88002fd6500 fffff88000e874fe : fffffa8001af2640 fffff88002fd6630 0000000000000400 fffff88000e965f0 : Wdf01000!FxPkgPnp::PnpEnterNewState+0x1a5
fffff88002fd6570 fffff88000e87201 : 0000000000000000 0000000000000400 0000000000000000 fffffa8001af2640 : Wdf01000!FxPkgPnp::PnpProcessEventInner+0x122
fffff88002fd65e0 fffff88000e85e54 : 0000000000000000 fffffa8001af2640 0000000000000002 0000000000000000 : Wdf01000!FxPkgPnp::PnpProcessEvent+0x1b1
fffff88002fd6670 fffff88000e7ddd6 : fffffa8002a3a660 0000000000000002 0000000000000000 fffffa8001af2640 : Wdf01000!FxPkgFdo::_PnpSurpriseRemoval+0x28
fffff88002fd66a0 fffff88000e4d245 : fffff9800c58ecf0 fffff9800c58ecf0 fffffa8001dd35e0 0000000000000000 : Wdf01000!FxPkgPnp::Dispatch+0x1b2
fffff88002fd6710 fffff88000e4d14b : fffff88002fd67f8 fffff9800c58ecf0 0000000000000002 fffffa8001dd35e0 : Wdf01000!FxDevice::Dispatch+0xa9
fffff88002fd6740 fffff80002f32c16 : fffff9800c58ecf0 0000000000000002 fffffa8001dd35e0 fffff80002df86eb : Wdf01000!FxDevice::DispatchWithLock+0x93
fffff88002fd6780 fffff88005e019bc : fffffa8002b3dc50 fffff9800c58ecf0 fffffa8003080bb0 fffffa800309c2b0 : nt!IovCallDriver+0x566
fffff88002fd67e0 fffff88005e082b9 : fffffa8002b3dc50 fffff9800c58ecf0 fffffa80000054fc fffffa8003080bb0 : pnpfiltr+0x19bc
fffff88002fd6810 fffff88005e075c8 : fffff9800c58ecf0 fffff88005e00000 fffffa8003080bb0 fffffa8003524010 : pnpfiltr+0x82b9
fffff88002fd6840 fffff80002f32c16 : fffff9800c58ecf0 0000000000000002 fffffa8003080bb0 fffff88002fd6988 : pnpfiltr+0x75c8
fffff88002fd6870 fffff80002cf8419 : fffffa8003080bb0 00000000c00000bb fffff88002fd6988 fffffa8003524010 : nt!IovCallDriver+0x566
fffff88002fd68d0 fffff80002e76391 : fffffa8003769490 0000000000000000 fffffa800376a430 0000000000000000 : nt!IopSynchronousCall+0xc5
fffff88002fd6940 fffff80002e70e08 : 0000000000000010 fffffa8003769490 000000000000030a 0000000000000308 : nt!IopRemoveDevice+0x101
fffff88002fd6a00 fffff80002e75ed7 : fffffa800376a430 0000000000000000 0000000000000003 0000000000010246 : nt!PnpSurpriseRemoveLockedDeviceNode+0x128
fffff88002fd6a40 fffff80002e75ff0 : 0000000000000000 fffff8a001571b00 fffff8a0022c4080 000000004e706e50 : nt!PnpDeleteLockedDeviceNode+0x37
fffff88002fd6a70 fffff80002f05f6f : 0000000000000002 0000000000000000 fffffa800376a430 fffff8a001571b00 : nt!PnpDeleteLockedDeviceNodes+0xa0
fffff88002fd6ae0 fffff80002f06b2c : fffff88002fd6cb8 fffff80002cf8000 0000000000000000 0000000000000000 : nt!PnpProcessQueryRemoveAndEject+0x6cf
fffff88002fd6c20 fffff80002df1c48 : 0000000000000000 fffffa800222b300 fffff8a001571b00 0000000000000001 : nt!PnpProcessTargetDeviceEvent+0x4c
fffff88002fd6c50 fffff80002a9a161 : fffff80002cf7fc0 fffff8a001571b00 fffff80002c305f8 0000000000000000 : nt! ?? ::NNGAKEGL::string'+0x5abab fffff88002fd6cb0 fffff80002d30166 : 0000000000000000 fffffa8000ceb040 0000000000000080 fffffa8000cce040 : nt!ExpWorkerThread+0x111 fffff88002fd6d40 fffff80002a6b486 : fffff880009e9180 fffffa8000ceb040 fffff880009f3f40 0000000000000000 : nt!PspSystemThreadStartup+0x5a fffff88002fd6d80 0000000000000000 : fffff88002fd7000 fffff88002fd1000 fffff88002fd4be0 00000000`00000000 : nt!KxStartSystemThread+0x16

FOLLOWUP_IP:
CsrBtPort!WdfIoQueuePurgeSynchronously+1b [c:\winddk\7600.16385.0\inc\wdf\kmdf\1.9\wdfio.h @ 980]
fffff880`02001d9b 4883c428 add rsp,28h

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: CsrBtPort!WdfIoQueuePurgeSynchronously+1b

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: CsrBtPort

IMAGE_NAME: CsrBtPort.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4cd284af

STACK_COMMAND: .cxr 0xfffff88002fd5910 ; kb

FAILURE_BUCKET_ID: X64_0x7E_VRF_CsrBtPort!WdfIoQueuePurgeSynchronously+1b

BUCKET_ID: X64_0x7E_VRF_CsrBtPort!WdfIoQueuePurgeSynchronously+1b

Followup: MachineOwner

2

Hi All,

I got one more bugcheck 7E while testing WDF Logo Tests. I am handling all the error cases for all the wdf functions which returns the status. But why I am getting a bug check in WdfUsbInterfaceGetConfiguredSettingIndex which doesnt have any status?

Somebody please help me with some suggestions for this one too…

0: kd> ! analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffff80000003, The exception code that was not handled
Arg2: fffff80002a6df40, The address that the exception occurred at
Arg3: fffff88002fcdea8, Exception Record Address
Arg4: fffff88002fcd700, Context Record Address

Debugging Details:

Unable to open image file: C:\Program Files (x86)\Debugging Tools for Windows (x86)\sym\ntkrnlmp.exe\4A5BC6005dd000\ntkrnlmp.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files (x86)\Debugging Tools for Windows (x86)\sym\ntkrnlmp.exe\4A5BC6005dd000\ntkrnlmp.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files (x86)\Debugging Tools for Windows (x86)\sym\ntkrnlmp.exe\4A5BC6005dd000\ntkrnlmp.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files (x86)\Debugging Tools for Windows (x86)\sym\ntkrnlmp.exe\4A5BC6005dd000\ntkrnlmp.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files (x86)\Debugging Tools for Windows (x86)\sym\ntkrnlmp.exe\4A5BC6005dd000\ntkrnlmp.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files (x86)\Debugging Tools for Windows (x86)\sym\ntkrnlmp.exe\4A5BC6005dd000\ntkrnlmp.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files (x86)\Debugging Tools for Windows (x86)\sym\ntkrnlmp.exe\4A5BC6005dd000\ntkrnlmp.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files (x86)\Debugging Tools for Windows (x86)\sym\ntkrnlmp.exe\4A5BC6005dd000\ntkrnlmp.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files (x86)\Debugging Tools for Windows (x86)\sym\ntkrnlmp.exe\4A5BC6005dd000\ntkrnlmp.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files (x86)\Debugging Tools for Windows (x86)\sym\ntkrnlmp.exe\4A5BC6005dd000\ntkrnlmp.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files (x86)\Debugging Tools for Windows (x86)\sym\ntkrnlmp.exe\4A5BC6005dd000\ntkrnlmp.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files (x86)\Debugging Tools for Windows (x86)\sym\ntkrnlmp.exe\4A5BC6005dd000\ntkrnlmp.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files (x86)\Debugging Tools for Windows (x86)\sym\ntkrnlmp.exe\4A5BC6005dd000\ntkrnlmp.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files (x86)\Debugging Tools for Windows (x86)\sym\ntkrnlmp.exe\4A5BC6005dd000\ntkrnlmp.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files (x86)\Debugging Tools for Windows (x86)\sym\ntkrnlmp.exe\4A5BC6005dd000\ntkrnlmp.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files (x86)\Debugging Tools for Windows (x86)\sym\ntkrnlmp.exe\4A5BC6005dd000\ntkrnlmp.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files (x86)\Debugging Tools for Windows (x86)\sym\ntkrnlmp.exe\4A5BC6005dd000\ntkrnlmp.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files (x86)\Debugging Tools for Windows (x86)\sym\ntkrnlmp.exe\4A5BC6005dd000\ntkrnlmp.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files (x86)\Debugging Tools for Windows (x86)\sym\ntkrnlmp.exe\4A5BC6005dd000\ntkrnlmp.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files (x86)\Debugging Tools for Windows (x86)\sym\ntkrnlmp.exe\4A5BC6005dd000\ntkrnlmp.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files (x86)\Debugging Tools for Windows (x86)\sym\ntkrnlmp.exe\4A5BC6005dd000\ntkrnlmp.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files (x86)\Debugging Tools for Windows (x86)\sym\ntkrnlmp.exe\4A5BC6005dd000\ntkrnlmp.exe
The system cannot find the file specified.

EXCEPTION_CODE: (HRESULT) 0x80000003 (2147483651) - One or more arguments are invalid

FAULTING_IP:
nt!DbgBreakPoint+0
fffff800`02a6df40 cc int 3

EXCEPTION_RECORD: fffff88002fcdea8 – (.exr 0xfffff88002fcdea8)
ExceptionAddress: fffff80002a6df40 (nt!DbgBreakPoint)
ExceptionCode: 80000003 (Break instruction exception)
ExceptionFlags: 00000000
NumberParameters: 1
Parameter[0]: 0000000000000000

CONTEXT: fffff88002fcd700 – (.cxr 0xfffff88002fcd700)
rax=0000000000000000 rbx=fffffa8003dae9b0 rcx=fffff88000f29f70
rdx=fffffa8001a147f0 rsi=fffffa8001a147e0 rdi=0000000000000000
rip=fffff80002a6df40 rsp=fffff88002fce0e8 rbp=0000057ffc251648
r8=fffffa8001a147f0 r9=fffff88000f29f40 r10=7efefefefeff6172
r11=fffffa8001a14690 r12=fffffa8004b31010 r13=0000057ffc6936e8
r14=0000057ffe607cb8 r15=0000057ffdfb58e8
iopl=0 nv up ei pl nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00000202
nt!DbgBreakPoint:
fffff800`02a6df40 cc int 3
Resetting default scope

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x7E

PROCESS_NAME: System

CURRENT_IRQL: 0

ERROR_CODE: (NTSTATUS) 0x80000003 - {EXCEPTION} Breakpoint A breakpoint has been reached.

EXCEPTION_PARAMETER1: 0000000000000000

LOCK_ADDRESS: fffff80002c78400 – (!locks fffff80002c78400)

Resource @ nt!PiEngineLock (0xfffff80002c78400) Exclusively owned
Contention Count = 46
NumberOfExclusiveWaiters = 1
Threads: fffffa80018b9680-01<*>
Threads Waiting On Exclusive Access:
fffffa80018b7040

1 total locks, 1 locks currently held

PNP_TRIAGE:
Lock address : 0xfffff80002c78400
Thread Count : 1
Thread address: 0xfffffa80018b9680
Thread wait : 0x4f4a

LAST_CONTROL_TRANSFER: from fffff80002de4824 to fffff80002a75f00

STACK_TEXT:
fffff88002fce0e8 fffff88000ec0289 : fffffa8003dae9b0 fffffa8001a147f0 fffffa8001a147f0 fffff88000f29f40 : nt!DbgBreakPoint
fffff88002fce0f0 fffff88000eb6ebe : fffffa800389ca30 0000000000000001 0000000000000000 fffff88000f7fb10 : Wdf01000!FxUsbInterface::GetConfiguredSettingIndex+0x7d
fffff88002fce130 fffff88000f83b8f : fffffa8003dae9b0 0000000000000008 0000000000000001 fffff80002ab2ec0 : Wdf01000!imp_WdfUsbInterfaceGetConfiguredSettingIndex+0x82
fffff88002fce170 fffff88005bdbd9b : fffffa80030bed00 0000000000000000 fffff88000000000 0000057ffc251603 : wdftester!CvRegisterHookProvider+0x2b3d7
fffff88002fce1e0 fffff88005bdd1e3 : 0000057ffc251648 0000000000000000 fffff88045494348 00000000000007ff : srusb!WdfUsbInterfaceGetConfiguredSettingIndex+0x1b [c:\winddk\7600.16385.0\inc\wdf\kmdf\1.9\wdfusb.h @ 2278]
fffff88002fce210 fffff88005bdce09 : 0000057ffc6936e8 fffffa8002cd8790 fffff88002fce318 00000000000000c1 : srusb!SelectInterfaces+0x3b3 [sys\srbc_device.c @ 894]
fffff88002fce2e0 fffff88005bdcca9 : 0000057ffc6936e8 fffffa800396cc80 fffffa800396cca0 0000000000000000 : srusb!ConfigureDevice+0x129 [sys\srbc_device.c @ 770]
fffff88002fce380 fffff88005bdc5a8 : 0000057ffc6936e8 fffff80000000002 fffff88005be4190 0000000000000000 : srusb!ReadAndSelectDescriptors+0x149 [\sys\srbc_device.c @ 686]
fffff88002fce3c0 fffff88000f3eedf : 0000057ffc6936e8 0000057ffdfb58e8 0000057ffe607cb8 0000000000000000 : srusb!srBc_EvtDevicePrepareHardware+0x48 [sys\srbc_device.c @ 364]
fffff88002fce440 fffff88000f14cfe : fffffa8003010780 0000000000000000 fffff88002fce510 fffffa8003010780 : Wdf01000!VfEvtDevicePrepareHardware+0x6f
fffff88002fce490 fffff88000f139ce : fffffa8001f1ab20 0000000000000108 0000000000000000 0000000000000000 : Wdf01000!FxPkgPnp::PnpPrepareHardware+0x8e
fffff88002fce4d0 fffff88000f13841 : 0000000000000101 0000000000000108 0000000000000108 fffff80002a34c00 : Wdf01000!FxPkgPnp::PnpEventHardwareAvailable+0x9a
fffff88002fce510 fffff88000f134fe : fffffa8003010780 fffff88002fce640 0000000000000004 fffff88000f22390 : Wdf01000!FxPkgPnp::PnpEnterNewState+0x1a5
fffff88002fce580 fffff88000f13201 : 0000000000000000 0000000000000002 0000000000000000 fffffa8003010780 : Wdf01000!FxPkgPnp::PnpProcessEventInner+0x122
fffff88002fce5f0 fffff88000f0ad9c : 0000000000000000 fffffa8003010780 fffffa8002a7a1b0 0000000000000000 : Wdf01000!FxPkgPnp::PnpProcessEvent+0x1b1
fffff88002fce680 fffff88000f09dd6 : fffffa8001a14690 fffffa8002a7a1b0 0000000000000000 fffffa8003010780 : Wdf01000!FxPkgPnp::_PnpStartDevice+0x20
fffff88002fce6b0 fffff88000ed9245 : fffffa8001ad7910 fffffa8001ad7910 fffffa8001f1ab20 fffff80002b73cd0 : Wdf01000!FxPkgPnp::Dispatch+0x1b2
fffff88002fce720 fffff88000ed914b : 0000000000000005 fffffa8001ad7910 fffffa8002a7a1b0 fffffa8001f1ab20 : Wdf01000!FxDevice::Dispatch+0xa9
fffff88002fce750 fffff80002e33bde : fffffa8001ad7910 fffffa8002a7a1b0 fffffa8001f1ab20 fffff80002beee80 : Wdf01000!FxDevice::DispatchWithLock+0x93
fffff88002fce790 fffff80002b6e0ed : fffffa8003723060 fffffa8002a7a1b0 fffff80002b73cd0 0000000000000000 : nt!PnpAsynchronousCall+0xce
fffff88002fce7d0 fffff80002e3e926 : fffff80002c781c0 fffffa8003493d90 fffffa8002a7a1b0 fffffa8003493f38 : nt!PnpStartDevice+0x11d
fffff88002fce890 fffff80002e3ebc4 : fffffa8003493d90 fffffa8003490024 fffffa8003493d90 0000000000000001 : nt!PnpStartDeviceNode+0x156
fffff88002fce920 fffff80002e61ea6 : fffffa8003493d90 fffffa8003493d90 0000000000000000 0000000000000000 : nt!PipProcessStartPhase1+0x74
fffff88002fce950 fffff80002e62297 : fffffa8003493d90 0000000000000000 0000000000000001 fffff80002ce271c : nt!PipProcessDevNodeTree+0x296
fffff88002fcebc0 fffff80002b76333 : 0000000100000003 0000000000000000 0000000000000001 0000000000000000 : nt!PiRestartDevice+0xc7
fffff88002fcec10 fffff80002a83161 : fffff80002b76020 fffff80002b76001 fffff80002c19500 0000000000000000 : nt!PnpDeviceActionWorker+0x313
fffff88002fcecb0 fffff80002d19166 : 0000000000000000 fffffa80018b9680 0000000000000080 fffffa80018a6040 : nt!ExpWorkerThread+0x111
fffff88002fced40 fffff80002a54486 : fffff880009e9180 fffffa80018b9680 fffff880009f3f40 0000000000000000 : nt!PspSystemThreadStartup+0x5a
fffff88002fced80 0000000000000000 : fffff88002fcf000 fffff88002fc9000 fffff88002fcdc50 0000000000000000 : nt!KxStartSystemThread+0x16

FOLLOWUP_IP:
wdftester!CvRegisterHookProvider+2b3d7
fffff880`00f83b8f 88842480000000 mov byte ptr [rsp+80h],al

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: wdftester!CvRegisterHookProvider+2b3d7

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: wdftester

IMAGE_NAME: wdftester.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4b07ad7e

STACK_COMMAND: .cxr 0xfffff88002fcd700 ; kb

FAILURE_BUCKET_ID: X64_0x7E_wdftester!CvRegisterHookProvider+2b3d7

BUCKET_ID: X64_0x7E_wdftester!CvRegisterHookProvider+2b3d7

Followup: MachineOwner

3

Why do you need to have a surprise removal handler? Typically you set up your queues so that KMDF purges them for you based on pnp/power state changes and not something you track by yourself

d

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@csr.com
Sent: Sunday, November 28, 2010 8:38 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] BSOD on running CHAOS-WDF Preview test

On running the WHQL test case I get the following bugcheck for my wdf driver, this bug check is a random one. On Calling WdfIoQueuePurgeSynchronously from the EvtDeviceSurpriseRemoval I am getting this issue.

What could be the possible senarios in which this bug check is happening? Somebody please help me with some suggestions?

0: kd> ! analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffff80000003, The exception code that was not handled
Arg2: fffff80002a84f40, The address that the exception occurred at
Arg3: fffff88002fd60b8, Exception Record Address
Arg4: fffff88002fd5910, Context Record Address

Debugging Details:

EXCEPTION_CODE: (HRESULT) 0x80000003 (2147483651) - One or more arguments are invalid

FAULTING_IP:
nt!DbgBreakPoint+0
fffff800`02a84f40 cc int 3

EXCEPTION_RECORD: fffff88002fd60b8 – (.exr 0xfffff88002fd60b8)
ExceptionAddress: fffff80002a84f40 (nt!DbgBreakPoint)
ExceptionCode: 80000003 (Break instruction exception)
ExceptionFlags: 00000000
NumberParameters: 1
Parameter[0]: 0000000000000000

CONTEXT: fffff88002fd5910 – (.cxr 0xfffff88002fd5910)
rax=0000000000000000 rbx=0000057ffdddef78 rcx=18987f349c080000
rdx=0000000000000008 rsi=fffffa8002a3a660 rdi=fffff88000ea0150
rip=fffff80002a84f40 rsp=fffff88002fd62f8 rbp=fffff88002fd6390
r8=0000000000000001 r9=fffff80002ac9ec0 r10=fffffffffffffffe
r11=fffff88002fd62f8 r12=0000057ffdfc0f78 r13=0000000000000000
r14=fffffa8003769490 r15=fffff88000e960f0
iopl=0 nv up ei pl nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00000202
nt!DbgBreakPoint:
fffff800`02a84f40 cc int 3
Resetting default scope

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x7E

PROCESS_NAME: System

CURRENT_IRQL: 0

ERROR_CODE: (NTSTATUS) 0x80000003 - {EXCEPTION} Breakpoint A breakpoint has been reached.

EXCEPTION_PARAMETER1: 0000000000000000

LAST_CONTROL_TRANSFER: from fffff88000e76a8b to fffff80002a84f40

STACK_TEXT:
fffff88002fd62f8 fffff88000e76a8b : fffff88000ea1308 fffffa8000ceb040 fffff88000ea0150 0000057ffdddef78 : nt!DbgBreakPoint
fffff88002fd6300 fffff88000e5ff26 : 0000057ffdddef78 0000000000000000 0000000000000000 0000000000000101 : Wdf01000!_FX_DRIVER_GLOBALS::WaitForSignal+0x53
fffff88002fd6350 fffff88000e5adbf : fffffa8002a3a660 0000000000000000 0000000000000101 0000000000000101 : Wdf01000!FxIoQueue::QueuePurgeSynchronously+0xd6
fffff88002fd63c0 fffff88002001d9b : fffffa8002221080 fffffa8003907380 0000000042727300 0000000000000004 : Wdf01000!imp_WdfIoQueuePurgeSynchronously+0x10b
fffff88002fd6410 fffff880020040c9 : 0000057ffdddef78 fffff880021c09d8 0000000000000000 0000000000000000 : BtPort!WdfIoQueuePurgeSynchronously+0x1b [c:\winddk\7600.16385.0\inc\wdf\kmdf\1.9\wdfio.h @ 980]
fffff88002fd6440 fffff88000eb36b6 : 0000057ffdfc0f78 fffff88002fd6538 0000000000000004 fffff88002fd6540 : BtPort!CsrBtPort_EvtDeviceSurpriseRemoval+0x89 [d:\harmony_test\rel_01_00\kernel\bt\csrbtport\csrbtportdriver\btport.c @ 1913]
fffff88002fd64a0 fffff88000e8878c : fffffa8001af2640 0000000000000127 0000000000000127 fffffa8001af2640 : Wdf01000!VfEvtDeviceSurpriseRemoval+0x5e
fffff88002fd64d0 fffff88000e87841 : 0000000000000127 fffff88002fd6630 0000000000000119 0000000000000000 : Wdf01000!FxPkgPnp::PnpEventSurpriseRemoveIoStarted+0x2c
fffff88002fd6500 fffff88000e874fe : fffffa8001af2640 fffff88002fd6630 0000000000000400 fffff88000e965f0 : Wdf01000!FxPkgPnp::PnpEnterNewState+0x1a5
fffff88002fd6570 fffff88000e87201 : 0000000000000000 0000000000000400 0000000000000000 fffffa8001af2640 : Wdf01000!FxPkgPnp::PnpProcessEventInner+0x122
fffff88002fd65e0 fffff88000e85e54 : 0000000000000000 fffffa8001af2640 0000000000000002 0000000000000000 : Wdf01000!FxPkgPnp::PnpProcessEvent+0x1b1
fffff88002fd6670 fffff88000e7ddd6 : fffffa8002a3a660 0000000000000002 0000000000000000 fffffa8001af2640 : Wdf01000!FxPkgFdo::_PnpSurpriseRemoval+0x28
fffff88002fd66a0 fffff88000e4d245 : fffff9800c58ecf0 fffff9800c58ecf0 fffffa8001dd35e0 0000000000000000 : Wdf01000!FxPkgPnp::Dispatch+0x1b2
fffff88002fd6710 fffff88000e4d14b : fffff88002fd67f8 fffff9800c58ecf0 0000000000000002 fffffa8001dd35e0 : Wdf01000!FxDevice::Dispatch+0xa9
fffff88002fd6740 fffff80002f32c16 : fffff9800c58ecf0 0000000000000002 fffffa8001dd35e0 fffff80002df86eb : Wdf01000!FxDevice::DispatchWithLock+0x93
fffff88002fd6780 fffff88005e019bc : fffffa8002b3dc50 fffff9800c58ecf0 fffffa8003080bb0 fffffa800309c2b0 : nt!IovCallDriver+0x566
fffff88002fd67e0 fffff88005e082b9 : fffffa8002b3dc50 fffff9800c58ecf0 fffffa80000054fc fffffa8003080bb0 : pnpfiltr+0x19bc
fffff88002fd6810 fffff88005e075c8 : fffff9800c58ecf0 fffff88005e00000 fffffa8003080bb0 fffffa8003524010 : pnpfiltr+0x82b9
fffff88002fd6840 fffff80002f32c16 : fffff9800c58ecf0 0000000000000002 fffffa8003080bb0 fffff88002fd6988 : pnpfiltr+0x75c8
fffff88002fd6870 fffff80002cf8419 : fffffa8003080bb0 00000000c00000bb fffff88002fd6988 fffffa8003524010 : nt!IovCallDriver+0x566
fffff88002fd68d0 fffff80002e76391 : fffffa8003769490 0000000000000000 fffffa800376a430 0000000000000000 : nt!IopSynchronousCall+0xc5
fffff88002fd6940 fffff80002e70e08 : 0000000000000010 fffffa8003769490 000000000000030a 0000000000000308 : nt!IopRemoveDevice+0x101
fffff88002fd6a00 fffff80002e75ed7 : fffffa800376a430 0000000000000000 0000000000000003 0000000000010246 : nt!PnpSurpriseRemoveLockedDeviceNode+0x128
fffff88002fd6a40 fffff80002e75ff0 : 0000000000000000 fffff8a001571b00 fffff8a0022c4080 000000004e706e50 : nt!PnpDeleteLockedDeviceNode+0x37
fffff88002fd6a70 fffff80002f05f6f : 0000000000000002 0000000000000000 fffffa800376a430 fffff8a001571b00 : nt!PnpDeleteLockedDeviceNodes+0xa0
fffff88002fd6ae0 fffff80002f06b2c : fffff88002fd6cb8 fffff80002cf8000 0000000000000000 0000000000000000 : nt!PnpProcessQueryRemoveAndEject+0x6cf
fffff88002fd6c20 fffff80002df1c48 : 0000000000000000 fffffa800222b300 fffff8a001571b00 0000000000000001 : nt!PnpProcessTargetDeviceEvent+0x4c
fffff88002fd6c50 fffff80002a9a161 : fffff80002cf7fc0 fffff8a001571b00 fffff80002c305f8 0000000000000000 : nt! ?? ::NNGAKEGL::string'+0x5abab fffff88002fd6cb0 fffff80002d30166 : 0000000000000000 fffffa8000ceb040 0000000000000080 fffffa8000cce040 : nt!ExpWorkerThread+0x111 fffff88002fd6d40 fffff80002a6b486 : fffff880009e9180 fffffa8000ceb040 fffff880009f3f40 0000000000000000 : nt!PspSystemThreadStartup+0x5a fffff88002fd6d80 0000000000000000 : fffff88002fd7000 fffff88002fd1000 fffff88002fd4be0 00000000`00000000 : nt!KxStartSystemThread+0x16

FOLLOWUP_IP:
CsrBtPort!WdfIoQueuePurgeSynchronously+1b [c:\winddk\7600.16385.0\inc\wdf\kmdf\1.9\wdfio.h @ 980]
fffff880`02001d9b 4883c428 add rsp,28h

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: CsrBtPort!WdfIoQueuePurgeSynchronously+1b

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: CsrBtPort

IMAGE_NAME: CsrBtPort.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4cd284af

STACK_COMMAND: .cxr 0xfffff88002fd5910 ; kb

FAILURE_BUCKET_ID: X64_0x7E_VRF_CsrBtPort!WdfIoQueuePurgeSynchronously+1b

BUCKET_ID: X64_0x7E_VRF_CsrBtPort!WdfIoQueuePurgeSynchronously+1b

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

4

For this and the previous bugcheck, they are not really bugchecks. Look closely at the call stack

fffff88002fce0e8 fffff88000ec0289 : fffffa8003dae9b0 fffffa8001a147f0 fffffa8001a147f0 fffff88000f29f40 : nt!DbgBreakPoint

each one ends with a call to DbgBreakPoint(). IN KMDF land this means it is an intentional break into the debugger and you should run !wdfkd.wdflogdump and see why kmdf is breaking in (something is clearly not right)

d
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@csr.com
Sent: Sunday, November 28, 2010 9:36 PM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] BSOD on running CHAOS-WDF Preview test

Hi All,

I got one more bugcheck 7E while testing WDF Logo Tests. I am handling all the error cases for all the wdf functions which returns the status. But why I am getting a bug check in WdfUsbInterfaceGetConfiguredSettingIndex which doesnt have any status?

Somebody please help me with some suggestions for this one too…

0: kd> ! analyze -v
Bugcheck Analysis



SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffff80000003, The exception code that was not handled
Arg2: fffff80002a6df40, The address that the exception occurred at
Arg3: fffff88002fcdea8, Exception Record Address
Arg4: fffff88002fcd700, Context Record Address

Debugging Details:
------------------

Unable to open image file: C:\Program Files (x86)\Debugging Tools for Windows (x86)\sym\ntkrnlmp.exe\4A5BC6005dd000\ntkrnlmp.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files (x86)\Debugging Tools for Windows (x86)\sym\ntkrnlmp.exe\4A5BC6005dd000\ntkrnlmp.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files (x86)\Debugging Tools for Windows (x86)\sym\ntkrnlmp.exe\4A5BC6005dd000\ntkrnlmp.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files (x86)\Debugging Tools for Windows (x86)\sym\ntkrnlmp.exe\4A5BC6005dd000\ntkrnlmp.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files (x86)\Debugging Tools for Windows (x86)\sym\ntkrnlmp.exe\4A5BC6005dd000\ntkrnlmp.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files (x86)\Debugging Tools for Windows (x86)\sym\ntkrnlmp.exe\4A5BC6005dd000\ntkrnlmp.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files (x86)\Debugging Tools for Windows (x86)\sym\ntkrnlmp.exe\4A5BC6005dd000\ntkrnlmp.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files (x86)\Debugging Tools for Windows (x86)\sym\ntkrnlmp.exe\4A5BC6005dd000\ntkrnlmp.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files (x86)\Debugging Tools for Windows (x86)\sym\ntkrnlmp.exe\4A5BC6005dd000\ntkrnlmp.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files (x86)\Debugging Tools for Windows (x86)\sym\ntkrnlmp.exe\4A5BC6005dd000\ntkrnlmp.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files (x86)\Debugging Tools for Windows (x86)\sym\ntkrnlmp.exe\4A5BC6005dd000\ntkrnlmp.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files (x86)\Debugging Tools for Windows (x86)\sym\ntkrnlmp.exe\4A5BC6005dd000\ntkrnlmp.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files (x86)\Debugging Tools for Windows (x86)\sym\ntkrnlmp.exe\4A5BC6005dd000\ntkrnlmp.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files (x86)\Debugging Tools for Windows (x86)\sym\ntkrnlmp.exe\4A5BC6005dd000\ntkrnlmp.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files (x86)\Debugging Tools for Windows (x86)\sym\ntkrnlmp.exe\4A5BC6005dd000\ntkrnlmp.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files (x86)\Debugging Tools for Windows (x86)\sym\ntkrnlmp.exe\4A5BC6005dd000\ntkrnlmp.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files (x86)\Debugging Tools for Windows (x86)\sym\ntkrnlmp.exe\4A5BC6005dd000\ntkrnlmp.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files (x86)\Debugging Tools for Windows (x86)\sym\ntkrnlmp.exe\4A5BC6005dd000\ntkrnlmp.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files (x86)\Debugging Tools for Windows (x86)\sym\ntkrnlmp.exe\4A5BC6005dd000\ntkrnlmp.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files (x86)\Debugging Tools for Windows (x86)\sym\ntkrnlmp.exe\4A5BC6005dd000\ntkrnlmp.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files (x86)\Debugging Tools for Windows (x86)\sym\ntkrnlmp.exe\4A5BC6005dd000\ntkrnlmp.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files (x86)\Debugging Tools for Windows (x86)\sym\ntkrnlmp.exe\4A5BC6005dd000\ntkrnlmp.exe
The system cannot find the file specified.

EXCEPTION_CODE: (HRESULT) 0x80000003 (2147483651) - One or more arguments are invalid

FAULTING_IP:
nt!DbgBreakPoint+0
fffff80002a6df40 cc int 3<br><br>EXCEPTION_RECORD: fffff88002fcdea8 -- (.exr 0xfffff88002fcdea8)<br>ExceptionAddress: fffff80002a6df40 (nt!DbgBreakPoint)<br> ExceptionCode: 80000003 (Break instruction exception)<br> ExceptionFlags: 00000000<br>NumberParameters: 1<br> Parameter[0]: 0000000000000000<br><br>CONTEXT: fffff88002fcd700 -- (.cxr 0xfffff88002fcd700)<br>rax=0000000000000000 rbx=fffffa8003dae9b0 rcx=fffff88000f29f70<br>rdx=fffffa8001a147f0 rsi=fffffa8001a147e0 rdi=0000000000000000<br>rip=fffff80002a6df40 rsp=fffff88002fce0e8 rbp=0000057ffc251648<br> r8=fffffa8001a147f0 r9=fffff88000f29f40 r10=7efefefefeff6172<br>r11=fffffa8001a14690 r12=fffffa8004b31010 r13=0000057ffc6936e8<br>r14=0000057ffe607cb8 r15=0000057ffdfb58e8<br>iopl=0 nv up ei pl nz na pe nc<br>cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00000202<br>nt!DbgBreakPoint:<br>fffff80002a6df40 cc int 3
Resetting default scope

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x7E

PROCESS_NAME: System

CURRENT_IRQL: 0

ERROR_CODE: (NTSTATUS) 0x80000003 - {EXCEPTION} Breakpoint A breakpoint has been reached.

EXCEPTION_PARAMETER1: 0000000000000000

LOCK_ADDRESS: fffff80002c78400 – (!locks fffff80002c78400)

Resource @ nt!PiEngineLock (0xfffff80002c78400) Exclusively owned
Contention Count = 46
NumberOfExclusiveWaiters = 1
Threads: fffffa80018b9680-01<*>
Threads Waiting On Exclusive Access:
fffffa80018b7040

1 total locks, 1 locks currently held

PNP_TRIAGE:
Lock address : 0xfffff80002c78400
Thread Count : 1
Thread address: 0xfffffa80018b9680
Thread wait : 0x4f4a

LAST_CONTROL_TRANSFER: from fffff80002de4824 to fffff80002a75f00

STACK_TEXT:
fffff88002fce0e8 fffff88000ec0289 : fffffa8003dae9b0 fffffa8001a147f0 fffffa8001a147f0 fffff88000f29f40 : nt!DbgBreakPoint
fffff88002fce0f0 fffff88000eb6ebe : fffffa800389ca30 0000000000000001 0000000000000000 fffff88000f7fb10 : Wdf01000!FxUsbInterface::GetConfiguredSettingIndex+0x7d
fffff88002fce130 fffff88000f83b8f : fffffa8003dae9b0 0000000000000008 0000000000000001 fffff80002ab2ec0 : Wdf01000!imp_WdfUsbInterfaceGetConfiguredSettingIndex+0x82
fffff88002fce170 fffff88005bdbd9b : fffffa80030bed00 0000000000000000 fffff88000000000 0000057ffc251603 : wdftester!CvRegisterHookProvider+0x2b3d7
fffff88002fce1e0 fffff88005bdd1e3 : 0000057ffc251648 0000000000000000 fffff88045494348 00000000000007ff : srusb!WdfUsbInterfaceGetConfiguredSettingIndex+0x1b [c:\winddk\7600.16385.0\inc\wdf\kmdf\1.9\wdfusb.h @ 2278]
fffff88002fce210 fffff88005bdce09 : 0000057ffc6936e8 fffffa8002cd8790 fffff88002fce318 00000000000000c1 : srusb!SelectInterfaces+0x3b3 [sys\srbc_device.c @ 894]
fffff88002fce2e0 fffff88005bdcca9 : 0000057ffc6936e8 fffffa800396cc80 fffffa800396cca0 0000000000000000 : srusb!ConfigureDevice+0x129 [sys\srbc_device.c @ 770]
fffff88002fce380 fffff88005bdc5a8 : 0000057ffc6936e8 fffff80000000002 fffff88005be4190 0000000000000000 : srusb!ReadAndSelectDescriptors+0x149 [\sys\srbc_device.c @ 686]
fffff88002fce3c0 fffff88000f3eedf : 0000057ffc6936e8 0000057ffdfb58e8 0000057ffe607cb8 0000000000000000 : srusb!srBc_EvtDevicePrepareHardware+0x48 [sys\srbc_device.c @ 364]
fffff88002fce440 fffff88000f14cfe : fffffa8003010780 0000000000000000 fffff88002fce510 fffffa8003010780 : Wdf01000!VfEvtDevicePrepareHardware+0x6f
fffff88002fce490 fffff88000f139ce : fffffa8001f1ab20 0000000000000108 0000000000000000 0000000000000000 : Wdf01000!FxPkgPnp::PnpPrepareHardware+0x8e
fffff88002fce4d0 fffff88000f13841 : 0000000000000101 0000000000000108 0000000000000108 fffff80002a34c00 : Wdf01000!FxPkgPnp::PnpEventHardwareAvailable+0x9a
fffff88002fce510 fffff88000f134fe : fffffa8003010780 fffff88002fce640 0000000000000004 fffff88000f22390 : Wdf01000!FxPkgPnp::PnpEnterNewState+0x1a5
fffff88002fce580 fffff88000f13201 : 0000000000000000 0000000000000002 0000000000000000 fffffa8003010780 : Wdf01000!FxPkgPnp::PnpProcessEventInner+0x122
fffff88002fce5f0 fffff88000f0ad9c : 0000000000000000 fffffa8003010780 fffffa8002a7a1b0 0000000000000000 : Wdf01000!FxPkgPnp::PnpProcessEvent+0x1b1
fffff88002fce680 fffff88000f09dd6 : fffffa8001a14690 fffffa8002a7a1b0 0000000000000000 fffffa8003010780 : Wdf01000!FxPkgPnp::_PnpStartDevice+0x20
fffff88002fce6b0 fffff88000ed9245 : fffffa8001ad7910 fffffa8001ad7910 fffffa8001f1ab20 fffff80002b73cd0 : Wdf01000!FxPkgPnp::Dispatch+0x1b2
fffff88002fce720 fffff88000ed914b : 0000000000000005 fffffa8001ad7910 fffffa8002a7a1b0 fffffa8001f1ab20 : Wdf01000!FxDevice::Dispatch+0xa9
fffff88002fce750 fffff80002e33bde : fffffa8001ad7910 fffffa8002a7a1b0 fffffa8001f1ab20 fffff80002beee80 : Wdf01000!FxDevice::DispatchWithLock+0x93
fffff88002fce790 fffff80002b6e0ed : fffffa8003723060 fffffa8002a7a1b0 fffff80002b73cd0 0000000000000000 : nt!PnpAsynchronousCall+0xce
fffff88002fce7d0 fffff80002e3e926 : fffff80002c781c0 fffffa8003493d90 fffffa8002a7a1b0 fffffa8003493f38 : nt!PnpStartDevice+0x11d
fffff88002fce890 fffff80002e3ebc4 : fffffa8003493d90 fffffa8003490024 fffffa8003493d90 0000000000000001 : nt!PnpStartDeviceNode+0x156
fffff88002fce920 fffff80002e61ea6 : fffffa8003493d90 fffffa8003493d90 0000000000000000 0000000000000000 : nt!PipProcessStartPhase1+0x74
fffff88002fce950 fffff80002e62297 : fffffa8003493d90 0000000000000000 0000000000000001 fffff80002ce271c : nt!PipProcessDevNodeTree+0x296
fffff88002fcebc0 fffff80002b76333 : 0000000100000003 0000000000000000 0000000000000001 0000000000000000 : nt!PiRestartDevice+0xc7
fffff88002fcec10 fffff80002a83161 : fffff80002b76020 fffff80002b76001 fffff80002c19500 0000000000000000 : nt!PnpDeviceActionWorker+0x313
fffff88002fcecb0 fffff80002d19166 : 0000000000000000 fffffa80018b9680 0000000000000080 fffffa80018a6040 : nt!ExpWorkerThread+0x111
fffff88002fced40 fffff80002a54486 : fffff880009e9180 fffffa80018b9680 fffff880009f3f40 0000000000000000 : nt!PspSystemThreadStartup+0x5a
fffff88002fced80 0000000000000000 : fffff88002fcf000 fffff88002fc9000 fffff88002fcdc50 0000000000000000 : nt!KxStartSystemThread+0x16

FOLLOWUP_IP:
wdftester!CvRegisterHookProvider+2b3d7
fffff880`00f83b8f 88842480000000 mov byte ptr [rsp+80h],al

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: wdftester!CvRegisterHookProvider+2b3d7

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: wdftester

IMAGE_NAME: wdftester.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4b07ad7e

STACK_COMMAND: .cxr 0xfffff88002fcd700 ; kb

FAILURE_BUCKET_ID: X64_0x7E_wdftester!CvRegisterHookProvider+2b3d7

BUCKET_ID: X64_0x7E_wdftester!CvRegisterHookProvider+2b3d7

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

5

Thank you doron. I used !wdfkd.wdflogdump as you suggested. I found out the issue

With out checking the status WdfUsbTargetDeviceSelectConfig was returning I was using GetConfiguredSettingIndex which caused the problem.

6

Are you running prefast against your code? It would indicate a problem
like this (not checking function’s result) since
WdfUsbTargetDeviceSelectConfig is decorated with __checkReturn
annotation.

Kris

On Wed, Dec 1, 2010 at 6:55 AM, wrote:
> Thank you doron. I used !wdfkd.wdflogdump as you suggested. I found out the issue
>
> With out checking the status WdfUsbTargetDeviceSelectConfig was returning I was using GetConfiguredSettingIndex which caused the problem.
>
> —
> 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
>