1 Topic by cjunekim (edited by cjunekim 2021-02-18 12:58:16)

  • Registered: 2021-01-17
  • Posts: 30

Topic: BSOD with MULTIPLE_IRP_COMPLETE_REQUESTS

Hello

I purchased a digiface USB a month ago. Quite satisfied, I purchased another.

To test the new one, I plugged off the already connected digiface. Suddenly BSOD showed up. On another time, BSOD showed up when connecting the new one. So I have had two BSOD.

The error was MULTIPLE_IRP_COMPLETE_REQUESTS.

Analyzing the memory dump with windbg, the culprit seems to be USBXHCI.SYS. They are connected to the USB 3.0 port.

The following is the analysis from windbg:

Microsoft (R) Windows Debugger Version 10.0.18362.1 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\021821-52312-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response                         Time (ms)     Location
OK                                             C:\Windows\System32

************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: C:\Windows\System32
Windows 10 Kernel Version 18362 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff807`44200000 PsLoadedModuleList = 0xfffff807`44645e90
Debug session time: Thu Feb 18 20:25:46.902 2021 (UTC + 9:00)
System Uptime: 0 days 9:34:01.063
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..........
Loading User Symbols
Loading unloaded module list
.................
For analysis of this file, run !analyze -v
0: kd> !analyze -v
ERROR: FindPlugIns 8007007b
ERROR: Some plugins may not be available [8007007b]
*******************************************************************************
*                                                                             *
*                        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: ffffd70d8d30aa30, Address of the IRP
Arg2: 0000000000001232
Arg3: 0000000000000000
Arg4: 0000000000000000

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

*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  18362.1.amd64fre.19h1_release.190318-1202

SYSTEM_MANUFACTURER:  System manufacturer

SYSTEM_PRODUCT_NAME:  System Product Name

SYSTEM_SKU:  SKU

SYSTEM_VERSION:  System Version

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  1905

BIOS_DATE:  10/27/2014

BASEBOARD_MANUFACTURER:  ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT:  P8H77-V

BASEBOARD_VERSION:  Rev X.0x

DUMP_TYPE:  2

BUGCHECK_P1: ffffd70d8d30aa30

BUGCHECK_P2: 1232

BUGCHECK_P3: 0

BUGCHECK_P4: 0

IRP_ADDRESS: ffffd70d8d30aa30

FOLLOWUP_IP: 
USBXHCI!Isoch_Transfer_CompleteCancelable+213
fffff807`4f2c243b 90              nop

CPU_COUNT: 8

CPU_MHZ: d48

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 3a

CPU_STEPPING: 9

CPU_MICROCODE: 6,3a,9,0 (F,M,S,R)  SIG: 21'00000000 (cache) 21'00000000 (init)

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0x44

PROCESS_NAME:  System

CURRENT_IRQL:  2

ANALYSIS_SESSION_HOST:  JUNE-DESK

ANALYSIS_SESSION_TIME:  02-18-2021 20:41:50.0887

ANALYSIS_VERSION: 10.0.18362.1 amd64fre

LAST_CONTROL_TRANSFER:  from fffff8074440da3b to fffff807443c3a90

STACK_TEXT:  
fffff807`48c9b508 fffff807`4440da3b : 00000000`00000044 ffffd70d`8d30aa30 00000000`00001232 00000000`00000000 : nt!KeBugCheckEx
fffff807`48c9b510 fffff807`44275f77 : 00000000`ffffffff ffffd70d`8d750100 00000000`00000001 00000000`00000001 : nt!IopfCompleteRequest+0x197aab
fffff807`48c9b620 fffff807`478084ad : 00000000`c0000120 ffffd70d`8d750020 00000000`00000002 fffff807`48c9b708 : nt!IofCompleteRequest+0x17
fffff807`48c9b650 fffff807`47807f7b : 00000000`00000002 fffff807`00000005 ffffd70d`8d30aa30 00000000`c0000120 : Wdf01000!FxRequest::CompleteInternal+0x22d [minkernel\wdf\framework\shared\core\fxrequest.cpp @ 869] 
fffff807`48c9b6e0 fffff807`4f2c243b : 00000000`c0010002 ffffd70d`8d750020 ffffd70d`89010a30 ffffd70d`8d7501c0 : Wdf01000!imp_WdfRequestComplete+0x8b [minkernel\wdf\framework\shared\core\fxrequestapi.cpp @ 436] 
fffff807`48c9b740 fffff807`4f2bdc50 : 00000000`00000000 ffffd70d`890109d0 fffff807`48c9b850 ffffd70d`8d7501c0 : USBXHCI!Isoch_Transfer_CompleteCancelable+0x213
fffff807`48c9b7a0 fffff807`4f2bf502 : ffffd70d`890109d0 fffff807`48c9b850 fffff807`48c9b900 00000000`00000002 : USBXHCI!Isoch_CompleteTransfers+0x1b4
fffff807`48c9b810 fffff807`4f2c274c : 000028f2`7709c838 ffffd70d`88f637ca ffffd70d`88f63880 ffffd70d`88f63890 : USBXHCI!Isoch_ProcessTransferCompletion+0x102
fffff807`48c9b870 fffff807`47813ed0 : ffffd70d`839cd210 00000000`00000ee0 00000000`00000f44 00000000`00400a02 : USBXHCI!Isoch_WdfEvtDpcForTransferCompletion+0x2c
fffff807`48c9b8a0 fffff807`442c5b2a : fffff807`40a82f80 ffffd70d`839ca000 fffff807`48c9b9f0 00000000`00000002 : Wdf01000!FxDpc::FxDpcThunk+0x70 [minkernel\wdf\framework\kmdf\src\core\fxdpc.cpp @ 354] 
fffff807`48c9b8f0 fffff807`442c517f : 00000000`00000014 00000000`00989680 fffff807`48c9bb30 00000000`00000036 : nt!KiExecuteAllDpcs+0x30a
fffff807`48c9ba30 fffff807`443c75be : 00000000`00000000 fffff807`40a80180 fffff807`4478f400 ffffd70d`8eed2080 : nt!KiRetireDpcList+0x1ef
fffff807`48c9bc60 00000000`00000000 : fffff807`48c9c000 fffff807`48c96000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x7e


THREAD_SHA1_HASH_MOD_FUNC:  b401638434820ae8aee490c3cb5278f4e50349f9

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  e0d8c1dd836de673a049e0a4f037c8f00c194d90

THREAD_SHA1_HASH_MOD:  5ed62ea5e553154cde5ae520dfffb1c78c6eae0d

FAULT_INSTR_CODE:  4ccb8a90

SYMBOL_STACK_INDEX:  5

SYMBOL_NAME:  USBXHCI!Isoch_Transfer_CompleteCancelable+213

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: USBXHCI

IMAGE_NAME:  USBXHCI.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  0

IMAGE_VERSION:  10.0.18362.900

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  213

FAILURE_BUCKET_ID:  0x44_USBXHCI!Isoch_Transfer_CompleteCancelable

BUCKET_ID:  0x44_USBXHCI!Isoch_Transfer_CompleteCancelable

PRIMARY_PROBLEM_CLASS:  0x44_USBXHCI!Isoch_Transfer_CompleteCancelable

TARGET_TIME:  2021-02-18T11:25:46.000Z

OSBUILD:  18362

OSSERVICEPACK:  1379

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  unknown_date

BUILDDATESTAMP_STR:  190318-1202

BUILDLAB_STR:  19h1_release

BUILDOSVER_STR:  10.0.18362.1.amd64fre.19h1_release.190318-1202

ANALYSIS_SESSION_ELAPSED_TIME:  864f

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x44_usbxhci!isoch_transfer_completecancelable

FAILURE_ID_HASH:  {daeadff0-c95a-c399-f9ed-a24188f18c67}

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

2 Reply by danielellar79 (edited by danielellar79 2024-03-07 21:52:42)

  • Registered: 2024-03-07
  • Posts: 1

Re: BSOD with MULTIPLE_IRP_COMPLETE_REQUESTS

Hi there, I'm having the same problem. If I turn off the Fireface UFX iiiwhile Windows 11 is running  I get a BSOD.

Did you manage to resolve the issue?

This report is from WhoCrashed

Crash dump directories: 
C:\WINDOWS
C:\WINDOWS\Minidump

On Thu 07/03/2024 01:02:16 your computer crashed or a problem was reported

Crash dump file:  C:\WINDOWS\Minidump\030724-19687-01.dmp (Minidump)  
Bugcheck code:  0x44(0xFFFF88846B95D010, 0x1347, 0x0, 0x0) 
Bugcheck name: MULTIPLE_IRP_COMPLETE_REQUESTS 
Bug check description: This indicates that a driver has tried to requested an IRP be completed that is already complete. 
Analysis: This is a typical software problem. Most likely this is caused by a bug in a driver.