How to Fix BSOD NTFS_FILE_SYSTEM (0x00000024)
What error 0x00000024 means
NTFS is the file system Windows uses to organize everything on your drive — every file, folder, and piece of metadata passes through a driver called ntfs.sys. When that driver encounters a problem it cannot handle — a corrupted file-system structure, a sector it cannot read, or data that arrives already damaged — it stops the whole system with the NTFS_FILE_SYSTEM blue screen (stop code 0x00000024) rather than risk writing garbage over your files. The name is unusually direct for a blue screen: this one is about the file system and the drive underneath it.
The most common cause is exactly what the name points at: a hard drive or SSD that is starting to fail. Bad sectors, a worn-out SSD, or a drive with a failing controller all feed the NTFS driver data it cannot trust. But this blue screen has other triggers too. A sudden power loss or forced shutdown can leave the NTFS structures themselves inconsistent, even on a perfectly healthy drive. Outdated or buggy storage drivers — especially after a Windows feature update — can mishandle disk requests. Bad RAM can corrupt data on its way to the disk, so the file system looks broken when the memory is really at fault. And third-party antivirus, encryption, or disk-imaging tools install filter drivers that sit between Windows and the drive, and a buggy filter can crash NTFS outright. The fixes below work through these causes in the right order: protect your data first, repair the file system, then rule out drivers, RAM, and finally the drive hardware itself.
Common causes
- Failing hard drive or SSD: bad sectors, worn flash cells, or a dying controller feed the NTFS driver unreadable data — the most serious cause, and the one that risks your files.
- Corrupt NTFS file system: a power loss, forced shutdown, or interrupted update can leave file-system structures inconsistent even on a healthy drive.
- Outdated or buggy storage drivers: SATA, NVMe, or RAID controller drivers that mishandle disk requests are a classic trigger, especially after a Windows feature update.
- Faulty RAM: bad memory corrupts data in transit to the disk, so the file system looks broken when the real fault is a memory stick.
- Third-party disk filter drivers: antivirus, encryption, and disk-imaging tools sit between Windows and the drive, and a buggy filter can crash the NTFS driver.
How to fix error 0x00000024 — step by step
Work through these fixes in order. Step 1 comes first for a reason: this blue screen points at the drive, so your files are the thing at risk.
- Back up your data before anything else. NTFS_FILE_SYSTEM points at the drive, so the first move is to protect your files while the drive still reads. If Windows still boots, copy your documents, photos, and anything irreplaceable to an external drive or cloud storage right away. If Windows will not boot, boot from a Windows installation USB, choose Repair your computer, and use the Command Prompt to copy files with xcopy or robocopy to an external drive. Do not run disk repairs until your important data is safe, because a drive that is physically failing can get worse during a long scan.
- Boot into Recovery or Safe Mode. If the blue screen repeats at startup, interrupt the boot process three times in a row (hold the power button during the Windows logo) to reach the Recovery screen. Go to Troubleshoot > Advanced options > Command Prompt, or to Startup Settings and press 4 for Safe Mode. Working from Recovery or Safe Mode keeps the file system quiet while you repair it, and if the PC is stable in Safe Mode, a third-party driver or filter program is more likely than a dying drive.
- Run CHKDSK to repair the NTFS file system. From an admin Terminal or the Recovery Command Prompt, run
chkdsk C: /f /rand type Y when asked to schedule the check, then restart so it runs before Windows loads. The /f flag fixes file-system errors and /r locates bad sectors and recovers readable data. Let it finish — on a large drive this takes a while, and interrupting it can leave the file system half-repaired. If CHKDSK reports bad sectors or the same errors keep returning after a clean pass, the drive hardware itself is suspect, not just the file system. - Repair system files with SFC and DISM. Open an admin Terminal (right-click Start > Terminal (Admin)) and run
sfc /scannowfirst, letting it finish completely. Then runDISM /Online /Cleanup-Image /RestoreHealth, which repairs the component store SFC relies on. If SFC found corruption it could not fix, run it once more after DISM completes. Corrupted Windows files can crash the NTFS driver just as surely as a bad drive can, so this step rules out the software side before you spend money on hardware. - Update storage and chipset drivers. Press Win + X and open Device Manager, then expand Disk drives and IDE ATA/ATAPI controllers. Right-click each storage controller and choose Update driver, but do not stop there: download the latest chipset and storage (SATA, NVMe, or RAID) drivers from your motherboard or PC maker's support page. Outdated or generic storage drivers are a classic NTFS_FILE_SYSTEM trigger, especially after a Windows feature update. If the crashes started right after a driver update, use the Driver tab's Roll Back Driver option instead.
- Check the drive's health with SMART data. Download a free SMART reader such as CrystalDiskInfo and look at the drive's health status and the reallocated sector count, pending sector count, and uncorrectable error count. A status of Caution or Bad, or any rising reallocated-sector number, means the drive is physically wearing out — no software fix will save it, and replacement is the only real fix. SSDs also wear out: check the remaining life percentage and the total terabytes written against the manufacturer's endurance rating.
- Test the RAM and disable third-party disk filters. Bad RAM can corrupt data on its way to the disk, which the NTFS driver then trips over. Press Win + R, type
mdsched.exe, and choose Restart now and check for problems. Also consider third-party disk tools: antivirus, encryption, and disk-imaging programs install file-system filter drivers that sit between Windows and the drive, and a buggy filter can crash NTFS. Temporarily uninstall (not just disable) any such program added around the time the crashes began, and see whether the blue screens stop.
Did this fix it? Quick checklist
- Important files backed up to an external drive or cloud storage
- CHKDSK completed with no new bad sectors on a second pass
- SFC and DISM both completed without unrepairable corruption
- SMART health status reads Good with no rising reallocated sectors
If crashes continue after all seven steps, check the drive cables and connections — reseat the SATA data and power cables, or try a different SATA port or M.2 slot, since a loose or damaged cable produces read errors that look exactly like a failing drive. If the drive still reports bad sectors or disappears from BIOS intermittently, replace it and restore from the backup you made in step 1: a drive that is failing only gets worse, and no software fix can repair worn-out hardware.
Frequently asked questions
What causes NTFS_FILE_SYSTEM (0x00000024)?
The NTFS file-system driver (ntfs.sys) ran into a problem it could not handle. The top causes are a failing hard drive or SSD, a corrupted NTFS file system after a crash or power loss, outdated or buggy storage drivers, bad RAM corrupting data in transit, and third-party disk filter drivers from antivirus or encryption software.
Does 0x00000024 always mean my hard drive is dying?
No, but a dying drive is the cause you must rule out first, because it is the one that risks your data. Corrupt file-system structures, bad storage drivers, and faulty RAM all produce the same blue screen. That is why the fix order starts with a backup, then CHKDSK, then SFC and DISM, then drivers and a SMART health check, before concluding the drive needs replacing.
Can CHKDSK make things worse on a failing drive?
On a drive that is physically failing, a long CHKDSK scan can stress it further, which is why backing up your data first matters so much. If the drive is clicking, disappearing from BIOS, or extremely slow, skip the scan and clone the drive or copy files off it first. On a healthy drive with only file-system corruption, CHKDSK is safe and is the correct fix.
Will reinstalling Windows fix 0x00000024?
It can fix it only if the cause is software — corrupted system files, bad drivers, or a damaged file system. It will not fix a physically failing drive or bad RAM, and the blue screen will return after the reinstall. Check the drive's SMART health and test the RAM before doing a clean install, since a reinstall is a last resort that wipes your setup.