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

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.

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[/quote] 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.

 

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

 

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.

 

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?

 

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 *Wink

 

Should I post an updated minidump file?

 

If a new BSOD has occured, but I leave it further to @lifetec to not cause any conflict.

 

For various reasons I have had to manually restart my computer a few times over the last few days, so the frequency of rebooting every 24 hours and 16 minutes has been disturbed. However, the reboots have begun again now that the machine has been running uninterrupted.. This morning, the desktop rebooted 24 hours and 16 minutes after I manually restarted yesterday.

Here's the link to my minidump files. The zip file includes all of the minidumps that I have, including the one that was generated with this morning's reboot.

Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.

Thanks for the help. This is driving me nuts.

 

The latest zip file is the Minidump3.zip

 

Please run the DM Log Collector again and upload a new zip, we'll need to see a few files.

 

Here is the current run of the DM Log Collector:

Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.

 

Please uninstall Norton while troubleshooting and use Windows Defender as alternative
Solved Anti Virus (AV) stand alone removal tools - Windows 10 Forums






Diagnostics Test

HDD TEST
*Arrow Run HDTune to

• check the health,
• scan for errors, no quick scan but full scan
• run a benchmark.

It may take some time, but please take the time you need to perform it properly.
When above is done please make screenshots of the following

• the health,
• the error scan,
• the benchmark incl. following
  • transfer rate,
  • access time,
  • burst rate,
  • cpu usage.

*Arrow Run SeaTools DOS to check the integrity of your HDD. SeaTools for DOS and Windows - How to Use - Windows 7 Help Forums
Run the long test.
*Arrow Check Disk (chkdsk) - Read Event Viewer Log - Windows 7 Help Forums

 

I have removed Norton and am running Windows Defender. I have run HD Tune. Screenshots of the Computer Health, Error Scan (Full), and Benchmark are provided under the following OneDrive link. (Screenshots are included in both docx and pdf formats.) I did not run the SeaTools DOS because my C: drive is an SSD. I ran Chkdsk with /r. The text file is also included under the following link.

Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.

 

It is highly recommended to perform the scans on all connected storage devices.

 

Used HDTune to run health checks on internal drives (C, D, and G) and external drives (F and I). Also ran error scans on each. I could not complete the error scan on the I: drive because it took longer than 24 hours to run, and my computer will not run longer than 24 hours and 16 minutes before it reboots. The partial scan results are included in the files that follow. Benchmarks were run on all drives.

I ran SeaTools DOS on the internal drives and all passed.

I ran chkdsk /r on all internal drives. I ran error checking with repairs on both external drives.

Results from all tests are available at:

Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.