ERRORBlue screen0x00000024
NTFS_FILE_SYSTEMStop code 0x00000024
NTFS_FILE_SYSTEM (stop code 0x00000024) indicates a problem in ntfs.sys, the driver for the NTFS file system, and almost always reflects disk corruption or a failing drive. Checking the disk with chkdsk and testing the drive's health are the priorities; a drive showing errors should be backed up and replaced.
What it means
NTFS_FILE_SYSTEM, bug check 0x00000024, is raised when ntfs.sys, the driver that implements the NTFS file system, hits a problem it cannot handle. In the large majority of cases this means the file system or the drive is corrupted, not that the driver itself is at fault.
Most likely causes
- Disk corruption from an unclean shutdown, power loss or interrupted write.
- A failing drive: bad sectors, reallocated sectors, or an SSD near end of life; check SSD health.
- Loose or faulty cables on a SATA drive.
- A misbehaving disk-filter driver (some antivirus or backup products), less commonly.
Fixes
1. Repair the file system:
chkdsk C: /f /r/r also scans for and recovers readable data from bad sectors. Run it from the recovery environment if Windows will not stay up. See chkdsk.
2. Check drive health. Read SMART with CrystalDiskInfo or the vendor tool. Reallocated or pending sectors, or a raised warning, mean the drive should be replaced.
3. Reseat cables on desktop SATA drives; a marginal connection causes intermittent file-system errors.
4. Repair system files in case Windows components were damaged:
DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow5. Temporarily remove disk-filter software (third-party antivirus, backup agents) if the drive tests healthy but the crashes continue.
General blue-screen approach
Most stop codes are caused by drivers, hardware faults, or corrupted system files, in that order of likelihood. The efficient path is:
- Note what changed. A new driver, a Windows update, new hardware, or an overclock immediately before the crashes began is the prime suspect. Roll it back or remove it.
- Boot to Safe Mode if Windows will not stay up: hold Shift and restart, or interrupt boot three times to reach the recovery environment, then Troubleshoot → Advanced options → Startup Settings → Safe Mode.
- Update or roll back drivers, especially graphics, storage and chipset, from the vendor rather than only Windows Update.
- Repair system files from an elevated prompt:
DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow- Test hardware: Windows Memory Diagnostic for RAM, the drive vendor's tool and chkdsk for storage, and check temperatures.
- Read the dump. The minidump in
C:\Windows\Minidumpnames the faulting driver when analysed with WinDbg or a tool like BlueScreenView.
Frequently asked questions
What causes NTFS_FILE_SYSTEM?
A fault in the NTFS driver processing the file system, usually because the file system or the drive beneath it is corrupted. Bad sectors, a failing drive, a loose cable, or damage from an unclean shutdown are typical. Occasionally a buggy disk-related driver or antivirus filter is involved.
How do I fix NTFS_FILE_SYSTEM?
Run chkdsk /f /r on the affected volume to repair the file system and recover readable sectors, check the drive's SMART health, and reseat data and power cables. If SMART shows reallocated sectors or the drive keeps producing errors, back up immediately and replace it.