Çözüldü DPC_WATCHDOG_VIOLATION 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

Hopeツ︎

Decapat
Katılım
22 Ağustos 2020
Mesajlar
253
Yer
Turkey
Daha fazla  
Sistem Özellikleri
HP Gaming Pavilion - 15-dk0011nt
HP 85FB 42.46 & Insyde F.60
Windows 11 Home 22H2 & Fedora 37 Workstation
Intel(R) Core(TM) i7-9750H CPU @2.60+4.50GHz
SAMSUNG 512 GB MZVLB512HBJQ-000H1
16 GB DDR4 Micron 3200MHz
NVIDIA GeForce GTX 1660 Ti with Max-Q Design
NVIDIA High Definition Audio B&o Bang Olufsen
Razer Kraken Tournament Edition Black
Razer Deathadder Elite RGB
Razer Blackwidow Elite RGB
Razer Goliathus Control Fissure Edition Extended
Cinsiyet
Erkek
Meslek
Grafiker
Merhaba, daha önce bu hata üzerine çözüm içeren kısa bir makale de yazmıştım forumda ama belli ki tam çözememişim. Bilgisayarımı sıfırlayana kadar bu hatayı uzun süredir görmüyordum ve uygulamalarımı, oyunlarımı rahatça açabiliyordum. Hatanın kaynağının, WinDbg ile NVIDIA'nın nvlddmkm.sys sürücü dosyasından kaynaklandığını bir şekilde ortaya çıkarabildim. Fakat, çözümü hakkında bir fikrim yok. Şu an güncel olarak söyleyebileceğim DDU ile güvenli modda silme işlemi gerçekleştirmem ve Windows Update'nin otomatik olarak sürücüyü kurması ve şu an halihazırda kullanıyor olmam. Bu işlemleri yaptıktan sonra yarım saat kadar belirli oyunları ve yazılımları açıp Intel kartıma değil de NVIDIA'ya kullandırtmaya çalıştım tekrar olacak mı diye olmadı. Ama bu içimi rahatlatmıyor yani olmadığı olmayacağı anlamına gelmiyor tabii ki. Bu yüzden forum içerisinde benden bu konuda daha bilgili arkadaşların konuyu inceleyip daha iyi yorumlamasını isterim. Sistemim HP Gaming Pavilion 15-dk0011nt . Minidump içeriğini de alt satırda paylaşıyor olacağım;

Minidump
@Enes3078

Sistemim detaylı olarak;
HP Gaming Pavilion 15-dk0011nt - Windows 10 Home 64 bit - Intel i7-9750H 2.60GHz
512 GB Samsung MZVLB512HBJQ-000H1 - 16 GB Micron 3200MHz - 6 GB GDDR6 NVIDIA GeForce GTX 1660 Ti Max-Q
Razer Kraken Tournament Edition - Razer Deathadder Elite - Razer Blackwidow Elite - Razer Goliathus Control
 
Son düzenleme:
Çözüm
Evet, dediğinizde haklısınız. Sorunun kaynağı NVIDIA ekran kartı sürücüsü imiş ve tavsiye edeceğimi siz zaten uygulamışsınız. Artık 2-3 gün boyunca kontrol edin ki sorunun çözülmüş olması gerek. Sorun çözülürse ve belirtirseniz sevinirim. İyi günler, kolay gelsin.

[CODE title="Dökümler"]*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
component can usually be identified with a stack trace.
Arg2: 0000000000000501, The DPC time count (in ticks).
Arg3: 0000000000000500, The DPC time allotment (in ticks).
Arg4: fffff80347cfa320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
additional information regarding this single DPC timeout

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

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*************************************************************************
*** ***
*** ***
*** 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: TickPeriods ***
*** ***
*************************************************************************
*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 11078

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 130005

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

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

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

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z

Key : WER.OS.Version
Value: 10.0.19041.1


BUGCHECK_CODE: 133

BUGCHECK_P1: 0

BUGCHECK_P2: 501

BUGCHECK_P3: 500

BUGCHECK_P4: fffff80347cfa320

DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED

TRAP_FRAME: fffff8034c00e020 -- (.trap 0xfffff8034c00e020)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000020
rdx=fffff8034c00e168 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80362a29217 rsp=fffff8034c00e1b0 rbp=ffff958790da8000
r8=0000000000000001 r9=0000000000000020 r10=ffff9587889a5050
r11=fffff8034c00e080 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
nvlddmkm+0x209217:
fffff803`62a29217 ebfe jmp nvlddmkm+0x209217 (fffff803`62a29217)
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
fffff803`4c01de18 fffff803`4741f4fa : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
fffff803`4c01de20 fffff803`47216ac3 : 000000db`cef2ab62 fffff803`427ea180 00000000`00000000 fffff803`427ea180 : nt!KeAccumulateTicks+0x2061da
fffff803`4c01de80 fffff803`472165aa : fffff803`47cf3780 fffff803`4c00e0a0 00000000`00000000 fffff803`4c01df20 : nt!KeClockInterruptNotify+0x453
fffff803`4c01df30 fffff803`472de045 : fffff803`47cf3780 fffff803`473f8890 ffffe200`a56c28c8 ffffe200`a56c28c0 : nt!HalpTimerClockIpiRoutine+0x1a
fffff803`4c01df60 fffff803`473f8c7a : fffff803`4c00e0a0 fffff803`47cf3780 00000000`00000000 ffff9587`90b21000 : nt!KiCallInterruptServiceRoutine+0xa5
fffff803`4c01dfb0 fffff803`473f91e7 : ffff9587`90da90a8 fffff803`62989a48 00000000`00000020 ffff9587`887d0760 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff803`4c00e020 fffff803`62a29217 : ffff9587`90ce0010 ffff9587`02810000 ffff9587`88918ca0 ffff9587`74000020 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff803`4c00e1b0 ffff9587`90ce0010 : ffff9587`02810000 ffff9587`88918ca0 ffff9587`74000020 00000000`00000010 : nvlddmkm+0x209217
fffff803`4c00e1b8 ffff9587`02810000 : ffff9587`88918ca0 ffff9587`74000020 00000000`00000010 fffff803`62a29a66 : 0xffff9587`90ce0010
fffff803`4c00e1c0 ffff9587`88918ca0 : ffff9587`74000020 00000000`00000010 fffff803`62a29a66 00000000`00001010 : 0xffff9587`02810000
fffff803`4c00e1c8 ffff9587`74000020 : 00000000`00000010 fffff803`62a29a66 00000000`00001010 ffff9587`90b21000 : 0xffff9587`88918ca0
fffff803`4c00e1d0 00000000`00000010 : fffff803`62a29a66 00000000`00001010 ffff9587`90b21000 ffff9587`80000000 : 0xffff9587`74000020
fffff803`4c00e1d8 fffff803`62a29a66 : 00000000`00001010 ffff9587`90b21000 ffff9587`80000000 ffff9587`90daab38 : 0x10
fffff803`4c00e1e0 00000000`00001010 : ffff9587`90b21000 ffff9587`80000000 ffff9587`90daab38 00000000`00000000 : nvlddmkm+0x209a66
fffff803`4c00e1e8 ffff9587`90b21000 : ffff9587`80000000 ffff9587`90daab38 00000000`00000000 fffff803`62b8f0d8 : 0x1010
fffff803`4c00e1f0 ffff9587`80000000 : ffff9587`90daab38 00000000`00000000 fffff803`62b8f0d8 00000000`80000000 : 0xffff9587`90b21000
fffff803`4c00e1f8 ffff9587`90daab38 : 00000000`00000000 fffff803`62b8f0d8 00000000`80000000 ffff9587`90b21000 : 0xffff9587`80000000
fffff803`4c00e200 00000000`00000000 : fffff803`62b8f0d8 00000000`80000000 ffff9587`90b21000 00000000`00000003 : 0xffff9587`90daab38


SYMBOL_NAME: nvlddmkm+209217

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 209217

FAILURE_BUCKET_ID: 0x133_DPC_nvlddmkm!unknown_function

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {15c3af0e-5564-7a80-2e26-65b5115ecc4d}

Followup: MachineOwner
---------[/CODE]
Evet, dediğinizde haklısınız. Sorunun kaynağı NVIDIA ekran kartı sürücüsü imiş ve tavsiye edeceğimi siz zaten uygulamışsınız. Artık 2-3 gün boyunca kontrol edin ki sorunun çözülmüş olması gerek. Sorun çözülürse ve belirtirseniz sevinirim. İyi günler, kolay gelsin.

[CODE title="Dökümler"]*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
component can usually be identified with a stack trace.
Arg2: 0000000000000501, The DPC time count (in ticks).
Arg3: 0000000000000500, The DPC time allotment (in ticks).
Arg4: fffff80347cfa320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
additional information regarding this single DPC timeout

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

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*************************************************************************
*** ***
*** ***
*** 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: TickPeriods ***
*** ***
*************************************************************************
*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 11078

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 130005

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

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

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

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z

Key : WER.OS.Version
Value: 10.0.19041.1


BUGCHECK_CODE: 133

BUGCHECK_P1: 0

BUGCHECK_P2: 501

BUGCHECK_P3: 500

BUGCHECK_P4: fffff80347cfa320

DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED

TRAP_FRAME: fffff8034c00e020 -- (.trap 0xfffff8034c00e020)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000020
rdx=fffff8034c00e168 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80362a29217 rsp=fffff8034c00e1b0 rbp=ffff958790da8000
r8=0000000000000001 r9=0000000000000020 r10=ffff9587889a5050
r11=fffff8034c00e080 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
nvlddmkm+0x209217:
fffff803`62a29217 ebfe jmp nvlddmkm+0x209217 (fffff803`62a29217)
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
fffff803`4c01de18 fffff803`4741f4fa : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
fffff803`4c01de20 fffff803`47216ac3 : 000000db`cef2ab62 fffff803`427ea180 00000000`00000000 fffff803`427ea180 : nt!KeAccumulateTicks+0x2061da
fffff803`4c01de80 fffff803`472165aa : fffff803`47cf3780 fffff803`4c00e0a0 00000000`00000000 fffff803`4c01df20 : nt!KeClockInterruptNotify+0x453
fffff803`4c01df30 fffff803`472de045 : fffff803`47cf3780 fffff803`473f8890 ffffe200`a56c28c8 ffffe200`a56c28c0 : nt!HalpTimerClockIpiRoutine+0x1a
fffff803`4c01df60 fffff803`473f8c7a : fffff803`4c00e0a0 fffff803`47cf3780 00000000`00000000 ffff9587`90b21000 : nt!KiCallInterruptServiceRoutine+0xa5
fffff803`4c01dfb0 fffff803`473f91e7 : ffff9587`90da90a8 fffff803`62989a48 00000000`00000020 ffff9587`887d0760 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff803`4c00e020 fffff803`62a29217 : ffff9587`90ce0010 ffff9587`02810000 ffff9587`88918ca0 ffff9587`74000020 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff803`4c00e1b0 ffff9587`90ce0010 : ffff9587`02810000 ffff9587`88918ca0 ffff9587`74000020 00000000`00000010 : nvlddmkm+0x209217
fffff803`4c00e1b8 ffff9587`02810000 : ffff9587`88918ca0 ffff9587`74000020 00000000`00000010 fffff803`62a29a66 : 0xffff9587`90ce0010
fffff803`4c00e1c0 ffff9587`88918ca0 : ffff9587`74000020 00000000`00000010 fffff803`62a29a66 00000000`00001010 : 0xffff9587`02810000
fffff803`4c00e1c8 ffff9587`74000020 : 00000000`00000010 fffff803`62a29a66 00000000`00001010 ffff9587`90b21000 : 0xffff9587`88918ca0
fffff803`4c00e1d0 00000000`00000010 : fffff803`62a29a66 00000000`00001010 ffff9587`90b21000 ffff9587`80000000 : 0xffff9587`74000020
fffff803`4c00e1d8 fffff803`62a29a66 : 00000000`00001010 ffff9587`90b21000 ffff9587`80000000 ffff9587`90daab38 : 0x10
fffff803`4c00e1e0 00000000`00001010 : ffff9587`90b21000 ffff9587`80000000 ffff9587`90daab38 00000000`00000000 : nvlddmkm+0x209a66
fffff803`4c00e1e8 ffff9587`90b21000 : ffff9587`80000000 ffff9587`90daab38 00000000`00000000 fffff803`62b8f0d8 : 0x1010
fffff803`4c00e1f0 ffff9587`80000000 : ffff9587`90daab38 00000000`00000000 fffff803`62b8f0d8 00000000`80000000 : 0xffff9587`90b21000
fffff803`4c00e1f8 ffff9587`90daab38 : 00000000`00000000 fffff803`62b8f0d8 00000000`80000000 ffff9587`90b21000 : 0xffff9587`80000000
fffff803`4c00e200 00000000`00000000 : fffff803`62b8f0d8 00000000`80000000 ffff9587`90b21000 00000000`00000003 : 0xffff9587`90daab38


SYMBOL_NAME: nvlddmkm+209217

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 209217

FAILURE_BUCKET_ID: 0x133_DPC_nvlddmkm!unknown_function

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {15c3af0e-5564-7a80-2e26-65b5115ecc4d}

Followup: MachineOwner
---------[/CODE]
 
Çözüm
Aynı hatayı az önce oyundayken aldım. Ne yapacağım?
 
Son düzenleyen: Moderatör:

Yeni konular

Geri
Yukarı