*******************************************************************************
* *
* 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: 8539cde0, Address of the IRP
Arg2: 00000e7a
Arg3: 00000000
Arg4: 00000000
Debugging Details:
------------------
IRP_ADDRESS: 8539cde0
FOLLOWUP_IP:
Sacm2A+2174
901cc174 ?? ???
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: INTEL_CPU_MICROCODE_ZERO
BUGCHECK_STR: 0x44
PROCESS_NAME: BF2.exe
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from 82079484 to 8210c163
STACK_TEXT:
STACK_COMMAND: kb
SYMBOL_STACK_INDEX: 5
SYMBOL_NAME: Sacm2A+2174
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Sacm2A
IMAGE_NAME: Sacm2A.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 40c8573c
FAILURE_BUCKET_ID: 0x44_Sacm2A+2174
BUCKET_ID: 0x44_Sacm2A+2174
Followup: MachineOwner
---------