What NTFS_FILE_SYSTEM means

Windows uses the NTFS file system on most drives. This stop is raised when the NTFS driver meets a condition it cannot handle. Damaged file system structures, a failing drive or loose connection, or security software interfering with disk access can be behind it.

Common causes

  • File system corruption, often after power loss or forced shutdowns
  • A failing drive with bad sectors
  • A loose cable or poor M.2 contact
  • Disk-related security or backup software conflicting with Windows

How to fix NTFS_FILE_SYSTEM

Work through these in order and test after each one. Stopping as soon as the crashes stop tells you which change mattered.

  1. Back up your data. If the drive is reachable at all, copy important files to another drive before running repairs.
  2. Scan and repair the volume. Open Terminal (Admin) and run chkdsk C: /scan. If it reports errors, schedule a repair with chkdsk C: /f and restart.
  3. Check the health of the drive. Read the SMART data with the drive maker's tool or CrystalDiskInfo and look for reallocated or pending sectors, media errors and a low remaining-life figure. Back up important files first if the drive reports any warning.
  4. Reseat the drive connection. With the PC off and unplugged, reseat the SATA cable or M.2 drive, and try a different SATA port or cable if you have one.
  5. Repair Windows system files. Open Terminal (Admin) and run sfc /scannow. If it reports damage it could not repair, run DISM /Online /Cleanup-Image /RestoreHealth, restart, and run sfc /scannow once more.
When to stop and protect your data

Recurring file system errors on a drive that reports health warnings mean replacement, not repeated repair.

Not sure this is your code?

The stop code appears as text on the blue screen. If the PC restarted before you could read it, open Event Viewer, then Windows Logs, then System, and look for a BugCheck event with ID 1001. You can also search all stop codes.

Related guides

Other storage and file system errors