Hi.
..............................................................
................................................................
.............
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 44, {fffffa8033fb1d30, 1d7b, 0, 0}
Probably caused by : msdsm.sys ( msdsm!DsmpReportTargetPortGroupsAsync+240 )
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: fffffa8033fb1d30, Address of the IRP
Arg2: 0000000000001d7b
Arg3: 0000000000000000
Arg4: 0000000000000000
Debugging Details:
------------------
IRP_ADDRESS: fffffa8033fb1d30
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP
BUGCHECK_STR: 0x44
PROCESS_NAME: System
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from fffff80003a79e61 to fffff80003ac4f00
STACK_TEXT:
fffff800`0389a698 fffff800`03a79e61 : 00000000`00000044 fffffa80`33fb1d30 00000000`00001d7b 00000000`00000000 : nt!KeBugCheckEx
fffff800`0389a6a0 fffff880`01027558 : fffffa80`17841360 00000000`00000104 00000000`00000104 fffffa80`3349a5d0 : nt! ?? ::FNODOBFM::`string'+0x31b6c
fffff800`0389a6e0 fffff880`010214eb : fffffa80`0e437780 00000000`00000000 fffffa80`3349a5d0 00000000`00000104 : msdsm!DsmpReportTargetPortGroupsAsync+0x240
fffff800`0389a740 fffff880`0101a7df : fffffa80`0e4376c0 00000000`00000000 fffffa80`0e437102 00000000`00000000 : msdsm!DsmpSetPathForIoRetryALUA+0x583
fffff800`0389a7d0 fffff880`011b4e45 : fffffa80`0e4376c0 00000000`00000000 00000000`0b04003f 00000000`0000000b : msdsm!DsmInterpretError+0x6bb
fffff800`0389a860 fffff880`011b5443 : 00000000`00000000 fffff800`c0000185 fffffa80`2f6314d0 fffffa80`17fea1b0 : mpio!MPIOHandleError+0xf5
fffff800`0389a900 fffff800`03ac7516 : fffffa80`17fea060 fffff800`03a0ec01 fffffa80`2f6314d0 00000000`c0000185 : mpio!MPIOPdoCompletion+0x2a7
fffff800`0389a9b0 fffff880`018f4cdd : fffff880`1295d010 fffffa80`2f61e700 fffffa80`34b46770 00000000`00000000 : nt!IopfCompleteRequest+0x3a6
fffff800`0389aa90 fffff880`018f4869 : fffffa80`34b46770 00000000`00000000 fffffa80`000000f1 fffffa80`0d908040 : storport!RaUnitAsyncError+0x26d
fffff800`0389ab70 fffff880`018fb2ce : 00000000`00000000 00000000`000000f1 00000000`00000000 00000000`00000000 : storport!RaidUnitCompleteRequest+0x399
fffff800`0389ac50 fffff800`03ad05dc : fffff800`03c3de80 fffffa80`0d908000 00000001`00000000 00000000`00000015 : storport!RaidpAdapterRedirectDpcRoutine+0x4e
fffff800`0389ac90 fffff800`03acd6fa : fffff800`03c3de80 fffff800`03c4bc40 00000000`00000000 fffff880`018fb280 : nt!KiRetireDpcList+0x1bc
fffff800`0389ad40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
FOLLOWUP_IP:
msdsm!DsmpReportTargetPortGroupsAsync+240
fffff880`01027558 488b0db19b0000 mov rcx,qword ptr [msdsm!WPP_GLOBAL_Control (fffff880`01031110)]
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: msdsm!DsmpReportTargetPortGroupsAsync+240
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: msdsm
IMAGE_NAME: msdsm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bcadb
FAILURE_BUCKET_ID: X64_0x44_msdsm!DsmpReportTargetPortGroupsAsync+240
BUCKET_ID: X64_0x44_msdsm!DsmpReportTargetPortGroupsAsync+240
Followup: MachineOwner
---------