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; 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.... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by Sachin Kumar Dubey (SACD), Jun 7, 2019.

  1. 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), Jun 7, 2019
    #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, Jun 7, 2019
    #2
  3. BSOD DPC_WATCHDOG_VIOLATION

    A. Analysis Results

    1. File Name:121018-9484-01.dmp

    DPC_WATCHDOG_VIOLATION (133)

    IMAGE_NAME: nvlddmkm.sys

    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys

    B. Third Party Drivers

    nvlddmkm.sys - nVidia

    Driver Date - 27-Oct-17

    C. Recommendations

    Your nVidia driver is still of 27-Oct-17 date. It means it was not updated. Update it.
     
    Vijay_Verma, Jun 7, 2019
    #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, Jun 7, 2019
    #4
Thema:

BSoD : DPC_WATCHDOG_VIOLATION (133)

Loading...
  1. BSoD : DPC_WATCHDOG_VIOLATION (133) - Similar Threads - BSoD DPC_WATCHDOG_VIOLATION 133

  2. DPC_WATCHDOG_VIOLATION 133 Keeps Occuring

    in Windows 10 BSOD Crashes and Debugging
    DPC_WATCHDOG_VIOLATION 133 Keeps Occuring: Hi. I keep getting the DPC WATCHDOG VIOLATION and I don't know how to fix it. I've tried updating the drivers but nothing helps. Most recent crash dump: Microsoft R Windows Debugger Version 10.0.19528.1000 AMD64Copyright c Microsoft Corporation. All rights...
  3. Código de Error DPC_WATCHDOG_VIOLATION 133 - 0x133_DPC_nvlddmkm!unknown_function

    in Windows 10 BSOD Crashes and Debugging
    Código de Error DPC_WATCHDOG_VIOLATION 133 - 0x133_DPC_nvlddmkm!unknown_function: He tenido este bsod desde que recuerdo haber tenido esta computadora. He tratado de formatearla completamente e incluso re-instalar Windows pero el error persistía así que la llevé al servicio técnico de Acer donde le cambiaron el disco duro pero con solo horas de usarla el...
  4. pc frezez sometimes on startup DPC_WATCHDOG_VIOLATION 133

    in Windows 10 BSOD Crashes and Debugging
    pc frezez sometimes on startup DPC_WATCHDOG_VIOLATION 133: here is the link to the drive where all the information is for the stuff https://drive.google.com/open?id=1p_QY7HzqfEyU2T4mrof9MjNxjh1joG9b https://answers.microsoft.com/en-us/windows/forum/all/pc-frezez-sometimes-on-startup/372f9cf4-1aca-4826-9d0e-cdc479721513
  5. DPC_WATCHDOG_VIOLATION (133)

    in Windows 10 BSOD Crashes and Debugging
    DPC_WATCHDOG_VIOLATION (133): Hello, some days ago my computer started crashing with this bluescreen. I tried several things already but didn't find out the issue: - Sometimes it crashes after many hours of usage, today it crashed after a little more than one hour. - Every crash happened when playing...
  6. DPC_WATCHDOG_VIOLATION (133) when closing monitor of laptop

    in Windows 10 BSOD Crashes and Debugging
    DPC_WATCHDOG_VIOLATION (133) when closing monitor of laptop: Dear all, Since yesterday I have trouble with my computer when I close the monitor of my laptop. It is a Lenovo ThinkPad X1 Yoga 2nd. I installed WinDBG and extracted the following information from the memory.dmp file. Any Idea what is the reason for this problem?...
  7. BSOD DPC_watchdog_violation

    in Windows 10 BSOD Crashes and Debugging
    BSOD DPC_watchdog_violation: Computer keeps crashing and giving this error. What is it and what do I need to do? I have MSinfo and dump files from last incident. https://answers.microsoft.com/en-us/windows/forum/all/bsod-dpcwatchdogviolation/c1e547ca-7535-4d8f-8120-b92232569dd1
  8. BSOD after 15 min idling (following boot). DPC_WATCHDOG_VIOLATION 133

    in Windows 10 BSOD Crashes and Debugging
    BSOD after 15 min idling (following boot). DPC_WATCHDOG_VIOLATION 133: Hello, So I just bought a brand new HP spectre, installed few softwares like CCleaner, Speccy... And randomly get BSOD 10 or 15 min after booting (btw booting takes some time , about 1min ((for an SSD that's quite long isn't it ?))). I noticed that it can take up to 30 min...
  9. BSOD DPC_WATCHDOG_VIOLATION, error (133) driving me crazy

    in Windows 10 BSOD Crashes and Debugging
    BSOD DPC_WATCHDOG_VIOLATION, error (133) driving me crazy: System Config: GA-970A-UD3 1.1 AMD FX-6100, 16G RAM NVIDIA GeForce GT 610 Patriot Pyro SE 120GB SSD WD 1TB SATA III ST 1TB SATA III I continue to get DPC_WATCHDOG_VIOLATION. I have updated BIOS, MB Drivers (Realtek LAN and Audio) , NVIDIA Drivers. I have disabled...
  10. BSOD DPC_Watchdog_Violation

    in Windows 10 BSOD Crashes and Debugging
    BSOD DPC_Watchdog_Violation: Dear Sir/Madame, I have received a few messages since upgrading to Windows 10 saying my computer needed to restart and that I could find the answer at DPC Watchdog Violation. I have not had this happen while I am using the computer but the message seems to happen when the...

Users found this page by searching for:

  1. DPC_WATCHDOG_VIOLATION (133)