Execute DBCC CHECKTABLE on the second object specified in the error message.
To determine the full extent of the corruption, execute DBCC CHECKDB as soon
as possible. Also check the error log for other errors, which often accompany
a 605 error.
If the 605 error is not transient, the problem is severe and you must run
DBCC CHECKDB with one of the repair clauses. If the error involves an index
page, use the REPAIR_REBUILD clause. If the error involves a data page, it
may be necessary to use the REPAIR_ALLOW_DATA_LOSS clause. In the likely event
that you cannot allow the loss of data, you will need to restore from a known
clean backup. If the problem persists, contact your primary support provider.