Storage · critical

How to fix NTFS_FILE_SYSTEM (0x24)

Storage troubleshooting guide

What this error means

Windows stopped because of a problem in ntfs.sys, the driver that reads and writes NTFS drives. The blue screen often names ntfs.sys after "What failed". Microsoft names disk corruption as a likely cause: errors in the NTFS file system, bad sectors on the drive, or damaged storage drivers. Programs that constantly monitor the disk, such as antivirus, backup and defragmentation tools, can also be involved, and very low free space makes problems more likely.

Updated

Applies to
Windows 11 and Windows 10
Difficulty
Beginner to intermediate
Before changes
Medium if the drive is failing: long scans can stress it

Reviewed by Matyáš Rada · Documentation checked: 2026-10-31 · Checked against Microsoft's bug check documentation; not tested on every configuration.

Before you begin

Back up important files first. If the crash names ntfs.sys, this is the right guide; the file is part of Windows and should not be downloaded or replaced manually. If Windows cannot start, see the startup guide.

Work through these checks

0 of 7 complete
01Back up your files

This stop code is often linked to a damaged file system or bad sectors, which can mean data loss.

  1. Copy important files to an external drive or cloud storage now.
  2. If Windows does not start, connect the drive to another PC to copy the files.
What to expect

Your important files are safe on another device.

If it does not help

Continue with step 2.

Browse related errors
02Check the drive with chkdsk

Microsoft names corruption in the NTFS file system and bad sectors as causes; chkdsk repairs the file system and maps bad sectors.

  1. Open Terminal (Admin) and run chkdsk C: /f /r. Answer Y and restart so the check runs before Windows starts.
  2. For another drive, replace C: with its letter; it is checked immediately.
  3. If Windows does not start, run the same command from the recovery Command Prompt (check the drive letter with dir first).

Chkdsk /r can take hours on large hard drives. Do not interrupt it.

What to expect

Chkdsk completes and reports that it fixed any errors.

If it does not help

If chkdsk finds bad sectors, check the drive's health in step 3 before trusting it again.

Browse related errors
03Check the drive's health and Event Viewer

Microsoft recommends checking the System log for drive errors and running the manufacturer's storage diagnostics.

  1. Open Event Viewer (Win + R, eventvwr.msc) > Windows Logs > System and look for disk, Ntfs or storage controller errors near the crash time.
  2. Run the drive maker's diagnostic tool or a S.M.A.R.T. viewer such as CrystalDiskInfo and check its health status.
What to expect

No repeated disk errors, and the drive reports good health.

If it does not help

Repeated disk errors or a Caution/Bad health status mean the drive should be replaced (step 7).

Browse related errors
04Free up space

Microsoft recommends keeping 10% to 15% of the drive free.

  1. Open Settings > System > Storage and use Cleanup recommendations or Temporary files.
  2. Move large files such as videos to another drive, and uninstall programs and games you no longer use.
What to expect

At least 10% to 15% of the drive is free.

If it does not help

Keep that much space free in future.

Browse related errors
05Temporarily disable disk-monitoring software

Microsoft suggests disabling virus scanners, backup programs and defragmentation tools that continually monitor the system.

  1. Pause or uninstall third-party antivirus, backup and disk optimization tools, then use the PC normally for a while.
  2. If the crashes stop, install the latest version of the program or replace it.

Do not leave the PC without antivirus protection.

What to expect

You know whether one of these programs is involved.

If it does not help

Microsoft Defender protects the PC while a third-party antivirus is removed.

Browse related errors
06Update storage drivers and repair system files

Microsoft notes that damaged storage drivers can break reading and writing to the disk.

  1. Install the latest chipset and storage controller drivers (SATA/AHCI, Intel RST, NVMe) from your PC or motherboard maker, and update the SSD firmware with the drive maker's tool.
  2. In Terminal (Admin), run DISM /Online /Cleanup-Image /RestoreHealth and then sfc /scannow.
What to expect

Drivers are current and SFC reports no remaining problems.

If it does not help

If crashes continue, also test the RAM with Windows Memory Diagnostic (mdsched.exe), since faulty memory can corrupt file system data.

Browse related errors
07Replace the drive if errors keep returning

If chkdsk keeps finding new errors, the drive itself is failing.

  1. Make sure your backup is complete.
  2. Replace the drive and reinstall Windows, or clone the old drive to the new one if it can still be read.
  3. If the drive is under warranty, contact its maker.
What to expect

The PC runs without NTFS_FILE_SYSTEM crashes on the new drive.

If it does not help

If the stop code appears on a new drive too, have the storage controller or motherboard checked.

Browse related errors

Possible causes

  • Errors in the NTFS file system
  • Bad sectors on the drive
  • Damaged or outdated storage drivers
  • Antivirus, backup or disk tools that constantly monitor the drive
  • Very little free space on the drive

Useful Windows tools

These commands open Windows tools. Review changes before applying them.

eventvwr.msc

Sources & further reading