[SOLVED] BSOD crash "MULTIPLE_IRP_COMPLETE_REQUESTS"

[donnyvan1968]

Hey all, crashes have been happening for about a month and a half now. About once a day, usually while playing games, but sometimes happens when I'm browsing Youtube. Drivers are all up to date, I have uninstalled and reinstalled my USB hardware drivers as it looks like it could be coming from that. Any suggestions?

CPU: AMD Ryzen 7 3700X
GPU: NVIDIA GeForce RTX 2070 SUPER
Motherboard: ASUS GA15DH

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


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff80249000000 PsLoadedModuleList = 0xfffff80249c2a2b0
Debug session time: Mon May 16 09:28:46.969 2022 (UTC + 10:00)
System Uptime: 1 days 12:50:46.910
Loading Kernel Symbols
...............................................................
................................................................
................................................................
...............................................
Loading User Symbols

Loading unloaded module list
..................................................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff802493f7d60 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffffa892c2294a0=0000000000000044
1: 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: ffff800393154a30, Address of the IRP
Arg2: 0000000000001232
Arg3: 0000000000000000
Arg4: 0000000000000000

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 2952

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 5246

Key : Analysis.Init.CPU.mSec
Value: 608

Key : Analysis.Init.Elapsed.mSec
Value: 40045

Key : Analysis.Memory.CommitPeak.Mb
Value: 110

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z

Key : WER.OS.Version
Value: 10.0.19041.1


FILE_IN_CAB: MEMORY.DMP

BUGCHECK_CODE: 44

BUGCHECK_P1: ffff800393154a30

BUGCHECK_P2: 1232

BUGCHECK_P3: 0

BUGCHECK_P4: 0

IRP_ADDRESS: ffff800393154a30

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME: System

STACK_TEXT:
fffffa892c229498 fffff8024942c036 : 0000000000000044 ffff800393154a30 0000000000001232 0000000000000000 : nt!KeBugCheckEx
fffffa892c2294a0 fffff802492437b7 : 0000000000000001 0000000000000000 ffff800387547410 0000000000000002 : nt!IopfCompleteRequest+0x1e8866
fffffa892c229590 fffff8024b3b811a : 00000000c0000120 ffff8003726f4b70 ffff800393154a30 fffffa892c229670 : nt!IofCompleteRequest+0x17
fffffa892c2295c0 fffff8024b3b5bbf : fffffa892c229702 fffff802553b6c02 ffff800393154a30 00000000c0000120 : Wdf01000!FxRequest::CompleteInternal+0x23a [minkernel\wdf\framework\shared\core\fxrequest.cpp @ 869]
fffffa892c229650 fffff802553bc874 : fffffa892c229702 ffff800380d9eb30 ffff800380d9ecd0 fffffa892c229760 : Wdf01000!imp_WdfRequestComplete+0x8f [minkernel\wdf\framework\shared\core\fxrequestapi.cpp @ 436]
fffffa892c2296b0 fffff802553bc4d5 : fffffa892c2297d0 fffffa892c229760 ffff8003861f7570 0000000000000780 : USBXHCI!Bulk_Transfer_Complete+0x44
fffffa892c2296e0 fffff802553bbb03 : ffff8003875477f0 ffff800387547850 ffff800387547980 fffff802492a27f9 : USBXHCI!Bulk_CompleteTransfers+0x1f5
fffffa892c229790 fffff802553bba1a : ffff8003844fd730 fffffa892c229960 fffffa892c229b30 ffff80036a7fc000 : USBXHCI!Bulk_ProcessTransferCompletion+0xdb
fffffa892c2297f0 fffff8024b3c940a : 0000000000000f44 0000000000400a02 0000000000000000 0000c2005a7f9a94 : USBXHCI!Bulk_WdfEvtDpcForTransferCompletion+0x2a
fffffa892c229820 fffff802492a181e : ffffa70041fab240 ffff80036a7d5000 fffffa892c229b20 ffffa70000000002 : Wdf01000!FxDpc::FxDpcThunk+0x5a [minkernel\wdf\framework\kmdf\src\core\fxdpc.cpp @ 354]
fffffa892c229860 fffff802492a0b04 : 0000000000000000 fffff802492e4535 0000000000140001 0000000000000000 : nt!KiExecuteAllDpcs+0x30e
fffffa892c2299d0 fffff802493fb8ce : ffffffff00000000 ffffa70041fa8180 ffffa70041fb3440 ffff8003949f3540 : nt!KiRetireDpcList+0x1f4
fffffa892c229c60 0000000000000000 : fffffa892c22a000 fffffa892c224000 0000000000000000 0000000000000000 : nt!KiIdleLoop+0x9e


SYMBOL_NAME: USBXHCI!Bulk_Transfer_Complete+44

MODULE_NAME: USBXHCI

IMAGE_NAME: USBXHCI.SYS

IMAGE_VERSION: 10.0.19041.1566

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 44

FAILURE_BUCKET_ID: 0x44_USBXHCI!Bulk_Transfer_Complete

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {ff508c08-488c-15f6-e5e5-4e8a5f1741d6}

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

 

[Colif]

usbxhci - USB extensible host controller interface'

cause could be a USB device as well.

Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

1. Open Windows File Explore
   
2. Navigate to C:\Windows\Minidump
   
3. Copy the mini-dump files out onto your Desktop
   
4. Do not use Winzip, use the built in facility in Windows
   
5. Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
   
6. Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
   
7. Then post a link here to the zip file, so we can take a look for you . . .
   

 

[johnbl]

1: kd> !error 0xc0000120
Error code: (NTSTATUS) 0xc0000120 (3221225760) - The I/O request was canceled.

most likely you will need to provide the kernel dump file
c:\windows\memory.dmp

you might also go into windows control panel, find the menu item to show removed devices. look for any greyed out drivers and remove them. removed usb devices just get hidden, the driver can still be working.

 

[donnyvan1968]

usbxhci - USB extensible host controller interface'

cause could be a USB device as well.

Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

1. Open Windows File Explore
2. Navigate to C:\Windows\Minidump
3. Copy the mini-dump files out onto your Desktop
4. Do not use Winzip, use the built in facility in Windows
5. Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
6. Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
7. Then post a link here to the zip file, so we can take a look for you . . .

Thanks for the super straight forward instructions, think I have what I'm meant to. I've added the last 3 crashes to the zip file. https://drive.google.com/file/d/1OL6ln1z_V9K2YjIAavqPug036K81PtTD/view?usp=sharing

Let me know if there's something different I should provide or anything, super appreciate the help.

 

[johnbl]

Thanks for the super straight forward instructions, think I have what I'm meant to. I've added the last 3 crashes to the zip file. https://drive.google.com/file/d/1OL6ln1z_V9K2YjIAavqPug036K81PtTD/view?usp=sharing

Let me know if there's something different I should provide or anything, super appreciate the help.

I think these two drivers are messing each other up.
I think usbaudio2.sys is processing packets and Usbaudio.sys is still expecting the packet.


OriginalFilename: USBAudio.sys
ProductVersion: 10.0.19041.1185
FileVersion: 10.0.19041.1185 (WinBuild.160101.0800)
FileDescription: USB Audio Class Driver

OriginalFilename: USBAudio2.sys
ProductVersion: 10.0.19041.1030
FileVersion: 10.0.19041.1030 (WinBuild.160101.0800)
FileDescription: Microsoft USB Audio Class 2.0 Driver

i could not read any of the usb logs or the device chain.

it could be that you need to provide the full kernel dump file c:\windows\memory.dmp
from the error I would go into device manager, select the option to show removed devices, see if you can uninstall the usb audio2 device and let it get reinstalled.
the usbaudio2.sys driver was having the problems.

looks like usbaudio2 is processing request that usbaudio.sys is still expecting and asks for the packet again and just never gets it. I think if you uninstall the usbaudio.sys driver and reinstall it then it will get installed at the beginning of the link and get the packet first. this assumes that usbaudio2 is picking up packets it should not process.

it used to be that the last usb driver installed gets inserted first in the linked list. you want drivers with bugs to be at the end of the linked list so they do not screw up other drivers. That is why is sounds stupid to uninstall the working driver to get the bad driver lower in the link and things working ok. other option would be that usbaudio2.sys is intended to replace usbaudio.sys not run with it. I don't know.

 

[donnyvan1968]

I think these two drivers are messing each other up.
I think usbaudio2.sys is processing packets and Usbaudio.sys is still expecting the packet.


OriginalFilename: USBAudio.sys
ProductVersion: 10.0.19041.1185
FileVersion: 10.0.19041.1185 (WinBuild.160101.0800)
FileDescription: USB Audio Class Driver

OriginalFilename: USBAudio2.sys
ProductVersion: 10.0.19041.1030
FileVersion: 10.0.19041.1030 (WinBuild.160101.0800)
FileDescription: Microsoft USB Audio Class 2.0 Driver

i could not read any of the usb logs or the device chain.

it could be that you need to provide the full kernel dump file c:\windows\memory.dmp
from the error I would go into device manager, select the option to show removed devices, see if you can uninstall the usb audio2 device and let it get reinstalled.
the usbaudio2.sys driver was having the problems.

looks like usbaudio2 is processing request that usbaudio.sys is still expecting and asks for the packet again and just never gets it. I think if you uninstall the usbaudio.sys driver and reinstall it then it will get installed at the beginning of the link and get the packet first. this assumes that usbaudio2 is picking up packets it should not process.

it used to be that the last usb driver installed gets inserted first in the linked list. you want drivers with bugs to be at the end of the linked list so they do not screw up other drivers. That is why is sounds stupid to uninstall the working driver to get the bad driver lower in the link and things working ok. other option would be that usbaudio2.sys is intended to replace usbaudio.sys not run with it. I don't know.

Thanks for the reply

I'll try and uninstall and reinstall the usbaudio devices and see how it goes. Here's a link for the kernel dump if that helps - https://drive.google.com/file/d/10i0QNPgPM6l82QjAc40BoFqvCv_LelG9/view?usp=sharing

EDIT: I've looked and looked for the usbaudio files on the device manager but I can't seen to find them even with hidden files on. I found the direct file but I need permission from TrustedInstaller in order to delete it. Any idea how I go about reinstalling the drivers?

 

[johnbl]

Thanks for the reply

I'll try and uninstall and reinstall the usbaudio devices and see how it goes. Here's a link for the kernel dump if that helps - https://drive.google.com/file/d/10i0QNPgPM6l82QjAc40BoFqvCv_LelG9/view?usp=sharing

EDIT: I've looked and looked for the usbaudio files on the device manager but I can't seen to find them even with hidden files on. I found the direct file but I need permission from TrustedInstaller in order to delete it. Any idea how I go about reinstalling the drivers?

it will be a sound device uses the audio driver. i will see if i can find it in the kernel dump
-----------
plug and play is complaining about 3 devices:

bluetooth:
ServiceName is "BthA2dp" looks like it got a error
1: kd> !error 0xc00002b6
Error code: (NTSTATUS) 0xc00002b6 (3221226166) - The device has been removed. service went from initialized to a unknown state.
plug and play is trying to remove the device but it is locked so it can not remove it.

try this: try starting cmd.exe as an admin and run
Sigverif.exe
(this will bring up a tool to scan for unsigned files, scan and click advance button to look at the log and see if a file is unsigned)
to fix run:
sfc.exe /scannow
DISM.exe /Online /Cleanup-image /Restorehealth
(in case the file is corrupted)
Note: debugger reported 8 modifications to your bluetooth file and modifications to your usb extensions file.
dism command should fix it.
otherwise I would try to stop the service

usbaudio thinks a device has been removed but has a unknown problem during removal. device was:
"USB\VID_194F&PID_0303&MI_03\7&26f2ba10&0&0003"
vendor=194f device =0303 =
presonus audiobox
PreSonus Audio Electronics, Inc
PreSonus | Wherever sound takes you.

last plug and play error is a failed install of
the presonus audiobox driver.
-----------
look in windows control panel, device manager ->
sound video and game controllers-> microsoft bluetooth a2dp source
see if there is a error indication.
------------
suspect driver:
C:\Users\donov\AppData\Local\Temp\mhyprot3.sys Mon Feb 28 05:09:58 2022

drivers running out of a temp directory are always suspect.
mhyprot3.sys
google for microsoft autoruns, you can download it, run it and disable or remove the driver if you do not have a uninstaller for it.
----------
i would not run drivereasy.exe these tools can download custom versions of drivers that will not work correctly for your machine.

i would look into why you have AdobeUpdateService.exe running.
it used to be a way to feed malware to a machine. (malware that hides as a fake update service)

lots of asus utilites running. (these are malware targets)

 

[donnyvan1968]

it will be a sound device uses the audio driver. i will see if i can find it in the kernel dump
-----------
plug and play is complaining about 3 devices:

bluetooth:
ServiceName is "BthA2dp" looks like it got a error
1: kd> !error 0xc00002b6
Error code: (NTSTATUS) 0xc00002b6 (3221226166) - The device has been removed. service went from initialized to a unknown state.
plug and play is trying to remove the device but it is locked so it can not remove it.

try this: try starting cmd.exe as an admin and run
Sigverif.exe
(this will bring up a tool to scan for unsigned files, scan and click advance button to look at the log and see if a file is unsigned)
to fix run:
sfc.exe /scannow
DISM.exe /Online /Cleanup-image /Restorehealth
(in case the file is corrupted)
Note: debugger reported 8 modifications to your bluetooth file and modifications to your usb extensions file.
dism command should fix it.
otherwise I would try to stop the service

usbaudio thinks a device has been removed but has a unknown problem during removal. device was:
"USB\VID_194F&PID_0303&MI_03\7&26f2ba10&0&0003"
vendor=194f device =0303 =
presonus audiobox
PreSonus Audio Electronics, Inc
PreSonus | Wherever sound takes you.

last plug and play error is a failed install of
the presonus audiobox driver.
-----------
look in windows control panel, device manager ->
sound video and game controllers-> microsoft bluetooth a2dp source
see if there is a error indication.
------------
suspect driver:
C:\Users\donov\AppData\Local\Temp\mhyprot3.sys Mon Feb 28 05:09:58 2022

drivers running out of a temp directory are always suspect.
mhyprot3.sys
google for microsoft autoruns, you can download it, run it and disable or remove the driver if you do not have a uninstaller for it.
----------
i would not run drivereasy.exe these tools can download custom versions of drivers that will not work correctly for your machine.

i would look into why you have AdobeUpdateService.exe running.
it used to be a way to feed malware to a machine. (malware that hides as a fake update service)

lots of asus utilites running. (these are malware targets)

THANK YOU! This is super duper helpful. Appreciate you going through all this.

I figured when you said it was an audio driver issue my audiobox could be a problem, as I've had it mess up in the past. I removed it a few days ago and while I've still had crashes they seem a little less frequent.

I've found the BthA2dp with an error message, it looks like the bluetooth component of my audiotechnica headphones I use, but I use them wired so I have no need for the bluetooth connectivity. Ran DISM command and I just removed it from my bluetooth devices, hopefully that helps.

looks like mhyprot3.sys is made by Genshin Impact, which is a game I trust but looks like you can remove it without problems so I've done that. As for the things that might be malware targets, definitely concerned about it as my email password got taken and subsequently a few other accounts back in march so will delete all those. I've run malwarebytes a few times but it didn't find anything other than PUPs. Will definitely remove those but is there any antivirus you'd reccomend to clean out my computer?

 

[johnbl]

THANK YOU! This is super duper helpful. Appreciate you going through all this.

I figured when you said it was an audio driver issue my audiobox could be a problem, as I've had it mess up in the past. I removed it a few days ago and while I've still had crashes they seem a little less frequent.

I've found the BthA2dp with an error message, it looks like the bluetooth component of my audiotechnica headphones I use, but I use them wired so I have no need for the bluetooth connectivity. Ran DISM command and I just removed it from my bluetooth devices, hopefully that helps.

looks like mhyprot3.sys is made by Genshin Impact, which is a game I trust but looks like you can remove it without problems so I've done that. As for the things that might be malware targets, definitely concerned about it as my email password got taken and subsequently a few other accounts back in march so will delete all those. I've run malwarebytes a few times but it didn't find anything other than PUPs. Will definitely remove those but is there any antivirus you'd reccomend to clean out my computer?

I really don't keep up on the malware/antivirus scanners. Maybe someone else can recommend a good one?

 

[Marco Vargas]

Hi All.
I come here and ask for some orientation. This happens to me also, but always playing, i notices sometimes i see a fps drop before it crash. Something when i am doing nothin inside a game. It pretty random though. It can happen one every six months, only the pc restarts, one time a black screen, but last week i noticed 1 bsod, and i looked for the minidump files. I use Windbg. Sorry for the long copy paste:


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


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


Path validation summary *
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff8037b200000 PsLoadedModuleList = 0xfffff8037be2a2b0
Debug session time: Mon Jun 13 18:30:52.740 2022 (UTC - 4:00)
System Uptime: 2 days 11:35:09.938
Loading Kernel Symbols
..

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

.............................................................
................................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
.............................................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff8037b5f7d60 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff8037e6987f0=0000000000000044
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: ffff9f8cea2eaa60, Address of the IRP
Arg2: 0000000000001232
Arg3: 0000000000000000
Arg4: 0000000000000000

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 3327

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 34817

Key : Analysis.Init.CPU.mSec
Value: 765

Key : Analysis.Init.Elapsed.mSec
Value: 23904

Key : Analysis.Memory.CommitPeak.Mb
Value: 114

Key : Dump.Attributes.AsUlong
Value: 8

Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1


FILE_IN_CAB: 061322-64390-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump

BUGCHECK_CODE: 44

BUGCHECK_P1: ffff9f8cea2eaa60

BUGCHECK_P2: 1232

BUGCHECK_P3: 0

BUGCHECK_P4: 0

IRP_ADDRESS: ffff9f8cea2eaa60

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: svchost.exe

DPC_STACK_BASE: FFFFF8037E698FB0

STACK_TEXT:
fffff8037e6987e8 fffff8037b62c036 : 0000000000000044 ffff9f8cea2eaa60 0000000000001232 0000000000000000 : nt!KeBugCheckEx
fffff8037e6987f0 fffff8037b4437b7 : 0000000000000001 0000000000000000 ffff9f8ce5128a30 0000000000000002 : nt!IopfCompleteRequest+0x1e8866
fffff8037e6988e0 fffff8037cdb811a : 00000000c0000120 ffff9f8cd64c9dd0 ffff9f8cea2eaa60 fffff8037e6989c0 : nt!IofCompleteRequest+0x17
fffff8037e698910 fffff8037cdb5bbf : fffff8037e698b02 fffff8038cd36c02 ffff9f8cea2eaa60 00000000c0000120 : Wdf01000!FxRequest::CompleteInternal+0x23a [minkernel\wdf\framework\shared\core\fxrequest.cpp @ 869]
fffff8037e6989a0 fffff8038cd3c874 : fffff8037e698b02 ffff9f8ceb7c5060 ffff9f8ceb7c5200 fffff8037e698ab0 : Wdf01000!imp_WdfRequestComplete+0x8f [minkernel\wdf\framework\shared\core\fxrequestapi.cpp @ 436]
fffff8037e698a00 fffff8038cd3c4d5 : fffff8037e698b20 fffff8037e698ab0 ffff9f8ceb7c5290 0000000000000780 : USBXHCI!Bulk_Transfer_Complete+0x44
fffff8037e698a30 fffff8038cd3bb03 : ffff9f8ce5128e10 ffff9f8ce5128e70 ffff9f8ce5128fa0 fffff8037b4a27f9 : USBXHCI!Bulk_CompleteTransfers+0x1f5
fffff8037e698ae0 fffff8038cd3ba1a : ffff9f8cec2df2e0 fffff8037e698cb0 fffff8037e698e80 ffff9f8ccfefc000 : USBXHCI!Bulk_ProcessTransferCompletion+0xdb
fffff8037e698b40 fffff8037cdc940a : 0000000000000f44 0000000000400a02 0000000000000000 0002aa208d861b60 : USBXHCI!Bulk_WdfEvtDpcForTransferCompletion+0x2a
fffff8037e698b70 fffff8037b4a181e : fffff80376fba240 ffff9f8ccfdce000 fffff8037e698e70 ffff9f8c00000002 : Wdf01000!FxDpc::FxDpcThunk+0x5a [minkernel\wdf\framework\kmdf\src\core\fxdpc.cpp @ 354]
fffff8037e698bb0 fffff8037b4a0b04 : fffff80376fb7180 0000000000000000 0000000000000002 0000000000000004 : nt!KiExecuteAllDpcs+0x30e
fffff8037e698d20 fffff8037b5feda5 : 0000000000000000 fffff80376fb7180 ffffd701e38468c0 0000000000000004 : nt!KiRetireDpcList+0x1f4
fffff8037e698fb0 fffff8037b5feb90 : fffff8037b5f3e70 fffff8037b51962a 0061004b002d0074 0072006500700073 : nt!KxRetireDpcList+0x5
fffff90e40ef3fc0 fffff8037b5fe445 : 0000000000000004 fffff8037b5f98d1 ffff9f8cd1a95014 00300030002d0072 : nt!KiDispatchInterruptContinue
fffff90e40ef3ff0 fffff8037b5f98d1 : ffff9f8cd1a95014 00300030002d0072 0000000000300030 0000000000000000 : nt!KiDpcInterruptBypass+0x25
fffff90e40ef4000 fffff8037dbcfbee : fffff8037dc88a6d ffff9f8cd1a95010 fffff90e40ef4320 ffff9f8cd1a954e0 : nt!KiInterruptDispatch+0xb1
fffff90e40ef4198 fffff8037dc88a6d : ffff9f8cd1a95010 fffff90e40ef4320 ffff9f8cd1a954e0 0000000000000000 : ndis!memcpy+0x6e
fffff90e40ef41a0 fffff8037db9a2f6 : ffff9f8cd1a95010 ffff9f8cd6861010 fffff90e40ef4300 ffff9f8cf163eed8 : ndis!ndisNsiGetInterfaceRosEnumObject+0x16d
fffff90e40ef4220 fffff8037dd14ddd : 0000000002d803e6 0000000000000000 0000000000000000 fffff8037dc571b8 : ndis!ndisNsiEnumerateAllInterfaceInformation+0xa06
fffff90e40ef4390 fffff8037fed2b32 : 000000dc1c37f2c0 000000dc1c37f2c0 ffff9f8cf1637000 ffff9f8cd6d14098 : NETIO!NsiEnumerateObjectsAllParametersEx+0x27d
fffff90e40ef45c0 fffff8037fed26e2 : 0000000000000000 ffff9f8cd6d14130 ffff9f8cd6d14060 000000dc1c37f2c0 : nsiproxy!NsippEnumerateObjectsAllParameters+0x282
fffff90e40ef47b0 fffff8037b44e565 : 0000000000000002 0000000000000000 ffff9f8ce06b1e00 ffff9f8cd1e40ca0 : nsiproxy!NsippDispatch+0x82
fffff90e40ef4800 fffff8037b80da18 : ffff9f8cd6d14060 0000000000000000 0000000000000000 0000000000000070 : nt!IofCallDriver+0x55
fffff90e40ef4840 fffff8037b80e9f7 : 0000000000000000 fffff90e40ef4b80 0000000000040800 fffff90e40ef4b80 : nt!IopSynchronousServiceTail+0x1a8
fffff90e40ef48e0 fffff8037b80dd76 : 0000000000000001 0000000000000680 0000000000000000 0000000000000000 : nt!IopXxxControlFile+0xc67
fffff90e40ef4a20 fffff8037b6096b8 : ffff9f8cda5ca0c0 000000dc1c37f138 fffff90e40ef4aa8 0000000000000000 : nt!NtDeviceIoControlFile+0x56
fffff90e40ef4a90 00007ffcd5ecce24 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x28
000000dc1c37f1c8 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ffc`d5ecce24


SYMBOL_NAME: USBXHCI!Bulk_Transfer_Complete+44

MODULE_NAME: USBXHCI

IMAGE_NAME: USBXHCI.SYS

IMAGE_VERSION: 10.0.19041.1613

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 44

FAILURE_BUCKET_ID: 0x44_USBXHCI!Bulk_Transfer_Complete

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {ff508c08-488c-15f6-e5e5-4e8a5f1741d6}

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

Last week i did was delete all amd drivers (my ignorance was telling me to do that), and reinstalled again from zero.

I did a Scan /sfc (last week there was a problem and it was solve), today i ran it again but all so far is good.

Also today i did Sigverif.exe, no error found so far.


Now, since i only use : 1 Wireless Receiver, 1 wiereless bluetooth Headphone, 1 wireless bluetoth mouse, and 1 usb xbox 360 1controller (dont think this is an original one), i'm trying to see if it there exists something to uninstall every usb device and plug in one by one.

I gotta be honest thought, my motherboards is kind of old, that means i never update that nor the drivers nothing, only what windows 10 says to me. Also i found around there, is related too the the usb 3.0, they recommended to detactivated the 3.0. But i dont want to mess with the bios yet.

Any ideas or suggestions i would be appreciated. Thanks in advance.