ErrorBase
Independent technical referenceOfficial site
  • Software and digital services
  • Operating system

NTFS_FILE_SYSTEM

NTFS_FILE_SYSTEM (0x24) on Windows: NTFS file system fault

Verified with sources3 sourcesReviewed Oct 4, 2026
Technician coming? See the 2 steps they must show you

Risk level

High

Professional inspection is recommended.

Urgency

High

Quick answer

Windows stopped because of a problem in ntfs.sys, the driver that reads and writes NTFS drives. Back up your files, then check the drive from its Properties, Tools tab.

Safety first

Stop and check this first

  • With disk errors, every repair can move or lose data: back up before checking the drive, and do not format or reset Windows without that copy.
  • If the recovery options ask for the BitLocker recovery key, do not try random keys: look for it only in your Microsoft account (aka.ms/myrecoverykey), your work or school account, a printout or the USB drive where you saved it. Microsoft support cannot retrieve it.

Safe checks you can perform

  • Backup
  • Check the drive from Properties
  • Free space and Event Viewer
  • System File Checker

Leave these tasks to a qualified professional

  • Do not attempt this professional task: Maker's storage diagnostic
  • Do not attempt this professional task: Dump and storage drivers

What a technician must be able to justify

Technician visit

These are the steps they must carry out and show you. Tick them as they work: if steps are skipped, do not accept a part swap.

These are not instructions for opening or handling the equipment yourself. They are the checks that should support a technical conclusion.

  1. Maker's storage diagnostic

    What they doThe technician runs the maker's hardware diagnostics for the storage subsystem and reviews disk errors in the system log.

    They must show youthe diagnostic report and the disk events.

    In writingwhether the drive passed and, if replaced, the part reference and reason.

  2. Dump and storage drivers

    What they doThey open the dump, use .cxr with parameter 3 and kb to see the stack, and if it points to a storage driver they test it with Driver Verifier.

    They must show youthe dump stack and the driver it points to.

    In writingwhich driver was updated or replaced and the conclusion.

Before accepting a part or repair

Nothing has been shown yet. Do not accept a part swap based on the code alone.

Follow these steps

Note: Follow the documented order. An error code identifies the affected system, but it does not prove by itself which part has failed.

  1. Backup

    No special tools

    Who:
    you.
    How:
    copy your important files to another drive or OneDrive before checking or repairing the drive.
    Result that matters:
    having a copy off the failing drive.
    If the copy finishes cleanly:
    carry on with the check.
    If errors appear while copying:
    stop and consult a technician.
    Evidence to keep:
    folders copied and errors shown.

    Evidence: Troubleshooting Windows unexpected restarts and stop code errors · Bug Check 0x24 NTFS_FILE_SYSTEM

  2. Check the drive from Properties

    No special tools

    Who:
    you.
    How:
    in File Explorer, right-click the drive, Properties, Tools, Check; accept the restart if asked.
    Result that matters:
    whether Windows finds file system errors.
    If it finds and repairs errors:
    the damage was in NTFS; watch whether the crash returns.
    If it finds none:
    check free space and Event Viewer.
    Evidence to keep:
    screenshot of the check result.

    Evidence: Bug Check 0x24 NTFS_FILE_SYSTEM

  3. Free space and Event Viewer

    No special tools

    Who:
    you.
    How:
    check under This PC that the drive has at least 10% to 15% free; in Event Viewer, System, look for disk-related errors.
    Result that matters:
    whether space is low or there were earlier disk errors.
    If space is low:
    free some and test again.
    If there are disk errors:
    the case moves to the maker's diagnostic.
    Evidence to keep:
    screenshot of free space and events.

    Evidence: Troubleshooting Windows unexpected restarts and stop code errors · Bug Check 0x24 NTFS_FILE_SYSTEM

  4. System File Checker

    No special tools

    Who:
    you, from a Command Prompt as administrator.
    How:
    run SFC /scannow and restart when it finishes.
    Result that matters:
    whether SFC finds and repairs damaged Windows files.
    If it repairs files and the crash stops:
    the damage was in system files.
    If it finds nothing and the crash continues:
    hand the PC to a technician.
    Evidence to keep:
    screenshot of the SFC result.

    Evidence: Bug Check 0x24 NTFS_FILE_SYSTEM

Still not solved

If the error persists, stop here. See what the technician must do and show you.

Where this code applies

A code is meaningful only inside the right product and version context.

Primary scope

System
Software and digital services
Brand
Microsoft Windows
Product type
Operating system

Known code variants

  • 0x00000024
  • 0x24
  • NTFS FILE SYSTEM
  • Ntfs.sys
  • STOP 0x00000024
  • stop code NTFS_FILE_SYSTEM

What it means

Microsoft defines bug check 0x00000024 as a problem in ntfs.sys, the driver that lets the system read and write NTFS drives. Possible causes it gives are corruption in the NTFS file system, bad sectors on the disk and corrupted SATA or IDE drive drivers affecting reads and writes. In the past, nonpaged pool depletion could also cause it. The code says where the failure happened (the file system), not whether the drive is faulty.

Warnings and stop conditions

  • Higheditorial warning

    With disk errors, every repair can move or lose data: back up before checking the drive, and do not format or reset Windows without that copy.

    Evidence: Bug Check 0x24 NTFS_FILE_SYSTEM

  • Mediumsource verified

    If the recovery options ask for the BitLocker recovery key, do not try random keys: look for it only in your Microsoft account (aka.ms/myrecoverykey), your work or school account, a printout or the USB drive where you saved it. Microsoft support cannot retrieve it.

    Evidence: Find your BitLocker recovery key

Symptoms and causes

Probable causes · in order

  • NTFS file system corruptionCommon

    Confirmed if the drive error check finds and fixes file system errors.

    Evidence: Bug Check 0x24 NTFS_FILE_SYSTEM

  • Bad sectors on the drivePossible

    You can tell because the check or the maker's diagnostic finds damaged sectors, sometimes with disk errors in Event Viewer.

    Evidence: Bug Check 0x24 NTFS_FILE_SYSTEM

  • Corrupted SATA or IDE drive driverPossible

    If the drive passes the tests, Microsoft points to the storage driver affecting reads and writes.

    Evidence: Bug Check 0x24 NTFS_FILE_SYSTEM

  • Low free space on the drivePossible

    Microsoft recommends 10% to 15% free for swap files and other functions; you can see it under This PC.

    Evidence: Troubleshooting Windows unexpected restarts and stop code errors · Bug Check 0x24 NTFS_FILE_SYSTEM

Virtual technician

Does NTFS_FILE_SYSTEM still appear after these checks?

Answer a few questions to narrow down the likely cause and the safest next action. Guidance only - it never replaces a professional.

Start diagnosis

Sources and technical references

  1. 1

    Troubleshooting Windows unexpected restarts and stop code errors

    Microsoft · 2026 · official_doc

  2. 2

    Bug Check 0x24 NTFS_FILE_SYSTEM

    Microsoft · 2026 · official_doc

  3. 3

    Find your BitLocker recovery key

    Microsoft · 2026 · official_doc

Sources: Troubleshooting Windows unexpected restarts and stop code errors · Bug Check 0x24 NTFS_FILE_SYSTEM · Find your BitLocker recovery keyreviewed 2026-10-04 · verified

Was this entry useful?