Windows 10: Watch Dog Violation 133

Discus and support Watch Dog Violation 133 in Windows 10 BSOD Crashes and Debugging to solve the problem; Microsoft (R) Windows Debugger Version 10.0.18303.1000 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by Jdiddy480, Dec 24, 2018.

  1. JDIDDY480
    Jdiddy480 Win User

    Watch Dog Violation 133


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


    Loading Dump File [C:\Users\jonbo\OneDrive\Desktop\MEMORY.DMP]
    Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.


    ************* Path validation summary **************
    Response Time (ms) Location
    Deferred srv*
    Symbol search path is: srv*
    Executable search path is:
    Windows 10 Kernel Version 17134 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 17134.1.amd64fre.rs4_release.180410-1804
    Machine Name:
    Kernel base = 0xfffff801`85406000 PsLoadedModuleList = 0xfffff801`857b4150
    Debug session time: Sun Dec 23 19:53:08.707 2018 (UTC - 7:00)
    System Uptime: 6 days 9:17:36.437
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ................................................................
    ................
    Loading User Symbols
    PEB is paged out (Peb.Ldr = 000000a8`47dbc018). Type ".hh dbgerr001" for details
    Loading unloaded module list
    ..................................................
    For analysis of this file, run     !analyze -v
    nt!KeBugCheckEx:
    fffff801`855b00a0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffa600`58115bd0=0000000000000133
    1: 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: fffff80185853378, 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

    STACKHASH_ANALYSIS: 1

    TIMELINE_ANALYSIS: 1


    DUMP_CLASS: 1

    DUMP_QUALIFIER: 401

    BUILD_VERSION_STRING: 17134.1.amd64fre.rs4_release.180410-1804

    SYSTEM_MANUFACTURER: Acer

    SYSTEM_PRODUCT_NAME: Predator G3-571

    SYSTEM_SKU: 0000000000000000

    SYSTEM_VERSION: V1.15

    BIOS_VENDOR: Insyde Corp.

    BIOS_VERSION: V1.15

    BIOS_DATE: 03/05/2018

    BASEBOARD_MANUFACTURER: KBL

    BASEBOARD_PRODUCT: Sienta_KLS

    BASEBOARD_VERSION: V1.15

    DUMP_TYPE: 1

    BUGCHECK_P1: 1

    BUGCHECK_P2: 1e00

    BUGCHECK_P3: fffff80185853378

    BUGCHECK_P4: 0

    DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

    CPU_COUNT: 8

    CPU_MHZ: af8

    CPU_VENDOR: GenuineIntel

    CPU_FAMILY: 6

    CPU_MODEL: 9e

    CPU_STEPPING: 9

    CPU_MICROCODE: 6,9e,9,0 (F,M,S,R) SIG: 70'00000000 (cache) 70'00000000 (init)

    BLACKBOXBSD: 1 (    !blackboxbsd)


    BLACKBOXPNP: 1 (    !blackboxpnp)


    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

    BUGCHECK_STR: 0x133

    PROCESS_NAME: chrome.exe

    CURRENT_IRQL: d

    ANALYSIS_SESSION_HOST: LAPTOP-64BUOVAT

    ANALYSIS_SESSION_TIME: 12-24-2018 00:33:28.0861

    ANALYSIS_VERSION: 10.0.18303.1000 amd64fre

    LAST_CONTROL_TRANSFER: from fffff801855db19b to fffff801855b00a0

    STACK_TEXT:
    ffffa600`58115bc8 fffff801`855db19b : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff801`85853378 : nt!KeBugCheckEx
    ffffa600`58115bd0 fffff801`854483ba : 00058162`c0e498ac ffffa600`580c0180 00000000`00000282 00000000`00000000 : nt!KeAccumulateTicks+0x19049b
    ffffa600`58115c30 fffff801`85d5c51b : 00058162`c0e47e64 00000000`00000005 00000000`00000000 ffff8209`5db1a200 : nt!KeClockInterruptNotify+0x9da
    ffffa600`58115f40 fffff801`8550da65 : ffff8209`5db1a200 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalpTimerClockIpiRoutine+0x1b
    ffffa600`58115f70 fffff801`855b195a : ffffe90c`43176f90 ffff8209`5db1a200 ffffce4a`c5138408 ffffd406`01fcac10 : nt!KiCallInterruptServiceRoutine+0xa5
    ffffa600`58115fb0 fffff801`855b1e47 : 00000000`00000046 fffff801`855b1ece ffffb680`00000000 ffff8209`5db1a200 : nt!KiInterruptSubDispatchNoLockNoEtw+0xea
    ffffe90c`43176f10 fffff801`854dac2d : fffff801`854753f1 ffffb680`07b1a4f0 00000000`0000000f ffffd406`01fcac08 : nt!KiInterruptDispatchNoLockNoEtw+0x37
    ffffe90c`431770a8 fffff801`854753f1 : ffffb680`07b1a4f0 00000000`0000000f ffffd406`01fcac08 ffffce4a`c5138408 : nt!MiIsPfnInline+0x3d
    ffffe90c`431770b0 fffff801`854b53df : 00000010`00000001 00000000`00000000 00000000`00000001 ffffb680`037914c0 : nt!MiUnlinkStandbyBatch+0xc1
    ffffe90c`43177100 fffff801`854b39cf : 00000000`00000180 00000000`00280000 00000000`00280000 000001f0`83a21040 : nt!MmCheckCachedPageStates+0xf7f
    ffffe90c`431772e0 fffff801`85907a19 : 00000000`00280000 00000000`00000000 00000000`00000001 ffffe90c`431773f0 : nt!CcFetchDataForRead+0x8f
    ffffe90c`43177340 fffff801`854b378e : ffff8209`6a68a630 00000000`00280000 ffff8209`00040000 fffff802`6c4da401 : nt!CcMapAndCopyFromCache+0xd9
    ffffe90c`431773e0 fffff802`6c5bc643 : ffffe90c`43177510 00000000`00000000 ffff820a`0039d746 00000000`0039d746 : nt!CcCopyReadEx+0x12e
    ffffe90c`43177470 fffff802`6b867a4b : 00000000`000002b0 00000000`00000000 ffff820a`54c302a0 000001f0`837a1040 : Ntfs!NtfsCopyReadA+0x273
    ffffe90c`43177730 fffff802`6b865017 : ffffe90c`43177820 ffff820a`54c30200 ffff820a`a062c6f0 ffff820a`a062c5f0 : FLTMGR!FltpPerformFastIoCall+0x10b
    ffffe90c`43177790 fffff802`6b89b7c9 : 00000000`0039d788 000000a8`4c5ff018 ffffe90c`43177a80 00000000`00000001 : FLTMGR!FltpPassThroughFastIo+0xc7
    ffffe90c`431777f0 fffff801`85919c4b : ffff820a`54c302a0 000000a8`4c5ff080 000001f0`00000000 ffff820a`54c302a0 : FLTMGR!FltpFastIoRead+0x159
    ffffe90c`43177890 fffff801`855c0743 : ffffffff`ffffffff 00000000`00000000 00000000`00000000 000000a8`4c5ff0b0 : nt!NtReadFile+0x44b
    ffffe90c`43177990 00007ffb`e504aa64 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    000000a8`4c5feff8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`e504aa64


    THREAD_SHA1_HASH_MOD_FUNC: 4285c86e62a11a69bceacf3b9139d2b40968b228

    THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 8c63ad760229aa48b96ae07e013f14d5058f41f4

    THREAD_SHA1_HASH_MOD: edcac58c6ae3c9db43054fd3856d677b7d934398

    FOLLOWUP_IP:
    nt!KeAccumulateTicks+19049b
    fffff801`855db19b cc int 3

    FAULT_INSTR_CODE: ab3944cc

    SYMBOL_STACK_INDEX: 1

    SYMBOL_NAME: nt!KeAccumulateTicks+19049b

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME:     nt

    IMAGE_NAME: ntkrnlmp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP: 5c0b7468

    STACK_COMMAND: .thread ; .cxr ; kb

    BUCKET_ID_FUNC_OFFSET: 19049b

    FAILURE_BUCKET_ID: 0x133_ISR_nt!KeAccumulateTicks

    BUCKET_ID: 0x133_ISR_nt!KeAccumulateTicks

    PRIMARY_PROBLEM_CLASS: 0x133_ISR_nt!KeAccumulateTicks

    TARGET_TIME: 2018-12-24T02:53:08.000Z

    OSBUILD: 17134

    OSSERVICEPACK: 0

    SERVICEPACK_NUMBER: 0

    OS_REVISION: 0

    SUITE_MASK: 784

    PRODUCT_TYPE: 1

    OSPLATFORM_TYPE: x64

    OSNAME: Windows 10

    OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal

    OS_LOCALE:

    USER_LCID: 0

    OSBUILD_TIMESTAMP: 2018-12-08 00:36:08

    BUILDDATESTAMP_STR: 180410-1804

    BUILDLAB_STR: rs4_release

    BUILDOSVER_STR: 10.0.17134.1.amd64fre.rs4_release.180410-1804

    ANALYSIS_SESSION_ELAPSED_TIME: 12ee

    ANALYSIS_SOURCE: KM

    FAILURE_ID_HASH_STRING: km:0x133_isr_nt!keaccumulateticks

    FAILURE_ID_HASH: {65350307-c3b9-f4b5-8829-4d27e9ff9b06}

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



    :)
     
    Jdiddy480, Dec 24, 2018
    #1
  2. BOBLEVERETH
    BobLevereth Win User

    DPC WATCH DOG VIOLATION

    DPC WATCH DOG VIOLATION STILL DONT KNOW WHAT CAUSES IT
     
    BobLevereth, Dec 24, 2018
    #2
  3. LUKEXM
    lukeXM Win User
    Help! Watch Dog Violation

    I have a problem where my Computer (windows 10) will freeze then the blue screen witll appear with Watch dog violation. anyone how to fix it.... thanks
     
    lukeXM, Dec 24, 2018
    #3
  4. ZALTAR319
    Zaltar319 Win User

    Watch Dog Violation 133

    Zaltar319, Dec 24, 2018
    #4
Thema:

Watch Dog Violation 133

Loading...

  1. Watch Dog Violation 133 - Similar Threads - Watch Dog Violation

  2. DPC Watch Dog Violation

    in Windows 10 Software and Apps
    DPC Watch Dog Violation: Hello,Can anybody help me, sometimes my windows 11 got bsod dpc watch dog violation. Attached my minidump dmp files in zip.Minidump: Minidump.zipThank You. https://answers.microsoft.com/en-us/windows/forum/all/dpc-watch-dog-violation/17d57b4d-fbff-4d44-b5c8-7b93a9d4af8c

  3. DPC Watch Dog violation

    in Windows 10 Gaming
    DPC Watch Dog violation: I have found something interesting firstly have a look at the image it is saying the previous shutdown at 6:43 was unexpected. I was using the pc around that time, and I might have shut it down at this time, but the interesting thing is that I had shut down the pc using the...

  4. DPC Watch Dog violation

    in Windows 10 Software and Apps
    DPC Watch Dog violation: I have found something interesting firstly have a look at the image it is saying the previous shutdown at 6:43 was unexpected. I was using the pc around that time, and I might have shut it down at this time, but the interesting thing is that I had shut down the pc using the...

  5. DPC WATCH DOG VIOLATION

    in Windows 10 Gaming
    DPC WATCH DOG VIOLATION: Hi, Ive been getting more and more bsod of dpc watch dog violation. I have tried reformatting,chkdsk and sfc scannow.minidump link https://answers.microsoft.com/en-us/windows/forum/all/dpc-watch-dog-violation/adfa8cd2-a2c2-4a2c-9792-9b34f786a683

  6. DPC WATCH DOG VIOLATION

    in Windows 10 Software and Apps
    DPC WATCH DOG VIOLATION: Hi, Ive been getting more and more bsod of dpc watch dog violation. I have tried reformatting,chkdsk and sfc scannow.minidump link https://answers.microsoft.com/en-us/windows/forum/all/dpc-watch-dog-violation/adfa8cd2-a2c2-4a2c-9792-9b34f786a683

  7. DPC WATCH DOG VIOLATION

    in Windows 10 BSOD Crashes and Debugging
    DPC WATCH DOG VIOLATION: Hi, Ive been getting more and more bsod of dpc watch dog violation. I have tried reformatting,chkdsk and sfc scannow.minidump link https://answers.microsoft.com/en-us/windows/forum/all/dpc-watch-dog-violation/adfa8cd2-a2c2-4a2c-9792-9b34f786a683

  8. Watch dog violation 0x80000000000000

    in Windows 10 BSOD Crashes and Debugging
    Watch dog violation 0x80000000000000: Hello, These past few weeks ive had Multiple bleu Screen of death , and sometimes on daily basis , and ive searched a bit and found out its a watch dog violation with an error code of 0x80000000000000 so can anyone help please ? Much appreciated and thank you ....

  9. Watch dog violation BSOD

    in Windows 10 BSOD Crashes and Debugging
    Watch dog violation BSOD: https://filebin.net/c1ka0zwu7mw6kicn That's the dump. When I look at it in WhoCrashed it mentions Amdppm.sys being an issue. When I look at it in BlueScreenViewer is mentions atikmdag.sys, NETIO.sys, and ntoskrnl.exe. If anyone could help with this, I'd pay them...

  10. Help! Watch Dog Violation

    in Windows 10 BSOD Crashes and Debugging
    Help! Watch Dog Violation: I have a problem where my Computer (windows 10) will freeze then the blue screen witll appear with Watch dog violation. anyone how to fix it.... thanks...