Windows 10: nvlddmkm error in event log

I have problem
Getting nvlddmkm error in event log
Try update nvidia driver but the problem still continue 388.00- 388.13-388.31
How to fix the problem?
whether this can be caused by ram?
I installed 3 ram Samsung
2x 8GB M471A1K43BB1-CRC
1z 16Gb M471A2K43BB1-CRC

Imgur

I did not experience bsod / bluescreen. but event log always shows error

:)

 

Seiki 4K TV randomly shows "Not Support" when turned on - must add/remove second monitor + reboot

Downgrading didn't solve anything. I searched through the system event logs and noticed this error: "Display driver nvlddmkm stopped responding and has successfully recovered."

I'm trying some of the solutions listed on
this thread.

 

frequent windows event 4101(Display driver nvlddmkm stopped responding and has successfully recovered.)

Having the same exact issue in bf1, second monitor goes dark then game freezes.

In event log getting

the 4101 event

Display driver nvlddmkm stopped responding and has successfully recovered.

 

Imgur: The most awesome images on the Internet

 

Are you talking about errors like: "Display driver nvlddmkm stopped responding and has successfully recovered."

If so I have read about and tried TdrDelay registry tweaks and a bunch of other crap but have never found a proper fix. The only thing that has worked for me is down-clocking the video card. Even if it is not "over clocked", almost all are factory over clocked these days and often unstable at those "stock" clocks except for the rare cream of the crop chips.

I would try nvidia inspector (1.9.7.8 latest?) if you don't already have some other utility for clock speeds and under-clock it a bit. Try somewhere between Nvidia's reference stock speed and whatever the manufacturer/factory over clock is, or just knock off about 40-100 MHz at a time and see if it stabilizes. If is does, you know what the problem is, and you can decide to run under-clocked or go into RMA HELL until you get lucky enough to get the "perfect" card that is actually stable at factory OC speed...but good luck with that, I just run mine at a stable under-clock unless it is significantly lower than acceptable (whatever that is for you).