Çözüldü MpKslDrv.sys DRIVER_IRQL_NOT_LESS_OR_EQUAL (D1) mavi ekran hatası

Bu konu çözüldü olarak işaretlenmiştir. Çözülmediğini düşünüyorsanız konuyu rapor edebilirsiniz.
İşletim sistemi
Windows 10
1

142404

Kilopat
Katılım
23 Kasım 2016
Mesajlar
109
RAM
CORSAIR 16GB (2x8GB) Vengeance Siyah DDR4 3000MHz AMA 2133 TE ÇALIŞIYOR
SSD veya HDD modeli
Kingston A2000 500gb 2200/2000mb/s Nvme M.2
Ekran kartı
MSI GEFORCE GTX 1660 TI VENTUS XS 6G 6GB GDDR6 192
Anakart
msi b360m-a pro max
İşlemci
Intel(R) Core(TM) i5-9400F
Merhaba,

Dump dosyası son iki gündür Age of Empires 4 oynarken mavi ekran alıyorum ve bu durum tamamen rastgele oluyor bazen 12 saat oynuyorum bir şey olmuyor. Bazen de oyuna gireli 5 dakika oluyor tak diye mavi ekran geliyor. Hataların birinden sonra bilgisayar açılırken XMP overclock hatası verdi BIOS'ta bende BIOS'tan XMP profilini kapattım ama XMP ile herhangi bir ayar değişmiyordu, kapatmama rağmen yine bu hatayı aldım Memtest SSD testlerim CPU ve GPU stress tesleride temiz çıktı.
 
Çözüm
lazye
Hocam iki ihtimal var ya anakart üzerindeki sokette bir sıkıntı var ya da RAM de bir sıkıntı var. Ben RAM de bir sıkıntı olduğunu düşünüyorum etrafında arkadaşın da vs. RAM alabilirsin denemelik 1-2 günlük o şekilde deneyin. Eğer sorunsuz kullanıyorsan o zaman RAM degistirmeni tavsiye ederim. Bu arada Memtest86 uygulaması flash bellekten dolayı error vermez sadece RAM'leri test eder.
Tarihe göre sırala Puana göre sırala
* Aldığınız ilk mavi ekran 6 Mart 2023'ten kalma. Neden olduğu çok belli olmuyor. Ta ki sürücüler listesine göz atana kadar. Corsair yazılımları, XIGNCODE, ProtonVPN, WireGuard gibi potansiyel çakışma/problem oluşturabilecek araçlar var.

* Ancak yeni aldığınız mavi ekranda bu araçları göremedim, zaten kaldır kaldıra bir tek AOE IV kaldı demişsiniz. Bu mavi ekran NVIDIA ekran kartı sürücüsünden kaynaklanmış.

* DDU ile NVIDIA sürücülerini tamamen temizleyip güncelini yükler misiniz?

- Güncel sürücüyü indirin: 535.98 WHQL
- Daha sonra DDU ile Sürücü Kaldırma rehberini takip edin.


* Ayrıca Windows sürümünüz de epey eski kalmış (19041).
* Windows Update ile son sürüme güncelleyin.
msedge_snp9uIfhL9.png



Kod: 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 000000000000003f, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff80696e557af, address which referenced memory

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1811

    Key  : Analysis.Elapsed.mSec
    Value: 2240

    Key  : Analysis.IO.Other.Mb
    Value: 0

    Key  : Analysis.IO.Read.Mb
    Value: 0

    Key  : Analysis.IO.Write.Mb
    Value: 0

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0xd1

    Key  : Dump.Attributes.AsUlong
    Value: 8

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Failure.Bucket
    Value: AV_nvlddmkm!unknown_function

    Key  : Failure.Hash
    Value: {7eea5677-f68d-2154-717e-887e07e55cd3}


BUGCHECK_CODE:  d1

BUGCHECK_P1: 3f

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff80696e557af

FILE_IN_CAB:  060423-12453-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

READ_ADDRESS: fffff8066e8fb390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
 000000000000003f

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

TRAP_FRAME:  fffff80671874ba0 -- (.trap 0xfffff80671874ba0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000000000003f rbx=0000000000000000 rcx=00000000ffffffff
rdx=ffff800cac3ba000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80696e557af rsp=fffff80671874d30 rbp=fffff80671874ee0
 r8=0000000000000001  r9=0000000000000000 r10=0000000000000000
r11=fffff80671874dd8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
nvlddmkm+0x1857af:
fffff806`96e557af 3908            cmp     dword ptr [rax],ecx ds:00000000`0000003f=????????
Resetting default scope

STACK_TEXT:
fffff806`71874a58 fffff806`6e00fd29     : 00000000`0000000a 00000000`0000003f 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff806`71874a60 fffff806`6e00b8e3     : 00000000`00000200 fffff806`96d7d0d6 00000050`71875030 00000002`00000000 : nt!KiBugCheckDispatch+0x69
fffff806`71874ba0 fffff806`96e557af     : ffff800c`ac3ba000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x463
fffff806`71874d30 ffff800c`ac3ba000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nvlddmkm+0x1857af
fffff806`71874d38 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 fffff806`96e555db : 0xffff800c`ac3ba000


SYMBOL_NAME:  nvlddmkm+1857af

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  1857af

FAILURE_BUCKET_ID:  AV_nvlddmkm!unknown_function

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {7eea5677-f68d-2154-717e-887e07e55cd3}

Followup:     MachineOwner
---------
 
Artı 0 Eksi
EgeN7 dedi:
* Aldığınız ilk mavi ekran 6 Mart 2023'ten kalma. Neden olduğu çok belli olmuyor. Ta ki sürücüler listesine göz atana kadar. Corsair yazılımları, xıgncode, ProtonVPN, wireguard gibi potansiyel çakışma/problem oluşturabilecek araçlar var.

* Ancak yeni aldığınız mavi ekranda bu araçları göremedim, zaten kaldır kaldıra bir tek AOE IV kaldı demişsiniz. Bu mavi ekran NVIDIA ekran kartı sürücüsünden kaynaklanmış.

* DDU ile NVIDIA sürücülerini tamamen temizleyip güncelini yükler misiniz?

- Güncel sürücüyü indirin: 535.98 WHQL
- Daha sonra DDU ile Sürücü Kaldırma rehberini takip edin.

* Ayrıca Windows sürümünüz de epey eski kalmış (19041).
* Windows Update ile son sürüme güncelleyin.
Eki Görüntüle 1806105

Kod: 
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an.
interrupt request level (IRQL) that is too high. This is usually.
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 000000000000003f, memory referenced.
Arg2: 0000000000000002, IRQL.
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg4: fffff80696e557af, address which referenced memory.

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

KEY_VALUES_STRING: 1

 Key : Analysis.CPU.mSec
 Value: 1811.

 Key : Analysis.Elapsed.mSec
 Value: 2240.

 Key : Analysis.IO.Other.Mb
 Value: 0

 Key : Analysis.IO.Read.Mb
 Value: 0

 Key : Analysis.IO.Write.Mb
 Value: 0

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

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

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

 Key : Bugcheck.Code.LegacyAPI
 Value: 0xd1.

 Key : Dump.Attributes.AsUlong
 Value: 8

 Key : Dump.Attributes.KernelGeneratedTriageDump
 Value: 1

 Key : Failure.Bucket
 Value: AV_nvlddmkm!unknown_function

 Key : Failure.Hash
 Value: {7eea5677-f68d-2154-717e-887e07e55cd3}

BUGCHECK_CODE: d1.

BUGCHECK_P1: 3f.

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff80696e557af.

FILE_IN_CAB: 060423-12453-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8.
 Kernel Generated Triage Dump.

READ_ADDRESS: fffff8066e8fb390: Unable to get MiVisibleState.
Unable to get NonPagedPoolStart.
Unable to get NonPagedPoolEnd.
Unable to get PagedPoolStart.
Unable to get PagedPoolEnd.
unable to get nt!MmSpecialPagesInUse
 000000000000003f.

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System.

TRAP_FRAME: fffff80671874ba0 -- (.trap 0xfffff80671874ba0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000000000003f rbx=0000000000000000 rcx=00000000ffffffff
rdx=ffff800cac3ba000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80696e557af rsp=fffff80671874d30 rbp=fffff80671874ee0
 r8=0000000000000001 r9=0000000000000000 r10=0000000000000000
r11=fffff80671874dd8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc.
nvlddmkm+0x1857af:
fffff806`96e557af 3908 cmp dword ptr [rax],ecx ds:00000000`0000003f=????????
Resetting default scope.

STACK_TEXT:
fffff806`71874a58 fffff806`6e00fd29 : 00000000`0000000a 00000000`0000003f 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff806`71874a60 fffff806`6e00b8e3 : 00000000`00000200 fffff806`96d7d0d6 00000050`71875030 00000002`00000000 : nt!KiBugCheckDispatch+0x69
fffff806`71874ba0 fffff806`96e557af : ffff800c`ac3ba000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x463
fffff806`71874d30 ffff800c`ac3ba000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nvlddmkm+0x1857af
fffff806`71874d38 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff806`96e555db : 0xffff800c`ac3ba000

SYMBOL_NAME: nvlddmkm+1857af

MODULE_NAME: nvlddmkm.

IMAGE_NAME: nvlddmkm.sys

STACK_COMMAND: .cxr; .ecxr ; kb.

BUCKET_ID_FUNC_OFFSET: 1857af.

FAILURE_BUCKET_ID: AV_nvlddmkm!unknown_function

OSPLATFORM_TYPE: x64.

OSNAME: Windows 10.

FAILURE_ID_HASH: {7eea5677-f68d-2154-717e-887e07e55cd3}

Followup: MachineOwner.
---------
Genişletmek için tıkla...

Doğru dump siz söyleyince fark ettim evet ilk attığım dosya eski olan kayıtmış ilk aldığımı yine paylaşayım dedim dediğiniz gibi DDU ile temiz kurulum yaptım ve Windows'umu güncelleştirdim umarım tekrardan karşılaşmam durumla teşekkür ederim. Bu arada ICUE'yi geri yükledim mecburen çünkü kulaklığımın sarjını göremiyorum.
--------------------------------------------

1685841296586.png

DUMP maalesef durum yine aynı aldığım yeni hata. Her aldığım mavi ekran diğerinden farklı bu da şimdi böyle çıkıyor acaba donanımsal olarak RAM sorunu mu var
 
Son düzenleme:
Artı 0 Eksi
Şu an iki doğrultuda gidiyor konu. Ya hataları adım adım çözüyoruz ve bir sonraki, yenisi geliyor; ya da hatanın kaynağı hala sinsice bir köşede bekliyor.

* Güncel chipset sürücülerini kurmanız gerekiyor ama nedense Intel'in kendi sitesinden kaldırılmış.

Intel® B365 Chipset Downloads, Drivers and Software | Intel

Intel® B365 Chipset - Download supporting resources inclusive drivers, software, bios, and firmware updates.
www.intel.com www.intel.com


* Anakartınızın sürücü sayfasında ise eski chipset sürücüleri var. Her ihtimale karşı yüklü değilse kurar mısınız? Güncel değilse de güncellersiniz.
www.msi.com

B365M PRO-VH

Intel LGA 1151 B365 ATX professional motherboard, M.2, MSI PRO
www.msi.com www.msi.com

msedge_bo2hdiwRMw.png



* Ses sürücünüz de güncel değilmiş.
Rich (BB code): 
fffff803`52190000 fffff803`527b8000   RTKVHD64   (deferred)
    Image path: RTKVHD64.sys
    Image name: RTKVHD64.sys
    Browse all global symbols  functions  data
    Timestamp:        Thu Mar 30 13:14:35 2023 (6425610B)

* Aynı şekilde eskisini silip aşağıdan 23 Mayıs 2023 tarihli sürücüyü indirip kurun.
www.msi.com

B365M PRO-VH

Intel LGA 1151 B365 ATX professional motherboard, M.2, MSI PRO
www.msi.com www.msi.com
msedge_PTsHDpdfha.png



* SSD'nizin sağlığı ne durumda? Firmware güncellemesi var mı kontrol ettiniz mi?

* HDD var mı sistemde? Varsa HD Tune ile Health sekmesini paylaşın, Error Scan sekmesinden de Quick Scan kapalı olacak şekilde tarama yapın.


* AOE IV ile alakalı RAM problemleri varmış zamanında. Şu an ne durumda bilmiyorum. Acaba fiziksel belleği doldurup sanal belleği mi kullanmaya başlıyor?
Ama o zaman page file hatasını alırdınız yüksek ihtimalle. Oyun içerisinde RAM kullanımını takip eder misiniz? MSI Afterburner gibi bir programla olabilir mesela.


Kod: 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common BugCheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff803421fc977, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception

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

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: ExceptionRecord                               ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: ContextRecord                                 ***
***                                                                   ***
*************************************************************************

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2125

    Key  : Analysis.Elapsed.mSec
    Value: 2331

    Key  : Analysis.IO.Other.Mb
    Value: 1

    Key  : Analysis.IO.Read.Mb
    Value: 0

    Key  : Analysis.IO.Write.Mb
    Value: 1

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x1e

    Key  : Dump.Attributes.AsUlong
    Value: 8

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Failure.Bucket
    Value: AV_R_USBXHCI!WPP_RECORDER_SF_DDDqqq

    Key  : Failure.Hash
    Value: {86cdab07-13cb-42e9-0841-7ed8f1156452}


BUGCHECK_CODE:  1e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff803421fc977

BUGCHECK_P3: 0

BUGCHECK_P4: ffffffffffffffff

FILE_IN_CAB:  060423-12390-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: fffff8032dcfb390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
 ffffffffffffffff

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:
fffff803`3068b8e8 fffff803`2d460c23     : 00000000`0000001e ffffffff`c0000005 fffff803`421fc977 00000000`00000000 : nt!KeBugCheckEx
fffff803`3068b8f0 fffff803`2d3fd0d2     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x1792a3
fffff803`3068bfb0 fffff803`2d3fd0a0     : fffff803`2d410165 ffffbe0c`00000000 ffffbe0c`e822b330 ffffbe0c`f54e2010 : nt!KxExceptionDispatchOnExceptionStack+0x12
fffff803`30675068 fffff803`2d410165     : ffffbe0c`00000000 ffffbe0c`e822b330 ffffbe0c`f54e2010 fffff803`30675350 : nt!KiExceptionDispatchOnExceptionStackContinue
fffff803`30675070 fffff803`2d40b75a     : fffff803`30675321 fffff803`5175636b ffffbe0c`ea5e1200 fffff803`30675300 : nt!KiExceptionDispatch+0x125
fffff803`30675250 fffff803`421fc977     : ffffbe0c`e51070e0 ffffbe0c`e51070e0 00000000`00000008 ffffbe0c`e093aa20 : nt!KiGeneralProtectionFault+0x31a
fffff803`306753e0 ffffbe0c`e51070e0     : ffffbe0c`e51070e0 00000000`00000008 ffffbe0c`e093aa20 fffff803`30675481 : 0xfffff803`421fc977
fffff803`306753e8 ffffbe0c`e51070e0     : 00000000`00000008 ffffbe0c`e093aa20 fffff803`30675481 fffff803`431edf46 : 0xffffbe0c`e51070e0
fffff803`306753f0 00000000`00000008     : ffffbe0c`e093aa20 fffff803`30675481 fffff803`431edf46 fffff803`30670037 : 0xffffbe0c`e51070e0
fffff803`306753f8 ffffbe0c`e093aa20     : fffff803`30675481 fffff803`431edf46 fffff803`30670037 fffff803`306754d8 : 0x8
fffff803`30675400 fffff803`30675481     : fffff803`431edf46 fffff803`30670037 fffff803`306754d8 00000000`00000000 : 0xffffbe0c`e093aa20
fffff803`30675408 fffff803`431edf46     : fffff803`30670037 fffff803`306754d8 00000000`00000000 ffffbe0c`e9141bd0 : 0xfffff803`30675481
fffff803`30675410 fffff803`431ec0b1     : ffffbe0c`e9141bd0 00000000`0000000a ffffbe0c`e9141c60 fffff803`30675668 : USBXHCI!WPP_RECORDER_SF_DDDqqq+0xc6
fffff803`306754b0 fffff803`431ebea0     : 00000000`00000004 fffff803`30675620 00000000`00000000 ffffbe0c`e511e860 : USBXHCI!Bulk_ProcessTransferEventWithED1+0x1fd
fffff803`30675560 fffff803`431e6911     : 00000000`00000004 fffff803`30675638 00000000`00000008 fffff803`30675640 : USBXHCI!Bulk_EP_TransferEventHandler+0x10
fffff803`30675590 fffff803`431e6445     : 00000000`00000780 000041f3`20e4c500 ffffbe0c`e4b78db0 ffffbe0c`e4f2aa70 : USBXHCI!Endpoint_TransferEventHandler+0xb1
fffff803`306755f0 fffff803`431e611c     : ffffbe0c`e4f46368 fffff803`28077180 000041f3`27185308 fffff803`30675710 : USBXHCI!Interrupter_DeferredWorkProcessor+0x315
fffff803`306756f0 fffff803`2eba38f6     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : USBXHCI!Interrupter_WdfEvtInterruptDpc+0xc
fffff803`30675720 fffff803`2d28b57e     : fffff803`2807a240 00000000`00000000 fffff803`30675a20 fffff803`28077180 : Wdf01000!FxInterrupt::_InterruptDpcThunk+0xa6 [minkernel\wdf\framework\shared\irphandlers\pnp\km\interruptobjectkm.cpp @ 410]
fffff803`30675760 fffff803`2d28a864     : 00000000`00000000 00000000`00000000 00000000`00140001 00000000`00000000 : nt!KiExecuteAllDpcs+0x30e
fffff803`306758d0 fffff803`2d4008be     : 00000000`00000000 fffff803`28077180 fffff803`2dd27a00 ffffbe0c`e7664080 : nt!KiRetireDpcList+0x1f4
fffff803`30675b60 00000000`00000000     : fffff803`30676000 fffff803`3066f000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e


SYMBOL_NAME:  USBXHCI!WPP_RECORDER_SF_DDDqqq+c6

MODULE_NAME: USBXHCI

IMAGE_NAME:  USBXHCI.SYS

IMAGE_VERSION:  10.0.19041.3025

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  c6

FAILURE_BUCKET_ID:  AV_R_USBXHCI!WPP_RECORDER_SF_DDDqqq

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {86cdab07-13cb-42e9-0841-7ed8f1156452}

Followup:     MachineOwner
---------
 
Son düzenleme:
Artı 0 Eksi

Benzer konular

serkan0441
  • Soru
Driver IRQL NOT LESS OR EQUAL mavi ekran hatası
Mesaj
0
Görüntüleme
216
serkan0441
serkan0441
Starixx1
  • Soru
Windows 10 ''DRIVER IRQL NOT LESS OR EQUAL'' mavi ekran hatası
Mesaj
2
Görüntüleme
658
Starixx1
Starixx1
K
  • Soru
Windows 10 "DRIVER IRQL NOT LESS OR EQUAL" mavi ekran hatası
2 3 4
Mesaj
38
Görüntüleme
5B
Kaan Atbaş
K
snrkaan
  • Soru
Windows 10 "Driver irql not less or equal" mavi ekran hatası
Mesaj
3
Görüntüleme
1B
Murat5038
Murat5038
T
  • Soru
Windows 10 DRIVER IRQL NOT LESS OR EQUAL mavi ekran hatası
Mesaj
6
Görüntüleme
656
thisslewis
T

Yeni konular

Yeni mesajlar

Geri
Yukarı