Symptoms
The NTFS_FILE_SYSTEM error (stop code 0x00000024) appears as a blue screen during Windows startup, often immediately after the Windows logo or during the loading phase. The system may restart in a loop, preventing normal boot. In some cases, you may see the error after a recent driver update, disk cleanup, or power outage. The error is typically accompanied by a reference to the ntfs.sys driver file.
Root Causes
1. File System Corruption
The most common cause is corruption in the NTFS file system, often due to improper shutdowns, bad sectors, or disk errors. This prevents Windows from reading critical boot files.
2. Faulty or Incompatible Drivers
Third-party drivers (especially storage, antivirus, or filter drivers) that interact with the file system can trigger this BSOD. A recent driver update or installation is a common trigger.
3. Failing Hard Drive or SSD
Physical damage or wear on the storage device, including bad sectors, can cause the NTFS driver to fail. This is more common on older mechanical hard drives but can affect SSDs as well.
4. Memory (RAM) Issues
Faulty RAM can corrupt data being written to or read from the disk, leading to file system errors.
Step-by-Step Fix
Prerequisites
You will need a Windows installation media (USB/DVD) or access to the Windows Recovery Environment (WinRE). If you cannot boot normally, boot from the installation media and select Repair your computer.
Step 1: Run CHKDSK from Command Prompt
- Boot from Windows installation media or enter WinRE (via power button reset 3 times).
- Go to Troubleshoot > Advanced options > Command Prompt.
- Type the following command and press Enter:
chkdsk c: /f /r - Press Y if prompted to schedule a check on next boot (if running from within Windows). Wait for the scan to complete. This may take hours on large drives.
- After completion, type
exitand restart your PC.
Step 2: Run System File Checker (SFC)
- Open Command Prompt as described above.
- Type:
sfc /scannow - Wait for the scan to finish. If it finds corrupt files, it will attempt to repair them. Restart your PC.
Step 3: Run DISM to Repair System Image
- In Command Prompt, type:
DISM /Online /Cleanup-Image /RestoreHealth - If you are in WinRE, use:
DISM /Image:C:\ /Cleanup-Image /RestoreHealth /Source:C:\Windows\WinSxS - Wait for completion (may take 15-30 minutes). Restart.
Step 4: Check Disk for Bad Sectors
- Open Command Prompt as administrator.
- Type:
chkdsk c: /scan - If bad sectors are found, consider replacing the drive. You can also use third-party tools like CrystalDiskInfo to check S.M.A.R.T. status.
Step 5: Disable or Update Problematic Drivers
- Boot into Safe Mode (press F8 during startup or use WinRE > Troubleshoot > Advanced options > Startup Settings > Restart > Enable Safe Mode).
- Open Device Manager (
devmgmt.msc). - Look for devices with yellow exclamation marks, especially under Storage controllers, IDE ATA/ATAPI controllers, or System devices.
- Right-click and select Update driver or Uninstall device (then restart).
- If you suspect a recent driver, use System Restore to revert: WinRE > Troubleshoot > Advanced options > System Restore.
Step 6: Test RAM
- Boot into WinRE and open Command Prompt.
- Type:
mdsched.exe - Choose Restart now and check for problems. The system will boot into Windows Memory Diagnostic. Let it run (may take 30+ minutes).
- If errors are found, replace the faulty RAM module.
Alternative Fixes
Use Startup Repair
From WinRE, select Troubleshoot > Advanced options > Startup Repair. This can automatically fix boot issues.
Perform a System Restore
If you have a restore point from before the error started, use WinRE > Troubleshoot > Advanced options > System Restore.
Reset or Reinstall Windows
As a last resort, from WinRE choose Troubleshoot > Reset this PC. Choose to keep files or remove everything. If the drive is failing, replace it before reinstalling.
Prevention
- Regularly run CHKDSK (e.g., monthly) to catch disk errors early.
- Keep Windows and drivers updated via Windows Update and manufacturer websites.
- Use a UPS to prevent corruption from sudden power loss.
- Monitor disk health using tools like CrystalDiskInfo or
wmic diskdrive get statusin Command Prompt. - Avoid force shutdowns – always use the Start menu shutdown option.
- Back up important data regularly to an external drive or cloud storage.
If the error persists after all steps, the storage device is likely failing and should be replaced immediately to avoid data loss.