How to fix Error 684 on Windows 11

by

Why This Error Happens

Error 684 with the “frame consolidation” message typically originates from the Windows Memory Manager or Storage Optimizer subsystem when it attempts to defragment and merge non-contiguous memory pages or disk frames into a single contiguous block. This event is often logged when the consolidation process is interrupted by a resource lock—commonly caused by insufficient permissions on the Volume Shadow Copy service, a conflicting background task (like an antivirus scan) holding a file handle, or corrupted metadata in the NTFS Master File Table (MFT). While it usually appears as an informational event, repeated occurrences can indicate underlying disk health issues or a corrupted system file cache.

Step-by-Step Resolution Guide

  1. Check Event Viewer for Correlating Errors
    Open eventvwr.msc, navigate to Windows Logs > System, and filter for Event ID 684. Note the timestamp and check for any correlating disk (Event ID 7, 11, 51) or memory (Event ID 2019) errors within the same minute.

  2. Run System File Checker and DISM
    Open Command Prompt as Administrator and run:

   sfc /scannow
   DISM /Online /Cleanup-Image /RestoreHealth

This repairs corrupted system files that may be triggering improper consolidation attempts.

  1. Verify Disk Integrity
    Run chkdsk C: /f /r from an elevated Command Prompt and schedule it to run on the next restart. This checks for and repairs MFT/NTFS structural issues that interfere with frame consolidation.

  2. Disable Storage Sense Temporarily
    Go to Settings > System > Storage > Storage Sense, toggle it off. Storage Sense running concurrently with disk optimization tasks can cause resource contention leading to this error.

  3. Update Storage/Chipset Drivers
    Open Device Manager > Disk drives, right-click your primary drive, select Update driver. Also check the manufacturer’s website (Intel, AMD, or SSD vendor) for the latest storage controller drivers.

Alternative or Verification Steps

  • Verify the fix: After completing the steps above, open Event Viewer again and monitor the System log for 24–48 hours to confirm Event ID 684 does not reoccur.
  • Alternative solution: If the error persists, run Optimize-Volume -DriveLetter C -Defrag -Verbose in PowerShell (as Administrator) to manually force a clean consolidation pass and check the verbose output for specific failure points.