Windows 8.1: System Image Backup of C: drive fails, Error 0x8078012D and 0x8007045D

Anonymous
2014-01-04T23:16:08+00:00

Hello everyone.

I've a lot of people encounter problems similar to this, but here is my particular flavour:

I have a Windows 8.1. Pro (64 bit) desktop PC.

I am trying to use File History > System Image Backup to create a backup image of my C: drive.

I have been trying to save the backup both an external USB 3.0 drive, and this time to a network location (on a WD 'MyCloud' EX4 NAS)

Every time, the backup fails about 3/4 of the way through.

I get an error dialog saying

"The backup failed.  The operation failed due to a device error encountered either with the source or the destination. If the source or destination volume is on a disk, run CHKDSK /R on the source or destination volume, and then retry the operation. (0x8078012D)Additional Information: The request could not be performed because of an I/O device error. (0x8007045D)"

I've spent many hours diligently running CHKDSK /R  both on my C:\ and the destination drives, and it has never once found any problems.

I've tried closing all applications, unnecessary services, background processes and disabling Windows Defender's real time malware checking whilst the backup takes place, but that doesn't seem to fix anything.

My hunch is that there's nothing wrong with the disks or hardware at all, and that this is some kind of obscure permissions problem, where Windows can't access symbolic links on my C: drive.

But I basically haven't a clue! :) 

I'd be very grateful for any suggestions at fixing this, as currently I don't have any backup image of my C:\ drive, so if my PC goes kaputt, I'll have days of manual re-installing and configuring to do.

Thanks.

Windows for home | Previous Windows versions | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

190 answers

Sort by: Newest
  1. Anonymous
    2014-07-15T05:48:09+00:00

    I set Boot BIOS settings back to the way they were before I changed them to boot off of recovery drive

    Boot Tab

    a. Secure Boot            : Disabled

    b. Load Legacy Option Rom : Enabled

    c. Boot Option #1         : BootMGR

    d. Boot Option #2         : BootEFI

    I get following after booting

    internal hard disk drive not found

     to resolve this issue, try to reseat the drive.

    No bootable devices--strike F1 to retry boot, F2 enter Setup Menu, F5 enter PSA...

    The BIOS sees the internal 1TB drive...

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2014-07-15T05:36:40+00:00

    Need some help. Can't get system to boot after replacing mSATA and running reset using recovery drive.

    Replaced original 512GB mSATA with 1TB mSATA ( both Samsung ).

    Inserted Recovery Drive USB 3 stick created earlier.

    Powered up system, was getting continuous beeping sound, screen was solid black or blue.

    Did force shutdown via holding power button

    Powered up system

    a. messages says no boot drive or something

    b. Forced shutdown with power button

    Powered up system, held down F2 for setup

    Confirmed BIOS settings

    Main Tab

    * could see Samsun SSD 840 EVO 1TB mSATA ( 1000GB )

    Boot Tab

    a. Secure Boot : Disabled

    b. Load Legacy Option Rom : Enabled

    c. Boot Option #1 : BootMGR

    d. Boot Option #2 : BootEFI

    Exit Tab

    * Save Changes and Reset

    System booted off of USB Recovery Drive

    a. choose US keyboard

    b. choose Troubleshoot

    c. choose Reset

    Reset completed satisfactory, but I can get system to boot into Windows

    Using USB recovery drive

    a. selected cmd ( command line )

    b. diskpart

    diskpart> list disk

    Disk 0 Online  931GB GPT ( has *, guess than means it's active )

    Disk 1 Online 7552MB

    diskpart> list partition

      Partition 1 Recovery  424MB

      Partition 2 System    100MB

      Partition 3 Reserved  128MB

    * Partition 4 Primary   923GB

      Partition 5 Recovery 7157MB

    diskpart> list volume

    * Volume 0  C  Windows       NTFS  Partition  923 GB Healthy

      Volume 1     Windows RE    NTFS  Partition  424 MB Healthy  Hidden

      Volume 2     System        FAT32 Partition  100 MB Healthy  Hidden

      Volume 3     Recovery      NTFS  Partition 7157 MB Healthy  Hidden

      Volume 4  D  RECOVERY      Fat32 Removable 7551 MB Healthy

    D is USB recovery drive I created and am booted on

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2014-07-14T23:32:00+00:00

    That could be. I haven't seen any requirement for a ~39mb partition to use any of the Intel SRT but I could have missed something.

    Good to know you were able to make a Image with SRT in use. Maybe it is an issue with the way Dell has their factory Partitions set up. I don't have any way to test any theories out.

    Thanks for the info

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2014-07-14T22:36:42+00:00

    I looked in the 40 MB partition and it shows the icon of a drive and says diagnostics.  I believe it is the utility which can be started at boot to check the system.  Since I do not use Rapid Start, There would be no reason for it to be on this system.  Also, I have found nothing is the setup procedure for that technology which mentions needing a small Fat32 partition.

    The Smart Response Technology is more than the Fast Start Technology, but that is the only one for which additional software is needed.

    You are probably right about the 8GB partition.  I have no way of knowing if Dell intentionally set it as an OEM instead of a Primary partition, but I will check your links.

    I had no problem backing up my system with the Smart Response.  I had run that on a homebuilt system and it seemed to work fine.  I had not previously had any experience with the Rapid Start Technology.  The drives show as one drive because of the RAID, and I have not yet tried recovering an image.  I wanted to wait at least until the 30 day initial warranty period was over. ;)

    The comments about the System Volume folder may be relevant.  The error I got initially as different from what is being reported.  But I have seen threads where some restore points were corrupted, and one thread where there was 90 GBs of files in the one folder.

    Edit:  One of the links you provided does show the 8 GB partition as Healthy (primary partition), so the OEM designation probably means the partition cannot be used in its normal role.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2014-07-14T22:13:47+00:00

    I won't be able to comment about system image backup until I have a working system again. 

    But thanks for all suggestions and advice.  I'm learn alot.

    Was this answer helpful?

    0 comments No comments