Windows 10: DPC Watchdog BSOD Windows 10 1607
I didn't mention in the screen shot post to, select search your computer for software (1st Pic), then pick list of device drivers from my computer (2nd Pic). Hope all goes well for you.
Ok i did the first part no update found here is some pictures
should i rename files before or after all this?
Last edited by DrSysop; 27 Sep 2016 at 18:47.
UPDATE: Ok i got it to work manually install have disk option on the nvidia nforce i saw 2013 driver version & updated it & rename the files before I updated it & well see now if it works as the IDE part i did also but same driver ok let see what happens
OK Another Update: FAILED! When I rebooted PC went right to blue screen asking for nvstor64.sys. I had to use my new installed win 10 & slave the drive & rename that .bak to sys & all good. I noticed on clean install there is no nvstor64,sys only nvstor.sys. Is this in a boot file i need to edit? Now before I did this earler I uninstalled the drivers & it asked me to reboot & i did then blue screen came asking for that file so I need to find a newer than 2009 nvsto64.sys. As I noticed its a 64 bit in windows\system32\drivers folder. I checked the Syswow 64 folder on both & nothing. This is all new since the Anniversary update & was fine on 1511. My son accidently used disk clean up & deleted the uninstall back to 1511. I was wondering if I got a copy of that on cd & installed it as upgrade if it will work & just need to get the 1511 if its still available.
Since I updated through IDE ATA/ATAPI it uninstalled nforce drivers from storage controllers. You should have had nvstor and nvstor64 in the drivers folder though, because you have 64 bit windows, but it would not have been used because of the driver update through IDE ATA/ATAPI.
ok so uninstall the nforce & Microsoft storage & then update auto ide part?
Just update IDE part. It then should by itself uninstall nforce from driver storage. Microsoft storage will remain.
Ok, I did this uninstalled all IDE then right clicked it & scan for hardware changes & it reinstall again. Now the nForce date in driver details says 9-23-13 version 10.6.0.23 date but the old nvstor64.sys date of 2009 is there in drivers directory but not show in nForce driver details now still so let see if this fixed it.
Last edited by DrSysop; 26 Sep 2016 at 19:19.
That's great! Good luck and hopefully all will continue to be well.
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.
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...
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...
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...
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...