locked
BSOD Windows 8 (DPC_WATCHDOG_VIOLATION)- Samsung phone USB Tethering RRS feed

  • Question

  • Hi Team,

    When I try to use my new Samsung device for USB Tethering in Win8, BSOD occurs very often with error code "DPC_WATCHDOG_VIOLATION"

    In win7 also, connection is working fine, but if we select "Network and Sharing Center" , there was no response. And mouse pointer is keep on showing the progressing icon.

    Let me know where to attach the minidump.


    Thursday, October 31, 2013 4:52 AM

Answers

  • 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
    Links to out other wiki's can be found here.

    Advice offered in good faith. It is your decision to implement same.

    • Proposed as answer by ZigZag3143x Sunday, November 3, 2013 9:06 PM
    • Marked as answer by ZigZag3143x Wednesday, November 20, 2013 2:32 AM
    Thursday, October 31, 2013 5:50 AM

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
    Links to out other wiki's can be found here.

    Advice offered in good faith. It is your decision to implement same.

    • Proposed as answer by ZigZag3143x Sunday, November 3, 2013 9:06 PM
    • Marked as answer by ZigZag3143x Wednesday, November 20, 2013 2:32 AM
    Thursday, October 31, 2013 5:50 AM
  • Hi ZigZag,

    Not able to upload the dump. as of now
    For your quick reference, I extracted the call stack using WinDbg and pasted below.
    Meanwhile I will also upload the dump ASAP.

    Kindly provide some info with the below details

    /Satheesh

    1: 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: 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:
    ------------------
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x133
    PROCESS_NAME:  System
    CURRENT_IRQL:  d
    LAST_CONTROL_TRANSFER:  from fffff802401dcf4b to fffff8024005d440
    STACK_TEXT:  
    fffff880`009b8408 fffff802`401dcf4b : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
    fffff880`009b8410 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x145a4
    STACK_COMMAND:  kb
    FOLLOWUP_IP: 
    nt! ?? ::FNODOBFM::`string'+145a4
    fffff802`401dcf4b cc              int     3
    SYMBOL_STACK_INDEX:  1
    SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+145a4
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: nt
    IMAGE_NAME:  ntkrnlmp.exe
    DEBUG_FLR_IMAGE_TIMESTAMP:  51a966cd
    FAILURE_BUCKET_ID:  X64_0x133_nt!_??_::FNODOBFM::_string_+145a4
    BUCKET_ID:  X64_0x133_nt!_??_::FNODOBFM::_string_+145a4
    Followup: MachineOwner


    • Edited by ssk_1210 Wednesday, November 6, 2013 9:05 AM
    Wednesday, November 6, 2013 8:57 AM