*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 44, {fffffa8005cb2ad0, 1d7b, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+31b6c )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
MULTIPLE_IRP_COMPLETE_REQUESTS (44)
A driver has requested that an IRP be completed (IoCompleteRequest()), but
the packet has already been completed. This is a tough bug to find because
the easiest case, a driver actually attempted to complete its own packet
twice, is generally not what happened. Rather, two separate drivers each
believe that they own the packet, and each attempts to complete it. The
first actually works, and the second fails. Tracking down which drivers
in the system actually did this is difficult, generally because the trails
of the first driver have been covered by the second. However, the driver
stack for the current request can be found by examining the DeviceObject
fields in each of the stack locations.
Arguments:
Arg1: fffffa8005cb2ad0, Address of the IRP
Arg2: 0000000000001d7b
Arg3: 0000000000000000
Arg4: 0000000000000000
Debugging Details:
------------------
IRP_ADDRESS: ffffffffffffff88
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x44
PROCESS_NAME: ccsvchst.exe
CURRENT_IRQL: 1
LAST_CONTROL_TRANSFER: from fffff8000347ee61 to fffff800034c9f00
STACK_TEXT:
fffff880`0d65d8f8 fffff800`0347ee61 : 00000000`00000044 fffffa80`05cb2ad0 00000000`00001d7b 00000000`00000000 : nt!KeBugCheckEx
fffff880`0d65d900 fffff800`034e97c4 : fffffa80`05cb2ad0 fffffa80`00000000 fffffa80`07060700 fffff800`03458000 : nt! ?? ::FNODOBFM::`string'+0x31b6c
fffff880`0d65d940 fffff800`037dd975 : 00000000`00000000 fffffa80`059ef240 00000000`00000000 fffffa80`05cb2ad0 : nt!IopCompleteRequest+0x824
fffff880`0d65da10 fffff800`037e5143 : fffffa80`059ef240 fffffa80`05cb2a01 fffffa80`059ef240 00000000`00000002 : nt!IopSynchronousServiceTail+0x145
fffff880`0d65da80 fffff800`034c9153 : 00000000`00002840 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtReadFile+0x631
fffff880`0d65db70 00000000`74e42dd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0288f0f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74e42dd9
STACK_COMMAND: kb
FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+31b6c
fffff800`0347ee61 cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+31b6c
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600
FAILURE_BUCKET_ID: X64_0x44_nt!_??_::FNODOBFM::_string_+31b6c
BUCKET_ID: X64_0x44_nt!_??_::FNODOBFM::_string_+31b6c
Followup: MachineOwner
---------