If the computer displays an error on the screen, the most common types. Solving computer problems - frequently asked questions
Unfortunately, sometimes you can encounter quite serious problems with turning on computers and starting operating systems, although up to certain point There were no signs of trouble. It happens that most often the computer turns on, but the operating system does not start. It is these situations that will be discussed further. Let's look at questions related to why the computer won't boot and what to do in such situations. There are several universal solutions here.
The computer turns on, but the operating system does not start: reasons
Among all the possible situations when failures occur at the loading stage, several typical cases can be identified.
There are three options:
- a black screen appears;
- Blue screen BSoD occurs;
- The operating system starts, but cannot fully boot.
In the first case, when the computer does not start (the boot does not turn on), messages may appear on a black screen indicating physical or software problems. In the simplest case, when nothing serious happens, the system may report that, for example, the keyboard is missing (for desktop PCs). The simplest solution is to connect it and reboot.
If the computer turns on, but the boot does not start, and instead warnings about software failures or missing files appear on a black screen, there can be many reasons for this system behavior. Among them, first of all, we can highlight problems with the hard drive, damage to the operating system (accidental or intentional deletion of system components or registry entries), exposure to viruses, incorrect entries boot sector, RAM conflicts, etc. By the way, if a blue screen pops up, this is more related to the “RAM” or recently installed drivers devices that cause conflicts not at the software level, but at the physical level.
What to do if the computer does not boot and the operating system does not start for the above reasons? Depending on the situation, there are several solutions. To an uninitiated user, they may seem quite complicated, but in certain situations only they can be used to resuscitate the system. Therefore, you will have to spend both time and effort.
The computer turns on but does not boot: what to do first?
So, let's start with the simplest thing. Let's assume that a short-term technical failure has occurred in the system, for example due to incorrect shutdown or power surges.
As a rule, almost all Windows modifications used today usually automatically activate startup upon restart. If this does not happen, before starting the system you will have to use the F8 key to call up the additional boot menu (Windows 10 uses a different method).
The computer turns on, but the operating system does not start? There's no need to get upset. Here, in the simplest version, you can select the line to load the last working configuration. If everything is in order with the system components, the system will boot without problems. If this does not help, you will have to use the troubleshooting section, and sometimes even trying to boot into safe mode.
Possible viral infection
Unfortunately, viruses can also cause such situations. What to do if the computer does not turn on? Ways to solve this particular problem boil down to using a powerful one that could check for threats even before the OS itself starts.
Among the variety of anti-virus software, it is worth noting specially disk utilities that start directly from an optical media or USB device, have their own boot records and even a graphical interface like Windows. One of the most powerful tools is Kaspersky Rescue Disk. Its use can guarantee almost one hundred percent detection of viruses, even those hiding in RAM.
RAM conflicts
Now let's see what to do if the computer does not boot and instead a blue screen appears. As already mentioned, most often this indicates problems with drivers and RAM. We’re not touching the drivers yet, but let’s look at the RAM.
The proposed solution to the issue of if the computer does not boot is mainly designed for stationary PCs. In this situation, you should remove all memory sticks, and then insert them one by one and check the load. Perhaps one of them is the link that causes failures. This may occur when trims from different manufacturers are added.
If the system can somehow be loaded using the same safe mode, the RAM should immediately be checked using the Memtest86+ utility, which will help identify the true cause of the problem.
The system does not see the hard drive
Now the worst situation is when the computer does not boot. The causes and solutions may be related to the hard drive.
A hard drive can have both software and physical problems, although sometimes that’s not even the issue. The problem may be completely trivial: the user in the BIOS settings has set the priority for booting from a removable device, for example, from an optical disk, which is currently in the drive, but is not a system one. You just need to remove it and download again.
On the other hand, another problem that the computer does not start (the system does not start) may be due to the fact that the bootloader and the records of the corresponding sector are damaged. The solution to this situation will be discussed a little later. But in the simplest case, you can try to restore disk data using Recovery utilities.
Sometimes changing the settings of the primary BIOS input/output system also helps. Here you need to find the section related to setting up the hard drive, and in the SATA configuration parameters, deactivate the use of AHCI mode.
Finally, the hard drive may also have purely physical damage, and this cannot be done without outside intervention.
Using the installation disc
Many users clearly underestimate the help that the installation or system image can provide in solving problems associated with situations when the computer turns on, but the operating system does not load.
Firstly, almost any kit includes a so-called recovery console, with which you can eliminate many software failures, and secondly, you can use the command line here. This, by the way, is the most effective method. Next it will be clear how this works.
Problems with the BOOTMGR bootloader
It is believed that the most common problem when the computer turns on, but the operating system does not start, is damage Windows boot loader(Boot Manager). In this case, the system just writes that there is no system partition (it simply does not see the hard drive).
You can fix this problem by starting from the boot disk and going to command line in the recovery console, which can be opened by pressing the “R” key. Next, you need to first use the check disk command and then fix (restore) boot records.
The whole sequence looks like this:
- chkdsk c: /f /r;
- Bootrec.exe /FixMbr;
- Bootrec.exe /FixBoot.
After entering commands, punctuation marks are not placed, but the enter key is pressed. If for some reason executing these commands does not have a positive effect, you can alternatively use a complete rewrite of the boot sector, which is performed by the Bootrec.exe / RebuildBcd command. If the hard drive is not physically damaged, this should work, as they say, one hundred percent.
Some can also be used third party utilities. The most suitable program seems to be a tool called MbrFix, which is included in the Hiren’s Boot CD. After calling it, for example, for Windows 7, provided that this particular system is installed, and only on one disk (there is no partitioning), the following should be written:
- MbrFix.exe /drive 0 fixmbr /win7.
This will save the user from having to make changes to boot records, and the boot will be restored.
Problems accessing the NTLDR file
When a message appears that a given component is missing from the system, a boot commit is first applied, as in the previous case.
However, if the result is not achieved, you will need to copy the original file to the root of the system partition. For example, if the drive is "C" and the drive is "E", the command would look like this:
- E:\i386> copy ntldr C:\ (after copying, the system will boot without problems).
Damaged or missing HAL.dll file
If the computer turns on, but the operating system does not load in normal mode, the reason may be a damaged component HAL.dll (a corresponding notification may be displayed on the screen).
In this situation, you need to boot the system in safe mode, call the command console and write the following line in it:
- C:\windows\system32\restore\rstrui.exe (then press the Enter key and restart).
Instead of a total
Here is a brief summary of everything that concerns solving the problem of the inability to start the operating system. Naturally, the issues that could be caused by low power, failure of the CMOS battery, loose cable connections, or the presence of dust inside were not touched upon here. system unit or other malfunctions. But in software terms, the above methods work flawlessly.
And the most common messages from the POST self-test system. Now I want to continue a previously open topic.
So, after turning on the computer, the POST computer device self-test program starts. After its successful completion, the BIOS searches for the device from which the computer will boot. This device can be any storage medium - hard drive, flash drive, CD/DVD drive, etc.
How is this search carried out?
The fact is that the BIOS already has a list of devices from which it is possible to boot the computer and the search for a boot device is carried out in accordance with the order of devices in this list. The section of the BIOS that contains the list of boot devices is usually called Boot(loading) and the order of devices in this list can be changed if desired.
While loading computer BIOS scans all devices from the list in order until a device with boot files is found. At this point, the search for boot devices stops and computer boot control is transferred to the program, boot files which were found (in most cases this program is the operating system Windows).
Order of devices in the list BIOS boot can be changed. This is usually done like this: immediately after turning on the computer (at the stage of passing the POST check), you need to press the key Delete.
In this note I am publishing photographs of the screen of my ASUS EEE PC 1000H netbook; the BIOS view in your case may be slightly different.
Sometimes the access key in the BIOS may be different and this needs to be clarified in the manual motherboard, but in most cases it will be Delete or, as in my case, F2.
Once in the BIOS, you need to find the section responsible for the boot order from devices. This section is usually called Boot.
To navigate through the BIOS menu, you usually use the cursor keys - up, down, right and left arrows. To enter the menu section, use the key Enter, and for exit – Esc.
On the menu Boot you will see this list:
So, after passing the POST check, the BIOS queries all the devices in the list in order until it finds an available boot device. The presence of a device in the download list does not mean its physical presence on the computer. So, in the boot list, a CD/DVD drive may be in first place, but at the time of boot, the drive will not have a disk installed and therefore the BIOS will move to the next device on the list.
Once a boot device is found, the computer boot process continues from there. A special active partition of the device is detected, in which boot information (files) is located and the operating system kernel is loaded, to which all control of the computer boot process is then transferred.
If such a device is not found, or there are no boot files on it, or the boot files are damaged, an error message is displayed and the boot process stops.
There may be several errors:
- Non system disk
- Invalid system disk
- System disk error
- NTLDR is missing
What should you do if you see one of these messages?
First of all, find out in the BIOS the boot order from computer devices. It is quite possible that your first drive is a CD/DVD drive and some disc was installed in it during booting.
If the message continues to appear, corruption has most likely occurred. system files. There can be a lot of reasons for this - from computer infection with viruses to unreasonable actions of the user himself. In this case, you can try to restore Windows, but this is a very delicate matter and it is very difficult to recommend a clear algorithm of actions that would suit everyone in all cases.
If the cause of the failure is viruses or malware, you can try to restore the system using the Dr.Web LiveDisk program. This free program, with which you can boot your computer not from hard drive, ah, from a flash drive. You can then scan your computer for viruses and fix problems.
There are hundreds of other programs that help you restore your computer after a failure, but they are all built on the same principle as those mentioned above.
And one more piece of advice - if you didn’t have anything important on your computer, or more precisely on drive C (system drive), then simple solution problem will be reinstallation Windows .
If important information Yes, then this is where things get complicated. I would recommend not trying to restore the operating system, but removing the hard drive from the computer, connecting it with a second drive to the working computer and moving it necessary information from drive C to another, for example, D. Then return the hard drive back and reinstall the operating system with formatting drive C.
Why I don't like to restore Windows? Yes, because, as my experience shows, this is a thankless and temporary task. As a rule, such errors occur in very “cluttered” operating systems and restoring several damaged files does not solve the problem globally - soon either the problem repeats itself or new errors appear. Therefore, I prefer, firstly, to keep my operating system clean, and secondly, I never bother with restoring damaged files, but reinstall the system from scratch.
Of course, reinstalling the operating system for a novice user is a murky task and is unlikely to be done without outside help, but it’s still worth learning. On my website I have all the necessary information for this - a video course “How to install Windows”.
Don't miss the opportunity to do a good deed:
Hello! Help me please. When you turn on the computer, it gives the following error: “Windows could not start, perhaps this was due to a recent change in the hardware or software configuration” and the reboot begins. And so on in a circle. I never found any restore points. What to do?
Expert answer:
Hello, Nikita! This error, in its essence and difficulty of elimination, is in many ways similar to the Blue Screen of Death (BSOD).
Option 1
The error text also contains standard recommendations for elimination, which unfortunately do not always help, but it’s worth a try. To do this, insert into the computer installation disk or a bootable USB flash drive with the Windows operating system. Next, you should simply follow the installer’s recommendations to install and fix damaged files and boot sectors.Option 2
If unsuccessful, try pressing the “F8” button when booting the operating system to gain access to the “Advanced Boot Options” section. In this section, you should pay attention to two items “System Restore” and “Safe Mode.” “System Restore” is carried out by analogy with the steps described in “Option 1”. “Safe Mode” - the operating system will boot with minimal “baggage”, which allows you to bypass errors and load the OS (not always). If you managed to boot into Safe Mode, open “Start” - “Standard” - “Service” - “System Restore” and “roll back” the state of the operating system to the last successful configurations.Option 3
The error text contains the line “Status”, opposite which the error code is indicated, the most common is “0xc000000f”. The elimination methods are the same as described above; in addition, try the following:- When you turn on the computer, depending on the model, hold down the “BIOS” key - this can be “F2”, “F10”, “DEL”.
- Find the “Hard Disk Drivers” section, with two lines active, highlight the first one and press “Enter”.
- The second line is called “SATA: 4S-WDC WD20EARX-00PASB0” and it is this line that should be moved to the first place using the “+/-” or “up/down arrow” function keys.
Windows 10 users often encounter a blue or black screen when starting the system with an error message. Errors during loading are very unpleasant for the user, especially since they won’t even be able to use the computer. Moreover, information about possible reason there is no failure.
Please note that loading errors occur due to both software and hardware. In our article we will look at the main mistakes when booting Windows 10 problems that arise due to software, and ways to solve them.
To identify and resolve boot errors, you need to analyze the state of your computer before the crash. The system stopped starting:
- after updating BIOS or drivers;
- in connection with updating or installing an antivirus program;
- after adding computer devices;
- due to incorrect shutdown.
By paying attention to the above factors, you can most accurately identify and resolve the error when loading Windows 10.
Windows 10 gives an error when loading
The most popular type of failure is when, when you turn on the PC, Windows 10 does not start, and a window with an error message pops up on the monitor. Then a blue screen appears with the message and two options for solving the problem.
This error indicates (but not always) that system files have been damaged due to their deletion, installations and “demolition” of applications (especially antivirus ones), the use of software products to clean the registry and PC.
The solution to this problem is to restore the registry and damaged system Windows files 10. You can do it like this:
After this, you need to reinstall Windows 10 while saving system files. However, programs will not be saved after this action.
Error code 0x000000f when loading Windows 10
Windows 10 may not boot for various reasons. One of the system problems of your PC may be error code 0x000000f, which occurs after cleaning it from dust.
After cleaning the computer from dust accumulations, the user is faced with the fact that the PC gives him a black screen when he turns it on with a description of this error on English language in the “Status” item.
After this, you can restart the system at least 100 times or perform other actions with memory or motherboard, but the error will repeat itself all the time. The reason for this lies in the syndrome of spontaneous wallpapers in the BIOS settings, that is, the correct settings of the devices used to boot Windows 10 have been lost.
The algorithm for eliminating this error is as follows:
After this, the PC will restart without error 0x000000f occurring.
Error loading BOOT Windows 10
Often users when starting Windows systems 10 may see a blue screen with a notification on the computer monitor "inaccessible boot device".
This message indicates that the system has a problem accessing the file partition responsible for the boot mode. Blue screen in this situation, it serves as a protective “shield” for saving your data.
To fix this error, you need to know why it occurred. The reasons can be very different - after resetting the system, changing the partition structure on the disk, connecting another hard drive, or after updating the BIOS.
Before you start fixing the error loading BOOT Windows 10, it is recommended to try to restart the computer in this way:
- disconnecting additional storage devices from the PC (including flash drives and memory cards);
- examination system disk to boot priority into BIOS or UEF;
- you also need to make sure the connection is correct hard drives and SSD to power and SATA interfaces if you cleaned your PC from dust or connected something to it;
If the error appears after installing updates or resetting Windows 10, you can fix it this way:
- On the screen "The computer is not started correctly"(it appears when you search for error information) you need to select "Extra options".
- Next, click "Troubleshooting", go to "Boot Options" and press "Reboot". After restarting the PC, select item 4 by pressing the F4 key, then - Safe Windows mode 10 .
- After booting into safe mode, the computer needs to restart again ( Start - Shutdown - Reboot).
If a disk error occurs when loading Windows 10 (it was damaged or the partition structure on it changed), then you need to boot in the recovery environment. If you are not able to do this action from the computer itself, then you can use the installation drive to launch the recovery environment (bootable USB flash drive or recovery disk).
Bug fix:
An error occurs when loading Windows 10 and the PC restarts
The reason why an error occurs when loading Windows 10 and the computer restarts itself is because the automatic boot fix has failed. This problem can only be solved from a recovery environment from a boot disk or flash drive using the method described above. When you boot into the environment Windows recovery, carry out the same procedure for eliminating the error as for "The computer is not started correctly".
Let's consider the designation of codes Windows errors 10:
- Error 0xc0000225 during boot - a problem associated with damage to the boot sector (viruses, erroneous shutdown of the OS, mechanical shock).
- Error 0x00000e9 (input/output) when loading Windows 10. It indicates that a failure occurred when the removable storage device was disconnected or during operation, as well as a hardware problem (hard drive, floppy drive).
- Error code 0xc000021a Windows 10 at boot is called STATUS_SYSTEM_PROCESS_TERMINATED and occurs when it stops and terminates unexpectedly Windows process Logon Process. Also this error may occur from damage to the RAM or HDD, the impact of viruses and malware on files, or an unexpected failure when installing programs or drivers on the device.
The user often encounters various errors when loading Windows 10, which can be resolved on their own. The main thing is to figure it out in time and identify the reasons for the system failure during boot.
I'll start from the beginning. I have a computer with 2 hard disks. 1st regular 50 gig, 2nd Toshiba solid state 128 gig. Once upon a time, my sat wire that was connected to the DVD-RW drive broke down. I threw out this wire, disconnected the solid-state device and connected the sat cord from it to the drive. The solid body lay idle for about 2 years. The computer worked fine for about 2 years on Windows 7. A couple of months ago I decided to clean the computer from dust. I cleaned it and wiped it with a damp cloth so as not to touch the circuit boards and the ends of the cords. In short, moisture only got into places where there was no electricity. To make the case dry faster, I took it out onto the balcony for about 10 minutes. But I forgot it there for a couple of hours. It was freezing outside. In short, having come to my senses, I brought the frozen computer into the room. After waiting about a couple of hours until it warmed up to room temperature again, I turned it on. Windows did not boot. Bios did not see the hard one. Having connected different satas into different connectors, conjured again with wiping, removing and installing in place different devices computer, nothing helped (the BIOS still didn’t see the screw) I decided that the screw was dead. I took out the solid state drive that was lying idle and installed Win 10 on it. I disconnected the old screw. Everything worked for about three weeks. The computer really came to life, so to speak, and began to fly. Until one day the computer froze. It gave me error 0x00000e9. The BIOS again did not see the screw (solid state). Again I tried to clean the computer, pulled out all the RAM, etc., reassembled everything - the BIOS saw the screw - everything worked. But the next day everything happened again - only Windows (10) booted again from the fifth time. The computer worked in this mode for a week - every day the error 0x00000e9 appeared. I rolled back Windows several times; during this period there were some Windows updates on the computer. After some update, many services were disabled, including the Windows installer. Over the weekend I decided to clean my computer again - I licked it completely - not a speck of dust. Assembled - the solid state machine doesn’t see anything. I took out the old screw - which I thought was dead - connected it instead of the solid state - and lo and behold! Windows 7 (which was on the old hard drive) began to load. I checked - everything works. I connected the solid state drive - without disconnecting the old screw - everything works fine again. Windows Explorer sees all partitions on both hard drives. I decided to set the priority in the BIOS to the solid state drive with loading Windows 10. Everything worked. Again, just in case, I reinstalled Windows 10 on the solid-state drive, cleaned the old screw, leaving Windows 7 there. I thought, well, now everything will be ok. But after a couple of days it freezes again and this same error. I started sinning on both screws. I called a paid hardware specialist. Some Shraybikus arrived - who was smart there - checked both hard ones with the help of his programs, did not find a single error and did not even find a single bad block. He said the screws are completely in perfect condition. Having turned off the old hard drive, turned off the video card, the drive and pulled out one of the RAM strips - this shraybikus turned on the computer and everything worked. Then I connected the video card - and turned on the computer again - this error came out again - the BIOS again did not detect the screw. Then this young mega-brain began testing my computer with all sorts of programs from his separate portable, clever screw. After fiddling around, he said that the problem was that I had a crappy power supply. They say that when a minimum of any devices are connected to the computer, everything is normal. If you plug everything in - two screws, a video drive, three RAM dies and a separate sound one, then there is not enough power. At the same time, my 450W power supply always worked properly - the computer was weak five years ago. The Nvidia 9800GT is weak. Plus three sticks of RAM. In short, the power reserve when fully connected is about 150 W. Finally, after installing Windows 10 for me and setting something up in the BIOS, charging me 1100 rubles, they dumped this shribikus, recommending that I change the power supply. Next, I went and bought a new 700W power supply from Chivtek for 4,000 rubles. I connected everything and the problem happened again a couple of days later. Only error 0x00000e9, now it doesn’t always appear. The following happens most often:
Suddenly the computer freezes. It sags after 2-3 minutes. It says something like there is a problem, the computer needs to be rebooted, the percentages are starting to show up, like the system is collecting data and the computer is rebooting itself. After rebooting it says again that there is no hard drive. I press reset, I press delete, I go into the BIOS. The BIOS does not see either both screws or the one that has priority (solid state). When I exit the BIOS, the computer itself tries to boot again - again I press the button to enter the BIOS again and again the computer does not see either one or both screws. And so 3-7 attempts to reboot and at some point the BIOS again sees both screws. Windows loads normally again. After a while, this problem repeats itself again. If the BIOS does not detect both screws after 7 attempts to reboot, I turn off the computer, go into the hardware, remove my 3 RAM sticks (2, 2 and 4GB) and put them in different slots. I turn on the computer and the BIOS again sees both of my screws. And this is how I live. The problem occurs about once a day. I changed the sata slots (there are 6 of them on the motherboard). I also changed the sat cords, although I tried old cords - which are not necessarily working (at least these cords work on another weak computer).
The key question for me is whether the problem could be in the motherboard. Because I wouldn’t want to buy a new one for 5++ pieces. And it’s not a fact that this will help. I would like to know who had a similar problem and the cause would be the motherboard.
If the hard ones are checked. The power supply is new. There are still 3 options left for me:
1) buy a new motherboard and check if it helps or not.
2) buy the new best satov cables and check whether it helps or not.
3) throw away your three sticks of RAM and buy a new one with 8GB and check if it helps or not.
4) Call the cunning shribikus for money again so that he can see what’s going on there optimal settings in the BIOS.
With all options you have to pay grandma. I wouldn’t want to pay for all options at the same time, but only one. There is no trust in Shraybikus because he made a mistake last time, and he behaves like a hacker who hacked the American NSA. He looks a lot like a hack who, having muddled the brains of me, a teapot, is thinking about how to get another thousand out of me.
In general, I will be glad to any advice. Thank you in advance. I am ready to provide any information (on computer equipment, settings in the BIOS, etc.). Just please write in advance where I can find this information (where to click).
Loading...