Error in the ntfs.sys file (blue screen): what's the reason and how to fix the problem?
Virtually all Windows-based systems, whereAs the basic structure of the organization of files NTFS is used, often it is possible to meet a failure in the file ntfs.sys. The blue screen (Windows XP or higher versions, no matter) displays the full stop code 0x00000024 NTFS_FILE_SYSTEM, which often indicates a hard disk failure and entails damage to the file system itself. But this is only a general case, because the reasons for the appearance of the same stop code can be much more. Eliminating the problem is easy. How to do it? Read in the article.
Error in the file: what is the reason?
The system component ntfs.sys is the most common driver file that is responsible for reading data from NTFS partitions, as well as for writing information to such sectors. In other words, the driver implements a connection between the file organization of the hard disk, the operating system and the hard drive itself.
But why then there is a glitch in the ntfs file.sys? 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 well as the attendant reasons for the appearance of such an error, you can add the following:
- random system failures;
- incorrectly installed mode of operation of the SATA hard drive;
- damage to the disk or the presence of critical errors;
- inconsistency, improper installation or obsolete drivers;
- errors in the system registry.
System rollback
So, if a user receives an error message about the ntfs.sys component (blue screen), you can first try to fix the problem with a normal system restore.
If you can not perform such an operation in automatic mode, use the F8 key at startup and select the last successful configuration.
When ntfs crashes.sys (blue screen), Windows 10 such a technique can not be restored. It will take a long time to move from one menu to another. But in all systems for cleanliness of the solution, if recovery does not work, it is better to use the boot from removable media, then call the command console. By the way, it is the command line in most cases that offers the most effective tools for eliminating problems in non-working systems.
Checking the drive and restoring the NTFS partition
If you look closely at the message on the screen, you can see that there is a recommendation for an immediate hard disk check.
Therefore, if an error occurs with the ntfs file.sys (blue screen prevents normal loading), after starting from the disk or the flash drive in the diagnostics section, call the command line (Shift + F10) and first write the scan string for the hard disk chkdsk c: / f (if you see a message that the command can not be executed, the test will be performed upon reloading).
At the end of the process, exit the console (commandexit), restart the system. If the failure occurs again in the ntfs.sys component (the blue screen appears again), boot from the media, but on the command line, type the line for restoring the chkdsk c: / p file system, then try again to exit the console and reboot.
Changing SATA Mode
However, due to the incorrectly installed mode of operation of the SATA hard drive, the above methods may not yield the desired result.
In this case, when you turn on the computer orlaptop, use the input to the BIOS settings, 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 hard disk at the stage of loading from removable media in IDE mode.
Windows crash: driver update and rollback
Not the least role in the appearance of such failures playand drivers. If the normal start of the system is not possible, you can try to load it in the Safe Mode (Safe Start) mode. You may need to uninstall or reinstall some of the installed drivers. If the failure occurred after an incorrect update, it is better to use the rollback tool in the "Device Manager".
The optimal option, if there is a permanentconnection to the Internet, when using a boot with support for network drivers, will be the use of automated programs-updateers (for example, Driver Booster). They are able to independently find updates to all available drivers in the system, install them from official resources without user intervention in the boot and integration process.
Registry issues
If the system can be booted at least somehowyou should clean the registry properly. It is recommended to do this manually only for specialists, and ordinary users can be advised to use unpretentious portable utilities for automatic entry.
Microsoft experts recommend using its 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 load even after applying the above solutions, you will have to test it. But how to do it, because the start is impossible?
Here the help comes disk programs with a commonname 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 methods consideredhelp 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 does not hurt.
