ATIH 11 '0-0' was terminated.

The corrupt message means that TI can't read the archive and re-create checksums that were included in the archive when it was created. There are 4000 checksums/GB of archive and everyone must be perfect or the archive is declared corrupt.

This means that anything interfereing with this process is suspect and it can be a flakey disk cable, bad RAM, and as one user found out a bad CPU, overclocked system or memory, etc, etc.

If your system is overclocked in anyway such as with aggressive RAM timings put it back to normal operation.

Check the RAM, run Memtest86+, free from www.memtest.org , for seveal passes. Overnight is best. Don't assume because you don't appear to have any problems with typical PC operation that all is well. TI puts a significant load on the disk subsytem and RAM with the large amount of data carefully checked by the checksum process.

You can also look in the Windows Event log and see if any hardware issues are flagged. My problem with validation was caused by a marginal SATA cable and it was noted in the Event log with the recommendation to replace the cable.

I assume the problem occurs when running Windows. You can take Windows out of the equation by booting up the TI rescue disk and trying to validate. However, the Linux environment on the rescue CD tends to be more problematic than Windows because the drivers may not be the best. If you have been using the TI CD to do the backup/validation then try validating in Windows and see if it corrects the problem.

I'll do my workaround based on your advices, and I'll let you know.

Thank you for these great findings of yours. Cheers.