Kingston SSD sudden fail and Partition sector doesn't have the endmark 0xAA55

[sidk85]

Hi, I have a Kingston SUV500/480G SSD drive which failed recently (overnight) without any warning or symptoms. It now shows up on the main screen of the BIOS but does not show up in the Boot screen. It's not detected by the laptop. On boot up of laptop I get the message please insert boot disk..... I am not able to see the details of this Kingston ssd in the BIOS.
So, I purchased a new SSD and connected the faulty Kingston SSD to a SATA-USB enclosure and then tried to access it in Windows 10. Unfortunately, it does not show up. However, it shows up in Testdisk.

This is how it shows up on Testdisk -
"
TestDisk 7.1, Data Recovery Utility, July 2019 Christophe GRENIER <grenier@cgsecurity.org> https://www.cgsecurity.org Disk /dev/sdb - 480 GB / 447 GiB - CHS 58369 255 63 Current partition structure: Partition Start End Size in sectors Partition sector doesn't have the endmark 0xAA55 *=Primary bootable P=Primary L=Logical E=Extended D=Deleted >[Quick Search]
"
I had just the one partition with Windows 10 installed on this faulty drive and i think it also had a small recovery partition. Unfortunately it cannot detect any now.
I don't know exactly what " Partition sector doesn't have the endmark 0xAA55 " this means.

I have tried the deeper search but that also does not detect any partitions. PhotoRec is also not able to recover any files. There are large files detected in strange unreadable formats.

I have tried other recovery software which just do not detect any files, if they do, most of them are large swf files ? or unreadable files.

Is there anything I can do myself without having to approach profession recovery companies ? I do not want to give the drive to any third party company as it has a lot of personal and important data.

Is there any hope for this drive based on the information described above ?

Regards

[recuperation]

Is there anything I can do myself without having to approach profession recovery companies ?

You can post the Testdisk log file here.
Has this drive been encrypted?

I do not want to give the drive to any third party company as it has a lot of personal and important data.

Is there any hope for this drive based on the information described above ?

Based on your problem description, the description of recovery attempts and the restriction of not being able to consult a professional recovery service I don't see big hope but in order not to miss a chance I asked for the logfile above.

[sidk85]

Thanks.

The drive is not encrypted. It had Win 10 Home installed.

Is there any specific option to generate the log?

Regards

[recuperation]

No, there isn't.
The first thing Testdisk does is to ask you if it should write a log file.

[sidk85]

" Disk /dev/sdb - 480 GB / 447 GiB - CHS 58369 255 63, sector size=512 - SABRENT , S/N:DB9876543214E, FW:0204

Partition table type defaults to Intel
Disk /dev/sdb - 480 GB / 447 GiB - SABRENT
Partition table type: Intel

Interface Advanced
New options :
Dump : No
Align partition: Yes
Expert mode : No

Interface Advanced

Analyse Disk /dev/sdb - 480 GB / 447 GiB - CHS 58369 255 63
Current partition structure:

Partition sector doesn't have the endmark 0xAA55

search_part()
Disk /dev/sdb - 480 GB / 447 GiB - CHS 58369 255 63
file_pread(5,2,buffer,937703423(58369/86/21)) lseek err Invalid argument
file_pread(5,1,buffer,937703423(58369/86/21)) lseek err Invalid argument
file_pread(5,2,buffer,937703424(58369/86/22)) lseek err Invalid argument
file_pread(5,14,buffer,937703426(58369/86/24)) lseek err Invalid argument
file_pread(5,3,buffer,937703440(58369/86/38)) lseek err Invalid argument
file_pread(5,3,buffer,937703487(58369/87/22)) lseek err Invalid argument
file_pread(5,8,buffer,937703503(58369/87/38)) lseek err Invalid argument
file_pread(5,11,buffer,937703550(58369/88/22)) lseek err Invalid argument
file_pread(5,2,buffer,937705472(58369/118/54)) lseek err Invalid argument

Results

interface_write()

No partition found or selected for recovery
simulate write!

write_mbr_i386: starting...
Store new MBR code
write_all_log_i386: starting...
No extended partition
New options :
Dump : No
Align partition: Yes
Expert mode : No
"

[recuperation]

That does not look good.

Check your drive's health as described here:
viewtopic.php?p=31986#p31986
viewtopic.php?p=31992#p31992