NTFS File System Error in Windows 11 (8 Solutions to Fix It)

The NTFS_FILE_SYSTEM error (Stop Code 0x00000024) usually occurs when Windows 11 detects a serious problem while trying to read, write, or access data on an NTFS-formatted drive. NTFS (New Technology File System) is the default file system used by Windows to store and manage files on hard drives and SSDs. When Windows detects a problem that could affect data integrity or system stability, it stops the operating system and displays a Blue Screen of Death (BSOD) to prevent further damage. In most cases, the error is caused by file system corruption, disk errors, faulty storage drivers, or failing storage hardware. If your PC keeps crashing or won’t start due to the NTFS_FILE_SYSTEM BSOD error, here are the most effective solutions to diagnose and fix it on both Windows 11 and Windows 10.

What Causes the NTFS_FILE_SYSTEM Blue Screen Error?

Windows relies on the NTFS file system to store, organize, and access files on your hard drive or SSD. If the file system becomes corrupted or Windows can’t communicate properly with the storage device, it may stop the operating system and display the NTFS_FILE_SYSTEM blue screen to prevent further data corruption.

The most common causes include:

1. File System Corruption: The most common cause is corruption within the NTFS file system itself. This can happen due to sudden power loss, improper shutdowns, or disk errors.
2. Disk errors or bad sectors: A failing hard drive or SSD with bad sectors can cause read and write failures that trigger the BSOD.
3. Outdated or corrupted storage drivers: Faulty SATA, NVMe, RAID, or chipset drivers may interrupt communication between Windows and your storage device.
4. Failing storage hardware: An aging or malfunctioning HDD or SSD can lead to frequent file system errors and unexpected crashes.
5. Faulty RAM: Defective memory can corrupt data before it is written to disk, eventually causing NTFS-related errors.
6. Malware or unexpected power loss: Viruses, forced shutdowns, or sudden power outages can damage the file system and result in blue screen errors.

Solution 1: Disconnect External Devices and Restart Your PC

A faulty USB drive, external hard drive, SD card, printer, or other peripheral can sometimes interfere with Windows during startup and trigger the NTFS_FILE_SYSTEM blue screen. Before performing advanced troubleshooting, disconnect all unnecessary external devices connected to your computer and reboot Windows.

1. Turn off your computer completely.
2. Disconnect all external devices except your keyboard and mouse.
3. Turn the PC back on and check if Windows starts normally.

If the blue screen no longer appears, reconnect your devices one at a time until you identify the one causing the problem. Once identified, update its driver or replace the faulty device if necessary.

Solution 2: Boot into Safe Mode

If the NTFS_FILE_SYSTEM blue screen prevents Windows from starting normally, try booting into Safe Mode. Safe Mode starts Windows with only the essential drivers and services, making it easier to troubleshoot problems caused by faulty drivers, recent updates, or software conflicts.

If Windows Can Boot

Press Windows + I to open Settings.

Go to System > Recovery.

Under Advanced startup, click Restart now.

After your PC restarts, select Troubleshoot > Advanced options > Startup Settings > Restart.

Press 4 or F4 to start Safe Mode, or press 5 or F5 to start Safe Mode with Networking.

If Windows Won’t Boot

If your PC is stuck in a boot loop:

• Turn on your computer. As soon as the Windows logo appears, press and hold the Power button to force it to shut down.
• Repeat this process three times. On the fourth startup, Windows should automatically enter the Windows Recovery Environment (WinRE).

• Select Troubleshoot > Advanced options > Startup Settings > Restart.
• After your PC restarts, press 4 or F4 to boot into Safe Mode.

If Windows starts successfully in Safe Mode, continue with the next solutions in this guide, such as running CHKDSK, SFC, and DISM, updating storage drivers, or uninstalling a recent Windows update.

Solution 3: Run CHKDSK to Repair File System Errors

The CHKDSK (Check Disk) utility scans your drive for file system corruption, bad sectors, and other disk-related errors that can trigger the NTFS_FILE_SYSTEM blue screen. If it finds any problems, Windows will attempt to repair them automatically.

If Windows Can Boot

1. Press Windows + S, type Command Prompt, then select Run as administrator.
2. Type the following command and press Enter:

chkdsk C: /f /r

3. If prompted to schedule the scan for the next restart, type Y and press Enter.
4. Restart your computer. Windows will scan and repair the drive before loading the operating system.

If Windows Won’t Boot

• Boot into the Windows Recovery Environment (WinRE).
• Go to Troubleshoot > Advanced options > Command Prompt.

• Run the diskpart command to identify the Windows installed drive

diskpart
list volume
exit

• Once you’ve identified the Windows drive, run:

chkdsk C: /f /r

Note: Replace C: with the correct drive letter if necessary.

The scan may take anywhere from a few minutes to several hours, depending on your drive’s size and condition. Avoid interrupting the process, as doing so could cause additional file system corruption.

Note: The /f switch fixes logical file system errors, while /r locates bad sectors, attempts to recover readable data, and marks damaged sectors so they aren’t used again.

Solution 4: Run Startup Repair

If the NTFS_FILE_SYSTEM blue screen prevents Windows from starting, Startup Repair can automatically detect and fix common boot-related problems, including missing or corrupted system files that may be causing the error.

If Windows Can Still Boot

• Press Windows + I to open Settings.
• Go to System > Recovery.
• Under Advanced startup, click Restart now.

• After your PC restarts, select Troubleshoot > Advanced options > Startup Repair.
• Choose your Windows installation and let the repair process complete.

If Windows Won’t Boot

If your PC is stuck in a boot loop:

1. Turn on your computer.
2. As soon as the Windows logo appears, press and hold the Power button to force it to shut down.
3. Repeat this process three times. On the fourth startup, Windows should automatically enter the Windows Recovery Environment (WinRE).
4. Select Troubleshoot > Advanced options > Startup Repair.
5. Wait while Windows scans for startup issues and applies any available fixes.

Once Startup Repair is complete, restart your computer and check whether the NTFS_FILE_SYSTEM blue screen has been resolved.

Solution 5: Repair Corrupted System Files Using SFC and DISM

Corrupted or missing Windows system files can also trigger the NTFS_FILE_SYSTEM blue screen. Windows includes two built-in tools, System File Checker (SFC) and Deployment Image Servicing and Management (DISM), that can scan for and repair these files.

Step 1: Run System File Checker (SFC)

1. Open Command Prompt as an administrator.
2. Type the following command and press Enter:

sfc /scannow

3. Wait for the scan to complete. This may take 10–20 minutes.
4. Restart your PC after the scan finishes.

If SFC reports that it found and repaired corrupted files, check whether the BSOD has been resolved.

Step 2: Run DISM (If SFC Doesn’t Fix the Problem)

If the error persists or SFC reports that it couldn’t repair some files, run the following DISM commands one at a time:

DISM /Online /Cleanup-Image /RestoreHealth

If Windows won’t boot, open Command Prompt from the Windows Recovery Environment (WinRE) and run:

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

Note: If your Windows installation is on a different drive, replace C: with the correct drive letter.

After the scan completes, restart your computer and check if the NTFS_FILE_SYSTEM error has disappeared.

Solution 6: Update or Reinstall Storage Drivers

Windows relies on storage drivers to communicate with your hard drive or SSD. If these drivers become outdated, corrupted, or incompatible after a Windows update, they can cause the NTFS_FILE_SYSTEM blue screen.

Update the Driver

1. Press Windows + X and select Device Manager.
2. Expand IDE ATA/ATAPI controllers or Storage controllers.
3. Right-click your storage controller (such as Standard SATA AHCI Controller, Intel Rapid Storage Technology (RST), or your NVMe controller) and select Update driver.
4. Click Search automatically for drivers and install any available updates.
5. Restart your computer.

Reinstall the Driver

If updating doesn’t help:

1. Open Device Manager.
2. Right-click the storage controller and select Uninstall device.
3. Confirm the removal.
4. Restart your PC. Windows will automatically reinstall the required driver during startup.

Tip: If the blue screen started after installing a new storage driver or chipset driver, try rolling back to the previous version. In Device Manager, open the driver’s Properties, go to the Driver tab, and click Roll Back Driver if the option is available.

Solution 7: Uninstall Recent Windows Updates

If the NTFS_FILE_SYSTEM error started shortly after installing a Windows update, the update may have introduced a compatibility issue with your system or storage drivers. Removing the most recent update can help determine whether it’s the cause.

If Windows Can Boot

1. Press Windows + I to open Settings.
2. Go to Windows Update > Update history.
3. Scroll down and click Uninstall updates.
4. Select the most recently installed quality or feature update and click Uninstall.
5. Restart your PC after the update is removed.

If Windows Won’t Boot

1. Boot into the Windows Recovery Environment (WinRE).
2. Select Troubleshoot > Advanced options > Uninstall Updates.
3. Choose one of the following:
   • Uninstall latest quality update (recommended first)
   • Uninstall latest feature update (if the problem began after upgrading to a new Windows version)
4. Follow the on-screen instructions and restart your computer.

Note: If uninstalling the update fixes the issue, pause Windows Updates temporarily until Microsoft releases a newer update that addresses the problem.

Solution 8: Check Your Hard Drive or SSD Health

If the NTFS_FILE_SYSTEM blue screen keeps returning after trying the previous fixes, your hard drive or SSD may be developing hardware problems. A failing drive can cause file system corruption, read/write errors, and repeated BSODs.

Check the Drive’s SMART Status

Windows includes a built-in command to check the drive’s basic SMART (Self-Monitoring, Analysis, and Reporting Technology) status.

1. Open Command Prompt as an administrator.
2. Run the following command:

wmic diskdrive get status

If the result shows OK, Windows hasn’t detected any obvious hardware problems. If it reports Pred Fail or anything other than OK, back up your important files immediately and consider replacing the drive.

Run a Manufacturer Diagnostic Tool

For a more thorough health check, use the diagnostic utility provided by your SSD or hard drive manufacturer. These tools can detect issues that the basic SMART status may not report.

Common examples include:

• Samsung SSD – Samsung Magician
• Western Digital – WD Dashboard
• Crucial SSD – Crucial Storage Executive
• Seagate – SeaTools
• Kingston SSD – Kingston SSD Manager

If the diagnostic tool reports bad sectors, excessive errors, or a failing drive, replace the storage device as soon as possible to prevent data loss.

Solution 9: Run Windows Memory Diagnostic

Faulty RAM can corrupt data before Windows writes it to the storage drive, which may eventually trigger the NTFS_FILE_SYSTEM blue screen. Running the built-in Windows Memory Diagnostic tool can help identify memory-related problems.

• Press Windows + S, type Windows Memory Diagnostic, and open the tool.
• Click Restart now and check for problems (recommended).
• Your computer will restart, and Windows will scan the memory for errors.

After the scan is complete, Windows will boot normally and display the test results. If memory errors are detected, replacing the faulty RAM may resolve the Blue Screen of Death error.

If Windows Won’t Boot

If you can’t access Windows, create a bootable MemTest86 USB drive using another computer and boot from it.

Allow the test to complete at least one full pass. If MemTest86 reports memory errors, one or more RAM modules may be defective.

If your computer has multiple RAM sticks installed, test them one at a time to identify the faulty module before replacing it.

Solution 10: Reset or Repair Windows

If you’ve tried all the previous solutions and the NTFS_FILE_SYSTEM blue screen still appears, your Windows installation may be too corrupted to repair using built-in tools. Resetting or repairing Windows can replace damaged system files while giving you the option to keep your personal files.

Reset This PC

If Windows can still boot:

1. Press Windows + I to open Settings.
2. Go to System > Recovery.
3. Click Reset PC next to Reset this PC.
4. Choose Keep my files to reinstall Windows without deleting your personal files. (Installed apps and settings will be removed.)
5. Follow the on-screen instructions to complete the reset.

Reinstall Windows Using Installation Media

If your PC won’t boot or the reset process fails, create a bootable Windows USB drive on another computer and perform a clean installation.

Before reinstalling Windows:

• Back up your important files if the drive is still accessible.
• Make sure you have your Microsoft account credentials and product key (if required).
• Disconnect unnecessary external devices during the installation.

A clean installation removes corrupted system files and provides a fresh copy of Windows, but it also deletes installed applications and, depending on the option you choose, may erase personal files.

Important: If the NTFS_FILE_SYSTEM error continues even after reinstalling Windows, the problem is likely caused by failing hardware, such as a defective SSD, hard drive, RAM, or storage controller. In that case, inspect or replace the faulty component.

Final Thoughts

The NTFS_FILE_SYSTEM blue screen is usually a sign of file system corruption, disk errors, or problems with your storage hardware. In most cases, you can resolve the issue by running CHKDSK, repairing Windows system files, updating storage drivers, or removing a problematic Windows update.

Frequently Asked Questions