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
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).
Last edited by Falco1029; 09 Aug 2015 at 05:24.
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+
Run MemTest86+ to analyse your RAM. 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
Run Furmark for around 30 minutes
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?
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.
Quote