Windows 8 and 8.1 Forums

BSOD DPC watchdog violation

  1. #1

    Posts : 3
    Windows 8

    BSOD DPC watchdog violation

    My computer crashes on startup everytime i start it and then has to restart i get this BSOD everytime

    Any help would be greatly appreciated
    Attached Files
    Last edited by spartan5397; 05 Jan 2013 at 19:23.

      My System SpecsSystem Spec

  2. #2

    Posts : 3
    Windows 8

      My System SpecsSystem Spec

  3. #3

    Posts : 651
    Windows 8.1 x64

    The jraid.sys driver is causing this as it's causing a processor delay in a loop - as per the dump file, a bugcheck with the 0x133 code with the first parameter of 0 should have the offending driver on the stack, the second parameter should be the number of microseconds that the offending DPC has been running for, and the 3rd parameter should be set to the watchdog timeout (DPC timeout/limit) of 282 microseconds:

    // The bugcheck code does make it easy - 1st param is 0, so the second and third should be
    // <some number greater than 282> and 282 - in this case, the second param is indeed a
    // number greater than 282:
    0: kd> .bugcheck
    Bugcheck code 00000133
    Arguments 00000000`00000000 00000000`00000283 00000000`00000282 00000000`00000000
    // While this is a minidump, we can see from the thread stack (read bottom up) that
    // jraid.sys is calling KeStallExecutionProcessor, and the DPC that is being caused here
    // is being caused by the driver on the stack - again, jraid.sys:
    0: kd> kn
     # Child-SP          RetAddr           Call Site
    00 fffff800`0ad7ed88 fffff800`0afeb143 nt!KeBugCheckEx
    01 fffff800`0ad7ed90 fffff800`0aebd011 nt! ?? ::FNODOBFM::`string'+0x13c4c
    02 fffff800`0ad7ee10 fffff800`0aebde97 nt!KeUpdateRunTime+0x51
    03 fffff800`0ad7ee40 fffff800`0b582eca nt!KeUpdateTime+0x3f9
    04 fffff800`0ad7f030 fffff800`0ae8b7ee hal!HalpTimerClockInterrupt+0x86
    05 fffff800`0ad7f060 fffff800`0b58bbe0 nt!KiInterruptDispatchLBControl+0x1ce
    06 fffff800`0ad7f1f8 fffff800`0b57e0e0 hal!HalpTscQueryCounter
    07 fffff800`0ad7f200 fffff880`012036d1 hal!HalpTimerStallExecutionProcessor+0x131
    08 fffff800`0ad7f290 00000000`00000000 jraid+0x36d1
    0: kd> lmvm jraid
    start             end                 module name
    fffff880`01200000 fffff880`0121e000   jraid    T (no symbols)           
        Loaded symbol image file: jraid.sys
        Image path: \SystemRoot\System32\drivers\jraid.sys
        Image name: jraid.sys
        Timestamp:        Thu Aug 13 04:10:27 2009 (4A83CA73)
        CheckSum:         00026B2F
        ImageSize:        0001E000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    I cannot tell you how long the driver is using as it's default to call KeStallExecutionProcessor, as this is a minidump so none of the register or PCR data is there to disassemble this, but suffice to say this is actually pretty common behavior for these bugchecks. You'll need to work with the driver vendor (this is a JMicron JMB36x SATA controller, it looks like) of the device if a newer version of the driver (it looks like potentially there are 10 versions newer than the one you're running from August 2009) doesn't resolve the issue. Ultimately, it's not a problem you can "fix" short of the driver spending less time running whatever routine it's running that it thus needs to stall the processor for (and thus extending the DPC that exceeds the timeout).

    While this probably doesn't matter to you specifically, Microsoft's documentation on how to write a RAID driver for Windows tells driver makers not to stall the processor this way for more than 100 microseconds:
    The WDK documentation states that the StorPortStallExecution() or ScsiPortStallExection() routines should be called to stall the process for less than 1 millisecond. However, best practice dictates that these routines—which call KeStallExecutionProcessor()—not be used for delays greater than 100 microseconds. For an example, see the white paper Device-Driver Performance Considerations for Multimedia Platforms.
    However, frequently miniport drivers call the KeStallExecutionProcessor function in a loop to stall the execution for several seconds—or minutes in some cases. This delay causes the Windows DPC watchdog timer to be evoked when running with an attached debugger.
      My System SpecsSystem Spec

  4. #4

    Posts : 3
    Windows 8

    Thank you soo much you are a lifesaver i updated it and it works perfectly so far
      My System SpecsSystem Spec

  5. #5

    Tropical Island Pair a Dice
    Posts : 3,030
    Windows 8.1 Pro x64/ Windows 7 Ult x64

    Thanks for letting us know the results.

    You can mark this thread 'Solved' it may help others with a similar issue.
      My System SpecsSystem Spec

BSOD DPC watchdog violation

Similar Threads
Thread Forum
BSOD DPC Watchdog Violation
My English is not very good. The computer to worked wonderfully. I recently had a problem with internet connection, which you uninstall the Driver TP-LINK WN721N, installing the latest driver I could find. After this, they have been showing blue screen while using MOBA or even applications...
BSOD Crashes and Debugging
BSOD. DPC Watchdog Violation !
Hey. The past 4 days i was having a lot of problem with my laptop!!. First BSOD was Bad Pool Header and i fix it today by change the HDD but today i got another BSOD and this time it's DPC Watchdog Violation ! I don't know how to fix it !!. It's came to me every time i try to download a...
BSOD Crashes and Debugging
BSOD DPC watchdog violation
hello there, ive upgraded from win7 to win 8 , and im having the same problem that the above dude is having, every while the BSOD appeares with eror DPC_WATCHDOG VILOLATION. Between, my laptop is a hp pavilion dv6 10404 i7 720 quad 1.6 6GB Ram ATI mobility HD 5650 VGA
BSOD Crashes and Debugging
DPC Watchdog Violation BSOD need help :(
Hello ! , I've just changed few components in my PC , re installed Windows and I'm getting this BSOD , can't figure out what it is , sometimes my PC will restart 4-5 times in the row before i can get few hours of use from it. I changed only my CPU and Motherboard all the rest is the same and I've...
BSOD Crashes and Debugging
BSOD Dpc Watchdog violation
Hi! I have a Problem with my Lenovo X220T Notebook that I have updated to W8 a few days ago. I also upgradet to Adata S511 SSD and 16GB Ram. Specialy when I sent the Notebook to sleep, after waking up I have a BSOD. Sometimes also during normal Operation. Maybe someone can help me? Would be...
BSOD Crashes and Debugging
BSOD DPC watchdog violation
Hey there! It's the first time I got this blue screen, I don't know if it'll happen again. I searched for it on google and I didn't understand very well why it is caused. Anyway, I haven't updated my drivers yet, could it be the problem? thanks in advance! :)
BSOD Crashes and Debugging

Eight Forums Android App Eight Forums IOS App Follow us on Facebook