The database page read from the file "%1" at offset %2 (database page %5) for %3 bytes failed verification. Bit %4 was corrupted and has been corrected. This problem is likely due to faulty hardware and may continue. Transient failures such as these can be a precursor to a catastrophic failure in the storage subsystem containing this file. Please contact your hardware vendor for further assistance diagnosing the problem.
The database object '{0}' in Active Directory has been corrupted and is in an inconsistent state. Unable to find any server ...
The database page read from the file "%1" at offset %2 (database page %5) for %3 bytes failed verification because it contains ...
The database page read from the file "%1" at offset %2 (database page %5) for %3 bytes failed verification due to a lost ...
The database page read from the file "%1" at offset %2 (database page %5) for %3 bytes failed verification due to a persisted ...
The database page read from the file "%1" at offset %2 (database page %5) for %3 bytes failed verification. Bit %4 was corrupted ...
The database page read from the file "%1" at offset %2 (database page %6) for %3 bytes failed verification. Bit %5 was corrupted ...
The database page read from the file "%1" at offset %2 (database page %7) for %3 bytes failed verification due to a page ...
The database page read from the file "%1" at offset %2 for %3 bytes failed verification due to a page number mismatch. The ...
The database page read from the file "%4" at offset %5 (database page %10) for %6 bytes failed verification due to a page ...