Windows 10: BSOD Watchdog Violation 0x00000133 on startup (Dump included)

  1.    06 Sep 2016 #1

    BSOD Watchdog Violation 0x00000133 on startup (Dump included)


    Hello,

    since last week I'm getting everyday a BSOD on startup, it only happens once per day.
    The BSOD is called Watchdog Violation, and when I check BlueScreenView,
    I see errors with hal.dll and ntoskml.exe. ( https://i.imgur.com/Rh4V3D7.png )

    After that I used WinDBG to read out the dump file:
    Code:
    Microsoft (R) Windows Debugger Version 10.0.14321.1024 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    
    
    Loading Dump File [C:\Users\jonas\Desktop\090616-8562-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    
    
    
    ************* Symbol Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
    Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 10 Kernel Version 10586 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 10586.545.amd64fre.th2_release.160802-1857
    Machine Name:
    Kernel base = 0xfffff802`98485000 PsLoadedModuleList = 0xfffff802`98762cf0
    Debug session time: Tue Sep  6 11:19:58.604 2016 (UTC + 2:00)
    System Uptime: 3 days 22:47:24.281
    Loading Kernel Symbols
    .
    
    
    Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
    Run !sym noisy before .reload to track down problems loading symbols.
    
    
    ..............................................................
    ................................................................
    ............................................
    Loading User Symbols
    Loading unloaded module list
    ................................................
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    
    Use !analyze -v to get detailed debugging information.
    
    
    BugCheck 133, {1, 1e00, 0, 0}
    
    
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+3302b )
    
    
    Followup:     MachineOwner
    ---------
    
    
    0: 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: 0000000000000000
    Arg4: 0000000000000000
    
    
    Debugging Details:
    ------------------
    
    
    
    
    DUMP_CLASS: 1
    
    
    DUMP_QUALIFIER: 400
    
    
    BUILD_VERSION_STRING:  10.0.10586.545 (th2_release.160802-1857)
    
    
    SYSTEM_MANUFACTURER:                                  
    
    
    SYSTEM_PRODUCT_NAME:                                  
    
    
    SYSTEM_VERSION:                                  
    
    
    BIOS_VENDOR:  Intel Corp.
    
    
    BIOS_VERSION:  BAP6710H.86A.0055.2011.0215.1656
    
    
    BIOS_DATE:  02/15/2011
    
    
    BASEBOARD_MANUFACTURER:  Intel Corporation
    
    
    BASEBOARD_PRODUCT:  DP67BA
    
    
    BASEBOARD_VERSION:  AAG10219-300
    
    
    DUMP_TYPE:  2
    
    
    BUGCHECK_P1: 1
    
    
    BUGCHECK_P2: 1e00
    
    
    BUGCHECK_P3: 0
    
    
    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: 2a
    
    
    CPU_STEPPING: 7
    
    
    CPU_MICROCODE: 6,2a,7,0 (F,M,S,R)  SIG: 29'00000000 (cache) 29'00000000 (init)
    
    
    CUSTOMER_CRASH_COUNT:  1
    
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    
    BUGCHECK_STR:  0x133
    
    
    PROCESS_NAME:  System
    
    
    CURRENT_IRQL:  d
    
    
    ANALYSIS_SESSION_HOST:  DESKTOP-E86G7RJ
    
    
    ANALYSIS_SESSION_TIME:  09-06-2016 16:22:55.0172
    
    
    ANALYSIS_VERSION: 10.0.14321.1024 amd64fre
    
    
    LAST_CONTROL_TRANSFER:  from fffff8029860932b to fffff802985c7940
    
    
    STACK_TEXT:  
    fffff802`9a06cce8 fffff802`9860932b : 00000000`00000133 00000000`00000001 00000000`00001e00 00000000`00000000 : nt!KeBugCheckEx
    fffff802`9a06ccf0 fffff802`9850fc16 : ffffd000`70fc50b0 00000000`00000001 0002634c`023b5d2b fffff802`987a1180 : nt! ?? ::FNODOBFM::`string'+0x3302b
    fffff802`9a06cd80 fffff802`98511e5f : 00000000`00000000 00000000`00000000 fffff802`98769e40 ffffe000`db74d001 : nt!KiUpdateRunTime+0x56
    fffff802`9a06cde0 fffff802`98414a46 : 00000000`00000000 fffff802`987a1180 00000000`00000002 0002634c`03cfdc68 : nt!KeClockInterruptNotify+0x44f
    fffff802`9a06cf40 fffff802`98574207 : fffff802`9845f4d0 ffffd000`70b86450 ffffd000`70fc58c8 fffff802`985c898a : hal!HalpTimerClockInterrupt+0x56
    fffff802`9a06cf70 fffff802`985c8d6a : fffff802`9845f4d0 fffff802`987a1180 00000000`00000000 fffff802`987a7050 : nt!KiCallInterruptServiceRoutine+0x87
    fffff802`9a06cfb0 fffff802`985c9197 : 00000001`ffffffff fffffff6`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xea
    ffffd000`70b863d0 fffff802`98536255 : 00000000`00000000 00000000`00000000 ffff8f34`17b8e590 fffff802`987a1180 : nt!KiInterruptDispatchNoLockNoEtw+0x37
    ffffd000`70b86560 fffff802`98535eca : fffff802`987a1100 00000000`00000000 ffffffff`ffffff00 00000000`00003487 : nt!KiTransitionSchedulingGroupGeneration+0xc5
    ffffd000`70b865d0 fffff802`985589ec : 00000000`014d3f00 fffff802`987a1180 00000000`00000000 00000000`00000000 : nt!KiGroupSchedulingGenerationEnd+0x5a
    ffffd000`70b86610 fffff802`985582b3 : fffff802`987a1100 fffff802`987a1180 00000000`00000000 ffffd000`70b866b8 : nt!KiGroupSchedulingQuantumEnd+0x9c
    ffffd000`70b86680 fffff802`985cc496 : ffffffff`00000001 000001e1`0000000f ffffe000`00000009 00000000`00000286 : nt!KiQuantumEnd+0x233
    ffffd000`70b86770 fffff802`985cae0a : 00000004`ad9bbffe fffff802`985cc9af fffff802`00010027 00000107`257fd976 : nt!KiDispatchInterruptContinue+0x16
    ffffd000`70b867a0 fffff802`98554836 : 00000000`00000000 00000000`00000001 00000000`00000000 fffff802`987592e0 : nt!KiDpcInterrupt+0xca
    ffffd000`70b86930 fffff802`98554299 : fffff802`987a3f28 00000000`00000001 00000000`00000000 ffffd000`70b86ad0 : nt!KiSwapThread+0x186
    ffffd000`70b869e0 fffff802`984b45bf : fffff802`987a6980 ffffe000`00000000 00000000`00000080 00000000`00000000 : nt!KiCommitThreadWait+0x149
    ffffd000`70b86a70 fffff802`985a779c : fffff802`987a1180 00000000`00000080 fffff802`987a3f6e fffff802`987a1180 : nt!KeWaitForGate+0xb7
    ffffd000`70b86ab0 fffff802`984cba45 : 00000000`00000000 ffffe000`db74d040 00000000`00000080 00000000`00000000 : nt!KiExecuteDpc+0x74
    ffffd000`70b86c10 fffff802`985ccae6 : fffff802`987a1180 ffffe000`db74d040 fffff802`984cba04 00000000`00000000 : nt!PspSystemThreadStartup+0x41
    ffffd000`70b86c60 00000000`00000000 : ffffd000`70b87000 ffffd000`70b81000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
    
    
    
    
    STACK_COMMAND:  kb
    
    
    THREAD_SHA1_HASH_MOD_FUNC:  14608360c7abd0410870e1b47ec2a79260b2b515
    
    
    THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  3be4cdc144b3f78111157333789fa91c77ebc13c
    
    
    THREAD_SHA1_HASH_MOD:  81e4fc47ac0211067f7674b1054e6172257f4e35
    
    
    FOLLOWUP_IP: 
    nt! ?? ::FNODOBFM::`string'+3302b
    fffff802`9860932b cc              int     3
    
    
    FAULT_INSTR_CODE:  e92ccdcc
    
    
    SYMBOL_STACK_INDEX:  1
    
    
    SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+3302b
    
    
    FOLLOWUP_NAME:  MachineOwner
    
    
    MODULE_NAME: nt
    
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  57a1b615
    
    
    IMAGE_VERSION:  10.0.10586.545
    
    
    BUCKET_ID_FUNC_OFFSET:  3302b
    
    
    FAILURE_BUCKET_ID:  0x133_ISR_nt!_??_::FNODOBFM::_string_
    
    
    BUCKET_ID:  0x133_ISR_nt!_??_::FNODOBFM::_string_
    
    
    PRIMARY_PROBLEM_CLASS:  0x133_ISR_nt!_??_::FNODOBFM::_string_
    
    
    TARGET_TIME:  2016-09-06T09:19:58.000Z
    
    
    OSBUILD:  10586
    
    
    OSSERVICEPACK:  545
    
    
    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:  2016-08-03 11:15:01
    
    
    BUILDDATESTAMP_STR:  160802-1857
    
    
    BUILDLAB_STR:  th2_release
    
    
    BUILDOSVER_STR:  10.0.10586.545
    
    
    ANALYSIS_SESSION_ELAPSED_TIME: 1119d8
    
    
    ANALYSIS_SOURCE:  KM
    
    
    FAILURE_ID_HASH_STRING:  km:0x133_isr_nt!_??_::fnodobfm::_string_
    
    
    FAILURE_ID_HASH:  {89366ad1-5557-ac2b-d015-8f6ec2fdbf31}
    
    
    Followup:     MachineOwner
    ---------
    I've tried to Google, but didn't really find a solution. People were even talking about a defected hardware, which would suck. :/ Any ideas what I can do?

    Thanks a lot!
    Last edited by NoOtaku; 07 Sep 2016 at 05:19.
      My ComputerSystem Spec


  2. Posts : 5,012
    Windows 10 Pro X64 15063.138
       06 Sep 2016 #2

    Before posting a BSOD thread, please read the instructions here: Blue Screen of Death (BSOD) Posting Instructions
      My ComputersSystem Spec

  3.    07 Sep 2016 #3

    Ztruker said: View Post
    Before posting a BSOD thread, please read the instructions here: Blue Screen of Death (BSOD) Posting Instructions
    Sorry! Added my file.
    Today I didn't had a BSOD, but I did had a laggy start where my mouse was moving slowly for ~20 secs.
      My ComputerSystem Spec


  4. Posts : 5,012
    Windows 10 Pro X64 15063.138
       08 Sep 2016 #4

    Only one dump in the zip file you uploaded. If you are using a hard drive cleaning program like CCleaner, stop using it until this is resolved as it's deleting dumps, or if CCleaner, uncheck Memory Dumps and System log files.
    Attachment 100501

    First thing I noticed is the date of your BIOS is old, 2011 (!sysinfo smbios command). Check the manufacturers web site, see if there is an update available. If yes, install it, see if that helps.

    Also, fill out your System Specs more fully, especially the make and full model number of the computer or system board as msinfo32 is not showing that info.
      My ComputersSystem Spec


 

Related Threads
I have been getting many bsods recently, and the main one is IRQL_NOT_LESS_OR_EQUAL. I don't always get it immediately upon booting up, most of the time its during the playing of a game. I have ran memtest and my results came back within an hour...
BSOD DPC Watchdog Violation Windows 10 64 bit in BSOD Crashes and Debugging
Hello guys. I recently upgraded my Ram from 2 to 4 (2*2) and installed windows 10 64 bit. Before, I hadn't any problem with 2 GB ram and 32 bit windows 10. After a few days later I got this BSOD for 2 times in a week . All drivers have been...
Bsod- dpc_ watchdog violation in BSOD Crashes and Debugging
Hello, My sister seems to be having issues on her laptop with it constantly having to restart and being presented with a blue screen with it saying DPC_ WATCHDOG VIOLATION. I was wondering if anyone could help out with the issue as neither her...
I'd like to start off by saying that I've had this error since I bought this laptop. Should I have returned it as soon as I realized it crashed randomly? Yes. Did I? No, because I was dumb. Anywho, it's almost two years old, and I decided I might...
Hello, I upgraded yesterday and everything looked okay, but today I keep getting bluescreen with watchdog violation error like every 10 minutes. I don't know if it is win10 bug or I messed something up myself -- today I got some kind of malicious...
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 08:35.
Find Us