Error Corrupt Log Unavailable 796 (0x31C): How to Fix it

This error is associated with the drive corruption


ERROR_CORRUPT_LOG_UNAVAILABLE
XINSTALL BY CLICKING THE DOWNLOAD FILE
A message from our partner

Fix Windows 11 OS errors with Fortect:

  • Download Fortect and install it on your PC
  • Launch the tool and Start scanning to find broken files that are causing the problems
  • Right-click on Start Repair to fix issues affecting your computer’s security and performance
Download Now Fortect has been downloaded by 0 readers this month, rated 4.6 on TrustPilot

The ERROR_CORRUPT_LOG_UNAVAILABLE usually affects developers and occurs if there’s a problem with your drive. However, there are a few ways you can fix this problem.

How can I fix ERROR_CORRUPT_LOG_UNAVAILABLE?

1.  Use Event Viewer

  1. Press the Windows key + X and choose Event Viewer.
  2. Go to Windows Logs and select System.
    System Event viewer 0x80070000
  3. Look for any errors related to corrupt logs or disk issues.

2. Run chkdsk

  1. Press the Windows key + S and type cmd. Choose Run as administrator.
  2. Run the following command: chkdsk C: /f /r /x
  3. Press Y to schedule the restart.
  4. Restart your PC.

3. Repair system files

  1. Open Command Prompt as administrator.
  2. Next, run the following command: sfc /scannow
    SFCSCANNOW CMD
  3. Once finished, check if the problem is gone.
  4. If the issue persists, run DISM /Online /Cleanup-Image /RestoreHealth
    dism scan

Keep in mind that these scans can take a while, so don’t interrupt them.

4. Check drive health

  1. Start Command Prompt with administrative privileges.
  2. Next, run wmic diskdrive get model,status
    wim diskdrive
  3. If the status says Caution or Bad, it might be time to back up your drive.

If the error persists, you might have to reinstall Windows and reformat the affected drive.

ERROR_CORRUPT_LOG_UNAVAILABLE often comes with the following message: 796 (0x31C) One of the volume corruption logs is unavailable for being operated on, so it can be easily recognized.

This is one of many developer errors you can encounter, and we already wrote about Error_Log_Hard_Error and Error_Mca_Occured in our previous articles, so don’t miss them.

We also have a guide on ERROR_CORRUPT_LOG_OVERFULL, so you might want to check it out.

More about the topics: error

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

User forum

0 messages