windows 7 - how to detect file corruption?

08
2014-07
  • user150951

    Sometimes, my files become corrupted without me noticing - this happens to my photos a lot. This doesn't bother me when I notice it because I have backups. It's growing to be a pain to manually go over all the photos from time to time (I have tens of thousands). What can I do to automatically detect if a file has been corrupted?

    So far, the only method I have found is to use MD5 checksums. But I haven't found a way to automate this.

    For example, if I have a folder with 500 pictures, how I do determine if the MD5 checksums for the photos have changed since last time I checked?

    • Answers
  • Der Flatulator

    I haven't used this software before, but I believe it to be a valid answer to your question.

    http://corz.org/windows/software/checksum/

    [...] providing secure verification against tampering, virus infection, file (and backup file) corruption, transfer errors and more, digital fingerprints can serve as an "early warning" of possible media failures, be they optical or magnetic. [...]


    • Related Question

    windows 7 - Cause of file corruption on Lenovo T60
  • rwb

    What would be possible causes for corrupt Windows 7 system files? We have 5 Lenovo T60 laptops, and noticed that a system file scan - sfc - showed 2 of the 5 machines had modified files. What would cause this? Keep in mind that:

    1. these laptops are never connected to the internet (ran a full A/V scan anyway- nothing found)
    2. one that had scf violations just had a clean install of Win 7, from the DVD, 4 weeks ago.

    The prime suspect is the hard drive, but I can't prove it. The drives passed 3 diagnostics:

    1. Thinkpad's built-in HDD tester (in BIOS)
    2. SeaTools
    3. Windows scan disk

    The drives in these machines are seagate ST910021AS. I am aware of this issue: Seagate Momentus XT corrupting files (Linux and Mac) , but have been unable to reproduce a problem using their steps (those were not on windows anyway).

    The issue came up because a vendor's dll was found corrupted 2 weeks after an install - with certainty, the file was correct when it was installed. So the question is, why would the files just change? Is there something that should be looked at other than the hard drive?

    More info: found another dll (from a vendor - not a system file), with an invalid checksum. However, the file modified date reported by Windows is expected (2 years ago). Since it was recently installed, it was actually overwritten in the last 2 weeks. Why would the modified date not change?


    • Related Answers
  • Dave M

    Have you used the Lenovo diagnostic to check the drive controller? Also, have you run the diagnostics for a period of time(multiple runs)? have seen one test pass and a later one show a problem.

    Any hard shutdowns? Have seen this result in a corrupt file.

    Have you used bootable media to check for a rootkit?