Here is more detail on my NTFS BSODs. I have a SATA disk as my C-drive, andI get lots of EventID 55 (NTFS) in the System Log. That EventId says that the C-drive is corrupt and needs a chkdsk. Windows schedules and runs a 12-minute "chkdsk c:" at reboot, and it always says "no problems found". After a BSOD the chkdsk finds index errors, which it corrects. Once, in 2013, I rebooted into XP ), and the chkdsk that ran said, "correcting errors in the upercase file". It did not tell me what errors were corrected, and I have no idea what the "uppercase file" is. The C-drive does not remain "clean" for long. Sometimes after a BSOD (Friday night or Saturday morning - more below), the system waits for me to logon. When I logon Saturday night I sometimes see that the C-drive has become dirty while the system was waiting for my login. When I start an incremental backup, I get an almost immediate EventID 55; when I start a full MSE scan on Friday night I also get an EventID 55. I did purchase and install SpinRite. I ran it at level 4 (16+ hours), and it reported no problems. Therefore I conclude that my SATA c-drive disk has no hardware problems.
Now on to the NTFS BSODs. I get these usually Friday night or Saturday morning during the full MSE scans. I have seen six so far his year and seven in 2018. I have full dumps and minidumps for each, and for each I have the output of windbg "!analyze -f -v". I obviously do not have the source code for ntfs.sys, and I do not know enough about the internals of Windows 7 to be able to do anything more with windbg and the dumps.
I hope that I have all of the desired information in the attached ZIP file.
Thanks.