Can't boot, not even in safe mode due to INACCESSIBLE BOOT DEVICE

This is all that I could find about a possible reset. Most of the other websites indicate that consumers cannot reset the CRC.

Resetting Interface CRC Error Count Hard Disk Monitoring

It turns out that Hard Disk Sentinel can not remove errors like that. As it explians in the link you posted, it is just for getting Hard Disk Sentinel to ignore errors on the selected drive.

I did a chkdsk, with no paramters and it said there was an error with the MFT mirror. I took out the SSD, put it in an enclousre and connected it as external USB drive to another computer and ran chkdsk. It fixed the MFT error. I then did a chkdsk /f/r and it found no errors. I then put the SSD back into the old computer. After I booted, I ran a chkdsk with no paramters, which found no errors. Then I did another chkdsk/x/f/r. When Windows booted again, event viewer was showing the same write error again. Also another chkdsk with no paramters, showed the MFT error back again. "Detected errors in the Master File Table (MFT) mirror."

Do you have any more suggestions?

The drive seems to have problems with MFT mirror and with CRC.

It's unclear the impact of each or both combined.

Consider using a drive that does not have these problems as the primary drive on the computer.

I am cloning the SSD to a hard drive, to see if that makes any difference.

I cloned the SSD to a hard drive, but I get same error in Event Viewer after running chkdsk when I reboot. However, I just ran chkdsk with no parameters, so I could run a scan without rebooting, and it showed no issues.

Ignoring the chkdsk problem for the moment, I am getting a BAD POOL HEADER BSOD (but occasionaly it is PAGE FAULT IN NONPAGED AREA) when trying to boot with the hard drive or SSD in the new computer.

Also, as before, no minidump is saved when I get the BSOD.

If possible for debugging please post:
BSOD - Posting Instructions - Windows 10 Forums
or
C:\Windows\MEMORY.DMP

Unfortunately there is no dump file. If there was, I could probably sort out the problem myself, but Windows won't save one.

There are other ways to find the cause of dumps by viewing the logs within the DM log collector.
Sometimes when it appears that there are no mini dump files there are memory dump files etc.
When mini dump and memory dump files are created they can be accidentally deleted.