| Previous | Next |
| ERROR_BAD_COMMAND | ERROR_BAD_LENGTH |
ERROR_CRC
An integrity check failed
ERROR_CRC is returned when a device or protocol calculates a cyclic redundancy check that does not match the received data. On local storage this can indicate damaged media, a failing cable or controller, or unreadable sectors. In communications it can point to corruption on the transport path.
What to collect
- Identify the exact file offset, sector, device, or packet involved.
- Check SMART data, controller logs, and Windows storage events.
- Repeat the read from a known-good cable, port, or machine when practical.
- Compare checksums with another copy before trusting recovered data.
Handling the failure
Do not overwrite the only copy of affected data during diagnosis. A retry may succeed for a transient transport fault, but recurring CRC errors should be treated as a reliability warning. Back up readable data promptly, replace suspect hardware, and restore corrupted content from a verified source.
References
Looking for a different code? Search another status or error code.