Windows 10: Daily BSOD (DPC_WATCHDOG_VIOLATION): ntoskrnl.exe? nvstor.sys?

Discus and support Daily BSOD (DPC_WATCHDOG_VIOLATION): ntoskrnl.exe? nvstor.sys? in Windows 10 BSOD Crashes and Debugging to solve the problem; Please answer my question. Discussion in 'Windows 10 BSOD Crashes and Debugging' started by ipaul, Nov 5, 2016.

  1. axe0 New Member

    Daily BSOD (DPC_WATCHDOG_VIOLATION): ntoskrnl.exe? nvstor.sys?


    Please answer my question.
     
  2. ipaul Win User

    My machine uses AwardBIOS Flash Utility for Dell V1.00. I do not see an option to flash BIOS from within the current BIOS.

    Per your comment that the I531_1013.exe contained a BIN, I tried multiple extractor programs but none could locate a .bin or any other files to extract.

    Randomly, I went back to trying to boot the I531_1013.exe file from a USB drive (formatted to include a .cmd program), but typing C:\> I531_1013.exe kept saying "Command or filename not recognized." So get this: I type C:\> dir, and notice that the directory of USB files shows the .exe filename as "I531_1~3". So I tried running I531_1~3.exe from the USB drive's command prompt, and voila!!

    It FINALLY flashed the bios and updated to the latest version. Whoa, what a rush.

    Now, let's see if the BSODs stop... I'll report back. Thanks!
     
    ipaul, Dec 4, 2016
    #17
  3. axe0 New Member
    I've used 7-zip version 16.02 to find the BIN.


    Good to hear *Smile
     
  4. ipaul Win User

    Daily BSOD (DPC_WATCHDOG_VIOLATION): ntoskrnl.exe? nvstor.sys?

    I just had my first BSOD since updating BIOS to the latest version *Sad

    Here's the crash report (it's the same two potential causes as before the BSOD update: ntoskrnl.exe and nvstor.sys).

    On Tue 12/6/2016 3:26:11 PM GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\120616-37484-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x14A510)
    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 12/6/2016 3:26:11 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

    The above was run with "WhoCrashed". What else would you suggest I try next? Thanks for your time.
     
    ipaul, Dec 5, 2016
    #19
  5. axe0 New Member
  6. ipaul Win User
    I've run dm_log_collector three times and each time it completes successfully after a few minutes, but just leaves an empty zipped file on the desktop with nothing in it. I'll keep trying.
     
    ipaul, Dec 5, 2016
    #21
  7. axe0 New Member
  8. ipaul Win User

    Daily BSOD (DPC_WATCHDOG_VIOLATION): ntoskrnl.exe? nvstor.sys?

    Windows Update History does not show any updates to the SATA drives for my desktop.

    In Device Manager, I have the following under Storage controllers:
    -Microsoft Storage Spaces Controller
    -NVIDIA nForce Serial ATA Controller
    -NVIDIA nForce Serial ATA Controller

    Under Properties for each, Driver Files shows:
    -C:\Windows\system32\DRIVERS\spaceport.sys
    -C:\Windows\system32\DRIVERS\nvstor.sys
    -C:\Windows\system32\DRIVERS\nvstor.sys

    I tried updating the drivers on all 3 (searching online) but get "Windows has determined the driver software for your device is up to date."

    Is there anything else I can try? Disable/Re-enable? Uninstall? Look for third party driver updates? I'm an amateur with all this so any suggestions at all are appreciated.

    I did notice in Device Manager an "Other devices" that says "Unknown device" and has a yellow triangle caution icon over it. Properties says "the drivers for this device are not installed" but I can't figure out what it is and cannot update drivers. I disabled it and nothing happened. Could this be related to the BSODs?
     
    ipaul, Dec 5, 2016
    #23
  9. ipaul Win User
    I also noticed in Device Manager that the NVIDIA nForce Serial ATA Controllers both show the following under "Events":

    8/5/2016 Device migrated
    8/5/2016 Device configured (nvraid.inf)
    8/5/2016 Device started (nvstor)

    And 8/5/2016 is *roughly* when these BSODs started. Again, I have no idea if I'm on to something here, but seems possible!

    If it'd help for me to paste the full Event details for each of the above 3 events (from Event Viewer), just let me know.
     
    ipaul, Dec 5, 2016
    #24
  10. axe0 New Member
    You could try to uninstall the Nvidia serial ata controllers, reboot and let Windows reinstall. Much more than that you can't do, (and it is not recommended to install the driver outside of Windows Update, Windows device manager and Dell, because most then end up using programs that mostly screw up their systems more (driver update programs).)

    Such devices are not critical to the system, because they usually are peripheral for which no driver could install at the time. Due to this Windows can't recognize what category it belongs to and puts it in 'other devices' category.
    You can safely uninstall this device.

    I have the same events with my Intel controller, if you look at some other devices you may notice that this happens to them too (not all though).
     
  11. valihrach Win User
  12. ipaul Win User
    Hi valihrach - thanks! In that post, you say:

    NVidia nForce SATA controller driver (nvstor.sys or nvraid.sys) can be replaced by Standard Dual-channel IDE controller driver (atapi.sys) included in Windows.

    How do I do this? I want to make sure I follow accurate steps. Do I uninstall the NVIDIA nForce Serial ATA Controller in Device Manager, and then just reboot and let Windows do its thing? Or do I need to manually replace it with the Standard Dual-channel IDE controller driver (atapi.sys)? If so, how?

    Thanks for the help!
     
    ipaul, Dec 10, 2016
    #27
  13. valihrach Win User

    Daily BSOD (DPC_WATCHDOG_VIOLATION): ntoskrnl.exe? nvstor.sys?

    I haven't English system at hand, please be informed that all messages are translated.

    Before modifying your system, make system image using Macrium Reflect or at least create system restore checkpoint.

    Run Device Manager, then locate two instances of NVIDIA nForce Serial ATA Controller - either under IDE ATA Controllers or under SCSI & RAID Controllers nodes.

    For one of them, rightclick and select Properties, click Driver tab, click Update Driver button. Select Find Driver Manually, click Select from List, (maybe uncheck Show Compatible - I don't remember), select Standard IDE/ATA Controllers, select Standard Dual Channel PCI IDE Controller, resume wizard without restart.

    Repeat for second NVIDIA controller, this time with restart.

    After restart, you should have 3 instances of PCI IDE Controller and 6 ATA Channels. This is because (I suppose) you have one real PATA controller and two NVIDIA SATA but with same driver; all of them are dualchannel.
     
    valihrach, Dec 11, 2016
    #28
  14. ipaul Win User
    I followed these steps exactly, and after restart indeed I have 3 instances of PCI IDE Controller and 6 ATA Channels. Let's hope this stops the BSODs!

    I'll report back - thanks!
     
    ipaul, Dec 11, 2016
    #29
  15. ipaul Win User
    So far so good. I haven't gotten a BSOD since replacing the NVidia nForce SATA controller drivers with the Standard Dual-channel IDE controller drivers. I'm cautiously optimistic.

    Question: Does this replacement mean I should no longer allow NVidia GeForce Experience to check for updates, or update GeForce drivers? I'm not sure if doing so would replace the Standard Dual-channel IDE drivers with the old nForce SATA drivers.

    If I need to ignore NVidia GeForce Experience's driver update prompts from now on, forever, please let me know! Thanks!
     
    ipaul, Dec 14, 2016
    #30
Thema:

Daily BSOD (DPC_WATCHDOG_VIOLATION): ntoskrnl.exe? nvstor.sys?

Loading...
  1. Daily BSOD (DPC_WATCHDOG_VIOLATION): ntoskrnl.exe? nvstor.sys? - Similar Threads - Daily BSOD DPC_WATCHDOG_VIOLATION

  2. ntoskrnl bsod

    in Windows 10 Software and Apps
    ntoskrnl bsod: My pc has been bsod-ing for 2-3 years now and i recently decided to try and fix it. I use bluescreen view and always see that the bsods are always caused by ntoskrnl.exe. heres all of the stuff ive to try and fix it.Used 1 8gb ram stick at a timeused different ram slotsused...
  3. ntoskrnl BSOD

    in Windows 10 Gaming
    ntoskrnl BSOD: Hello, I have quite a persistent problem here.I often get BSOD or straight out system restarts the latter don't have any trace in minidump. In the past few days, they were too recurrent and got to a point where I had to reinstall Windows because my laptop actually got slowed...
  4. ntoskrnl BSOD

    in Windows 10 Software and Apps
    ntoskrnl BSOD: Hello, I have quite a persistent problem here.I often get BSOD or straight out system restarts the latter don't have any trace in minidump. In the past few days, they were too recurrent and got to a point where I had to reinstall Windows because my laptop actually got slowed...
  5. BSOD Minidump shows page_faul ntoskrnl..exe

    in Windows 10 BSOD Crashes and Debugging
    BSOD Minidump shows page_faul ntoskrnl..exe: KUKutter_UKFirstly, I would like to say that I am posting this again because after having an instant reply from an 'Andrew', and posting my dmp files as requested on July 24th I haven't heard anything back since! I have responded a couple of times but nothing is happening to...
  6. BSOD Minidump shows page_faul ntoskrnl..exe

    in Windows 10 BSOD Crashes and Debugging
    BSOD Minidump shows page_faul ntoskrnl..exe: Hi there, My new machine around 8 months old now runs perfectly most of the time. Uptime 3 - 6 weeks at a time. NO issues at all - I am a heavy PC user: Gaming, Audio Work and some 3D modelling, so my machine goes through its paces.Every now and then on boot, I get the error...
  7. Ntoskrnl BSOD

    in Windows 10 BSOD Crashes and Debugging
    Ntoskrnl BSOD: Hello, Any ideas how I can stop ntoskrnl.exe of causing blue screens? It happens every few days while I am playing games on steam Here are my dumps: https://drive.google.com/file/d/1E7Kwdh1341_R2psC5NVUoETVBtqC_QlP/view?usp=sharing...
  8. BSOD ntoskrnl..exe

    in Windows 10 BSOD Crashes and Debugging
    BSOD ntoskrnl..exe: My computer has crashed a few times often when i play games. I bought more ram because i thought that it was the issue but it didn't help. It did work a few days but then the crashes came back. After that i fixed the BSOD´s by lowering the graphics and the resolution on the...
  9. BSOD ntoskrnl..exe+1b35e0

    in Windows 10 BSOD Crashes and Debugging
    BSOD ntoskrnl..exe+1b35e0: Help. Getting 4-5 of these a day. Running latest Windows 10 Pro, Xibo signboard, Docker with Xibo server. Always the same 'Caused By Address'. Put in new memory, ran memory test, no errors, all drivers up to date. Change disk type to AHCA, made sure windows driver was...
  10. Bsod ntoskrnl

    in Windows 10 BSOD Crashes and Debugging
    Bsod ntoskrnl: Hi guys, Any help would be massively appreciated. My computer is BSOD at least two times a day. As far as I can tell, all drivers are up to date including Nvidia. Could somebody take a look at the attached and let me know if you find anything? I've ran a system check...