none
Windows 8.1 pro 64 bluescreen: DPC_WATCHDOG_VIOLATION

    Question

  • I just updated 8 to 8.1. And this problem occur, when I'm playing game,  using 3dsmax, using chrome, even doing nothing. After searched on the internet, I've checked disk, memory, and drivers. Nothing I could find to solve the problem. Even I have reinstalled OS, but the problem still.

    Here is the bugcheck analysis, but I don't how/what to do with this.

    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    DPC_WATCHDOG_VIOLATION (133)
    The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
    or above.
    Arguments:
    Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
    component can usually be identified with a stack trace.
    Arg2: 0000000000000501, The DPC time count (in ticks).
    Arg3: 0000000000000500, The DPC time allotment (in ticks).
    Arg4: 0000000000000000

    Debugging Details:
    ------------------


    DUMP_FILE_ATTRIBUTES: 0xc
      Insufficient Dumpfile Size
      Kernel Generated Triage Dump

    DPC_TIMEOUT_TYPE:  SINGLE_DPC_TIMEOUT_EXCEEDED

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

    BUGCHECK_STR:  0x133

    PROCESS_NAME:  System

    CURRENT_IRQL:  d

    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

    LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80256fd2ca0

    STACK_TEXT:  
    ffffd000`20706e38 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx


    STACK_COMMAND:  kb

    SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: Unknown_Module

    IMAGE_NAME:  Unknown_Image

    DEBUG_FLR_IMAGE_TIMESTAMP:  0

    IMAGE_VERSION:  

    BUCKET_ID:  ZEROED_STACK

    FAILURE_BUCKET_ID:  ZEROED_STACK

    ANALYSIS_SOURCE:  KM

    FAILURE_ID_HASH_STRING:  km:zeroed_stack

    FAILURE_ID_HASH:  {4af92c9d-8968-8d00-06f5-868dfba32e9a}

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

    Anyone could help to find what\how cause it?

    Thanks for the advices. I will try to see whether they will help.

    And here is the dmp file: https://skydrive.live.com/redir?resid=77F3959EB0FBFC6A!1029&authkey=!AGc6SdrTcq4WNcU

    I don't konw why I can't add the link.

    • Edited by jianeddie Saturday, October 26, 2013 4:26 AM
    Saturday, October 26, 2013 3:54 AM

Answers

  • Hi, 

    It appears that display driver is incompatible. 

    I suggest we try to remove display driver and re-install an older version (like for Windows 8) of it from manufacturer site to check the results. 


    Regards,

    Kate Li

    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

    Monday, October 28, 2013 11:18 AM
  • Jianeddie

    Both of the DMP'S were inconclusive.  I would suggest running driver verifier to pin down the mis-behaving driver.

    Driver verifier (for complete directions see our wiki here)
    Using Driver Verifier is an iffy proposition.
    Most times it will crash and it will tell you what the driver is, but sometimes it will crash and won't tell you the driver.
    Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

    I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise.
    Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

    Here is the procedure:

    Go to Start and type in "verifier" (without the quotes) and press Enter
    Select "Create custom settings (for code developers)" and click "Next
    Select "Select individual settings from a full list" and click "Next"
    Select everything EXCEPT FOR "Low Resource Simulation" 
    For Win 8 dont check Concurrency stress test, and DDI compliance checking click "Next"
    Select "Select driver names from a list" and click "Next"
    Then select all drivers NOT provided by Microsoft and click "Next"
    Select "Finish" on the next page.

    Reboot the system and wait for it to crash to the Blue Screen.

    Continue to use your system normally, and if you know what causes the crash, do that repeatedly. 
    The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. 
    If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.

    If you can't get into Windows because it crashes too soon, try it in Safe Mode.
    If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.


    Wanikiya & Dyami--Team Zigzag

    Monday, October 28, 2013 7:51 PM

All replies

  • We do need the actual DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.  

    WE NEED AT LEAST TWO DMP FILES TO SPOT TRENDS AND CONFIRM THE DIAGNOSIS.

    If you are overclocking (pushing the components beyond their design) you should revert to default at least until the crashing is solved. If you dont know what it is you probably are not overclocking.

    You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

    To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.  

    *

    The procedure:
    * Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
    * Zip up the copy (compress them)

    *Please upload them to a file sharing service like Skydrive or"Rapidshare" and put a link to them in your reply.

     

    Link for how to  upload below.
    *
    To ensure minidumps are enabled:
    * Go to Start, in the Search Box type: sysdm.cpl, press Enter.
    * Under the Advanced tab, click on the Startup and Recovery Settings... button.
    * Ensure that Automatically restart is unchecked.
    * Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
    * Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
    * OK your way out.
    * Reboot if changes have been made.
    Please also run MSinfo32 and upload the output as well.
    To run MSinfo32 please go to start>run>MSinfo32
    Go to "file" "save" and upload the saved file with the DMPS
    System specs are extremely useful so please include whatever you know.

    Blue Screen View & Who Crashed are often wrong and should only be used in an emergency...

    You can read more about BSODS here
    You can learn how to test your memory here
    Asking an effective question to get help fast here
    Basic troubleshooting tips can be found here
    Driver verifier-Tracking down a mis behaving driver  here






    • Edited by JMH3143MVP Saturday, October 26, 2013 4:10 AM
    Saturday, October 26, 2013 4:09 AM
  • First, it's good to run the System File Checker tool.

    Start --> Run --> type cmd and press the Enter button.

    sfc /scannow

    If this doesn't help, you can go the manufacturer's website and verify that you have the latest drivers (at least chipset) installed for Windows 8.1.

    Saturday, October 26, 2013 4:10 AM
  • Thanks, but this not help. And I've checked all drivers, all seems the lastest
    Saturday, October 26, 2013 5:21 AM
  • Hi, 

    It appears that display driver is incompatible. 

    I suggest we try to remove display driver and re-install an older version (like for Windows 8) of it from manufacturer site to check the results. 


    Regards,

    Kate Li

    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

    Monday, October 28, 2013 11:18 AM
  • Jianeddie

    Both of the DMP'S were inconclusive.  I would suggest running driver verifier to pin down the mis-behaving driver.

    Driver verifier (for complete directions see our wiki here)
    Using Driver Verifier is an iffy proposition.
    Most times it will crash and it will tell you what the driver is, but sometimes it will crash and won't tell you the driver.
    Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

    I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise.
    Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

    Here is the procedure:

    Go to Start and type in "verifier" (without the quotes) and press Enter
    Select "Create custom settings (for code developers)" and click "Next
    Select "Select individual settings from a full list" and click "Next"
    Select everything EXCEPT FOR "Low Resource Simulation" 
    For Win 8 dont check Concurrency stress test, and DDI compliance checking click "Next"
    Select "Select driver names from a list" and click "Next"
    Then select all drivers NOT provided by Microsoft and click "Next"
    Select "Finish" on the next page.

    Reboot the system and wait for it to crash to the Blue Screen.

    Continue to use your system normally, and if you know what causes the crash, do that repeatedly. 
    The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. 
    If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.

    If you can't get into Windows because it crashes too soon, try it in Safe Mode.
    If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.


    Wanikiya & Dyami--Team Zigzag

    Monday, October 28, 2013 7:51 PM