nvlddmkm.sys

[Diablo1099_v1legacy]

So since my last Advice thread asking about Kernal Traps, I've been plagued by this bastard of a error from my NVIDIA GeForce 840m on my Acer Aspire V.
I've tried everything from factory resets, uninstalling and reinstalling all my graphic drivers to testing my hardware (Nothing came up) and I can't get rid of this bastard of an error.

It's gotten to the point where even playing Fucking Hearthstone for too long causes a crash.

 

[Vendor-Lazarus]

I just had a bluescreen caused by nvlddmkm.sys, like 20-30 minutes ago.
I was watching an episode of VOY when it happened.
Got the IRQL_NOT_LESS_OR_EQUAL error and downloaded the Bluescreenview program where it pointed out that the Nvidia driver was faulty.

I've spent the last half-hour searching for a solution to the problem and the only way seems to be updating the driver to a more recent one.
I also used an air-can to remove any dust.
Have you checked that the nvlddmkm.sys driver in system32 is not older than the one in your Nvdida folder?

Finding a good Nvidia driver seems to be an entire exercise in itself as well.
The only non-"game ready" driver I found was 353.62.
If my error keeps popping up I will try that one.
Oh, better update your driver anyway, before they force you to download their bloatware of Geforce Experience when drivers becomes locked to it.

Could also be your OS or simply all the junk accumulated if your computer is getting on in years.
My latest Nvidia error was a WHEA one, and it was so severe that I had to return my computer to the store.
Luckily it was only a few months old and I got a new one for free.

Sorry I couldn't be of more help.

 

[Barbas]

Is there some sort of Nvidia control panel program on your laptop that you can fiddle around in, specifically to roll back to earlier drivers?

 

[Loonyyy]

I've had this problem before, but I couldn't fix it properly, I never worked out where it was wrong, or how to repair it, but I can add to Vendor's fix, for me, I tried downgrading the driver, no luck, I upgraded to a beta driver and that fixed it.

I'd recommend using the clean install option too, hopefully that helps to avoid leaving the bad file there.

Apart from that, I don't have anything, sorry I can't be more useful.