Share via

DPC_WATCHDOG_VIOLATION BlueScreen Problem

Anonymous
2022-11-21T08:48:00+00:00

Recently, I meet this problem for three times, and every time, the errors are completely same.

I try to analysis minidump using WinDbg Preview as following, I don't know exactly what problem caused this bluescreen problem:

(Dump file is here: https://1drv.ms/u/s!AhUFepNKgNj3jlDu9UIGkh5M6Jqm?e=lO9lf0)

For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff802`691f92d0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:fffff802`6e6a4b10=0000000000000133
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
DISPATCH_LEVEL or above.
Arg2: 0000000000001e00, The watchdog period (in ticks).
Arg3: fffff80269afb320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
additional information regarding the cumulative timeout
Arg4: 0000000000000000

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 8093

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 92852

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

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

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

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

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

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

    Key  : Bugcheck.Code.DumpHeader
    Value: 0x133

    Key  : Bugcheck.Code.Register
    Value: 0x133

    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

FILE_IN_CAB:  112122-93531-01.dmp

BUGCHECK_CODE:  133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff80269afb320

BUGCHECK_P4: 0

DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

TRAP_FRAME:  fffff8026e6a4cf0 -- (.trap 0xfffff8026e6a4cf0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff80269198700 rbx=0000000000000000 rcx=0000000000001864
rdx=0000000000001864 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80269198719 rsp=fffff8026e6a4e88 rbp=ffff99866e259bf0
 r8=fffff8026e6a4f00  r9=0000000000000001 r10=fffff80269198710
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!HalpAcpiPmRegisterReadPort+0x9:
fffff802`69198719 418800          mov     byte ptr [r8],al ds:fffff802`6e6a4f00=00
Resetting default scope

BLACKBOXACPI: 1 (!blackboxacpi)

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:  
fffff802`6e6a4b08 fffff802`6925bf02     : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff802`69afb320 : nt!KeBugCheckEx
fffff802`6e6a4b10 fffff802`690d2973     : 0004fee6`b8ef89b4 fffff802`63eb9180 00000000`00000000 fffff802`63eb9180 : nt!KeAccumulateTicks+0x186d32
fffff802`6e6a4b70 fffff802`690d245a     : fffff802`69af3880 fffff802`6e6a4d70 00000000`00000000 00000000`00000000 : nt!KeClockInterruptNotify+0x453
fffff802`6e6a4c20 fffff802`69008a45     : fffff802`69af3880 fffff802`69a48e40 00000000`00000024 fffff802`691fb26a : nt!HalpTimerClockIpiRoutine+0x1a
fffff802`6e6a4c50 fffff802`691fb26a     : fffff802`6e6a4d70 fffff802`69af3880 0004fee6`b8ee980e fffff802`6912300a : nt!KiCallInterruptServiceRoutine+0xa5
fffff802`6e6a4ca0 fffff802`691fba37     : fffff802`6917c400 00000000`00001873 00000000`00001873 fffff802`6e6a4ed8 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff802`6e6a4cf0 fffff802`69198719     : fffff802`69197ce9 00400a02`00000014 0004fee6`b8ee352e ffff9986`6dbf9800 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff802`6e6a4e88 fffff802`69197ce9     : 00400a02`00000014 0004fee6`b8ee352e ffff9986`6dbf9800 ffff9986`6dcd4040 : nt!HalpAcpiPmRegisterReadPort+0x9
fffff802`6e6a4e90 fffff802`6c4d680a     : 00000000`00000004 00000000`000007f0 00000000`00000010 ffff9986`6e259c00 : nt!HalpAcpiPmRegisterRead+0x39
fffff802`6e6a4ec0 fffff802`6c4d5d84     : 00000000`00000400 ffffbe81`d61dcdc0 00000000`0000000c ffff9986`6daee000 : ACPI!ACPIReadGpeStatusRegister+0x66
fffff802`6e6a4f00 fffff802`69008a45     : ffffbe81`d61dcdc0 ffff9986`70723c90 ffffbe81`d61dce70 fffff802`6e6a4fc0 : ACPI!ACPIInterruptServiceRoutine+0x54
fffff802`6e6a4f40 fffff802`691fafef     : fffff802`6e69d960 ffffbe81`d61dcdc0 0004fea6`5c1d0e6e fffff802`691fb26a : nt!KiCallInterruptServiceRoutine+0xa5
fffff802`6e6a4f90 fffff802`691fb2b7     : 00000000`0000000c fffff802`6912300a 00000000`00000000 fffff802`6912300a : nt!KiInterruptSubDispatch+0x11f
fffff802`6e69d8e0 fffff802`69198719     : fffff802`69197ce9 ffffffff`ffffffb0 fffff802`6c4d680e 00000000`01000010 : nt!KiInterruptDispatch+0x37
fffff802`6e69da78 fffff802`69197ce9     : ffffffff`ffffffb0 fffff802`6c4d680e 00000000`01000010 00000000`00000286 : nt!HalpAcpiPmRegisterReadPort+0x9
fffff802`6e69da80 fffff802`6c4d680a     : 00000000`00000006 fffff802`6e69db60 ffffffff`ffffffb0 fffff802`6c4d65d4 : nt!HalpAcpiPmRegisterRead+0x39
fffff802`6e69dab0 fffff802`6c4d65a4     : 00000000`80010400 fffff802`69035879 ffffbe81`d5f05a00 fffff802`63ebc200 : ACPI!ACPIReadGpeStatusRegister+0x66
fffff802`6e69daf0 fffff802`6c4d5d01     : 00000000`80010400 ffff9986`6e259bf0 00000000`80010400 00000000`0000000c : ACPI!ACPIInterruptDispatchEvents+0x5c
fffff802`6e69db80 fffff802`6903489e     : fffff802`63ebc240 fffff802`6e69dcb0 fffff802`6e69de70 fffff802`00000002 : ACPI!ACPIInterruptServiceRoutineDPC+0xb1
fffff802`6e69dbb0 fffff802`69033b84     : fffff802`63eb9180 00000000`00000000 00000000`00000002 00000000`00000014 : nt!KiExecuteAllDpcs+0x30e
fffff802`6e69dd20 fffff802`692017c5     : 00000000`00000000 fffff802`63eb9180 00000000`00000000 ffff9986`708ba920 : nt!KiRetireDpcList+0x1f4
fffff802`6e69dfb0 fffff802`692015b0     : ffff9986`708ba978 00000000`00000000 ffff9986`708ba901 fffff802`69200d35 : nt!KxRetireDpcList+0x5
fffffa85`6c796cd0 fffff802`69200a18     : ffff9986`708ba900 ffff9986`708ba978 00000000`00000001 00000000`00000000 : nt!KiDispatchInterruptContinue
fffffa85`6c796d00 fffff802`6c50434a     : ffff9986`708ba900 ffff9986`708ba918 ffff9986`708ba918 ffff9986`708ba920 : nt!KiDpcInterrupt+0x2e8
fffffa85`6c796e90 fffff802`6c504225     : ffff9986`708ba920 ffff9986`708ba901 00000000`00000060 ffff9986`708ba901 : ACPI!ACPIEcServiceIoLoop+0xa6
fffffa85`6c796f10 fffff802`6c503506     : 00000000`00000000 ffff9986`708ba978 ffff9986`708ba978 00000000`00000000 : ACPI!ACPIEcServiceDevice+0x95
fffffa85`6c796f40 fffff802`6c50338d     : 00000000`00000001 ffff9986`c5ec6db8 fffff802`6c4d3b90 fffff802`6c4bf44c : ACPI!ACPIEcQueueEcIrp+0x136
fffffa85`6c796f80 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ACPI!ACPIEcOpRegionHandler+0x4d

SYMBOL_NAME:  ACPI!ACPIReadGpeStatusRegister+66

MODULE_NAME: ACPI

IMAGE_NAME:  ACPI.sys

IMAGE_VERSION:  10.0.19041.1741

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  66

FAILURE_BUCKET_ID:  0x133_ISR_ACPI!ACPIReadGpeStatusRegister

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {9524459d-2f22-efe5-b0c9-f824c586f42c}

Followup:     MachineOwner
---------
Windows for home | Windows 10 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

9 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. DaveM121 891.6K Reputation points Independent Advisor
    2022-11-21T12:36:21+00:00

    Hi Zhirui, glad to help, I will be here.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2022-11-21T12:35:45+00:00

    Thanks, I will try to do this.

    Was this answer helpful?

    0 comments
  3. DaveM121 891.6K Reputation points Independent Advisor
    2022-11-21T11:40:44+00:00

    Hi Zhirui,

    To try to force Windows 10 show any faulting drivers, the best option would be to turn on Driver Verifier, let your PC crash 3 times, then you must turn off Driver Verifier, and finally, upload any newly created minidump files

    https://answers.microsoft.com/en-us/windows/for...

    Note, if you have any difficulty getting into Windows with Driver Verifier enabled:

    Start your PC, just as Windows attempts to load (spinning dots), press and hold Power Button for 5 - 10 seconds to perform a Hard Shut Down

    Do this twice

    On the third start Windows will boot into the Recovery Environment and from there you can access System Repair, Safe Mode, Command Prompt... etc.

    Go to Troubleshoot - Advanced Option - Startup Settings and click Restart

    Upon restart, press 4 to enter Safe Mode

    Open Command Prompt as Administrator and run these two commands, then restart your PC.

    verifier /reset

    verifier /bootmode resetonbootfail

    Was this answer helpful?

    0 comments
  4. Anonymous
    2022-11-21T11:32:12+00:00

    No, I have this file only.

    Was this answer helpful?

    0 comments
  5. DaveM121 891.6K Reputation points Independent Advisor
    2022-11-21T09:23:00+00:00

    Hi Zhirui,

    I am Dave, I will help you with this.

    Your minidump files just indicated some driver associated to a device on the PCi bus is causing the crashes, the specific deice was not listed.

    Do you have any more minidump files you can upload for analysis?

    Was this answer helpful?

    0 comments