Logical page 0x%1x in database %d is already hashed.
This error occurs when SQL Server attempts to hash logical page 0x%Id of database %d and the page is already in SQL Server's hash table.
This error usually occurs as a side effect of other data corruption that can usually be detected by running DBCC NEWALLOC and DBCC CHECKDB.
Review the SQL Server error log, and then execute the DBCC CHECKDB and DBCC NEWALLOC statements on the database. This error may be associated with errors 1203 and 2521. Focus on these errors first; investigate their cause and correct them.
Verify with your hardware vendor that the disk subsystem being used by SQL Server is at the currently supported and recommended firmware and hardware level.
If DBCC CHECKDB and DBCC NEWALLOC find no errors, or if errors are found and corrected so that subsequent DBCC statements indicate no errors, but this error reoccurs, call your primary support provider. Have the SQL Server error logs and the output from DBCC CHECKDB, DBCC NEWALLOC, and sp_configure, available for review.