BSOD Ntoskrnl.exe windows 10

Jackster13 said:

So the only way to fix it is the driver verifier?

Well it is just a suggestion to try and flush out any faulty driver. Otherwise you just have to wait for more BSOD events and post up new files for us to look at. How frequently do you think they are happening now?

About every other day

here is the newest error list

I could not find any new BSOD files in this latest log.

Looking at the eventlog all I could see was a startup repair failed back on 29th Jan.

Code:

Event[17215]:
  Log Name: System
  Source: Microsoft-Windows-StartupRepair
  Date: 2017-01-29T11:22:22.406
  Event ID: 1121
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: DESKTOP-MGLGIS0
  Description: 
The following file necessary for Windows startup was corrupt: c:\windows\system32\drivers\ntfs.sys

Please open a command prompt and run sfc /scannow to see if any of your system files can be repaired.

didn't find any integrity issues. though when it ran the first time, it did BSOD. with a system thread exception not handled in the windows file manager.