The RAID 0 is the most basically form of multi device striping.
If you have a (very small) filesystem that is made of 8 blocks (in this case blocks the size of the striping, not necessarily the device block size), you will have on a "normal" single disk blocks arranged as:
1st disk 1-2-3-4-5-4-7-8
When you create a Raid 0 you "stripe" the filesystem on two disks, and you will have:
1st disk 1-3-5-7
2nd disk 2-4-6-8
A destriped image is the result of taking the blocks alternatively from the two devices and arranging them as they would have been on a single disk:
In "normal" operation of the OS the RAID 0 (be it a hardware raid or a software one) is "transparent" to the user, but when it comes to data recovery, the tool in use may access the device(s) directly or however using algorithms that are not compatible with a non-sequential/multi-device arrangement.
If you prefer, once the two devices in a Raid0 have been destriped into a single image, the recovery process is exactly the same if there was not a Raid0, but rather a "normal" single disk/volume.
The reasons why *any* filesystem may fail can be mainly caused by:
- hardware failure <- which can be due to any of the two SSD involved malfunctioning or to one of the two channels to which they are attached (just as an example think what would happen if one of the two cables connecting the devices has a "false contact"
- software failure <- which can be due both to an issue with a Mass Storage driver in the OS or to an incorrect filesystem driver or to a "wrong" write operation caused by *any* malfunctioning software running in it or even to an issue of some kind in the firmware (please read as BIOS) in the case of a "hardware" RAID
Once you have accessed a device (or in your case a couple of devices) in DMDE, you do a "scan" to find which (parts of) filesystems it can find, each and every disk image that was saved as "RAW" (or as VMDK or as VHD/VHDX) on the original volume will be found (DMDE has no way to know it is an image and not a partition/volume).
It is your duty to find (since it was a single partition volume, from the info you posted, it will be easy) which volume is the "previous one" and select it for further analysis (the volume will be in your case the one which starts first and ends last, i.e. the one with biggest extents).
Depending on the actual reason why the corruption occurred and to the specific corruption that occurred (i.e. which areas of the filesystem were affected and how large are the affected areas) recovering a corrupted filesystem can be easy or downright impossible, no way to know in advance.
Then again, even if the filesystem is unrecoverable, single files in it may be either fully recoverable (contiguous files) or only partially recoverable or unrecoverable.
DMDE is a very powerful tool but it implies (besides studying attentively it's manual/help file) an underlying knowledge of the filesystem that you are going to attempt recovering.