Event ID/Source search
Keyword searchExample: Windows cannot unload your registry file
Event ID: 399 Source: ESE
Information Store (<PID>) Storage Group 1: The database page read from the file "<file>" at offset <offset> for <value> bytes failed verification. Bit <value> 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.
|English: Request a translation of the event description in plain English.|
According to MSEX2K3DB, this Warning event indicates that a database page had a single-bit error that was corrected automatically. The article provides some suggestions on how to troubleshoot this type of problem.
Simon L. Pelletier
After reviewing the error message, I understood that the problem was a read/write error. I disabled the write caching on my SCSI drive to correct the problem. When you have databases sitting on the drives, disabling write caching can fix the problem. It may degrade the performance but not enough to be a problem.
As per Microsoft: "This event indicates that a single-bit error has been detected, and that this error has been successfully corrected in memory. In this scenario, the page where this error occurred may or may not have been corrected on the physical hard disk. The single-bit error is not corrected on the physical hard disk unless the page has been written to. Therefore, if the database page is only read, the single-bit error is corrected in memory, but the single-bit error is not corrected on the physical hard disk". See ME867626 for more details.
|Private comment: Subscribers only. See example of private comment|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated