Windows 10: DPC Watchdog violation (0x133, 1) with Win10 1809

Discus and support DPC Watchdog violation (0x133, 1) with Win10 1809 in Windows 10 Drivers and Hardware to solve the problem; Hi - I'm having sporadic blue screens, with stop code 133, 1 DPC WATCHDOG VIOLATION. Anecdotally this seems to have become an issue with Windows 10... Discussion in 'Windows 10 Drivers and Hardware' started by Damian Wilson UK, Mar 3, 2019.

  1. DAMIAN WILSON UK
    Damian Wilson UK Win User

    DPC Watchdog violation (0x133, 1) with Win10 1809


    Hi -


    I'm having sporadic blue screens, with stop code 133, 1 DPC WATCHDOG VIOLATION. Anecdotally this seems to have become an issue with Windows 10 1809. It only seems to occur with web browsing, most often when looking at media heavy pages - interestingly the system will play CPU/GPU/memory intensive games absolutely rock-solid.


    Some system details:

    Intel i7-6700K (8 core)

    32 Gb RAM

    Gigabyte Z170X Gaming 3 motherboard

    Gigabyte GeForce GTX 1070 G1 Gaming 8G

    Intel SSD 600p 512Gb boot

    Western Digital WD2003FZEX 1.8Tb data drive

    Killer E2200 ethernet (part of motherboard)

    Windows 10 Pro, x64, 1809 - Hyper-V enabled

    Running Windows Defender, default settings


    I have crash dump(s) available, including one with kernel circular logging enabled, happy to supply to MS. WinDbg !analyze points to nvlddmkm (see below), but as I understand it, these DPC watchdog violations are tricky to diagnose since Windows is complaining of a cumulative error and the DPC itself could be servicing frequent interrupts.


    I've tried just about everything I can think of - updating BIOS, removing/downgrading/upgrading NVidia drivers (now back to latest), updating SSD firmware, updating network drivers, disabling HDMI audio driver to no avail.


    Note dumps vary, I have one where pretty much the only DPCs in the queue are ndis, dxgkrnl and nvlddkm. The ETL trace shows dxgkrnl flatlining CPU 0 prior to the bugcheck.



    I'm at the point of thinking I need to change the graphics card, but before going down those lines it'd be great to get some confirmation of whether I'm looking at genuine hardware problem or not.


    !analyze -v dump:

    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. The offending component can usually be
    identified with a stack trace.
    Arg2: 0000000000001e00, The watchdog period.
    Arg3: fffff802337ed380, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
    additional information regarding the cumulative timeout
    Arg4: 0000000000000000

    Debugging Details:
    ------------------


    KEY_VALUES_STRING: 1


    PROCESSES_ANALYSIS: 1

    SERVICE_ANALYSIS: 1

    STACKHASH_ANALYSIS: 1

    TIMELINE_ANALYSIS: 1


    DUMP_CLASS: 1

    DUMP_QUALIFIER: 401

    BUILD_VERSION_STRING: 17763.1.amd64fre.rs5_release.180914-1434

    SYSTEM_MANUFACTURER: Gigabyte Technology Co., Ltd.

    SYSTEM_PRODUCT_NAME: Z170X-Gaming 3

    SYSTEM_SKU: Default string

    SYSTEM_VERSION: Default string

    BIOS_VENDOR: American Megatrends Inc.

    BIOS_VERSION: F21

    BIOS_DATE: 03/06/2017

    BASEBOARD_MANUFACTURER: Gigabyte Technology Co., Ltd.

    BASEBOARD_PRODUCT: Z170X-Gaming 3

    BASEBOARD_VERSION: x.x

    DUMP_TYPE: 1

    BUGCHECK_P1: 1

    BUGCHECK_P2: 1e00

    BUGCHECK_P3: fffff802337ed380

    BUGCHECK_P4: 0

    DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

    CPU_COUNT: 8

    CPU_MHZ: fa8

    CPU_VENDOR: GenuineIntel

    CPU_FAMILY: 6

    CPU_MODEL: 5e

    CPU_STEPPING: 3

    CPU_MICROCODE: 6,5e,3,0 (F,M,S,R) SIG: C2'00000000 (cache) C2'00000000 (init)

    BLACKBOXBSD: 1 (    !blackboxbsd)


    BLACKBOXPNP: 1 (    !blackboxpnp)


    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

    BUGCHECK_STR: 0x133

    PROCESS_NAME: System

    CURRENT_IRQL: d

    ANALYSIS_SESSION_HOST:

    ANALYSIS_SESSION_TIME: 03-03-2019 11:18:15.0121

    ANALYSIS_VERSION: 10.0.18317.1001 amd64fre

    LAST_CONTROL_TRANSFER: from fffff****02`333cedaf : 0000****`755****`7558f510 ffff8080`cb30e140 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
    ffffae06`755****`7558f630 fffff802`33367cde : 00000000`00000000 fffff802`3933b5dd 00000000`00000000 00000000`00000001 : nt!KiChainedDispatch+0xb1
    ffffae06`7558f7c0 fffff802`39318f8c : ffffae06`7558f820 00000000`00000004 00000000`00000000 ffff5e9a`09c1fd2b : nt!KzLowerIrql+0x1e
    ffffae06`7558f7f0 fffff802`3933c783 : 00000000`00000002 00000000`00000000 00000000`00000000 00000000`00000000 : nvlddmkm+0x****
    ffffae06`755****aa0 00000000`00000000 ffff9d83`e04b9040 00000000`00000000 : nvlddmkm+0x1dc5e1
    ffffae06`755****3`eb730040 00000000`00000000 : nt!ExpWorkerThread+0x16a
    ffffae06`7558fb90 fffff802`3346589c : ffff8080`ca7a0180 ffff9d83`eb730040 fffff802`33331b70 00000000`00000000 : nt!PspSystemThreadStartup+0x55
    ffffae06`7558fbe0 00000000`00000000 : ffffae06`75590000 ffffae06`75589000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x1c


    THREAD_SHA1_HASH_MOD_FUNC: 7defba9c24bb5c2c6ff517dc1b196667cd39d7f3

    THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 85a62b95549dcec35b074af313a7366f4a7e75b1

    THREAD_SHA1_HASH_MOD: e****8c48348

    SYMBOL_STACK_INDEX: a

    SYMBOL_NAME: nvlddmkm+1f8f8c

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME:     nvlddmkm

    IMAGE_NAME: nvlddmkm.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 5c5b3281

    STACK_COMMAND: .thread ; .cxr ; kb

    BUCKET_ID_FUNC_OFFSET: 1f8f8c

    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-02-27T19:45:28.000Z

    OSBUILD: 17763

    OSSERVICEPACK: 0

    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: 180914-1434

    BUILDLAB_STR: rs5_release

    BUILDOSVER_STR: 10.0.17763.1.amd64fre.rs5_release.180914-1434

    ANALYSIS_SESSION_ELAPSED_TIME: dc4

    ANALYSIS_SOURCE: KM

    FAILURE_ID_HASH_STRING: km:0x133_isr_nvlddmkm!unknown_function

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

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

    0: kd> !dpcs
    CPU Type KDPC Function
    0: Normal : 0xfffff802329a2f90 0xfffff802333cca****d48e0 dxgkrnl!DpiFdoDpcForIsr
    0: Normal : 0xffff9d83e0d44ac8 0xfffff8079ff466b0 ndis!ndisInterruptDpc
    0: Normal : 0xffff9d83e5fded00 0xfffff8079f183780 Wdf01000!FxInterrupt::_InterruptDpcThunk
    0: Normal : 0xffff9d83f29d6648 0xfffff802334380f0 nt!EtwpLoggerDpc
    0: Normal : 0xffff9d83e01a11c0 0xfffff8079f782710 stornvme!NVMeCompletionDpcRoutine
    0: Normal : 0xffff9d83e06c80c8 0xfffff8023488b780 tcpip!TcpPeriodicTimeoutHandler
    0: Normal : 0xffffae0679e0f6d0 0xfffff802332ef520 nt!PopExecuteProcessorCallback
    0: Normal : 0xffffae06775df6d0 0xfffff802332ef520 nt!PopExecuteProcessorCallback
    0: Normal : 0xffffae067a4f76d0 0xfffff802332ef520 nt!PopExecuteProcessorCallback
    0: Normal : 0xffffae06797cf010 0xfffff802332ef520 nt!PopExecuteProcessorCallback
    0: Normal : 0xffff9d83e9d4b9a0 0xfffff80280676d20 Ndu!NduQueryStatisticsDpc
    0: Normal : 0xffffae06760076d0 0xfffff802332ef520 nt!PopExecuteProcessorCallback
    0: Normal : 0xffff9d83e0c9ad28 0xfffff8023a551900 HDAudBus!HdaController::CodecDpc

    0: Threaded: 0xfffff802329a30d8 0xfffff8023330f480 nt!KiDpcWatchdog


    Thanks in advance,


    Damian

    :)
     
    Damian Wilson UK, Mar 3, 2019
    #1
  2. AUGGY
    auggy Win User

    DPC watchdog violation

    A minidump file has a record of what occurred during a blue screen error such as a

    DPC_WATCHDOG_VIOLATION     error and may help identify the cause of the error.

    Did you locate the minidump files?
     
    auggy, Mar 3, 2019
    #2
  3. ERIC BER
    Eric Ber Win User
    DPC watchdog violation

    Hi Kathy,

    To assist you further, kindly answer the questions below:

    • Have you made any changes to your computer prior to this issue?
    • What troubleshooting steps have you done so far?
    • Have you tried the troubleshooting steps on this
      link       that was provided by Billion Debbarma on September 19, 2015 and see if you will still encounter the same issue?

    Regards.
     
    Eric Ber, Mar 3, 2019
    #3
  4. LARS-GöRANÖHMAN
    Lars-GöranÖhman Win User

    DPC Watchdog violation (0x133, 1) with Win10 1809

    DPC Watchdog Violation

    Another DPC Watchdog Violation today 17 december 2016, HELP!!
     
    Lars-GöranÖhman, Mar 3, 2019
    #4
Thema:

DPC Watchdog violation (0x133, 1) with Win10 1809

Loading...

  1. DPC Watchdog violation (0x133, 1) with Win10 1809 - Similar Threads - DPC Watchdog violation

  2. win10 dpc watchdog violation

    in Windows 10 Gaming
    win10 dpc watchdog violation: Microsoft R Windows Debugger Version 6.12.0002.633 AMD64 Copyright c Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\092524-8515-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: *** Invalid...

  3. win10 dpc watchdog violation

    in Windows 10 Software and Apps
    win10 dpc watchdog violation: Microsoft R Windows Debugger Version 6.12.0002.633 AMD64 Copyright c Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\092524-8515-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: *** Invalid...

  4. win10 dpc watchdog violation

    in Windows 10 Drivers and Hardware
    win10 dpc watchdog violation: Microsoft R Windows Debugger Version 6.12.0002.633 AMD64 Copyright c Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\092524-8515-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: *** Invalid...

  5. DPC watchdog violation

    in Windows 10 BSOD Crashes and Debugging
    DPC watchdog violation: Hi, I've had this issue before and fixed it by asking the community but I'm not sure if the same thing is causing it this time. My windows 10 pc freezes every once in a while and sends me to a screen that says "your device ran into a problem and needs to restart." along with...

  6. DPC Watchdog Violation

    in Windows 10 Gaming
    DPC Watchdog Violation: I've been getting a lot of this BSOD and I thought it was because of my Nord VPN but after switching it's not gone away. Can anyone point me in the right direction? Thanks in advance!https://drive.google.com/drive/folders/1gzvlzr7Y0K3v1zWhSQePtIN2vsB75S9v?usp=sharing...

  7. DPC WATCHDOG VIOLATION

    in Windows 10 Software and Apps
    DPC WATCHDOG VIOLATION: SATAsfc /scannowdebugger toolminidump, minidumphttps://anonfiles.com/f0O9u2E8x1/minidump_7z==============Eng=================The computer has rebooted from a bugcheck. The bugcheck was: 0x00000133 0x0000000000000001, 0x0000000000001e00, 0xfffff80068cfb320,...

  8. DPC Watchdog Violation

    in Windows 10 Ask Insider
    DPC Watchdog Violation: Need help with DPC Watchdog violation; pc was just kind of idle and suddenly BSOD. I'm running windows 10 version 1909 Build(18363.720) 2 of the latest updates have been giving me random bsods as well and I have felt that the KB4551762 update has been the most stable for me...

  9. DPC Watchdog Violation

    in Windows 10 Support
    DPC Watchdog Violation: hi recently I have a problem that I have blue screen (dpc watchdog violation) sometimes happens to me especially when I open the overwatch game sometimes I can play all day and without problems and other times just start the game I get the error of dpc watchdog violation blue...

  10. BSOD Since Win10 1809 update, 0x133(1) DPC Watchdog Violation

    in Windows 10 BSOD Crashes and Debugging
    BSOD Since Win10 1809 update, 0x133(1) DPC Watchdog Violation: Hi Guys, Getting random yet sometimes frequent 0x133 (1) Bugcheck on my laptop since the win10 v1809 update. I had this several months ago, and the only way to fix it was to roll back to v1803, problem solved. Forward to now, and I recently allowed it to update again, and...
  1. MOHDFARIS1
    Thread

    dpc_watchdog_violation bsod

    hi, when i launch rainbow six siege my computer constantly crashes into bsod.Is there any way i can solve this? Using an asus x550jx on Windows...
    Thread by: MohdFaris1, Nov 15, 2020, 0 replies, in forum: Windows 10 Gaming
  2. OSKARI_SALMONLAKE
    Thread

    Blue screen crash: dpc_watchdog_violation. PC constantly reboots due to bugchecks. How to...

    Win10 crashes about every 15 minutes. It crashes into bluescreen and an error code. DPC_watchdog_violation. I built this pc a few years ago and...
    Thread by: Oskari_Salmonlake, Nov 11, 2020, 3 replies, in forum: Windows 10 BSOD Crashes and Debugging
  3. SPEN_2
    Thread

    BoD DPC_WATCHDOG_VIOLATION / VIDEO_TDR_FAILURE due to graphics driver or faulty hardware?

    Since quite some time I regularly get BoDs with a DPC_WATCHDOG_VIOLATION 133 and after some driver changes VIDEO_TDR_FAILURE 116....
    Thread by: Spen_2, Nov 8, 2020, 3 replies, in forum: Windows 10 BSOD Crashes and Debugging
  4. RAZVANCHINA
    Thread

    DPC_WATCHDOG_VIOLATION 133

    while I was using my pc it just froze and then bluescreen out of nowhere. I opened the minidump file and this is what I got. Microsoft R Windows...
    Thread by: RazvanChina, Nov 3, 2020, 3 replies, in forum: Windows 10 BSOD Crashes and Debugging
  5. TRAVISAS
    Thread

    DPC_WATCHDOG_VIOLATION

    My computer crashed about a month ago and gave me the DPC_WATCHDOG_VIOLATION BSOD. It ended up sending my computer into a automatic repair loop. I...
    Thread by: TravisAS, Nov 2, 2020, 3 replies, in forum: Windows 10 BSOD Crashes and Debugging
Tags:

Users found this page by searching for:

  1. windows 10 1903 1809 whocrashed bluescreen dpc watchdog

    ,

  2. i7 6700k dpc watchdog violation

    ,

  3. driver causes BSOD 133

    ,
  4. nvlddmkm dpc watchdog violation gtx980 1809,
  5. dpc watchdog vialoation