This error can occur, however, most often due to defective hardware or operational errors . This post will explain how to restore from suspect mod.however, but still go through your SQL-server error logs and find out the root cause of the error.
To resolve this issue run the commands listed below,
EXEC sp_resetstatus [YourDatabase]; ALTER DATABASE [YourDatabase] SET EMERGENCY DBCC checkdb([YourDatabase]) ALTER DATABASE [YourDatabase] SET SINGLE_USER WITH ROLLBACK IMMEDIATE DBCC CheckDB ([YourDatabase], REPAIR_ALLOW_DATA_LOSS) ALTER DATABASE [YourDatabase] SET MULTI_USER
Replace YourDatabase with your actual database name.
Hope this will help you to resolve your issue,If the database is still marked as suspect after executing these commands, there may be other issues preventing the database from recovering. At this point, only choice remaining is recover from a good backup.