How to fix Error 557 on Windows 11

by

Troubleshooting Guide: Error 557 – “Getting Data” / Undefined MM Error Mapped by FsRtl Filter

Why This Error Happens

Error 557 occurs when the Windows Memory Manager (MM) returns an internal status code that is not part of the standard set of exceptions defined in the FsRtl (File System Runtime Library) exception filter. Because the filter only recognizes a fixed list of error codes, the undefined MM error is remapped to a generic placeholder error—in this case, one associated with the “Getting Data” operation—so the exception handling can proceed safely. While this remapping allows the system to continue without crashing, the original, more specific diagnostic information about the root cause (often related to corrupted memory-mapped files, failing storage I/O, or low-level driver faults) is lost in the process.

Step-by-Step Resolution Guide

  1. Check Event Viewer for Correlated Errors: Press Win + X → select Event Viewer → navigate to Windows Logs > System. Look for entries around the same timestamp as Error 557, particularly from sources like Ntfs, disk, or volsnap, which may reveal the true underlying MM error before it was remapped.

  2. Run Memory Diagnostics: Press Win + R, type mdsched.exe, and press Enter. Choose Restart now and check for problems to rule out physical RAM issues that could be triggering unexpected MM error codes.

  3. Scan and Repair System Files: Open Command Prompt as Administrator and run:

   sfc /scannow

Followed by:

   DISM /Online /Cleanup-Image /RestoreHealth

This repairs corrupted system files that may be interfering with FsRtl’s exception handling.

  1. Check Disk for File System Corruption: In an elevated Command Prompt, run:
   chkdsk C: /f /r

Schedule the scan on next restart if prompted, and reboot the system. This addresses NTFS-level issues that commonly trigger unmapped MM exceptions during file I/O.

  1. Update Storage and Chipset Drivers: Go to Settings > Windows Update > Advanced options > Optional updates and install any pending driver updates, especially for storage controllers (AHCI/NVMe) and chipset drivers, as outdated drivers can cause abnormal MM return codes.

Alternative or Verification Steps

  • Verify the fix: Reopen Event Viewer after completing the steps above and confirm that Error 557 no longer appears during the same operation that previously triggered it (e.g., file transfer, backup, or data retrieval task).
  • Alternative approach: If the error persists, back up your data and perform a System Restore to a point before the issue began, or consider an in-place upgrade repair via Settings > System > Recovery > Fix problems using Windows Update.