Share via

How to fix DPC_WATCHDOG_VIOLATION (133) on my PC?

兴勇 马 0 Reputation points
2023-11-08T12:40:37.2533333+00:00 

Microsoft (R) Windows Debugger Version 10.0.18362.1 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\110823-301718-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 19041 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff802`1ac00000 PsLoadedModuleList = 0xfffff802`1b82a360
Debug session time: Wed Nov  8 20:00:34.057 2023 (UTC + 8:00)
System Uptime: 0 days 22:48:32.875
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
.............
For analysis of this file, run !analyze -v
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: 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: fffff8021b8fb320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
	additional information regarding this single DPC timeout

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 timestamp for win32k.sys

KEY_VALUES_STRING: 1


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  19041.1.amd64fre.vb_release.191206-1406

SYSTEM_MANUFACTURER:  Dell Inc.

SYSTEM_PRODUCT_NAME:  Inspiron 3847

SYSTEM_SKU:  0622                  

SYSTEM_VERSION:    

BIOS_VENDOR:  Dell Inc.

BIOS_VERSION:  A08

BIOS_DATE:  06/29/2015

BASEBOARD_MANUFACTURER:  Dell Inc.

BASEBOARD_PRODUCT:  088DT1       

BASEBOARD_VERSION:  A01

DUMP_TYPE:  2

BUGCHECK_P1: 0

BUGCHECK_P2: 501

BUGCHECK_P3: 500

BUGCHECK_P4: fffff8021b8fb320

DPC_TIMEOUT_TYPE:  SINGLE_DPC_TIMEOUT_EXCEEDED

CPU_COUNT: 4

CPU_MHZ: c79

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 3c

CPU_STEPPING: 3

CPU_MICROCODE: 6,3c,3,0 (F,M,S,R)  SIG: 27'00000000 (cache) 27'00000000 (init)

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0x133

PROCESS_NAME:  System

CURRENT_IRQL:  d

ANALYSIS_SESSION_HOST:  TIANTIANTIAN

ANALYSIS_SESSION_TIME:  11-08-2023 20:12:29.0901

ANALYSIS_VERSION: 10.0.18362.1 amd64fre

LAST_CONTROL_TRANSFER:  from fffff8021b0317e0 to fffff8021affd640

STACK_TEXT:  
fffff802`1a1d3c88 fffff802`1b0317e0 : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
fffff802`1a1d3c90 fffff802`1ae48dbd : 000007db`34099c50 fffff802`1838c180 00000000`00000246 00000000`00503038 : nt!KeAccumulateTicks+0x1ebc40
fffff802`1a1d3cf0 fffff802`1ae3fe41 : fffff802`2d436e76 00000000`002fcbc5 fffff802`1838c180 00000000`00000001 : nt!KiUpdateRunTime+0x5d
fffff802`1a1d3d40 fffff802`1ae431d3 : fffff802`1838c180 00000000`00000000 fffff802`1b831a08 00000000`00000000 : nt!KiUpdateTime+0x4a1
fffff802`1a1d3e80 fffff802`1ae4aa62 : fffff802`1a1cc020 fffff802`1a1cc0a0 fffff802`1a1cc000 00000000`00000002 : nt!KeClockInterruptNotify+0x2e3
fffff802`1a1d3f30 fffff802`1aea7765 : 000000bf`31701f79 fffff802`1b8f3c20 fffff802`1b8f3cd0 ffffd501`69b61500 : nt!HalpTimerClockInterrupt+0xe2
fffff802`1a1d3f60 fffff802`1afff5da : fffff802`1a1cc0a0 fffff802`1b8f3c20 fffff802`267d9000 00000000`00000c30 : nt!KiCallInterruptServiceRoutine+0xa5
fffff802`1a1d3fb0 fffff802`1afffda7 : ffffd501`69b61500 fffff802`1af2a8aa ffffc484`71c86290 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff802`1a1cc020 fffff802`1fce11eb : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff802`1a1cc1b0 fffff802`267d1b53 : ffffd501`69b61500 fffff802`1af2a8aa ffffc484`71ca2e10 00000000`00000002 : WppRecorder!WppAutoLogTrace+0xbb
fffff802`1a1cc220 fffff802`267d1256 : 00000000`00000000 fffff802`1a1cc390 ffffc484`71c86100 fffff802`1af2a8aa : hidusb!WPP_RECORDER_SF_Lqq+0x93
fffff802`1a1cc290 fffff802`267f91b1 : ffffc484`00000000 ffffc484`71c86290 ffffc484`71c86290 fffff802`267fa710 : hidusb!HumInternalIoctl+0x136
fffff802`1a1cc580 fffff802`267facba : ffffc484`71c86290 fffff802`1a1cc719 fffff802`26811918 00000000`00000009 : HIDCLASS!HidpSubmitInterruptRead+0x1b1
fffff802`1a1cc600 fffff802`1ae546b5 : ffffc484`71c8ced3 ffffc484`71c8c860 fffff802`1a1cc701 ffffc484`71bb1000 : HIDCLASS!HidpInterruptReadComplete+0x5aa
fffff802`1a1cc6a0 fffff802`1ae544f7 : ffffc484`71c8c860 fffff802`1fbd8000 00000000`01000010 00000000`00000246 : nt!IopfCompleteRequest+0x1a5
fffff802`1a1cc780 fffff802`1fbd811a : 00000000`00000000 ffffc484`6f384dc0 ffffc484`71c8c860 00000000`00000000 : nt!IofCompleteRequest+0x17
fffff802`1a1cc7b0 fffff802`1fbd5bbf : ffffc484`71ba5102 fffff802`1ae1d9eb ffffc484`71c8c860 00000000`00000000 : Wdf01000!FxRequest::CompleteInternal+0x23a [minkernel\wdf\framework\shared\core\fxrequest.cpp @ 869] 
fffff802`1a1cc840 fffff802`2c80c1ec : 00000000`ffffff02 ffffc484`71ba5020 ffffc484`71c5e400 ffffc484`71c5e400 : Wdf01000!imp_WdfRequestComplete+0x8f [minkernel\wdf\framework\shared\core\fxrequestapi.cpp @ 436] 
fffff802`1a1cc8a0 fffff802`2c80c0b1 : ffffc484`71ba51c0 00000000`00000008 ffffc484`71ba5250 fffff802`1a1ccab8 : USBXHCI!Bulk_Transfer_CompleteCancelable+0xc8
fffff802`1a1cc900 fffff802`2c80bea0 : 00000000`01000010 00000000`00000a03 00000000`00000000 ffffc484`71c5e620 : USBXHCI!Bulk_ProcessTransferEventWithED1+0x1fd
fffff802`1a1cc9b0 fffff802`2c806910 : 00000000`00000004 fffff802`1a1cca88 00000000`00000008 fffff802`1a1cca90 : USBXHCI!Bulk_EP_TransferEventHandler+0x10
fffff802`1a1cc9e0 fffff802`2c806445 : 00000000`00000780 00003b7b`95268300 ffffc484`6f4ff8f0 ffffc484`71bcab70 : USBXHCI!Endpoint_TransferEventHandler+0xb0
fffff802`1a1cca40 fffff802`2c80611c : 00000000`01000010 00000000`00000a03 00003b7b`95281748 00000000`00000018 : USBXHCI!Interrupter_DeferredWorkProcessor+0x315
fffff802`1a1ccb40 fffff802`1fbd38f5 : 00000000`00000071 fffff802`1fbd3855 00000000`01000010 00000000`00000a07 : USBXHCI!Interrupter_WdfEvtInterruptDpc+0xc
fffff802`1a1ccb70 fffff802`1ae4d4fe : fffff802`1838f240 ffffc484`68f21000 fffff802`1a1ccea0 fffff802`00000002 : Wdf01000!FxInterrupt::_InterruptDpcThunk+0xa5 [minkernel\wdf\framework\shared\irphandlers\pnp\km\interruptobjectkm.cpp @ 404] 
fffff802`1a1ccbb0 fffff802`1ae4c7e4 : fffff802`1838c180 00000000`00000000 00000000`00000008 00000000`002fbd00 : nt!KiExecuteAllDpcs+0x30e
fffff802`1a1ccd20 fffff802`1b005b35 : 00000000`00000000 fffff802`1838c180 ffffd501`69b61500 00000000`00009400 : nt!KiRetireDpcList+0x1f4
fffff802`1a1ccfb0 fffff802`1b005920 : ffffd501`69b61500 fffff802`1af2a8aa 00000000`00000000 00000000`00000010 : nt!KxRetireDpcList+0x5
ffffc28b`492b5340 fffff802`1b0050a5 : 00000000`00009400 fffff802`1affed51 ffffc484`71d91000 fffff802`2d547288 : nt!KiDispatchInterruptContinue
ffffc28b`492b5370 fffff802`1affed51 : ffffc484`71d91000 fffff802`2d547288 00000000`00009400 00000000`00000000 : nt!KiDpcInterruptBypass+0x25
ffffc28b`492b5380 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiChainedDispatch+0xb1


THREAD_SHA1_HASH_MOD_FUNC:  05a1c5dd56b84834e0ee56aa7736d691ecb6a7a6

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  cb50c8a83d6d7703ddcf0589a6bfeb9db7ac808b

THREAD_SHA1_HASH_MOD:  93cb58557ab6e7fa00eda9adeb376b3ae17a4c40

FOLLOWUP_IP: 
WppRecorder!WppAutoLogTrace+bb
fffff802`1fce11eb 4d8d1439        lea     r10,[r9+rdi]

FAULT_INSTR_CODE:  39148d4d

SYMBOL_STACK_INDEX:  9

SYMBOL_NAME:  WppRecorder!WppAutoLogTrace+bb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: WppRecorder

IMAGE_NAME:  WppRecorder.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  15060d00

IMAGE_VERSION:  10.0.19041.1030

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  bb

FAILURE_BUCKET_ID:  0x133_DPC_WppRecorder!WppAutoLogTrace

BUCKET_ID:  0x133_DPC_WppRecorder!WppAutoLogTrace

PRIMARY_PROBLEM_CLASS:  0x133_DPC_WppRecorder!WppAutoLogTrace

TARGET_TIME:  2023-11-08T12:00:34.000Z

OSBUILD:  19041

OSSERVICEPACK:  3570

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  unknown_date

BUILDDATESTAMP_STR:  191206-1406

BUILDLAB_STR:  vb_release

BUILDOSVER_STR:  10.0.19041.1.amd64fre.vb_release.191206-1406

ANALYSIS_SESSION_ELAPSED_TIME:  9000

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x133_dpc_wpprecorder!wppautologtrace

FAILURE_ID_HASH:  {fd1da68d-ab73-baaf-a7e9-f0c09fd6a112}

Followup:     MachineOwner
---------
Windows 10
Windows 10
A Microsoft operating system that runs on personal computers and tablets.
11,195 questions
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Reza-Ameri 16,866 Reputation points
    2023-11-08T21:24:49.72+00:00

    Try open start and search for feedback and open the Feedback Hub app and report this issue.

    Run Windows Update and download and install all updates.

    Try visit Dell's support website and download and install the latest driver for your device (since you are using Dell).

    0 comments