ERROR_CORRUPT_LOG_CORRUPTED - 795 (0x31B)
One of the volume corruption logs is internally corrupted and needs to be recreated. The volume may contain undetected corruptions and must be scanned.
Updated: Feb 21, 2026
Technical Meaning
The error code ERROR_CORRUPT_LOG_CORRUPTED indicates that one of the volume corruption logs, which are used to track and manage file system integrity, is internally corrupted. This corruption may have gone undetected previously, necessitating a recreation of the log.
Error Details
This specific error suggests that there might be underlying issues with the file system's metadata or journaling mechanism. The volume in question should undergo a thorough scan to identify and correct any potential data inconsistencies.
Usage Context
The ERROR_CORRUPT_LOG_CORRUPTED is typically encountered during operations that rely on the integrity of the file system logs, such as recovery from corruption or maintenance tasks. It can also be observed when attempting to access files or directories stored on a volume with corrupted log entries.
Developer Interpretation
Developers should interpret this error as an indication that the file system may contain undetected corruptions. The affected volume must be thoroughly scanned and possibly repaired before it can be safely used again. This error does not provide specific details about the nature of the corruption but signals a need for further investigation.
Related Errors
ERROR_FILE_SYSTEM_CORRUPT(532)ERROR_VOLUME_CORRUPTION_WARNING_READ(1908)ERROR_VOLUME_CORRUPTION_WRITE(1907)
FAQ
Q: What does the ERROR_CORRUPT_LOG_CORRUPTED error mean?
A: It indicates that a volume corruption log is internally corrupted and needs to be recreated. The volume may contain undetected corruptions.
Q: How should I handle this error?
A: The affected volume must be scanned for potential data inconsistencies before it can be safely used again.
Summary
The ERROR_CORRUPT_LOG_CORRUPTED is a specific error indicating internal corruption in one of the volume's corruption logs. Developers should treat this as an indication that the file system may contain undetected corruptions and must perform a thorough scan to ensure data integrity.