When you substitute laptop or server (motherboard, drive controller, and so forth.), restore a system picture from a backup or migrate a bodily host into the virtualization surroundings (P2V), the BSOD with error 0x0000007B can seem on the first time you boot Windows Server 2008 R2 or Windows 7.
STOP: 0x0000007B (0xFFFFF880009A9928, 0xFFFFFFFFC0000034, 0x0000000000000000, 0x0000000000000000).
This cease code corresponds to the INACCESSABLE_BOOT_DEVICE error and is expounded to the distinction of the onerous disk controller of a brand new server (a pc or a digital machine) from the unique tools. When booting, the driving force essential to boot from the brand new controller just isn’t loaded. Windows can’t be began as a result of it.
An administrator could encounter the error 0x0000007B within the following instances:
- When restoring an OS from a backup to a different bodily laptop or a Hyper-V / VMware / VirtualField digital machine (the restoration from Bare Metal Recovery to a different , as a person case);
- When migrating a bodily system utilizing a pc picture (created for instance utilizing disk2vhd) and deploying a brand new digital machine from this picture;
- After switching the SATA controller mode in BIOS from AHCI to IDE or vice versa;
- When changing a motherboard and/or a tough drive controller.
In my case, the issue appeared when migrating a bodily server working Windows Server 2008 R2 into VMWare surroundings. The blue display appeared on the first startup of the VM.
In the debug mode you possibly can see that Windows boot stops on the stage of loading the CLASSPNP.SYS driver.
To repair the error 0x0000007B, you should boot from any Windows set up media (with Windows 7 / 2008 R2 or larger) or a boot disk (for instance, ). If you utilize the Windows set up disk, press Shift+F10 on the primary set up display (then you definitely deciding on a language and keyboard format). The command immediate window seems, the place it’s essential to execute the command:
In the Registry Editor window, go to the registry hive HKEY_LOCAL_MACHINE and choose File -> Load Hive. On the native server drive (don’t confuse it with the WinPE disk), choose the file WindowsSystem32configSYSTEM. This file shops the system a part of the registry your native Windows copy.
Thus, you’ll mount (for instance, beneath the title local_hkey) the registry hive of your system from the onerous drive to the registry editor.
In the loaded hive, go to registry key HKEY_LOCAL_MACHINElocal_hkeyControlSet001providers.
Find these registry keys:
Find REG_DWORD parameters with the title Start in every of those keys and change their values to zero (0x00000000).
If you had switched your SATA controller mode to AHCI earlier than this error appeared, you also needs to set Start = zero within the msahci part.
Note. The Start=zero worth signifies that the service will begin at Windows startup. Start=three signifies that the service will probably be began manually.
To save the adjustments within the native registry file on the disk, go to the registry key HKEY_LOCAL_MACHINElocal_hkey and choose Unload Hive within the menu.
Now you possibly can restart your server. Windows ought to boot usually. It will search and set up drivers on your new drive controller.
In case of VMWare, you’ll simply have to put in VMWare Tools.
If after these adjustments your Windows nonetheless returns the identical error INACCESSABLE_BOOT_DEVICE when booting, it means you might be utilizing another kind of the disk controller. Try to alter the worth of the Start parameter in HKEY_LOCAL_MACHINElocal_hkeyControlSet001providers in accordance with the desk under.
|Windows Service Name||VMWare Virtual Machine||Physical PC Running Windows x64 with Native SATA Adapter||Physical PC with RAID Controller|