A few weeks ago i did a BIOS update on my Asus Z 170 D Motherboard from version 1702 to 2202. After that and a reboot my RAID 0 ( which was also my boot drive ) was displayed as failed. One of the two Samsung 950 Pro NVMe M.2 SSDs ( 256 GB each ) was displayed as Non-Member disk. So i did a a lot of research and found a really good guide on this site: http://blog.quindorian.org/2013/07/repa ... rted.html/ A how to repair guide for a similar problem ( similar because in this case the RAID 0 was not the Boot Volume )
But after talking to Quindor ( the nice guy which created that Blog and the How to ) i was confident that this guide would also work in my case. In theory.
First i bought a new HDD to install Windows and Testdisk on it. Then i followed the steps and re created the RAID 0 in the UEFI of my Motherboard and booted to my Windows on the HDD to use Testdisk. But here there was a difference between the Guide from Quindor and what was displayed on testdisk at my screen.
After that i guess i did some stupid things in testdisk and now i`m totally afraid that i have lost and destroyed my Partitions so, if somebody could maybe advice me what to do i would highly appreciate it.

If I understand correctly, your problem is that the D: partition is listed as RAW by Windows.
Use latest TestDisk 7.1-WIP, PhysicalDrive1, Advanced, select the partition corresponding to D:, Boot, RebuildBS, List.
If you see your files, choose Write, confirm, Quit and restart your computer.
If you have problems, please copy/paste the testdisk.log file content.

cgrenier wrote:If I understand correctly, your problem is that the D: partition is listed as RAW by Windows.
Use latest TestDisk 7.1-WIP, PhysicalDrive1, Advanced, select the partition corresponding to D:, Boot, RebuildBS, List.
If you see your files, choose Write, confirm, Quit and restart your computer.
If you have problems, please copy/paste the testdisk.log file content.

thank you Mr Grenier for your help.

I did what you recommended. But while Testdisk was working ( RebuildBS ) Testdisk closed it self without any message. So i was not able to click list. Any other suggestion?

A valid NTFS Boot sector must be present in order to access
any data; even if the partition is not bootable.
0 [main] testdisk_win 1744 cygwin_exception::open_stackdumpfile: Dumping stack trace to testdisk_win.exe.stackdump

Thank you very much for your advice, i really appreciate your helpfulness.
Have you seen the pictures on Imgur?
I guess i should tell you what i did to get to this point in.
I will try to describe and reconstruct it.

First i tried the Steps in Quindors guide ( the first mistake was using TestDisk 7.0 win 64 bit as i read it not correctly... "use only if lacking Wow64" )
After that i clicked, PyhsicalDrive1, Intel, Analyse, Quick Search, and then it showed me not one partition like in Quindors case but instead three partitions.
like this:
1 * HPFS NTFS 0 32 33 Size in Sector was little
2 P FAT 32 57 126 6 Size in Sector was also very small
3 P HPFS - NTFS 72 39 32 Size in Sector was really Hughe so i guessed this is my RAID 0 Partition and the other two something from Windows ( 100 MB & 450 MB big )

After Quick search i choose number 3 and "Write". After that i quited and restarted with first disconnecting the HDD an the windows on it.
It does not boot and give and error ( some Bluescreen wich told me to insert the (Windows CD/USB ) what i did. But it was not able to repair the two SSDs.
But the Windows USB did something because as i went back to the UEFI i saw two Windows boot Drives one was (intel Volume1) what should be my RAID 0 and one just named Windows Boot Drive ( 488000 MB ). After that i connected again the HDD rebooted in Windows and started again Testdisk.
This time ( and now i get much more stupid ) i run Testdisk with PyhsicalDrive1, and instead of choosing Intel i saw ( what i did not recognized first i guess ) the Hint from TestDisk "EFI GPT partition table type has been detected." So i thought ( with forgetting that i have some Linux and Mac VMWARE Virtual Maschines for testing on the RAID 0 ) i should try this one. So I choose EFI GPT, Analyse, Quick Search and then choose Write on all three ( ) partitions.
After i reboot and disconnecting again the HDD nothing worked. No Bluescreen just a blackscreen from windows in which it said something with the Boot drive is not okay.
So i reconnected and rebooted and run Testdisk 7.0 again but this time choose to PhysicalDrive1, Intel ( i recognized one of my failure ), Analyse, Quick Search and write on all three again. ( i know that there a lot of facepalms from you know). Well, Same procedure again shut down, disconneted the HDD reboot and again a bluescreen from windows with some instructions. Nothing worked.
So i shut down again, conneted the HDD to reboot windows and did a little research as i saw now the PhysicalDrive1 and D: ( and D: in in RAW )
so i tried to use this guide http://us.informatiweb.net/troubleshoot ... ition.html
and switched
1 * HPFS NTFS 0 32 33 Size in Sector in Sector little ( i don't remember the correct Size )
2 P Fat 32 57 126 6 Size was little
3 P HPFS NTFS 72 39 32 Size in Sector big

to
1 P HPFS NTFS 032 33
2 P FAT 32
3 * HPFS NTFS Size in Sector big

and then again Quick search and choose write.

And then i recognized i'm lost and searched for this forum to find some help.

I have downloaded Testdisk 7.1 now ( the right version for windows ) and took the steps that you recommended.
Any other recommendation Mr Grenier?

You can try
- run cmd, right click run as administrator) and next chkdsk /f d:
- try testdisk, advanced, list from a Linux LiveUSB (see https://www.cgsecurity.org/testdisk.pdf for details)
- if nothing works, use photorec on this partition, choose [Whole] instead of [Free]

cgrenier wrote:You can try
- run cmd, right click run as administrator) and next chkdsk /f d:
- try testdisk, advanced, list from a Linux LiveUSB (see https://www.cgsecurity.org/testdisk.pdf for details)
- if nothing works, use photorec on this partition, choose [Whole] instead of [Free]

I am forever in your debt for helping me through this tough time, thanks so much for taking the time to help with my problem.

cgrenier wrote:You can try
- run cmd, right click run as administrator) and next chkdsk /f d:
- try testdisk, advanced, list from a Linux LiveUSB (see https://www.cgsecurity.org/testdisk.pdf for details)
- if nothing works, use photorec on this partition, choose [Whole] instead of [Free]

Hello Mr. Grenier,

i tried to run cmd and chkdsk /f d:
but i had no success.

Then i tried a Linux LIveUSB (Fedora) as you recommended but the problem is testdisk and the fedora live usb can not recognize the raid. I guess, without the intel raid driver its not possible. Do you know how i can install the Intel Rapid Storage driver on the Fedora LiveUSB?

Also i have taken some screenshots from which maybe you can see what the real problem is with the raid.
When i am analyzing with Testdisk 7.1 the raid, the partitions are listed double. Also in my UEFI BIOS there are two RAID SSD listed, but i have just one. As you can see in the UEFI screenshot there is a "Windows Boot Manager Intel Volume1" (my raid) and a "Windows Boot Manager 488392MB" which is obviously also my two SSDs in raid.
Do you know how to solve this? Is there any solution for this?