J'ai un serveur qui crashe ces derniers temps
J'ai installé ce qu'il faut pour exploiter les fichiers minidump et voilà le résultat :
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: 850e1c28, Address of the IRP
Arg2: 00000d39
Arg3: 00000000
Arg4: 00000000
Debugging Details:
------------------
IRP_ADDRESS: 850e1c28
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x44
LAST_CONTROL_TRANSFER: from 00000000 to 8041df2c
STACK_TEXT:
f2073a24 00000000 850e1c28 00000d39 00000000 nt!FsRtlCancelExclusiveIrp+0x95
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!FsRtlCancelExclusiveIrp+95
8041df2c ?? ???
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!FsRtlCancelExclusiveIrp+95
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntoskrnl.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 45069e6e
FAILURE_BUCKET_ID: 0x44_nt!FsRtlCancelExclusiveIrp+95
BUCKET_ID: 0x44_nt!FsRtlCancelExclusiveIrp+95
Une idée de comment savoir vers quels drivers il faudrait que je fasse une investigation ?
