New
#61
Well usually it is the mini dump (I think JT) that is sent but if in doubt just send whatever you have.
Well usually it is the mini dump (I think JT) that is sent but if in doubt just send whatever you have.
I now set the thing set up to make a Kernel Memory Dump...did not ask for a reboot, but I did. Plus I don't see where the .dmp file will reside in the Windows subfolder, there is clearly one there for minidump but that's all I see... where is it supposed to show up if in fact it does?
Thanks
J T
Last edited by Tinsby; 13 Jul 2017 at 15:18.
Hmm JT mate have a look at this because I have only (in the main) been looking at the mini dumps
Kernel Memory Dump | Microsoft Docs
ICIT2LOL, It would appear from that link that the folder will be created when there is a kernel memory dump. Until that time that folder apparently doesn't exist. It will be interesting to see what if any information will be entered there when I get the TDR message.
Thanks again, I will keep soldiering on, the truth is out there...or maybe it's here and I can't understand it!
J T
Well if the mini dump is not going to be created and it seem s if I am reading t right those other dumps are not either so where to from here maybe worth getting someone to have a look because you are stuck in the mud with both feet it seems.
I'll ask anyway I think as I am not real sure of just what to get what we want.
Hi ALL,
GOD I HATE THAT pop-up
9 times outta 10 its just the driver going squirrelly, a processing time llimit has been exceeded, had it on my lappy a couple times, and yeah i changed the Regedit value NO change.
Just learned to live with it, the latest Nvidea driver for me has resolved it, 6 months ago.
Roy
I haven't seen that pop-up in wellover a month now. I'm still convinced the problem was from a squirrily program or program update, possibly completely unrelated to the card, and has since been rectified.
Hi Roy,
If you look at my laundry list of items that I have done, changing drivers was job one and to no effect. # vid cards later and I still have the bloody thing popping up. I am not even using the newest driver, it doesn't seem that ANY of them will stop the darned error. Of course as I have said in a number of postings, my Linux Mint, on another partition doesn't have the problem, it may well BE THERE but Mint doesn't care about Timeout Delay Recovery, it just runs. I've been putting up with this BS for almost a year now and the novelty has long since worn off.
I see no way to sort it out other than an entirely new system MOBO and all, then I am stuck with tons of software that won't play nice on W10,So that's not a viable option financially and otherwise.
Again, look at my list of attempted fixes and tell me what I've missed! Everyone here has been as helpful as they can be, no complaints there that's for sure! :)
Thanks for checking in and letting me know I am not the only poor sob that has the problem. There are hundreds of links about it all over the web so it's clearly not that uncommon.
When I was an auto technician I much preferred working on a car that was totally dead, brought in on a hook. That's a hell of a lot easier to figure out over one that has been to 5 garages prior to you getting it. I only wish the machine would QUIT, then I'd have a clue what to do next, this intermittent crap is for the birds. Same as in the car business.
Did you have the same experience with your laptop. IE: It might run for days and you never see the message, and then the next day you get it 2 or 3 times or more? That's what goes on here,, truly maddening
Cheers and best wishes,
J T
Hi Lady Fitzgerald,
Well I'm glad you got some resolution to it, at least for now. Time will tell if it's really fixed, mine would go for a week at times and not a peep of trouble, then lo and behold there it is again. It gets to the point that unless I am using Linux, I sit here waiting for the popup error to grace me with it's presence! <sigh>
Nice to hear that something, no matter what apprarently fixed yours. cross all your parts and hope it continues!
NB: Really the first posting I made I mistakenly used the wrong subject line it is not the video CARD!! Message says " Video driver xxx.xx has stopped responding but has recovered" Either that or it blames the file "nvlddmkm" in place of the driver number. I wish I could change the subject line but I don't see a way to correct it...any ideas? I surely can't start a new thread.
Cheers,
J T