Acronis True Image 2017 (giving erros) vs Intel Data Migration (all good)
I have an Intel SSD as my main drive. Lately I have been getting startup errors (Windows 8.1 Blue Screen errors) so I decided to buy a new Intel SSD. I have a working Back Up (Clone through Acronis) Hard Drive which I use to clone new drives. When I clone this drive to my NEW SSD I get a Blue Screen errors (Header) and just won't boot. If I do the same process using the INTEL SSD MIGRATION software everything works fine.
Why is this happening?
Note: I tried cloning 3 times with ACRONIS to no avail. By the way I was using ACRONIS through the BOOT DISK


- Anmelden, um Kommentare verfassen zu können

Thanks for a very good explanation. Yes I was "cloning" with the BOOT DISK in UEFI mode. I will use your sector to sector Back Up in the Future.
Thanks again!
Cheers
- Anmelden, um Kommentare verfassen zu können

Rene,
Normally, sector by sector is not necessary, unless there is some disk corruption (bad sectors). I'd suggest running chkdsk /R on the source drive to see if it finds and/or repairs corruption. If it does, then a regular clone, or a non sector by sector backup and recovery should be fine. Sector-by-sector is much slower (and larger) since it backs up the entire disk and not just the currently used portion.
chkdsk /?
Checks a disk and displays a status report.
CHKDSK [volume[[path]filename]]] [/F] [/V] [/R] [/X] [/I] [/C] [/L[:size]] [/B] [/scan] [/spotfix]
volume Specifies the drive letter (followed by a colon),
mount point, or volume name.
filename FAT/FAT32 only: Specifies the files to check for
fragmentation.
/F Fixes errors on the disk.
/V On FAT/FAT32: Displays the full path and name of every
file on the disk.
On NTFS: Displays cleanup messages if any.
/R Locates bad sectors and recovers readable information
(implies /F, when /scan not specified).
- Anmelden, um Kommentare verfassen zu können