I'm seeing no signs of blue screening in the syslog but I do see reports of unexpected shutdowns. Nothing else we can gather so far. I did notice previously though that it reported it couldn't produce crashdumps because there wasn't enough space on the drive. Make sure the amount of free space on your Windows partition is at least the mount of your RAM and that your paging file set to be just as large plus set it so that the file exists on the Windows partition. Those are the best options to ensure that the system will be able to produce a crashdump when needed.
I recommend turning on Driver Verifier
. Do not
select the following checks: Force Pending I/O Requests, IRP Logging
, and Low Resource Sim
. Select all other checks. Make sure to restart system after you finish setup. If you experience a boot loop afterwards, go into Safe Mode by pressing F8 prior to Windows logo and disable DV there. Provide us any new crashdumps.
I reviewed your CrystalDiskInfo and I'm seeing both disconcerting and unusual values. However there's a good chance that this drive just has a very proprietary method of establishing SMART values which makes it difficult to interpret them. I normally would disregard this, but your symptoms lately sound similar to a disk I/O failure. Probably best to give that CHKDSK one more spin. If you see it correcting errors again as before, it most likely is conducive of a drive failure that's corrupting the file system on a continual basis.
However all this said is just speculation right now since we don't have any solid evidence to go on. Hopefully Driver
Verifier will help us weed out all unruly drivers
, but this is indeed sounding more and more like a hardware issue, which is most likely going to mean swapping hardware.