[SOLVED] Display driver nvlddmkm stopped responding and has successfully recovered.

[soderious]

Greetings everyone.

After i got my new ssd i did a clean windows 10 install. After that i have been getting some weird issues.

What exactly happens is whenever i browse/play a game that requires flash/play any game the monitor goes black, i can hear the audio in the background play but everything is still black. (monitor goes to sleep)

This usually happens when i first turn on my computer, yesterday i played PoE for 6 hours straight with no issues whatsoever.

In the event viewer i get this error : Display driver nvlddmkm stopped responding and has successfully recovered.

I have tried to reinstalling my drivers with DDU (425->418) but the problem still occured.

It happens rarely and if it doesnt happen within 1 hour after i turned on my computer than it wont happen at all. It's very rare.

What could the issue be?

Thank you all in advance!

 

[Quarkzquarkz]

Never use 3rd party installers and/or uninstallers. Go to Nvidia and download the latest drivers from there directly. Do a clean installation by checking the box and your issue usually comes from old outdated drivers that struggle to run newer games that haven't been optimized. I used to have the nvlddmkm error on my older laptop too but getting the newest ones solved that issue, Good luck!

 

[soderious]

Never use 3rd party installers and/or uninstallers. Go to Nvidia and download the latest drivers from there directly. Do a clean installation by checking the box and your issue usually comes from old outdated drivers that struggle to run newer games that haven't been optimized. I used to have the nvlddmkm error on my older laptop too but getting the newest ones solved that issue, Good luck!

I get my drivers from the official nvidia site. I installed the latest one after the format. After it happens, i can play For honor/R6S/CS:GO/PoE/Dead by Daylight without any issues for a lot of hours and it never happens after that. (sometimes it happens sometimes it doesnt, its rare. )

 

[Colif]

In the event viewer i get this error : Display driver nvlddmkm stopped responding and has successfully recovered.

it seems strange then that monitor goes off if driver recovers. I had something like this last year and in my case the driver wouldn't recover, wdm would try 8 times to get it to restart and eventually swap to basic display drivers that would result in monitor turning off.

mine was random, once every few weeks, hard to figure out problems that you can't create on demand. mine was fixed by replacing my mouse and not using a certain AV which just seems odd to me.

have a look in reliability history. any errors there around time PC turns screen off?

I have tried to reinstalling my drivers with DDU

possible other person didn't know what DDU (Display Driver Uninstaller) is. You could try running ddu and instead of using Nvidia drivers, run windows update and try the drivers they have from Nvidia - just old drivers from Sept 2017

 

[soderious]

it seems strange then that monitor goes off if driver recovers. I had something like this last year and in my case the driver wouldn't recover, wdm would try 8 times to get it to restart and eventually swap to basic display drivers that would result in monitor turning off.

mine was random, once every few weeks, hard to figure out problems that you can't create on demand. mine was fixed by replacing my mouse and not using a certain AV which just seems odd to me.

have a look in reliability history. any errors there around time PC turns screen off?



possible other person didn't know what DDU (Display Driver Uninstaller) is. You could try running ddu and instead of using Nvidia drivers, run windows update and try the drivers they have from Nvidia - just old drivers from Sept 2017

Hello colif and thank you for helping me out! i really appreciate it.

When the event viewer error comes up nothing else happens. The only error i see is that my driver stopped working and recovered succesfully.

I will try to use the win 10 drivers (388) and hope for the best.

Thanks again!

 

[soderious]

The issue occured again after 4 days. I was using the 388 nvidia drivers this time. It seems to happen only in the first 1-30m when i first turn on my computer. After that it doesnt happen no more and i can game for hours.

 

[soderious]

I found application event viewer logs that happen at the same time the black screen happens.


Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: dwm.exe
P2: 10.0.17763.1
P3: e52aabf3
P4: udwm.dll
P5: 10.0.17763.404
P6: c4744ab5
P7: c0000005
P8: 0000000000024149
P9:
P10:

Attached files:

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_dwm.exe_64c63045e5f75e429e721ed1da0429db13332e5_41746857_0be34a32

Analysis symbol:
Rechecking for solution: 0
Report Id: af2e2a2f-99bd-4d8b-aae8-94690b7148e4
Report Status: 4
Hashed bucket:
Cab Guid: 0

-


Fault bucket , type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 0

Problem signature:
P1: 141
P2: ffffa289bcbb0010
P3: fffff80313b4eb24
P4: 0
P5: 1b7c
P6: 10_0_17763
P7: 0_0
P8: 768_1
P9:
P10:

Attached files:
\\?\C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20190411-2046.dmp
\\?\C:\Windows\TEMP\WER-86815968-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC9FF.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCA0F.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCA0E.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCA2E.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_97e2b8d9f3bd67d45dba9d9c0c8a88a4861d2c_00000000_cab_22dcca8b

Analysis symbol:
Rechecking for solution: 0
Report Id: 62967155-bf8c-4f21-8e35-14f965e90eba
Report Status: 2049
Hashed bucket:
Cab Guid: 0

--

Fault bucket , type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 0

Problem signature:
P1: 117
P2: ffffdb07dc4ed0b0
P3: fffff805724de9f0
P4: 0
P5: 1ccc
P6: 10_0_17763
P7: 0_0
P8: 768_1
P9:
P10:

Attached files:
\\?\C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20190422-1212.dmp
\\?\C:\Windows\TEMP\WER-33409468-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDF86.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDF97.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDF96.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDFA7.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_117_358486dbf19a2d6430fbc0c38878947fcdb4d2cb_00000000_cab_1f99e003

Analysis symbol:
Rechecking for solution: 0
Report Id: a1c7a6e2-8a56-44e5-a33a-0ea3e32342bc
Report Status: 2049
Hashed bucket:
Cab Guid: 0

Currently im gonna try and format my computer and install the 1803 windows 10 version.

 

[Colif]

It seems to happen only in the first 1-30m when i first turn on my computer.

mine would happen at start up as well, or randomly at any time of day when I least expected it

App crash with DWM,exe is what I expected to see since screen turns off. DWM = Windows Desktop Manager
event 141 (63) is a reaction to PC restarting without being closed correctly. Its a reaction, not a cause.
The VIDEO_TDR_TIMEOUT_DETECTED bug check has a value of 0x00000117. This indicates that the display driver failed to respond in a timely fashion.

that looks like what I was getting, except you getting a BSOD, mine just stopped responding and turning off.

clean install might find cause, as if its is not the GPU itself, its possible reinstalling everything else will fix it or flush out problem. My last 2 fresh installs were done to fix problems and both times, it was only afterwards I found it was 2 of my peripherals.. speakers and a mouse.

 

[soderious]

mine would happen at start up as well, or randomly at any time of day when I least expected it

App crash with DWM,exe is what I expected to see since screen turns off. DWM = Windows Desktop Manager
event 141 (63) is a reaction to PC restarting without being closed correctly. Its a reaction, not a cause.
The VIDEO_TDR_TIMEOUT_DETECTED bug check has a value of 0x00000117. This indicates that the display driver failed to respond in a timely fashion.

that looks like what I was getting, except you getting a BSOD, mine just stopped responding and turning off.

clean install might find cause, as if its is not the GPU itself, its possible reinstalling everything else will fix it or flush out problem. My last 2 fresh installs were done to fix problems and both times, it was only afterwards I found it was 2 of my peripherals.. speakers and a mouse.

Lets hope for the best! before i reinstalled windows 10 i did a stress test aswell.

GPU : 72c - 30mins with furmark

CPU : 77c - 30mins with furmark

Nothing odd happend, everything was smooth.

(i used furmark after the bsod happend)

 

[Colif]

my hardware was stress tested running AIDA64 for 48 hours, its hardware was fine, it was just a weird software error. So yours appears to be similar.

 

[soderious]

Cleaned my gpu,reinstalled the 1803 windows 10 verison and it still happend. This time it happend 2 times in a row.

Is there anything else i can do? or is it safe to say that my gpu/psu is faulty?

 

[SkyNetRising]

Model names of GPU, PSU?
(I'm surprised, nobody has asked for any hardware info yet)

Anyway - gpu overclock could be causing this. If no manual overclock, then factory overclock may be at fault.
Dial down gpu overclock settings.

 

[soderious]

PSU : Seasonic S12II-430
GPU : N750-1GD5/OCV1 (GTX 750 1GB MSI OC EDITION)
CPU : i3 4170 3.7ghz


I never did any sort of overclocking to my computer.

This is a new error that now appears after the screen goes black on event viewer

Display driver failed to start; using Microsoft Basic Display Driver instead. Check Windows Update for a newer display driver.

 

[captaincharisma]

a 430W PSU does seem pretty weak to run a GPU like that even if it is from a reliable brand. please post your "full" system specs. i only seen bits and pieces of them throughout this entire thread which makes it hard to diagnose. also is this a prebuilt PC?

 

[soderious]

PSU : Seasonic S12II-430
GPU : N750-1GD5/OCV1 (GTX 750 1GB MSI OC EDITION)
CPU : i3 4170 3.7ghz
2x4gb ddr3 1600mhz sticks
1 120gb ssd and 1tb hdd

It's not a prebuilt system. I havent had an issue with the computer for 2.5 years. After i installed the ssd and formatted this started happening rarely.

 

[SkyNetRising]

GPU : N750-1GD5/OCV1 (GTX 750 1GB MSI OC EDITION)

Factory overclocked model (as suspected). GPU clocks are
boost 1137 MHz / base 1059 MHz

Nvidia reference clocks are
boost 1085 MHz / base 1020 MHz

Reduce clocks to Nvidia reference levels.

PSU is fine BTW. Nvidia recommends minimum 300W, MSI recommends 400W (for this card model).

 

[soderious]

That fixed my issue, thank you!