DiskPatch Runtime error on SSD drive

[scooter79]

I have a 115 GB SSD drive running in a laptop that suddenly rebooted and since has displayed:  "No Boot Sector on Internal HDD (IRRT)  Missing Operating System <or> No Bootable Devices" 
Drive is running under Intel Matrix Storage Manager
I am not aware of any precipitating events, laptop was running normally in a docking station prior to event.
I first ran MBR_Tool.  Displaying the MBR for drive 0 shows no valid partition table (all zeros).
Attempting to 'Start DiskPatch' or 'Create a Support Analysis log' I get the following message:
"DiskPatch has encountered an unrecoverable error, all operations are halted to prevent damage.
Address: 78334
ErrorC: 11
Error Specifics: Unforeseen Runtime Error"
Is DiskPatch compatible with SSD drives?

I am able to successfully 'Create a S.M.A.R.T. Report' (Report and log files attached). 
I am writing the reports to a 2 GB USB flash drive that was inserted before booting with version 3.5.300 of DiskPatch from the full product suite ISO download.

Since then I have also attempted to recreated the partition table by using the Edit function in MBR_Tool and replicating the settings from what should be an identically configured system.  This has been unsuccessful and yields the same boot message.

System was running Windows 7 with NTFS partition

Apologize is this is a redundant post.  First attempt to post errored and wasn't sure if it actually submitted.

[attachment deleted by admin]

[Joep]

hello,

We can't read from it. I think it's dead.

[scooter79]

Gave it shot with iRecover.  I forgot to have it scan for missing partitions though.
It discovered a some "LostFiles" in what it did see.
Does iRecover read the partition table at all in doing its scan?
Would I be better off if I set the partition table back to blank (all zeros) instead of trying to guess at what it should be?
Other thoughts?
I guess we need to move this over to the iRecover forum...

[Tom]

The logs you submitted show nothing, meaning that no info could be gathered from the disk. From that we surmised that the disk was dead. If iRecover allows access and sees files, the situation is more complex. Even so, if iRecover gets you this far, give the recovery a try. That is, if you need files from that disk. I don't think repair is an option. Scanning for missing volumes isn't of much interest in this case; just analyze the entire disk and see what comes up. If there's anything good in the list, give it a go.