With a "xxxxx.val is corrupt, missing or has been tampered with" error, the program will continue to fold, and will buffer the results until the error is cleared up. Not a fatal error. Hence the multiple copies of the set of error messages -- it finishes a generation, tries to upload, throws an error, folds the next generation.
On a friends machine (if I'm called upon for tech service, I sneak DF in
) a couple of months ago, over five hundred generations were buffered in an identical situation. All uploaded after repairs.
The .val and _min.val files are essentially identical. One can be substituted for the other in an emergency. If both are corrupt, the -purgeuploadlist command will let you skip generations until good data is found.
Edit: I just looked at Clone's stats. A 27,000 point update. Good to see the error cleared up and the points on the board.