Hi. . .
The first dump output that you listed contained an ESET driver as the probable cause - https://www.sysnative.com/drivers/dr...d=em018_64.dat
Be sure that your ESET installation is up-to-date (most recent version is installed).
One of the other outputs showed a bugcheck = 0x24
and named the Microsoft file system driver ntfs.sys
as the probable cause.
Seeing those two together often indicates that there may be a problem with your HDD.
Run chkdsk /r
from a CMD prompt; re-boot the system. chkdsk will begin upon start-up.
If you have an HDD, run SeaTools for DOS, LONG test - https://www.sysnative.com/forums/har...agnostics.html
If you have an SSD, be sure that the firmware is updated. VERY IMPORTANT.
For info, ntoskrnl.exe
is the Windows NT Kernel and is never the cause of a BSOD. It is listed merely as a default.
Lastly, your BSODs contain varying bugchecks (STOP errors), which is usually indicative of unknown hardware failure as the cause. Unfortunately, the dumps are incapable of telling us the exact piece of hardware that has failed. Sometimes, it can point us in a direction, but that's about it.
Regards. . .