Page 5 of 7 FirstFirst ... 34567 LastLast

  1. Join Date : Sep 2015
    Posts : 117
    Microsoft Windows 10 Pro 64-bit Version 1607
       29 Sep 2016 #41

    I got up this morning and been over 36 hours & Blue Screen appeared again this time It's different according to the dump file. This happened also on my other PC same error ... Here is WhoCrashed info & another file I uploaded.

    1 was the Microsoft Digitally Signed nvstor.sys I am giving up on this & rolling back to 1511 or Windows 7
    2 was another file called ntoskrnl.exe which this happens here & on another system of mine also.



    On Thu 9/29/2016 7:24:23 AM GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\092916-34421-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x14A0B0)
    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 Thu 9/29/2016 7:24:23 AM 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
    DPC Watchdog BSOD Windows 10 1607 Attached Files
    Last edited by DrSysop; 29 Sep 2016 at 12:20.
      My System SpecsSystem Spec


  2. Join Date : Sep 2015
    Posts : 117
    Microsoft Windows 10 Pro 64-bit Version 1607
       29 Sep 2016 #42

    Last update for now, I finally contacted Microsoft tech support this morning & they told me this problem been reported many times & they think cause for issue is from ntoskml.exe & to disable TimeBroker in the registry.
    Type regedit & go this this following line.

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TimeBroker] "Start"=dword:00000003

    Change the 3 to a 4.

    It should look like this

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TimeBroker] "Start"=dword:00000004

    Also do this as well in settings, Make sure Get Tips, Tricks & suggestions is turned off also.

    Click image for larger version. 

Name:	settings.jpg 
Views:	4 
Size:	29.8 KB 
ID:	103641

    Then reboot!

    They advised me another update will correct this issue as many users been reporting using Asus, HP & Dell machines. So this should fix it for now but I will not know until 24-36 hours from my last reboot. If it crashes then have to wait for their update. Also If you using Google Chrome as I was close the browser when finished as it will cause issues.

    Thanks again Chris & for those who reading this & having same or similar issues as it's one pain in the neck!
    Last edited by DrSysop; 29 Sep 2016 at 13:29.
      My System SpecsSystem Spec


  3. Join Date : Sep 2015
    Posts : 117
    Microsoft Windows 10 Pro 64-bit Version 1607
       01 Oct 2016 #43

    Ok, Microsoft just had a cumulative update & that didn't fix the issue. But this crash seems to be coming at 3 AM local time. As I did all the things above & still crashes & found out my clients are having same issue on Asus motherboards & some MSI motherboards also. If anyone knows a way to disable this DPC Watchdog I will do that.
    I can't seem to find Windows 10 version 1511, So I will just put my Windows 7 drive back in until Microsoft or NVIDIA releases update.
      My System SpecsSystem Spec


  4. Join Date : Aug 2015
    Posts : 23
    Windows 10
       01 Oct 2016 #44

    DrSysop,

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


  5. Join Date : Sep 2015
    Posts : 117
    Microsoft Windows 10 Pro 64-bit Version 1607
       04 Oct 2016 #45

    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.
      My System SpecsSystem Spec


  6. Join Date : Aug 2015
    Posts : 16
    Windows 10 Pro 64-bit Version 1607
       07 Oct 2016 #46

    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.
      My System SpecsSystem Spec


  7. Join Date : Sep 2015
    Posts : 117
    Microsoft Windows 10 Pro 64-bit Version 1607
       11 Oct 2016 #47

    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!

      My System SpecsSystem Spec


  8. Join Date : Oct 2016
    Posts : 1
    Windows 10
       12 Oct 2016 #48

    DrSysop said: View Post
    Latest update on new install after a week of being up it happened again:


    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.
      My System SpecsSystem Spec


  9. Join Date : Sep 2015
    Posts : 117
    Microsoft Windows 10 Pro 64-bit Version 1607
       12 Oct 2016 #49

    Draven said: View Post
    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.
      My System SpecsSystem Spec


  10. Join Date : Aug 2015
    Posts : 16
    Windows 10 Pro 64-bit Version 1607
       4 Weeks Ago #50

    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.
      My System SpecsSystem Spec


 
Page 5 of 7 FirstFirst ... 34567 LastLast


Similar Threads
Thread Forum
DPC Watchdog BSOD 1607
So this Laptop freezes and hard reboots, the BSODs occur after the hard reboots wondering if you can discern any potential causes from the following zip. Lenovo E550 105669
BSOD Crashes and Debugging
BSOD DPC Watchdog Violation Windows 10
hi I'm receiving this BSOD periodically unfortunately I can't tell that I'm doing something particular to get it and it seems random. so I'm attaching logs and dumps hoping someone can help me. i know the reason of MEMORY_MANAGEMENT BSODs...
BSOD Crashes and Debugging
BSOD Watchdog on Windows 10, Seemingly Random
Hi everyone! This is my first post here. My computer has been fine until I updated it to windows 10 from win 8. I have been getting Watchdog violations randomly every 30 min to 3 hours since the update. One error report analyzed via WhoCrashed...
BSOD Crashes and Debugging
BSOD DPC Watchdog Violation Windows 10 64 bit
Hello guys. I recently upgraded my Ram from 2 to 4 (2*2) and installed windows 10 64 bit. Before, I hadn't any problem with 2 GB ram and 32 bit windows 10. After a few days later I got this BSOD for 2 times in a week . All drivers have been...
BSOD Crashes and Debugging
BSOD DPC Watchdog Violation Windows Kernel Fail
Background: DPC_Watchdog_Violation -- Going crazy! : Windows10 See comment thread in link for fix already attempted. Every 10 minutes or so, around when it would go to rest, machine crashes with DPC Watchdog Violation Have had this problem...
BSOD Crashes and Debugging
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 08:35.
Find Us
Twitter Facebook Google+



Windows 10 Forums