Windows xp won't load. The computer turns on, but the operating system does not start: possible causes and solutions to the problem

It would seem that we have studied the computer boot process down to the smallest detail: button - BIOS - operating system- login... Have you ever thought about what is actually happening at this time inside your computer? Can you tell me step by step how a computer works? I'm sure not. Therefore, today we will conduct a short educational program - we will talk about how a computer actually boots.

This article examines the operation of Windows XP; in other systems, the process, naturally, is somewhat different.

The power switch turns on.
The power supply is performing a self-diagnosis. When everything electrical parameters Normally, the power supply sends a Power Good signal to the processor. The time between turning on the power and leaving the signal is usually 0.1-0.5 seconds.

The microprocessor timer receives the Power Good signal.
Upon receipt of this signal, the timer stops sending a Reset signal to the processor, allowing it to turn on.

The CPU starts executing ROM BIOS code.
The processor loads the BIOS ROM starting at address FFFF:0000. At this address only the transition to the address of the real BIOS ROM code is registered.

The system performs an initial hardware test.
Each error encountered at this stage is reported by certain sound codes (in the past, a beep, now probably more modernly - with a voice), since the video system has not yet been initialized.

The BIOS looks for adapters that may require loading their own BIOS.
The most typical case in this case is a video card. The boot procedure scans the memory from address C000:0000 to C780:0000 for a video ROM. This way the systems of all adapters are loaded.

ROM BIOS checks whether it is shutdown or reboot.
Procedure two bytes at address 0000:0472. Any value other than 1234h is evidence of a “cold” start.

If enabled, the ROM BIOS will trigger a full POST (Power On Self Test). If this is a reboot, then the memory check is excluded from the POST procedure.
The POST procedure can be divided into three components:

• The video test initializes the video adapter, tests the card and video memory, and shows the configuration or any errors that have occurred.
• BIOS identification shows the firmware version, manufacturer and date.
• The memory test checks the memory chips and calculates the size of installed memory.

Errors that may occur during a POST check can be divided into fatal and not so fatal :). In the second case, they are shown on the screen, but allow you to continue the download process. It is clear that in the first case the download process stops, which is usually accompanied by a series of beep codes.

The BIOS reads configuration information from CMOS.
A small memory area (64 bytes) is powered by a battery motherboard. The most important thing for loading in it is the order in which the drives should be polled, which one should come first - the disk drive, CD-ROM or hard drive.

If the first one is hard drive, The BIOS checks the very first sector of the disk for the presence of a Master Boot Record (MBR). For the drive, the Boot Record in the first sector is checked.
Master Boot Record - first sector on cylinder 0, head 0, 512 bytes in size. If it is found, it is loaded into memory at address 0000:7C00, then checked for the correct signature - the last two bytes must be 55AAh. The absence of the MBR or these check bytes stops the boot process and issues a warning. The MBR itself consists of two parts - the system loader (partition loader or Boot loader), a program that takes control when loading from this hard drive; partition table, which contains information about the logical drives on the hard drive.

The correct MBR entry is written to memory and control is transferred to its code.
The process of installing multiple operating systems on one computer usually replaces the original loader with its own program, which allows you to choose from which disk to perform the rest of the boot.

Next, Boot Loader checks the partition table to find the active one. The bootloader then looks for a boot record on the very first sector of the partition.
In this case, Boot Record is another 512 bytes - a table describing the partition (number of bytes in a sector, number of sectors in a cluster, etc.) and a transition to the first file of the operating system (IO.SYS in DOS).

operating system

Control is transferred to the operating system. How does it work, how does the loading process go?

Boot Record is checked for correctness and if the code is found to be correct, then the boot sector code is executed as a program.
Booting Windows XP is controlled by the NTLDR file located in the root directory of the system partition. NTLDR works in four steps:

1. Initial loading phase
2. System selection
3. Determination of iron
4. Configuration selection

In the initial phase, NTLDR switches the processor to protected mode. It then loads the appropriate file system driver to work with files from any file system supported by XP.
In case anyone has forgotten, our favorite OS can work with FAT-16, FAT-32 and NTFS.

If there is a BOOT.INI in the root directory, then its contents are loaded into memory. If it has entries for more than one operating system, NTLDR stops running - shows a menu of choices and waits for user input for a certain period of time.
If there is no such file, then NTLDR continues loading from the first partition of the first disk, usually C:\.

If during the selection process the user selected Windows NT, 2000 or XP, then pressing F8 is checked and the corresponding menu with boot options is displayed.
After each successful boot, XP creates a copy of the current combination of drivers and system settings known as the Last Known Good Configuration. This collection can be used to boot if some new device has disrupted the operation of the operating system.

If the selected operating system is XP, then NTLDR finds and loads the DOS program NTDETECT.COM to determine the hardware installed in the computer.
NTDETECT.COM builds a list of components, which is then used in the HARDWARE key of the HKEY_LOCAL_MACHINE registry branch.

If the computer has more than one hardware profile, the program stops with a configuration selection menu.

Once the configuration is selected, NTLDR begins loading the XP kernel (NTOSKRNK.EXE).
During the kernel boot process (but before initialization), NTLDR remains central to computer control. The screen clears and an animation of white rectangles is shown at the bottom. In addition to the kernel, the Hardware Abstraction Layer (HAL.DLL) is also loaded so that the kernel can abstract itself from the hardware. Both files are located in the System32 directory.

NTLDR loads device drivers marked as bootable. Having loaded them, NTLDR transfers control of the computer further.
Each driver has a key in HKEY_LOCAL_MACHINE\SYSTEM\Services. If the Start value is equal to SERVICE_BOOT_START, then the device is considered bootable. For each such device, a dot is printed on the screen.

NTOSKRNL goes through two phases during the boot process - the so-called phase 0 and phase 1. The first phase initializes only that part of the microkernel and executive subsystems that is required for the operation of basic services and continued boot. At this stage, a graphic screen with a status bar is shown on the screen.
XP disables interrupts during phase 0 and enables them only before phase 1. Calls HAL to prepare the interrupt controller. Memory Manager, Object Manager, Security Reference Monitor and Process Manager are initialized. Phase 1 begins when HAL prepares the system to handle device interrupts. If there is more than one processor installed on the computer, they are initialized. All executive subsystems are reinitialized in the following order:

1. Object Manager
2. Executive
3. Microkernel
4. Security Reference Monitor
5. Memory Manager
6. Cache Manager
7. I/O Manager
8. Process Manager

Initializing the I/O Manager begins the process of loading all system drivers. From the moment where NTLDR stopped, drivers are loaded by priority.
A failure to load the driver may cause XP to reboot and attempt to restore the Last Known Good Configuration.

The last task of phase 1 of kernel initialization is to launch the Session Manager Subsystem (SMSS). The subsystem is responsible for creating the user environment that provides the NT interface.
SMSS runs in user mode, but unlike other applications, SMSS is considered a trusted part of the operating system and a "native" application (uses only executive functions), which allows it to run the graphics subsystem and login.

SMSS loads win32k.sys - the graphics subsystem.
The driver switches the computer to graphical mode, SMSS starts all services that should start automatically at startup. If all devices and services started successfully, the boot process is considered successful and a Last Known Good Configuration is created.

The download process is not considered complete until the user has logged into the system. The process is initialized by WINLOGON.EXE, which runs as a service and is supported by the Local Security Authority (LSASS.EXE), which displays the login dialog.
This dialog box appears around the time Services Subsystem starts the network service.

If your PC does not start, then the reasons may be both hardware and software. If the computer itself turns on, but the operating system does not load, and we see some kind of menu on the monitor, then do not be alarmed. This means that your operating system has failed. This can be fixed by simply reinstalling Windows.

If you don’t want to reinstall for some reason, you can try running System Restore. This is quite simple to do: when you turn on the PC, press F8 and select “Load last known known configuration” or safe mode, and then perform a system restore.

What to do if nothing helps?

You need to do some work on your system. We suggest doing this using two useful programs.

1. Update drivers with Driver Booster. This is really cool software that often helps. Updating old drivers to new ones is one of the key requirements for the normal functioning of games and programs on a computer.

You might think that Windows always alerts users when new updates are available. That's right, it shows alerts, but only for updates for Windows and the video card. But besides this, there are many more drivers that need to be updated regularly.

We will fix errors in Windows 10. But approximately the same will need to be done in Windows XP, 7 and 8. In Windows 7 and later releases, the developers have improved the recovery system for startup problems. In older versions of the system, serious errors often have to be resolved by reinstallation.

Disable peripherals

positive.org

Try to remember what changes you recently made to the system: did you install new devices or switch something. There may be a problem with one of the hardware components. Try disabling:

1. USB drives.
2. Card readers.
3. Printers.
4. Scanners.
5. Cameras.
6. All other external devices.

If this does not help, disconnect the keyboard and mouse: you need to exclude all possible sources of malfunction.

It may also be due to internal components, such as RAM. On a desktop PC, you can check the performance of the RAM by connecting the strips one by one.

Check power

takprosto.cc

If the computer does not turn on at all, pay attention to the power cable and sockets. Don't forget the power switch on the back of your desktop computer.

If everything works at this level, but the computer still does not turn on, then most likely the problem is in the power supply, which you are unlikely to be able to fix yourself: you will have to replace it or have it repaired by a specialist.

It is possible that the computer turns on, but only for a short time. This is the same problem with the power supply.

Configure the disk to boot the system

Errors may appear during startup: An operating system wasn’t found. Try disconnecting any drives that don’t contain an operating system. Press Ctrl+Alt+Del to restart or Boot failure. Reboot and Select Proper Boot device or Insert Boot Media in selected Boot device.

IN BIOS settings or UEFI may be set to boot from an external device or other logical partition rather than from the system drive. You can restore default settings like this:

1. Restart your computer.
2. Immediately after restarting, press the system key, for example F2. This may be another key: usually during system boot it can be found at the bottom of the screen with the logo of the laptop or motherboard manufacturer.
3. In the settings, set the desired disk to the first place in the boot.
4. Select the Save and Exit option to save your changes.

If the above does not help, you will have to restore the system bootloader. To do this, you will need a bootable USB flash drive or recovery disk with a system of suitable capacity. How to do bootable USB flash drive or disk, read Lifehacker about installing Windows.

Start the system from a flash drive or disk by selecting the desired option in the boot menu. In the menu that opens Windows installations select "System Restore".

From the recovery menu, select “Troubleshooting” → “ Additional options» → “Startup Recovery”. After this, the system will try to automatically fix the bootloader. In most cases this solves the problem.

The same can be done manually via the command line, but it is better to select the automatic option so as not to aggravate the situation.

If this method does not help, the problem probably lies in the hardware: the hard drive is damaged.

From the recovery menu, select Troubleshooting → Advanced Options → Command Prompt.

IN command line you need to enter the commands one by one: diskpart → list volume (be sure to remember the name of the Windows disk) → exit .

To check the disk for errors and damage, enter the command chkdsk X: /r (where X is the name of the Windows disk). The check usually takes quite a long time, you will have to wait.

Start Windows in Safe Mode

Due to a sudden shutdown of the computer during installation of operating system updates, cleaning of viruses and unnecessary entries in the registry, or due to the fault of acceleration utilities Windows operation System files may become damaged. In this case, a “blue screen of death” will appear when the system boots.

Try starting Windows in safe mode without loading drivers and programs at startup. If the computer is running in this mode, you will have to remove the drivers, perform a system rollback, and scan for viruses.

If you have restore points, this problem is quite easy to solve. You just need to roll back to the previous stable configuration.

Reinstall system files

The steps above may not help. Then you'll have to reset Windows settings and reinstall the system while saving the files. Unfortunately, all programs will need to be reinstalled.

In the recovery environment, select Troubleshoot → Reset this PC → Keep my files → Reset.

The system will roll back to the original settings.

In this article we will look at all the popular reasons why Windows 7 or xp does not load on a laptop or computer and a black screen with inscriptions appears. Those. Possible software problems and ways to resolve them will be discussed. This will be a continuation of the first part of our review, in which we looked at possible options, why the computer won’t boot, and hardware problems (with hardware). So, if you haven’t found the answer to your question here, be sure to read the first part - maybe it’s there.

If your PC shows absolutely no signs of life and does not react in any way to pressing the power button, then we recommend that you read the article why your computer won’t start. It discusses the main causes and ways to eliminate this breakdown. But don’t forget that if you don’t want to deal with the problem yourself, you can always contact our service and order computer repair at home.

We tried to make this review as complete as possible and collected all the most popular reasons why Windows 7 or xp does not start on a computer or laptop. Each case has been encountered many times in our practice. But it is also possible that you will not find a solution to your problem. In this case, write in the comments and we will try to help you.

On a black screen there is an inscription: NTLDR is missing and Windows does not boot

This is one of the most common reasons why Windows xp or 7 does not start. The message "NTLDR is missing" is translated as "NTLDR is missing." NTLDR is a boot file for the operating system, which requires three files (NTLDR, boot.ini and ntdetect.com) to be present on the active partition of the hard drive from which it is configured to boot. If at least one of the files is missing or there is no access to it, then Windows 7 or xp will not boot and will give an error.

Possible reasons and what to do:

• The NTLDR, ntdetect.com, and boot.ini files have been moved or completely removed from the disk containing the operating system. In this case, you need to copy the missing computer files from the working OS.
• Severe virus infection - a deep scan of your PC for viruses is necessary. You may also need to restore damaged system files.
• Too many files have accumulated in the root directory of the system disk.

Unfortunately, due to the nature of the file NTFS systems, which is used on most modern computers, simply deleting unnecessary files from the root directory of the system partition is unlikely to help eliminate the problem - Windows will not start anyway. Additionally, you may need to copy boot files from your work PC.

• If several operating systems are installed on the hard drive at once, then a conflict may have occurred between them.

You can fix this problem by booting the computer using the operating system recovery disk and manually editing the boot.ini file, which is responsible for the OS boot order.

Windows XP won't boot due to registry problems

As a rule, this problem is specific to this version of the operating system. In the newer ones (seven, eight, ten) we did not encounter such a problem.

Before booting begins, one of the following messages appears on a black screen:

• Windows cannot start because the \WINDOWS\SYSTEM32\CONFIG\SYSTEM file is corrupted or missing;
• Windows cannot start because the \WINDOWS\SYSTEM32\CONFIG\SOFTWARE file is corrupted or missing.

These messages mean that your operating system registry is faulty. There may be several reasons why this could happen and now Windows XP does not start:

• Your PC has become infected with a virus.
• You incorrectly shut down your computer by forcibly turning it off using a button or unplugging the cord from the outlet.
• Your hard drive is failing (or has already failed).

There are several ways in which you can restore functionality to your operating system. If everything goes well, this can be done even without reinstalling the entire system. But all these methods require deep knowledge of PC software.

A beginner, having made even a small mistake or inaccuracy, risks losing the opportunity for subsequent successful recovery. In addition, you may need to restore personal information located on your hard drive. Therefore, we recommend contacting specialists for this problem.

The following message appears on the black screen: BOOTMGR is missing

"BOOTMGR is missing" is translated as "BOOTMGR is missing." If Windows 7 or XP does not boot and this message appears, it means that the boot sector is missing or damaged.

This could happen due to incorrect installation programs, due to a failure in the operating system, careless user actions, or problems with the hard drive. Before attempting to resolve the error, you must diagnose your hard drive for bad sectors.

In order to eliminate this problem need boot disk from which Windows was installed. You need to boot your computer from the disk and select “Startup Repair” in “System Recovery Options.”

In this case, the boot sector will be restored to automatic mode. If after this Windows 7 still won’t start, and you don’t know what to do, then it’s better to contact the service. Because restoring the boot sector manually is a very difficult operation. Careless actions can lead to the loss of all information stored on the computer.

Why Windows won't boot and freezes during boot

Many have encountered a problem when, when starting the operating system, a logo with a creeping line appears and the computer freezes. There is no point in waiting an hour, two or a day - Windows will not start.

Here are the main reasons why this can happen:

• The operating system has been heavily infected with viruses - in this case, a full scan of the system disk for viruses can help. You can do this by booting your computer from a rescue disk or by connecting the hard drive to another computer.
• The operating system has crashed

You can try booting into safe mode and performing a system restore, or try performing a “Last Known Known Configuration” boot. Very often this helps solve the problem. To do this, immediately after turning on the PC, start pressing the “F8” key. A menu should appear where you can select this download option.

• Computer hard drive failure.

Due to improper use or simply over time, bad sectors may appear on the hard drive. The information that was written to them becomes inaccessible and, as a result, Windows 7 or XP may stop loading and freeze during the boot process. You can restore and replace bad sectors, but it would be best to replace the hard drive itself. You can read it.

Also, if such a malfunction occurs, you can try “Load last known known configuration”. If this still does not bring results, then in the same menu try the “Safe Mode” item (on English it could be " Safe mode"). When it turns on, try to rollback to the previous state. To do this, in “Start”, find and run “System Restore”.

Blue screen of death appears

Another popular problem is when Windows 7 does not load beyond the logo, but a “blue screen of death” appears. In this case, you will also need to bring up the boot menu using the "F8" key.

There should be an item in the menu called “Troubleshoot your computer.” Click it and the “Recovery Options” window should appear on your screen.

Let us briefly examine the points that are contained in it.

• Startup Repair - automatically analyzes problems that prevent Windows 7 from starting and attempts to fix them. It doesn't always help, but it's definitely worth a try.
• System Restore - from here you can also “roll back” the system, just like from safe mode.
• Restoring a system image - if you have a saved system image on your hard drive, you can restore using it.
• Diagnostics Windows memory- checking system memory for errors.
• The command line is for “advanced users”. Using it you can delete, copy or move files manually.

So, first of all, try using the “Startup Repair” item, if that doesn’t help, then “System Restore”.

In this article, we looked at the main reasons caused by a software malfunction of the computer, due to which Windows very often does not boot. We hope that we were able to answer all the questions and clearly explain what to do in this case.

If you still haven’t been able to figure out on your own the reason why Windows 7 or XP won’t start on your computer or laptop, and you don’t know what to do next, then you can always contact us for help - the center computer help website. Our service technicians will quickly and accurately determine the cause of the breakdown and eliminate all faults. In addition, they will give valuable advice on how to make sure this doesn’t happen again.

Also write your questions in the comments. And you will definitely get an answer to them.

The problem of Windows failing to boot is quite common, despite the fact that Windows 7 and Windows 10 are very reliable operating systems and rarely crash. Of course, equipment also plays a huge role in this, which is very diverse for home systems, and has a low fault tolerance factor for budget solutions.

In most cases, errors in loading the OS are either the fault of the users themselves, who, for example, performed an incorrect shutdown of the PC or accidentally deleted a system file, or a hard drive on which a bad area has formed on the boot sector.

CHIP suggests using our tips to solve the problem with loading Windows and restore system functionality.

Let's try to start

Faced with the impossibility of loading the operating room Windows systems, first you should restart your computer a couple of times, because the problem may be a one-time problem. If this does not help, then try turning off the power to the computer for ten seconds by unplugging it from the mains. In this case, you need to de-energize the block uninterruptible power supply, if one is connected, and if we are talking about a laptop, then remove the battery.

It also doesn’t hurt to temporarily disconnect external equipment: mouse, keyboard, printer, removable drives, modules wireless communication and so on. If the reason lies precisely in external devices, connecting each of them in turn will help identify the culprit.

Of course, the problem cannot always be solved with the simplest manipulations, which means you will have to start analyzing the text of the error message that appeared during the computer startup.

The bootloader may be damaged

If you see a message on the screen with the text “BOOTMGR is missing,” it means that the Windows 7 operating system boot loader is damaged or missing. To solve the problem, you will need a Windows 7 installation disc.

Restart your PC and during the first seconds of booting, press the function key to open the BIOS. These may be different keys for different PCs, such as ESC, F2 or F6. Pressing the F8 key in Windows 10 will bring up a menu of special boot options, including Safe Mode. If this doesn't work, hold down the Shift key when rebooting Tens.

So, if you managed to get into the BIOS, go to the “Boot device priority” section using the “+” or “PgUp” key and assign the CD/DVD drive as the first boot device. Then boot from the Windows installation disc and select the “System Restore” menu item. From the list of installed operating systems (if there are several of them), you need to select the one you need and click the “Next” button.

In the “System Recovery Options” window that appears, we are interested in two items: “System startup recovery” and “Command line”. The first option will automatically fix the problem with starting the operating system, and if it fails, you will have to turn to the services of the second.

At the command line, type:

"bootrec /rebuildbcd"

press “Enter” and agree to changes to the boot configuration data by alternately pressing the “Y” and “Enter” keys. After this, all that remains is to create a new boot sector using the “Bootrec / FixBoot” command and reboot the computer.

Boot disk not detected?

The error message “No bootable device” and its numerous variations (“No Boot device found”, “Invalid boot device”, “Non system disk or disk error”, etc.) indicate that the computer has not even started to start operating system, since it does not see the boot sector or even the hard drive.

To understand whether the problem lies at the software or hardware level, just go into the BIOS to the already familiar “Boot device priority” section. If the hard drive (HDD) is not visible among the proposed options, then the problem is related to the equipment. It is possible that the power data cable or power cable of the hard drive has come loose, or the drive has completely outlived its usefulness.

If the computer normally recognizes the hard drive, the reason is software in nature and lies in the main boot entry(MBR) - it is damaged or missing. Unlike those discussed above, this situation is relevant for both Windows 7 and XP, but can be solved extremely simply.

After booting from the installation disk, you just need to run just one command in the recovery console:

bootrec/fixmbr

Blue Screen of Death: Driver IRQL not less or equal

Messages about critical Windows errors, which are called “blue screens of death” (BSOD, Blue Screen of Death) because of the background color, are quite common problems not only in Windows 7 but also in Windows 10 (especially due to installing the wrong update). Moreover, in the top ten this screen can be green or red. The cause of a critical error may be malfunctioning hardware, for example, RAM or the absence of some system files.

Most often, early boot BSOD messages appear after updating device drivers and contain the text “DRIVER_IRQL_NOT_LESS_OR_EQUAL” along with a file name with the SYS extension. To remove the problematic driver in Device Manager, you can try starting Windows in safe mode, because it uses only a minimal set of drivers. To do this, press the F8 key while loading the OS and select “Safe Mode”.

If you still get the Blue Screen of Death when you boot into Safe Mode, you need to revert to a previous version of the driver that didn't have any problems. This can be done using a restore point, if one has been created previously.

In Windows 7, to do this, press the F8 key while the OS is loading and select “Troubleshoot computer problems” in the menu that appears. After which we find ourselves in exactly the same “Recovery Options” menu as when using the Windows installation disk.

This time we are interested in the “System Restore” item, where you can select one of the available restore points.

Returning a copy of the system file

The absence of some important system files in the system, primarily drivers with the SYS extension, is often found in Windows 7 and 10. The most effective way to solve the problem is to return the loss to its place by finding a copy of it on the installation Windows disk, borrowed from another computer with the same OS version or simply found on the vast expanses of the Internet.

If you don’t have a second computer at hand, then to search, download and copy files you will need a LiveCD with an OS that does not require installation, for example, Kaspersky Rescue Disk 18.

One of the most convenient options is the Puppy Linux operating system, which will be ready to work in less than a minute. This OS includes drivers for the most common models network cards, which means getting online won’t be difficult.

The exception is files system registry: System, Software, SAM, Security and Default, which are stored in the “C:\windows\system32\config” folder. Of course, it won’t be possible to replace them with copies from another computer, so the only option is to roll back to a restore point, if it was made at one time.

Restoring Windows 10 Boot

And to use the Windows 10 recovery tool, you need to open the menu of additional boot methods (by pressing F8 after turning on the computer) and go to the “Troubleshooting” section.

The chance of having time to press the desired key at this time (more precisely, the combination of F8 and Shift) is great if the system is installed on an MBR hard drive and the option is disabled quick launch. For fast system SSD drives you will have to try to press quickly or you will need bootable media.

In any case, you will need an installation disk with Windows 10. In our experience, a Windows 10 emergency recovery disk will often not be able to help restore the system. It is worth considering that the system image must be the same bit size as that installed on your PC. In addition, if you use a bootable USB stick, it must be with file system FAT32.

As an alternative, you can use the downloadable package of MS DaRT 10 utilities (Microsoft Diagnostic and Recovery Toolset for Windows 10). You can download it from the official Microsoft website. Windows images 10 are available for download from the Microsoft website.

Using Windows 10 bootable media

Connect the media to the computer, reboot, set this disk first in the BIOS settings and boot from it. After booting from it, select the system language. If Russian is selected, click Next.

You will then be prompted to proceed to installation or Windows recovery. Click System Restore. On the Select Action screen, click Troubleshooting.

Tens launch recovery options

In the recovery options section (Advanced Options screen) there are 5 subsections:

• System Restore. When you select this option, the standard utility rstrui.exe is launched, the purpose of which is to roll back the system to one of the saved checkpoints.
• Restoring the system image. Launches the Windows Deployment Wizard from backup copy, created by the OS's own tools.
• Boot recovery. Corrects errors in boot files and partitions.
  Command line. Allows you to run various system utilities.
• Return to the previous build. Rolls back to earlier installed version OS if it has been updated to Windows 10.

Repair utilities

Almost all of the Windows boot problems discussed in this article can be caused by damaged hard drive sectors (bad blocks). Even if, with the help of one of the manipulations discussed in the article, the operating system was brought back to life, it is not possible to check the working condition of the hard drive.

You can do this using the free MHDD application (can be downloaded), which can be launched directly from the boot CD. In the program menu, you must select from the list the channel to which the hard drive with the OS is connected, indicating its number. Then you can view the S.M.A.R.T data, a kind of “medical map” of the hard drive (F8 key), or start scanning sectors for errors (F4 key), having previously allowed their correction - “Remap | ON".

If there are a lot of problem sectors, the procedure may take hours or even days. Considering that bad blocks are usually concentrated at the beginning of the hard drive, it will be easier to move the OS partition away from the problem area - an indent of 2 GB will be enough.

A boot disk with free editor MiniTool Partition Wizard FE sections. In the program menu you need to resort to the operation “Partition | Move/Resize".

As we noted above, cause of BSOD There may be RAM that is not capable, for example, of operating at higher frequencies. In such cases, on blue screen possible text: “PAGE_FAULT_IN_NONPAGED_AREA”.

You can test RAM modules free application Memtest86. Like MHDD, Memtest86 can be run from a bootable CD. The application does not require configuration and immediately after launch it begins diagnostics using a number of tests. The “Pass” menu item displays the number of completed test cycles, while “Errors” displays the number of errors recorded.