CRC Error: What a Cyclic Redundancy Check Error Means and How to Fix It
A CRC error means your computer tried to read data from a drive, disc, or file, checked that data against a built-in verification value, and found a mismatch — so it stopped instead of copying something corrupted. CRC stands for Cyclic Redundancy Check, a maths-based check computers use to confirm that data was read or transferred exactly as it was stored. When the numbers do not line up, you see messages such as “Data error (cyclic redundancy check)”, and the copy, download, or extraction fails.
The important thing to understand is that this error is almost never a software bug. It is your computer telling you there is a physical or data problem underneath: a drive that is starting to fail, a scratched disc, a loose cable, or a file that was damaged while downloading. This guide walks through the causes from least to most serious, and the safest order to try fixes — starting with the ones that protect your data.
What This Error Actually Means
Every time data is written to a hard drive, USB stick, or disc, the system also stores a small check value calculated from that data. When the data is read back, the calculation is repeated. If the two values match, the data is almost certainly intact. If they do not match, something changed or could not be read properly, and the system raises an error rather than silently handing you a corrupted file.
That self-checking behaviour is a feature, not a flaw. A photo that copies with one damaged section might open with grey blocks across it; an important document or program file damaged the same way could be useless. The error is the warning that stops that from happening quietly.
If you want the broader idea of how verification values work — the same family of checks used when downloading files — our explainer on checksum error covers the concept itself. This page is the practical companion: it deals with the drive-and-disc version of the problem, where the error appears while copying, opening, or extracting real files.
Where It Usually Shows Up
The error tends to appear in a handful of everyday situations:
- Copying files from an external hard drive or USB stick — the copy runs for a while, then stops partway on one particular file.
- Reading a DVD or CD — often older discs, or discs with visible scratches and smudges.
- Extracting a downloaded archive — a ZIP or similar file that refuses to unpack, reporting the error near the end.
- Installing a program or game — the installer fails at the same point every time.
- Opening a backup stored on an ageing external drive.
Which situation you are in matters, because the likely cause — and the safe fix — is different for each.
The Most Common Causes
A failing drive. This is the cause to take most seriously. Hard drives wear out, and one of the earliest symptoms is sectors that can no longer be read reliably. If an external or internal drive starts producing these errors on files that used to copy fine, the drive itself is often on its way out.
A scratched or dirty disc. DVDs and CDs store data in a surface layer that is easily damaged. Even small scratches can make one section unreadable, which is enough to trigger the error.
A bad cable or port. External drives depend on their USB cable and the port it plugs into. A damaged cable, a loose connection, or a failing port can corrupt data in transit, producing errors that look like a dying drive but are not.
A corrupted download. If the error appears only when extracting a file you downloaded, the file itself may simply have arrived incomplete — especially if the download was interrupted or your connection dropped midway.
A loose or ageing connection inside a desktop PC. Less common, but an internal drive cable that has worked loose can cause the same symptoms.
Fixes to Try, in the Safest Order
Work through these in order. The early steps are free, quick, and carry no risk to your files. The later steps deal with drives that genuinely have problems — and there, protecting your data comes before fixing anything.
1. Try a Different Cable, Port, or Computer
Before assuming the worst, rule out the connection. Swap the USB cable for another one, plug the drive into a different port (preferably directly into the computer, not through a hub), and restart the computer. If you can, test the drive on a second computer. If the same files copy perfectly with a different cable or machine, your drive is fine — the connection was the problem.
2. Clean the Disc (for DVDs and CDs)
If the error comes from a disc, take it out and look at the shiny side under a light. Fingerprints and dust wipe away with a soft, clean microfibre cloth, moving from the centre outward in straight lines — never in circles, which can drag grit across the data tracks. Light scratches are harder; some people have success with disc-polishing kits, but treat that as a rescue attempt for a disc you cannot replace, and copy its contents to the computer the moment it reads successfully.
3. Re-Download or Re-Copy the File
If one downloaded archive or file triggers the error, delete it and download it again, ideally on a stable connection. A fresh copy fixes the problem completely when the original download was interrupted. The same applies to installation media: re-download the installer rather than fighting with the damaged one.
4. Copy Files in Smaller Batches
When an external drive struggles, copying a huge folder in one go puts it under sustained strain — and one bad file stops everything. Copy in smaller batches, or file by file. This does two useful things: good files get safely across, and you discover exactly which files the drive cannot read. Those unreadable files point to the damaged area, and knowing which files are affected tells you how much is really at risk.
5. Back Up What You Can — Before Running Any Repair
This step is deliberately placed before the repair tools. If a drive is failing, every extra minute of heavy work can make it worse, and a repair scan is heavy work. So first, copy off everything the drive will still give you, starting with your most important and irreplaceable files: photos, documents, anything that exists nowhere else. Only when your data is as safe as it can be should you move on to checking the disk itself.
6. Run the Built-In Disk Check (CHKDSK) on Windows
Windows includes a disk-checking tool called CHKDSK that can find and mark damaged sections of a drive so the system stops trying to use them. The simple way to run it:
- Open File Explorer, right-click the problem drive, and choose Properties.
- Go to the Tools tab and, under Error checking, click Check.
- Follow the prompts and allow the scan to complete — on a large drive this can take a while.
Alternatively, the command-line version chkdsk /r does a deeper scan that also attempts to recover readable data from bad sections. Be honest with yourself about what this tool does: it can make a drive usable and sometimes recovers files, but marking bad sectors is a repair, not a cure. A drive that has started developing bad sectors usually keeps developing them.
7. Accept When It Is a Recovery Situation, Not a Fix-It Situation
If the drive clicks, grinds, repeatedly disconnects, or the errors keep spreading to new files, stop experimenting. Continued use can turn recoverable data into lost data. At that point your choices are to copy off whatever still reads, one patient batch at a time, or — if the data is truly irreplaceable and valuable — consult a professional data-recovery service and ask for their assessment before anyone opens the drive. For ordinary home files, though, most people find step 5 already saved everything that mattered.
How to Prevent It in Future
You cannot make drives immortal, but you can make sure an error like this is an inconvenience instead of a disaster:
- Keep backups of anything irreplaceable — ideally in two places, such as an external drive and a cloud service. A failed drive with a backup is a shopping trip; without one, it is a loss.
- Eject drives properly. Use the “Safely Remove” / “Eject” option before unplugging. Pulling a drive out mid-write is a classic way to corrupt data.
- Treat discs gently and store them in cases, out of sunlight and heat.
- Replace ageing drives on your schedule, not theirs. If a drive is several years old and starts behaving oddly — slow reads, strange noises, occasional errors — retire it from important duty while it still works.
Frequently Asked Questions
Is this error serious?
It can be. A one-off error from a dirty disc or a bad cable is minor, and the fixes above resolve it. But when a hard drive keeps producing it, that is one of the classic early warnings of drive failure, which is why the first priority is always backing up what the drive will still let you copy.
Can it be fixed permanently?
Only if the cause is fixed. A new cable, a clean disc, or a fresh download solves it for good. If the cause is a drive developing bad sectors, tools like CHKDSK can work around the damage for a while, but the drive itself will keep deteriorating and should be replaced.
Will CHKDSK delete my files?
CHKDSK does not set out to delete files, and the normal scan is safe for your data. However, when it repairs a badly damaged file system, some already-corrupted files may end up removed or recovered as fragments. That is exactly why you should back up everything readable before running it on a failing drive.
Why does the error always stop on the same file?
Because the damage is physical and fixed in place — a scratched spot on a disc or a bad sector on a drive. The copy proceeds normally until it reaches that exact spot, fails to read it after repeated attempts, and reports the error.
Can I force-copy a file that gives this error?
Some copy tools offer to skip or retry problem files, and retrying occasionally succeeds on a marginal read. But a file copied past the error may be silently damaged — a video with glitches, a photo with missing bands, a document that will not open. Force-copying is a last resort for files you cannot obtain any other way, not a fix.
