Windows stopped with an NTFS_FILE_SYSTEM (bug check 0x00000024) because the NTFS file system driver encountered an unexpected condition it could not handle. This most commonly indicates corruption on the disk, bad sectors, a failing storage device, or a problem with the NTFS driver itself.
The storage drive (HDD or SSD) has bad sectors or is beginning to fail, causing the NTFS driver to encounter unreadable or corrupted file system structures.
File system metadata on the NTFS volume is corrupted, often caused by an abrupt power loss or improper shutdown.
A faulty SATA/NVMe cable, controller, or connector is causing intermittent read/write errors that corrupt NTFS structures.
The storage controller driver is buggy and returning incorrect data to the NTFS driver.
NTFS.sys itself (the Windows NTFS driver) has a bug triggered by a specific sequence of operations — less common but addressed by Windows updates.
How to fix it
Run CHKDSK on the affected volume from an elevated Command Prompt: `chkdsk C: /f /r /x` (replace C: with the affected drive letter). This requires a reboot to run before Windows loads. Let it complete fully.
Check drive health using the manufacturer's diagnostic tool (e.g., CrystalDiskInfo, Samsung Magician, WD Dashboard) or run `wmic diskdrive get status` to get a quick S.M.A.R.T. status check.
Check S.M.A.R.T. data in detail — look for reallocated sectors, pending sectors, or uncorrectable errors. Any non-zero values in these attributes indicate a failing drive.
Reseat or replace the SATA or NVMe data cable. On desktop systems, try a different port on the motherboard.
Update the storage controller driver from the motherboard or system manufacturer's website.
Run `sfc /scannow` in an elevated Command Prompt to repair any Windows system files that may have been corrupted by the disk problem.
If the drive is failing (confirmed by S.M.A.R.T. data or multiple CHKDSK bad sectors), back up data immediately and replace the drive.
