BSOD Error 0x0000007B on Boot on Windows Server 2008 R2 How to fix

Problems with device drivers , viruses, data corruption, generally triggers Windows error 0x0000007B.
Here at Ibmi Media, as part of our Server Management Services, we regularly help our Customers to solve Windows related errors.
In this context, we shall look into the main causes of this error and how to get rid of it.

More information about Windows error 0x0000007B?

Sometimes, in the process of booting up a Windows Server 2008 R2 for the first time after a hardware replacement or system image restore, you may see an error message as shown below;

STOP: 0x0000007B (0xFFFFF880009A9928, 0xFFFFFFFFFC0000034, 0x0000000000000, 0x00000000000).

This stop code corresponds to the INACCESSABLE_BOOT_DEVICE error and is related to the difference of the hard disk controller of a new server (a computer or a virtual machine) from the original equipment.
In the process of booting booting, the driver necessary to boot from the new controller is not loaded.

What triggers Windows error 0x0000007B?

Below are the common causes for the error 0x0000007B are;
i. When restoring an OS from a backup to another physical computer or a Hyper-V/VMware/VirtualBox virtual machine.
ii. When migrating a physical system using a computer image  and deploying a new virtual machine from this image.
iii. After switching the SATA controller mode in BIOS from AHCI to IDE or vice versa
iv. When replacing a motherboard and/or a hard drive controller.

In this case, the problem appeared when migrating a physical server running Windows Server 2008 R2 into VMWare environment. The blue screen appeared at the first startup of the VM.
In the debug mode you can see that Windows boot stops at the stage of loading the CLASSPNP.SYS driver.

How to fix Windows error 0x0000007B?

If the error message just triggered after we installed or made a change to a hard drive controller, you may fix it by Undoing the change.
Depending on the changes we made, some solutions might include:
i. Removing or reconfiguring the newly installed hard drive controller
ii. Starting up with Last Known Good Configuration to undo related registry and driver changes
iii. Using System Restore to undo recent changes
iv. Rolling back the hard drive controller device driver to the version prior to the driver update

Another solution is to verify that the SCSI chain is correctly terminated, assuming that we are using SCSI hard drives in the computer. Incorrect SCSI termination has been known to cause STOP 0x0000007B errors.
Additionally, it is also important to verify that the hard drive is properly installed. An improperly installed hard drive could cause this error.

Make sure you scan the computer for viruses. Certain malware that infects the master boot record (MBR) or boot sector can cause STOP 0x0000007B errors.
Also make sure that the virus scanning software is updated and configured to scan the MBR and boot sector.

Another solution is to update the drivers for the hard drive controller. If the drivers to the hard drive controller are outdated, incorrect, or corrupted, the STOP 0x0000007B error will likely occur.

How to Change the SATA mode in BIOS to IDE mode?

Disabling some of the advanced features of SATA drives in BIOS could stop the STOP 0x0000007B error from showing up, especially if we are seeing it in Windows installation.
Depending on the BIOS make and version, SATA mode may be referred to as AHCI mode and IDE mode may be referred to as either Legacy, ATA, or Compatibility Mode.

While not a common solution, we might also want to try the reverse: see if IDE mode is selected in BIOS and if so, change it to AHCI, especially if we see the STOP 0x0000007B error in Windows.

If we see this STOP error after making the BIOS change on a Windows computer, we might need to enable the AHCI disk driver.

How to run chkdsk on the hard drive?

If the boot volume is corrupted, the chkdsk command might repair the corruption.
We will likely have to run chkdsk from the Recovery Console.
This will likely be the solution if the second hexadecimal number after the STOP code is 0xC0000032.

Another option here is to run the fixmbr command to create a new master boot record. A corrupted master boot record might be causing the STOP 0x0000007B error.
This will likely be the solution if the second hexadecimal number after the STOP code is 0xC000000E.

Additionally, it is also a good option to clear the CMOS. Sometimes the STOP 0x0000007B error is caused by a BIOS memory issue. Clearing the CMOS could solve that problem.

Another option is to update the BIOS. In some situations, an outdated BIOS could cause this error due to incompatibilities with a hard drive controller.
Also, update the hard drive controller's firmware if possible. Just as with the BIOS in the previous step, an incompatibility could be causing the 0x7B error and a firmware update from the manufacturer may correct the problem

[Need urgent support in fixing windows error 0x0000007B? – We are available 24*7]


This article will guide you on how to fix Windows error 0x0000007B which generally occurs due to a number of reasons like issues with device drivers , viruses, and data corruption.

For Linux Tutorials

We create Linux HowTos and Tutorials for Sys Admins. Visit us on

Also for Tech related tips, Visit or General Technical tips on