Windows 10: Windows 10 BSOD Watchdog_Violation Code 133

Discus and support Windows 10 BSOD Watchdog_Violation Code 133 in Windows 10 BSOD Crashes and Debugging to solve the problem; Since updating to Windows 10 2004 and continued now with update 20H2 I have been getting Watchdog violation error BSOD specifically when using a... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by Ymiru, Oct 27, 2020.

  1. Ymiru Win User

    Windows 10 BSOD Watchdog_Violation Code 133


    Since updating to Windows 10 2004 and continued now with update 20H2 I have been getting Watchdog violation error BSOD

    specifically when using a browser for a short period of time no other process can recreate the BSOD.

    I'm not tech savvy but from my understanding the issue in the minidump file states something is a rye with NEITO.SYS

    though I get conflicting answers from other sources saying NEITO.SYS is related to a WIFI driver and must be updated

    though I have obtained the latest Update and have checked manufacturer drivers and devices.

    All hardware is working according to my computer and Ive exhausted all my attempts to fix and understand where the issue

    is arising from. Any assitance is appriciated and I can provide further details upon request.

    Minidump file:

    15: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************DPC_WATCHDOG_VIOLATION 133The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVELor 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: fffff80473afb320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains additional information regarding the cumulative timeoutArg4: 0000000000000000Debugging 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 Key : Analysis.CPU.mSec Value: 5280 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on LAPTOP-GBTE7N84 Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.mSec Value: 8007 Key : Analysis.Memory.CommitPeak.Mb Value: 95 Key : Analysis.System Value: CreateObject Key : WER.OS.Branch Value: vb_release Key : WER.OS.Timestamp Value: 2019-12-06T14:06:00Z Key : WER.OS.Version Value: 10.0.19041.1ADDITIONAL_XML: 1OS_BUILD_LAYERS: 1BUGCHECK_CODE: 133BUGCHECK_P1: 1BUGCHECK_P2: 1e00BUGCHECK_P3: fffff80473afb320BUGCHECK_P4: 0DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDEDTRAP_FRAME: ffffdf859cb0db20 -- .trap 0xffffdf859cb0db20NOTE: The trap frame does not contain all registers.Some register values may be zeroed or incorrect.rax=00000000dd5392a6 rbx=0000000000000000 rcx=ffffdf859cb0dd10rdx=ffffdf859cb0edf8 rsi=0000000000000000 rdi=0000000000000000rip=fffff804730bee17 rsp=ffffdf859cb0dcb0 rbp=ffffdf859cb0de40 r8=0000000000000008 r9=0000000000000000 r10=0000000000000002r11=ffffdf859cb0df88 r12=0000000000000000 r13=0000000000000000r14=0000000000000000 r15=0000000000000000iopl=0 nv up ei ng nz na po ncnt!KeYieldProcessorEx+0x17:fffff804`730bee17 4883c420 add rsp,20hResetting default scopeCUSTOMER_CRASH_COUNT: 1PROCESS_NAME: chrome.exeSTACK_TEXT: ffffce01`1a0f1e18 fffff804`73287a98 : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff804`73afb320 : nt!KeBugCheckExffffce01`1a0f1e20 fffff804`73126993 : 00000494`81c5ae22 ffffce01`1a0d8180 00000000`00000000 ffffce01`1a0d8180 : nt!KeAccumulateTicks+0x15dda8ffffce01`1a0f1e80 fffff804`7312647a : ffffe486`daef41c0 ffffdf85`9cb0dba0 00000000`00000000 ffffe486`ff4cfe60 : nt!KeClockInterruptNotify+0x453ffffce01`1a0f1f30 fffff804`7302ecd5 : ffffe486`daef41c0 00000000`00000000 00000000`00000000 ffff4d68`156f0fbd : nt!HalpTimerClockIpiRoutine+0x1affffce01`1a0f1f60 fffff804`731f604a : ffffdf85`9cb0dba0 ffffe486`daef41c0 00000000`00000000 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5ffffce01`1a0f1fb0 fffff804`731f65b7 : ffffdf85`9cb0dd10 ffffdf85`9cb0dde0 00000000`00000046 fffff804`731f663f : nt!KiInterruptSubDispatchNoLockNoEtw+0xfaffffdf85`9cb0db20 fffff804`730bee17 : 00000000`00000010 00000000`00040202 ffffdf85`9cb0dcd8 00000000`00000018 : nt!KiInterruptDispatchNoLockNoEtw+0x37ffffdf85`9cb0dcb0 fffff804`7310bd1a : 00000000`00000000 00000000`00000080 ffffdf85`9cb0dd28 ffffe486`f7fea180 : nt!KeYieldProcessorEx+0x17ffffdf85`9cb0dce0 fffff804`7310bcdf : 00000000`dd5392a6 ffff9b0b`59dd8200 00000000`000001c5 ffffdf85`9cb0de9b : nt!KxWaitForLockOwnerShip+0x2affffdf85`9cb0dd10 fffff804`790ddd64 : 00000000`00000000 fffff804`774b129b ffff9b0b`59dd8278 fffff804`78a03355 : nt!KeAcquireInStackQueuedSpinLock+0x7fffffdf85`9cb0dd40 fffff804`7916b367 : 000004f5`00000405 01000000`00100000 ffffe486`ff4cfb90 fffff804`79056fbb : tcpip!UdpSetDestinationEndpoint+0x94ffffdf85`9cb0df10 fffff804`79181794 : 00000000`00000405 01000000`00100000 ffffe486`fa221c70 fffff804`79181863 : tcpip!UDPConnectRedirectCallback+0x27ffffdf85`9cb0df40 fffff804`78fbe248 : ffffe487`09d77200 ffffdf85`9cb0e310 ffffe486`e0bef800 ffffe486`e0bef800 : tcpip!AlepReleaseConnectRequestInspectContext+0x54ffffdf85`9cb0df90 fffff804`78fbf69c : ffffdf85`9cb0e310 ffffe486`fa221c70 ffffe486`fa221c70 ffffdf85`9cb0e1b0 : NETIO!ClassifyContextCleanupRoutine+0x98ffffdf85`9cb0dfd0 fffff804`78fbf3cc : 00000000`00000405 fffff804`00000000 0c9cc933`28cc0b15 000004f5`00000405 : NETIO!WfpObjectDereference+0x20ffffdf85`9cb0e000 fffff804`793579e5 : 00000000`00000405 ffffdf85`9cb0e1b0 fffff804`d51a9100 ffffe487`0bda5820 : NETIO!FeReleaseClassifyHandle+0x6cffffdf85`9cb0e030 fffff804`8fd2005c : ffffe487`0c5d56f0 fffff804`d51ace02 ffffe487`0c5d5660 fffff804`8fd12199 : fwpkclnt!FwpsReleaseClassifyHandle0+0x15ffffdf85`9cb0e060 ffffe487`0c5d56f0 : fffff804`d51ace02 ffffe487`0c5d5660 fffff804`8fd12199 00000000`00000000 : gnf+0x1005cffffdf85`9cb0e068 fffff804`d51ace02 : ffffe487`0c5d5660 fffff804`8fd12199 00000000`00000000 ffffe487`0c5d59c8 : 0xffffe487`0c5d56f0ffffdf85`9cb0e070 ffffe487`0c5d5660 : fffff804`8fd12199 00000000`00000000 ffffe487`0c5d59c8 ffffdf85`9cb0e802 : mwac+0x1ce02ffffdf85`9cb0e078 fffff804`8fd12199 : 00000000`00000000 ffffe487`0c5d59c8 ffffdf85`9cb0e802 00000000`00000000 : 0xffffe487`0c5d5660ffffdf85`9cb0e080 00000000`00000000 : ffffe487`0c5d59c8 ffffdf85`9cb0e802 00000000`00000000 ffffe486`e0edb910 : gnf+0x2199SYMBOL_NAME: NETIO!ClassifyContextCleanupRoutine+98MODULE_NAME: NETIOIMAGE_NAME: NETIO.SYSIMAGE_VERSION: 10.0.19041.546STACK_COMMAND: .thread ; .cxr ; kbBUCKET_ID_FUNC_OFFSET: 98FAILURE_BUCKET_ID: 0x133_ISR_NETIO!ClassifyContextCleanupRoutineOS_VERSION: 10.0.19041.1BUILDLAB_STR: vb_releaseOSPLATFORM_TYPE: x64OSNAME: Windows 10FAILURE_ID_HASH: {c1e2a4dd-6594-caa1-e7b1-1d26c6a01cfc}Followup: MachineOwner---------

    :)
     
    Ymiru, Oct 27, 2020
    #1
  2. eidairaman1, Oct 27, 2020
    #2
  3. Ahhzz Win User
    Windows 10 Tweaks

    Pressing “Windows+Pause Break” (it’s up there next to scroll lock) opens the “System” Window.

    Windows 10: In the new version of Windows, Explorer has a section called Quick Access. This includes your frequent folders and recent files. Explorer defaults to opening this page when you open a new window. If you’d rather open the usual This PC, with links to your drives and library folders, follow these steps:

    • Open a new Explorer window.
    • Click View in the ribbon.
    • Click Options.
    • Under General, next to “Open File Explorer to:” choose “This PC.”
    • Click OK


    credit to Lifehacker.
     
    Ahhzz, Oct 27, 2020
    #3
  4. Ksanz Win User

    Windows 10 BSOD Watchdog_Violation Code 133

    Windows 10 BSOD with the Watchdog_Violation Code problem.

    Two months ago, I bought me a PC Medion Akoya P66064 tower. It has the following specs:

    +NVIDIA GeForce GTX 1050 Ti

    with 4 GB of graphic memory

    +256 GB PCle SSD

    +8 GB Memory

    +1 TB Hard disk

    A week after I bought it, I started getting the BSOD while I was playing a game on Steam with the Watchdog_Violation Code.

    I've updated my graphic card and a ran many scans. I also thought that maybe the memory was faulty but it wasn't that either. In some occasion my PC would be working fine and the next day, it can crash two or three times. This is not only limited to gaming
    but also when I use the internet or work. I checked the dumpfile and this was the result:

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

    Dump File : 041220-8359-01.dmp

    Crash Time : 12/04/2020 23:49:07

    Bug Check String :

    Bug Check Code : 0x00000133

    Parameter 1 : 00000000`00000000

    Parameter 2 : 00000000`00000501

    Parameter 3 : 00000000`00000500

    Parameter 4 : fffff800`5a973358

    Caused By Driver : hal.dll

    Caused By Address : hal.dll+18f8

    File Description :

    Product Name :

    Company :

    File Version :

    Processor : x64

    Crash Address : ntoskrnl.exe+1c2360

    Stack Address 1 :

    Stack Address 2 :

    Stack Address 3 :

    Computer Name :

    Full Path : C:\WINDOWS\Minidump\041220-8359-01.dmp

    Processors Count : 6

    Major Version : 15

    Minor Version : 18362

    Dump File Size : 2,625,732

    Dump File Time : 12/04/2020 23:49:47

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

    I have a hunch that it could a hardware problem. Thanks in advance.
     
    Ksanz, Oct 27, 2020
    #4
Thema:

Windows 10 BSOD Watchdog_Violation Code 133

Loading...
  1. Windows 10 BSOD Watchdog_Violation Code 133 - Similar Threads - BSOD Watchdog_Violation Code

  2. BSOD with Windows Error code 133 & 124

    in Windows 10 Gaming
    BSOD with Windows Error code 133 & 124: Hello All,I've been trying to troubleshoot BSOD with Windows Error code 133 & 124. Should I reinstall the program that cause the BSOD or reinstall the driver usbvideo.sys itself? Moreover, is there a way I can install the driver offline? The computer can't be connect to the...
  3. BSOD with Windows Error code 133 & 124

    in Windows 10 Software and Apps
    BSOD with Windows Error code 133 & 124: Hello All,I've been trying to troubleshoot BSOD with Windows Error code 133 & 124. Should I reinstall the program that cause the BSOD or reinstall the driver usbvideo.sys itself? Moreover, is there a way I can install the driver offline? The computer can't be connect to the...
  4. BSOD with Windows Error code 133 & 124

    in Windows 10 BSOD Crashes and Debugging
    BSOD with Windows Error code 133 & 124: Hello All,I've been trying to troubleshoot BSOD with Windows Error code 133 & 124. Should I reinstall the program that cause the BSOD or reinstall the driver usbvideo.sys itself? Moreover, is there a way I can install the driver offline? The computer can't be connect to the...
  5. BSOD with code: 133

    in Windows 10 Gaming
    BSOD with code: 133: Hello,PC specifications:32gb RAM1tb nvme windows drive has other software and 2 games on it500gb ssd for game storage2tb hdd for media storageMotherboard: Asus Prime x570-ProRyzen 9 3900xtAsus Tuf 3070I got a BSOD with code 133. I have the minidump file to provide.I was...
  6. BSOD - irql_not_less_or_equal//watchdog_violation

    in Windows 10 Ask Insider
    BSOD - irql_not_less_or_equal//watchdog_violation: Hello, I recently built a gaming pc, but since doing so I have had a plethora of different BSOD. This is my most recent. They only seem to happen when I'm on my desktop or just browsing the internet. They never really happen when I'm in games. I'm not sure if that helps. I've...
  7. BSOD - error codes 109, a, 133, 133, 133

    in Windows 10 BSOD Crashes and Debugging
    BSOD - error codes 109, a, 133, 133, 133: I have a new gaming pc just got delivered and it's BSOD 5 times. specs: Device name DESKTOP-3RG8SD0 Processor IntelR CoreTM i9-10900K CPU @ 3.70GHz 3.70 GHz Installed RAM 16.0 GB 15.9 GB usable GPU : Nvidia 3070 System type 64-bit operating system, x64-based...
  8. Windows 10 BSOD Watchdog_Violation Code

    in Windows 10 BSOD Crashes and Debugging
    Windows 10 BSOD Watchdog_Violation Code: I was using my laptop, just browsing the internet, nothing too heavy. And it suddenly completely froze and I got the BSOD. BlueScreenView says it's caused by hal.dll and ntoskrnl.exe. My laptop specs: processor: IntelR Core i7-4720HQ CPU @ 2.60GHZ RAM: 8 GB Crucial MX300...
  9. Windows 10 BSOD with the Watchdog_Violation Code problem.

    in Windows 10 Gaming
    Windows 10 BSOD with the Watchdog_Violation Code problem.: Two months ago, I bought me a PC Medion Akoya P66064 tower. It has the following specs: +NVIDIA GeForce GTX 1050 Ti with 4 GB of graphic memory +256 GB PCle SSD +8 GB Memory +1 TB Hard disk A week after I bought it, I started getting the BSOD while I was playing a...
  10. BSOD DPC-WATCHDOG_VIOLATION

    in Windows 10 Installation and Upgrade
    BSOD DPC-WATCHDOG_VIOLATION: The computer has rebooted from a bugcheck. The bugcheck was: 0x00000133 (0x0000000000000001, 0x0000000000001e00, 0xfffff800c7ef7378, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 07e8987e-bdbe-4ca9-8de0-d3e6cef33d26. I'm receiving this error...