All Windows operating systems, including the most stable seventh or newest tenth version, are characterized by the appearance of failures when the system does not boot in normal mode and informs the user that the computer does not start correctly. What is the reason and how to deal with it, see below.
The computer does not start correctly (Windows 8.1, 8, 10): the main causes of crashes
As for the reasons that cause this behavior of the system, there can be a lot of them. According to statistics, most often such failures occur due to improper shutdown of the computer, forced stop of some processes (for example, updates), damage to system files or even the bootloader itself.
The most common are failures with error descriptions like INACCESSIBLE_BOOT_DEVICE (unavailable boot device), CRITICAL_PROCESS_DIED (interrupted critical process) or something like that.
Very often, notifications that the computer does not start correctly and because of this Windows cannot start in normal mode can be found during power surges, when the terminal spontaneously disconnects from the network when there is no uninterruptible power supply unit or stabilizer, when the power supply overheats , etc. .d. We should also pay attention to the functionality of all the "iron" components. But these are trifles. Situations are much worse when viruses are present in the system that interfere with Windows, or for some reason the components responsible for loading the system fail. Consider several common cases of such problems and the main methods for their elimination, without touching the problems with the hardware.
What to do first?
So, if suddenly a situation occurs when the computer does not start correctly and the system cannot start, it may very well be a fleeting failure. In this case, for starters, you should reboot the system or simply turn off the terminal in the usual software way from the Start menu.
If this is not possible, you will have to apply forced shutdown by long pressing the power button on the system unit or on the laptop panel.
As a rule, after such a procedure at startup, the system initiates a check of the system disk for errors, after which it can boot in normal mode. Visually check can be observed in Windows 7 and below. In later versions, it is done in the background.
Virus scan
No less important in the case of a message that the computer does not start correctly is the diagnosis of the system for the presence of virus threats. If the system does not start at all, this is quite problematic.
Therefore, it is recommended to use special utilities like Kaspersky Rescue Disk, from which the boot is performed even before Windows starts. In the utility itself, to facilitate the task, you can use its own graphical interface, and it works much better than stationary scanners, allowing you to identify many threats even in RAM or boot sectors.
Auto recovery. The computer does not start correctly (Windows 10 and below)
In general, almost all the latest Windows systems are characterized by the presence of a special self-healing module after critical failures. This is the so-called automatic recovery. The computer does not start correctly, the system does not boot, although there are signs of operability. In this situation, system recovery should be started automatically.
A corresponding notification appears on the screen to start the analysis to restore the system. But this only works if Windows has a fixed rollback point. If the user cleaned or deleted previously created recovery points before the failure , nothing will work. There is simply no copy in reserve from which you can roll back to the previous state.
In the seventh version of the operating system and below, the correction of this situation looks much easier. When starting the system at the boot stage, use the F8 key, which is used to select the safe boot mode, but in the menu that appears, select the boot of the last working configuration (again, if possible). By the way, in the tenth version, using the F8 key to call such a menu is also possible to configure.
Download in safe mode with system file integrity checking
A somewhat more complicated situation is with the damage to system components of the system with the inability to restore them automatically (when starting or rebooting after a notification that the computer does not start correctly) appears. What to do in this case?
First you can try to boot in safe mode, and then use the command line that is called from the Run console (Win + R). If for some reason such a boot option is not possible, you should set the safe mode with confirmation on the command line to determine the component on which the download stops. In this situation, the command line will have to be called from the recovery console from the installation disk.
In both cases, sfc / scannow is written on the command line, after which the system will automatically check and recover the failed components. But this does not always help.
Disabling driver signature verification
Now let's look at the situation when the computer does not start correctly (Windows 10 on board). In the tenth version, getting to safe mode is quite problematic. Here you will need an installation or recovery disk, when booting from which you need to select additional settings in the recovery section and go to diagnostics, and then use the boot options menu.
In the menu that appears, there is a line for disabling driver digital signature verification, standing under the seventh number. You need to move to it and press the enter key (you can do this faster by pressing the number 7 on the keyboard).
This problem is often associated with the oem-drc64.sys driver. If disabling signature verification worked, you need to go into the registry editor on the system (regedit in the Run menu) and go down the HKLM branch through the SYSTEM section to the CurrentControlSet directory, which has the Services directory. Here you should find the driver folder and delete it.
System Restore from Image
It is believed that the best option to restore the system after a message appears that the computer does not start correctly (Windows 10 is used or any other version) is to restore from a previously recorded system image.
Not everyone, however, thinks about such things in advance, however, the process of putting Windows in order in this case is the fastest and easiest.
Using the command line with incomplete or aborted updates
There are situations when problems with the computer not starting correctly (8.1, 8, 7 or 10th modifications on board) are associated with an incomplete or interrupted system update. You can also deal with these failures.
We call the command line at boot, as shown earlier, and write the command shown below:
Force Recovery Commands
If this option does not help, the computer does not start correctly and the system does not boot, you can try to make a forced recovery.
To do this, first we write three commands on the command line:
- diskpart
- list volume;
- exit.
Be sure to remember the letter of the system partition, since in most cases it will differ from the generally accepted value "c" (most often the system partition "e" will appear).
Next, enter sfc / scannow / offbootdir = C: \ / offwindir = E: \ Windows first, and then the following:
After entering each command, the enter key is pressed. In theory, this method gives an almost 100 percent guarantee of the recovery of Windows.
Bootloader recovery
Finally, if the computer does not start correctly, Windows of all versions offers another universal solution that allows you to restore the bootloader, which may be damaged.
To do this, in the same command console, you must first use the chkdsk c: / f / r check command, and then directly the recovery directives, as shown below:
After that, you can reboot. The system, if the failure was associated with the bootloader, will work like clockwork.
If nothing helps
Finally, another situation when none of the above helps. Have to reinstall Windows. But, in order not to “tear down” the entire system, when booting from the installation disk in the diagnostics section, you need to select the point to return the computer to the so-called initial state.
This approach provides the option of saving user files, after which it will be possible to “clean” install Windows, which in most cases allows you to get rid of software crashes much better than all the checks taken together. But to do this, as is already clear, it should only be in the most extreme case, when all other means were powerless.
Instead of a total
In the end, it remains to add that the situation when the computer does not start correctly or the system does not start can be connected precisely with the hardware. In particular, problems with the graphics chip or hard drive can have a particularly strong impact on system loading when it starts to “crumble”. If these are really physical problems, there's nothing to be done. But for the accuracy of determining the faults, additional diagnostic tools should be used . Only in the case of the correct identification of the cause of the failure and the malfunctioning component can we determine the correct solution to eliminate such consequences.
As for all other cases, it is believed that at least one of the above proposed methods will work. So it remains to advise you to use the troubleshooting options, moving from simple to more complex methods. But in any case, so that such excesses do not happen in the future, it is better to take care in advance of creating an image of the system or recovery disk, recording anti-virus utilities, etc. To do this is quite simple, even with your own Windows tools. Such tools should be at hand for any user, as they say, for the most unforeseen case, because not one of the currently used Windows systems is safe from failures.