Direkt zum Inhalt

1st reboot after imaging with Acronis 2016--BSOD with error 0xc000000e

Thread needs solution

1st reboot after imaging Windows 10 system with Acronis 2016 resutls in BSOD with error 0xc000000e.  System is a controller, and is not connected to the internet.  Restoration from Acronis image does not correct the problem.  Use of Acronis recovery media on USB does not help at all. 

Does Acronis mess with the OS in some way we haven't been told about? How do I fix this?

Anhang Größe
img_2189.jpg 1.53 MB
0 Users found this helpful

Can you provide more background on exactly how you imaged and if the image was deployed back to the same system.

I get that generic BSOD about winload.exe missing when I have not selected the correct boot order in my bios on a Z170Z gigabyte mobo.  Took me forever to figure that out as it seems to suggest there's a bad file, but that's not really the case.  On this mobo, i have to always have "windows boot loader" as the first bios option when using UEFI install of Win10.  This board does not let you pick a specific sata hard drive in UEFI mode as I was accustomed to do doing on other older UEFI boards and all bios only boards.