Windows 10: BSOD and reboot every 24 hours and 16 minutes Solved

Page 2 of 4 FirstFirst 1234 LastLast
  1.    01 Dec 2016 #11

    Also the dumpfiles are not really helpful.
    Code:
     *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 133, {0, 501, 500, 0}
    
    Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
    
    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: 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.17336 (debuggers(dbg).150226-1500) x86fre
    
    LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff802f49bf510
    
    STACK_TEXT:  
    fffff802`f666dd88 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
    Did you already run the SFC command to see if any system files are corrupted.

    SFC
    Use SFC to check and repair windows system files.

    See this tutorial
    SFC Command - Run in Windows 10 - Windows 10 Forums
    Note
    If SFC could not fix something, then run the command again to see if it may be able to the next time. Sometimes it may take running the sfc /scannow command 3 times restarting the PC after each time to completely fix everything that it's able to.

    If not, then run the Dism /Online /Cleanup-Image /RestoreHealth command to repair any component store corruption, restart the PC afterwards, and try the sfc /scannow command again.
      My ComputerSystem Spec

  2.    01 Dec 2016 #12

    I will run the SFC and report back.
      My ComputerSystem Spec

  3.    01 Dec 2016 #13

    I ran the SFC three time in Windows 10. No problems found.
      My ComputerSystem Spec

  4.    05 Dec 2016 #14

    Can someone explain to me the following text that showed up in the dumpfile? My guess is that some process is starting 24 hours after the last reboot and then aborting 16 minutes later, creating my reboot frequency of 24 hours and 16 minutes.

    A single DPC or ISR exceeded its time allotment. The offending
    component can usually be identified with a stack trace.
      My ComputerSystem Spec


  5. Posts : 12,308
    Windows 10 Pro
       10 Dec 2016 #15

    A DPC is a deffered procedure call, one of the interrupts that Windows uses. A DPC is being used when the executing of something needs to be delayed as its current activity hasn't yet finished. The dump simply says that a DPC or ISR took too long for its current activity to finish, so a crash was called because else the system would freeze (if I'm correct).

    ISR is interrupt service routine, a bit similar to a DPC only a ISR is a hardware interrupt where a DPC is a software interrupt.

    My guess is that some process is starting 24 hours after the last reboot and then aborting 16 minutes later, creating my reboot frequency of 24 hours and 16 minutes.
    Lets read the parameters of the dump
    Code:
    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
    500, is the amount of time allowed.
    501, is the time it took.

    For understanding, lets say a tick is a second. The intterupt was allowed to finish its activity within 8 minutes and 20 seconds (500 seconds), it took the interrupt 8 minutes and 21 seconds to finish its activity. Because it took too long a crash was called.

    For the infomation, device drivers don't look up to 50ms execution delay (AFAIK), but they do look up to a second execution delay.
      My ComputersSystem Spec

  6.    10 Dec 2016 #16

    Thanks very much for the explanation. How can I determine what procedure is exceeding it time allotment?
      My ComputerSystem Spec


  7. Posts : 12,308
    Windows 10 Pro
       10 Dec 2016 #17

    Debug the memory dump, the memory dump contains all the kernel data that was saved at the time. Only through the memory dumps we can find out what went wrong and how/why.
      My ComputersSystem Spec

  8.    10 Dec 2016 #18

    Unfortunately this is getting to a point that's way over my head. I have done enough reading about debugging a memory dump to know that it is well beyond my ability. Is there somewhere that I can get support for debugging the memory dump?
      My ComputerSystem Spec


  9. Posts : 12,308
    Windows 10 Pro
       11 Dec 2016 #19

    Let I put it this way:
    Debugging the dump = finding the cause
    Finding the cause = finding a solution
    Finding a solution = why most are here.


    The debugging part is what we do for you
      My ComputersSystem Spec

  10.    12 Dec 2016 #20

    Should I post an updated minidump file?
      My ComputerSystem Spec


 
Page 2 of 4 FirstFirst 1234 LastLast

Related Threads
Hello everyone! The title is meant to be a question, but I ran out of characters. Firstly, I'm running both a Windows 10 and a Linux Mint. As per the default settings, if I turn on my laptop and don't touch it, it boots up Linux, I have to...
I have a very limiting issue. I've had Windows 10 for months and all has been fine. Then all of a sudden about 5 days ago I rebooted my machine and it passed by the normal logon screen and went straight to a blue screen (not a BSD screen, just a...
Hello, So yesterday I installed some updates on my computer, however when it was rebooting it sat there for about an hour doing nothing. Eventually I force turned it off and tried to reboot it, however it kept doing the same thing. I looked up...
I have an app named "Timer+" which after it is set and finishes makes a loud beeping noise until it is turned off. I can have up to three timers running at the same time. I have discovered if my QUIET HOURS are turned on, then no sound will be...
I installed Windows 10 fairly quickly on my laptop, and firlgured it'd be just as painfree to do so on my desktop, but the install was stuck at 'Copying files - 48%' for hours. I figured that since it was just copying files, I would just restart the...
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 12:01.
Find Us