Çözüldü DPC_WATCHDOG_VIOLATION hatası nasıl çözülür?

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

Erencikefe

Kilopat
Katılım
1 Haziran 2018
Mesajlar
130
Daha fazla  
Cinsiyet
Erkek
Meslek
Veteriner
Minidump Rapor Linki
https://drive.google.com/drive/folders/1XaVNp0Km2eb7u9rlRSZXY6FaU6jXYoqX?usp=sharing
RAM
8 GB 1333 MHZ Kingston
SSD veya HDD modeli
3 Sata, 1 SSD, 1 HDD
Ekran kartı
GTX 560 Ti
Anakart
Esonic G43
İşlemci
Intel Core 2 Quad Q9400
Merhabalar, elimde yaklaşık 6 yıllık eski bir bilgisayar var. Yakın zamanda içine yeni bir PSU taktım (400 wattan 600'e çıktı), ekran kartını da ATI Radeon HD 5450'den GTX 560 Ti'ya yükselttim. Tek sorun ekran kartı çok büyüktü, ve iki SATA portunu kapatıyordu. Çözüm olarak PCI to SATA adaptör satın aldım, PCI portuna kartı taktım ve SATA bağlantı kablolarını taktım. PCI üzerinden bağladığım HDD'ler RAID olarak gözüküyor, belirtmemde fayda var yanında küçük bir CD ile geldi kart. Driverını vs kurdum onun içinden. 6 yıl sonra ilk defa hem de üst üste 3 kere mavi ekran hatası aldım. Belki de karttan belki de driverdan hiç bilemiyorum. Minidump dosyalarının linkini aşağıya koydum. Bana yardım edebilir misiniz?
 
Son düzenleme:
Çözüm
Merhaba.

Kullandığınız Silicon Image SiL3114 çipli SATA kontrolcüsü hataya sebep oluyor. (PCI to SATA.)

Kod:
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: fffff8065f726340, 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 Si3114r5.sys
*** 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                                   ***
***                                                                   ***
*************************************************************************

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1140

    Key  : Analysis.Elapsed.mSec
    Value: 3716

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

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

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

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.29482.1003

    Key  : Analysis.Version.Description
    Value: 10.2509.29.03 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2509.29.3

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x133

    Key  : Bugcheck.Code.TargetModel
    Value: 0x133

    Key  : Failure.Bucket
    Value: 0x133_VRF_DPC_Si3114r5!unknown_function

    Key  : Failure.Hash
    Value: {96caa590-5c59-9ecb-0150-597398d14c22}

    Key  : Stack.Pointer
    Value: ISR

    Key  : WER.OS.Branch
    Value: ni_release

    Key  : WER.OS.Version
    Value: 10.0.22621.1

    Key  : WER.System.BIOSRevision
    Value: 8.15.0.0


BUGCHECK_CODE:  133

BUGCHECK_P1: 0

BUGCHECK_P2: 501

BUGCHECK_P3: 500

BUGCHECK_P4: fffff8065f726340

FILE_IN_CAB:  010626-16046-01.dmp

FAULTING_THREAD:  ffffc609181ed140

DPC_TIMEOUT_TYPE:  SINGLE_DPC_TIMEOUT_EXCEEDED

TRAP_FRAME:  fffff8065e4ae5d0 -- (.trap 0xfffff8065e4ae5d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000cb709730600 rbx=0000000000000000 rcx=fffff7ecc0001158
rdx=00000cb700000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8065ef28d81 rsp=fffff8065e4ae768 rbp=0000000000000001
 r8=0000000000000001  r9=fffff8065e4aeb30 r10=fffff8065ef28d60
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
nt!HalpTscQueryCounter+0x21:
fffff806`5ef28d81 c3              ret
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1 (!blackboxwinlogon)


CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  steamwebhelper.exe

STACK_TEXT:
fffff806`5e4b59e8 fffff806`5ecd0eb5     : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
fffff806`5e4b59f0 fffff806`5ecd0581     : 00000cb7`09743f28 00000000`000516fd 00000000`000516fc 00000000`00000000 : nt!KeAccumulateTicks+0x3d5
fffff806`5e4b5a50 fffff806`5eccccaf     : 00000000`00000004 00000000`00001388 00000000`00051600 00000000`000308a4 : nt!KiUpdateRunTime+0xd1
fffff806`5e4b5c00 fffff806`5eccd898     : 00000000`00000000 ffffa101`12e7f900 fffff806`5cfa2180 00000000`00000000 : nt!KiUpdateTime+0x63f
fffff806`5e4b5ea0 fffff806`5eccd15a     : fffff806`5f669378 ffffa101`12e7f970 ffffa101`12e7f970 00000000`00000008 : nt!KeClockInterruptNotify+0x228
fffff806`5e4b5f40 fffff806`5ed2d80c     : 0000000c`22a72947 fffff806`5f716930 fffff806`5f7169e0 00000000`000411b6 : nt!HalpTimerClockInterrupt+0x10a
fffff806`5e4b5f70 fffff806`5ee2943a     : fffff806`5e4ae650 fffff806`5f716930 00000cb7`097305b0 00000caa`bfdebdc0 : nt!KiCallInterruptServiceRoutine+0x9c
fffff806`5e4b5fb0 fffff806`5ee29d07     : 00000000`000002bd fffff806`5ee29d14 00000000`00000000 ffffc609`0ae02000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff806`5e4ae5d0 fffff806`5ef28d81     : fffff806`5eccd48c 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff806`5e4ae768 fffff806`5eccd48c     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalpTscQueryCounter+0x21
fffff806`5e4ae770 fffff806`5eccc027     : 00000000`00000010 00000000`0001b4ca ffffa101`126b5e80 00000000`00000018 : nt!HalpTimerStallExecutionProcessor+0x10c
fffff806`5e4ae810 fffff806`607fb77b     : ffffffff`ffffffd1 fffff806`6079a184 00000000`00000010 00000000`00000202 : nt!KeStallExecutionProcessor+0x27
fffff806`5e4ae840 fffff806`6079a192     : fffff801`8b85307b ffffc609`15ceb000 ffffc609`15ceb000 fffff801`8b9ed0a9 : SCSIPORT!ScsiPortStallExecution+0xb
fffff806`5e4ae870 fffff801`8b85307b     : ffffc609`15ceb000 ffffc609`15ceb000 fffff801`8b9ed0a9 00000000`00000000 : Si3114r5+0xa192
fffff806`5e4ae878 ffffc609`15ceb000     : ffffc609`15ceb000 fffff801`8b9ed0a9 00000000`00000000 fffff806`60793ad3 : nvlddmkm+0x8307b
fffff806`5e4ae880 ffffc609`15ceb000     : fffff801`8b9ed0a9 00000000`00000000 fffff806`60793ad3 ffffc609`0ffd01f0 : 0xffffc609`15ceb000
fffff806`5e4ae888 fffff801`8b9ed0a9     : 00000000`00000000 fffff806`60793ad3 ffffc609`0ffd01f0 00000000`00000002 : 0xffffc609`15ceb000
fffff806`5e4ae890 00000000`00000000     : fffff806`60793ad3 ffffc609`0ffd01f0 00000000`00000002 ffffc609`0ffe3910 : nvlddmkm+0x21d0a9


SYMBOL_NAME:  Si3114r5+a192

MODULE_NAME: Si3114r5

IMAGE_NAME:  Si3114r5.sys

STACK_COMMAND: .process /r /p 0xffffc60923b92080; .thread 0xffffc609181ed140 ; kb

BUCKET_ID_FUNC_OFFSET:  a192

FAILURE_BUCKET_ID:  0x133_VRF_DPC_Si3114r5!unknown_function

OS_VERSION:  10.0.22621.1

BUILDLAB_STR:  ni_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {96caa590-5c59-9ecb-0150-597398d14c22}

Followup:     MachineOwner

NVIDIA ekran kartı bileşeni de hata dosyasında yer alıyor ancak ana unsur, SATA kontrolcüsü.

Eğer Donanım Kimliği paylaşabilirseniz varsa daha güncel bir sürücü bulup yüklemeyi deneyebiliriz.
Merhaba.

Kullandığınız Silicon Image SiL3114 çipli SATA kontrolcüsü hataya sebep oluyor. (PCI to SATA.)

Kod:
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: fffff8065f726340, 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 Si3114r5.sys
*** 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                                   ***
***                                                                   ***
*************************************************************************

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1140

    Key  : Analysis.Elapsed.mSec
    Value: 3716

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

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

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

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.29482.1003

    Key  : Analysis.Version.Description
    Value: 10.2509.29.03 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2509.29.3

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x133

    Key  : Bugcheck.Code.TargetModel
    Value: 0x133

    Key  : Failure.Bucket
    Value: 0x133_VRF_DPC_Si3114r5!unknown_function

    Key  : Failure.Hash
    Value: {96caa590-5c59-9ecb-0150-597398d14c22}

    Key  : Stack.Pointer
    Value: ISR

    Key  : WER.OS.Branch
    Value: ni_release

    Key  : WER.OS.Version
    Value: 10.0.22621.1

    Key  : WER.System.BIOSRevision
    Value: 8.15.0.0


BUGCHECK_CODE:  133

BUGCHECK_P1: 0

BUGCHECK_P2: 501

BUGCHECK_P3: 500

BUGCHECK_P4: fffff8065f726340

FILE_IN_CAB:  010626-16046-01.dmp

FAULTING_THREAD:  ffffc609181ed140

DPC_TIMEOUT_TYPE:  SINGLE_DPC_TIMEOUT_EXCEEDED

TRAP_FRAME:  fffff8065e4ae5d0 -- (.trap 0xfffff8065e4ae5d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000cb709730600 rbx=0000000000000000 rcx=fffff7ecc0001158
rdx=00000cb700000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8065ef28d81 rsp=fffff8065e4ae768 rbp=0000000000000001
 r8=0000000000000001  r9=fffff8065e4aeb30 r10=fffff8065ef28d60
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
nt!HalpTscQueryCounter+0x21:
fffff806`5ef28d81 c3              ret
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1 (!blackboxwinlogon)


CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  steamwebhelper.exe

STACK_TEXT:
fffff806`5e4b59e8 fffff806`5ecd0eb5     : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
fffff806`5e4b59f0 fffff806`5ecd0581     : 00000cb7`09743f28 00000000`000516fd 00000000`000516fc 00000000`00000000 : nt!KeAccumulateTicks+0x3d5
fffff806`5e4b5a50 fffff806`5eccccaf     : 00000000`00000004 00000000`00001388 00000000`00051600 00000000`000308a4 : nt!KiUpdateRunTime+0xd1
fffff806`5e4b5c00 fffff806`5eccd898     : 00000000`00000000 ffffa101`12e7f900 fffff806`5cfa2180 00000000`00000000 : nt!KiUpdateTime+0x63f
fffff806`5e4b5ea0 fffff806`5eccd15a     : fffff806`5f669378 ffffa101`12e7f970 ffffa101`12e7f970 00000000`00000008 : nt!KeClockInterruptNotify+0x228
fffff806`5e4b5f40 fffff806`5ed2d80c     : 0000000c`22a72947 fffff806`5f716930 fffff806`5f7169e0 00000000`000411b6 : nt!HalpTimerClockInterrupt+0x10a
fffff806`5e4b5f70 fffff806`5ee2943a     : fffff806`5e4ae650 fffff806`5f716930 00000cb7`097305b0 00000caa`bfdebdc0 : nt!KiCallInterruptServiceRoutine+0x9c
fffff806`5e4b5fb0 fffff806`5ee29d07     : 00000000`000002bd fffff806`5ee29d14 00000000`00000000 ffffc609`0ae02000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff806`5e4ae5d0 fffff806`5ef28d81     : fffff806`5eccd48c 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff806`5e4ae768 fffff806`5eccd48c     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalpTscQueryCounter+0x21
fffff806`5e4ae770 fffff806`5eccc027     : 00000000`00000010 00000000`0001b4ca ffffa101`126b5e80 00000000`00000018 : nt!HalpTimerStallExecutionProcessor+0x10c
fffff806`5e4ae810 fffff806`607fb77b     : ffffffff`ffffffd1 fffff806`6079a184 00000000`00000010 00000000`00000202 : nt!KeStallExecutionProcessor+0x27
fffff806`5e4ae840 fffff806`6079a192     : fffff801`8b85307b ffffc609`15ceb000 ffffc609`15ceb000 fffff801`8b9ed0a9 : SCSIPORT!ScsiPortStallExecution+0xb
fffff806`5e4ae870 fffff801`8b85307b     : ffffc609`15ceb000 ffffc609`15ceb000 fffff801`8b9ed0a9 00000000`00000000 : Si3114r5+0xa192
fffff806`5e4ae878 ffffc609`15ceb000     : ffffc609`15ceb000 fffff801`8b9ed0a9 00000000`00000000 fffff806`60793ad3 : nvlddmkm+0x8307b
fffff806`5e4ae880 ffffc609`15ceb000     : fffff801`8b9ed0a9 00000000`00000000 fffff806`60793ad3 ffffc609`0ffd01f0 : 0xffffc609`15ceb000
fffff806`5e4ae888 fffff801`8b9ed0a9     : 00000000`00000000 fffff806`60793ad3 ffffc609`0ffd01f0 00000000`00000002 : 0xffffc609`15ceb000
fffff806`5e4ae890 00000000`00000000     : fffff806`60793ad3 ffffc609`0ffd01f0 00000000`00000002 ffffc609`0ffe3910 : nvlddmkm+0x21d0a9


SYMBOL_NAME:  Si3114r5+a192

MODULE_NAME: Si3114r5

IMAGE_NAME:  Si3114r5.sys

STACK_COMMAND: .process /r /p 0xffffc60923b92080; .thread 0xffffc609181ed140 ; kb

BUCKET_ID_FUNC_OFFSET:  a192

FAILURE_BUCKET_ID:  0x133_VRF_DPC_Si3114r5!unknown_function

OS_VERSION:  10.0.22621.1

BUILDLAB_STR:  ni_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {96caa590-5c59-9ecb-0150-597398d14c22}

Followup:     MachineOwner

NVIDIA ekran kartı bileşeni de hata dosyasında yer alıyor ancak ana unsur, SATA kontrolcüsü.

Eğer Donanım Kimliği paylaşabilirseniz varsa daha güncel bir sürücü bulup yüklemeyi deneyebiliriz.
 
Son düzenleme:
Çözüm
Bir tane de Silicon Image's Pseudo Processor Device var sistem aygıtlarında. Bunlar da onun kimlikleri:
SCSI\ProcessorSI______Pseudo_Device___0000
SCSI\ProcessorSI______Pseudo_Device___
SCSI\ProcessorSI______
SCSI\SI______Pseudo_Device___0
SI______Pseudo_Device___0
 
Sürücü sürümünü yine de kontrol edelim. Eğer aynı sürüm ise indirmenize gerek yok.

@Erencikefe merhaba. Bir gelişme var mı?

Hocam şu anlık bir sorun yok, sürücüden kasıt ben sürücüyü değil de yanında gelen RAID Controller vs gibi uygulamaları sildim. Asıl ondan sonra sorun yok oldu. İlginiz ve yardımınız için teşekkürler.

Sürücü sürümünü yine de kontrol edelim. Eğer aynı sürüm ise indirmenize gerek yok.

@Erencikefe merhaba. Bir gelişme var mı?
Hocam tekrardan selamlar, sorun çözüldü zannediyordum ama bilgisayarım bugün de mavi ekran verince direk driveri kaldırdım. Fakat böyle yapınca da Raid Denetleyicisi olarak gözüküyor aygıt yöneticisinde. 2 harddiskim yine PC'de gözükmüyor, ne yapabilirim?

Sürücü sürümünü yine de kontrol edelim. Eğer aynı sürüm ise indirmenize gerek yok.

@Erencikefe merhaba. Bir gelişme var mı?
Hocam tekrardan selamlar, sorun çözüldü zannediyordum ama bilgisayarım bugün de mavi ekran verince direk driveri kaldırdım. Fakat böyle yapınca da Raid Denetleyicisi olarak gözüküyor aygıt yöneticisinde. 2 harddiskim yine PC'de gözükmüyor, ne yapabilirim?
 
Son düzenleme:

Bu konuyu görüntüleyen kullanıcılar

Technopat Haberler

Yeni konular

Geri
Yukarı