Çözüldü Huawei Matebook D15 WDF_VIOLATION mavi ekran hatası

EgeN7 dedi:

Nisan ve Haziran'da DRIVER_CORRUPTED_EXPOOL (c5) bugcheck altında Riot Vanguard sürücüsü ile alakalı hatalar almışsınız.

WDF_VIOLATION'da ise dm9usb.sys yani USB To Fast Ethernet Adapter sürücüsü sebebiyle hata almışsınız. Sürücü sürümü ise eylül 2022 görünüyor.

Kod:Panoya kopyala

 Timestamp: Thu Sep 8 07:51:01 2022 (631974B5)

* Riot Vanguard çözümü için aşağıdaki konuya gidin, sadece Vanguard ile alakalı çözümü uygulayıp kendi konunuza geri dönün.

R5 4500 sistem mavi ekran verdi

Bilgisayarım mavi ekran verdi açılırken verdi ilk defa mavi ekran yedim. Bilgisayarımı hep özenli kullanırım neden oldu anlamadım. Hata: PAGE_FAULT_IN_NONPAGED_AREA Minidump: https://drive.google.com/file/d/1JsEV5EnR5YH7zQ6HH8cblOjzP4mm8ifz/view?usp=sharing Sistemim: Ryzen 5 4500. GTX 1660...

www.technopat.net

* USB to Fast Ethernet Adapter cihazınızın marka / modeli nedir? Veya kendiniz güncel sürücüyü adaptörün internet destek sayfasından bulabiliyorsanız indirin ve güncelleyin.

Dökümler:

Kod:Panoya kopyala

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

WDF_VIOLATION (10d)
The Kernel-Mode Driver Framework was notified that Windows detected an error
in a framework-based driver. In general, the dump file will yield additional
information about the driver that caused this BugCheck.
Arguments:
Arg1: 0000000000000005, A framework object handle of the incorrect type was passed to
 a framework object method.
Arg2: 0000000000000000, The handle value passed in.
Arg3: 0000000000001023, Reserved.
Arg4: ffff94869b8b9ae0, Reserved.

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

*** WARNING: Unable to verify timestamp for dm9usb.sys

KEY_VALUES_STRING: 1

 Key : Analysis.CPU.mSec
 Value: 1562

 Key : Analysis.Elapsed.mSec
 Value: 8775

 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: 156

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

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

 Key : Bugcheck.Code.LegacyAPI
 Value: 0x10d

 Key : Failure.Bucket
 Value: 0x10D_5_dm9usb!unknown_function

 Key : Failure.Hash
 Value: {f3b5c834-5454-4d7e-7854-898a5070d2c3}

 Key : WER.OS.Branch
 Value: ni_release

 Key : WER.OS.Version
 Value: 10.0.22621.1

BUGCHECK_CODE: 10d

BUGCHECK_P1: 5

BUGCHECK_P2: 0

BUGCHECK_P3: 1023

BUGCHECK_P4: ffff94869b8b9ae0

FILE_IN_CAB: 061823-8812-01.dmp

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffffa704`1096aaa8 fffff806`5c7a6390 : 00000000`0000010d 00000000`00000005 00000000`00000000 00000000`00001023 : nt!KeBugCheckEx
ffffa704`1096aab0 fffff806`5c7753f6 : 00000000`00040246 fffff806`58239f3b ffff9486`a22aa158 ffff9486`97c11160 : Wdf01000!FxVerifierBugCheckWorker+0x24 [minkernel\wdf\framework\shared\object\fxverifierbugcheck.cpp @ 87]
ffffa704`1096aaf0 fffff806`5c761466 : ffffea90`276aedd9 00000001`00000001 fffff806`5d523048 ffff9486`a22a91a0 : Wdf01000!FxObjectHandleGetPtr+0xf1c6 [minkernel\wdf\framework\shared\inc\private\common\fxhandle.h @ 328]
ffffa704`1096ab30 fffff806`579567b8 : 00000000`00000000 ffff9486`97c11160 00000000`00000000 fffff806`5d4545f0 : Wdf01000!imp_WdfWaitLockAcquire+0x26 [minkernel\wdf\framework\shared\support\fxwaitlockapi.cpp @ 134]
ffffa704`1096ab60 00000000`00000000 : ffff9486`97c11160 00000000`00000000 fffff806`5d4545f0 ffff9486`97c11000 : dm9usb+0x67b8

SYMBOL_NAME: dm9usb+67b8

MODULE_NAME: dm9usb

IMAGE_NAME: dm9usb.sys

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 67b8

FAILURE_BUCKET_ID: 0x10D_5_dm9usb!unknown_function

OS_VERSION: 10.0.22621.1

BUILDLAB_STR: ni_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {f3b5c834-5454-4d7e-7854-898a5070d2c3}

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

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_CORRUPTED_EXPOOL (c5)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is
caused by drivers that have corrupted the system pool. Run the driver
verifier against any new (or suspect) drivers, and if that doesn't turn up
the culprit, then use gflags to enable special pool.
Arguments:
Arg1: ffffbe857e24d323, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff8031dc9e08e, address which referenced memory

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

KEY_VALUES_STRING: 1

 Key : Analysis.CPU.mSec
 Value: 1375

 Key : Analysis.Elapsed.mSec
 Value: 9942

 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: 156

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

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

 Key : Bugcheck.Code.LegacyAPI
 Value: 0xc5

 Key : Failure.Bucket
 Value: 0xC5_2_vgk!unknown_function

 Key : Failure.Hash
 Value: {f440937e-e808-2f2e-10ad-7db228ddf2cc}

 Key : WER.OS.Branch
 Value: ni_release

 Key : WER.OS.Version
 Value: 10.0.22621.1

BUGCHECK_CODE: c5

BUGCHECK_P1: ffffbe857e24d323

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff8031dc9e08e

FILE_IN_CAB: 061323-11312-01.dmp

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: VALORANT-Win64-Shipping.exe

TRAP_FRAME: fffffd8932325570 -- (.trap 0xfffffd8932325570)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffbe8571200000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8031dc9e08e rsp=fffffd8932325700 rbp=0000000000000000
 r8=ffffd08f9b19bcb0 r9=0000000000000001 r10=ffffd08f9c524668
r11=fffffd8932325788 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
nt!ExFreePoolWithTag+0x7e:
fffff803`1dc9e08e f647f308 test byte ptr [rdi-0Dh],8 ds:ffffffff`fffffff3=??
Resetting default scope

STACK_TEXT:
fffffd89`32325428 fffff803`1d640fa9 : 00000000`0000000a ffffbe85`7e24d323 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffffd89`32325430 fffff803`1d63c634 : 00000276`cdcda917 00000000`00000000 00000000`00000000 ffffd08f`9b19bcb0 : nt!KiBugCheckDispatch+0x69
fffffd89`32325570 fffff803`1dc9e08e : 01000000`00100000 fffff803`2f29f5a4 00000000`00000f58 00000000`0000294c : nt!KiPageFault+0x474
fffffd89`32325700 fffff803`2f3c842f : fffff803`00000000 fffff803`2f2ce050 00000000`00000000 00000000`00000000 : nt!ExFreePoolWithTag+0x7e
fffffd89`32325790 fffff803`00000000 : fffff803`2f2ce050 00000000`00000000 00000000`00000000 00000000`00000001 : vgk+0x17842f
fffffd89`32325798 fffff803`2f2ce050 : 00000000`00000000 00000000`00000000 00000000`00000001 00000000`00000008 : 0xfffff803`00000000
fffffd89`323257a0 00000000`00000000 : 00000000`00000000 00000000`00000001 00000000`00000008 00000000`00000001 : vgk+0x7e050

SYMBOL_NAME: vgk+17842f

MODULE_NAME: vgk

IMAGE_NAME: vgk.sys

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 17842f

FAILURE_BUCKET_ID: 0xC5_2_vgk!unknown_function

OS_VERSION: 10.0.22621.1

BUILDLAB_STR: ni_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {f440937e-e808-2f2e-10ad-7db228ddf2cc}

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

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

WDF_VIOLATION (10d)
The Kernel-Mode Driver Framework was notified that Windows detected an error
in a framework-based driver. In general, the dump file will yield additional
information about the driver that caused this BugCheck.
Arguments:
Arg1: 0000000000000005, A framework object handle of the incorrect type was passed to
 a framework object method.
Arg2: 0000000000000000, The handle value passed in.
Arg3: 0000000000001023, Reserved.
Arg4: ffffc103baad86b0, Reserved.

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

*** WARNING: Unable to verify timestamp for dm9usb.sys

KEY_VALUES_STRING: 1

 Key : Analysis.CPU.mSec
 Value: 1375

 Key : Analysis.Elapsed.mSec
 Value: 2867

 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: 202

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

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

 Key : Bugcheck.Code.KiBugCheckData
 Value: 0x10d

 Key : Bugcheck.Code.LegacyAPI
 Value: 0x10d

 Key : Failure.Bucket
 Value: 0x10D_5_dm9usb!unknown_function

 Key : Failure.Hash
 Value: {f3b5c834-5454-4d7e-7854-898a5070d2c3}

 Key : WER.OS.Branch
 Value: ni_release

 Key : WER.OS.Version
 Value: 10.0.22621.1

BUGCHECK_CODE: 10d

BUGCHECK_P1: 5

BUGCHECK_P2: 0

BUGCHECK_P3: 1023

BUGCHECK_P4: ffffc103baad86b0

FILE_IN_CAB: 060623-11656-01.dmp

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffff958c`4fdf6aa8 fffff802`0cf56390 : 00000000`0000010d 00000000`00000005 00000000`00000000 00000000`00001023 : nt!KeBugCheckEx
ffff958c`4fdf6ab0 fffff802`0cf253f6 : 00000000`00040246 fffff802`0b03237b ffffc103`c12a1158 ffffc103`c2585160 : Wdf01000!FxVerifierBugCheckWorker+0x24 [minkernel\wdf\framework\shared\object\fxverifierbugcheck.cpp @ 87]
ffff958c`4fdf6af0 fffff802`0cf11466 : ffff9681`3d92bd38 00000001`00000001 fffff802`0dcd3048 ffffc103`c12a01a0 : Wdf01000!FxObjectHandleGetPtr+0xf1c6 [minkernel\wdf\framework\shared\inc\private\common\fxhandle.h @ 328]
ffff958c`4fdf6b30 fffff802`081b67b8 : 00000000`00000000 ffffc103`c2585160 00000000`00000000 fffff802`0dc04500 : Wdf01000!imp_WdfWaitLockAcquire+0x26 [minkernel\wdf\framework\shared\support\fxwaitlockapi.cpp @ 134]
ffff958c`4fdf6b60 00000000`00000000 : ffffc103`c2585160 00000000`00000000 fffff802`0dc04500 ffffc103`c2585000 : dm9usb+0x67b8

SYMBOL_NAME: dm9usb+67b8

MODULE_NAME: dm9usb

IMAGE_NAME: dm9usb.sys

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 67b8

FAILURE_BUCKET_ID: 0x10D_5_dm9usb!unknown_function

OS_VERSION: 10.0.22621.1

BUILDLAB_STR: ni_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {f3b5c834-5454-4d7e-7854-898a5070d2c3}

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

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_CORRUPTED_EXPOOL (c5)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is
caused by drivers that have corrupted the system pool. Run the driver
verifier against any new (or suspect) drivers, and if that doesn't turn up
the culprit, then use gflags to enable special pool.
Arguments:
Arg1: ffffac0280116063, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff8037c29c08e, address which referenced memory

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

KEY_VALUES_STRING: 1

 Key : Analysis.CPU.mSec
 Value: 2546

 Key : Analysis.Elapsed.mSec
 Value: 12812

 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: 171

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

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

 Key : Bugcheck.Code.LegacyAPI
 Value: 0xc5

 Key : Failure.Bucket
 Value: 0xC5_2_vgk!unknown_function

 Key : Failure.Hash
 Value: {f440937e-e808-2f2e-10ad-7db228ddf2cc}

 Key : WER.OS.Branch
 Value: ni_release

 Key : WER.OS.Version
 Value: 10.0.22621.1

BUGCHECK_CODE: c5

BUGCHECK_P1: ffffac0280116063

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff8037c29c08e

FILE_IN_CAB: 041223-16078-01.dmp

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: VALORANT-Win64-Shipping.exe

DPC_STACK_BASE: FFFFE58E8E037FB0

TRAP_FRAME: ffffe58e8e036bb0 -- (.trap 0xffffe58e8e036bb0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffac0221600000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8037c29c08e rsp=ffffe58e8e036d40 rbp=0000000000000000
 r8=0000000000000001 r9=ffffffffffffffff r10=0000fffff803a7f0
r11=ffffe58e8e036dc8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
nt!ExFreePoolWithTag+0x7e:
fffff803`7c29c08e f647f308 test byte ptr [rdi-0Dh],8 ds:ffffffff`fffffff3=??
Resetting default scope

STACK_TEXT:
ffffe58e`8e036a68 fffff803`7bc3e8a9 : 00000000`0000000a ffffac02`80116063 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffffe58e`8e036a70 fffff803`7bc39f34 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffffe58e`8e036bb0 fffff803`7c29c08e : 01000000`00100000 ffffe78f`00000000 00000000`05000000 00000000`00000030 : nt!KiPageFault+0x474
ffffe58e`8e036d40 fffff803`8e7b3c18 : fffff803`00000000 00000000`00000001 00000000`00000000 00000000`00000000 : nt!ExFreePoolWithTag+0x7e
ffffe58e`8e036dd0 fffff803`00000000 : 00000000`00000001 00000000`00000000 00000000`00000000 ffffe78f`00000000 : vgk+0x53c18
ffffe58e`8e036dd8 00000000`00000001 : 00000000`00000000 00000000`00000000 ffffe78f`00000000 ffffe78f`00000000 : 0xfffff803`00000000
ffffe58e`8e036de0 00000000`00000000 : 00000000`00000000 ffffe78f`00000000 ffffe78f`00000000 fffff803`7ba67b90 : 0x1

SYMBOL_NAME: vgk+53c18

MODULE_NAME: vgk

IMAGE_NAME: vgk.sys

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 53c18

FAILURE_BUCKET_ID: 0xC5_2_vgk!unknown_function

OS_VERSION: 10.0.22621.1

BUILDLAB_STR: ni_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {f440937e-e808-2f2e-10ad-7db228ddf2cc}

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

Genişletmek için tıkla...

EgeN7 dedi:

Evet o cihazla alakalı ciddi bir sıkıntı var. Ya kendisinde ya da sürücüsünde.

Güncel bir sürücüsü varsa indirin. En günceli sizin kullandığınız da olabilir fark etmez.

- Aygıt yöneticisini açıp bu adaptör cihazınızı bulun.
- Sağ tıklayıp "Cihazı kaldır" deyin.
- Adaptörü sistemden sökün.
- İnterneti kesin. Açılmasın.
- PC'yi yeniden başlatın.
- Adaptörü sisteme takın.
- İndirdiğiniz sürücüyü kurun.
- Şimdi interneti açabilirsiniz

Genişletmek için tıkla...

EgeN7 dedi:

Windows 10 olanı da deneyebilirsiniz.

Tekrar mavi ekran alırsanız yeni dökümü paylaşırsınız.

Genişletmek için tıkla...

EgeN7 dedi:

Windows 10 olanı da deneyebilirsiniz.

Tekrar mavi ekran alırsanız yeni dökümü paylaşırsınız.

Genişletmek için tıkla...

EgeN7 dedi:

Bazı sürücülerde Windows 10/11 fark etmiyor. Ama bazılarında da ediyor. Sizde de öyle olmuş.

O zaman herhangi bir sürücü kurmanıza gerek yok, taktığınız anda Windows kurmuş zaten anladığım kadarıyla. Yapmaya çalıştığımız işlem bir nevi buydu, sürücülerin bozulma ihtimaline karşı kaldırılıp tekrar yüklenmesi.

Aklımdaki soru adaptörün Win 11 ile uyumlu olup olmadığı.
Ama şu an bir problem yoksa ve mavi ekran almıyorsanız çözülmüştür.

Alırsanız tekrar paylaşırsınız.

Genişletmek için tıkla...