Prev: StorPortAllocatePool
Next: Mirror Driver Installation
From: hammerli22 on 19 Dec 2007 01:26
I have Wdf,DbgBreakOnError,0x00010001,1 turned on and when
my driver loads the very first thing it does is break into the debugger,
at first I thought that was normal in that when you hook up the debugger
it automatically breaks into the debugger, but then i realized I did not call
WdfVerifierDbgBreakPoint, instead its breaking into the debug because
of an exception, but the bugcheck code is 0. Any ideas ? If i hit 'g'
everthing runs normally.

thanks in advance

1: kd> !analyze -v
Connected to Windows 6001 Intel IA64 target, ptr64 TRUE
Loading Kernel Symbols
..........................................................................................................................
Loading User Symbols

Loading unloaded module list
.......
*** ERROR: Module load completed but symbols could not be loaded for
Wdf01000.sys
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************

Unknown bugcheck code (0)
Unknown bugcheck description
Arguments:
Arg1: 0000000000000000
Arg2: 0000000000000000
Arg3: 0000000000000000
Arg4: 0000000000000000

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






PROCESS_NAME: System

FAULTING_IP:
nt!DbgBreakPoint+8 [d:\longhorn_rc0\base\ntos\rtl\mp\debugstb.s @ 66]
e0000000`88201988 break.i 0x80016

EXCEPTION_RECORD: ffffffffffffffff -- (.exr 0xffffffffffffffff)
ExceptionAddress: e000000088201988 (nt!DbgBreakPoint+0x0000000000000008)
ExceptionCode: 80000003 (Break instruction exception)
ExceptionFlags: 00000000
NumberParameters: 5
Parameter[0]: 0000000000080016
Parameter[1]: 0000000000000000
Parameter[2]: 0000000000000000
Parameter[3]: e000000088201980
Parameter[4]: 0000040000000000

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

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x0

CURRENT_IRQL: 0

LOCK_ADDRESS: e000000088556ca0 -- (!locks e000000088556ca0)

Resource @ nt!PiEngineLock (0xe000000088556ca0) Exclusively owned
Contention Count = 5
Threads: e000012661eb3b60-01<*>
1 total locks, 1 locks currently held

PNP_TRIAGE:
Lock address : 0xe000000088556ca0
Thread Count : 1
Thread address: 0xe000012661eb3b60
Thread wait : 0x61f6

LAST_CONTROL_TRANSFER: from e0000106015e35e0 to e000000088201988

STACK_TEXT:
e0000106`07557680 e0000106`075585d8 e0000106`015e35e0 : e0000106`016eda90
e0000126`6659a9d0 e0000106`016ed9e0 e0000106`075576e0 : nt!DbgBreakPoint+0x8
[d:\longhorn_rc0\base\ntos\rtl\mp\debugstb.s @ 66]
e0000106`07557680 e0000106`075585d8 e0000106`995dcef0 : e0000126`6659a9c0
e0000106`07557888 e0000106`075576e0 00000000`c020020f : Wdf01000+0x3d5e0
e0000106`07557680 e0000106`07558560 e0000106`995dd9f0 : e0000106`07557888
e0000106`075576e0 e0000106`995dd9f0 00000000`0000028b :
xxxxxx!WdfDeviceInitSetRequestAttributes+0x90
[c:\winddk\6000\inc\wdf\kmdf\10\wdfdevice.h @ 2262]
e0000106`07557690 e0000106`07558538 e0000106`0163a210 : 1ffffed9`99b3c728
e0000106`07557888 e0000106`0163a210 00000000`00000c9d :
xxxxxx!IpmiEvtDriverDeviceAdd+0x1f0 [c:\dev\xxxxdrv\src\xxxxdrv.c @ 248]
e0000106`07557870 e0000106`07558470 e0000106`016395e0 : ffffffff`ffffff7f
e0000106`07557b30 e0000126`664c3968 ffffffff`c0000001 : Wdf01000+0x94210
e0000106`07557bf0 e0000106`07558450 e0000000`883f5a30 : e0000126`6514ab10
e0000126`622fe3a0 e0000000`883f5a30 00000000`0000040d : Wdf01000+0x935e0
e0000106`07557bf0 e0000106`07558410 e0000000`889a44a0 : e0000126`622fe3a0
e0000126`6514ab10 e0000106`016ce010 00000000`00000004 :
nt!PpvUtilCallAddDevice+0x60 [d:\longhorn_rc0\base\ntos\io\pnpmgr\verifier.c
@ 75]
e0000106`07557bf0 e0000106`075583c8 e0000000`889d0720 : 00000000`00000000
e0000126`6514ab10 e0000106`016ce010 00000000`00000002 :
nt!PnpCallAddDevice+0x120 [d:\longhorn_rc0\base\ntos\io\pnpmgr\enum.c @ 5507]
e0000106`07557c00 e0000106`07558310 e0000000`889d2230 : e0000126`62308ef0
00000000`00000000 e0000126`622fe3a0 e0000126`622fe3a0 :
nt!PipCallDriverAddDevice+0x9f0 [d:\longhorn_rc0\base\ntos\io\pnpmgr\enum.c @
2182]
e0000106`07557d40 e0000106`07558208 e0000000`889d2b10 : e0000106`07557f00
e0000126`65144e10 e0000106`07557f10 00000000`00000000 :
nt!PipProcessDevNodeTree+0x2c0 [d:\longhorn_rc0\base\ntos\io\pnpmgr\enum.c @
4232]
e0000106`07557f00 e0000106`075581d8 e0000000`883f89e0 : e0000126`65144e10
e0000126`62308ef0 e0000106`07557f10 e0000000`883f89e0 :
nt!PiRestartDevice+0x240 [d:\longhorn_rc0\base\ntos\io\pnpmgr\enum.c @ 3103]
e0000106`07557f10 e0000106`07558140 e0000000`8816cb30 : 00000000`00000003
00000000`00000000 e0000126`65144e10 e0000106`07557f20 :
nt!PnpDeviceActionWorker+0x3e0 [d:\longhorn_rc0\base\ntos\io\pnpmgr\action.c
@ 559]
e0000106`07557f20 e0000106`07558070 e0000000`88656d40 : e0000000`8813e0a0
00000000`00000000 e0000126`61eb3b60 00000000`00000000 :
nt!ExpWorkerThread+0x270 [d:\longhorn_rc0\base\ntos\ex\worker.c @ 1191]
e0000106`07557f30 e0000106`07558010 e0000000`88201250 : e0000000`8813e1f8
00000000`00000001 e0000106`07557f40 e0000126`61eb3b60 :
nt!PspSystemThreadStartup+0x100 [d:\longhorn_rc0\base\ntos\ps\psexec.c @ 5185]
e0000106`07557f50 e0000106`07558000 00000000`00000000 : 00000000`00000000
00000000`00000000 e0000000`8813e1f8 00000000`00000001 :
nt!KiThreadStartup+0x70 [d:\longhorn_rc0\base\ntos\ke\mp\threadbg.s @ 245]


STACK_COMMAND: kb

FOLLOWUP_IP:
xxxxxx!WdfDeviceInitSetRequestAttributes+90
[c:\winddk\6000\inc\wdf\kmdf\10\wdfdevice.h @ 2262]
e0000106`995dcef0 adds gp = 0,r36 ;;

FAULTING_SOURCE_CODE:
2258: __in
2259: PWDF_OBJECT_ATTRIBUTES RequestAttributes
2260: )
2261: {
> 2262: ((PFN_WDFDEVICEINITSETREQUESTATTRIBUTES) WdfFunctions[WdfDeviceInitSetRequestAttributesTableIndex])(WdfDriverGlobals, DeviceInit, RequestAttributes);
2263: }
2264:
2265: //
2266: // WDF Function: WdfDeviceInitAssignWdmIrpPreprocessCallback
2267: //


SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: xxxxxi!WdfDeviceInitSetRequestAttributes+90

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: xxxxxx

IMAGE_NAME: xxxxxx.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4768b5a9

FAILURE_BUCKET_ID: IA64_0x0_xxxxxx!WdfDeviceInitSetRequestAttributes+90

BUCKET_ID: IA64_0x0_xxxxxx!WdfDeviceInitSetRequestAttributes+90

Followup: MachineOwner
---------

From: Doron Holan [MSFT] on 19 Dec 2007 13:20
fix your symbols (.symfix in the debugger) and then send the stack. once
you do that, !wdflogdump <your driver name> will tell you why there was a
break. something was wrong with the WDF_OBJECT_ATTRIBUTES you passed in.

d

--
Please do not send e-mail directly to this alias. this alias is for
newsgroup purposes only.
This posting is provided "AS IS" with no warranties, and confers no rights.


"hammerli22" <hammerli22(a)discussions.microsoft.com> wrote in message
news:04D3FC67-DD3D-4E6B-8BF9-A4AB054678F3(a)microsoft.com...
>I have Wdf,DbgBreakOnError,0x00010001,1 turned on and when
> my driver loads the very first thing it does is break into the debugger,
> at first I thought that was normal in that when you hook up the debugger
> it automatically breaks into the debugger, but then i realized I did not
> call
> WdfVerifierDbgBreakPoint, instead its breaking into the debug because
> of an exception, but the bugcheck code is 0. Any ideas ? If i hit 'g'
> everthing runs normally.
>
> thanks in advance
>
> 1: kd> !analyze -v
> Connected to Windows 6001 Intel IA64 target, ptr64 TRUE
> Loading Kernel Symbols
> .........................................................................................................................
> Loading User Symbols
>
> Loading unloaded module list
> ......
> *** ERROR: Module load completed but symbols could not be loaded for
> Wdf01000.sys
> *******************************************************************************
> *
> *
> * Bugcheck Analysis
> *
> *
> *
> *******************************************************************************
>
> Unknown bugcheck code (0)
> Unknown bugcheck description
> Arguments:
> Arg1: 0000000000000000
> Arg2: 0000000000000000
> Arg3: 0000000000000000
> Arg4: 0000000000000000
>
> Debugging Details:
> ------------------
>
>
>
>
>
>
> PROCESS_NAME: System
>
> FAULTING_IP:
> nt!DbgBreakPoint+8 [d:\longhorn_rc0\base\ntos\rtl\mp\debugstb.s @ 66]
> e0000000`88201988 break.i 0x80016
>
> EXCEPTION_RECORD: ffffffffffffffff -- (.exr 0xffffffffffffffff)
> ExceptionAddress: e000000088201988 (nt!DbgBreakPoint+0x0000000000000008)
> ExceptionCode: 80000003 (Break instruction exception)
> ExceptionFlags: 00000000
> NumberParameters: 5
> Parameter[0]: 0000000000080016
> Parameter[1]: 0000000000000000
> Parameter[2]: 0000000000000000
> Parameter[3]: e000000088201980
> Parameter[4]: 0000040000000000
>
> ERROR_CODE: (NTSTATUS) 0x80000003 - {EXCEPTION} Breakpoint A breakpoint
> has been reached.
>
> DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
>
> BUGCHECK_STR: 0x0
>
> CURRENT_IRQL: 0
>
> LOCK_ADDRESS: e000000088556ca0 -- (!locks e000000088556ca0)
>
> Resource @ nt!PiEngineLock (0xe000000088556ca0) Exclusively owned
> Contention Count = 5
> Threads: e000012661eb3b60-01<*>
> 1 total locks, 1 locks currently held
>
> PNP_TRIAGE:
> Lock address : 0xe000000088556ca0
> Thread Count : 1
> Thread address: 0xe000012661eb3b60
> Thread wait : 0x61f6
>
> LAST_CONTROL_TRANSFER: from e0000106015e35e0 to e000000088201988
>
> STACK_TEXT:
> e0000106`07557680 e0000106`075585d8 e0000106`015e35e0 : e0000106`016eda90
> e0000126`6659a9d0 e0000106`016ed9e0 e0000106`075576e0 :
> nt!DbgBreakPoint+0x8
> [d:\longhorn_rc0\base\ntos\rtl\mp\debugstb.s @ 66]
> e0000106`07557680 e0000106`075585d8 e0000106`995dcef0 : e0000126`6659a9c0
> e0000106`07557888 e0000106`075576e0 00000000`c020020f : Wdf01000+0x3d5e0
> e0000106`07557680 e0000106`07558560 e0000106`995dd9f0 : e0000106`07557888
> e0000106`075576e0 e0000106`995dd9f0 00000000`0000028b :
> xxxxxx!WdfDeviceInitSetRequestAttributes+0x90
> [c:\winddk\6000\inc\wdf\kmdf\10\wdfdevice.h @ 2262]
> e0000106`07557690 e0000106`07558538 e0000106`0163a210 : 1ffffed9`99b3c728
> e0000106`07557888 e0000106`0163a210 00000000`00000c9d :
> xxxxxx!IpmiEvtDriverDeviceAdd+0x1f0 [c:\dev\xxxxdrv\src\xxxxdrv.c @ 248]
> e0000106`07557870 e0000106`07558470 e0000106`016395e0 : ffffffff`ffffff7f
> e0000106`07557b30 e0000126`664c3968 ffffffff`c0000001 : Wdf01000+0x94210
> e0000106`07557bf0 e0000106`07558450 e0000000`883f5a30 : e0000126`6514ab10
> e0000126`622fe3a0 e0000000`883f5a30 00000000`0000040d : Wdf01000+0x935e0
> e0000106`07557bf0 e0000106`07558410 e0000000`889a44a0 : e0000126`622fe3a0
> e0000126`6514ab10 e0000106`016ce010 00000000`00000004 :
> nt!PpvUtilCallAddDevice+0x60
> [d:\longhorn_rc0\base\ntos\io\pnpmgr\verifier.c
> @ 75]
> e0000106`07557bf0 e0000106`075583c8 e0000000`889d0720 : 00000000`00000000
> e0000126`6514ab10 e0000106`016ce010 00000000`00000002 :
> nt!PnpCallAddDevice+0x120 [d:\longhorn_rc0\base\ntos\io\pnpmgr\enum.c @
> 5507]
> e0000106`07557c00 e0000106`07558310 e0000000`889d2230 : e0000126`62308ef0
> 00000000`00000000 e0000126`622fe3a0 e0000126`622fe3a0 :
> nt!PipCallDriverAddDevice+0x9f0
> [d:\longhorn_rc0\base\ntos\io\pnpmgr\enum.c @
> 2182]
> e0000106`07557d40 e0000106`07558208 e0000000`889d2b10 : e0000106`07557f00
> e0000126`65144e10 e0000106`07557f10 00000000`00000000 :
> nt!PipProcessDevNodeTree+0x2c0 [d:\longhorn_rc0\base\ntos\io\pnpmgr\enum.c
> @
> 4232]
> e0000106`07557f00 e0000106`075581d8 e0000000`883f89e0 : e0000126`65144e10
> e0000126`62308ef0 e0000106`07557f10 e0000000`883f89e0 :
> nt!PiRestartDevice+0x240 [d:\longhorn_rc0\base\ntos\io\pnpmgr\enum.c @
> 3103]
> e0000106`07557f10 e0000106`07558140 e0000000`8816cb30 : 00000000`00000003
> 00000000`00000000 e0000126`65144e10 e0000106`07557f20 :
> nt!PnpDeviceActionWorker+0x3e0
> [d:\longhorn_rc0\base\ntos\io\pnpmgr\action.c
> @ 559]
> e0000106`07557f20 e0000106`07558070 e0000000`88656d40 : e0000000`8813e0a0
> 00000000`00000000 e0000126`61eb3b60 00000000`00000000 :
> nt!ExpWorkerThread+0x270 [d:\longhorn_rc0\base\ntos\ex\worker.c @ 1191]
> e0000106`07557f30 e0000106`07558010 e0000000`88201250 : e0000000`8813e1f8
> 00000000`00000001 e0000106`07557f40 e0000126`61eb3b60 :
> nt!PspSystemThreadStartup+0x100 [d:\longhorn_rc0\base\ntos\ps\psexec.c @
> 5185]
> e0000106`07557f50 e0000106`07558000 00000000`00000000 : 00000000`00000000
> 00000000`00000000 e0000000`8813e1f8 00000000`00000001 :
> nt!KiThreadStartup+0x70 [d:\longhorn_rc0\base\ntos\ke\mp\threadbg.s @ 245]
>
>
> STACK_COMMAND: kb
>
> FOLLOWUP_IP:
> xxxxxx!WdfDeviceInitSetRequestAttributes+90
> [c:\winddk\6000\inc\wdf\kmdf\10\wdfdevice.h @ 2262]
> e0000106`995dcef0 adds gp = 0,r36 ;;
>
> FAULTING_SOURCE_CODE:
> 2258: __in
> 2259: PWDF_OBJECT_ATTRIBUTES RequestAttributes
> 2260: )
> 2261: {
>> 2262: ((PFN_WDFDEVICEINITSETREQUESTATTRIBUTES)
>> WdfFunctions[WdfDeviceInitSetRequestAttributesTableIndex])(WdfDriverGlobals,
>> DeviceInit, RequestAttributes);
> 2263: }
> 2264:
> 2265: //
> 2266: // WDF Function: WdfDeviceInitAssignWdmIrpPreprocessCallback
> 2267: //
>
>
> SYMBOL_STACK_INDEX: 2
>
> SYMBOL_NAME: xxxxxi!WdfDeviceInitSetRequestAttributes+90
>
> FOLLOWUP_NAME: MachineOwner
>
> MODULE_NAME: xxxxxx
>
> IMAGE_NAME: xxxxxx.sys
>
> DEBUG_FLR_IMAGE_TIMESTAMP: 4768b5a9
>
> FAILURE_BUCKET_ID: IA64_0x0_xxxxxx!WdfDeviceInitSetRequestAttributes+90
>
> BUCKET_ID: IA64_0x0_xxxxxx!WdfDeviceInitSetRequestAttributes+90
>
> Followup: MachineOwner
> ---------
>

 | 
Pages: 1
Prev: StorPortAllocatePool
Next: Mirror Driver Installation