The Non Xmas Xmas Film Is On...
Film, Media & TV0 min ago
Nvlddmkm
23 Answers
This is related to questions I have posted previously.
I'm getting a game freeze/crash on a regular basis. On checking the logs I find this nvlddmkm seems at the root of it, or near to it. Have been trying various things to try to stop it to no avail.
(Nvidia is convinced it isn't their driver; the graphic card fans are all working fine and the temperature plateaus at 80° C anyway according to a graphics test I downloaded. Have no reason to think the power supply isn't fine. Game options set to minimum everywhere makes no difference. Neither does unplugging one of the monitor displays. RAM test shows no problem, but more RAM is on order anyway.)
Against my better judgement, since I was told it was a Win 7 issue at one site, I opted to upversion to Windows 10 a few months earlier than I intended.
So far two issues :
a) nvlddmkm is still an issue. The logs / log screen looks different but digging in it is the same problem ! "Display driver nvlddmkm stopped responding and has successfully recovered." Their idea of recovered is that it managed to get control back to the user but the game still has a white screen and has to be closed via the task manager again.
b) Despite all claims that all my files will remain where they were, it seems to be a lie. Outlook 2003 is not finding a datafile containing older e-mails,and which I often look into to check things. I tried searching for *.pst (in a DOS window because the Explorer search is as useless as ever and pretends it can't find things) and I thought I'd found 2 possible files, but on adding them it turned out to be different paths to the same blessed file it was using as the current one !!! Any thoughts on what Windows 10 had done to it, and where it might be found ?
One tries to sort one problem and simply adds to them :-(
I'm getting a game freeze/crash on a regular basis. On checking the logs I find this nvlddmkm seems at the root of it, or near to it. Have been trying various things to try to stop it to no avail.
(Nvidia is convinced it isn't their driver; the graphic card fans are all working fine and the temperature plateaus at 80° C anyway according to a graphics test I downloaded. Have no reason to think the power supply isn't fine. Game options set to minimum everywhere makes no difference. Neither does unplugging one of the monitor displays. RAM test shows no problem, but more RAM is on order anyway.)
Against my better judgement, since I was told it was a Win 7 issue at one site, I opted to upversion to Windows 10 a few months earlier than I intended.
So far two issues :
a) nvlddmkm is still an issue. The logs / log screen looks different but digging in it is the same problem ! "Display driver nvlddmkm stopped responding and has successfully recovered." Their idea of recovered is that it managed to get control back to the user but the game still has a white screen and has to be closed via the task manager again.
b) Despite all claims that all my files will remain where they were, it seems to be a lie. Outlook 2003 is not finding a datafile containing older e-mails,and which I often look into to check things. I tried searching for *.pst (in a DOS window because the Explorer search is as useless as ever and pretends it can't find things) and I thought I'd found 2 possible files, but on adding them it turned out to be different paths to the same blessed file it was using as the current one !!! Any thoughts on what Windows 10 had done to it, and where it might be found ?
One tries to sort one problem and simply adds to them :-(
Answers
Best Answer
No best answer has yet been selected by Old_Geezer. Once a best answer has been selected, it will be shown here.
For more on marking an answer as the "Best Answer", please visit our FAQ.
-- answer removed --
Excel/Win 10 thing again.
Got back yesterday; had a good bash at this issue. It seems to me that, not only to MS have the arrogance to ignore the settings of the OS it was replacing, and setting things as if the whole world were Americans; it appears to me they have the same setting in more than one place. I had already changed some settings from US to UK, but I found a further one last night. Not easy, as control panel access is not obvious as it used to be in the previous versions. I ended up finding a link to it on some window that I finally came across. I've only just had a quick look at the spreadsheet that was getting messed up, and it seems corrected.
As for Nvlddmkm, I'll get back to that soon.
Got back yesterday; had a good bash at this issue. It seems to me that, not only to MS have the arrogance to ignore the settings of the OS it was replacing, and setting things as if the whole world were Americans; it appears to me they have the same setting in more than one place. I had already changed some settings from US to UK, but I found a further one last night. Not easy, as control panel access is not obvious as it used to be in the previous versions. I ended up finding a link to it on some window that I finally came across. I've only just had a quick look at the spreadsheet that was getting messed up, and it seems corrected.
As for Nvlddmkm, I'll get back to that soon.
Just thought I'd update as I'm still looking for the cause of this and I'm now reconsidering the temperature.
Speedfan shows me what is happening (I'm no expert using it) but the problem is that I don't know what temperatures are considered normal when a PC goes from near idle/ticking over to running an action game with decent graphics. I know I've checked the fans some time ago and ensured all moving freely and no fluff/dust. (It may have accumulated a little since I guess).
Not being a non-proportional font here, this probably will come out all skewiff but ...
_________________________ GPU __ System _ CPU __ AUX __ CPU __ Local _ Remote 2 _ HD1 __ HD0
Before launch ___________ 34°C _ 28°C ___ 38°C _ 26°C _ 31°C _ 31°C __ 31°C _____ 26°C _ 30°C
Game launched ___________ 43°C _ 28°C ___ 58°C _ 27°C _ 40°C _ 33°C __ 37°C _____ 30°C _ 30°C
Last save restored ______ 48°C _ 28°C ___ 58°C _ 27°C _ 48°C _ 34°C __ 50°C _____ 30°C _ 30°C
Battle started __________ 69°C _ 30°C ___ 60°C _ 24°C _ 66°C _ 43°C __ 67°C _____ 31°C _ 30°C
Crashed straight away ___ 64°C _ 31°C ___ 65°C _ 22°C _ 53°C _ 46°C __ 48°C _____ 32°C _ 30°C
Two columns labelled CPU. Is 53°C and 65°C ok ? Unsure why there are two anyway.
GPU went up 20°C to 64°C. Should I assume that's normal ? I have known it continue running at 73°C.
No idea what Remote 2 is either, and that got a little warm at 67°C.
But if all the fans are running well why would any of this be an issue ? Must be working as designed.
Keeping fingers crossed (in vain) for the table; here goes. {submit}
Speedfan shows me what is happening (I'm no expert using it) but the problem is that I don't know what temperatures are considered normal when a PC goes from near idle/ticking over to running an action game with decent graphics. I know I've checked the fans some time ago and ensured all moving freely and no fluff/dust. (It may have accumulated a little since I guess).
Not being a non-proportional font here, this probably will come out all skewiff but ...
_________________________ GPU __ System _ CPU __ AUX __ CPU __ Local _ Remote 2 _ HD1 __ HD0
Before launch ___________ 34°C _ 28°C ___ 38°C _ 26°C _ 31°C _ 31°C __ 31°C _____ 26°C _ 30°C
Game launched ___________ 43°C _ 28°C ___ 58°C _ 27°C _ 40°C _ 33°C __ 37°C _____ 30°C _ 30°C
Last save restored ______ 48°C _ 28°C ___ 58°C _ 27°C _ 48°C _ 34°C __ 50°C _____ 30°C _ 30°C
Battle started __________ 69°C _ 30°C ___ 60°C _ 24°C _ 66°C _ 43°C __ 67°C _____ 31°C _ 30°C
Crashed straight away ___ 64°C _ 31°C ___ 65°C _ 22°C _ 53°C _ 46°C __ 48°C _____ 32°C _ 30°C
Two columns labelled CPU. Is 53°C and 65°C ok ? Unsure why there are two anyway.
GPU went up 20°C to 64°C. Should I assume that's normal ? I have known it continue running at 73°C.
No idea what Remote 2 is either, and that got a little warm at 67°C.
But if all the fans are running well why would any of this be an issue ? Must be working as designed.
Keeping fingers crossed (in vain) for the table; here goes. {submit}
