Windows 10: DPC_WATCHDOG_VIOLATION 2020

Discus and support DPC_WATCHDOG_VIOLATION 2020 in Windows 10 Installation and Upgrade to solve the problem; From 2 days and i have that BSOD here is the dump file: Microsoft R Windows Debugger Version 10.0.18362.1 AMD64 Copyright c Microsoft Corporation.... Discussion in 'Windows 10 Installation and Upgrade' started by Rectos VX, Apr 12, 2020.

  1. RECTOS VX
    Rectos VX Win User

    DPC_WATCHDOG_VIOLATION 2020


    From 2 days and i have that BSOD here is the dump file:



    Microsoft R Windows Debugger Version 10.0.18362.1 AMD64

    Copyright c Microsoft Corporation. All rights reserved.





    Loading Dump File [C:\Windows\minidump\041320-6468-01.dmp]

    Mini Kernel Dump File: Only registers and stack trace are available





    ************* Path validation summary **************

    Response Time ms Location

    Deferred SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols

    Symbol search path is: SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols

    Executable search path is:

    Windows 10 Kernel Version 18362 MP 12 procs Free x64

    Product: WinNt, suite: TerminalServer SingleUserTS Personal

    Built by: 18362.1.amd64fre.19h1_release.190318-1202

    Machine Name:

    Kernel base = 0xfffff805`12200000 PsLoadedModuleList = 0xfffff805`12648170

    Debug session time: Mon Apr 13 00:08:45.170 2020 UTC + 4:00

    System Uptime: 0 days 11:58:56.299

    Loading Kernel Symbols

    ...............................................................

    ................................................................

    ................................................................

    ..............

    Loading User Symbols

    Loading unloaded module list

    ................

    For analysis of this file, run !analyze -v

    10: 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: fffff80512773358, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains

    additional information regarding the cumulative timeout

    Arg4: 0000000000000000



    Debugging Details:

    ------------------



    *** WARNING: Unable to verify timestamp for Netwtw08.sys

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

    *** ***

    *** ***

    *** 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: 18362.1.amd64fre.19h1_release.190318-1202



    SYSTEM_MANUFACTURER: ASUSTeK COMPUTER INC.



    SYSTEM_PRODUCT_NAME: Strix GL504GS_GL504GS



    SYSTEM_VERSION: 1.0



    BIOS_VENDOR: American Megatrends Inc.



    BIOS_VERSION: GL504GS.308



    BIOS_DATE: 03/13/2020



    BASEBOARD_MANUFACTURER: ASUSTeK COMPUTER INC.



    BASEBOARD_PRODUCT: GL504GS



    BASEBOARD_VERSION: 1.0



    DUMP_TYPE: 2



    BUGCHECK_P1: 1



    BUGCHECK_P2: 1e00



    BUGCHECK_P3: fffff80512773358



    BUGCHECK_P4: 0



    DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED



    CPU_COUNT: c



    CPU_MHZ: 8a0



    CPU_VENDOR: GenuineIntel



    CPU_FAMILY: 6



    CPU_MODEL: 9e



    CPU_STEPPING: a



    CPU_MICROCODE: 6,9e,a,0 F,M,S,R SIG: 96'00000000 cache 96'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: RECTOS



    ANALYSIS_SESSION_TIME: 04-13-2020 00:24:47.0867



    ANALYSIS_VERSION: 10.0.18362.1 amd64fre



    LAST_CONTROL_TRANSFER: from fffff8051243d8b1 to fffff805123c2360



    STACK_TEXT:

    ffffe080`479f5b08 fffff805`1243d8b1 : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff805`12773358 : nt!KeBugCheckEx

    ffffe080`479f5b10 fffff805`122b90a7 : 00002d0e`73176f6b ffffe080`479d6180 00000000`00000286 fffff905`11e14f80 : nt!KeAccumulateTicks+0x181641

    ffffe080`479f5b70 fffff805`12cba291 : 00000000`00000165 ffffbe86`3deeb700 fffff905`11e15000 ffffbe86`3deeb7b0 : nt!KeClockInterruptNotify+0xc07

    ffffe080`479f5f30 fffff805`1222cc75 : ffffbe86`3deeb700 fffff805`12269347 00000000`00000000 00000000`00000000 : hal!HalpTimerClockIpiRoutine+0x21

    ffffe080`479f5f60 fffff805`123c3dea : fffff905`11e15000 ffffbe86`3deeb700 ffffbe86`41bc0598 ffffbe86`3deeb700 : nt!KiCallInterruptServiceRoutine+0xa5

    ffffe080`479f5fb0 fffff805`123c4357 : 00000000`96d4c3b3 fffff905`11e15000 ffffbe86`3deeb700 00000000`00000005 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa

    fffff905`11e14f80 fffff805`122a1460 : 00000000`00000f00 00000000`00000000 00000000`0000000c fffff805`2c201300 : nt!KiInterruptDispatchNoLockNoEtw+0x37

    fffff905`11e15110 fffff805`122a1047 : ffffbe86`44759348 ffffe080`479d6180 00000000`0000000c 00000000`00000008 : nt!KxWaitForSpinLockAndAcquire+0x30

    fffff905`11e15140 fffff805`2c045e53 : fffff905`11e153c0 ffffbe86`44759240 ffffbe86`448a8000 00001d00`00000000 : nt!KeAcquireSpinLockRaiseToDpc+0x87

    fffff905`11e15170 fffff905`11e153c0 : ffffbe86`44759240 ffffbe86`448a8000 00001d00`00000000 00000000`00000005 : Netwtw08+0x165e53

    fffff905`11e15178 ffffbe86`44759240 : ffffbe86`448a8000 00001d00`00000000 00000000`00000005 0000008c`00000001 : 0xfffff905`11e153c0

    fffff905`11e15180 ffffbe86`448a8000 : 00001d00`00000000 00000000`00000005 0000008c`00000001 ffffbe86`446f8d30 : 0xffffbe86`44759240

    fffff905`11e15188 00001d00`00000000 : 00000000`00000005 0000008c`00000001 ffffbe86`446f8d30 fffff805`2c045a83 : 0xffffbe86`448a8000

    fffff905`11e15190 00000000`00000005 : 0000008c`00000001 ffffbe86`446f8d30 fffff805`2c045a83 00000000`00000000 : 0x00001d00`00000000

    fffff905`11e15198 0000008c`00000001 : ffffbe86`446f8d30 fffff805`2c045a83 00000000`00000000 00000000`00000000 : 0x5

    fffff905`11e151a0 ffffbe86`446f8d30 : fffff805`2c045a83 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0000008c`00000001

    fffff905`11e151a8 fffff805`2c045a83 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffffbe86`446f8d30

    fffff905`11e151b0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : Netwtw08+0x165a83





    THREAD_SHA1_HASH_MOD_FUNC: 7227ffc29797e38d40cf865b02a49c98231d5174



    THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 688ea95665f97ab168af460cb3fc560980c6312c



    THREAD_SHA1_HASH_MOD: 0f07afe34553737c3c86fd22e42e49acecb63242



    FOLLOWUP_IP:

    Netwtw08+165e53

    fffff805`2c045e53 888310010000 mov byte ptr [rbx+110h],al



    FAULT_INSTR_CODE: 1108388



    SYMBOL_STACK_INDEX: 9



    SYMBOL_NAME: Netwtw08+165e53



    FOLLOWUP_NAME: MachineOwner



    MODULE_NAME: Netwtw08



    IMAGE_NAME: Netwtw08.sys



    DEBUG_FLR_IMAGE_TIMESTAMP: 5bfe73ea



    STACK_COMMAND: .thread ; .cxr ; kb



    BUCKET_ID_FUNC_OFFSET: 165e53



    FAILURE_BUCKET_ID: 0x133_ISR_Netwtw08!unknown_function



    BUCKET_ID: 0x133_ISR_Netwtw08!unknown_function



    PRIMARY_PROBLEM_CLASS: 0x133_ISR_Netwtw08!unknown_function



    TARGET_TIME: 2020-04-12T20:08:45.000Z



    OSBUILD: 18362



    OSSERVICEPACK: 752



    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: unknown_date



    BUILDDATESTAMP_STR: 190318-1202



    BUILDLAB_STR: 19h1_release



    BUILDOSVER_STR: 10.0.18362.1.amd64fre.19h1_release.190318-1202



    ANALYSIS_SESSION_ELAPSED_TIME: 17e57



    ANALYSIS_SOURCE: KM



    FAILURE_ID_HASH_STRING: km:0x133_isr_netwtw08!unknown_function



    FAILURE_ID_HASH: {e75ae9b2-3d64-925d-b718-dfe007edea58}



    Followup: MachineOwner

    ---------

    :)
     
    Rectos VX, Apr 12, 2020
    #1
  2. ROSE CAL
    Rose Cal Win User

    DPC_WATCHDOG_VIOLATION

    Hi,

    It is possible that the error DPC_WATCHDOG_VIOLATION may occur if the iastor.sys driver is incompatible with Windows 10. To isolate your issue, we'd like to gather more information:

    • Have you made any recent changes before this issue occurred?
    • What troubleshooting steps have you done so far?

    Any response will be highly appreciated.
     
    Rose Cal, Apr 12, 2020
    #2
  3. HAIRINWIND
    hairinwind Win User
    Blue screen: DPC_WATCHDOG_VIOLATION

    After a recent updating, my machine has blue screen every 5 - 10 minutes.

    The error code is DPC_WATCHDOG_VIOLATION

    I saw another post here which suggest to use "iastor.sys". But I don't have that in the driver list. Mine is storahci.sys.

    Please advise! Thanks,
     
    hairinwind, Apr 12, 2020
    #3
  4. MARQUE LOR
    Marque Lor Win User

    DPC_WATCHDOG_VIOLATION 2020

    DPC_WATCHDOG_VIOLATION

    Hi Mattie,

    The DPC_WATCHDOG_VIOLATION blue screen error can be caused by a variety of hardware, firmware, driver, or software issues. Now, you mentioned that you already changed the IDE ATA/ATAPI controllers to standard. Did you update the driver as well? And also,
    are you getting the same blue screen error when you play other games? Or is it only occurring when you play a particular game?

    For the mean time, if you haven't tried any further troubleshooting steps, we suggest that you perform the suggested steps from this article:

    Troubleshoot blue screen errors    .

    Let us know how this turns out for you.
     
    Marque Lor, Apr 12, 2020
    #4
Thema:

DPC_WATCHDOG_VIOLATION 2020

Loading...

  1. DPC_WATCHDOG_VIOLATION 2020 - Similar Threads - DPC_WATCHDOG_VIOLATION 2020

  2. DPC_Watchdog_violation crashing

    in Windows 10 Gaming
    DPC_Watchdog_violation crashing: Hi there,I have a gaming laptop that keeps continuously crashing due to the violation mentioned above and I’m not sure why. Afterwards, my laptop would not recognize my GPU. Please help....

  3. DPC_Watchdog_violation crashing

    in Windows 10 Software and Apps
    DPC_Watchdog_violation crashing: Hi there,I have a gaming laptop that keeps continuously crashing due to the violation mentioned above and I’m not sure why. Afterwards, my laptop would not recognize my GPU. Please help....

  4. DPC_Watchdog_violation crashing

    in Windows 10 BSOD Crashes and Debugging
    DPC_Watchdog_violation crashing: Hi there,I have a gaming laptop that keeps continuously crashing due to the violation mentioned above and I’m not sure why. Afterwards, my laptop would not recognize my GPU. Please help....

  5. HELP with DPC_WATCHDOG_VIOLATION

    in Windows 10 Gaming
    HELP with DPC_WATCHDOG_VIOLATION: For 3 days now i cant seem to figure out why my computer is blue screening, the error i get is DPC_Watchdog_Violation, ive tried multiple ways to fix it but nothing seems to work, does anyone know a fix?here is a link to the minidumps: minidumps mediafire.com...

  6. HELP with DPC_WATCHDOG_VIOLATION

    in Windows 10 Software and Apps
    HELP with DPC_WATCHDOG_VIOLATION: For 3 days now i cant seem to figure out why my computer is blue screening, the error i get is DPC_Watchdog_Violation, ive tried multiple ways to fix it but nothing seems to work, does anyone know a fix?here is a link to the minidumps: minidumps mediafire.com...

  7. DPC_WATCHDOG_VIOLATION

    in Windows 10 Gaming
    DPC_WATCHDOG_VIOLATION: DPC_WATCHDOG_VIOLATIONHello, I have been getting this error at random lately. I have a feeling it might be a driver after seeing some other threads in the community. I have no experience with this or looking at the DMP files. Here is a link the files: MP Files.zipThe PC...

  8. DPC_WATCHDOG_VIOLATION

    in Windows 10 Software and Apps
    DPC_WATCHDOG_VIOLATION: DPC_WATCHDOG_VIOLATIONHello, I have been getting this error at random lately. I have a feeling it might be a driver after seeing some other threads in the community. I have no experience with this or looking at the DMP files. Here is a link the files: MP Files.zipThe PC...

  9. DPC_WATCHDOG_VIOLATION

    in Windows 10 Software and Apps
    DPC_WATCHDOG_VIOLATION: My PC keeps crashing because of a dpc_watchdog_violation. I really don't know what could be the cause it just started today. https://answers.microsoft.com/en-us/windows/forum/all/dpcwatchdogviolation/f85a6aa1-5dea-4bb7-ae42-63c70bb3211d

  10. Repeated DPC_WATCHDOG_VIOLATION September 2020 - Blue Screen of Death on Window 10

    in Windows 10 BSOD Crashes and Debugging
    Repeated DPC_WATCHDOG_VIOLATION September 2020 - Blue Screen of Death on Window 10: Hi all, Currently stumped with this BSOD issue, any help would be much appreciated. Issue: I've been having issues in the last month with BSODs, all with the same stop code: "DPC_WATCHDOG_VIOLATION". Almost always, this blue screen does not restart, and freezes at 100%,...
  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: