ERROR_CORRUPT_LOG_CORRUPTED: How to Fix BSoD Error

Run the SFC scan to repair the corrupted system files

Reading time icon 3 min. read


Readers help support Windows Report. We may get a commission if you buy through our links. Tooltip Icon

Read our disclosure page to find out how can you help Windows Report sustain the editorial team. Read more

The ERROR_CORRUPT_LOG_CORRUPTED with error code 795 (0x31B) and description One of the volume corruption logs is internally corrupted and needs to be recreated. The volume may contain undetected corruptions and must be scanned, typically indicates that Windows has detected one of the volume corruption logs, (related to file system integrity) is corrupted. The error may appear due to disk, file system, or volume metadata issues.

How can I fix the ERROR_CORRUPT_LOG_CORRUPTED?

1. Run the CHKDSK utility

  1. Press the Windows key, type cmd in the search box, choose Command Prompt, and select Run as administrator from the list of options to launch Command Prompt with elevated rights.CMD elevated ERROR_CORRUPT_LOG_CORRUPTED
  2. Copy & paste the following command to check the integrity of your file system and fix logical disk errors and hit Enter: chkdsk C: /f /rCHKDSK FRC
  3. If the drive is in use, you will get the prompt to schedule the scan for the next system restart. Type Y and press Enter.
  4. Restart your computer to initiate the scan and fix any corruption on the disk.

2. Use the System File Checker tool

  1. Press the Windows key, type cmd in the search box, choose Command Prompt, and select Run as administrator from the list of options to launch Command Prompt with elevated rights.CMD elevated ERROR_CORRUPT_LOG_CORRUPTED
  2. Type the following command to scan all system files and replace any corrupted or missing files, then hit Enter: sfc /scannowSFCSCANNOW CMD ERROR_CORRUPT_LOG_CORRUPTED
  3. Wait for the scan to complete, then copy & paste the following command to fix issues with the Windows system image, including corruption that could be affecting volume, and press Enter: Dism /Online /Cleanup-Image /RestoreHealthRestore health
  4. Let the scan be executed successfully, then reboot your computer to let the changes take effect.

3. Check the volume with disk management

  1. Press Windows + R to open the Run window.DISKMGMT RUN COMMAND with signs ERROR_CORRUPT_LOG_CORRUPTED
  2. Type diskmgmt.msc and click OK to open the Disk Management window.
  3. Check the drives to ensure any of the volumes have unusual status, RAW, or Unallocated.
  4. Right-click the affected drive and select Properties.Properties - ERROR_CORRUPT_LOG_CORRUPTED
  5. On the Properties window, check the File system to ensure NTFS.NTFS

4. Reformat the drive

Note icon NOTE
First, back up all the important data from the affected drive as reformatting will erase all data on the drive.
  1. Press Windows + R to open the Run window.DISKMGMT RUN COMMAND with signs ERROR_CORRUPT_LOG_CORRUPTED
  2. Type diskmgmt.msc and click OK to open the Disk Management window.
  3. Right-click the volume of the affected drive and choose Format from the context menu.Format from the context menu
  4. In the Format dialog box, select these options:
    • Volume label: Disk
    • File system: NTFS (Windows)
    • Allocation unit size: Default
  5. Select Perform a quick format, then click OK.Format - ERROR_CORRUPT_LOG_CORRUPTED
  6. You will get a warning prompt that all your data will be erased; click OK to confirm.

The process can take a few minutes, and once you’re done, the drive is formatted correctly, and you can restore your data.

In conclusion, to fix the ERROR_CORRUPT_LOG_CORRUPTED, you can run the CHKDSK utility, run the system file checker tool, check the file system with disk management, or reformat the drive.

Recently, we also covered some other BSoD errors, such as ERROR_ACCESS_DISABLED_NO_SAFER_UI_BY_POLICY and ERROR_CORRUPT_LOG_OVERFULL

We also covered ERROR_CORRUPT_LOG_CLEARED in our latest guide, and ERROR_CORRUPT_LOG_DELETED_FULL so you might want to check it out. If you have any questions or suggestions about the BSoD error; feel free to mention them in the comments section below.

More about the topics: BSoD error codes, BSoD errors

User forum

0 messages