NTFS_FILE_SYSTEM, the blue screen, explained and fixed

This stop code (0x00000024) means ntfs.sys, the driver for the NTFS file system used by your Windows partitions, encountered corruption or an error it could not recover from. The two sources are a damaged file system (often from an unclean shutdown or a crash during a write) and a drive that is starting to fail. Both deserve respect: back up first, then repair.

The fix, in order

  1. Back up your files if the PC still boots. File-system corruption plus a possibly failing drive is the combination that loses data. Get the important things onto another drive or cloud storage before running repairs.
  2. Run chkdsk with repair. Admin Command Prompt: chkdsk C: /f /r and agree to run it at the next restart. The /f fixes file-system errors; /r also hunts for bad sectors and recovers readable data from them.
  3. Read the drive’s SMART health. Use the drive maker’s tool (or CrystalDiskInfo-style utilities) and check for reallocated sectors, pending sectors, and overall health warnings. Growing counts mean the drive, not the file system, is the problem, and chkdsk is only buying time.
  4. Repair Windows files afterward. Once the file system is consistent, run DISM /Online /Cleanup-Image /RestoreHealth, then sfc /scannow. Corruption that reached the file system often reached system files too.
  5. Test the RAM. Faulty memory writes garbage to disk through a perfectly healthy file system, producing this crash again and again. Windows Memory Diagnostic rules it in or out.
  6. Check for storage driver and firmware updates. SSD firmware and storage controller drivers from the manufacturers fix real corruption bugs; install current versions once the drive checks out healthy.
If chkdsk finds more bad sectors every time it runs, stop. That is a drive in active decline. Image or copy the data off and replace the drive; repeated surface scans on a dying disk can finish it off.

If it still happens

If Windows will not boot, run chkdsk from the recovery menu’s Command Prompt (Troubleshoot → Advanced options → Command Prompt, the drive letter may differ there, often still C:). If corruption returns on a drive with clean SMART data and passing RAM, use System Restore, and consider that the storage controller or cable is corrupting writes.

Common questions

Can NTFS_FILE_SYSTEM delete my files? The crash itself does not delete data, but the underlying corruption can make files or folders unreadable, and a failing drive can get worse quickly. That is why backup is step one rather than an afterthought. chkdsk’s repairs can also orphan damaged files into FOUND folders, which beats losing them silently.

How is this different from FAT_FILE_SYSTEM (0x23)? They are the same failure in two different file system drivers. NTFS (0x24) covers your Windows and data partitions. FAT (0x23) covers USB sticks, SD cards, and the EFI boot partition. The code tells you which volume class to look at first.

Related errors

FAT_FILE_SYSTEM · KERNEL_DATA_INPAGE_ERROR · INACCESSIBLE_BOOT_DEVICE · CRITICAL_PROCESS_DIED