Windows 10 MULTIPLE_IRP_COMPLETE_REQUESTS mavi ekran hatası

USB sürücünüz güncel değil ise güncelleyin.
BIOS ayarlarınızı sıfırlayın veya CMOS reset deneyin muhtemelen düzelecektir.

Ek olarak BIOS sürümünüz çok eski, en kısa zamanda güncellemenizde fayda var.

Birde belirteyim 1903 sürümünü kullanıyorsunuz, mümkün olduğunuzda Windows 10 1909 sürümüne geçin. Bu yüzden performans kaybı yaşıyor olabilirsiniz.

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: ffffc98ab6bf8280, Address of the IRP
Arg2: 0000000000001232
Arg3: 0000000000000000
Arg4: 0000000000000000

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 5984

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-JO5OOR3

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.mSec
Value: 12666

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

Key : Analysis.System
Value: CreateObject

Key : WER.OS.Branch
Value: 19h1_release

Key : WER.OS.Timestamp
Value: 2019-03-18T12:02:00Z

Key : WER.OS.Version
Value: 10.0.18362.1


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE: 44

BUGCHECK_P1: ffffc98ab6bf8280

BUGCHECK_P2: 1232

BUGCHECK_P3: 0

BUGCHECK_P4: 0

IRP_ADDRESS: ffffc98ab6bf8280

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
fffff800`7be672a8 fffff800`76c25f8d : 00000000`00000044 ffffc98a`b6bf8280 00000000`00001232 00000000`00000000 : nt!KeBugCheckEx
fffff800`7be672b0 fffff800`76aaf577 : ffffc98a`b0f06570 00000000`00000100 00000000`00000001 00000000`00000001 : nt!IopfCompleteRequest+0x1769fd
fffff800`7be673c0 fffff800`7a7284ad : 00000000`00000000 ffffc98a`b4ca0930 00000000`00000002 fffff800`7be674d0 : nt!IofCompleteRequest+0x17
fffff800`7be673f0 fffff800`7a727f7b : 00000000`00000002 fffff800`7be67518 ffffc98a`b6bf8280 00000000`00000000 : Wdf01000!FxRequest::CompleteInternal+0x22d [minkernel\wdf\framework\shared\core\fxrequest.cpp @ 869]
fffff800`7be67480 fffff800`82b2b523 : ffffc98a`b4ca0a02 ffffc98a`b4ca0930 ffffc98a`b4502440 00000000`00000000 : Wdf01000!imp_WdfRequestComplete+0x8b [minkernel\wdf\framework\shared\core\fxrequestapi.cpp @ 436]
fffff800`7be674e0 fffff800`82b2b6dd : ffffc98a`b4ca0ad0 00000000`00000000 00000000`00000000 00000000`00000000 : USBXHCI!Control_Transfer_Complete+0x1d7
fffff800`7be67560 fffff800`82b2afc1 : ffffc98a`b45024a0 00000000`00000000 ffffc98a`b4ca0ad0 ffffc98a`b4502440 : USBXHCI!Control_Transfer_CompleteCancelable+0x161
fffff800`7be675b0 fffff800`82b2a2b0 : ffffc98a`b44bba30 00000000`00000000 00000000`00000000 00000000`00000000 : USBXHCI!Control_ProcessTransferEventWithED1+0x48d
fffff800`7be67640 fffff800`82b298d2 : ffffc98a`b4575580 00000000`00000002 00000000`018001c0 fffff800`7be67770 : USBXHCI!Control_EP_TransferEventHandler+0x10
fffff800`7be67670 fffff800`82b1ba4f : 00000000`0000002b fffff800`7be67761 ffffc98a`b0f114e0 fffff800`82b034b9 : USBXHCI!TR_TransferEventHandler+0x16
fffff800`7be676a0 fffff800`82b3c2f2 : fffff800`7be677f8 fffff800`7be677c8 00000000`00000000 fffff800`7be677d0 : USBXHCI!Endpoint_TransferEventHandler+0x167
fffff800`7be67720 fffff800`82b1ea3c : ffffc98a`b0f7e6c0 fffff800`7be67819 00000000`00000000 ffffc98a`b402f420 : USBXHCI!UsbDevice_TransferEventHandler+0xa6
fffff800`7be67780 fffff800`82b1f55c : 00000000`00000000 00000000`00000001 00000000`00000000 ffffc98a`b0f7e4c0 : USBXHCI!Interrupter_DeferredWorkProcessor+0x578
fffff800`7be67880 fffff800`7a7226ac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : USBXHCI!Interrupter_WdfEvtInterruptDpc+0xc
fffff800`7be678b0 fffff800`76a506ea : fffff800`74639180 00000000`00000001 fffff800`7be678a8 00000000`00000000 : Wdf01000!FxInterrupt::_InterruptDpcThunk+0x9c [minkernel\wdf\framework\shared\irphandlers\pnp\km\interruptobjectkm.cpp @ 404]
fffff800`7be678f0 fffff800`76a4fd3f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExecuteAllDpcs+0x30a
fffff800`7be67a30 fffff800`76bc5ece : 00000000`00000000 fffff800`74639180 fffff800`76f91400 ffffc98a`b722e080 : nt!KiRetireDpcList+0x1ef
fffff800`7be67c60 00000000`00000000 : fffff800`7be68000 fffff800`7be62000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x7e


SYMBOL_NAME: USBXHCI!Control_Transfer_Complete+1d7

MODULE_NAME: USBXHCI

IMAGE_NAME: USBXHCI.SYS

IMAGE_VERSION: 10.0.18362.900

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 1d7

FAILURE_BUCKET_ID: 0x44_USBXHCI!Control_Transfer_Complete

OS_VERSION: 10.0.18362.1

BUILDLAB_STR: 19h1_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {9bad8ac1-be58-4d6c-7c2e-d372963cb065}

Followup: MachineOwner
---------
 
ASUS'un hızlı şarj uygulaması var Ai Charger. Onunla iPhone şarj ediyordum. Acaba o mu sebebiyet verdi? Ama sürekli kullandığım bir şey. BIOS da B450-F kullanıcılarının en stabil bu sürüm olduğunu söyledikleri için güncellememiştim.
Büyük ihtimalle onun yüzünden. Dump'a göre bir USB sürücüsü sorun çıkarmış. Başka portlarda deneyin.
 
Büyük ihtimalle onun yüzünden. Dump'a göre bir USB sürücüsü sorun çıkarmış. Başka portlarda deneyin.
Bir de ben 1909 kullanıyorum. Orada yanlış görünüyor olmasın? 2004'ü yüklemedim sadece. Güncelleştirmeler kısmında da sadece 2004 sürümü görünüyor.

1909.png
 
Uyarı! Bu konu 6 yıl önce açıldı.
Muhtemelen daha fazla tartışma gerekli değildir ki bu durumda yeni bir konu başlatmayı öneririz. Eğer yine de cevabınızın gerekli olduğunu düşünüyorsanız buna rağmen cevap verebilirsiniz.

Technopat Haberler

Geri
Yukarı