Board logo

標題: [Windows 10] win 7->10 經常出現dpc_watchdog_violation [打印本頁]

作者: kbpaul    時間: 昨天 15:21     標題: win 7->10 經常出現dpc_watchdog_violation

本帖最後由 kbpaul 於 2026-9-3 15:27 編輯

行winDbg睇memery dump file,分析如下

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: fffff80704cfb320, 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 echo1394.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: 3281

    Key  : Analysis.Elapsed.mSec
    Value: 6457

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

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

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

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.29617.1000

    Key  : Analysis.Version.Description
    Value: 10.2604.29.1 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2604.29.1

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x133

    Key  : Bugcheck.Code.TargetModel
    Value: 0x133

    Key  : Failure.Bucket
    Value: 0x133_DPC_ks!CKsQueue::UnlockStreamPointer

    Key  : Failure.Hash
    Value: {53605990-ed08-1cb4-4fe1-2560485dee2d}

    Key  : Stack.Pointer
    Value: ISR

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Version
    Value: 10.0.19041.1

    Key  : WER.System.BIOSRevision
    Value: 3.96.0.0


BUGCHECK_CODE:  133

BUGCHECK_P1: 0

BUGCHECK_P2: 501

BUGCHECK_P3: 500

BUGCHECK_P4: fffff80704cfb320

FILE_IN_CAB:  090126-21562-01.dmp

FAULTING_THREAD:  fffff80704d27a00

DPC_TIMEOUT_TYPE:  SINGLE_DPC_TIMEOUT_EXCEEDED

TRAP_FRAME:  fffff807088a8540 -- (.trap 0xfffff807088a8540)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000002 rbx=0000000000000000 rcx=ffff8007f26f4120
rdx=ffff8007f26f4120 rsi=0000000000000000 rdi=0000000000000000
rip=fffff807042d89fa rsp=fffff807088a86d0 rbp=ffff8007f06d0010
r8=0000000000000000  r9=0000000000000000 r10=fffff807042d89e0
r11=ffffd57daf400000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
nt!KeAcquireSpinLockRaiseToDpc+0x1a:
fffff807`042d89fa 8b05603ca200    mov     eax,dword ptr [nt!KiIrqlFlags (fffff807`04cfc660)] ds:fffff807`04cfc660=????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1 (!blackboxwinlogon) (!blackboxwinlogonnotify)


CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:  
fffff807`088b6c88 fffff807`04426b7a     : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
fffff807`088b6c90 fffff807`042275ed     : 001e8555`58f9f1ca fffff807`0049c180 00000000`00000246 00000000`00854488 : nt!KeAccumulateTicks+0x2027aa
fffff807`088b6cf0 fffff807`04227b91     : ffff8007`eb002000 00000000`004f6f09 fffff807`0049c180 00000000`00000001 : nt!KiUpdateRunTime+0x5d
fffff807`088b6d40 fffff807`042218e3     : fffff807`0049c180 00000000`00000000 fffff807`04c31980 00000000`00000000 : nt!KiUpdateTime+0x4a1
fffff807`088b6e80 fffff807`04229fe2     : fffff807`088a8540 fffff807`088a85c0 fffff807`088a8500 00000000`00000002 : nt!KeClockInterruptNotify+0x2e3
fffff807`088b6f30 fffff807`04343a65     : 0000013d`bc3ceda6 fffff807`04cf3da0 fffff807`04cf3e50 ffff6fed`7e604732 : nt!HalpTimerClockInterrupt+0xe2
fffff807`088b6f60 fffff807`043ff5fa     : fffff807`088a85c0 fffff807`04cf3da0 00000000`00000000 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
fffff807`088b6fb0 fffff807`043ffe27     : ffff8007`f5934100 fffff807`043ffe34 fffff807`043f9670 fffff807`042eed8a : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff807`088a8540 fffff807`042d89fa     : 00000000`00000000 00000000`00000000 00000000`00000000 ffffd57d`af400000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff807`088a86d0 fffff80d`3ced1614     : ffff8007`f5934170 ffff8007`f5934170 ffff8007`f26f4010 fffff80d`3cedeac0 : nt!KeAcquireSpinLockRaiseToDpc+0x1a
fffff807`088a8700 fffff80d`3ced6a23     : 00000000`00000000 00000000`00000000 00000000`00000000 fffff80d`3ced4104 : ks!CKsQueue::UnlockStreamPointer+0x164
fffff807`088a87a0 fffff80d`28fe1df9     : ffffe581`137d46f0 00000000`00000000 00000000`00000008 ffff8007`d5efb000 : ks!KsStreamPointerAdvanceOffsetsAndUnlock+0xd3
fffff807`088a87f0 ffffe581`137d46f0     : 00000000`00000000 00000000`00000008 ffff8007`d5efb000 ffff8007`d5579f70 : echo1394+0x1df9
fffff807`088a87f8 00000000`00000000     : 00000000`00000008 ffff8007`d5efb000 ffff8007`d5579f70 00000000`00000000 : 0xffffe581`137d46f0


SYMBOL_NAME:  ks!CKsQueue::UnlockStreamPointer+164

MODULE_NAME: ks

IMAGE_NAME:  ks.sys

IMAGE_VERSION:  10.0.19041.6389

STACK_COMMAND: .process /r /p 0xfffff80704d24a00; .thread /r /p 0xfffff80704d27a00 ; kb

BUCKET_ID_FUNC_OFFSET:  164

FAILURE_BUCKET_ID:  0x133_DPC_ks!CKsQueue::UnlockStreamPointer

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {53605990-ed08-1cb4-4fe1-2560485dee2d}

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

有無師兄知係什么原因

參考:echo1394.sys係echo audiofire4(firewire) audio interface驅動程式
作者: cyberyeah    時間: 昨天 18:16

影張相比AI問喇

via HKEPC IRF 5.1.14 - Android(5.1.2)





歡迎光臨 電腦領域 HKEPC Hardware (https://www.hkepc.com/forum/) Powered by Discuz! 7.2