Uh oh... if indeed those images WERE fine... and now you are opening images (known to previously fine on that same computer) and they are no longer fine... then I suspect you've got a failing hard drive.
I'll explain.
I had a problem very much like yours except in my case I was using Apple's "Aperture" software.
HOWEVER... I'm a big believer in having backups.. and I have two different types of backup systems which backup my entire computer. Both of them have saved me in different ways.
One of my backups is basically a disk "clone". It creates a backup image of my hard drive and it's even a bootable backup. In other words if my disk were to fail completely (or even if the whole computer was fried) I could plug that backup drive into a working computer and boot from the backup drive... and literally have everything as though I was working on my original computer hard drive.
The other backup is an "incremental" backup (it's Apple's "Time Machine" backup system.) Time Machine activates once per hour, in the background, and looks for any files that have changed. It automatically backs up all changes to the backup system every hour (but only files that have changed in that hour. It is taught to neglect some unimportant files such as caches, etc. that don't really need to be backed up.) Once the hourly backups are 1 week hold, Time Machine consolidates those "hourly" backups into "daily" backups. It also consolidates "daily" backups which are more than 1 month old into "weekly" backups and it maintains weekly backups going back as far in time as possible for as long as it has disk space to store the data. At some point it will run out of disk space and when that happens it deletes the oldest backups to make room for the newest backups.
So here's the story...
I had been using Aperture without issue for years. One day I needed to get some images that I had shot about 3 months ago (and had used those images many times -- there was no problem with them.) But on this particular day I opened the images and they were showing signs of corruption... much like the images you posted of your DPP images. I knew those same images were previosuly fine and that I hadn't touched in them in a couple of months.
I ran a filesystem check and the filesystem utility found (no surprise here) that there were numerous errors on the filesystem. It repaired them. But the damage was done and those files were still corrupted.
So I brought the backup system online (the one that "clones" my drive) to just grab the files I needed from that system... only to discover that the images were corrupted on the backup system (that backup system backs up "everything" when it runs so it backed up the already-corrupt copies of the images.)
So then I brought the time-machine backup online and checked the images there and discovered that the latest backups were indeed also corrupt... but I started going back in time... one week at a time... until I found a point where the images existed and were not corrupted. I restored those images and the problem was solved.... so I thought.
Within a day or two, I began to notice more randomly corrupted files... did another filesystem integrity check. It failed. I did a filesystem repair and fixed the filesystem (which claimed to repair all errors successfully)... but just for fun I re-rain the filesystem integrity check just a few hours later and... it failed again (within that short amount of time). Clearly I couldn't trust the drive anymore.
Here's why:
The hard drive has physical platters and a set of "access arms". The arms swing in or out to reach the inner or outer "tracks" (concentric rings onto which the drive will save your data). The tolerances are very tight and the access arms move VERY fast. After enough years of heavy use, things can start to loosen up in the drive and the access arms can have just a tiny amount of slop. This means that when the read/write heads position over a track they might not be directly over that specific track... but off by just a small amount. As the drive ages enough, that "small amount" of error can be enough that the drive is partially writing onto the adjacent track and damaging whatever files just happened to be stored there.
So... I ordered a replacement drive and in the two days it took for that drive to be delivered, I ran my computer off the "bootable" backup. Once the new drive was installed, I did a restore from the Time Machine backup, but I restored the machine to a point in time which was about a month old (before all the damage wa done to random files.) Things were messy for a few days but once the replacement drive arrived I did get everything restored back as though nothing had ever happened.
If you are getting damaged files from images that you KNOW were previously not damaged when they came out of the camera (you've opened these same images before and they were fine... and you're sure about that...) then I suggest you use a disk utility to check the integrity of your filesystem. You may (and I suspect you probably do) have slow failing hard drive and it's no longer accurately positioning the read/write heads over the intended disk track.
The somewhat famouse Google hard drive study found that while a drive *could* fail at any age, they are most likely to fail either in the 1st six months of use... or after about 5 years of use. But they *could* fail anytime.
Tim Campbell
5D III, 5D IV, 60Da
