Windows 10: Random BSOD - DPC_WATCHDOG_VIOLATION

Another one that hasn't much to offer, lets try driver verifier again to see if it gives us a driver.
Code: ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 109, {a3a01f59b21434fd, b3b72be00494ee4a, 6, 18} Processing initial command '!analyze -v; !sysinfo smbios; !sysinfo machineid; !sysinfo cpuspeed; !thread; .bugcheck; .time;' Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE ) Followup: MachineOwner[/quote]




Diagnostic Test

DRIVER VERIFIER


Warning Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.
Please follow this tutorial to run driver verifier.

Some windows drivers are blamed in a few crashes, but that usually means that a 3rd party driver is actually the cause.
Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.



Note Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.

 

Thanks, I did turn the verifier back on right after this dump. Time to wait...

 

I happened to be swapping a hard disk tonight and poking around my BIOS and noticed an option called "SATA Aggressive link power management" and that it was ENABLED. As this is a computer I leave on 24/7 (including all hard drives spinning) I decided to research a bit and see if I should disable it given my usage. A quick google turned up lots of hits indicating that having this enabled could cause BSODs... so it is off. Fingers still crossed...

 

I have my fingers crossed too.

 

No crashes since last post - marking as solved.