Win 10 Pro And Bsod

Hello all,

I am currently running windows 10 Pro and keep getting random BSOD with a error stating DPC_Watchdog_Violation and restarts.

Checked my dump folder but not dump file has been created. My System is a custom build.

AMD Athlon 64 x2 dual core 4600+ 2.5Ghz
4GB Ram
Nvidia Geforce GTX 750 Ti 2GB
Windows 10 Ver 10.0.14393.0

 

From what I just read, uninstall and re-install the Graphics Driver. NVidia may even have a driver update.

 

I have already done that and also turned of fast boot in power button options. Also done a Scandisk through command prompt in admin.

 

Follow this and upload the needed zip, it should give us some clues.

 

Ok here come the zip files that have been created as I followed the steps

 

Bugchecks were both 0x133, the only 3rd party driver in theStacks (the driver that's being waited on) is nvstor.sys, part of the Nvidia chipset/storage drivers. But, the debugger is also showing that it can't verify nvstor.sys, so there might be some kind of access issue/interference from an unknown driver behind it.

I'd avoid using nvstor.sys by forcing Device Manager to use the stock Windows driver instead (IDE ATA/ATAPI controllers > the Nvidia controller > update it to the built in Standard SATA AHCI Controller, or whichever MS option you have listed). Make a System Restore point before doing this, just in case. If there's a recent NForce WHQL driver set for W10 for your chipset, you could try installing these instead.

So, what could be causing the blockage of the storage driver? Kaspersky/MBAE would be my first suspects, uninstall both using their respective maker's uninstall tools/routines and enable Windows Defender during troubleshooting.

Code:

Debug session time: Mon Aug  8 21:37:54.001 2016 (UTC + 1:00)
Loading Dump File [C:\Users\Me\SysnativeBSODApps\080816-37000-01.dmp]
Built by: 14393.0.amd64fre.rs1_release.160715-1616
System Uptime: 1 days 0:15:20.937
*** WARNING: Unable to verify timestamp for nvstor.sys
*** ERROR: Module load completed but symbols could not be loaded for nvstor.sys
Probably caused by : nvstor.sys ( nvstor+176f3 )
BugCheck 133, {0, 501, 500, 0}
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x00000133]DPC_WATCHDOG_VIOLATION (133)[/url]
Bugcheck code 00000133
Arguments:
Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
   component can usually be identified with a stack trace.
Arg2: 0000000000000501, The DPC time count (in ticks).
Arg3: 0000000000000500, The DPC time allotment (in ticks).
Arg4: 0000000000000000
BUGCHECK_STR:  0x133
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  0x133_DPC_nvstor!Unknown_Function
BiosVersion = F9
BiosReleaseDate = 07/15/2008
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = M61SME-S2
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Thu Aug  4 17:10:02.709 2016 (UTC + 1:00)
Loading Dump File [C:\Users\Me\SysnativeBSODApps\080416-45578-01.dmp]
Built by: 14393.0.amd64fre.rs1_release.160715-1616
System Uptime: 1 days 0:15:20.641
*** WARNING: Unable to verify timestamp for nvstor.sys
*** ERROR: Module load completed but symbols could not be loaded for nvstor.sys
Probably caused by : nvstor.sys ( nvstor+7468 )
BugCheck 133, {0, 501, 500, 0}
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x00000133]DPC_WATCHDOG_VIOLATION (133)[/url]
Bugcheck code 00000133
Arguments:
Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
   component can usually be identified with a stack trace.
Arg2: 0000000000000501, The DPC time count (in ticks).
Arg3: 0000000000000500, The DPC time allotment (in ticks).
Arg4: 0000000000000000
BUGCHECK_STR:  0x133
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  0x133_DPC_nvstor!Unknown_Function
BiosVersion = F9
BiosReleaseDate = 07/15/2008
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = M61SME-S2
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Stacktexts

Code:

**************************Mon Aug  8 21:37:54.001 2016 (UTC + 1:00)**************************
STACK_TEXT: 
fffff803`7ce9ed88 fffff803`7abeca3c : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
fffff803`7ce9ed90 fffff803`7aaa82b9 : 0000c6e4`df6ac6a1 0000c6e4`df6aba3f fffff780`00000320 fffff803`7aa5e490 : nt! ?? ::FNODOBFM::`string'+0xe87c
fffff803`7ce9edf0 fffff803`7aa13366 : fffff803`7ce90720 fffff803`7adc7180 00000000`00000002 0000c6e4`df6aba3f : nt!KeClockInterruptNotify+0x469
fffff803`7ce9ef40 fffff803`7ab53f97 : fffff803`7aa5e3e0 00000000`00000000 ffffe001`13105c80 fffff803`7abd0267 : hal!HalpTimerClockInterrupt+0x56
fffff803`7ce9ef70 fffff803`7abd060a : fffff803`7aa5e3e0 ffffc985`0cb55138 00000000`00000000 00000000`00000008 : nt!KiCallInterruptServiceRoutine+0x87
fffff803`7ce9efb0 fffff803`7abd0a57 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xea
fffff803`7ce90720 fffff803`46a376f3 : fffff803`46a2744c 00000000`00000000 ffffc985`12c89450 00000000`00000088 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff803`7ce908b8 fffff803`46a2744c : 00000000`00000000 ffffc985`12c89450 00000000`00000088 00000000`00000000 : nvstor+0x176f3
fffff803`7ce908c0 00000000`00000000 : ffffc985`12c89450 00000000`00000088 00000000`00000000 00000000`00000000 : nvstor+0x744c


¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Aug  4 17:10:02.709 2016 (UTC + 1:00)**************************
STACK_TEXT: 
fffff801`59cb9d88 fffff801`57978a3c : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
fffff801`59cb9d90 fffff801`578342b9 : 0000c38d`73c3ee5b 0000c38d`73c3e225 fffff780`00000320 fffff801`5807f490 : nt! ?? ::FNODOBFM::`string'+0xe87c
fffff801`59cb9df0 fffff801`58034366 : fffff801`59cab690 fffff801`57b53180 00000000`00000002 0000c38d`73c3e225 : nt!KeClockInterruptNotify+0x469
fffff801`59cb9f40 fffff801`578dff97 : fffff801`5807f3e0 00000000`00000008 fffff801`59cb9f50 00000000`0000000c : hal!HalpTimerClockInterrupt+0x56
fffff801`59cb9f70 fffff801`5795c60a : fffff801`5807f3e0 00000000`45ecdeef 00000001`00000000 ffffffff`ba132127 : nt!KiCallInterruptServiceRoutine+0x87
fffff801`59cb9fb0 fffff801`5795ca57 : 00000000`00000000 fffff801`5795ca64 00000000`00000000 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xea
fffff801`59cab690 fffff801`58032bad : fffff801`58049c89 fffff80f`c0133f30 ffffc38f`73149440 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff801`59cab828 fffff801`58049c89 : fffff80f`c0133f30 ffffc38f`73149440 00000000`00000000 ffffc38f`731493e0 : hal!HalpHpetQueryCounter+0xd
fffff801`59cab830 fffff80f`be857468 : 00000000`00000000 ffffc38f`756c6450 00000000`00000088 00000000`00000000 : hal!KeStallExecutionProcessor+0x170d9
fffff801`59cab8c0 00000000`00000000 : ffffc38f`756c6450 00000000`00000088 00000000`00000000 00000000`00000000 : nvstor+0x7468

3rd Party driver list (for info only):
http://www.carrona.org/drivers/driver.php?id=LcUvcUpper.sys
http://www.carrona.org/drivers/driver.php?id=RTCore64.sys
http://www.carrona.org/drivers/driver.php?id=SaiBus.sys
http://www.carrona.org/drivers/driver.php?id=SaiMini.sys
http://www.carrona.org/drivers/driver.php?id=cm_km.sys
iorate.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=kl1.sys
http://www.carrona.org/drivers/driver.php?id=klbackupdisk.sys
http://www.carrona.org/drivers/driver.php?id=klbackupflt.sys
http://www.carrona.org/drivers/driver.php?id=kldisk.sys
http://www.carrona.org/drivers/driver.php?id=klflt.sys
http://www.carrona.org/drivers/driver.php?id=klhk.sys
klids.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=klif.sys
http://www.carrona.org/drivers/driver.php?id=klim6.sys
http://www.carrona.org/drivers/driver.php?id=klkbdflt.sys
http://www.carrona.org/drivers/driver.php?id=klmouflt.sys
http://www.carrona.org/drivers/driver.php?id=klpd.sys
http://www.carrona.org/drivers/driver.php?id=klwfp.sys
http://www.carrona.org/drivers/driver.php?id=klwtp.sys
http://www.carrona.org/drivers/driver.php?id=kneps.sys
http://www.carrona.org/drivers/driver.php?id=mbae64.sys
http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
http://www.carrona.org/drivers/driver.php?id=nvmf6264.sys
http://www.carrona.org/drivers/driver.php?id=nvstor.sys
http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
registry.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=rt640x64.sys
http://www.carrona.org/drivers/driver.php?id=rzendpt.sys
http://www.carrona.org/drivers/driver.php?id=rzpmgrk.sys
http://www.carrona.org/drivers/driver.php?id=rzpnk.sys
http://www.carrona.org/drivers/driver.php?id=rzudd.sys
http://www.carrona.org/drivers/driver.php?id=tap0901.sys
volume.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
wcifs.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
wcnfs.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.

 

I have managed to delete the driver for the NVidia onboard graphics and changed it to standard dual channel pci ide controller and it hasn't loaded back after a pc restart so I'm going to try that to see if the BSOD comes back.

 

Update: Since deleting the Nvidia onboard graphics driver, I haven't had a BSOD for a while now. Hopefully it should have been solved but I will update if anything changes.

 

That'll be the Nvidia chipset drivers

Give it 7-10 days before relaxing, I'm still not sure they were the cause, perhaps they were left holding the smoking gun.

 

I think it was updating drivers for my PCIe Nvidia Grahics Card Drivers but not the onboard graphics and also it was using nvstor but since deleting it everything has calmed down.

 

Okay, I think I'm following

With both AMD and Nvidia graphics, if there's any hint of a problem I clear them out and do a fresh install, drivers only. Not sure that's still possible with the latest Nvidia downloads, I haven't needed to dig that deep yet.

 

Update: still no BSOD as we speak I think the problem has defo being sorted out. Thank you for all your help.

 

Looking good then

BTW, was your previous graphics driver a update from MS? On my alt. PC, I've had issues with MS ATI/AMD graphics driver updates in both 1511 and 1607.

 

my asus GeForce GTX 750 Ti the drivers are through GeForce experience but it wasn't updating the graphics onboard with my motherboard. onboard graphics are Nvidia
GeForce® 6100 / nForce 405 but I have now disabled this and just running on graphics card.