Error 0x00000024 (NTFS_FILE_SYSTEM) in Windows

STOP code 0x00000024 is usually displayed as NTFS_FILE_SYSTEM and indicates that Windows has encountered a critical error while working with the NTFS file system. The most common causes are corruption of the NTFS structure, issues with the storage device (HDD/SSD/NVMe), storage controller driver failures, or (less frequently) faulty RAM.

Symptoms

• Blue screen with code 0x00000024 or the message NTFS_FILE_SYSTEM.
• Reboots during Windows startup, when copying/installing programs, or when working with large files.
• Slowdowns, freezes, read/write errors, "folder/file is corrupted."
• Errors such as Disk, Ntfs, storahci, stornvme, iaStor, etc., may appear in the event log.

Common Causes

1. Corruption of the NTFS file system (after sudden power loss, freezes, improper shutdowns).
2. Storage issues: SSD/HDD degradation, bad sectors, controller errors, SATA cable/port issues.
3. Storage drivers: AHCI/RAID/NVMe driver, third-party filters (antivirus/encryption/backup).
4. RAM errors (data corruption when writing to the file system).
5. Overclocking/system instability, overheating, power drops.

Before You Begin: Important Steps to Take

• If you have access to the system — back up important data to another disk/cloud.
• If Windows does not boot, use WinRE or a Windows bootable USB to:
  • copy data (via Notepad/Command Prompt),
  • run disk diagnostics.

If there is suspicion of a failing disk (HDD clicks, regular read errors, SMART warnings) — first copy data, then perform checks.

Method 1. Boot into Safe Mode / WinRE

If Windows boots

1. Start → Settings → Update & Security → Recovery.
2. Advanced startup → Restart now.
3. Then: Troubleshoot → Advanced options → Startup Settings → Restart → (4) Safe Mode.

If Windows does not boot

• Interrupt the boot process 3 times (by turning off at the Windows logo) → WinRE will open, or boot from the Windows installation media → System Recovery.

Method 2. Disk Check: CHKDSK (Main Step)

In working Windows (as administrator)

Open Terminal/PowerShell/Command Prompt (Administrator) and run:

chkdsk C: /f

If the system prompts to schedule a check on reboot:

Y

Restart the PC.

More thorough check (longer)

If you suspect reading issues/bad sectors:

chkdsk C: /f /r

/r includes searching for damaged sectors and attempting to recover readable data. This can take a long time.

In WinRE (if Windows does not boot)

1. Advanced options → Command Prompt
2. Find out the letter of the system partition (in WinRE it may differ):

diskpart
list vol
exit

3. Run the check (substitute the correct letter, e.g., D:):

chkdsk D: /f

Method 3. System File Recovery: SFC and DISM

In Windows (administrator)

sfc /scannow

If SFC reports that it could not fix some files, run:

DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow

In WinRE (offline recovery)

If the system does not boot, you can check the offline image (example; letters may differ):

sfc /scannow /offbootdir=D:\ /offwindir=D:\Windows

Method 4. Check Disk Status (SMART) and Logs

Quick SMART check using Windows

wmic diskdrive get model,status

If the status is not OK — this is a warning sign. For more accurate diagnostics, use the manufacturer's SSD/HDD utilities or third-party SMART tools.

Check NTFS/Disk events

Open Event Viewer → Windows Logs → System and filter sources:

• Disk
• Ntfs
• storahci, stornvme
• RAID drivers (e.g., iaStorA)

Repeated input/output errors are a common sign of disk/controller issues.

Method 5. Storage Drivers and Controller (SATA/AHCI/NVMe/RAID)

1. Open Device Manager:
   • IDE ATA/ATAPI Controllers, Storage Controllers, Disk Drives.
2. Update:
   • chipset driver (from the laptop/motherboard manufacturer's website),
   • NVMe/RAID/AHCI driver (if used),
   • SSD firmware (official utility from the manufacturer).

Additionally:

• If using third-party antivirus/encryption/filter drivers, temporarily uninstall/disable them and check if the BSOD recurs.
• For SATA drives, check the cable/port (replacing the cable often resolves instability).

Method 6. Check RAM

RAM errors can lead to data corruption on the disk and NTFS crashes.

Quick check

• Win+R → mdsched.exe → Restart and check.

More reliably

• MemTest86 (bootable test) — if possible.

If the test shows errors — disable XMP/EXPO overclocking, check the sticks one by one, replace the faulty one.

Method 7. System Restore / Roll Back Updates (if started after changes)

If the error appeared after an update, driver, or software:

• WinRE → Advanced options → System Restore (restore point)
• WinRE → Uninstall updates (latest quality/feature)

When the Problem is Almost Certainly with the Disk (and What to Do)

Signs:

• SMART warns of degradation/errors.
• CHKDSK finds errors repeatedly.
• There are Disk/Ntfs errors in events, read/write failures.
• The system often "hangs" when accessing the disk.

Actions:

1. Urgently copy data.
2. Replace the storage device.
3. After replacement — clean install of Windows or restore from an image/backup.

Useful Commands (Cheat Sheet)

:: Disk check
chkdsk C: /f
chkdsk C: /f /r

:: System files
sfc /scannow
DISM /Online /Cleanup-Image /RestoreHealth

:: SMART (simplified)
wmic diskdrive get model,status

:: Determine volume letters in WinRE
diskpart
list vol
exit

If Nothing Worked

• Collect a memory dump and analyze:
  • C:\Windows\Minidump\*.dmp
  • C:\Windows\MEMORY.DMP
• Check which module is causing the crash (often it's a storage driver or filter).
• If the issue recurs and there are no obvious software causes — hardware diagnostics (disk, RAM, controller, power) become a priority.

See Also

• Error 0x0000007A (KERNEL_DATA_INPAGE_ERROR)
• Error 0x000000F4 (CRITICAL_OBJECT_TERMINATION)
• Error 0x0000001E (KMODE_EXCEPTION_NOT_HANDLED)