Recurring "Disk Utility found corruption" error.

I kept getting an error from Disk Utility that it found corruption (on my startup partition) and suggested I rerun it from The Recovery Partition. However, doing so never found an issue with the drive. Furthermore, simply rebooting the system and running Disk Utility again, not only did not find any errors (same as when running it from The Recovery Partition) but it did not issue the same error.

Until the next time it did.....sometime later. It seemed that simply rebooting the system and rerunning Disk Utility was the fastest, most reliable way to get a clean bill of health from Disk Utility.

And then completely erased my startup drive (formerly a Apple FileVault encrypted disk where I opted not to let my iCloud account unlock the disk, but chose a encryption key instead, thinking it might be more secure than trusting iCloud never be hacked into).

Slowly, I reconfigured my system step-by-step. My goal was to find the offending culprit.

For days I did not get the error, though I tested it several times everyday, by running Disk Utility. Even after encrypting the drive again (using the same encryption key procedure).

UNTIL I INSTALLED AND RAN MAINTAIN SOFTWARE'S COCKTAIL AND ALLOWED IT TO CHECK THE STARTUP DRIVE.

THAT SAME AFTERNOON, I RAN DISK UTILITY, AND THE PROBLEM RE-SURFACED!

NOTE: HAVING ALREADY BACKED UP THE DRIVE WITH COCKTAIL ONCE INSTALLED, AND RESTORING IT FROM THAT BACKUP ONLY RESTORED THE PROBLEM. I WAS FORCED TO REFORMAT THE ENTIRE DRIVE AND START ALL OVER AGAIN!

I then resolved to myself to never use Cocktail on my Mac again. I have run Disk Utility scores of times since (even with the drive encrypted) and so far, NO ERRORS.

So, for those plagued by this issue, I have the following questions:

Have you ever installed and or run Cocktail on your system (even if you have un-installed it)? If so, are you still getting the error message?

Have you restored your system drive from a backup that reflects a partition that once had Cocktail installed and/or run upon it? It doesn't seem to matter if Cocktail is installed or not. What seems to matter is what Cocktail did to the partition, regardless of whether Cocktail still exists.

Is your drive encrypted? And if so, did you encrypt it using the "encryption key method"?

I would be interested by how many people (and there seem to be hundreds of you) who have or had the same combination as I did (Cocktail installed or previously installed) on a Mac that also has FileVault (or Finder) encrypted partition(s) where an encryption key was used instead of opting to allow iCloud to unlock the drive.

I have to suspect Cocktail is the culprit. In my case, the answer seems to be "YES".