Windows 10: DPC_WATCHDOG_VIOLATION 133 Error with hashcat.exe

Discus and support DPC_WATCHDOG_VIOLATION 133 Error with hashcat.exe in Windows 10 Customization to solve the problem; Hi everyone, I had next error when using hashcat.exe https://hashcat.net/hashcat/ and My Pc go to reboot, without Blue Screen only reboot Here... Discussion in 'Windows 10 Customization' started by Mobi pill, Feb 27, 2021.

  1. Mobi pill Win User

    DPC_WATCHDOG_VIOLATION 133 Error with hashcat.exe


    Hi everyone, I had next error when using hashcat.exe https://hashcat.net/hashcat/ and My Pc go to reboot, without Blue Screen only reboot
    Here information and url to download of my minidump File:

    ======================

    URL to download minidump file:
    https://dropmefiles.com/Ld7Er

    ======================

    Winver:
    20H2 build 19042.804

    ======================
    PC Hardware Report:


    https://dropmefiles.com/JW3aa

    ======================

    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: fffff8021fefb320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
    additional information regarding the cumulative timeout
    Arg4: 0000000000000000

    Debugging Details:


    KEY_VALUES_STRING: 1

    Key : Analysis.CPU.Sec
    Value: 61

    Key : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on USER-PC

    Key : Analysis.DebugData
    Value: CreateObject

    Key : Analysis.DebugModel
    Value: CreateObject

    Key : Analysis.Elapsed.Sec
    Value: 56

    Key : Analysis.Memory.CommitPeak.Mb
    Value: 289

    Key : Analysis.System
    Value: CreateObject


    BUGCHECK_CODE: 133

    BUGCHECK_P1: 1

    BUGCHECK_P2: 1e00

    BUGCHECK_P3: fffff8021fefb320

    BUGCHECK_P4: 0

    DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

    BLACKBOXNTFS: 1 !blackboxntfs


    BLACKBOXPNP: 1 !blackboxpnp


    BLACKBOXWINLOGON: 1

    CUSTOMER_CRASH_COUNT: 1

    PROCESS_NAME: hashcat.exe

    STACK_TEXT:
    ffff9480`2715ce18 fffff802`1f63ad0c : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff802`1fefb320 : nt!KeBugCheckEx
    ffff9480`2715ce20 fffff802`1f46f9a3 : 00005ca8`5bd0b4c8 ffff9480`271e7180 00000000`00000000 ffff9480`271e7180 : nt!KeAccumulateTicks+0x1c8b0c
    ffff9480`2715ce80 fffff802`1f46f48a : ffffab0b`96ce70e0 ffff900f`63c479f0 fffff802`373b3f00 00000000`00007101 : nt!KeClockInterruptNotify+0x453
    ffff9480`2715cf30 fffff802`1f527ef5 : ffffab0b`96ce70e0 ffff9480`2715cf40 00000000`00000010 ffffe0c6`941ad224 : nt!HalpTimerClockIpiRoutine+0x1a
    ffff9480`2715cf60 fffff802`1f5f752a : ffff900f`63c479f0 ffffab0b`96ce70e0 ffffab0b`970e8da8 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
    ffff9480`2715cfb0 fffff802`1f5f7a97 : 00001fe5`87ded6e0 00001fe5`a5ac3be0 00001fe5`a5ac3be0 00001fe5`ff146ae0 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
    ffff900f`63c47970 fffff802`1f408857 : 00000000`00000000 ffff9480`271ea200 ffff900f`63c47b70 00000000`00000002 : nt!KiInterruptDispatchNoLockNoEtw+0x37
    ffff900f`63c47b00 fffff802`1f40792d : ffff9480`271ea240 ffffab0b`96e42000 ffff900f`63c47e90 ffff9480`00000002 : nt!EtwpLogKernelEvent+0x2a7
    ffff900f`63c47bb0 fffff802`1f406b04 : ffff9480`271e7180 8b48fff1`00000000 00000000`00000008 00000000`0014580d : nt!KiExecuteAllDpcs+0x41d
    ffff900f`63c47d20 fffff802`1f5fcac5 : cccc000d`4646e800 ffff9480`271e7180 ffff9480`28d90dc0 00000000`00000000 : nt!KiRetireDpcList+0x1f4
    ffff900f`63c47fb0 fffff802`1f5fc8b0 : 00000000`0255be40 fffff802`1f4ec5ca ffffe20a`87e65a00 00000000`00df8b50 : nt!KxRetireDpcList+0x5
    ffff900f`656129c0 fffff802`1f5fc165 : 00000000`00000000 fffff802`1f5f75f1 00000000`00000000 00000000`0f209490 : nt!KiDispatchInterruptContinue
    ffff900f`656129f0 fffff802`1f5f75f1 : 00000000`00000000 00000000`0f209490 00000000`00dfe108 00000000`00dfe270 : nt!KiDpcInterruptBypass+0x25
    ffff900f`65612a00 00007ffd`ce5b0241 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatch+0xb1
    00000000`00dfdf30 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`ce5b0241


    SYMBOL_NAME: nt!KeAccumulateTicks+1c8b0c

    MODULE_NAME: nt

    IMAGE_NAME: ntkrnlmp.exe

    IMAGE_VERSION: 10.0.19041.804

    STACK_COMMAND: .thread ; .cxr ; kb

    BUCKET_ID_FUNC_OFFSET: 1c8b0c

    FAILURE_BUCKET_ID: 0x133_ISR_nt!KeAccumulateTicks

    OS_VERSION: 10.0.19041.1

    BUILDLAB_STR: vb_release

    OSPLATFORM_TYPE: x64

    OSNAME: Windows 10

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

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

    2: kd> !analyze -show
    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: fffff8021fefb320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
    additional information regarding the cumulative timeout
    Arg4: 0000000000000000
    2: kd> !blackboxntfs

    NTFS Blackbox Data

    0 Slow I/O Timeout Records Found
    0 Oplock Break Timeout Records Found
    2: kd> lmvm nt
    Browse full module list
    start end module name
    fffff802`1f200000 fffff802`20246000 nt pdb symbols c:\symcache\ntkrnlmp.pdb\5278AFF86C341677D7D7835C85B7B8441\ntkrnlmp.pdb
    Loaded symbol image file: ntkrnlmp.exe
    Mapped memory image file: c:\symcache\ntoskrnl.exe\0D8333E61046000\ntoskrnl.exe
    Image path: ntkrnlmp.exe
    Image name: ntkrnlmp.exe
    Browse all global symbols functions data
    Image was built with /Brepro flag.
    Timestamp: 0D8333E6 This is a reproducible build file hash, not a timestamp
    CheckSum: 00A5938C
    ImageSize: 01046000
    File version: 10.0.19041.804
    Product version: 10.0.19041.804
    File flags: 0 Mask 3F
    File OS: 40004 NT Win32
    File type: 1.0 App
    File date: 00000000.00000000
    Translations: 0409.04b0
    Information from resource tables:
    CompanyName: Microsoft Corporation
    ProductName: Microsoft® Windows® Operating System
    InternalName: ntkrnlmp.exe
    OriginalFilename: ntkrnlmp.exe
    ProductVersion: 10.0.19041.804
    FileVersion: 10.0.19041.804 WinBuild.160101.0800
    FileDescription: NT Kernel & System
    LegalCopyright: © Microsoft Corporation. All rights reserved.

    :)
     
    Mobi pill, Feb 27, 2021
    #1

  2. Hashcat

    Hi,

    Hashcat is a software not developed by Microsoft. To get the best answer to your questions, we suggest contacting Hashcat support.

    Let us know if you need anything else. We're here to help.
     
    Martin Bar, Feb 27, 2021
    #2
  3. Hashcat

    Does Hashcat Function in Windows 10. also can wordlists be stored on external usb drive and used in conjunction with Hashcat for pen testing..

    ***Post moved by the moderator to the appropriate forum category.***
     
    TerryPoynton, Feb 27, 2021
    #3
  4. auggy Win User

    DPC_WATCHDOG_VIOLATION 133 Error with hashcat.exe

    DPC_WATCHDOG_VIOLATION

    The minidump files showed two different errors, a DPC_WATCHDOG_VIOLATION (133) error and a SYSTEM_SERVICE_EXCEPTION (3b) error.

    The DPC_WATCHDOG_VIOLATION may be caused by a wireless driver, the athwnx.sys.

    Which wireless adapter do you have and which driver is installed?

    Also, what ASUS software is installed?
     
    auggy, Feb 27, 2021
    #4
Thema:

DPC_WATCHDOG_VIOLATION 133 Error with hashcat.exe

Loading...
  1. DPC_WATCHDOG_VIOLATION 133 Error with hashcat.exe - Similar Threads - DPC_WATCHDOG_VIOLATION 133 Error

  2. DPC_WATCHDOG_VIOLATION 133

    in Windows 10 Gaming
    DPC_WATCHDOG_VIOLATION 133: Random BSOD a little worried 1: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************DPC_WATCHDOG_VIOLATION 133The DPC watchdog...
  3. DPC_WATCHDOG_VIOLATION 133

    in Windows 10 Gaming
    DPC_WATCHDOG_VIOLATION 133: Hi there,I keep getting the DPC_WATCHDOG_VIOLATION 133. I ran the minidump file through WinDbg, but I don't know how to proceed from there, and I was hoping that someone could help me. I've been trying to fix this for a bit, so I've been going down a list of possible fixes...
  4. DPC_WATCHDOG_VIOLATION 133

    in Windows 10 Software and Apps
    DPC_WATCHDOG_VIOLATION 133: Hi there,I keep getting the DPC_WATCHDOG_VIOLATION 133. I ran the minidump file through WinDbg, but I don't know how to proceed from there, and I was hoping that someone could help me. I've been trying to fix this for a bit, so I've been going down a list of possible fixes...
  5. DPC_WATCHDOG_VIOLATION 133

    in Windows 10 Gaming
    DPC_WATCHDOG_VIOLATION 133: Hi. I keep getting the DPC WATCHDOG VIOLATION and I don't know how to fix it.Crash Dump:21: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis **...
  6. DPC_WATCHDOG_VIOLATION 133

    in Windows 10 Software and Apps
    DPC_WATCHDOG_VIOLATION 133: Hi. I keep getting the DPC WATCHDOG VIOLATION and I don't know how to fix it.Crash Dump:21: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis **...
  7. DPC_WATCHDOG_VIOLATION 133

    in Windows 10 Gaming
    DPC_WATCHDOG_VIOLATION 133: Hi,Rather than the last resort of resetting my PC, I was hoping someone might be able to help me analyse my minidump files. I suspect it's a driver issue, but I'm not sure how to diagnose which one it is.As a bit of background, the computer will crash to restart whenever I...
  8. DPC_WATCHDOG_VIOLATION 133

    in Windows 10 Software and Apps
    DPC_WATCHDOG_VIOLATION 133: Hi,Rather than the last resort of resetting my PC, I was hoping someone might be able to help me analyse my minidump files. I suspect it's a driver issue, but I'm not sure how to diagnose which one it is.As a bit of background, the computer will crash to restart whenever I...
  9. DPC_WATCHDOG_VIOLATION 133

    in Windows 10 BSOD Crashes and Debugging
    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 Debugger Version 10.0.20153.1000 AMD64Copyright c Microsoft Corporation. All rights reserved.Loading Dump File...
  10. 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...