Windows 10: Multiple Bluescreens (DPC_WATCHDOG, VIDEO_TDR) after upgrade

Hello! I've been having issues after upgrading to Windows 10, so I figured I'd see if I could find some answers about it here.

Essentially, ever since I upgraded, my computer (which has had its issues in the past, admittedly) has been crashing repeatedly, multiple times per day, exact amount varying with what I'm doing. The most common error according to WhoCrashed is Video_TDR_ERROR, followed by DPC_WATCHDOG_VIOLATION, and HAL_INITIALIZATION_FAILED.

I've noticed it crashes more often when playing a flash video or similar streaming, followed by media players, and then even sometimes when just browsing the web. The majority of the time, it will freeze first, repeating a sound loop varying from a split second to a full second or so until it finally bluescreens.

I've taken the following steps so far to try fixing it, after some google searching:
*Rolling back Nvidia drivers to .30
*Completely removing the nvidia drivers with the uninstaller utility, and then reinstalling them again
*Reinstalling sound drivers and wifi drivers.
*SFC checks, and DISM even when nothing was found
*Hard drive repair (Check disk and seatools)
*Virus scans

But no luck so far. I'm assuming it's driver/software related based on what I know of the errors and the timing of it all.

As a side note, I can't change back to 7 right now, it's a long story that basically comes down to the files getting deleted when they shouldn't have been. I'd also prefer to avoid Restoring, as that removes all programs (Effectively, I don't have any from the Store), which defeats the purpose of upgrading instead of doing a clean install, unless someone knows of a 'repair' installation option like Windows 7 had, that keeps ALL programs installed, but I can't find anything like that.

Attached the generated archive.

:)

 

DPC_WATCHDOG violation BSOD Windows 8.1/10

I am experiencing multiple BSOD's with the message DPC_WATCHDOG Violation. This has been happening since I upgraded to Windows 8.1 and has continued since upgrading to Windows 10.

My dump files are on OneDrive

082315-20828-01.zip

Please can you have a look and give me some indication of where to start looking?

Regards

Chris Fry

 

Issue upgrading to Windows 1709, Fall Creator Update

I performed a clean boot a few times now, tried updating multiple times, and have had no luck thus far. I've used the Windows Update fixer while in clean boot, the upgrade helper while in clean boot, and tried the basic updater. It will reboot, begin updating,
then reboot, bluescreen, reboot, bluescreen, rollback, back to 1703. The error I get on the bluescreen is ERROR EXCEPTION NOT HANDLED or something like that.

 

Hey, had a couple more crashes, seemingly in the same vein as the others, but I went ahead and got those collected too, since you never know!

 

Just to note, I've also now gotten crashes when doing something as simple as moving files around. I won't bother updating the new crashes as 1) I'm on my laptop right now and 2) It's just more of the same, I doubt it will help. But let me know if you'd rather have the extra ones!

 

The Video_TDR_ERROR and DPC_WATCHDOG_VIOLATION are definitely GPU related (I suffer from the DPC_WATCHDOG_VIOLATION myself on a GTX 750), and honestly I don't think there is much you can do at this point. Each driver for windows 10 to date has had memory issues. SLI is basically useless atm due to HUGE memory leaks, and single card setups get BSODs with tags like this: "*** Memory manager detected 11 instance(s) of page corruption, target is likely to have memory corruption." Nvidia has to sort that out, I have posted in their forum and given feedback reports including debug results. Hopefully it is fixed in the next driver release, and until it is unfortunately I really have no advice to offer you. HAL_INITIALIZATION_FAILED can also be caused by faulty drivers ( but I haven't seen this on in the windows 10 drivers personally) but the most common cause is corrupt registry entries. You could start by running a system cleaner/registry repair tool (I Like CCleaner) and scanning with malwarebytes just to make sure there isn't anything funny going on.

 

I signed up just so I could post this, hopefully it helps you. I have been having a NVidia driver crash a few times a day since upgrading to windows 10. Particularly when I stream video.

I made the following setting changes I found someone had done on a windows 7 machine and I haven't had a crash since. So far it only has been a day though. It might be worth trying until they get a fix done, if it works for you.

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\GraphicsDrivers

TDrLevel = 0 (new 32 bit d-word if you don't have it)
TDrDelay = 2 (I believe this is actually default already, you might try adjusting it. same 32 bit d-word)

Help me configure registry correctly to solve TDR issue - Windows 7 Help Forums

I would recommend doing a little more searching if you want more info on what it does.

edit: here is the link to the different reg keys: TDR Registry Keys (Windows Drivers)

 

I've run Ccleaner on my registry several times now, and the hal crashes are most infrequent according to my list of dumps, so maybe that's fixed? We'll see.

As for the rest, win10guy, thanks, I'll give it a try and see if it helps! I'll keep you all informed.

 

I checked your 2nd dump upload, i didn't see any in it but figured I should mention it anyways. And fyi I have seen mixed results regarding adjusting the tdr keys int he registry, and even if it helps you a bit the drivers are still flaky so I wouldn't expect the DPC_WATCHDOG_VIOLATION to go anywhere til after they release a new driver (which may also affect the TDRs). Nothing is ever perfect on a brand new OS *Tongue

 

Changing the values doesn't seem to have helped with the issues caused when I move to many files at once or try to archive a huge folder (I wanted to try doing a bit of backup, I know, should've done it already, but ya know), it does this thing where it will slow to a crawl, give me a few seconds of responsiveness, then slow to a crawl again (can't move mouse, barely responds to typing, etc), and repeat that ad infinitum, though notably it doesn't crash, at least not right away, I even had time to restart my PC once.

WHen I get that PC up again, I'll upload the dump files I grabbed right before I had changed the values, as the last one in it is from me moving files, I figure maybe it's different somehow and might give another clue?

EDIT: And to note, I haven't tried anything graphics intensive yet to see if I get the same issue with that.

 

Ya, my error was different then his. Mine was also crashing in the middle of the night when i wasn't on my PC. I thought it was worth a shot, if it was semi related.

But I agree, we need a driver fix.

 

Checked the 'file moving' crashes in whocrashed and saw they were video_tdr too, despite a lack of a bluescreen.

Alright, well, besides waiting for Nvidia to fix their sucky drivers, is there anything else I can try, anything that pops up in my logs as a possible alternative cause, even if unlikely?

 

Alright, so, no guarantee it's working longterm, but thus far it's been working better than it had. What I did was install pre-Windows 10 drivers, specifically 350.12, as per a suggestion by someone on the Nvidia forums themselves.

Not going to call this 'solved' for certain until I've gone a couple of days without a crash and I've done more than watch some videos on it, but I'll let you all know.

 

Yes that is the current workaround I have seen people using both 350.12 or 347.88, I forget what the problems were with each but they weren't as serious as the issues with the current drivers... I think at least with 350.12 it was game specific? But it should hold you/anyone else over until they sort out their mess *Biggrin

 

Alright, got a new crash even though it took a lot longer than previous ones had, but it was another VIDEO_TDR. I used the log collector again, but should only be the most recent one that needs looking at.

Can someone please take a glance and see if it just seems to be the same typical Windows 10 stuff that I just happen to be incredibly unlucky with, or if maybe there IS some sort of a conflict on my system somewhere, given most people don't seem to have the same issues with the 350 drivers?

I checked the minidumps myself as best I could but I don't know what a lot of it means, or if anything other than the pointer to the nvidia drivers matters. I did try to follow the debugging guide but what it basically came down to was me only seeing the nvidia stuff and then that video_tdr has the usual fixes (which of course I've run through, past getting a brand new card, since I know this one works).