There is a corrupt page in a seed db that DBCC CHECKDB didn't recognize
Consistency checks only run on the pages in the database that are allocated. If a page isn't allocated to anything, then the 8192 bytes of it are meaningless and can't be interpreted. As long as a page is allocated, it will be consistency checked by DBCC CHECKDB, including testing the page checksum, if it exists. A corruption can seem to 'disappear' if a corrupt page is deallocated at the time a DBCC CHECKDB runs.
Did you ever find a solution for this particular issue?
To fix the corruption issue of your database page you can take the help of third party SQL repair tool[/url]. Download the demo version first to see if the tool fits your need.