BSOD nvlddmkm.sys

tristesse1 · 07 Sep 2015

I followed the instruction given and here is the full data zip

i already updated my GPU up till the latest ver. furthermore I always got BSOD after my ram exceeded it's "limit" (i.e. very heavy / up to 95% usage). but I don't know why the RAM keeps increasing incrementally the longer i keep my laptop on. This holds true even when I do not do anything. It seems that the memory is being constantly dumped by something that gobble up the free space until there is so little left and then voila~ I got the BSOD.

I think my laptop information on my profile would suffice, but I would be glad to offer more details.
This event started approximately 4 days ago.

I have looked up through all kind of general issues but still could not fix it
updating driver to its latest version,
rolling it back to previous version,
stress testing the GPU (FurMark)
and the laptops in general (Prime95) and both found no issue (I think if i read the report correctly)
(update) checking via cmd for file integrity as shown on another post on BSOD of similar nature (GPU)

Update: I added another attachment from CPU-Z report about my Hardware information

tristesse1 · 07 Sep 2015

essenbe said:

Hello, Nemecys. I'm not sure what the issue is for sure. For some reason we cannot open your dump files in the debugger correctly. What information I do get is that the issue is with your Graphics card or drivers.

I did notice you have Dameon Tools installed. Dameon tools is a well known cause of BSODs. I would recommend you uninstall it .

Daemon Tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known cause of BSOD's.

1. Uninstall Daemon Tools.

2. Download the SPTD standalone installer and follow these steps:

- Double click the executable to open it

- Click the button shown below

If the button it is grayed out, as shown in the image, there is no more SPTD installation on your system, and you can just close the window.

Also, open an elevated command prompt ( click start, type cmd in the search box, right click on the cmd entry and select run as administrator) in the black box that opens, copy/paste sfc /scannow. If you decide to type it, notice the space between the sfc and the /. It is a system file checker which will scan your system files and attempt to correct any missing or corrupt files. What we want are the results to say windows found no integrity violations. If it says files were found but could not be repaired, close the box, reboot and run it again, after opening the administrative command prompt. You may have to reboot and run it three times for it to repair all system files. If it can't repair them after 3 reboots, let us know.

taken from this post

i will post an update here just in case. I am doing what is suggested on running the scan on cmd.
maybe more info (I dont use Daemon)

tristesse1 · 07 Sep 2015

update

after performing cmd 3x (once then reboot, for 3x) it still cannot fix the corrupted file.. can anyone help ;w;

tristesse1 · 08 Sep 2015

bumping.... can anyone help ;w;

i still can't figure out the issue, but i did not get BSOD anymore.. (probably because i did not put the laptop on long enough), but the cmd scan still shows the issue (corrupted file)

tristesse1 · 10 Sep 2015

bumping still... can anyone assist >.<