Windows 10: DPC Watchdog BSOD Windows 10 1607

DrSysop,

Sorry to hear this couldn't get fixed. I was fresh out of ideas. Hopefully MS will get on top of this.....hopefully.

 

Chris, I gave up just using the fresh installed windows 10 so far no crashes & runs great. I did this on 2 other PC friends of mine had issues with & works like a charm. Best you do it when you can. *Smile

 

Hoping Microsoft fix this soon. Having the same issue on my home server PC which updated to 1607 a couple of weeks ago and now crashes and reboots every 24 hours and some odd minutes. It's running an MSI board. Quite irritating as it's an un-monitored computer which runs home security systems, media streaming, and TS servers. Having to constantly reboot it manually to avoid this issue is very annoying.

 

Latest update on new install after a week of being up it happened again:

On Tue 10/11/2016 5:35:50 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\101116-21937-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A2B0)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 10/11/2016 5:35:50 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: nvstor.sys (nvstor+0x7468)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\Windows\system32\drivers\nvstor.sys
product: NVIDIA nForce(TM) SATA Driver
company: NVIDIA Corporation
description: NVIDIA® nForce(TM) Sata Performance Driver
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might also be caused because of overheating (thermal issue).
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvstor.sys (NVIDIA® nForce(TM) Sata Performance Driver, NVIDIA Corporation).
Google query: NVIDIA Corporation DPC_WATCHDOG_VIOLATION


This time ntoskrnl.exe also. So Microcrap & nvidia needs to get this fixed ASAP!

 

I signed up because i have been having this exact issue, so i would like it to be more attention out there to others that this is a BIG common issue.

What i have done is set up a Task Schedule to restart my PC every morning at 3am. Because like most others, that are experiencing this my PC is on 24 hours a day, as it is the main server and Media server in my house.

So it stops the 24-36 hour DPC Watchdog crash.

I can also confirm for others out there.... it is NOT nVidia graphics it is nVidia SATA controllers.

 

Yes it is. I seen this on HP, Dell & Asus PC's but thanks I will try that for now unless there is a way to disable the DPC Watchdog then maybe it will stop.

 

Several updates later and this is still happening. My system is now starting to become rather unstable due to the daily crashing and I've actually had to repair a few off my programs because they keep getting shutdown improperly due to the crashes. Really annoyed this has been allowed to go on so long since Microsoft are apparently aware of it.

 

What I did is as described above made a schedule to reboot PC 3am every day & so far been ok but still had 1 or 2 occasional crashes before 3am but seems to help a bit. I noticed if I am in youtube watching videos it can crash by hearing sound messing up also. Seems this is a problem on Asus based motherboards using this nvidia SATA driver & HP & Dell machines.

 

Whilst that would help prevent further corruption (the last two days after the crashes the PC hasn't even reached Windows again without a manual reset of the power) it sadly doesn't help me out much since the PC in question runs home security systems and TeamSpeak servers, all of which require sign-in and manual activation.

I think I'm going to look at rolling back to the previous version and using a regedit to disable Windows Update until I see this problem as having been fixed as it's driving me insane. Really disappointed with their handling of this issue.

 

Just found a suggested 'fix' in another thread here, second last post. I've gone through and switched all relevant drivers on the PC suffering from this and will see how it goes in just over 24 hours. One last attempt haha.

 

I tried that & it will install the nForce again & ask you to reboot. This is what I see in my device manager now check to see if it's the same. That other link had something to do with ATI graphics card also but this is a SATA controller issue.

 

Yeah I noticed they were also talking about graphics in that thread but the guy in the post I was referring to seemed to solely be talking about the SATA controller which is the issue I'm having, same as yourself.

I had the same NVIDIA nForce Serial ATA Controller references (three times for me) under storage controllers on the affected PC. I changed their drivers to the Standard Dual Channel PCI IDE Controller version and they now show under IDE ATA/ATAPI controllers and thus far haven't attempted to update themselves to the nVidia driver again. I'll let you know once the 24 hour mark has passed as to whether it has any success in averting the crash.

 

Well I've just gone in and checked and found this in the task manager.

Attachment 109200

It's the first time since the 1607 update that the PC has passed approximately 24 hours and 15 minutes without crashing.

 

Well after playing around I managed to get it this way also by selecting manual install driver & saw it on list & had to do it 2x since my nForce was listed twice & rebooted. It seems stable & speed same, but we will see if this works & can always system restore back if not. I also did this to my other Dell machines & so far no crash but only 9 hrs. Will update you also after 36 hours.

Here what it looks like now in my device manager.

Attachment 109227Attachment 109228

 

Yeah that's pretty much the same as how mine looks now after changing the drivers manually. My affected PC has now passed 50 hours up time. Will keep my fingers crossed you have similar results.