e2fsck is only for checking and fixing errors in filesystem types
ext4. It can do nothing at all for NTFS. The
Bad magic number in super-block error message basically means "I cannot find anything at all that would indicate this is an ext2/3/4 type filesystem. If you are sure this is in fact one of those filesystem types, then you should probably try one of other superblocks as an alternate starting point."
But since you know this is a NTFS filesystem,
e2fsck cannot fix it.
Your CrystalDiskInfo results indicate the disk is in bad shape: 2829 disk blocks have already been replaced by a spare location because the original block no longer works, and there seems to be 65533 more disk blocks waiting for reallocation.
See here for more information about the "Current Pending Sector Count" value, and here about the "Reallocated Sectors Count" value. Basically, this is the last gasp of a dying disk.
The 2829 reallocated sectors are already bad enough that the "enough reallocated sectors to declare this disk as failed" limit has already been crossed, and the Current Pending Sector Count value indicates that the number of reallocated sectors is likely to increase by 65533 as soon as those failed blocks are either overwritten by the computer, or the disk itself manages to successfully read them even once.
If 2829 reallocated sectors is enough for the manufacturer to declare the disk as bad, then it is likely that 65533 more would completely overwhelm the reallocation mechanism, and the NTFS filesystem itself would have to begin tracking and avoiding the failing sectors, using its "bad clusters" mechanism. But the fact that there are already 2829 successfully reallocated sectors and 65533 more already identified as in need of reallocation indicates the failure within the disk is probably spreading, possibly quite fast.
Maybe one of the read/write heads has hit the disk surface, chipped away a bit of the magnetic material, and the resulting tiny chips are now bouncing around in the airflow inside the hard disk and occasionally getting jammed in between the read/write heads and the spinning disk, causing further damage and more loose chips. Maybe it's something else.
The bottom line is: this disk is not likely to be fixable. Some of the data in it might yet be recoverable, but any recovered data should be stored to a different disk. Any attempts to use the failed disk may make the disk worse as a side effect, so you should not power up the disk unless you're actually trying to recover data from it.
You should now make a honest evaluation for yourself: how much, measured in time, effort and money, are the contents of the disk worth to you? If there is something really valuable on the disk, you should consider contacting data recovery professionals instead of trying to do the recovery yourself.
Since you already know trying to access the filesystem in normal way is not going to work, you'll need something like PhotoRec: it will read the disk from the beginning to the end, attempt to recognize anything that looks like a valid video file, and copy that to a new disk. Yes, it is going to take a long time, but you should be able to let it run on its own.
I also note that CrystalDiskInfo reports your system disk is also in a "Caution" state. I'd recommend that you get two new disks, then clone your system disk to the new disk and replace it before it gets as bad as your current problem disk now is. Then use the other new disk for recovering data from the failed disk. Depending on what exactly CrystalDiskInfo says about your old system disk, you might still be able to use it for non-critical purposes, but you should not consider it reliable any more.