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 = 0xfffff803
7be2a2b0
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:fffff803
7e6987f0=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 fffff803
7b62c036 : 0000000000000044 ffff9f8c
ea2eaa60 0000000000001232 00000000
00000000 : nt!KeBugCheckEx
fffff8037e6987f0 fffff803
7b4437b7 : 0000000000000001 00000000
00000000 ffff9f8ce5128a30 00000000
00000002 : nt!IopfCompleteRequest+0x1e8866
fffff8037e6988e0 fffff803
7cdb811a : 00000000c0000120 ffff9f8c
d64c9dd0 ffff9f8cea2eaa60 fffff803
7e6989c0 : nt!IofCompleteRequest+0x17
fffff8037e698910 fffff803
7cdb5bbf : fffff8037e698b02 fffff803
8cd36c02 ffff9f8cea2eaa60 00000000
c0000120 : Wdf01000!FxRequest::CompleteInternal+0x23a [minkernel\wdf\framework\shared\core\fxrequest.cpp @ 869]
fffff8037e6989a0 fffff803
8cd3c874 : fffff8037e698b02 ffff9f8c
eb7c5060 ffff9f8ceb7c5200 fffff803
7e698ab0 : Wdf01000!imp_WdfRequestComplete+0x8f [minkernel\wdf\framework\shared\core\fxrequestapi.cpp @ 436]
fffff8037e698a00 fffff803
8cd3c4d5 : fffff8037e698b20 fffff803
7e698ab0 ffff9f8ceb7c5290 00000000
00000780 : USBXHCI!Bulk_Transfer_Complete+0x44
fffff8037e698a30 fffff803
8cd3bb03 : ffff9f8ce5128e10 ffff9f8c
e5128e70 ffff9f8ce5128fa0 fffff803
7b4a27f9 : USBXHCI!Bulk_CompleteTransfers+0x1f5
fffff8037e698ae0 fffff803
8cd3ba1a : ffff9f8cec2df2e0 fffff803
7e698cb0 fffff8037e698e80 ffff9f8c
cfefc000 : USBXHCI!Bulk_ProcessTransferCompletion+0xdb
fffff8037e698b40 fffff803
7cdc940a : 0000000000000f44 00000000
00400a02 0000000000000000 0002aa20
8d861b60 : USBXHCI!Bulk_WdfEvtDpcForTransferCompletion+0x2a
fffff8037e698b70 fffff803
7b4a181e : fffff80376fba240 ffff9f8c
cfdce000 fffff8037e698e70 ffff9f8c
00000002 : Wdf01000!FxDpc::FxDpcThunk+0x5a [minkernel\wdf\framework\kmdf\src\core\fxdpc.cpp @ 354]
fffff8037e698bb0 fffff803
7b4a0b04 : fffff80376fb7180 00000000
00000000 0000000000000002 00000000
00000004 : nt!KiExecuteAllDpcs+0x30e
fffff8037e698d20 fffff803
7b5feda5 : 0000000000000000 fffff803
76fb7180 ffffd701e38468c0 00000000
00000004 : nt!KiRetireDpcList+0x1f4
fffff8037e698fb0 fffff803
7b5feb90 : fffff8037b5f3e70 fffff803
7b51962a 0061004b002d0074 00720065
00700073 : nt!KxRetireDpcList+0x5
fffff90e40ef3fc0 fffff803
7b5fe445 : 0000000000000004 fffff803
7b5f98d1 ffff9f8cd1a95014 00300030
002d0072 : nt!KiDispatchInterruptContinue
fffff90e40ef3ff0 fffff803
7b5f98d1 : ffff9f8cd1a95014 00300030
002d0072 0000000000300030 00000000
00000000 : nt!KiDpcInterruptBypass+0x25
fffff90e40ef4000 fffff803
7dbcfbee : fffff8037dc88a6d ffff9f8c
d1a95010 fffff90e40ef4320 ffff9f8c
d1a954e0 : nt!KiInterruptDispatch+0xb1
fffff90e40ef4198 fffff803
7dc88a6d : ffff9f8cd1a95010 fffff90e
40ef4320 ffff9f8cd1a954e0 00000000
00000000 : ndis!memcpy+0x6e
fffff90e40ef41a0 fffff803
7db9a2f6 : ffff9f8cd1a95010 ffff9f8c
d6861010 fffff90e40ef4300 ffff9f8c
f163eed8 : ndis!ndisNsiGetInterfaceRosEnumObject+0x16d
fffff90e40ef4220 fffff803
7dd14ddd : 0000000002d803e6 00000000
00000000 0000000000000000 fffff803
7dc571b8 : ndis!ndisNsiEnumerateAllInterfaceInformation+0xa06
fffff90e40ef4390 fffff803
7fed2b32 : 000000dc1c37f2c0 000000dc
1c37f2c0 ffff9f8cf1637000 ffff9f8c
d6d14098 : NETIO!NsiEnumerateObjectsAllParametersEx+0x27d
fffff90e40ef45c0 fffff803
7fed26e2 : 0000000000000000 ffff9f8c
d6d14130 ffff9f8cd6d14060 000000dc
1c37f2c0 : nsiproxy!NsippEnumerateObjectsAllParameters+0x282
fffff90e40ef47b0 fffff803
7b44e565 : 0000000000000002 00000000
00000000 ffff9f8ce06b1e00 ffff9f8c
d1e40ca0 : nsiproxy!NsippDispatch+0x82
fffff90e40ef4800 fffff803
7b80da18 : ffff9f8cd6d14060 00000000
00000000 0000000000000000 00000000
00000070 : nt!IofCallDriver+0x55
fffff90e40ef4840 fffff803
7b80e9f7 : 0000000000000000 fffff90e
40ef4b80 0000000000040800 fffff90e
40ef4b80 : nt!IopSynchronousServiceTail+0x1a8
fffff90e40ef48e0 fffff803
7b80dd76 : 0000000000000001 00000000
00000680 0000000000000000 00000000
00000000 : nt!IopXxxControlFile+0xc67
fffff90e40ef4a20 fffff803
7b6096b8 : ffff9f8cda5ca0c0 000000dc
1c37f138 fffff90e40ef4aa8 00000000
00000000 : nt!NtDeviceIoControlFile+0x56
fffff90e40ef4a90 00007ffc
d5ecce24 : 0000000000000000 00000000
00000000 0000000000000000 00000000
00000000 : nt!KiSystemServiceCopyEnd+0x28
000000dc1c37f1c8 00000000
00000000 : 0000000000000000 00000000
00000000 0000000000000000 00000000
00000000 : 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.