Error Corrupt Log Overfull 794 (0x31A): How to Fix it

ERROR_CORRUPT_LOG_OVERFULL usually affects developers, and if it occurs, you won’t be able to log future events. This can be a problem, but there are a few ways you can fix this.

How can I fix ERROR_CORRUPT_LOG_OVERFULL?

1. Check Event Viewer

1. Press the Windows key + X and choose Event Viewer.
   
2. Next, navigate to Windows Logs and select System.
   
3. Look for other events and warnings that have occurred before the error.
4. Research the issues and try to resolve them on your own.

2. Scan the drive

1. Press the Windows key + S and enter cmd. Choose Run as administrator.
2. Run the following command: chkdsk C: /f /r
   
3. Press Y to schedule a scan.
4. Restart your PC and wait for the scan to finish.

3. Repair system files

1. Open Command Prompt as administrator.
2. Run the following command: sfc /scannow
   
3. Wait for the scan to finish.
4. If the issue is still there, run the following commands:
   DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth

4. Perform a clean boot

1. Press Windows key + R and type msconfig.
   
2. Navigate to the Services tab, check Hide all Microsoft services, and then click on Disable all.
   
3. Click Apply and OK but don’t restart your PC.
4. Press Ctrl + Shift + Esc to open Task Manager.
5. Navigate to the Startup tab and disable all startup applications.
   
6. Restart your PC.

If the issue doesn’t appear anymore, it means that it was caused by one of the disabled services or apps. To find the culprit, enable services and apps in groups until you reproduce the problem.

5. Reset the NTFS log file

1. Open Command Prompt as administrator.
2. Run the following: fsutil resource setautoreset true C:\
   
3. Save changes and restart.

It’s worth mentioning that ERROR_CORRUPT_LOG_OVERFULL often comes with 794 (0x31A) One of the volume corruption logs is full, further corruptions that may be detected won’t be logged message, so you can easily recognize it.

This isn’t the only error you can encounter, and we wrote about Error_Corrupt_Log_Unavailable and Error_Corrupt_System_File so feel free to check those articles out.

We also have a guide on ERROR_CORRUPT_LOG_CLEARED, so don’t miss it for more information.