MULTIPLE_IRP_COMPLETE_REQUESTS mavi ekran hatası

iemralan · 24 Eylül 2022

Merhaba, dump dosyalarını ekliyorum.

092422-44515-01.dmp

drive.google.com

092422-11265-01.dmp

drive.google.com

EgeN7 · 24 Eylül 2022

Merhaba,

BIOS sürümünüz epey bir eski. 2018'den kalma F7 sürümünü kullanıyorsunuz. Son sürüm 2021 sonunda çıkan F11 sürümü. Bu 3 yıllık süre içerisinde paylaşılan BIOS sürümleriyle kümülatif (birikimli) bir şekilde farklı kategorilerde farklı çözümler sağlanmış.

BIOS Listesi: Z390 AORUS MASTER - Destek
Güncel BIOS: mb_bios_z390-aorus-master_f11.zip

BIOS güncellemeden önce ayarlarınız varsa onları not edin veya fotoğrafını çekin, BIOS güncelleme sonrası BIOS ayarları varsayılan olarak sıfırlanacak.

Hataya kcache64.sys sebep olmuş gibi duruyor. İnternette bunun hangi programın/servisin sürücüsü olduğuna dair bir bilgi bulamadım. CPU microcode ile alakalı olabilir, çok karşılaştığım bir şey olmadığı için tahmin yürütüyorum. Zaten CPU microcode güncellemeleri size önerdiğim son BIOS sürümünde ve öncekilerde yapılmış. F11 sürümüne güncellediğinizde hatayı çözme olasılığı yüksek.

Dökümler:

Kod:

*******************************************************************************
*                                                                             *
*                        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: ffff980430574bd0, Address of the IRP
Arg2: 0000000000002543
Arg3: 0000000000000000
Arg4: 0000000000000000

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1030

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 2418

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

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

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

    Key  : Bugcheck.Code.DumpHeader
    Value: 0x44

    Key  : Bugcheck.Code.Register
    Value: 0x44

    Key  : Dump.Attributes.AsUlong
    Value: 8

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1


FILE_IN_CAB:  092422-11265-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

BUGCHECK_CODE:  44

BUGCHECK_P1: ffff980430574bd0

BUGCHECK_P2: 2543

BUGCHECK_P3: 0

BUGCHECK_P4: 0

IRP_ADDRESS: ffff980430574bd0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXPNP: 1 (!blackboxpnp)


CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:
ffffd882`7326f928 fffff802`1e8324e0     : 00000000`00000044 ffff9804`30574bd0 00000000`00002543 00000000`00000000 : nt!KeBugCheckEx
ffffd882`7326f930 fffff802`1e6f3ff3     : ffff9804`1eb67cf0 ffff9804`2d26ddd0 00000000`00000000 ffff9804`30574bd0 : nt!IopFreeIrp+0x13e4d0
ffffd882`7326f970 fffff802`2185575e     : ffff9804`1eb67cf0 ffff9804`248fd300 0a00000a`0aecf863 fffffac2`40e54dd0 : nt!IoFreeIrp+0x13
ffffd882`7326f9a0 ffff9804`1eb67cf0     : ffff9804`248fd300 0a00000a`0aecf863 fffffac2`40e54dd0 ffff9804`30574bd0 : kcache64+0x575e
ffffd882`7326f9a8 ffff9804`248fd300     : 0a00000a`0aecf863 fffffac2`40e54dd0 ffff9804`30574bd0 00000000`00000000 : 0xffff9804`1eb67cf0
ffffd882`7326f9b0 0a00000a`0aecf863     : fffffac2`40e54dd0 ffff9804`30574bd0 00000000`00000000 ffff9804`1eb67cf0 : 0xffff9804`248fd300
ffffd882`7326f9b8 fffffac2`40e54dd0     : ffff9804`30574bd0 00000000`00000000 ffff9804`1eb67cf0 fffff802`21854f20 : 0x0a00000a`0aecf863
ffffd882`7326f9c0 ffff9804`30574bd0     : 00000000`00000000 ffff9804`1eb67cf0 fffff802`21854f20 ffff8481`ca9aa000 : 0xfffffac2`40e54dd0
ffffd882`7326f9c8 00000000`00000000     : ffff9804`1eb67cf0 fffff802`21854f20 ffff8481`ca9aa000 ffffd882`7326fa60 : 0xffff9804`30574bd0


SYMBOL_NAME:  kcache64+575e

MODULE_NAME: kcache64

IMAGE_NAME:  kcache64.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  575e

FAILURE_BUCKET_ID:  0x44_kcache64!unknown_function

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {7cb52984-2464-f740-47af-bb7d3daa7eff}

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

Kod:

*******************************************************************************
*                                                                             *
*                        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: ffff8d89091bdb90, Address of the IRP
Arg2: 0000000000002543
Arg3: 0000000000000000
Arg4: 0000000000000000

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1140

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 2732

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

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

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

    Key  : Bugcheck.Code.DumpHeader
    Value: 0x44

    Key  : Bugcheck.Code.Register
    Value: 0x44

    Key  : Dump.Attributes.AsUlong
    Value: 8

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1


FILE_IN_CAB:  092422-44515-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

BUGCHECK_CODE:  44

BUGCHECK_P1: ffff8d89091bdb90

BUGCHECK_P2: 2543

BUGCHECK_P3: 0

BUGCHECK_P4: 0

IRP_ADDRESS: ffff8d89091bdb90

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXPNP: 1 (!blackboxpnp)


CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:
fffffa09`deb07928 fffff800`0bcdb4e0     : 00000000`00000044 ffff8d89`091bdb90 00000000`00002543 00000000`00000000 : nt!KeBugCheckEx
fffffa09`deb07930 fffff800`0bb9cff3     : ffff8d88`fc9029c0 ffff8d89`1850c7c0 00000000`00000000 ffff8d89`091bdb90 : nt!IopFreeIrp+0x13e4d0
fffffa09`deb07970 fffff800`0e68575e     : ffff8d88`fc9029c0 ffff8d88`fc9d5ae0 0a00000a`7d0d0863 ffff84d4`c0a64b20 : nt!IoFreeIrp+0x13
fffffa09`deb079a0 ffff8d88`fc9029c0     : ffff8d88`fc9d5ae0 0a00000a`7d0d0863 ffff84d4`c0a64b20 ffff8d89`091bdb90 : kcache64+0x575e
fffffa09`deb079a8 ffff8d88`fc9d5ae0     : 0a00000a`7d0d0863 ffff84d4`c0a64b20 ffff8d89`091bdb90 00000000`00000000 : 0xffff8d88`fc9029c0
fffffa09`deb079b0 0a00000a`7d0d0863     : ffff84d4`c0a64b20 ffff8d89`091bdb90 00000000`00000000 ffff8d88`fc9029c0 : 0xffff8d88`fc9d5ae0
fffffa09`deb079b8 ffff84d4`c0a64b20     : ffff8d89`091bdb90 00000000`00000000 ffff8d88`fc9029c0 fffff800`0e684f20 : 0x0a00000a`7d0d0863
fffffa09`deb079c0 ffff8d89`091bdb90     : 00000000`00000000 ffff8d88`fc9029c0 fffff800`0e684f20 ffffa981`4c954000 : 0xffff84d4`c0a64b20
fffffa09`deb079c8 00000000`00000000     : ffff8d88`fc9029c0 fffff800`0e684f20 ffffa981`4c954000 fffffa09`deb07a60 : 0xffff8d89`091bdb90


SYMBOL_NAME:  kcache64+575e

MODULE_NAME: kcache64

IMAGE_NAME:  kcache64.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  575e

FAILURE_BUCKET_ID:  0x44_kcache64!unknown_function

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {7cb52984-2464-f740-47af-bb7d3daa7eff}

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

Şu an kullandığınız BIOS bilgileri:

Kod:

Machine ID Information [From Smbios 2.8, DMIVersion 0, Size=4778]
BiosVersion = F7
BiosReleaseDate = 12/04/2018
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = Z390 AORUS MASTER
BaseBoardProduct = Z390 AORUS MASTER-CF
BaseBoardVersion = x.x

iemralan · 25 Eylül 2022

EgeN7 dedi:

Merhaba,

BIOS sürümünüz epey bir eski. 2018'den kalma F7 sürümünü kullanıyorsunuz. Son sürüm 2021 sonunda çıkan F11 sürümü. Bu 3 yıllık süre içerisinde paylaşılan BIOS sürümleriyle kümülatif (birikimli) bir şekilde farklı kategorilerde farklı çözümler sağlanmış.

BIOS listesi: Z390 AORUS MASTER - Destek
Güncel BIOS: mb_bios_z390-aorus-master_f11.zip

BIOS güncellemeden önce ayarlarınız varsa onları not edin veya fotoğrafını çekin, BIOS güncelleme sonrası BIOS ayarları varsayılan olarak sıfırlanacak.

Hataya kcache64.sys sebep olmuş gibi duruyor. İnternette bunun hangi programın/servisin sürücüsü olduğuna dair bir bilgi bulamadım. CPU microcode ile alakalı olabilir, çok karşılaştığım bir şey olmadığı için tahmin yürütüyorum. Zaten CPU microcode güncellemeleri size önerdiğim son BIOS sürümünde ve öncekilerde yapılmış. F11 sürümüne güncellediğinizde hatayı çözme olasılığı yüksek.

Dökümler:

Kod:

*******************************************************************************
* *
* 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: ffff980430574bd0, Address of the IRP.
Arg2: 0000000000002543.
Arg3: 0000000000000000.
Arg4: 0000000000000000.

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

KEY_VALUES_STRING: 1

 Key : Analysis.CPU.mSec
 Value: 1030.

 Key : Analysis.DebugAnalysisManager
 Value: Create.

 Key : Analysis.Elapsed.mSec
 Value: 2418.

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

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

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

 Key : Bugcheck.Code.DumpHeader
 Value: 0x44.

 Key : Bugcheck.Code.Register
 Value: 0x44.

 Key : Dump.Attributes.AsUlong
 Value: 8

 Key : Dump.Attributes.KernelGeneratedTriageDump
 Value: 1

FILE_IN_CAB: 092422-11265-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8.
 Kernel Generated Triage Dump.

BUGCHECK_CODE: 44.

BUGCHECK_P1: ffff980430574bd0.

BUGCHECK_P2: 2543.

BUGCHECK_P3: 0

BUGCHECK_P4: 0

IRP_ADDRESS: ffff980430574bd0.

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXPNP: 1 (!blackboxpnp)

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System.

STACK_TEXT:
ffffd882`7326f928 fffff802`1e8324e0 : 00000000`00000044 ffff9804`30574bd0 00000000`00002543 00000000`00000000 : nt!KeBugCheckEx
ffffd882`7326f930 fffff802`1e6f3ff3 : ffff9804`1eb67cf0 ffff9804`2d26ddd0 00000000`00000000 ffff9804`30574bd0 : nt!IopFreeIrp+0x13e4d0
ffffd882`7326f970 fffff802`2185575e : ffff9804`1eb67cf0 ffff9804`248fd300 0a00000a`0aecf863 fffffac2`40e54dd0 : nt!IoFreeIrp+0x13
ffffd882`7326f9a0 ffff9804`1eb67cf0 : ffff9804`248fd300 0a00000a`0aecf863 fffffac2`40e54dd0 ffff9804`30574bd0 : kcache64+0x575e
ffffd882`7326f9a8 ffff9804`248fd300 : 0a00000a`0aecf863 fffffac2`40e54dd0 ffff9804`30574bd0 00000000`00000000 : 0xffff9804`1eb67cf0
ffffd882`7326f9b0 0a00000a`0aecf863 : fffffac2`40e54dd0 ffff9804`30574bd0 00000000`00000000 ffff9804`1eb67cf0 : 0xffff9804`248fd300
ffffd882`7326f9b8 fffffac2`40e54dd0 : ffff9804`30574bd0 00000000`00000000 ffff9804`1eb67cf0 fffff802`21854f20 : 0x0a00000a`0aecf863
ffffd882`7326f9c0 ffff9804`30574bd0 : 00000000`00000000 ffff9804`1eb67cf0 fffff802`21854f20 ffff8481`ca9aa000 : 0xfffffac2`40e54dd0
ffffd882`7326f9c8 00000000`00000000 : ffff9804`1eb67cf0 fffff802`21854f20 ffff8481`ca9aa000 ffffd882`7326fa60 : 0xffff9804`30574bd0

SYMBOL_NAME: kcache64+575e

MODULE_NAME: kcache64.

IMAGE_NAME: kcache64.sys

STACK_COMMAND: .cxr; .ecxr ; kb.

BUCKET_ID_FUNC_OFFSET: 575e.

FAILURE_BUCKET_ID: 0x44_kcache64!unknown_function

OSPLATFORM_TYPE: x64.

OSNAME: Windows 10.

FAILURE_ID_HASH: {7cb52984-2464-f740-47af-bb7d3daa7eff}

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

Kod:

*******************************************************************************
* *
* 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: ffff8d89091bdb90, Address of the IRP.
Arg2: 0000000000002543.
Arg3: 0000000000000000.
Arg4: 0000000000000000.

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

KEY_VALUES_STRING: 1

 Key : Analysis.CPU.mSec
 Value: 1140.

 Key : Analysis.DebugAnalysisManager
 Value: Create.

 Key : Analysis.Elapsed.mSec
 Value: 2732.

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

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

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

 Key : Bugcheck.Code.DumpHeader
 Value: 0x44.

 Key : Bugcheck.Code.Register
 Value: 0x44.

 Key : Dump.Attributes.AsUlong
 Value: 8

 Key : Dump.Attributes.KernelGeneratedTriageDump
 Value: 1

FILE_IN_CAB: 092422-44515-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8.
 Kernel Generated Triage Dump.

BUGCHECK_CODE: 44.

BUGCHECK_P1: ffff8d89091bdb90.

BUGCHECK_P2: 2543.

BUGCHECK_P3: 0

BUGCHECK_P4: 0

IRP_ADDRESS: ffff8d89091bdb90.

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXPNP: 1 (!blackboxpnp)

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System.

STACK_TEXT:
fffffa09`deb07928 fffff800`0bcdb4e0 : 00000000`00000044 ffff8d89`091bdb90 00000000`00002543 00000000`00000000 : nt!KeBugCheckEx
fffffa09`deb07930 fffff800`0bb9cff3 : ffff8d88`fc9029c0 ffff8d89`1850c7c0 00000000`00000000 ffff8d89`091bdb90 : nt!IopFreeIrp+0x13e4d0
fffffa09`deb07970 fffff800`0e68575e : ffff8d88`fc9029c0 ffff8d88`fc9d5ae0 0a00000a`7d0d0863 ffff84d4`c0a64b20 : nt!IoFreeIrp+0x13
fffffa09`deb079a0 ffff8d88`fc9029c0 : ffff8d88`fc9d5ae0 0a00000a`7d0d0863 ffff84d4`c0a64b20 ffff8d89`091bdb90 : kcache64+0x575e
fffffa09`deb079a8 ffff8d88`fc9d5ae0 : 0a00000a`7d0d0863 ffff84d4`c0a64b20 ffff8d89`091bdb90 00000000`00000000 : 0xffff8d88`fc9029c0
fffffa09`deb079b0 0a00000a`7d0d0863 : ffff84d4`c0a64b20 ffff8d89`091bdb90 00000000`00000000 ffff8d88`fc9029c0 : 0xffff8d88`fc9d5ae0
fffffa09`deb079b8 ffff84d4`c0a64b20 : ffff8d89`091bdb90 00000000`00000000 ffff8d88`fc9029c0 fffff800`0e684f20 : 0x0a00000a`7d0d0863
fffffa09`deb079c0 ffff8d89`091bdb90 : 00000000`00000000 ffff8d88`fc9029c0 fffff800`0e684f20 ffffa981`4c954000 : 0xffff84d4`c0a64b20
fffffa09`deb079c8 00000000`00000000 : ffff8d88`fc9029c0 fffff800`0e684f20 ffffa981`4c954000 fffffa09`deb07a60 : 0xffff8d89`091bdb90

SYMBOL_NAME: kcache64+575e

MODULE_NAME: kcache64.

IMAGE_NAME: kcache64.sys

STACK_COMMAND: .cxr; .ecxr ; kb.

BUCKET_ID_FUNC_OFFSET: 575e.

FAILURE_BUCKET_ID: 0x44_kcache64!unknown_function

OSPLATFORM_TYPE: x64.

OSNAME: Windows 10.

FAILURE_ID_HASH: {7cb52984-2464-f740-47af-bb7d3daa7eff}

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

Şu an kullandığınız BIOS bilgileri:

Kod:

Machine ID Information [From Smbios 2.8, DMIVersion 0, Size=4778]
BiosVersion = F7.
BiosReleaseDate = 12/04/2018
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = Z390 AORUS MASTER.
BaseBoardProduct = Z390 AORUS MASTER-CF
BaseBoardVersion = x.x

Merhaba, cevabınız için çok teşekkürler. BIOS'u en son sürüme güncelledim. Hataya sebep olan dosya disksiz boot yazılımının bir parçası. İlgili programı da gece yeniden yükledim. Bakalım aynı hatayı tekrar alacak mıyım.

MULTIPLE_IRP_COMPLETE_REQUESTS mavi ekran hatası

Ayrıntılı düzenleme

iemralan

Hectopat

092422-44515-01.dmp

092422-11265-01.dmp

EgeN7

Megapat

iemralan

Hectopat

Benzer konular

Yeni konular

Yeni mesajlar

Gizliliğinize önem veriyoruz