How to Fix NTFS_FILE_SYSTEM BSOD in Windows 11

•
Ankit Kumar
Windows 11BSODStorageData RecoveryFix

The Problem

NTFS_FILE_SYSTEM (stop code 0x00000024) means the NTFS driver hit corruption in the on-disk structures it depends on — the master file table, a directory index, or the journal. Windows stops immediately rather than write more data on top of damaged metadata.

Two things cause it: the file system was damaged (sudden power loss, a bad shutdown, an interrupted update), or the drive underneath is failing and returning bad data. Treat your files as at risk from the moment you see this screen.

Before anything else: if the PC still boots, copy your important files to another drive now. Organise and back up important documents covers what to grab first. Cannot boot at all? See fix INACCESSIBLE_BOOT_DEVICE.

Symptoms

  • Blue screen reading NTFS_FILE_SYSTEM, often on boot or when opening a particular folder.
  • Files or folders that show as 0 bytes, have garbled names, or throw "The file or directory is corrupted and unreadable".
  • File Explorer hangs when browsing one specific drive.
  • Windows runs a disk check automatically at startup, then blue-screens again anyway.

Step 1: Get Your Data Off First

Every repair step below writes to the damaged volume. That is normal and usually safe, but it is not free.

  1. If Windows boots, copy documents, photos, and anything irreplaceable to an external drive or cloud storage right now.
  2. Copy the smallest, most important files first — a dying drive may not survive the whole transfer.
  3. If Windows will not boot, boot from a Windows installer USB, choose Repair your computer → Troubleshoot → Command Prompt, and copy files with robocopy: 
    robocopy C:\Users\YourName D:\Rescue /E /R:1 /W:1 /XJ
    Drive letters differ in the recovery environment — run diskpart, then list volume, then exit to check.
  4. If files are already missing: how to recover deleted files in Windows.

Step 2: Run CHKDSK Against the Affected Volume

  1. Open Terminal (Admin).
  2. Scan without repairing first, so you know what you are dealing with: 
    chkdsk C: /scan
  3. To repair the Windows volume, schedule a full pass and reboot: 
    chkdsk C: /f /r
  4. Type Y when asked to schedule it for the next restart, then reboot.
  5. The /r pass reads every sector and can take several hours on a large mechanical drive. Do not interrupt it, and keep a laptop plugged in.
  6. For a secondary drive, substitute its letter — for example chkdsk D: /f /r — and no reboot is needed.

Step 3: Repair Windows System Files

Corrupted system files produce the same crash even when the disk is fine.

  1. In Terminal (Admin): 
    sfc /scannow

    DISM /Online /Cleanup-Image /RestoreHealth
  2. Reboot and run sfc /scannow once more — the first pass often cannot replace files that are in use.
  3. Step-by-step: how to run SFC and DISM.

Step 4: Check the Drive's SMART Health

  1. In Terminal (Admin): 
    wmic diskdrive get model,status
  2. Read the detailed attributes with CrystalDiskInfo or your drive vendor's tool. Watch Reallocated Sector Count, Current Pending Sector Count, Uncorrectable Sector Count, and NVMe Percentage Used / Available Spare.
  3. Full guide: check SSD and hard drive health.
  4. A drive with growing pending sectors is failing. No amount of CHKDSK fixes that — replace it.

Step 5: Reseat Cables and Rule Out the Connection

  1. Shut down, unplug the power, and hold the power button for five seconds.
  2. Reseat SATA data and power cables at both ends, or the M.2 module in its slot.
  3. Try a known-good SATA cable and a different SATA port on the motherboard.
  4. An intermittent cable writes garbage to the file system repeatedly, so this is worth ruling out before you replace a drive.

Step 6: Disable Fast Startup

Fast Startup leaves the file system in a partially mounted state between sessions, which turns one bad shutdown into recurring corruption.

  1. Open Control Panel → Power Options → Choose what the power buttons do.
  2. Click Change settings that are currently unavailable.
  3. Untick Turn on fast startup (recommended) → Save changes.
  4. Always shut down from the Start menu rather than holding the power button. Related: fix Windows 11 not shutting down or restarting.

Step 7: Test the Memory

Bad RAM corrupts data on its way to disk, so the file system takes the blame for a memory fault.

  1. Windows + R → mdsched.exe → Restart now and check for problems.
  2. Press F1 and set the Test Mix to Extended.
  3. Confirm with MemTest86 from a USB stick over four or more passes.
  4. Related: fix MEMORY_MANAGEMENT BSOD.

Step 8: Update Storage Drivers and Firmware

  1. Windows + R → msinfo32 → note System Model and BIOS Version/Date.
  2. Install the current chipset and storage controller (Intel RST / AMD RAID) drivers from the PC or motherboard manufacturer.
  3. Check the SSD manufacturer's toolbox for a firmware update — several NVMe firmware bugs caused exactly this crash.
  4. Related: how to update outdated drivers.

What Not to Do

  • Don't keep rebooting and hoping. Each crash writes more damage into the metadata.
  • Don't run chkdsk /r on a drive with SMART warnings before you have copied your data off. Recovery is far harder after a failed repair pass.
  • Don't reformat immediately if you still need the files — reformatting makes recovery much less likely.

Still Not Working?

If CHKDSK finds and "fixes" errors on every run, the drive is failing — new corruption keeps appearing. Replace it, then either restore from backup or move the installation across: how to clone a hard drive to an SSD.

If the drive tests clean but Windows still crashes, do a repair install that keeps your files: reinstall Windows without losing data.

Related: fix UNEXPECTED_STORE_EXCEPTION and fix a corrupted USB or external drive.

Related guides