Windows 10: Help me with major crash postmortem analysis, where did it go wrong?

I dual boot, both disks are Win10 and are clones. I have used Macrium Reflect free edition for the disk cloning process and it has always worked very well.

Not this time. I got "This restore must be completed in the Windows PE rescue environment.". At the time I didn't get what PE stood for, nor why. I started another partition manager program although cannot remember with 100% certainty which one, likely AOMEI partition manager. And I repeat the procedure I wanted to run with Macrium Reflect. Disk copy. Except this one doesn't have any safety protocols other than giving a warning about "Your computer may become unbootable". I am thinking the software does not realize I have *two* disks, both bootable and by overwriting the clone disk, it thinks the machine will become unbootable, which is clearly an impossibility since I also have the *source* disks that cannot be affected by the disk copy operation. Was I wrong about that.

It presents "OK" to click on, I go right ahead, then it says so you want to reboot, the rest of the procedure will be completed in PE, which I again click OK. And it bounces. And comes back to the dreaded blue screen of "Your PC/Device needs to be repaired". It has become unbootable just like it said it would.

So I am thinking at that point, it is trying to reboot off the clone disk somehow, not the source disk. Then I discover a disturbing surprise that it is my *source* disk and the EFI partition is gone, and all the BCDboot entries are gone as well.

So my question are, where did it all go so wrong and how is it possible for the simple disk clone procedure to wipe out the source partition when clearly during the disk clone procedure, the source cannot be overwritten? Does AOMEI Partition Assistant have a huge bug in its "Disk Clone" subroutine? Where is the logic behind that? How can you copy from disk A to disk B and it blows your disk A?

I guess the only thing I am not sure about if in my UEFI configuration, I had RAID instead of AHCI and it thought the disks shared the same EFI partition and blew away both of them. The program damaged EFI on both disks, with the clone disk suffering even heavier casulaties, I think it wiped out the main data partition there, while the source only damaged the EFI.

I am really really disappointed.
And I am still not understanding why it did what it did, does not make any sense. It seemed like somehow during the boot process, both EFI, on source and on target, got involved in the system, in the active state and the partition programs, both Macrium and this AOMEI contraption got really confused. I told them to overwrite the target disk and they overwrote itself, but just the EFI partition for some reason.

The non-EFI partitions were not affected. It took me 4 days to recover this cluster-f. I was really upset. I tried to rebuild the EFI to non avail. None of the commonly known commands worked at all. Diskpart, etc. I booted into WinPE rescue and used all the tools there. They were sort of helpful but just could no get it to boot.
I ended up installing Windows on another drive,and making sure that booted - then copying the non-EFI (meaning the primary) partition from the damaged disk to the new disk with the fresh Windows EFI install.
And that did not work either until Windows had to fix it. Finally got back into it just recently.
What a journey.
Anybody care to shed some light on this? Especially if you have a dual boot system like an MSI Titan laptop.

This is the Disk Management layout FWIW:






:)

 

OFFICIAL   Dragon's Dogma: Dark Arisen (Review)

there is something wrong with suggested for you list on npu page. clicking on picture of dd:da review from suggested for you list leads to perormance analysis instead of review. hovering mouse over it shows in status bar correct link to review but clicking on picture reloads analysis.
links from reviews&articles page works fine.

edit: link from home page of npu sends you to analysis instead of review as well.

 

all games crash!

I suggest you run rthdribl > http://www.daionet.gr.jp/~masa/archives/rthdribl_1_2.zip
Increase the window size step by step and watch your vga temps permanently.
What happens?
If it crashes, run at stock speeds as suggested before and retry.

P.S.: When your system locks, does the display signal turn off after a time?
Stuttering sound or no sound at all when freezing?
What X1800XT model do you own exactly?

 

help to remote connect

not sure how to use both programs u 2 suggested, i need more helpful steps thanks