I also am having a problem with running into CRC errors and Recuva aborting because of it.
I thought the errors were spawned because I had a failing RAM module (since replaced), so I ran chkdsk d: /r /x
Part of the resulting output is:
Free space verification is complete.
Adding 160 bad clusters to the Bad Clusters File.
Correcting errors in the Volume Bitmap.
Windows has made corrections to the file system.
976759528 KB total disk space.
0 KB in 1 files.
4 KB in 9 indexes.
640 KB in bad sectors.
95796 KB in use by the system.
65536 KB occupied by the log file.
976663088 KB available on disk.
Since I'd assumed that the CRC errors were actually introduced as a soft failure caused by the failing RAM module, I figured this would resolve my problem.
Since then, I've run Recuva on the drive again, and it again failed with a CRC error (though, far later).
Since I don't want to get stuck in a loop of running chkdsk to rewrite/mark bad sectors and then have more appear as I run Recuva across the drive, would it be possible to have an option in the Options settings such that you could have Recuva continue after ALL errors, but log them and let you know what files were affected?
Oh, I should mention that this process takes many hours for just chkdsk (and even longer for Recuva)... This is a 1TB drive!
Thank you for your help!
---- Edited ----
Additional information. I ran chkdsk again, and found no problems, but Recuva is still reporting a CRC error and aborting.
The debug log file is extensive, 4.4GB uncompressed, 3MB compressed... Where can I send it? (or do you want t clipping of just the start and end pieces of it?)