Attempting to clean up after chkdsk

[alternety]

A few weeks ago my PC crashed. On reboot error I got a message from chkdsk saying an index was broken (I believe that was what it said). I allowed it to repair. It ran through hundreds and hundreds of items. Running down the screen too fast to even read. When it was over the system rebooted OK. It seemed to be running OK. Then a few weeks later I found some applications failed when I tried to start them. Messages about them not being found. I have no idea how to find out what chkdsk did, or if there is any way to fix the fix. I do not want to lose newer changes or data/files on the boot disk. Applications have the annoying habit of stuffing data on the boot drive without explaining what or where.

So, I have a backup run about a month before the chkdsk event (I know, do it more often). I have downloaded ViceVersa to try to make sense out of the situation. I have loaded the backup onto a fresh drive; but not made it a bootable drive. The backup software I currently use (another long story) spoofs explorer to be able to see inside a backup archive; but other applications can't do it. Hence the restored copy.

I have run VV comparing both copies. I was not seeing things that looked like what I was after. Nothing clearly missing. I ran CRC check and found things, but in a strange way that I don't understand.

A lot of files are now showing as newer (+) on the newest active copy of the disks, but the date/time is exactly alike. Under those conditions they should have a ckeck mark - and they did before I believe. They are also the same files sizes. However the CRCs are different. If someone could help me understand if this is a useful indicator or if some other mechanism is causing it. Any help in finding out just what chkdsk did would be an immense help.

[TGRMN Software]

Hi, have you tried another chkdsk (without repairing , only checking) on the original disk? It looks like that disk is failing.
_________________
--
TGRMN Software Support
http://www.tgrmn.com
http://www.compareandmerge.com

[alternety]

I believe the problem was caused by an overclocking attempt. I do not think there is a problem on the drive itself. But I seriously need some analytical help on what VV is showing me.

In an aside; one thing you may consider changing in the application is to not stop and require a user input when an error occurs in CRC checking. Log them, but don't stop. I takes more than an hour to do the CRC check on my two drives. Because of these messages I can not do this unattended. This is rather a large waste of user time and there is really nothing I can see gained by the messages. All they say is that it was one of three different things. And in error intense areas this is also a bit strenuous on the click finger.

[alternety]

Can anyone explain why the CRCs are different?