What DBCC CHECKDB reported? Are you running it daily to catch corruption immediately?

>I have never this one:
>
>The operating system returned error 23(Data error (cyclic redundancy check).) to SQL Server during a read at offset 0x0000000c4f0000 in file 'D:\SqlData\MyTable\MyTable.mdf'. Additional messages in the SQL Server error log and system event log may provide more detail. This is a severe system-level error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
>
>We have a corruption somewhere.
>
>All the errors point to the same table at the write time. We have removed the index and recreated it. This was not a factor. As this is a log table, we are trying to clean it up, remove the index, recreate the index and see if that resolves the issue. We have a backup of it. At this point, we can verify if all is OK with data when attempting to do a backup. At this point, the backup cannot be done as it reports something about the MDF. So, while we wait for those procedures to take place, I was wondering if someone already had this situation.