About a month ago the Mint 19.1 on my Dell Inspiron notebook (dual boots with Win

started crashing on me. During booting I noticed there were brief flashes on the bootscreen with numerous error messages of something to do with ascpi?? (i believe it this may relate to Dell having issues with the way they monitor the power jack on notebooks??).
Then either the notebook booted to a command prompt, instead of the Desktop or it would boot into the Desktop but it was frozen and I had to press and hold the power button to shut down the notebook.
This boot issue happened about the time when I applied a Mint update that was showing and I believe the update did have a kernal update, included with the other updates.
The command prompt mentioned something about doing a fsck. So I had Mint 20 on a bootable usb thunb drive, I booted from the thumb drive and did a fsck of the sda9 partition that Mint 19 was located on.
There were a multitude of errors in the file system that I had to say yes to, and fsck fixed them.
Then I was able to successfully boot into Mint 19 again. However after a few boots Mint 19 again failed to boot or froze.
Kal suggested that because the Dell had an SSD and the computer was a number of years old, that the SSD partition that the Mint 19 was on, may have reached it's maximum number of read/write cycles.
The Win 8 on the notebook was able to boot and run without problem.
Kal suggested I download the repair/diagnostic software from the SSD manufacturer, to test the SSD. The Samsung diagnostic software for my model of SSD, Samsung Magician would only run under Windows and it would not recognize ext4 partitions.
So I wiped the Mint 19 partition and made it an NTFS.
However when I ran the Magician software it came up with various functions that it would do but when I ran the diagnostic part it said my drive was not supported???
So I used gparted to again make sda9 an ext4 partition and I booted from the Mint 20 usb thumb drive and installed Mint 20.1.
So far I have had no issues at all booting into Mint 20 and it works very well. :-)
Edit: I also ran a virus check with the ClamTK software, during this period of crashing and Clam did not find any problems.