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

Bit of an update since there's been no real response. New n vidia drivers helped a little; no more watchdog errors, meaning my bluescreens are just from video_TDR and have gone from once every hour or two to once or twice a day, sometimes skipping a day. Currently looking for another video card to test, as a just in case measure, if those remaining bluescreens might be a hardware issue that was already present, just not obvious in a more stable OS.

 

I haven't replied here in a bit, but I'm gonna try once more and give some updates to see if anyone has anything new they can suggest.

New things I've tried.
*Using an older Nvidia Quadro card with similarly old (307) drivers. That DPC-Watchdog'd within 20 minutes of getting things booted up after all of the clean reinstalls and whatnot of the drivers (DDU was of course used beforehand).
*Upgrading drivers a few more times as newer ones have come out. No help.
*Removing one stick of RAM at a time, just in case it was one of them. On one of the times I removed one of the 2gb sticks, I got a DPC_WATCHDOG almost as soon as I had firefox going, so I figured maybe that stick was the problem.
*Switched it out, and with the second one, it lasted much longer, but then eventually got to a point where it kept lagging (like, the mouse and everything on screen would freeze for a few seconds), then going again, then lagging, to the point of not being able to do anything. I don't know if it's relevant, but System Interrupts was consistently using 20-25% of the CPU, even when I got down to the point of no applications being active.
(To note, neither of the above watchdog violations produced a minidump for some reason or I'd post them here, but I doubt they'd be anything new)

So, with that new information, can anyone give me any new suggestions? I've run memtest before and gotten an error unreliably (like, out of 5 times running for 9-10 passes, only one gave me an error, and I could never repeat it), but I sincerely doubt BOTH sticks of RAM are bad, especially because they've never caused Video_TDR bluescreens before Windows 10.

For the sake of fun I've reattached a new dump set, just in case you want something fresh to look over, but they look to be the same thing I've been getting (And to note, there's far less dumps there than have actually happened, from a combination of it just not writing sometimes to me getting impatient and hard resetting before a crash actually full resets on its own).

 

Hi Falco1029,

Are the dumps from 15th this month the most recent?

Please move some files from partition I to another partition to increase the free space to at least 10-15%.
Every partition needs at least 10-15% free space so Windows can do its thing in the background.


Warning Less free space could cause BSOD's .

You ran memtest, do you mean the built-in feature?
If so, please follow instructions below for running MemTest86+





Diagnostic Test

RAM TEST


Run MemTest86+ - Test RAM - Windows 10 Forums



Note



MemTest86+ needs to be run for at least 8 passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

Please try the following to test your GPU.
- Note the temperatures of your GPU when idle (before doing the test) and under load





Diagnostic test

GPU TEST


Run Furmark tutorial



Note Run Furmark for around 30 minutes



Warning Your GPU temperatures will rise quickly while Furmark is running. Keep a keen eye on them and abort the test if temperatures rise too high

 

The only partition with less than 10% space is an external drive. Could that honestly cause the problem? Either way, I'll move some files just to be safe.

As for memtest, I meant MemTest86+, the one you linked, and have already run it in the way I described. I haven't gotten an error on it in almost a year (tested earlier this month with 10 passes or so), but it's the same RAM, even if they never test positive anymore.

I'll run furmark later today, though, and see what happens. What should I be looking for?

 

As described in the tutorial artifacts

 

Wow, so, I can't believe I haven't noted this before. I sort of noticed it but I never actually posted it before. Whenever I move files around larger than like a gig at a time, it gives me a Video_TDR crash, almost reliably so.

Obviously, that just happened while I was trying to move some files from that external drive.

To note, I've tested all of my hard drives before with various tools (Manufacturer appropriate when possible), no issues, and this happens no matter what drive; in this case it was two externals, but it's also happened moving stuff between my primary and secondary, and from either of those to an external drive. Dunno if that helps at all.

Still gotta run furmark, at any rate.

 

Attaching the new dump I just got, as it's a DPC_WATCHDOG instead of a VIDEO_TDR, according to whocrashed, but still points at the nvidia driver. Figure it might make more sense to someone here.

 

FYI, the VIDEO_TDR_FAILURE means that the drivers weren't responding anymore and windows tries to get them working again. But the timeout is getting too much so the bugcheck is called to prevent any damage that may occur due to this problem.

Cause is the Nvidia Video driver.
Code: 2: kd> lmvm nvlddmkm start end module name fffff801`d3fa0000 fffff801`d4a93000 nvlddmkm T (no symbols) Loaded symbol image file: nvlddmkm.sys Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys Image name: nvlddmkm.sys Timestamp: Sun Sep 13 23:12:24 2015 (55F5E6B8) CheckSum: 00AB4A61 ImageSize: 00AF3000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4[/quote]

 

Right, I do get what a VIDEO_TDR_FAILURE implies, I just wasn't sure if the newer DPC_WATCHDOG_VIOLATION I got could possibly be related somehow, noting that it was a very specific thing (Moving large files across hard drives) that caused it, since it also claimed to be caused by the nvidia driver.

 

Furmark didn't seem to cause any artifacts so I don't think it's the video card itself.

I decided to run memtest again (Cus I'm a sucker for punishment) and it froze during the test; everything stopped but the + blinking (which I know happens automatically even if your CPU is on fire). Is memtest freezing akin to a failure or does it mean something else entirely is wrong?

 

It might be due to some things that have to do with the memory.

Please download and install Speccy.
When you have installed and opened Speccy, click on RAM and click SPD -> Slot #1 (every slot) -> Timing table, please make a screenshot of it and post it
It looks like

 

Alrighty, here ya go:

Attachment 39538

 

Please try the following:

• Shut down your computer
• Once the computer is turned off, unplug all power sources (AC Adapter then Battery)
• Hold down the power button for 30 seconds
• Plug power sources back in (Battery then AC Adapter)
• Turn your computer back on

This will reset your software connections between the BIOS and hardware, and it will also clear any memory corruption in the temporary memory (disregard the battery statements if you are using a desktop and not a laptop).

Please try MemTest86+ again when you've done this.

 

Alright, running that now (posting from laptop). I'll keep you updated, probably later tonight when it finishes 8 passes, or sooner if it still fails.

 

Alright, got through 8+ passes this time, no errors.