In almost all Windows systems that use NTFS as the main file organization structure, you can often see a failure in the ntfs.sys file. The blue screen (Windows XP or versions of a rank higher, it doesn’t matter) displays the full stop code 0x00000024 NTFS_FILE_SYSTEM, which often indicates a malfunction of the hard drive and leads to damage to the file system itself. But this is only a general case, since there can be many more reasons for the appearance of the same stop code. Fix the problem easily. How to do it? Read the article.
File error: what is the reason?
The ntfs.sys system component is the most common driver file responsible for the ability to read data from NTFS partitions, as well as for writing information to such sectors. In other words, the driver communicates between the file organization of the hard disk, the operating system and the hard drive itself.
But why then does the ntfs.sys file fail? The blue screen (in Windows 7, for example) contains a special stop code, and also gives a recommendation for checking the hard drive. Here, as concomitant reasons for the appearance of such an error, one can add the following:
- random system crashes;
- incorrectly set operation mode of the SATA hard drive;
- disk corruption or critical errors;
- mismatch, improper installation or outdated drivers;
- errors in the registry.
Rollback system
So, if the user receives an error message about the ntfs.sys component (blue screen), the first thing you can try to fix the problem is the usual system recovery.
If such an operation cannot be performed in automatic mode, use the F8 key at startup and select the download of the last successful configuration.
When ntfs.sys (blue screen) crashes, Windows 10 cannot be repaired by this technique. It will take quite a while to switch from one menu to another. But on all systems, for a clean solution, if recovery does not work, it is better to use booting from removable media, followed by calling the command console. By the way, it is the command line in most cases that offers the most effective tools for troubleshooting problems in idle systems.
Disk Check and NTFS Partition Recovery
If you carefully look at the message on the screen, you will notice that there is a recommendation for an immediate check of the hard drive.
Thus, if an ntfs.sys file error occurs (the blue screen prevents normal loading), after starting from a disk or flash drive in the diagnostics section, call the command line (Shift + F10) and first write down the line for checking the hard drive chkdsk c: / f (if appears a message about the impossibility of the command execution, agree, and the check will be performed upon repeated download).
At the end of the process, exit the console (exit command), restart the system. In the event of a repeated failure of the ntfs.sys component (the blue screen appears again), boot from the media, but at the command line, write the chkdsk c: / p file system recovery line, then try to exit the console again and reboot.
SATA mode change
However, due to the incorrectly set operating mode of the SATA hard drive, the above methods may not give the desired result.
In this case, when you turn on the computer or laptop, use the BIOS settings entry, where among the parameters of the hard drive you need to find the SATA mode and switch it from AHCI to IDE. It is recommended to check the hard drive at the boot stage from removable media in the IDE mode.
Windows crashes: updating and rolling back drivers
Not the last role in the appearance of such failures is played by drivers. If a normal start of the system is not possible, you can try to load it in Safe Mode (safe start). You may need to uninstall or reinstall some installed drivers. If the failure occurred after an incorrect update, it is better to use the rollback tool in the "Device Manager".
The best option, if you have a constant Internet connection, when downloading with support for network drivers is used, will be the use of automated updater programs (for example, Driver Booster). They are able to independently find updates of all the drivers available in the system, install them from official resources without user intervention in the download and integration process.
Registry issues
If the system can be booted at least somehow, you should thoroughly clean the registry. Manually doing this is recommended only to specialists, and ordinary users can be advised to use simple portable utilities for automatic login.
Microsoft experts recommend using their own development called Scanreg, which is presented as a portable program with one executable EXE file.
Viruses
If the system has been exposed to viruses, it does not boot even after applying the above solutions, you will have to check it. But how to do it, because the start is impossible?
Here come to the rescue disk programs with the general name Rescue Disk, with which you can boot like a recovery disk, use in-depth scanning of all available partitions. Perhaps this will help in solving the problem.
Versatility
It remains to add that the considered methods help in almost all cases. When restoring NTFS partitions, you can still use the sfc / scannow command to check and restore system components. This is not always necessary, but as an additional tool, in general, it will not hurt.