Windows 10: System backup getting CRC Errors chkdsk doesn't see any problems

Hi All,In my system I have the following HD's:Samsung Evo 250 System C:Samsung Evo 120Barracuda 1TBWD Red 3TBI have full drive backups on my NAS mapped drives using Free File Sync to keep them up to date. I have been trying to do a complete system backup on a 4TB WD Passport.I've tried the WD prog, Acronis, DriveImage XML, and a couple of others. Every time it starts getting CRC errors probably 75% of the way through. DriveImage XML gets the farthest.It seems to be maybe on the 3TB drive but not sure. sometimes it stops on that drive, sometimes on the Barracuda. The SSDs backup really fast

:)

 

Macrium Image Backup Fails, due to CRC error first, now MFT errors

Hi

I had this problem when imaging a drive when migrating to win 10.

First check if something as simple as the cable.

Otherwise follow the Macrium suggestion which is to run chkdsk /r on the drive, then retry the backup, if you do it enough times it should finish the backup.

As a last resort there is an option in Macrium to ignore the CRC errors and finish the backup, but be aware when doing that you will have a corrupt backup. The default behaviour is for good reason, its to give peace of mind the backup is of good quality.

 

Macrium Image Backup Fails, due to CRC error first, now MFT errors

W-10 - Build 1903 ---

I must get an image backup, to replace the old 1 TB with errors, with my new 500GB WD SSD. I'm trying to use "Macrium 7.x Free", to back up to a known good USB. (I did an image to that USB from my other PC, = NP). i suspect that Window updates may have failed because of the CRC error that keeps being reported every few days.

Windows Event log does show 47 bad block errors, during all my PC us and backup attempts overnight. I can't read / tell which blocks, or if it is the same error.

Macrum's logged VSS error -->> After it told me the backup failed due to Error code 6 -- CRC Error, this was in the first attempted Image backup VSS log: NOTE: Windows Event Viewer has hundreds of this specific file error, over weeks (at least).

-- The 2ndBackup VSS log also failed with the same "Error Code 6". But, this time the log didn't show anything after normal VSS snapshot errata.

The drive has been throwing a CRC Errors on C: periodically. After searching, I ran Chkdsk C: /r /f after reviewing this thread for "Macrium Error Code 6".

Although I haven't looked extensively at Windows logs, I suspect that Chkdsk ran OK, since it was booted when it finally finished, hours later. But now, the backup still fails, and now it shows an "MFT bad error" instead of a CRC Error. The 3rd Macrium VSS Log shows nothing, other than the snapshot it took.
So, I decided it was a great place to stop, and ask for help, before I can't even boot and I corrupt the drive.

• Six months ago, i ran Crystal Disk, and couldn't see any significant problems, no "grown defects", or sectors mapped out, (at least by the drive).
• I can run Chkdsk C: /R as Macrium suggested when it reported the MFT error before shutting down the backup. But, seems I should check to status of boot, BCD, etc. before I do more. That link above, had a post that suggested that I should have Macrium verify "Boot status / partitions". I couldn't find anything in Macruim... Where is it??
• After advice from you guys, I thought I'd start with MiniTool Partition repair, since I had licenses to it a few years ago

Let me know what i should do next. I won't start fixing anything until I hear from someone.

 

CRC error

Ta for the links. I know why the CRC error occurs, but not how to get around it. to quote from the 2nd link: "If you encounter a CRC check error then either your program has changed or you are running a different version of ShareGuard Lock. There are 2 different CRC checks. The most common problem that you will encounter is the CRC error when you modify your program executable. ShareGuard actually records the original CRC of your file. NOTE: This only happens if you set the CRC check on in ShareGuard Locksmith. The loading of the CRC DLL is for checking the CRC of the ShareGuard Lock program. This CRC is always dynamically computed when you generate your parameters. If you receive a CRC error then just reset the Product Id from the Tools page of the ShareGuard Locksmith. The ShareGuard Lock will then automatically re-compute a new CRC for your program. This CRC value will always be enforced until you reset the Product Id. This is something that your customers cannot do but protects your software from cracking. You will always create a new product id so that a new CRC value will be computed for your next version release."

Looks like I might have to make my own installer as well *Bang Head :banghead: