Windows 10: Bsod - dpc_watchdog_violation (133)

Discus and support Bsod - dpc_watchdog_violation (133) in Windows 10 BSOD Crashes and Debugging to solve the problem; Hi guys, This is Lenovo ideapad 320 laptop Winver 2004 that keep crashing with the DPC Watchdog Violation 133. I ran the Windbg with Anlyze-v and... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by rmalchi, Oct 3, 2020.

  1. rmalchi Win User

    Bsod - dpc_watchdog_violation (133)


    Hi guys,

    This is Lenovo ideapad 320 laptop Winver 2004 that keep crashing with the DPC Watchdog Violation 133.
    I ran the Windbg with Anlyze-v and came up with the following error codes which by googling rtwlane seems to be the Realtek 8821AE Wireless Lan card. How do I verify it is actually this card that causing the crashes?
    Here are the V2 Log Collector logs : Sign in to your account




    SYMBOL_NAME: rtwlane+39cf88

    MODULE_NAME: rtwlane

    IMAGE_NAME: rtwlane.sys

    STACK_COMMAND: .thread ; .cxr ; kb

    BUCKET_ID_FUNC_OFFSET: 39cf88

    FAILURE_BUCKET_ID: 0x133_ISR_rtwlane!unknown_function

    OS_VERSION: 10.0.19041.1

    BUILDLAB_STR: vb_release

    OSPLATFORM_TYPE: x64

    OSNAME: Windows 10


    Thank you all,
    Roy

    :)
     
    rmalchi, Oct 3, 2020
    #1

  2. Windows 10 build 10586 BSOD DPC_WATCHDOG_VIOLATION

    Check (enable) it then do Step #5 & test.

    The above notwithstanding...

    Are you still getting the DPC_WATCHDOG_VIOLATION BSODs or...?
     
    PA Bear - MS MVP, Oct 3, 2020
    #2
  3. BSoD : DPC_WATCHDOG_VIOLATION (133)

    I am using Win 10 and keep getting a DPC_WATCHDOG_VIOLATION (133) BSoD at random intervals.

    Below is my latest mini dump results, can anyone assist.

    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. The offending component can usually be

    identified with a stack trace.

    Arg2: 0000000000001e00, The watchdog period.

    Arg3: fffff80121bf2380, 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 ***

    *** ***

    *************************************************************************

    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: 17763.1.amd64fre.rs5_release.180914-1434

    SYSTEM_MANUFACTURER: Hewlett-Packard

    SYSTEM_PRODUCT_NAME: HP EliteDesk 800 G1 TWR

    SYSTEM_SKU: C8N27AV

    BIOS_VENDOR: Hewlett-Packard

    BIOS_VERSION: L01 v02.74

    BIOS_DATE: 01/25/2018

    BASEBOARD_MANUFACTURER: Hewlett-Packard

    BASEBOARD_PRODUCT: 18E4

    DUMP_TYPE: 2

    BUGCHECK_P1: 1

    BUGCHECK_P2: 1e00

    BUGCHECK_P3: fffff80121bf2380

    BUGCHECK_P4: 0

    DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

    CPU_COUNT: 8

    CPU_MHZ: d40

    CPU_VENDOR: GenuineIntel

    CPU_FAMILY: 6

    CPU_MODEL: 3c

    CPU_STEPPING: 3

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

    BLACKBOXBSD: 1 (!blackboxbsd)

    BLACKBOXPNP: 1 (!blackboxpnp)

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

    BUGCHECK_STR: 0x133

    PROCESS_NAME: OUTLOOK.EXE

    CURRENT_IRQL: d

    ANALYSIS_SESSION_HOST: LAPIN0140

    ANALYSIS_SESSION_TIME: 06-03-2019 15:09:51.0953

    ANALYSIS_VERSION: 10.0.18362.1 amd64fre

    LAST_CONTROL_TRANSFER: from fffff801218dcbc3 to fffff80121863730

    STACK_TEXT:

    fffff801`214ceba8 fffff801`218dcbc3 : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff801`21bf2380 : nt!KeBugCheckEx

    fffff801`214cebb0 fffff801`217948bf : 0006e3d4`051cf7e3 fffff801`1fdae180 00000000`00000286 00000000`022e4dde : nt!KeAccumulateTicks+0x144c93

    fffff801`214cec10 fffff801`2161b47c : 00000000`00000000 fffff801`21680750 fffff503`048b1f50 fffff801`21680800 : nt!KeClockInterruptNotify+0xcf

    fffff801`214cef30 fffff801`217e3195 : fffff801`21680750 fffff801`21864d40 ffffad00`1e2348c8 fffff503`048b1f50 : hal!HalpTimerClockIpiRoutine+0x1c

    fffff801`214cef60 fffff801`2186512a : fffff503`048b1f50 fffff801`21680750 00000000`c1d00000 fffff801`21680750 : nt!KiCallInterruptServiceRoutine+0xa5

    fffff801`214cefb0 fffff801`21865677 : 00000000`00000000 fffff503`048b1f50 ffffad00`1e2348c0 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa

    fffff503`048b1ed0 fffff801`21869c31 : 00000000`00000003 fffff801`218649e1 00000000`00000000 fffff503`048b20f0 : nt!KiInterruptDispatchNoLockNoEtw+0x37

    fffff503`048b2060 fffff801`218649e1 : 00000000`00000000 fffff503`048b20f0 ffffad00`1e2348c0 ffffe08c`3051fda0 : nt!KiDpcInterruptBypass+0x11

    fffff503`048b2070 fffff801`2c00f5f5 : 00000000`00000002 00000000`00000001 00000000`00000003 ffffae07`b64942a8 : nt!KiChainedDispatch+0xb1

    fffff503`048b2200 00000000`00000002 : 00000000`00000001 00000000`00000003 ffffae07`b64942a8 00000000`00000000 : nvlddmkm+0x1bf5f5

    fffff503`048b2208 00000000`00000001 : 00000000`00000003 ffffae07`b64942a8 00000000`00000000 fffff801`2c00f918 : 0x2

    fffff503`048b2210 00000000`00000003 : ffffae07`b64942a8 00000000`00000000 fffff801`2c00f918 fffff503`048b23f0 : 0x1

    fffff503`048b2218 ffffae07`b64942a8 : 00000000`00000000 fffff801`2c00f918 fffff503`048b23f0 ffffe08c`428ca080 : 0x3

    fffff503`048b2220 00000000`00000000 : fffff801`2c00f918 fffff503`048b23f0 ffffe08c`428ca080 00000000`00000000 : 0xffffae07`b64942a8

    THREAD_SHA1_HASH_MOD_FUNC: 936ab3482a43b455fc540bcc4956a7e7f0603158

    THREAD_SHA1_HASH_MOD_FUNC_OFFSET: ce2f9a73874763c8485aecdab5d96458e84039fd

    THREAD_SHA1_HASH_MOD: d0c4326baaecf4e9adb1c8c55d4daee64aa76950

    FOLLOWUP_IP:

    nvlddmkm+1bf5f5

    fffff801`2c00f5f5 488b542438 mov rdx,qword ptr [rsp+38h]

    FAULT_INSTR_CODE: 24548b48

    SYMBOL_STACK_INDEX: 9

    SYMBOL_NAME: nvlddmkm+1bf5f5

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nvlddmkm

    IMAGE_NAME: nvlddmkm.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 59953bcb

    STACK_COMMAND: .thread ; .cxr ; kb

    BUCKET_ID_FUNC_OFFSET: 1bf5f5

    FAILURE_BUCKET_ID: 0x133_ISR_nvlddmkm!unknown_function

    BUCKET_ID: 0x133_ISR_nvlddmkm!unknown_function

    PRIMARY_PROBLEM_CLASS: 0x133_ISR_nvlddmkm!unknown_function

    TARGET_TIME: 2019-05-24T13:49:15.000Z

    OSBUILD: 17763

    OSSERVICEPACK: 437

    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: 2005-12-02 08:58:59

    BUILDDATESTAMP_STR: 180914-1434

    BUILDLAB_STR: rs5_release

    BUILDOSVER_STR: 10.0.17763.1.amd64fre.rs5_release.180914-1434

    ANALYSIS_SESSION_ELAPSED_TIME: 27a85

    ANALYSIS_SOURCE: KM

    FAILURE_ID_HASH_STRING: km:0x133_isr_nvlddmkm!unknown_function

    FAILURE_ID_HASH: {f97493a5-ea2b-23ca-a808-8602773c2a86}

    Followup: MachineOwner

    ---------
     
    Sachin Kumar Dubey (SACD), Oct 3, 2020
    #3
  4. Bsod - dpc_watchdog_violation (133)

    BSOD with DPC_WATCHDOG_VIOLATION

    Hi,

    Thank you for contacting Microsoft community.

    I suggest you to follow the below article regarding BSOD error and check if it helps.

    DPC_WATCHDOG_VIOLATION

    Bluescreen Error: DPC_WATCHDOG_VIOLATION

    Hope this information was helpful and do let us know if you need further assistance. We will be glad to assist.
     
    Karthicka_R, Oct 3, 2020
    #4
Thema:

Bsod - dpc_watchdog_violation (133)

Loading...
  1. Bsod - dpc_watchdog_violation (133) - Similar Threads - Bsod dpc_watchdog_violation 133

  2. Problem with BSOD DPC_WATCHDOG_VIOLATION 133

    in Windows 10 Gaming
    Problem with BSOD DPC_WATCHDOG_VIOLATION 133: I am experiencing a BSOD DPC_WATCHDOG_VIOLATION 133 on my Windows 10 computer. It often occurs when I am listening to music through applications like Spotify. Here are the specifications of my computer:Intel Core i3 7100Gigabyte H110M-DS2Nvidia GTX 1650s 4GB GDDR68x1 DDR4 RAM...
  3. Problem with BSOD DPC_WATCHDOG_VIOLATION 133

    in Windows 10 Software and Apps
    Problem with BSOD DPC_WATCHDOG_VIOLATION 133: I am experiencing a BSOD DPC_WATCHDOG_VIOLATION 133 on my Windows 10 computer. It often occurs when I am listening to music through applications like Spotify. Here are the specifications of my computer:Intel Core i3 7100Gigabyte H110M-DS2Nvidia GTX 1650s 4GB GDDR68x1 DDR4 RAM...
  4. DPC_WATCHDOG_VIOLATION 133 BSOD with minidump

    in Windows 10 Gaming
    DPC_WATCHDOG_VIOLATION 133 BSOD with minidump: Looking for someone to help me with this. My computer has BSOD about 10 times in the last week. About one to two times a day. Sometimes just when idle.********************************************************************************...
  5. DPC_WATCHDOG_VIOLATION 133 BSOD with minidump

    in Windows 10 Software and Apps
    DPC_WATCHDOG_VIOLATION 133 BSOD with minidump: Looking for someone to help me with this. My computer has BSOD about 10 times in the last week. About one to two times a day. Sometimes just when idle.********************************************************************************...
  6. DPC_WATCHDOG_VIOLATION 133 BSOD with minidump

    in Windows 10 BSOD Crashes and Debugging
    DPC_WATCHDOG_VIOLATION 133 BSOD with minidump: Looking for someone to help me with this. My computer has BSOD about 10 times in the last week. About one to two times a day. Sometimes just when idle.********************************************************************************...
  7. BSOD netr28ux.sys DPC_WATCHDOG_VIOLATION 133

    in Windows 10 Software and Apps
    BSOD netr28ux.sys DPC_WATCHDOG_VIOLATION 133: HelloI went into BSOD problem with netr28us.sys when browsing chrome or online gaming since my WIFI Modem Router replaced. I've checked the community with the same problem then I replaced the netr28us.sys driver with the previous version, my windows will still crash. I've...
  8. BSOD netr28ux.sys DPC_WATCHDOG_VIOLATION 133

    in Windows 10 Drivers and Hardware
    BSOD netr28ux.sys DPC_WATCHDOG_VIOLATION 133: HelloI went into BSOD problem with netr28us.sys when browsing chrome or online gaming since my WIFI Modem Router replaced. I've checked the community with the same problem then I replaced the netr28us.sys driver with the previous version, my windows will still crash. I've...
  9. DPC_WATCHDOG_VIOLATION 133 BSOD ntkrnlmp.exe

    in Windows 10 BSOD Crashes and Debugging
    DPC_WATCHDOG_VIOLATION 133 BSOD ntkrnlmp.exe: Hello There! I would like to ask help, rather for a long time constant BOSD is my problem, and I do not manage to solve it. I receive a diverse mistake when I try to analyse the mistake, and i don't know what can I do. This is thi last one dump: Loading Dump File...
  10. BSoD : DPC_WATCHDOG_VIOLATION (133)

    in Windows 10 BSOD Crashes and Debugging
    BSoD : DPC_WATCHDOG_VIOLATION (133): I am using Win 10 and keep getting a DPC_WATCHDOG_VIOLATION (133) BSoD at random intervals. Below is my latest mini dump results, can anyone assist. DPC_WATCHDOG_VIOLATION (133) The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above....