Windows 10: DPC_WATCHDOG_VIOLATION BSoD if Windows took 1 minute to boot

If Windows 10 took 1 or more minutes to boot on my laptop, it will BSoD with DPC_WATCHDOG_VIOLATION as a stopcode. After rebooting, the system will hang/freeze, then I have to wait 3-5 minutes until the system continues to boot.

I can't screenshot because the reboot was so quick and there wasn't much infos in the Event Viewer or the Reliability History

submitted by /u/__andr3w
[link] [comments]

:)

 

ughhh! BSOD on boot

I guess my computer BSOD on boot right before getting to windows. not sure what the problem is though, everything is stable.

It gave me a list of two files in windows that could have caused the problems

 

Windows 10 build 10586 BSOD DPC_WATCHDOG_VIOLATION

Check (enable) it then do Step #5 & test.

The above notwithstanding...

Are you still getting the DPC_WATCHDOG_VIOLATION BSODs or...?

 

BSOD with DPC_WATCHDOG_VIOLATION

For the last week I'm suffering from a hand and BSOD in Windows 10 Pro. I didn't changed hardware and I cannot remember any update, but it is possible Windows updated my computer while shutting down (it does it regularly, so I didn't payed attention anymore).

The behavior is: the computer boots normally, everything appears to be running smoothly and after a few minutes (around 5 minutes), it almost hangs (mouse still moving), 5 seconds later it is completely hung (mouse doesn't move), and in 10 extra seconds I get to a BSOD with the only reference of DPC_WATCHDOG_VIOLATION.

The behavior is the same if I boot in safe mode.

After reading available information, it looks like it could be a hardware problem or a driver problem. I tried to reinstall a few drivers (named in the forums), but it didn't work. I also ran the standard memory test and half of the extended memory test and no errors aroused.

By using NirSoft's BlueScreenView, I managed to track down the problem to the HAL (which is like saying nothing to me... it could be anything).

Any idea of what I can try? Any place where I can see which is the hardware piece it is causing trouble? Once I find it, I can try to update the driver or disconnect/replace the faulty part.

UPDATE:

I managed to get into safe mode with command line and run sfc /scannow. It ran for some time, up to 25%, without issues, then the system got the BSOD. As long as the system boots into Windows, I have very few minutes to do whatever I have to do. Longer operations will be stopped by the BSOD.

I also ran the extended memory test. No failures until I went to sleep. When I woke up, the computer was on, but no screen signal. I can try to ask the system to repeat the test multiple times in order to survive the night. I will update if I get better results.