Error Msg: BlInitializeLibrary failed 0xc0000001

Another Fix Attempt:

11. Maybe my process was flawed and I couldn't follow instructions so I attempted to create another SSD clone to a new Samsung Evo 850 1TB SSD drive that I bought on eBay. Well I created another SSD useless "brick", no boot, no nothing, same error message as before. Now I'm even more worried because I believed in my Acronis True Image 2015 (ATI2015) software build 6613. By now my wife and dog are now ready to leave me for being so technically stupid (LOL) and spending over $660 on two new 1TB SSDs that are now useless "bricks" (term "brick" like it just sits there doing nothing, not usable, or a building "brick").

Further Diagnosis:

12. Remember I couldn't boot the PC as long as the new ("bricked") SSD Drive B was attached. So my boot up CD hard drive tools or Windows hard drive tools were not usable. After several reboots I suspected the error message: "BlInitializeLibrary failed 0xc0000001" was from the Microsoft Win7 OS and not my motherboard AMI BIOS. I confirmed that after using the "delete" key to enter the BIOS that indeed my BIOS saw both my source SSD, my target SSD, and my CD/DVD drive. Aha ... a clue at last.

Solution:

13. Being a nerd engineer, I slept on the problem described thus far (thread above) and came up with the following approach that I would try next. It becomes a solution because it actually worked using two different methods and both worked.

Solution A:

Remove bricked SSD that has prevented PC from booting properly. Leave bootable source SSD and boot PC normally. Login as administrator. Attach brick SSD to an external adapter: USB 3.0 to SATA interface. Attach (i.e., live insert, hot insert, etc.) this to a USB 3.0 port of the PC. I used a Bytecc BT-390 USB 3.0/SATA adapter. Wait while OS discovers bricked SSD and shows up on Windows explorer, verify "cloned" contents are present. Use other software tools to display brick SSD partitions. I suggest you use Acronis Disk Director v11 or v12, or Microsoft's built-in Disk Management Tool, to view and delete all existing partitions found on the bricked SSD. Now create a new clone using whatever cloning tool you trust and start all over again. Sorry Acronis (ATI2015) after failing me twice, I chose to use the free Samsung Data Migration v2.7.1.0 software application to make a clone SSD this time. It worked like a champ and created a working bootable SSD. (I suspect the real problem cause was that I was confused by the restore options of the ATI2015 software app and selected a mix of parameters (MBR vs GPT, FAT32 vs NTFS, non-active vs active, boot vs non-boot, etc.) that would result in a non-bootable OS drive. See attached partition image file with my notations).

Solution B:

Follow solution A instructions above except use a SSD/HDD drive cage which supports "Hot Swap" of drives. I used an Icy Dock ToughArmor MB996SP-6SB Full Metal 6 Bay 2.5" SATA HDD & SSD Backplane Cage for 5.25" Bay. Insert (hot insert, hot swap, etc.) the bad brick SSD and the OS will discover it so your software tools can see the hosed partitions. I never really trusted these things but it actually works. I think you have to make sure your PC motherboard has a Intel RST (Rapid Storage Technology) compatible controller chipset and driver to work. Not all SATA chipsets may support "hot swap".

Final Conclusion:

14. Don't assume ATI2015 will over-write any and all partitions on a target drive when you want to restore a good known drive image to it (e.g., clone a SSD to another SSD). Yes, ATI2015 will let you make stupid choices on selecting partition parameters that may result in non-bootable drives. The OS and data partitions were good, just the boot partition didn't work, my mistake.

15. Always make sure your target drive has no partitions ("clean drive") with no residual MBR/GPT fingerprints, no old boot/OS/data partitions, only raw unallocated space! Use other software tools to remove any existing partitions such as Acronis Disk Director or Microsoft's built in Disk Management Tool, etc.

16. Hopefully by recording my bad experience above on this forum may help someone else in the future. Best of luck to you.