home > Internet > Volume in win xp works with errors. Troubleshoot windows xp

Volume in win xp works with errors. Troubleshoot windows xp

Search by computer articles

Troubleshoot windows xp.

The Windows registry is one of the most mysterious and complex components of the operating system. Find and fix bugs system registry only an experienced user or programmer who is well versed in the installation components of the Windows XP OS can do it. One of the most the best programs to fix "Windows XP" errors, clean the registry and optimize the system is an excellent free program Wise Registry Cleaner 4 Free by Wise Cleaner. When installing this program, the user will be prompted to select a language. In addition, in order to start working with the program, you will need to enter your own e-mail.

Next, you should run "Wise Registry Cleaner", and in the "Options" section, select the Russian language. In addition, you must select the manual mode of cleaning the registry by clicking "Options - Automatic Cleaning - Manual", and in the "General" tab - "Create a backup copy before cleaning".

Convenient translation of the program will allow even a novice user to learn how to work with Wise Registry Cleaner.

Before you start analyzing the registry, you must click on the large button in the menu bar. This program allows you to analyze all registry values and keys, as well as diagnose all registry errors. All registry errors that are marked in green are deleted without hesitation. Before you can remove orange registry errors, you need to right-click to open the drop-down menu. If necessary, you can also return to the initial state of the registry before cleaning. In addition, you can restore the registry from saved copies. Thus, the Wise Registry Cleaner program allows you to check the system, remove junk files, as well as full recovery systems.

Manually editing the Windows registry to remove invalid Error 3 keys is not recommended unless you are PC service professional. Mistakes made while editing the registry can render your PC unusable and cause irreparable damage to your operating system. In fact, even a single comma in the wrong place can prevent your computer from booting up!

Because of this risk, we highly recommend using a trusted registry cleaner such as WinThruster [Download] (Developed by Microsoft Gold Certified Partner) to scan for and repair any Error 3 related issues. By using the [Download] Registry Cleaner, you can automate the process of looking for broken registry entries, missing file references (such as those causing the %%error_name%% error), and broken links within the registry. A backup copy is automatically created before each scan, allowing you to undo any changes with a single click and protecting you from possible damage to your computer. The best part is that fixing [Download] registry errors can drastically improve system speed and performance.

Warning: Unless you are an advanced PC user, we do NOT recommend editing the Windows Registry manually. Incorrect use of the Registry Editor can lead to serious problems and require reinstalling Windows. We do not guarantee that problems resulting from misuse of Registry Editor can be resolved. You use the Registry Editor at your own risk.

Before manually restoring Windows registry, you need to create a backup by exporting a part of the registry related to Error 3 (for example, Windows XP):

Click on the button To begin.
Enter " command" in search bar... DO NOT PRESS YET ENTER!
Holding down the keys CTRL-Shift on the keyboard, press ENTER.
An access dialog will be displayed.
Click Yes.
The black box opens with a blinking cursor.
Enter " regedit" and press ENTER.
In the Registry Editor, select the Error 3-related key (eg. Windows XP) you want to back up.
On the menu File select Export.
Listed Save to select the folder where you want to save the backup Windows key xp.
In field File name enter a name for the backup file, such as "Windows XP Backup".
Make sure the field Export range value selected Selected branch.
Click Save.
The file will be saved with .reg extension.
You now have a backup of your Windows XP-related registry entry.

The next steps for manually editing the registry will not be covered in this article, as they are likely to damage your system. If you would like more information on editing the registry manually, please see the links below.

Hello, now I will tell you how you can restore the bootloader not only, but also manually, which often helps in most cases.

How is the computer boot process going?

After the computer has turned on, it performs a self-test, then control is transferred to the main boot record hard disk, it contains the hard disk partition table and a small bootloader program that reads information in this table from which hard drive (if there are several) and which hard disk partition to boot the OS.

Next, the operating system kernel is loaded into RAM and actually Windows startup xp. You also need to know that a group of files located in the root directory of drive C, namely boot.ini, NTDETECT.COM, ntldr, also participate in the loading of the operating system. The presence of all of the above excludes the presence bootmgr errors is missing when XP boots and ensures that the system starts successfully.

What could be the causes of the Bootmgr is missing error?

The first is the simplest, with several hard drives in the system, violated bios settings, namely, for example, in AMI Bios, in the BOOT tab, the Boot Device Priority item, then Hard Disk Drives, the hard drive from which you need to boot is set to the wrong one at all.

2. The use of third-party programs in the master boot record, the so-called boot managers, such as Acronis OS Selector, is mainly used when there are several operating systems on the computer, the manager displays a convenient OS selection menu at the beginning of the boot.

You need to use such programs very carefully, in case of incorrect removal from the computer itself Acronis software Disk Director, a very big chance to do Windows XP bootloader recovery.

3. The same applies to the GRUB bootloader, which allows you to use Linux and Windows XP on one computer, when you remove GRUB, you will leave your computer alone with an incomprehensible boot entry and it will show you Bootmgr is missing without hesitation.

Here's what we're going to do

In this case, we will correct the situation in the console Windows Recovery XP, first we will enter the FIXMBR command and overwrite the master boot record, with the second FIXBOOT command we will write a new boot sector.

But that's not all, after fixing the boot record, as well as writing a new boot sector in the console, the situation with the error output may remain unchanged and there may already be other errors, for example: NTLDR is missing. In this case, you need to make sure once again that there are boot sector files that are directly involved in Windows boot XP: boot.ini, NTDETECT.COM, ntldr, in the root directory of the drive (C :), in principle, three of these files are enough to boot Windows XP.

The easiest way is to use a Live CD, boot from it, then go to the root directory of drive C and make sure that these files are present, if they are not there, then you need to copy them from any workable XP and drop them to yourself, after checking and editing if necessary boot.ini file, a simple text file that contains the path to the system Windows files XP, you must do this, otherwise you will get another error, you can read Editing BOOT.INI.

But there is an easier way: recovering the Windows XP bootloader using the Recovery Console. If you have an XP distribution, let's use it and copy our three boot.ini files, NTDETECT.COM, NTLDR to the root directory of drive C.

How to restore the Windows XP bootloader?

We boot from the Windows XP installation disk, select restore R. If we have one operating system, put the number 1.

If there was a password, enter it, if not, press Enter.

We enter the FIXMBR command, this command is to repair a damaged hard disk partition table, it will overwrite the master boot record.

We confirm the recording of the new MBR, set Y

We enter the FIXBOOT command, and agree to write a new boot sector.

Copy the files ntldr, NTDETECT.COM, boot.ini from the distribution to the root system disk C. Enter the MAP command and look at the letter of our drive, in my case (D :)

Type D: (drive letter) and press Enter.

Go to the i386 folder, which is located on the installation Windows disk XP, from it we will copy our NTLDR file to the root of drive C. Enter the command cd i386 and Enter

Copy the NTLDR file to the root of our system drive with the operating system using the copy NTLDR C command.

Many users, when serious failures appear in Windows XP, prefer "amputation": formatting the disk and complete reinstallation OS. However, such a simple and radical surgical method is not suitable if many important programs are installed and configured in the system, the reinstallation of which is impossible or too expensive. In this case, a deep Windows diagnostic is required.

Each type of Windows XP failure has its own cause, and therefore, although quite unambiguous recipes for getting rid of the most common problems are known, it is impossible to develop some kind of universal method"treatment". The configuration of each operating system, software, drivers and hardware is unique, and most often it is possible to find out the cause of a problem only by carefully dissecting the hardware and software insides of a particular computer. If the failure does not accompany the OS right from the moment it was installed, but appeared at some specific moment (after installing another program or driver, changing Windows settings, power failure), then getting rid of it is easy, just remove the problematic application, or restore the registry or even the entire contents of the hard drive from the backup. Not only the standard System Restore will help in this, but also more interesting programs eg Norton Ghost , Ashampoo Uninstaller , WinRescue XP . Of course, this is possible if the user did not disdain prevention and regularly used such programs, which is not at all difficult, by the way. For example, a full backup of a 10 GB NTFS system partition in Norton Ghost takes only 10 minutes (it is unreasonable to allocate the entire disk space to the OS).

If there is no way to restore the system " little blood”, or completely reinstall it, you will have to independently look for the cause of the failure. To achieve success in such an ungrateful and tedious business, it is recommended to follow this technology:

preliminary stage

Before starting diagnostics, make a backup copy of the registry, configuration files, or the entire system, so as not to get even bigger problems as a result of experiments. Be sure to remember all your further actions so that in case of problems they can be easily undone.
Delete all temporary files, clear the browser cache, Trash, History, clear the Program Files\ folder Internet Explorer\ Plugins with IE plugins (to restore them, do backups). Clear the folders from which MS-Office scripts are auto-started (such as Documents and Settings\ USER\ Application Data\ Microsoft\ Excel\ Xlstart, Documents and Settings\ USER\ Application Data\ Microsoft\ Word\ Startup), delete the normal.dot template, used by MS Office. Clear Windows folders\ Downloaded Program Files, Documents and Settings\ USER\ NetHood, Documents and Settings\ USER\ PrintHood, Documents and Settings\ USER\ Recent. Delete the autorun.inf files from all local drives.
Check the system with several fresh antiviruses and Ad-Aware program, scan HDD utilities such as ScanDisk, Norton DiskDoctor (with the mandatory inclusion of write testing). Check system files using the System File Checker utility (SFC /SCANNOW command) and repair corrupted libraries from a Windows distribution or Service Pack.
Update the system: in addition to the latest service pack (if it is already installed, reinstall it), install all the latest "patches" on the site windows update(windowsupdate.microsoft.com, just be aware that some patches themselves can be problematic). Update (reinstall) Internet Explorer and the Microsoft JAVA Virtual Machine. Update DirectX using the redist distribution for this (the volume is about 25-30 megabytes, and the file name contains the word "REDIST": DX90b_Redist.exe). Sometimes it turns out to be useful to first remove Internet Explorer or DirectX, and then reinstall it - you can use the XPLite utility for this.

Finding a turnkey solution

Carefully study the documentation for the failed program or expansion board, maybe there are some special instructions in it. Also visit the website of the developer of the failed program or device - perhaps the manufacturer's technical support service knows about the problem and offers to download some kind of patch.
If the failure is accompanied by error messages (for example, STOP errors on a blue screen), then write down their exact contents and go to the Microsoft support site. Based on the error message, you need to formulate a request for search engine(for maximum search efficiency, try to formulate a query with several different ways). Find a solution in the database Microsoft data- most fast way troubleshooting. If there is no information about your failure in the Microsoft database, then run a specialized Internet search utility, such as Copernic or Search Plus, and also try to search the Web and UseNet technical conferences for materials on similar problems. Or use Russian and foreign search engines such as Yandex, Yahoo or Google.
Please note that if your system has the automatic reboot if it fails, then the blue screen of death message will not be displayed. Therefore, in the Control Panel - System - Startup and Recovery - Settings menu, clear the Automatically restart flag in advance.
For more information about the failure that has occurred, also refer to system log errors - Event Log (Computer Management - Event Viewer, "Computer Management" - "Event Viewer"). Documentation for most Event IDs is available at the Microsoft Events and Errors Message Center and www.eventid.net. Something can be squeezed out of the Dr.Watson system debugger, which can be called from the System Information program window.
Enable the mode of sending error messages to Microsoft in Windows XP: Control Panel → System → Advanced → Error reporting → Enable Error Reporting (Control Panel → System → Advanced → Error reporting → Enable error reporting). You will laugh, but there have been cases when, after sending information to the developers about the crash, the user received a response with a specific solution to the problem.
Check out Windows nationwide troubleshooting sites such as www.techadvice.com , www.jsiinc.com/reghack.htm , www.mdgx.com , www.aumha.org , labmice.techtarget.com/troubleshooting/generalguides .htm - they will provide links to articles on troubleshooting many common crashes.
Attend popular web and UseNet conferences on operating systems, software, and hardware. After describing the failure of your system in great detail (and not forgetting to indicate its version!), Specifying the exact content of the error message and describing the configuration of your system, try asking other users for help - perhaps someone has already encountered a similar problem and knows its solution, or may suggest the direction of further searches.

Checking the settings

In the Control Panel, check all system and hardware settings - set all parameters to the "Default" position. In particular, remove swap file size limits, check if there is enough disk space, and in the settings environment variables temporarily provide a shorter path to the TEMP folder (for example, C:\TEMP). Even in the keyboard settings, set the default English language. Also check all settings in the options of the applications used.
Restore the settings in the registry and in the configuration files user.ini, system.ini made using the tweaker utilities to their original state. Check the settings in autoexec.nt, config.nt, _default.pif files. Run a search in the registry for the word "Policies" and delete all settings in the found sections (except for the PowerCfg sections responsible for power policies, as well as the HKEY_LOCAL_MACHINE\ SOFTWARE\ Microsoft\ Windows\ CurrentVersion\ Internet Settings\ TemplatePolicies section, which contains IE security policy templates) - perhaps the failure is just a consequence of the restriction of user rights. Carefully check the current security policy settings in the Editor group policies Group Policy Editor (GPEDIT.MSC).
Return to the original - Default - the state of the setting in the BIOS, experiment with different options CMOS Setup, for example, turn off DMA mode for disks, change memory timings, turn off all integrated devices, turn on the “hole” around 15 megabytes of memory. Disable everything related to power management in CMOS Setup, including ACPI. Or vice versa - enable all these options if they are disabled. Experiment with PnP OS Installed and USB Legacy Support in the same way. Update the BIOS. And give up overclocking: overclocking is the main enemy of Windows XP!

System and programs

Run the msconfig.exe utility and disable all startup programs. Try experimenting with the Selective Startup mode as well - perhaps an incorrect entry lurks in system.ini or win.ini, another rudimentary configuration file. Using msconfig, it is also convenient to check system services, for example, by comparing the list running services with another PC that does not experience such a failure. good description assignment of Windows XP services, which will help you find out the initial and recommended status of their settings in different Windows versions, you can find it at www.blackviper.com . Try disabling unnecessary services, such as WEB Client, and also check service dependencies using the Services snap-in.
Try to remember what actions caused the failure. Uninstall a few programs and drivers that were installed most recently - one of them may be causing a system crash or conflicting with other programs and hardware, causing them to crash. Uninstall any programs that were created more than two years ago and haven't been updated since. Remove antiviruses and other software that closely integrates with the system. Be sure to use a specialized uninstaller such as Ashampoo Uninstaller, both when installing and removing programs - this is the only way to completely clean the system of all traces of the program or driver being removed! In addition, the analysis of the uninstaller log allows you to find out which files on the disk and which parameters in the registry were changed during the installation of the program - often, to fix a failure, it is enough to change an incorrectly changed parameter in the registry. When reinstalling programs and drivers, try not only the latest version (note that patch updates are regularly released for some programs), but also an older one - it often turns out to be more stable. Try reinstalling the failed application to a different directory with a shorter name.
For outdated programs try setting the special compatibility mode. To do this, create a shortcut to the program, enter its properties and on the tab "Compatibility" (Compatibility) in the item "Run the program in compatibility mode" (Run in emulation mode) select the compatibility mode with another type of Windows. Also, make use of the Application Compatibility Toolkit, which is designed to greatly expand the capabilities and manual setting this mode.
Try running the offending application under an administrator account. If the program works only under it, then under the Administrator account, find the section with the settings of the desired program in the HKEY_LOCAL_MACHINE \ SOFTWARE registry branch and right-click on it. Select "Permissions" from the menu that appears and set full access to this registry key for the user or group of users who are allowed to work with it. Also find the section corresponding to the failed program in the HKEY_CURRENT_USER branch and export it to a REG file. Log in now as ordinary user and import this .reg file back into the registry. Sometimes you can get rid of such a failure if you delete your account(and the entire user profile) and then re-create it.
Try to find and fix registry errors with a program like Norton WinDoctor. Found errors should be corrected only in manual mode analyzing each of them. To do this, you need to try to find out which program or system setting There is an erroneous entry in the registry, by viewing in RegEdit the branch that WinDoctor signals - by the names of files, parameters or by the prescribed paths, it is easy to install the application that generated the error. Try using other diagnostic utilities, such as the DirectX Diagnostic Tool included with Windows, it will check DirectX files, drivers, settings of some devices. Some simple failures are eliminated by the Tweak UI program, for this it provides a “Repair” tab.
Some Windows problems XP are eliminated by restoring the hard disk master boot record (MBR) with the "fdisk /mbr" command after starting the PC from a Windows 98 floppy disk (this is necessary to subsequently overwrite the disk ID), or using the "fixboot" and "fixmbr" recovery console commands. Boot the PC from a Windows 98/Me floppy disk with NTFS support (to do this, use the program NTFS for DOS Pro) or the ERD Commander disk and delete the PAGEFILE.SYS file. ERD Commander is, generally speaking, an excellent program, which is a kind of LiveCD for Windows XP. It allows you to fix many problems and access OS settings, even if Windows itself does not boot into failsafe mode. Check for errors in boot.ini and the current file and folder permissions: the user group "System" and "Administrators" must have full rights access to the root directory of the system disk and to the file virtual memory PAGEFILE.SYS.
Track various system events, requests and accesses to the registry at the time of the failure using special monitoring programs. Analyzing calls to the registry, you can, for example, determine which parameters from the registry are requested by the program immediately at the time of the failure - perhaps some of them are missing or have an incorrect value. And with the help of file access analysis, it is easy to understand which files contain the settings of a failed program, and which files it needs are missing. Utilities from SysInternals will help with this: Registry Monitor - analysis of registry accesses, File Monitor - monitoring of file accesses, DllView - information about libraries used by current processes, OpenList - information about all open files, PortMon - access to ports, TCPView - information about TCP connections. Display information about all running programs the TaskInfo program is the best. It will also show how much CPU resources each application consumes. And to find out the cause of the congestion that occurs during boot, you can use the well-known diagnostic utility BootVis (however, Microsoft no longer distributes it, so use the search). Also check the system with a comprehensive diagnostic and information package SiSoft Sandra or AIDA32.
Remove unnecessary fonts, disable all performance counters, make sure that there are no folders and files with very long names or extensions (220 characters or more) on the disk, do not use very long command line parameters (220 characters or more) when working with programs.

Equipment

Update all drivers for all devices (or uninstall and reinstall the drivers of the problematic device, as well as the driver of the device to which it is connected), especially chipset drivers: Intel Chipset Software Installation Utility and Intel Application Accelerator or VIA-4-in-1 ( plus other drivers and patches from VIA, such as VIA IRQ Routing Miniport Driver, VIA IDE Miniport driver and others, depending on system configuration). Check for special patches and updates on the websites of equipment manufacturers, and most importantly - motherboard.
Check the health of the equipment, the correct setting of jumpers on it, test it using utilities such as Memory Test, CPU Stability Test and the like. Check everything, right down to the battery, the voltage of the power supply and the quality of the motherboard mounting - there should not be any spontaneous short circuits or unreliable contacts anywhere!
Temporarily replace all memory modules - this is the device that fails most often. If this is not possible, then try to limit its size, for example, to the first 64 megabytes. In Windows XP, it is convenient to use the MSCONFIG.EXE utility for this: the MAXMEM parameter in the boot.ini file. Try more powerful block power supply, oddly enough, the lack of power is very often the cause of Windows crashes.
Check the temperature and performance of the cooling devices of all system components, even the chipset (you can even install a special fan on the chipset heatsink). Ground PC, install surge protector or source uninterruptible power supply. Check the quality of the telephone cable, network cable, electrical wiring.
Delete everything additional devices from a PC (except for the hard drive and video card, although sometimes replacing the video card helps), even the internal tweeter speaker, after which, in fail-safe mode, using the "System Properties" dialog, remove their drivers and look - did the crash go away? If it disappeared, then install the devices back in turn, each time repeating the procedure, which usually leads to an error message - perhaps there is some kind of hardware conflict and in this way you will either identify its source, or the system will redistribute resources and eliminate it itself .
Install the problematic device in another PCI slot, in the system properties and the System Information utility (Program Files\ Common Files\ Microsoft Shared\ MSInfo\ msinfo32.exe) check for conflicts. The SiSoftware Sandra program is very good for getting information about the system. If ACPI is disabled, try manually remapping conflicting interrupts (or other resources such as DMA channels or I/O ranges). Try replacing the problem device with exactly the same one, or with a device of a different brand - perhaps the defective copy is simply to blame or changing the manufacturer of the expansion board will eliminate the conflict. For disks, try a different cable, instead of an 80-wire cable, try a 40-wire cable and vice versa, check that the Master / Slave jumpers are set correctly, move the disk to another cable, set it to auto-detect in CMOS Setup, or set its parameters explicitly, or set it to "NONE". Do not connect other devices to the same cable with the problem disk.
Take a look at the properties of the problematic device - perhaps there are settings there that will fix the failure, for example, disable or enable DMA mode for the disk. If the computer does not boot, then try to access these menus from the Safe Mode.
In case of problems with the drivers, boot the PC in failsafe mode, delete the problematic device in the Device Manager (as well as all printers and devices that do not exist in reality, even joysticks) and after loading the OS in normal mode, install the latest driver. However, sometimes more old driver turns out to be more stable, try different versions. Note that instead of rebooting, turning off the PC completely and then turning it back on after a few minutes of no power is sometimes helpful in eliminating the failure. If the failure has something to do with the network, then in the Network properties, delete all network components and, after rebooting, install everything you need again. Remove all printers if there are problems with them, and also reinstall their drivers after the reboot. Remove all drivers not certified for Windows XP, verify signatures system files the File Signature Verification utility, called from the System Information program window, will help. If the driver was installed unsuccessfully, then use either the Last Known Good Configuration (called in the boot Windows menu), or in the system properties, roll back to previous version drivers.

Things are bad

Reinstall Windows over a previous installation, all files will be restored to their original versions, but the main settings in the registry are preserved, so if the failure is due to incorrect registry settings, then such a reinstallation may not fix anything. In some cases, just before installation, you can remove all hardware from the failover mode in the System Properties dialog so that Windows reinstalls all drivers again. Try also different disks with the OS distribution kit - the original disk may be damaged.
After completely erasing the Windows, Program Files, System Volume Information and Recycler folders (or repartitioning and formatting the disk), install Windows "naked". Windows 2000 or Windows 98 may be more efficient. Sometimes you need to format a drive special utility from the manufacturer of the hard drive to completely reset it. In some cases, for example, after incorrect operation of programs such as Partition Magic, to fix the failure, it is necessary to partition the disk again using the standard Fdisk.

Finish

Ask the experts or… try your luck with Linux…

www.symantec.com
www.ashampoo.com
www.superwin.com
www.lavasoft.com
www.microsoft.com/windows/ie/download/default.htm
www.microsoft.com/java/vm/dl_vm40.htm
www.litepc.com
search.support.microsoft.com/search/?adv=1
www.copernic.com
srchplus.chat.ru
www.microsoft.com/technet/support/ee/ee_advanced.aspx
www.eventid.net
www.techadvice.com
www.jsifaq.com/reghack.htm
www.mdgx.com
www.aumha.org
labmice.techtarget.com/troubleshooting/generalguides.htm
www.blackviper.com
www.microsoft.com/windows/appcompatibility/default.mspx
www.winternals.com
www.sysinternals.com
www.iarsn.com
www.microsoft.com/whdc/hwdev/platform/performance/fastboot/BootVis.mspx
sisoftware.net
www.aida32.hu/aida32.php
support.intel.com/support/chipsets/driver.htm
www.viaarena.com/?PageID=66

Windows boot errors are quite common. It may indicate a hard drive failure, random access memory, processor or operating system.
Let's see what the errors mean and how to get rid of them.

System boot

Read also: TOP-12 Programs for computer diagnostics: a description of proven software tools

Let's analyze the OS boot process. When the computer is turned on and booted successfully, the processor executes a series of instructions provided to it by the BIOS.

These instructions are stored in volatile CMOS memory. After starting, the processor accesses the addressable cell of the microcircuit. It depends on the embedded properties. It contains the BIOS code.

The initial set of instructions executed by the processor is called POST (Power-On Self Test).

With its help, the following actions are carried out:

An initial check of the hardware is performed, including the state of the processor and the size of the RAM. At the same time, the performance of the OP is checked.
The system configuration setting is being received from the CMOS memory.
The bus frequency is set in accordance with the supplied settings from CMOS.
It checks for the presence of a device from which the OS will be loaded (hard disk, floppy drive, etc.).
An audible signal indicates the end of the test.
Other devices are initializing.
At the end of the POST procedure, other adapters begin their internal check, such as a video card, sound card, hard disk controllers. When checking, all information is displayed on the monitor screen.

The BIOS stops booting when it finds the master boot record on the hard drive (or in the location of the OS record) and transfers control of further booting to it.

Now the programs recorded on the media enter into the download.

We list the main download problems:

You need to find out the cause of the failure and fix it. And so that problems do not arise again - do not repeat these mistakes.

This is very important for the further correct operation of the system, otherwise you will have to reinstall again and again software and operating system, which will wear out the hard drive.

The fact is that the error when loading Windows varies depending on the version of the OS.

So, different versions will have different errors most common. That is why you need to look for a solution to the problem for your OS.

Read also: 3 ways to install Windows XP from a flash drive

At present, this Windows version practically ceased to exist.

However, some computers (often these are older models) still work on this OS.

And although people who have known XP for a long time are used to its mistakes, it is worthwhile to deal with the most common of them.

Loss of bootloader

This is the most common problem when booting Windows XP. It usually occurs when trying to reinstall the OS.

When this error occurs, the system issues one of two messages:

1 OS boot failure.

2 Corruption of partition tables.

Elimination of these errors is possible by performing these points:

start the recovery process from the disk on which the OS is recorded;
run the installation program;
after the inscription of the greeting, press the button "R";
the recovery console will be displayed, you must specify in it installed version OS;
type "fixmbr" and press Enter.

The system will then restart and the error will be resolved.

Although there are other reasons for the loss of the bootloader, however, the above happens most often.

NTLDR is missing

This problem is also quite common. When it appears, often, users simply format the disk, which leads not only to the elimination of the error, but also to the loss of all memory.

However this problem can be solved without such radical methods, it is enough to understand the reason for its origin. And to eliminate and at the same time save the data is not so difficult.

This error is a black screen with the inscription NTLDR is missing.

Sometimes, to fix the problem, it is enough to press the popular keyboard shortcut Ctrl + Alt + Delete (this is written in the error screen).

This combination should restart the system, but this does not always help.

The error means that the files responsible for loading the system are not available. There may be several reasons for it:

1 Hardware failure. This is the most annoying problem, since it means that the malfunction lies in the hardware, and is not the result of any failure in the system. Correction of this error will be the replacement / repair of a faulty component.

2 Connection additional hard disk. It is also the cause of the error. The problem is fixed by the BIOS tool, after performing a series of simple steps.

3 Conflict between two installed OS. Some computers have two Operating Systems which may lead to their reluctance to work with each other. Troubleshooting occurs using the installation disk with Windows.

HAL.dll

With this problem, during the OS boot, the user observes an inscription like “Cannot run HAL.dll” or “File not found or corrupted”.

When it appears, the first solution that comes to mind is reinstalling Windows. However, you can cope without such drastic measures.

The fact is that given file is responsible for the interaction of hardware (the computer itself) and its software components.

The problem arises because XP, as the most old version, is subject to various errors most often.

As such, there can be many reasons for the error to occur. However, it can still be eliminated using a series of actions in the BIOS without reinstalling the operating system.

Nevertheless, it should be understood that sometimes only a radical method will help to cope.

Read also: TOP 6 Ways to clean Windows 7-10 from unnecessary garbage, just clear the memory cache, uninstall updates and clean the registry

Despite the new versions of Windows, the seven still remains the most popular. It's more of a matter of habit.

Many people think this version the most convenient and average between XP and the same eight (in principle, this is how it is)

It is precisely because the version is the most popular that the Windows 7 download error is a common problem.

Most often, when loading Windows 7, various error codes occur that indicate a particular problem. It is worth dealing with the most common problems that arise.

System bootloader

Like Windows XP, the seven has problems with the bootloader. The cause of the problem is the same as the previous version.

However, you can restore the seven bootloader both automatically and manually.

The first method is the most convenient and even the most inexperienced user can handle it, but it can not always help get rid of the problem.

0x80300024

This error occurs during OS installation. This happens due to the inexperience of many users who, when reinstalling, forget to format one of the hard disk partitions.

This error usually indicates that there is not enough space to install the system.

In order for the error not to occur, it is necessary to check the memory on the hard disk and, if necessary, format it.

"ERROR"

A well-known error that occurs when the system starts. Usually occurs after installing the OS. Large red letters are highlighted on a white background.

To solve the problem, you need to restart your computer with installation disk inside and when you turn on the drive.

Go to the "System Restore" item, and then check the box next to "Use recovery tools ...", however, it is worth considering that you will have to select a system.

AT command line you need to enter "bootrec / fixboot". After that, the problem will be fixed.

Startup Repair Offline

Literally, this problem means “offline startup recovery”, sometimes it is fixed after a reboot.

However, often the system tries to restore itself without a network connection and it fails. So you have to help her.

This is usually solved in several ways:

Reset BIOS settings.
Connecting loops.
Launch recovery.
With the help of "Command line".

All these methods require certain knowledge and it is better for an inexperienced person to call a person who is well versed in this.

0x0000007b

The most frightening error for users is “ blue screen of death". Often this means that the system has “lay down” and only drastic measures will help it.

However, sometimes it also happens that after restarting the computer, the error disappears and no longer manifests itself, but it should be understood that in this way the computer signaled a serious problem that needs to be fixed.

There can be several main reasons for the problem:

Hardware incompatibility.
Driver problems.
Problems with antivirus.
Problems in the registry.

First of all, it is necessary to diagnose the error in order to find out the cause of the problem, after which it is already taken to eliminate it, depending on the identified causes.