Fix Data Error Cyclic Redundancy Check Without Losing Files

Data error cyclic redundancy check (CRC) is a Windows error that appears when you try to open, copy, or move a file from a hard drive, USB stick, or memory card. It usually means the drive has bad sectors or the file system is corrupted, and Windows refuses to read the data. This guide shows you how to get your files back without formatting the drive or paying for expensive recovery software.

What You’ll Need

• A PC running Windows 10 or Windows 11 (the steps work on older versions too, but menu names may differ slightly)
• A second storage device with enough free space to hold the recovered files (external drive, USB stick, or another internal drive)
• Administrator access to your PC (you’ll need it for the command prompt and disk check)
• Patience – the process can take hours on large drives

Step-by-Step

1. Stop using the drive immediately. As soon as you see the CRC error, do not keep trying to open the file or run other programs from that drive. Every read attempt can make the problem worse and increase the chance of permanent data loss.
2. Try a different USB port or cable (for external drives). A loose connection or failing cable can cause CRC errors. If the drive is external, plug it into a different port, ideally a USB 3.0 port directly on the motherboard (not a hub). If you have a spare cable, try that too. Sometimes this alone fixes the issue.
3. Run a disk check (CHKDSK) to fix file system errors. Open Command Prompt as administrator (press Windows key, type cmd, right-click Command Prompt, and choose Run as administrator). Type the following and press Enter:
   
   chkdsk X: /f /r
   
   Replace X with the drive letter of the problem drive (e.g., E:). The /f flag fixes errors, and /r locates bad sectors and recovers readable information. If the drive is in use, you’ll be asked to schedule the check for the next restart – type Y and restart. This can take a long time, so let it run overnight if needed.
4. Try copying the file again after CHKDSK. Often the CRC error is caused by a corrupted file system entry, and CHKDSK repairs it. Try to copy the file to your other drive. If it works, you’re done.
5. Use a file recovery tool to copy the data. If CHKDSK doesn’t fix it, the drive has physical bad sectors. Standard copy will fail at the first bad spot. Use a recovery program that can read around bad sectors. Open-source options like ddrescue (for advanced users) or GUI tools like Recuva or DMDE (free versions are enough) can often copy the data. In these tools, select the drive, choose the files you need, and save them to your healthy second drive. The software will retry bad sectors and skip them if unreadable, so you get back as much as possible.
6. If the drive is not recognized at all, try a different computer. Sometimes the issue is with your PC’s USB controller or drivers. Plug the drive into another computer and see if it appears. If it does, copy the files from there.
7. As a last resort, try a Linux live USB. Boot from a Linux live USB (like Ubuntu) and use the built-in Disks utility or ddrescue from the terminal. Linux is often more tolerant of damaged drives and may read files Windows won’t. This is more advanced, but it’s a proven way to recover data from a dying drive.

Common Mistakes

• Running CHKDSK on a failing drive and expecting it to fix everything. CHKDSK can repair file system errors, but it cannot fix physical bad sectors. It may also mark bad sectors as unusable, which is fine, but it won’t recover data from them.
• Formatting the drive out of frustration. Formatting will erase the file system and make the drive usable again, but it will also destroy all your data. Never format until you’ve tried every recovery option.
• Copying files one by one with Windows Explorer. Explorer stops at the first error. Use a recovery tool that skips bad sectors.
• Ignoring SMART warnings. If you see a warning that the drive is failing, don’t put off recovery. The drive can die completely at any moment.
• Using the drive for anything else while recovering. Don’t install software or save files to the failing drive – you’ll overwrite the very data you’re trying to save.

Tips

• Copy the most important files first. If the drive is failing, prioritize documents, photos, and other irreplaceable files. Don’t waste time on large media files that you can re-download.
• Use a recovery tool that supports “image” mode. Tools like ddrescue can create a full image of the drive, and then you can recover files from the image. This is safer because you’re not working on the failing hardware.
• Keep the drive cool. Overheating can worsen bad sectors. If the drive is external, place it on a cool surface and ensure good airflow.
• If you get a partial copy, check the file sizes. If a file is smaller than the original, it’s likely incomplete. Try to recover it again with a different tool.
• After recovery, replace the drive. Even if you manage to copy all files, the drive is unreliable. Use it only for temporary storage, and back up your data regularly.

Troubleshooting

• CHKDSK says “Access denied” or “The type of the file system is RAW.” This means the file system is severely damaged. Run CHKDSK with administrator rights. If it still fails, try the Linux live USB method – it can often read RAW drives.
• Recovery tool shows no files. If the drive is not detected, check the connection. If it’s detected but shows no files, the file system may be too damaged. Try a deeper scan in the recovery tool (often called “deep scan” or “raw recovery”).
• Copy starts but freezes. This is normal – the drive is struggling. Let it sit for a few minutes. If it’s still frozen, cancel and try a different tool that handles bad sectors better.
• You get a CRC error on a DVD or CD. The disc is scratched or damaged. Try cleaning it with a soft cloth, and use recovery software like IsoBuster (free trial) to read it.
• The drive makes clicking or grinding noises. Stop immediately. The drive is physically failing. Professional data recovery may be the only option, but it’s expensive. If you must try DIY, use the Linux ddrescue in “read-only” mode, but be aware you could cause more damage.
• After recovery, the drive still shows errors. It’s likely beyond repair. Use it only for non-critical data, and back up everything important.

Frequently Asked Questions

What exactly is a cyclic redundancy check error?

It’s a checksum error. When data is written to a drive, a small checksum is stored alongside it. When reading, the drive recalculates the checksum and compares it. If they don’t match, it means the data is corrupted, often due to bad sectors or physical damage.

Can I fix a CRC error without losing data?

Yes, in many cases. The steps above – especially using recovery software – can retrieve most or all of your files. The key is to stop using the drive and start recovery immediately.

Is it safe to keep using the drive after fixing the error?

If the error was due to a temporary glitch or file system corruption, the drive may be fine. But if it’s caused by bad sectors, the drive is failing. Back up your data and replace it as soon as possible.

Why does the error happen on a new drive?

New drives can have manufacturing defects. Also, a bad cable, a faulty USB port, or an improper shutdown can cause CRC errors. Try a different cable and port first.

Will formatting the drive fix the CRC error?

Formatting will remove the file system and allow you to use the drive again, but it will erase all data. It doesn’t fix physical bad sectors – the drive may still have issues. Only format if you don’t need the data.

Can I prevent CRC errors in the future?

Back up your data regularly, safely eject external drives, avoid physical shocks, and monitor drive health with tools like CrystalDiskInfo. If you see warnings, replace the drive.

Related

• Essential Work From Home Gadgets for a Better Setup
• AT&T Cheap Internet: Plans, Eligibility and What to Expect
• TV Shows June 19–21: Sugar and House of the Dragon