Windows 10 BSOD & lag

Sandissy12

Estimable
Sep 27, 2015
3
0
4,510
(specs: Samsung NP350V5C; Windows 10 64 bit; Intel(R) Pentium(R) CPU B970 @ 2.30GHz; 6 GB ram)

Hi! So, two days ago I had about 5 successive Blue Screens of Death ("system_thread_exception_not_handled (ntfs.sys)") on my Samsung NP350V5C notebook/laptop. This seems to have been the culmination of about a week of lag affecting my browsers and games, which have become frustratingly unresponsive at times.

Googling seems to indicate that this is a question of outdated drivers? I downloaded the Intel utility, which wasn't able to detect any drivers in need of updating. I then went to the driver's properties, and it too said my drivers were updated (running version 9.17.10.4229 installed in May 2015); however, looking at Windows Update history, there was a failed attempt to download drivers for Intel HD Graphics on the day that I installed Windows 10 (which I did on 14 August).

I experienced no problems during the first month of using Windows 10. Everything, in fact, appeared faster and more responsive! The only major addition since installing Win 10 has been cumulative updates for Star Wars The Old Republic. I've defragged my HD, run spyware and antivirus scans (AVG, Malwarebytes, and SuperAntiSpyware), checkdisk - all to no avail.

It's been so frustrating, and I really hope there's a solution. Thanks in advance!

 

Sandissy12

Estimable
Sep 27, 2015
3
0
4,510
Anything? This lag just refuses to abate. Right now, games are unplayable and videos are unwatchable (except on Youtube and local files). I apologise if bumping a thread is inappropriate, but I'm just at such a loss.
 

johnbl

Honorable
Nov 4, 2012
140
1
10,710
I would stop the search indexer service then delete the Windows.edb file. Then restart the search indexer service.
http://www.thewindowsclub.com/windows-edb-file

Then try to figure out why the database became corrupted. Look for update sata drivers, see if you need ssd firmware update, make sure the ssd has plenty of free space and boot it into bios and leave the drive powered but idle for a while to allow the firmware to run its garbage collection clean up routines.

Otherwise you could use resource monitor and figure out what is being accessed on your system. Then stop programs or services that are accessing the file until you can isolate the problem.