%1 (%2) %3The database page read from the file "%4" at offset %5 (database page %9) for %6 bytes failed verification. Bit %8 was corrupted and was corrected but page verification failed with error %7. 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 name or the server name for the configuration database is not correct. Ensure that the server hosting the AD ...
The database page read from the file "%4" at offset %5 (database page %10) for %6 bytes failed verification due to a page ...
The database page read from the file "%4" at offset %5 (database page %8) for %6 bytes failed verification because it contains ...
The database page read from the file "%4" at offset %5 (database page %8) for %6 bytes failed verification. Bit %7 was corrupted ...
The database page read from the file "%4" at offset %5 (database page %9) for %6 bytes failed verification. Bit %8 was corrupted ...
The database page read from the file "%4" at offset %5 for %6 bytes failed verification due to a page number mismatch. The ...
The database page read from the file '%4' at offset %5 (database page %6) failed verification due to a page checksum mismatch. ...
The database stored in the media cannot be used; please refer to http://go.microsoft.com/fwlink/?LinkId=91180 to create an ...
The Database Update Messages Delta performance counter shows the number of new cluster database update messages sent over ...