How to fix Error 794 on Windows 11

by

Windows 11 Error 794: Volume Corruption Log Full

Why This Error Happens

Error 794 occurs when NTFS’s internal “Spotfix” or “$Corrupt” logging mechanism, which tracks detected file system corruption on a volume, reaches its maximum capacity. This typically happens after repeated, unresolved corruption events accumulate without the volume being scanned and repaired via CHKDSK. Once the log is full, Windows can no longer record new corruption entries, meaning subsequent damage to the file system goes undetected and unlogged until the existing log is cleared through a repair operation.

Step-by-Step Resolution Guide

  1. Identify the affected volume: Open Event Viewer (eventvwr.msc), navigate to Windows Logs > System, and filter for Event ID 794 to confirm which drive letter is reporting the full corruption log.

  2. Run CHKDSK with repair flags: Open Command Prompt as Administrator and run:

   chkdsk C: /f /r /x

Replace C: with the affected volume. This scans for bad sectors, repairs file system errors, and clears the corruption log. If the volume is in use (e.g., the system drive), you’ll be prompted to schedule the scan on next restart—type Y and reboot.

  1. Verify NTFS self-healing status: Ensure Windows’ automatic NTFS self-healing feature is enabled by running:
   fsutil repair set C: 1

This allows Windows to proactively fix minor corruption without manual intervention going forward.

  1. Check disk health via PowerShell: Run the following to get a broader health status of the volume:
   Get-Volume -DriveLetter C | Get-StorageReliabilityCounter

Look for high values in ReadErrorsTotal or Wear indicators, which may suggest failing hardware rather than a purely logical file system issue.

  1. Update storage drivers and firmware: Open Device Manager, expand Disk drives, right-click your drive, and select Update driver. Also check your SSD/HDD manufacturer’s website for firmware updates, as outdated firmware can trigger false corruption flags.

Alternative or Verification Steps

  • Verify the fix: After running CHKDSK, re-check Event Viewer for new Event ID 794 entries. Also run chkdsk C: /scan (read-only) to confirm no corruption remains without needing a reboot.
  • Alternative if corruption persists: Back up your data immediately and run wmic diskdrive get status or a manufacturer diagnostic tool (e.g., CrystalDiskInfo) to rule out failing hardware, since recurring corruption logs often indicate a physically deteriorating disk rather than a software glitch.