Looks like there is some issue with the Hidden Snapshot that SQL Server creates while running DBCC CHECKDB. Read Paul's article here

To ensure that the database is clean, create a snapshot of the database and run DBCC CHECKDB against it.