A database in suspect mode may not be recoverable. That's why Gail is asking about backups. But, to understand what is wrong with the database we need more information than you've provided. Remember, we're not sitting there and can't see what you can see. The error message looks to be from when SQL Server was shutting down at 08:47 this morning. There is an error regarding closing CRS_Financial, but it doesn't indicate the origin of the corruption, which must be elsewhere in your error messages. The error you do have, 9004, indicates a problem with the log. Here is a troubleshooting page
from Microsoft Developers Network, MSDN (the documentation for SQL Server) that might help. But we still don't know the original error. That may be in other error logs. It appears you may be starting & stopping the server in an attempt to fix things. Don't do that. Instead, investigate your error logs to see if you can find an error reference to CRS_Financial. But, you may have to go that backup and run a restore. But, if you don't know when the error occurred, you may have backed up the error along with your database.
Just remember, a differential is only good if you also have the full backup that matches with it. Otherwise, you will not be able to restore (unless you also have log backups). But either way, you need to have a "good" backup. This means a backup that doesn't have the corruption in it. Test your restore to a different database and validate that it can come online before you overwrite the existing database.
The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood...
Theodore RooseveltThe Scary DBA
Author of: SQL Server Query Performance Tuning
and SQL Server Execution Plans
Product Evangelist for Red Gate Software