Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.

Dismiss

Explain WinDbg info please

48 views

Skip to first unread message

May

unread,

Jun 12, 2008, 6:34:01 PM6/12/08

Hello,
I got the following debug info regarding to a fatal error caused by my
driver. I don't understand where is wrong since this part of the code running
fine with my Windows 2003 server driver. The only different is that the new
driver using MSI interrupt and run on Windows Vista. The procedure is this:
1. In my IOCTL function, I forward the request to a waiting queue and return
since I need to wait for DMA interrupt.
2. In interrupt DPC, I call WdfIoQueueRetrieveNextRequest to get the request
from wait queue and call WdfRequestCompleteWithInformation to complete this
request.
But this WdfRequestCompleteWithInformation cause fatal error. Why?
The buffer is from user as output buffer. What is the meaning here for
"outstanding references"?
Could anyone tell me what is wrong from the following message?

Thanks,
May

----------------------------------------------------------------------------------
<----ccpWinDrv---:: ***Return from dmaWait 1, reqCount=0, req=0x7abf8e90, ***

*** Fatal System Error: 0x0000010d
(0x00000003,0x7ABF8E90,0x00000001,0x872C1168)

Break instruction exception - code 80000003 (first chance)

A fatal system error has occurred.
Debugger entered on first try; Bugcheck callbacks have not been invoked.

A fatal system error has occurred.

Connected to Windows Server 2008 6001 x86 compatible target, ptr64 FALSE
Loading Kernel Symbols
.......................................................................................................................................................................................
Loading User Symbols
...............
Loading unloaded module list
......
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 10D, {3, 7abf8e90, 1, 872c1168}

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: kernel32!pNlsUserInfo ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: kernel32!pNlsUserInfo ***
*** ***
*************************************************************************
Probably caused by : CCADCCP.sys (
CCADCCP!WdfRequestCompleteWithInformation+1d )

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

nt!RtlpBreakWithStatusInstruction:
8196b66c cc int 3
0: kd> !analyze -v
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************

WDF_VIOLATION (10d)
The Kernel-Mode Driver Framework has detected that Windows detected an error
in a framework-based driver. In general, the dump file will yield additional
information about the driver that caused this bug check.
Arguments:
Arg1: 00000003, Windows Driver Framework Verifier has encountered a fatal
error.
In particular, an I/O request has been completed, but a framework
request object cannot be deleted because there are outstanding
references to the input buffer or the output buffer, or both. The
driver's IFR will include details on the outstanding references.
Arg2: 7abf8e90, WDFREQUEST handle
Arg3: 00000001, The number of outstanding references remaining on both
buffers.
Arg4: 872c1168, Reserved.

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

BUGCHECK_STR: 0x10D_3

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: ccpTest.exe

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from 81842a72 to 8196b66c

STACK_TEXT:
8039da4c 81842a72 00000003 8e6be1dc 00000065 nt!RtlpBreakWithStatusInstruction
8039da9c 8184353b 00000003 00000000 85407168 nt!KiBugCheckDebugBreak+0x1c
8039de60 8184291c 0000010d 00000003 7abf8e90 nt!KeBugCheck2+0x67f
8039de80 82232340 0000010d 00000003 7abf8e90 nt!KeBugCheckEx+0x1e
8039de9c 822368ef 872c1168 00000003 7abf8e90 Wdf01000!FxVerifierBugCheck+0x24
8039ded4 8223960f 0e000000 7abf8e21 872c1168
Wdf01000!FxRequest::CompleteInternal+0x57a
8039def8 82239633 00000000 00000000 8039df24 Wdf01000!FxRequest::Complete+0xfc
8039df08 82220d43 00000000 00000000 8199fc20
Wdf01000!FxRequest::CompleteWithInformation+0x18
8039df24 8cdc9c7d 85407168 7abf8e90 00000000
Wdf01000!imp_WdfRequestCompleteWithInformation+0x7f
8039df3c 8cdca2e2 7abf8e90 00000000 00000000
CCADCCP!WdfRequestCompleteWithInformation+0x1d
[c:\winddk\6001.18001\inc\wdf\kmdf\1.7\wdfrequest.h @ 949]
8039df64 8cdc958a 8737b8d0 8199fc20 00000000 CCADCCP!CcpDpcDmaWaitQueue+0xa2
[c:\dev\keyserver\ccp\winccpdriver\sys\ccpwininit.c @ 901]
8039df90 8184e641 8737b8f0 85146038 00000000 CCADCCP!CcpInterruptDpc+0x1ea
[c:\dev\keyserver\ccp\winccpdriver\sys\ccpwindrv.c @ 689]
8039dff4 8197b155 a55bfafc 00000000 00000000 nt!KiRetireDpcList+0x167
8039dff8 a55bfafc 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x45
WARNING: Frame IP not in any known module. Following frames may be wrong.
8197b155 00000000 0000001b 00c7850f bb830000 0xa55bfafc

STACK_COMMAND: kb

FOLLOWUP_IP:
CCADCCP!WdfRequestCompleteWithInformation+1d
[c:\winddk\6001.18001\inc\wdf\kmdf\1.7\wdfrequest.h @ 949]
8cdc9c7d 5d pop ebp

FAULTING_SOURCE_CODE:
945: ULONG_PTR Information
946: )
947: {
948: ((PFN_WDFREQUESTCOMPLETEWITHINFORMATION)
WdfFunctions[WdfRequestCompleteWithInformationTableIndex])(WdfDriverGlobals,
Request, Status, Information);
> 949: }
950:
951: //
952: // WDF Function: WdfRequestGetParameters
953: //
954: typedef

SYMBOL_STACK_INDEX: 9

SYMBOL_NAME: CCADCCP!WdfRequestCompleteWithInformation+1d

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: CCADCCP

IMAGE_NAME: CCADCCP.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 48519424

FAILURE_BUCKET_ID: 0x10D_3_CCADCCP!WdfRequestCompleteWithInformation+1d

BUCKET_ID: 0x10D_3_CCADCCP!WdfRequestCompleteWithInformation+1d

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

0: kd> !C:\WinDDK\6001.18001\bin\x86\wdfkd.wdftmffile
C:\WinDDK\6001.18001\tools\tracing\i386\wdf01007.tmf
Set TMF file name is : 'C:\WinDDK\6001.18001\tools\tracing\i386\wdf01007.tmf'
0: kd> !C:\WinDDK\6001.18001\bin\x86\wdfkd.wdflogdump ccadccp
*** ERROR: Module load completed but symbols could not be loaded for spldr.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
igdkmd32.sys -
*** ERROR: Module load completed but symbols could not be loaded for HECI.sys
*** ERROR: Module load completed but symbols could not be loaded for
ADIHdAud.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
drmk.sys -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
spsys.sys -
*** ERROR: Module load completed but symbols could not be loaded for
secdrv.SYS
Trace searchpath is:

Trace format prefix is: %7!u!: %!FUNC! -
TMF file used for formatting IFR log is:
C:\WinDDK\6001.18001\tools\tracing\i386\wdf01007.tmf
Log at 87346000
Gather log: Please wait, this may take a moment (reading 4032 bytes).
% read so far ... 10, 20, 100
There are 27 log entries
--- start of log ---
1: FxPkgPnp::PnpEnterNewState - WDFDEVICE 0x78C848F0 !devobj 0x8737B4C8
entering PnP State WdfDevStatePnpInit from WdfDevStatePnpObjectCreated
2: FxPkgPnp::Dispatch - WDFDEVICE 0x78C848F0 !devobj 0x8737B4C8, IRP_MJ_PNP,
0x00000000(IRP_MN_START_DEVICE) IRP 0x8737E008
3: FxPkgPnp::PnpEnterNewState - WDFDEVICE 0x78C848F0 !devobj 0x8737B4C8
entering PnP State WdfDevStatePnpInitStarting from WdfDevStatePnpInit
4: FxPkgPnp::PnpEnterNewState - WDFDEVICE 0x78C848F0 !devobj 0x8737B4C8
entering PnP State WdfDevStatePnpHardwareAvailable from
WdfDevStatePnpInitStarting
5: FxPkgPnp::PnpMatchResources - Not enough interrupt objects created by
WDFDEVICE 0x78C848F0
6: FxPkgPnp::PowerPolicyEnterNewState - WDFDEVICE 0x78C848F0 !devobj
0x8737B4C8 entering power policy state WdfDevStatePwrPolStarting from
WdfDevStatePwrPolObjectCreated
7: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x78C848F0 !devobj
0x8737B4C8 entering power idle state FxIdleStarted from FxIdleStopped
8: FxPkgPnp::PowerEnterNewState - WDFDEVICE 0x78C848F0 !devobj 0x8737B4C8
entering Power State WdfDevStatePowerStartingCheckDeviceType from
WdfDevStatePowerObjectCreated
9: FxPkgPnp::PowerEnterNewState - WDFDEVICE 0x78C848F0 !devobj 0x8737B4C8
entering Power State WdfDevStatePowerD0Starting from
WdfDevStatePowerStartingCheckDeviceType
10: FxPkgPnp::PowerEnterNewState - WDFDEVICE 0x78C848F0 !devobj 0x8737B4C8
entering Power State WdfDevStatePowerD0StartingConnectInterrupt from
WdfDevStatePowerD0Starting
11: FxPkgPnp::PowerEnterNewState - WDFDEVICE 0x78C848F0 !devobj 0x8737B4C8
entering Power State WdfDevStatePowerD0StartingDmaEnable from
WdfDevStatePowerD0StartingConnectInterrupt
12: FxPkgPnp::PowerEnterNewState - WDFDEVICE 0x78C848F0 !devobj 0x8737B4C8
entering Power State WdfDevStatePowerD0StartingStartSelfManagedIo from
WdfDevStatePowerD0StartingDmaEnable
13: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x78C848F0 !devobj
0x8737B4C8 entering power idle state FxIdleStartedPowerUp from FxIdleStarted
14: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x78C848F0 !devobj
0x8737B4C8 entering power idle state FxIdleDisabled from FxIdleStartedPowerUp
15: FxPkgPnp::PowerEnterNewState - WDFDEVICE 0x78C848F0 !devobj 0x8737B4C8
entering Power State WdfDevStatePowerDecideD0State from
WdfDevStatePowerD0StartingStartSelfManagedIo
16: FxPkgPnp::PowerEnterNewState - WDFDEVICE 0x78C848F0 !devobj 0x8737B4C8
entering Power State WdfDevStatePowerD0 from WdfDevStatePowerDecideD0State
17: FxPkgPnp::PowerPolicyEnterNewState - WDFDEVICE 0x78C848F0 !devobj
0x8737B4C8 entering power policy state WdfDevStatePwrPolStartingSucceeded
from WdfDevStatePwrPolStarting
18: FxPkgPnp::PowerPolicyEnterNewState - WDFDEVICE 0x78C848F0 !devobj
0x8737B4C8 entering power policy state WdfDevStatePwrPolStartingDecideS0Wake
from WdfDevStatePwrPolStartingSucceeded
19: FxPkgPnp::PowerPolicyEnterNewState - WDFDEVICE 0x78C848F0 !devobj
0x8737B4C8 entering power policy state WdfDevStatePwrPolStarted from
WdfDevStatePwrPolStartingDecideS0Wake
20: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x78C848F0 !devobj
0x8737B4C8 entering power idle state FxIdleDisabled from FxIdleDisabled
21: FxPkgPnp::PnpEnterNewState - WDFDEVICE 0x78C848F0 !devobj 0x8737B4C8
entering PnP State WdfDevStatePnpEnableInterfaces from
WdfDevStatePnpHardwareAvailable
22: FxPkgPnp::PnpEnterNewState - WDFDEVICE 0x78C848F0 !devobj 0x8737B4C8
entering PnP State WdfDevStatePnpStarted from WdfDevStatePnpEnableInterfaces
23: FxPkgPnp::Dispatch - WDFDEVICE 0x78C848F0 !devobj 0x8737B4C8,
IRP_MJ_PNP, 0x00000007(IRP_MN_QUERY_DEVICE_RELATIONS) IRP 0x876B44B0
24: FxIoQueue::DispatchEvents - Presentation lock for WDFQUEUE 0x78CB81E8 is
already held, deferring to dpc or workitem
25: FxRequest::CompleteInternal - WDFREQUEST 0x7ABF8E90, PIRP 0xA3A9B008,
Major Function 0xe, completed with outstanding references on WDFMEMORY
0x7ABF8E29 or 0x7ABF8E21 retrieved from this request
26: FxRequest::CompleteInternal - WDFMEMORY 0x7ABF8E29, buffer A3A26208,
PMDL 00000000, length 460 bytes
27: FxRequest::CompleteInternal - IOCTL output WDFMEMORY 0x7ABF8E21, buffer
8B5EF000, PMDL A7409810, length 1024 bytes
---- end of log ----
0: kd>

Doron Holan [MSFT]

unread,

Jun 13, 2008, 5:49:53 PM6/13/08

it means that there there is an outstanding referenc eon the WDFREQUEST when
you completed it. did you ever format it for an WDFIOTARGET?

--
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.

"May" <M...@discussions.microsoft.com> wrote in message
news:E6939E8D-0A40-4D41...@microsoft.com...

0 new messages