It is possible to re-activate Windows 10. Replacing the motherboard without reinstalling Windows. Cloning operating system. Why is this happening

If you are going to update / replace your motherboard, but do not want to reinstall Windows, driver, programs, or you want to switch the SATA controller modes with IDE to AHCI or RAID (or vice versa), then this article is just for you!

Often when changing the motherboard and start a PC without reinstalling Windows you can see " blue screen Death "(BSOD) with Stop 0x0000007B Inaccessable_Boot_Device error.

The cause of this unpleasant picture of the Windows-availability of Windows itself to find proper drivers for the SATA controller. This problem can be easily eliminated without reinstalling Windows. For this, everyone needs to "order" the operating system to use it standard driver SATA controller at startup, which is loaded after a clean Windows reinstall. And the registry editor will help us.

Run "old" windows on a new motherboard

To make changes to the Windows registry, just follow the instructions below:
Before proceeding to further actions, it is necessary to determine below:

1. You are just going to replace the motherboard or change the IDE / AHCI mode and your PC is running in normal normal mode, Windows starts
2. You have already replaced the motherboard and Windows does not start. In this case, you will have to use the autonomous registry editor.

1. Changing the registry Before updating the motherboard or controller settings

This section is suitable for those whose PC starts in normal mode and you are just going to replace the motherboard. Open, for this press the buttons " Win + R."And the window that appears, type" ", then click ENTER.

We offer the registry editor. It looks like a "tree" with a bunch of folders and settings:

We need to go into the branch:

HKEY_LOCAL_MACHINE \\ SYSTEM \\ CURRENTCONTROLSET \\ SERVICES \\ MSAHCI

We find the START parameter there and set it the meaning " 0 "(Zero) and press the button" OK»

HKEY_LOCAL_MACHINE \\ SYSTEM \\ CURRENTCONTROLSET \\ SERVICES \\ PCIIDE

and do the same with the start parameter

If you use RAID (if not, then skip this step) It is necessary to do the same in the next branch:

HKEY_LOCAL_MACHINE \\ SYSTEM \\ CURRENTCONTROLSET \\ SERVICES \\ IASTORV

This preparation is over. Now you can install a new motherboard or me the SATA controller parameters. The next time you launch Windows will boot with standard SATA controller drivers. After launch, automatically drivers will be installed on a new controller. After downloading, do not forget to install the new drivers from the motherboard, which come in the kit, or download them from the Internet. It is best to download original drivers from the manufacturer of your motherboard.

2. Changing the registry after updating the motherboard (Windows does not start)

If you have already changed the motherboard and there is no possibility to download Windows, for example, the old failed, then in this case you need to use the autonomous registry editor. To solve this task, I prefer to use the recovery environment where you can get, for example, using a disk for installation operating system.
To open the registry editor using the installation DVD or USB drive, download the computer using installation disk. You may need to choose a DVD / CD or USB as the first boot device in the BIOS settings.
After loading, on the first screen, click "Next", and then select Restore System.

If you have Windows 7, then on the first screen, click Next, it will notice to start the command prompt

If you use Windows 8.x or Windows 10, then you need to choose "Diagnostics" -\u003e " Extra options"-\u003e" Command Line ".

In the command line, enter and click ENTER.

In the registry editor, highlight the branch HKEY_LOCAL_MACHINE, And in the "File" menu, click "Load a bush".

Open the disk on which the operating system is installed.

Go to the Windows \\ System32 \\ Config directory, select File system. And click "Open".

Enter the partition name (for example, offline) and click OK.

Opening the HKEY_LOCAL_MACHINE branch, you will see the created section (in our example it is called offline).

Deploy a new section and go to the following subsection:

HKEY_LOCAL_MACHINE \\ OFFLINE \\ CONTROLSET001 \\ SERVICES \\ MSAHCI

Open the Start parameter, change its value to 0 (zero), click OK.

Perform the same operation in the subsection:

HKEY_LOCAL_MACHINE \\ OFFLINE \\ CONTROLSET001 \\ SERVICES \\ PCIIDE

Close the registry editor, command line and restart the computer. Remove the installation disk so that the operating system can boot as usual. Now Windows must start without any problems and then install the necessary drivers of the hard disk controller. Do not forget to install the drivers from your new motherboard!

Conclusion

This is not a difficult method, you can save your Windows operating system and all programs installed on it when changing the motherboard or when changing the SATA controller parameters without reinstalling the system.
I hope this article was useful!

If you touch the license for the Windows 10 operating system, then its work is carried out somewhat differently than, for example, it is implemented in versions of Windows 7 and Windows 8. If the user could use the license key on different computers, then with the "dozen" Somewhat differently - the license applies only to one desktop and can "fly" when replacing equipment in a PC.

For comparison, Windows 7 and Windows 8.1 operated such a scheme: after purchasing a license for a system or a new device, the user received a license key that actually activated Windows. Moreover, there was no importance on which PC did the system worked, for example, after PCs outdated and broke, the user, withdrawing the activation from it, could activate a new device. In the case of the Windows 10 operating system, the situation is different: each license is carried out with reference to the user account in Microsoft, while the unique identification number is assigned, which is associated with one device on which the system itself has been activated.

If the user has thought up to change the equipment on the device, it can also be changed by the identification number, with the "flying" system of Windows 10, which will be unsacting again. Moreover, different types Devices "weigh" in different ways, which in itself affects re-activation. For example, after replacing the mouse, hard drive or keyboard, activation will remain unchanged. But if the motherboard or the RAM processor is subject to replacement, the activation responds. Acquisition of the Windows 10 activation key is possible only in the case of buying a new license, but if the desktop is updated with Windows 7 or Windows 8.0, then the user has no licensed key, as well as the possibility of re-activation.

Based on all the specifics of the activation of "dozens", it is necessary to note the explicit imperfection of the system, which checks the uniqueness of the computers. As already noted, the failures often arise if the user wants to use its right to replace components on his desktop, as a result of which it can lose the license of Windows 10. The imperfection of its system is recognized in Microsoft, introducing automatic check of modified computers, without having to contact technical supportThat sometimes became a real "headache" when the user had to prove that he did not get a new computer and does not try to install the system to another PC.

So, if, after the PC Upgrade was implemented with the "Ultimate" of Windows 10, after opening the "Parameters" system application, you must transition to the "Update and Security" section, then "Activation", click "Troubleshooting". Performing this function is possible exclusively on the non-activated copy of Windows 10 and only under the personal account of Microsoft. Then the interaction with automatic systemWhen the user should describe the essence of the problem, for example, the activation disappeared after the PC is upgraded. After that, the system once again implements the equipment check, which is installed on the desktop with the return of activation. It should be noted that in activation it can be denied if the user somehow conceived to circle the system "around the finger". In the event that the computer has already been activated and the activation of Windows 10 "flew" from it, even after a thorough check, it will be returned. However, if something went wrong, you can always contact technical microsoft support by e-mail or in another way (how to do it, you can read in our article about the service of support).

On the official Microsoft resource, a chain of action is given for a possible solution to a problem with windows 10 activation loss. It is noteworthy that if the user greatly upgraded his PC, for example, it concerns the replacement of the motherboard, then with a large share of the probability, Windows 10 will be impossible. But if the user managed to bind his account microsoft recording To the Windows 10 digital license before the equipment replaced, the re-activation is possible with some of the necessary information, for example:

In the means to troubleshoot, you must select item "I recently changed the equipment on this device" followed by the transition to the item "Next";

You must enter your Microsoft account with a password and input;

Then from the entire list of devices tied to the account, you must select the one that is necessary by clicking "activate";

If the device with which "flew" activation is not displayed in the list, you should compare the account with the one that appears with the digital windows license 10 on PC.

If everything is done correctly, but the license activation is still not possible, the Microsoft Resource provides a list possible causesTo check:

Non-compliance with the release of Windows on a PC with topics that is tied to a digital license;

Non-compliance of the type of device, which must be activated, which is tied to a digital license;

A limit has been made regarding Windows re-activation on a PC;

If Windows has never been activated on this device;

If the PC is controlled by the organization, Windows repeated activation is not possible.

Often, after replacing your motherboard or change the hard disk controller in the BIOS settings (RAID, COMPATIBLE, AHCI, Native SATA), the system boot starts as usual, the initial screen saver appears, then reset, information about POST BIOS passage, and again, start the download With the same continuation. This is usually due to the fact that the system was not able to upload the boot device driver and a critical error occurred (the loading device is not available)

Instead of rebooting, it is necessary to disconnect the automatic reboot mode in the Windows bootloader menu. This can be done if at the very beginning of the download click F8 and select the download option - Disable automatic reboot If system fails

When loading in this mode, the so-called "blue screen of death" will be displayed by the critical error on the monitor screen or Bsod. - B.lUE S.creen O.f. D.eath. This term arose during the first operators of the Windows family, due to the fact that the critical error information was displayed on a blue background. Such an error cannot be corrected by the tools itself and to minimize the loss of user data, its work stops emergency. The causes of critical errors may be malfunctions or malfunctions of equipment, errors in system components, driver errors, or their absence for critical devices.

Critical error Stop: 0x0000007B Inaccessible Boot Devicearising when replacing the motherboard, or changing the hard disk controller mode, it occurs either because the new controller is not recognized by the system as, it is, a hard disk controller, or not the ability to start the driver that can serve this controller.

At the very beginning of the process of loading the operating system, no drivers, including providing a hard disk, in the computer's memory there are no and for performing I / O operations, special BIOS subroutines are used (to work with a hard disk - the interrupt functions INT 13H function 41H 49h and 4eh to address LBA). Access to the data of the hard disk is performed using the device drivers, but via a call to the BIOS subroutines that allow the bootloader to perform the standard disk operations input - output. So, for example, to read the hard disk sectors, an interrupt is used INT 13H Function 42h - Extended reading. The 42H function transmits sectors from a specified disk area to the memory buffer. Before calling the interrupt, you must write the following values \u200b\u200bto the registers:

In An - the value of the extended reading function - 42h;

In DL - drive number;

In DS: SI - the address of the disk address package ((Disk Address Packet), which contains the information necessary to search and read data from the disk media and placing the results of the operation to perform the operational memory.

The following interrupt command is then running. INT 13H.. This receives the control of the BIOS subroutine that performs the data from the disk and transmit them to the RAM in accordance with the parameters of the disk address package. According to the results of the operation, the 42H function returns a sign of a successful (or unsuccessful) operation to the Announcement of the operation. Caused interruption INT 13. The program again receives management and processes the data obtained. That is why the loading of the system begins and for some time it is performed normally. The BIOS interrupt call allows the bootloader to perform the necessary I / O operations, including the keyboard, display, and operations with the file system. However, at a certain stage of loading, the search and reading of the drivers that provide the Windows operation begins, because in the BIOS interrupt option itself, not used for performing I / O operations. Downloads and initialization of drivers and system services begins, information about which is stored in the Registry section
HKLM \\ SYSTEM \\ CURRENTCONTROLSET \\ SERVICES
Each driver corresponds to its key, which includes a parameter Start.Defining at which stage of the system loading is loaded and initializing this driver or service. The Start parameter can take the following values:
0 - BOOT - The driver is loaded by the bootloader.
1 - SYSTEM - The driver is loaded during the initialization of the kernel.
2 - AUTO - the service starts automatically when the system is loaded.
3 - MANUAL - the service starts manually.
4 - Disable - Driver disabled.
At the initial load stage, with system Disc Low-level devices drivers are read and initialized, the START parameter in which is equal to 0 , among other things, drivers through which access to the boot device will be accessed (Boot Device). Thus, the system must determine the parameters of the download device and download the driver you need. If the download device parameters cannot be determined, or it is impossible to download the desired driver - the continuation of the system is not possible, and it is terminated by a critical error in the unavailability of the download device (STOP 7B).

& NBSP & NBSP When replacing the motherboard on a single type board, a hard disk controller, from the point of view of the operating system, will become another, new device. During the initial load, the Plug-N-Play device (PNP) is identified by the system using a special code (PNP-ID), depending on the chipset, on which the device, or chipset (chipset) is collected, and the new HDD controller collected on another The chipset will have another identifier. If the new PNP-ID of the HDD controller is "known", and there is a driver for its service - then the motherboard will be replaced without any problems. Otherwise, an unknown identifier of the HDD controller identifier will not allow it to load the driver for operation. In other words, to get rid of a critical error Stop 7b. It is necessary that the system refer to the new hard disk controller to the class of disk devices and have the ability to download the driver for servicing this class.

In the light of the above information about the Windows load process, 2 options for solving the problem are viewed:

Make the system to work with the new hard disk controller using standard Microsoft drivers.
- Add a new hard disk controller driver from the manufacturer of the equipment into a non-working system.

The first option is much easier, safer and can be easily made using the usual import of multiple keys into the register of the non-working system, for example, using disk emergency recovery Microsoft Dart.His predecessor Erd Commander. or any other means based on the Windows Preinstall Environment Preinstall Environment (Windows PE).

The second option is a bit more complicated because it is required not only to add an identification entry for the HDD controller, but also to associate the appropriate driver with it, as well as ensure its download and initialization.

& NBSP & NBSP One of the ways to eliminate STOP errox 7B is a sequential execution of the following actions:

Translation of the controller, if necessary, in the settings Bios maternal Boards in Compatibility Mode (Compatible Mode) with a standard IDE controller
Usually, this is performed in the hard disk controller configuration section and may have different settings,
Controller Mode: compatible
Configure SATA AS: IDE
SATA OPERATION AS ATA
Ahci Mode: Disabled
SATA Native Mode: Disable

Using standard Windows Distribution Drivers to download the system.

Usually, no particular effort is required for this, except to check several values \u200b\u200bof the registry parameters.

In Windows 7 operating systems and older, there are standard drivers not only for compatible mode (ATA, IDE), but also for advanced (AHCI-Advanced Host Controller Interface), which allows you to use a simpler Method of fixing STOP 7B error based on the enlarged mode The hard disk controller works in the BIOS settings (SATA AHCI) and changing the standard driver start mode.

Eliminating Stop Error 7B using standard Microsoft drivers.

& NBSP & NBSP standard driver with support for SATA AHCI controllers in Windows XP is not, so the hard disk controller must be translated into compatible iDE mode (ATA), but if the STOP 7B error occurs in this mode, then the reason can be either using the system (before replacing the motherboard) of the non-standard driver from the manufacturer of the hard disk controller, or the impossibility of recognizing the new controller at the loading stage, which is not surprising for outdated OS.
The Windows XP Distribution includes standard drivers for working with IDE (ATA) controllers HDD (atapi.sys, pciide.sys, pciidex.sys, intelide.sys), which can be used for any disk IDE-compatible controller, ensuring it recognition in quality standard IDE controller.

In rare cases, the occurrence of BSOD 7B in Windows Vista / 7 is possible due to the impossibility of recognizing the HDD controller as a hard disk of the PNP identifier. In this case, as well as for Windows XP, it is necessary to ensure the recognition of the disk controller on its PNP. But most often, the cause of the STOP error 7b for the OS data is that the standard driver that could be used has settings that do not allow it to use it at the initial load phase (what will be discussed below).

& NBSP & NBSP First, a bit of theory. Information about famous system of devices Created on the basis of.inf files when installing new equipment and is stored in the Registry section:

HKEY_LOCAL_MACHINE \\ SYSTEM \\ CURRENTCONTROLSET \\ CONTROL \\ CRITICALDEVICEDATABASE \\

Consequently, the solution to the problem with the correct recognition of the disk controller is as follows:

Determine the identifier of the new hard disk controller.
- Make, based on the identifier, changes in the registry endowed by the error "STOP 7B" of the record system, allowing you to use standard drivers from the Windows Distribution. In other words, specify the system that the device with such a PNP-ID is a standard ATA hard disk controller.

To solve the task, we need any program that allows you to get a PNP device identifier, for example, in the case of Windows XP -

This utility has been developed for quite a long time, and before Windows Vista appears, it is perhaps one of the most simple and convenient software tools for determining PNP identifiers. However, on this moment, the utility is outdated, does not work in the Windows Vista operating system environment and older, as well as in disk disk disks on windows database PE2 and later (versions of the ERD Commander older than DART 5.0). As a modern alternative to the program, it is preferable to use the universal and portable program running in any Windows environment, including Windows PE, such as the utility from Nirsoft DevmanView.designed as an alternative to the standard dispatcher windows devices:

The DevManView utility does not require installation in the system and can be used in any Windows of the Windows XP \\ 2000 family to Windows 10. And as a means of working with an unloading system, you can use boot disk or a Windows PE flash drive, the most convenient disk created by Microsoft Dianostic and Recovery Toolset ( Dart), previously known as ERD Commander (ERDC).

& NBSP & NBSP ERD Commander was specially developed by Winternals Software as a convenient tool for emergency recovery ( E.mergency. R.ePair. D.iSK - ERD). After purchasing the company WINTERNALS Software Microsoft, ERDC has become part of the optimization package called Microsoft Diagnostic and Recovery Toolset (MS Dart or Dart). Nevertheless, in the specialist environment, it is often still used old and now an unofficial name - ERD Commander ( ERDC.):

DART 5.0 - ERDC 5.0 - For Windows XP

DART 6.0 - ERDC 6.0 - For Windows Vista

Dart 6.5 7.0 - ERDC 6.5 7.0 - for windows 7

Dart 8.0 - ERDC 8.0 - for windows 8

DART 8.1 - ERDC 8.1 - for windows 8.1

DART 10 - ERDC 10 - for windows 10

Each MS DART release allows you to work with Windows, the corresponding bit (32 or 64).

Detailed Description ERD Commander and Practical Instructions for Working with Different Versions are given on the page.

MS DART (ERDC) is a software shell based on Widows PE (for Windows Vista and later - based on Windows PE2 or older), allowing you to boot from a CD or other removable media, connect to problem Windows and get convenient access to its components - file System, system magazine, registry, drivers and services, etc. The recovery environment provides the user with a set of software tools (Tools) with which you can access many resources of the connected Windows in the same way as when it is normal. It is possible to use a conductor, view system logs, disable or connect services and drivers, work with registry editor, change passwords local users, reliably destroy data on hard disk, etc. In addition, in the DART (ERD Commander), it is possible to perform almost any portable (portable) program (or programs for which it is not critical of the lack of some entries in the Windows registry performed when installing the application).

Programs DevmanView. (DevManView.exe) and (Ap Ciinfo.exe) can be performed in the ERD Commander environment without the need to install the application. ApCiinfo - only in a 32-digit versions environment for Windows XP or earlier OS. ApciInfo archive contains the utility itself and drivers required for its work. After downloading, you need to unzip the contents in any folder whose name does not contain the characters of the Russian alphabet and write to some carrier, for example, a flash drive to be able to run the utility after loading ERDC. At the time starting the loading, the media must be connected to the computer. DevManView archives contain executable module and reference information and applied similarly without installation.

STOP 7B error correction for Widows XP / 2000 OS

If there is no appropriate eRD Commander edition, it is quite possible to do with any boot disk based on Windows PE, which will be discussed below.

After selecting the system, log in to the ERDC user shell and accessible tools to work with it via the button menu Start.

Run ADVANCED PCI Info Utility (APCIINFO.EXE executable) via Start - "RUN". The utility will give a list of PCI devices

VID is the manufacturer identifier ( Vendor ID), column DID - device identifier ( Device ID). Column Device Name. - This is the name of the device assigned by the operating system, in this case, ERD Commander "OM.

& NBSP & NBSP Double-click You can call the properties of the selected device.

The hard disk controller in this example has Vendor / Device ID - 8086/7111.

Using DevmanView. Even easier than and also allows you to define PNP controller identifier hard disks:

The hard disk controller in this example has Vendor ID / Device ID - 8086 / 24D1.

Knowing the PNP-identifier values \u200b\u200bof the device, you can enter an entry to the section CriticalDevicedatabase. Registry of the problem system, specifying that this device refers to the class of hard disk controllers. This action is easiest to complete by creating a REG file, for subsequent imports in the registry, as follows:

Windows Registry Editor Version 5.00

"SERVICE" \u003d "Intelide"
"ClassGuid" \u003d "(4D36E96A-E325-11CE -BFC1-08002BE10318)"

Windows devices are divided into classes, for example - a class of video devices, printers, modems, network adapters, etc. Any device should belong to some class. Each class is identified by its unique class identifier or GUID - A global unique identifier. List of classes standard devices Windows is given
The name of the registry key pCI # Ven_8086 & Dev_7111 Corresponds to the PNP identifier of our hard drive controller, and the value Classguid. Indicates that the device with data PNP identifier belongs to the class of hard disk controllers (HDD). The class identifier is written in the form of 32 hexadecimal digits concluded with curly brackets. After adding such an entry into the registry, the system bootloader will be able to determine that the device with Vendor / Device IDequivalent 8086/7111 It is a HDD controller, and will load a standard driver for it. intelide.. Stop7B errors will not be.

& NBSP & NBSP In order not to type this data manually, you can use the contents of the PNPID.reg file, which I placed in the archive of the utility. You can edit its contents using the ERDC notepad ("Start" - "NotePad")
It is necessary to correct the PNP identifier to the one that will be obtained using the Advanced PCI Info utility or the DevManView utility. The "Service" string determines the driver that will serve the device. The driver file must exist in the catalog \\ Windows \\ System32 \\ Drivers and be workable. The "ClassGuid" string should specify the device with the PNP-ID data to the class of hard drive controllers.

The beginning of the PNPID.REG file has been added to the use of the standard or most common drivers. If the records for the necessary PNP-ID are not available - it will have to add it, or to correct the existing one.

To check the availability of drivers in the system, you can use the services and drivers as part of the ERD Commander. Starts through the "Start" menu - "Administrative Tools" - "Service and Drivers Manager"

To import data into the registry of a problem system, launch the ERDC registry editor through
Start - Administrative Tools - Regedit
In the ERD Commander environment, the registry editor will not work with the register of the ERDC itself, but with the registry of the system that we connected in the login window when loading ERD Commander. Import will be performed in the registry of the unguarded system and, when rebooting, a new hard disk controller will be properly identified as the hard disk controller.

In the PNPID.reg file mentioned above, there are entries for adding standard drivers pciide.sys., intelide.sys., aTAPI.SYS.. These files and file pciidex.sys must be present in the driver catalog \\ Windows \\ System32 \\ Drivers. Usually, with a standard installation, they are present there. If not - you can take from the distribution or from the catalog similar to the OS.

Fixing STOP 7B error for Windows Vista operating systems, 7,8,10

Usually, the "Blue Death Screen" with the error code of the STOP 0x0000007B "Inaccessible_Boot_Device" with the standard Windows settings is not displayed, and the system performs an automatic reboot by a critical error. For Windows 7-10 operating systems, in the overwhelming majority, the problem of the STOP 7B critical error when replacing the motherboard or changing the hard disk controller mode, is solved easier than in the case of Windows XP. Usually HDD controllers are correctly recognized as hard drive controller class devices, but often standard drivers are either disabled, or the start-up mode is set for them. after Completion of download. The driver start sequence is determined by the parameter Start.stored in the registry for each of them. To initialize the driver during the download process, this parameter must be equal 0 . As part of the modern Windows OS, there is almost always a set of drivers providing standard work with hard drive controllers as in advanced mode Ahci.and standard IDE, but parameter Start. For them, it is 3-4, i.e. The driver starts manually (Start is 3) or disabled (Start is 4).

An example of recording in the registry for the SATA AHCI standard SATA controller driver msahci. With parameters that are created during the installation process of Windows7 (Registry section HKLM \\ System \\ Current Controlset \\ Services \\ MSAHCI):

"Group" \u003d "SCSI Miniport"

"ImagePath" \u003d \\ SystemRoot \\ System32 \\ Drivers \\ MsaHCI.sys

"ErrorControl" \u003d DWORD: 00000003

"Start" \u003d DWORD: 00000004

"TYPE" \u003d DWORD: 00000001

Starting with Windows 8 standard SATA AHCI controller has a name storahci. Therefore, you need to work with the section

Set of standard SATA AHCI parameters microsoft Driver (Microsoft Standard Sata Ahci Driver) may differ in different versions Windows, however, the parameter Start. It is mandatory for everyone without exception, the component of the drivers stored in the Windows registry. Value Start. Determines at which stage of the download and operation of the system will be downloaded by each specific driver. As mentioned above, the driver has a parameter Start. Equal zero is loaded with the initial loader.

As you can see, in the example, the parameter Start. Raven 4 - What does that mean that the driver is disabled. Even with the operationable device and the availability of the driver installed in this system, the bootloader will not be able to run it, since it only downloads drivers with the START parameter equal to zero, and the system will end with the "Blue Death Screen" STOP 0x0000007B "Inaccessible_Boot_Device". Even if the driver is not disabled, but its start mode will be set to, for example, "automatically" or "manually" further Windows loading is not possible. It is for this reason that the STOP 7B critical error occurs most often when changing motherboards on computers with relatively new versions of Windows. If you have in the system standard SATA AHCI driver from Microsoft, it is not possible to start the bootloader if the driver from the manufacturer has been installed before replacing the motherboard, and the standard has been turned off, or its start-up mode is changed. However, Driver. msahci.sys. For Windows 7 or storahci.sys. For Windows 8 and older, will be successfully loaded if its parameter Start. It is equal to 0 . Therefore, in order to get rid of the Stop 7B critical error in the overwhelming majority of cases of replacing Motherboard computers running Windows 7 and later, it suffices to change the parameter Start. Standard aHCI drivers. If the system could be downloaded, at least in safe mode, then such a task would have decided without the slightest effort, but an error Stop 7b. It occurs much earlier than initialization will begin. safe mode (like any other). That is, change the parameter Start. The registry of the problem Windows needs to be performed from any other system. It is quite easy to perform using the Windows PE-based emergency recovery registry editor and in particular, using the same ERD Commander (MS DART). In cases where there is a boot disk or flash drive of MS DART (7.0-10) of the corresponding Windows used, you can even do without registering the startup type Boot (Bootable) For Driver msahci. or Driver storahci. Through the Computer Management menu, and the SERVICE AND DRIVER MANAGER section. You can use the registry editor in the MS DART environment by setting the parameter value Start.equal 0 .

To enable driver loading mode, for example msahci.You can do without MS DART (ERD Commander), for which it is enough to boot into any OS with the ability to edit registry, for example, in Windows PE from a CD or flash drive. You can even temporarily connect a disk with problem Windows to the work computer and manually correct the Start parameter using the usual registry editor regedit.exe

Standard editor windows registry Allows you to work not only with the data of the "own" registry, but also to process files that are the register of another operating system. For this

Load in another operating system with the possibility of launching the registry editor.
- Run the registry editor.
- On the left side of the window where the registry tree is displayed, click on the HKEY_LOCAL_MACHINE section.
- On the menu Registry (Registry) (In other versions of the registry editor, this menu item may be called " File") Select the command "Load a bush (Load Hive)".
- Choose a bush system. On the disk from the unguarded Windows (file named system. Without expansion, which is located in the \\ Windows \\ System32 \\ Config folder).
- Press the button Open.
- In field Section Enter a temporary name that will be assigned to the loaded bustle in the registry editor tree. For example, 123 .
After clicking OK.Select a section with assigned name 123 And find the subsection \\ System \\ ControlSet00x \\ Services \\ MSAHCI In the case of "repair" blue windows screen 7 I. \\ System \\ ControlSet00x \\ Services \\ Storahci In the case of Windows 8-10. As ControlSet00x, you need to select a section with a maximum value. x.. If the registry key connected to the editor is ControlSet001 and ControlSet002, then you need to edit the driver parameters in the section \\ System \\ ControlSet002 \\ Services \\ MSAHCI

After changing the parameter Start.In the left side of the registry editor window, select the connected bush ( 123 ) And run the menu item "Unload bush". The modified value of the parameter Start.equal 0 will be saved in the registry of the problem windows.

In cases where you enable the driver start mode msahci. or storahci. Windows loader did not allow to get rid of the blue screen Stop 7b., you can try to set the parameter Start. Equal zero for the following drivers:

aTAPI
ataport.
pciide.
intelide.
iastora
iASTORF.
iASTORV.

Loading a free driver is not a serious Windows problem and in reality does not affect its operation. Although to save resources and reduce loading time, unnecessary drivers are preferably not included. After the STOP 7B error is eliminated, the list of actually used drivers can be viewed in the device manager, and unnecessary - disable (Start \u003d 4) or translate to the start-up mode manually (start \u003d 3).

& NBSP & NBSP If you do not have enough qualifications to work with ERD Commander, or difficulties have arisen in defining the desired driver, you can use a very simple technique:

Loading on a new motherboard in any system where it is possible. In the extreme case, you can even temporarily install Windows into another section or another drive connected to this HDD controller. After that you need to export to the content file

HKEY_LOCAL_MACHINE \\ SYSTEM \\ CURRENTCONTROLSET \\ CONTROL \\ CRITICALDEVICEDATABASE

The content of this section will give a list of PNP identifiers, among which the one that corresponds to the controller will be present. HDD installed Systems.

Also, you can determine which drivers are serviced by a hard disk controller.

Loading to ERDC and import data from the previous paragraph, a file in the registry of the problem system. In the case of using MSAHCI.SYS drivers, storahci.sys, IASTOR ... for Windows 7-10, you need to check or change the parameter Start.

After the STOP7B error is eliminated, additionally installed system You can delete, after adjusting the system boot loader by default, Windows corrected.

And, quite simply solves the problem, if you have the opportunity to get exported data CriticalDevicedatabase. from the operating system of another computer with the same motherboard, rather, even with the same PNP identifier of the hard disk controller. If in the BIOS settings for the same motherboards, a different mode of operation of the controllers is installed, for example, on one AHCI, and on the other IDE, they will have different PNP identifiers, and serviced different drivers.

To transfer the PNP identifier list, it is enough to simply perform the import of this data into the Problem Windows registry and the STOP7B error will be eliminated if the problem has been caused by the HDD controller recognition. If the problem is caused by the START parameter, you can get a list of driver files similar working windowsserving this controller using the usual device manager - "Properties" - "Driver" - Press the "Details" button

In this example, the hard disk controller is served by drivers aTAPI.SYS., ataport.sys., msahci.sys. and pciidex.sys.. Not all drivers listed in the list can have entries in the Registry section HKLM \\ SYSTEM \\ CURRENTCONTROLSET \\ SERVICES, for example, in this case, a sign of Start, equal to 0, should be msahci. and aTAPIAnd the rest are loaded as an addition to them. The presence of a non-zero parameter START for any driver, from the list listed in the list, will result in the "blue screen of death"

Fix STOP 7B error when transferring a system to virtual machines.

In cases where, for example, to transfer the saved configuration of a real computer to a virtual machine, as a rule, the same problem arises the "blue screen of death". STOP 0x0000007B "incaccessible_boot_device". The cause of the error, as in the case of the replacement of the motherboard, is the impossibility of correctly identifying the hard disk controller and download the driver you need. This situation often occurs when in the VMware Workstaion or Oracle VM Virtualbox or Oracle VM VirtualBox, you need to restore the status of a real computer from the images of Aomei Backupper or Acronis True Image in the form of a virtual machine. Usually, in such cases a new virtual machine with an empty disk is created, and the CD / DVD drive is used as the loading device (for example, the Acronis True Image image). The recovery image is connected either as a removable USB disk, or by local network. Recovery is performed in the same way as on real equipment, but with a large probability, the download of the virtual machine will end the stop error STOP 0x0000007B "incaccessible_boot_device". The situation is quite predictable, however, having a simpler decision due to the fact that the virtualization system emulates virtual hard A disk with a predetermined defined PNP identifier. So, for example, Oracle VM VirtualBox, the default creates a virtual SATA disk:

In addition, in the VirtualBox environment, the standard Intel - PIIX3 or ICH9 chipsets are emulated, which allows you to prepare the corresponding REG files to correct the STOP 7B error for the specified chipsets. In the VMWare Workstation environment, virtual discs can be emulated as SATA, SCSI or IDE. By default, SCSI is used. Just as in the case of the use of real hard drive controllers for the VMware Workstation environment, you can use standard Microsoft drivers for IDE - "Intel (R) 82371AB / EB PCI Bus Master Ide Controller" (Intelide.sys), for SATA - "Standard SATA AHCI CONTROLLER "(MSAHCI or STORAHCI depending on the version of Windows) and for SCSI -" LSI Adapter, SAS 3000 Series, 8-Port WITH 1068 ". You can refine information about disk devices used by the virtual machine using the utility mentioned earlier. DevmanView.exe.:

In the general case, the problem with the STOP 7B error when transferring a real computer to a virtual machine, you can decide by adding all the emulated hard drive controllers to the list of critical devices and turning on the download of all standard drivers that ensure the hard disk operation.

Eliminating STOP 7B errors using Acronis Universal Restore.

Acronis Universal Restore. Finds and installs drivers for devices needed to start the operating system restored on new equipment. Practically, Acronis Universal Restore allows you to perform in several clicks most of the actions to eliminate the STOP 7B critical error, which have been described above. Before applying Universal Restore to the operating windows systemYou must prepare a set of drivers for a new hard drive controller and chipset (motherboard chipset). These drivers are critical to run the operating system. Driver files must have INF, SYS or OEM extensions. If the drivers have been loaded in EXE, Cab or Zip formats, remove them using a third-party application, for example, a free 7-zip archiver. For large quantities computers, it is advisable to create your own repository drivers, with sorting by type of devices or hardware configurations of computers. A copy of the repository is best used on standard interchangeable media supported by practically any operating systems - on CD / DVD discs and flash drives.

ACRONIS Universal Restore for free, but only the owners of registered products can download it from the official website of the developer. Acronis Backup. And Acronis Backup Advanced. Also, at least for representatives of educational institutions, it is possible to register on the company's website and get a 30-day version of these products and including the Acronis Universal Restore as part of the Acronis Backup or Acronis Backup Advanced package. Acronis Backup versions are not compatible with the Products of the Acronis True Image line and using Universal Restore cannot be restored by the Linux family.

After loading the Acronis Universal Restore environment, the main window is displayed, conditionally divided into 3 parts:

The program displays the found Windows OS for which the recovery will be performed, and also allows you to specify the sources of driver to search for the equipment of the equipment (HARDWARE ACCESS LAYER - HAL), a hard drive controller and network adapters. If drivers are on a disk from the manufacturer or other removable media, check the box Search for removable media. If the drivers are in local or network folder, specify the path to this folder by clicking the button. Add folder.

During the work, the Acronus Universal Restore tool searches for standard folder Windows Drivers Storage (usually is a folder \\ Windows \\ inf).

Setting Install storage drivers in any case Allows you to specify specific drivers that must be installed in the system. Usually it is required if there are special hard drive controllers - SCSI, SAS, RAID, etc.

After pressing the button Add Driver You need to specify the path to the driver files and check the knack you need for a mandatory installation:

Specifying the above settings, click OK. The task is started to install the required driver system. If Acronis Universal Restore does not detect a compatible driver in the specified locations, a request will appear indicating the PNP identifier of the problem device and the proposals for the further installation - repeat the request after adding the required driver to the location of the required driver, skip it to the installation or stop work. After the task is completed on the installation of the drivers, you can change the settings of the installation and repeat the task. As a rule, on standard configurations Equipment, Acronis Universal Restore tool quickly and easily returns Windows to a working condition. After the system is loaded, other drivers are installed in a standard way.

In addition to drivers of disk subsystems, Acronis Universal Restore sets network adapter drivers. A network adapter driver will be installed without notifications if it has a digital signatures Microsoft.. Otherwise, Windows will display a standard message with a request to confirm the installation of an unsigned driver.

In conclusion, I will add that the STOP 7B error can also be caused by the equipment malfunction, damage to the logical data structure on the disk, randomly deleting driver files or records in the registry, etc. However, in reality, similar cases are extremely rare.

This guide is intended for users who would like to replace the motherboard on their computers without reinstalling the system. In particular, the article may come in handy to you if:

• you are going to upgrade your motherboard, but you want to keep the current installing Windows Together with the settings and programs without reinstalling them from the very beginning;
• you want to switch the SATA controller mode with IDE to AHCI or RAID (or vice versa) to achieve better performance disk subsystem.

If one of the above scenarios apply to you, then you should know that regardless of your goal - replacing the motherboard or switching the SATA controller to another mode - the result will be the same: "Blue Death Screen" (BSOD) with an error Stop 0x0000007B incaccessable_boot_device. When loading the operating system.

The reason for this unpleasant incident is the inability of Windows to find proper drivers for the SATA controller. Fortunately, the problem can be bypassed, thereby avoiding Windows reinstallation. To do this, you only need to "say" the operating system so that it uses the standard SATA controller driver at startup, and the registry editor can help us.

To make appropriate changes in the Windows registry, simply follow the instructions below.

Before we begin, please read the information in the two items below, since your action plan depends on one of them:

1. The replacement of the motherboard is not yet produced, so Windows is loaded normally. In this case, you need to make changes to the registry in the usual Windows working environment and only then crime to update the motherboard.

2. The operating system is not loaded, because you have already installed another motherboard, or because they changed the SATA mode in the BIOS. In this case, you will have to use the autonomous registry editor.

Changing the Registry Before updating the motherboard (Windows is loaded normally)

These instructions are only for those who have Windows starts as usual, because the motherboard is not replaced yet. If you already have another board and Windows does not boot, then follow the instructions in the next section of the article.

So, turn on the computer as usual, and then open the Windows registry editor. To do this, press + R, enter the regedit, press ENTER.

Inside the registry, proceed (in the left pane of the window) on this way:

HKEY_LOCAL_MACHINE \\ SYSTEM \\ CURRENTCONTROLSET \\ SERVICES \\ MSAHCI

In the right window pane, double-click on the parameter Start. And change its value to 0 (zero). Then click OK.

Now perform the same in the next registry branch:

HKEY_LOCAL_MACHINE \\ SYSTEM \\ CURRENTCONTROLSET \\ SERVICES \\ PCIIDE

If you use RAID (otherwise skip this step), then you need to perform the same modification in this section:

HKEY_LOCAL_MACHINE \\ SYSTEM \\ CURRENTCONTROLSET \\ SERVICES \\ IASTORV

That's all. Now your car is ready to update. Turn off the computer, install the new motherboard and connect all the necessary components to it. Then run the system, log in to the BIOS and set the ATA (IDE-ATA, AHCI or RAID) mode or leave the default value. Running Windows will have to pass without problems. When the operating system finishes the installation of the controller driver, continue the installation of drivers for the rest of the new motherboard devices.

Windows does not boot: changing the registry using an autonomous editor

Use this instruction if the operating system is not loaded because you have already replaced the motherboard, or changed the SATA controller mode in the BIOS.

In this case, you need to use the autonomous registry editor. To solve this task, I prefer to use the recovery environment where you can get, for example, using a disk to install the operating system.

To open the registry editor using the installation DVD or USB drive, perform next steps:

Load your computer using the installation disk. You may need to choose a DVD / CD or USB as the first boot device in the BIOS settings. For this:

• turn on the computer and press the DEL or F1 or F2 or F10 key to enter the BIOS (the input key in the BIOS depends on the computer manufacturer);
• inside the BIOS menu, find the BOOT ORDER parameter (this parameter is usually inside the menu Advanced Bios. Features);
• in Boot Order, select CD / DVDRW or USB (depending on what type of media is located setup files Windows) as the first boot device. Save the changes and restart the computer by pressing F10.

Restarting, the computer will start loading from the installation disk.

After loading, on the first screen, click "Next", and then select Restore System.

If you have Windows 7, in the Recovery Options window, click "Next", and on the next screen, run the command prompt.

If you are using Windows 8.x or Windows 10, then you need to select "Diagnostics" -\u003e "Advanced Settings" -\u003e "Command Line".

In the command prompt enter regedit. And press ENTER.

In the registry editor, highlight the branch HKEY_LOCAL_MACHINE , And in the "File" menu, click "Load a bush".

Open the disk on which the operating system is installed.

Go to the Windows \\ System32 \\ Config directory, select File System. And click "Open".

Enter the partition name (for example, offline) and click OK.

Using the operating system on your own computer can be very different from the user to the user. Some, having bought a new PC, mainly use the built-in in Windows Programs and tools, as well as the default OS settings. Others - work with many third-party applications and utilities, while configuring the interface of the system to its own taste.

And if in the first case, reinstalling the system and several applications is not a challenge, then in the second, in addition to the installation of the OS, you will have to register all required programs, Windows personalization and other settings. That is why many users do not burn with a desire to do it again. Especially at hand, it may not be necessary applications or their settings were performed by a specialist who will now have to be repeated.

In general, the reasons do not touch the normally working operating system can be very much, but the time comes when the internal components of your computer begin to obscure hopelessly and their replacement to a more productive iron becomes an acute necessity. And if the installation of a new power supply unit, RAM, a separate processor or video card can be made relatively painless, that is, without reinstalling the operating system, then when replacing the hard disk or motherboard, everything is not so simple.

As you understand, all Windows files are stored on a computer hard drive, so that its replacement leads to a non-re-setting system. Although, this can be avoided, after making a full backup of the current OS into the image and retaining it on old HDD Or some other media information. Then you will only stay to unpack the received backup system to a new disk, and you can continue to work in the former Windows using all previously installed programs.

In case of replacing the motherboard on a PC with Windows Result It may depend on many different factors, but the main thing is to choose a future hardware platform (for example, when changing Intel on AMD or vice versa, problems are almost inevitable) and a set of system logic (chipset). In short, the more differences will be at the new system board from the previously installed, the less chances will be loaded at the previous system after its replacement.

Despite the fact that Windows 7 has an impressive database of drivers in its arsenal, simply change their motherboard and run the previously installed system often fails. This is especially true of those boards that were released much later than the exit of the system itself. But they are now most, since since that moment has passed for more than three years. So the question is how to replace the motherboard on personal Computer With Windows without its reinstallation, is still relevant.

Why is the replacement of the motherboard so often turns along to reinstall Windows? As a rule, the most common cause is the incompatibility of the controller of hard drives already installed in the ATA / SATA drivers system with those equipped with a new "motherboard". In this case, after replacing the "iron", during the boot of the OS, you will get a blue screen of death (BSOD) with a Stop error: 0x0000007b.

The fact is that when loading, Windows simply does not have the ability to change the hard drive controller driver on their own. As a consequence, the hard drive connected to the new controller from the installed OS simply does not see the system, and its further launch becomes impossible.

To avoid such a situation, there is a pretty simple solution. Even before replacing the motherboard, run Windows, go to Device Manager, Open click on the arrow point IDE ATA / ATAPI Controllers And remove all installed devices from it.

To do this, right-click alternately on all controllers and in the context menu that opens, select Delete. If after that window appears Confirmation of device deletionTick \u200b\u200bon the point Delete drivers for this device and click OK.

In some cases, to perform the controller removal operation, the system will require a reboot. Do not do this until you walk through the entire list. Then simply turn off the computer and proceed to replace your motherboard. If you still reboot the PC, then the entire procedure will have to be done again, since Windows will restore all previously remote devices at the time of startup.

And yet, not rare cases when this method does not help you. For example, if a set of system logic (chipset) on a new motherboard will be very technologically different from the previous one. In this case, to avoid problems with the loading system, you need to get rid of all drivers that can cause them. But how to do that?

There is one very useful utility in the Windows system, which are not even advanced users know about. It is called Sysprep. and allows you to delete system data from the operating system, including information about installed hardware, as well as user installed drivers.

Thus, to ensure successful Windows load on new equipment, you must clean the OS cleaning from the old system information using this utility even before replacing the components! Also, before starting Sysprep, it is better to better remove all installed antivirus programs or disable self-defense in them. This is especially true of the products of Kaspersky Lab. Otherwise, when starting an OS with a new iron, you risk getting a message: "Windows failed to complete the system setting. To resume settings, reboot. Only no reboot will no longer help you. You have to return the old equipment in place and do everything again.

So, to start the SYSPREP utility, press the Win + R key combination and in the window that opens Perform Enter the full path to the executable file: "% windir% \\ system32 \\ sysprep \\ sysprep". For those who do not know, "% windir%" is a variable containing the path to the folder in which the system is installed, most often "C: \\ Windows". And we use it, because the location of the system folder and its name on various computers can be different.

In the window that opens, the system preparation program in the option System Cleaning Action paragraph Switch to the system greeting window (Oobe)we leave unchanged. Next, we put a tick next to the parameter Preparation for use.

In the falling menu Options for completing work Choosing a team Completion of work. This is done in order to immediately after cleaning the system, the computer did not go to the reboot, because if it does not stop it on time, the primary Windows setup process will start and you will have to repeat everything again!

After performing all these simple settings, press the OK button to start the system cleaning procedure. This process is fully automatic and after its completion, the computer must only turn off. Now you can proceed to replace the motherboard.

During the first launch of Windows with new equipment will be installed required drivers Devices and appropriate records in the operating system register. You will also have to re-enter regional standards and parameters. account.

Please note that when the OS will ask the username, the name of the old account cannot be introduced, since it already exists. Particularly upset about this is not worth it. Enter any name, and after the first login, new account You can delete and use the old one.

The only inconvenience that can expect you after downloading the system with new components - Windows re-activation. The fact is that a number of versions of this OS are attributed to the installed equipment. In particular, the most common legal windows version 7 OEM, which is installed on new desktop computers And laptops. In this case, the activation is most likely to be done by phone, as it will not be possible to do this through the Internet due to the fact that the system will make the Windows installation operation you make to another computer, which in this version is prohibited by the terms of the license agreement.

Strictly speaking, initially designed to create a configured image of Windows, in order to reuse it. That is, simply speaking, Sysprep is a utility, for cloning the prepared OS on other computers. Most often, the installation of Windows from a preformed image is carried out in organizations where the set of basic working applications for employees, for the most part, may be the same.

True, in our time there is already a situation that there is no one computer, but at once a few. For example, one desktop PC is used as a multimedia center, the other is in the child's room for learning, and the laptop is a business tool of parents. Despite the various purpose of each device, they may well have a common software: the operating system, office package, web browser, archiving, program for recording optical disks, all kinds of auxiliary utilities and much more.

In such a situation, it is convenient to have a "duty" image of the OS, from which, if necessary, you can always install the system with all the main applications. To create it, it is enough to produce once the installation of Windows and all the necessary programs on any computer, then using the SYSPREP utility, delete the system data described above. Next, you will need to burn the image of the prepared system for a separate medium: the Blu-Ray disk (the DVD simply does not have enough space), outdoor hard disk or flash drive.

The key point here is the fact that the computer loading to remove the image must be carried out with optical disk or a USB drive, but in no case from the hard disk on which it is installed. If this happens, the primary setting process will start and the entire procedure will have to be repeated again.

Prepare boot disk and save image of Windows. in the right place can be using special applications, such as Acronis True Image Home, a paid program, but with a visual graphic interface and all required tools. There are free alternatives, for example, imagex as part of the Windows PE shell. True, in this case, prepare for working with the command line.

Unpacking the image to the desired (target) computer occurs similarly to its removal using the same programs.