Skip to main content

Clone starts but then after a few minutes shows plain blue screen and reboots

Thread needs solution

After starting TI 2015 both from the Recovery Media boot disk and then from the Windows app, it goes through all the steps and then starts cloning. After just a minute or two, it goes to a plain blue screen and reboots the machine.

This is on a recent update to Windows 10 Creators (1703) with an Intel i7 and 9 GB RAM.   Both HDD are directly connected to the motherboard..

What is happening and how can I get a clone to finish?

0 Users found this helpful

Neal, how does your Windows 10 computer start in terms of the BIOS mode?  How are you booting the Acronis Rescue Media - does this match how your Windows boots?

See webpage: Check if your PC uses UEFI or BIOS for how to check the above.

You may need to disable Secure boot in your BIOS if this is an UEFI system (as most modern computers are) in order to boot correctly from the default (Linux based) Rescue Media (which is also the same as used when starting this type of operation from within Windows).

Please also see: [IMPORTANT] CLONING - How NOT to do this!!! for some words of caution about cloning.

Thanks, Steve.

I've been using TI for many years.   Some background:   

  • My previous PC was a 2015 Acer slim (no slots), UEFI with an older Pentium. TI worked OK in it. (Win10 1607)
  • Newly acquired PC is an older (2010) HP Pavilion Elite full tower with an i7, BIOS based, but it's 4 or 5 times faster than the Acer and has PCI slots (which are now needed).  (Win10 1703)
  • Normally boots from the HDD, but it boots from the Rescue Media if inserted.
  • TI starts and lets me select disks and then reboots, starts the cloning process, then after a minute, the display shows a blue screen (not the BSOD) and then reboots itself back into Windows.
  • Retried many times, same results.

 

 

Neil, thanks for the further information, I would suggest taking a different approach here and trying the Backup and Restore method instead of using Cloning.

Cloning has more restrictions / limitations than using Backup and Restore, i.e. it will not work with dynamic disks.

Another option would be to create the Windows PE version of the Rescue Media and try that instead of using the standard, Linux based, media.

In reply to by truwrikodrorow…

Thanks again, Steve.   I'll try the PE rescue media when time allows, though I know that Linux is fine with this machine, as I installed Ubuntu when I first got it.)

I've been cloning regularly because if infected with malware, I can reboot from a clone to a clean system.  This has saved my skin a couple of times over that years.

Making an image has been suggested, but I'm not sure one can boot from that mode.

Since my default HDD is Western Digital, and they have a free version of TI 2016, I wonder if that might help?

 

 

 

In reply to by truwrikodrorow…

Thanks again, Steve.   I'll try the PE rescue media when time allows, though I know that Linux is fine with this machine, as I installed Ubuntu when I first got it.)

I've been cloning regularly because if infected with malware, I can reboot from a clone to a clean system.  This has saved my skin a couple of times over the years.

Making an image has been suggested, but I'm not sure one can boot from that mode.

Since my default HDD is Western Digital, and they have a free version of TI 2016, I wonder if that might help?