Submit an edit

Get the fix for the error <strong>0x0000007B(INACCESSIBLE BOOT DEVICE)</strong> on <strong>Windows XP,</strong> <strong>Windows Vista,</strong><strong> Windows 7, Windows 8 and Windows 10</strong>.
<h2>About "<strong>0x0000007B</strong>"</h2>
[kbintro]
<h3><span id="Description_and_Symptoms">Description and Symptoms</span></h3>
The error messages, alerts, warnings, and symptoms below are tied to this error.
<h3>Symptom 1: "0x0000007b" error screen on startup</h3>
When a computer is turned on, the BIOS picks an eligible, bootable hard drive and then calls code stored in the MBR at the start of that hard drive. That MBR code in turn loads the bootsector from the active partition. Then, the bootsector code loads the bootloader, which is responsible for loading the operating system. However, if the PC suddenly loses access to the system partition during startup, then the "0x0000007b" error screen is displayed and the boot process is halted.

Here is an example of "0x0000007b" error screen for Windows XP, Vista and Windows 7:

<a href="https://neosmart.net/blog/wp-content/uploads/sites/5/2014/06/0x0000007b1.png"><img class="alignnone wp-image-4446 size-full" src="https://neosmart.net/blog/wp-content/uploads/sites/5/2014/06/0x0000007b1.png" alt="0x0000007b on Windows XP, 7 and 8" width="640" height="480" /></a>
<pre>A problem has been detected and Windows has been shut down to prevent damage to your computer.

If this is the first time you've seen this Stop error screen, restart your computer. If this screen appears again, follow these steps:

Check for viruses on your computer. Remove any newly installed hard drives or hard drive controllers. Check your hard drive to make sure it is properly configured and terminated. Run CHKDSK /F to check for hard drive corruption, and then restart your computer.

Technical information:

*** STOP: 0x0000007B (0xFFFFF880009AE7E8, 0xFFFFFFFFC0000034, 0x0000000000000000, 0x0000000000000000)</pre>
On some PC's the error text may be a little different:
<pre>A problem has been detect and Windows has been shut down to prevent damage to your computer.

INACCESSIBLE_BOOT_DEVICE

If this is the first time you've seen this Stop error screen, restart your computer. If this screen appears again, follow these steps:

Check to make sure any new hardware or software is properly installed. If this is a new installation, ask your hardware or software manufacturer for any Windows updates you might need.

If problems continue, disable or remove any newly installed hardware or software. Disable BIOS memory options such as caching or shadowing. If you need to use Safe Mode to remove or disable components, restart your computer, press F8 to select Advanced Startup Options, and then select Safe Mode.

Technical information:

*** STOP: 0x0000007B (0xF8975528, 0xc0000034, 0x00000000, 0x00000000)</pre>
And here is an example of "0x0000007b" error screen for Windows 8, Windows 8.1 and Windows 10:

<img class="alignnone" src="/wiki/wp-content/uploads/sites/5/2014/06/inaccessible-boot-device-windows-8.png" alt="0x0000007b error screen in Windows 8/10" width="980" height="490" />
<pre>Your PC ran into a problem and needs to restart. We're just collecting some error info, and then you can restart. (0% complete)

If you'd like to know more, you can search online later for this error: INACCESSIBLE_BOOT_DEVICE</pre>
<h2>Causes of this Error</h2>
This error has been known to occur as a result of one of the following causes:
<h3>Cause 1: Bootloader files are missing or corrupt</h3>
One of the most common causes of this error is the boot-related files that became either missing, corrupt, or misconfigured. That could happen because of disk write errors, power outages, boot sector viruses, or errors made while configuring these files manually.
<h3>Cause 2: Incorrect BIOS configuration</h3>
the user made changes to the BIOS recently, the new settings he has entered might not be compatible with the hard drive. The UEFI/Legacy BOOT mode setting is the most infamous one in that regard, so users should take extra care when making changes to the BIOS.

Another thing that could happen is that the SATA controller has an incorrect work mode selected in BIOS. For most PC’s, there are three main SATA controller work modes available:
<ol>
 	<li>IDE is the most-basic mode that treats the SATA controller in the same way legacy IDE controllers treat ATA drives: the controller itself contains almost no read/write-related logic and simply serves as the most ascetic of bridges, simply proxying data to and from the drives.</li>
 	<li>AHCI is the more advanced and modern mode that also offers substantial optimized hardware-level read/write logic and caching, which results in a significant speed increase compared to IDE.</li>
 	<li>RAID mode that allows the user to combine multiple physical disk drivers into a single logical unit for optimized performance, redundancy, or combination thereof.</li>
</ol>
If the user’s hard drive does not support one of these modes, or if Windows was installed and booted using one mode, but a different mode was configured, then the boot process will be halted.
<h3>Cause 3: Boot sector virus</h3>
Another possible reason for this error is a boot sector virus that prevents the computer from loading. In that case, running an antivirus program that is capable of deleting boot-sector viruses may solve the issue.
<h3>Cause 4: Registry is damaged</h3>
This error may also occur after the key parts of system registry became corrupt. This usually happens after disk read/write errors, and in that case, a disk check program should be used to scan the disk for errors and fix them.
<h3>Cause 5: EFI bootloader is corrupt</h3>
The special EFI bootloader introduced in Windows 8 may also become corrupt or misconfigured. If that's the case, it should be rebuilt to fix the error.
<h2>Fixing “0x0000007b<span id="Fixing_8220Fatal_INT18_Boot_failure8221_on_Windows">” on Windows</span></h2>
[setupcd]
<h3>Fix #1: Rebuild boot files with Easy Recovery Essentials</h3>
Easy Recovery Essentials’ one-click automated system repair corrects issues caused by missing or misconfigured boot.ini and BCD by recreating them from scratch on the active bootable partition for Windows. It also checks the drive for viruses and removes them from the PC. This is done automatically as part of the automated repair process, and requires no manual action or user intervention.

[easyre guaranteed="true" error="0x0000007b" bootscreen="xp-vista-7-8-10"]
<h3>Fix #2: Check drive for viruses with Easy Recovery Essentials</h3>
If your computer is infected with a boot-sector virus, run an antivirus scan to remove all viruses from your computer to possibly fix this error.

Use any up-to-date modern antivirus scanner.

If you don't have an antivirus scanner or can't boot into Windows to run a scan, use the Virus Scanner of Easy Recovery Essentials (our recovery disk):
<ol>
 	<li><a href="https://neosmart.net/EasyRE/">Download Easy Recovery Essentials from here</a></li>
 	<li>Burn the image. <a href="https://neosmart.net/wiki/creating-a-bootable-cd-or-dvd/">Follow these instructions on how to burn the bootable ISO image</a> very carefully, as making a bootable CD can be tricky.</li>
 	<li>Boot Easy Recovery Essentials</li>
 	<li>Choose Virus Scanner</li>
 	<li><img src="/wiki/wp-content/uploads/sites/5/2013/08/EasyRE-Home.png" alt="Virus Scanner in EasyRE" /></li>
 	<li>Wait for the scan to complete</li>
 	<li><img src="https://neosmart.net/EasyRE/images/screenshots/VirusScan.png" alt="Virus Scan Complete in EasyRE" /></li>
</ol>
<h3>Fix #3: Boot into Last Known Good Configuration</h3>
Windows features a "Last Known Good Configuration" mode that can potentially fix certain issues caused by misconfigured drivers or any other corruptions.

This mode forces your system to use a previously saved version of the registry.

The instructions are:
<ol>
 	<li>Restart the computer</li>
 	<li>Tap the <kbd>F8</kbd> key repeatedly before the Windows logo appears</li>
 	<li>At the Boot Options list screen, choose <strong>Last Known Good Configuration (Advanced)</strong></li>
 	<li>Press <kbd>Enter</kbd></li>
</ol>
[caption id="attachment_4447" align="alignnone" width="980"]<a href="https://neosmart.net/blog/wp-content/uploads/sites/5/2014/06/Advanced-Boot-Options-menu.png"><img class="wp-image-4447 size-large" src="https://neosmart.net/blog/wp-content/uploads/sites/5/2014/06/Advanced-Boot-Options-menu-1024x768.png" alt="Advanced Boot Options Menu" width="980" height="735" /></a> Advanced Boot Options Menu[/caption]
<h3><span id="Fix_2_Repair_corrupted_system_files_with_the_SFC_command">Fix #4: Repair corrupted system files with the SFC command</span></h3>
On Windows Vista and Windows 7, it is possible to use the built-in Windows SFC(system file checker) tool to automatically scan a computer's system files and repair them if necessary.

Here are the steps to run SFC:
<ol>
 	<li>Boot from your Windows install disc</li>
 	<li>Click on <strong>Repair your co</strong><strong>mputer</strong> after selecting proper language, time and keyboard input.</li>
 	<li>Select the Windows installation drive, which is usually <code>C:\</code>, and click <strong>Next</strong></li>
 	<li>Choose Command Prompt when the System Recovery Options box appears</li>
 	<li>Write the following command and press <kbd>Enter</kbd> afterwards:
<pre>sfc /scannow /offbootdir=D:\ /offwindir=D:\Windows\</pre>
Replace D: with the letter of the driver where Windows is installed, and D:\Windows with the Windows folder location.</li>
</ol>
Here is an example of what the PC's console output should look like once the sfc.exe scan is complete and missing files are successfully restored:

[caption id="attachment_4233" align="alignnone" width="800"]<a href="https://neosmart.net/blog/wp-content/uploads/sites/5/2013/08/sfc_result.png"><img class="wp-image-4233 size-full" src="https://neosmart.net/blog/wp-content/uploads/sites/5/2013/08/sfc_result.png" alt="System files restored by the SFC utility" width="800" height="600" /></a> System files restored by the SFC utility[/caption]
<h3>Fix #5: Check your disk with CHKDSK utility</h3>
If the hard drive has its file integrity compromised, it is possible to use built-in Windows CHKDSK utility to scan the disk and fix the file system errors.

Here are the steps to run CHKDSK:
<ol>
 	<li>Boot from your Windows install disc</li>
 	<li>Click on <strong>Repair your co</strong><strong>mputer</strong> after selecting proper language, time and keyboard input.</li>
 	<li>Select the Windows installation drive, which is usually <code>C:\</code>, and click <strong>Next</strong></li>
 	<li>Choose Command Prompt when the System Recovery Options box appears</li>
 	<li>Write the following command and press <kbd>Enter</kbd> afterwards:
<pre>chkdsk C: /f</pre>
Replace C: with the letter of the driver where Windows is installed.</li>
</ol>
Here is an example of what the PC's console output should look like once the chkdsk.exe is complete:

[caption id="attachment_3697" align="alignnone" width="800"]<a href="https://neosmart.net/blog/wp-content/uploads/sites/5/2016/04/VirtualBox_Win7_clean_21_04_2016_03_58_48.png"><img class="wp-image-3697 size-full" src="https://neosmart.net/blog/wp-content/uploads/sites/5/2016/04/VirtualBox_Win7_clean_21_04_2016_03_58_48.png" alt="Chkdsk utility results screen" width="800" height="600" /></a> Chkdsk utility results screen[/caption]
<h3>Fix #6: <span id="Fix_1_Replace_NTLDR_and_NTDETECT046COM_files">Replace NTLDR and NTDETECT&#46;COM files</span></h3>
Windows XP users can replace the required files for NTLDR to load correctly by using your Windows Installation Disc. The files are named NTLDR and NTDETECT&#46;COM.

Here are the steps to replace these files:
<ol>
 	<li>Insert the Windows XP install CD in your CD drive</li>
 	<li>Restart the PC and boot from the CD</li>
 	<li>Press any key to boot from the CD</li>
 	<li>Press <kbd>R</kbd> after the Windows Options menu is done loading to access <strong>Repair Console</strong></li>
 	<li>After this step, log into Windows by pressing <kbd>1</kbd> using the Administrator password</li>
 	<li>Use the following commands to copy the NTLDR and NTDETECT&#46;COM files from the Windows installation disk to the hard disk:
<pre>copy D:\i386\ntldr C:\
copy D:\i386\ntdetect&#46;com C:\</pre>
Where <code>D:\</code> is the install CD’s drive letter and <code>C:\</code> is the Windows XP partition’s drive letter</li>
 	<li>Once these files are copied, remove the Windows installation disc from the disc drive</li>
 	<li>Restart the PC</li>
</ol>
Here is an example of what the PC's console output should look like once NTLDR and NTDETECT files are properly restored:

[caption id="attachment_3906" align="alignnone" width="720"]<a href="https://neosmart.net/blog/wp-content/uploads/sites/5/2013/08/NTLDR-NTDETECT-copy.png"><img class="wp-image-3906 size-full" src="https://neosmart.net/blog/wp-content/uploads/sites/5/2013/08/NTLDR-NTDETECT-copy.png" alt="Replacing ntldr and ntdetect&#46;com files" width="720" height="396" /></a> Replacing ntldr and ntdetect&#46;com files[/caption]
<h3><span id="Fix_2_Rebuild_bootini_file">Fix #7: Rebuild boot.ini file</span></h3>
The next steps to fix this error on Windows XP are to rebuild the <code>boot.ini</code> file:
<ol>
 	<li>Insert the Windows XP install CD in your CD drive</li>
 	<li>Restart the PC and boot from the CD</li>
 	<li>Press any key to boot from the CD</li>
 	<li>Press <kbd>R</kbd> after the Windows Options menu is done loading to access<strong> Repair Console</strong></li>
 	<li>After this step, log into Windows by pressing <kbd>1</kbd> using the Administrator password</li>
 	<li>Enter the following command when Command Prompt appears:
<pre>bootcfg /rebuild</pre>
</li>
 	<li>When the systems prompts about whether it should add an identified Windows installation to the boot list, answer "Y"(Yes)</li>
 	<li>Enter "Windows XP" as Load Identifier and "/fastdetect" as OS Load Options.</li>
 	<li>Remove the install CD</li>
 	<li>Restart the PC</li>
</ol>
Here is an example of what the PC's console output should look like once the boot.ini file is properly restored:

[caption id="attachment_3905" align="alignnone" width="720"]<a href="https://neosmart.net/blog/wp-content/uploads/sites/5/2013/08/Bootcfg_rebuild.png"><img class="wp-image-3905 size-full" src="https://neosmart.net/blog/wp-content/uploads/sites/5/2013/08/Bootcfg_rebuild.png" alt="Fixing Boot.ini file" width="720" height="396" /></a> Fixing Boot.ini file[/caption]
<h3><span id="Fix_2_Rebuild_bootini_file">Fix #8: Rebuild the BOOTMGR file</span></h3>
Since on newer systems, this error screen is often caused by a damaged BOOTMGR, replacing it with the correct version is often a good and effective solution.

Here are the steps to replace the BOOTMGR:
<ol>
 	<li>Boot from the Windows install disc</li>
 	<li>Click on <strong>Repair your computer</strong> after selecting proper language, time and keyboard input.</li>
 	<li>Select the Windows installation drive, which is usually <code>C:\</code>, and click <strong>Next</strong></li>
 	<li>Choose "Command Prompt" when the System Recovery Options box appears</li>
 	<li>Type in the following command and then press <kbd>Enter</kbd>:
<pre>Bcdboot C:\Windows /s D:\</pre>
Where C:\Windows is your Windows installation folder and D:\ is your active boot partition.</li>
</ol>
Here is an example screenshot of what the PC's console output should look like after the BOOTMGR is updated correctly:

[caption id="attachment_4103" align="alignnone" width="800"]<a href="https://neosmart.net/blog/wp-content/uploads/sites/5/2016/05/Win7_BcdBoot.png"><img class="wp-image-4103 size-full" src="https://neosmart.net/blog/wp-content/uploads/sites/5/2016/05/Win7_BcdBoot.png" alt="Windows 7 BcdBoot utility screen" width="800" height="600" /></a> Windows 7 BcdBoot utility screen[/caption]
<h3>Fix #9: Recover the registry</h3>
The corrupted registry may also be fixed by replacing it with a clean copy that was created on the hard drive when Windows was installed. Note that this operation will restore the system to a state that might be very far from its current state; however, it still should be possible to recover user data in that state. This procedure also should not be used if the computer has an OEM-installed operating system, because the system registry hive on OEM installations creates passwords and user accounts that did not exist previously. This means that if these steps are followed on an OEM machine, then it may not be possible to log back into the recovery console to restore the original registry hives.

First, a backup of all current registry files is made so that they could be restored if anything goes wrong. Then, the existing registry is deleted, and replaced with a clean copy from the C:\Windows\Repair folder.
<ol>
 	<li>Insert the Windows XP setup CD and restart the computer</li>
 	<li>Press any key to boot from the CD</li>
 	<li>Press <kbd>R</kbd> to access Repair Console</li>
 	<li>Enter the Administrator password. When the Command Prompt appears, type the following commands, one at a time and press <kbd>Enter</kbd> after each command, replacing <code>C:</code> with the Windows' drive letter:
<pre>md tmp
copy c:\windows\system32\config\system c:\windows\tmp\system.bak
copy c:\windows\system32\config\software c:\windows\tmp\software.bak
copy c:\windows\system32\config\sam c:\windows\tmp\sam.bak
copy c:\windows\system32\config\security c:\windows\tmp\security.bak
copy c:\windows\system32\config\default c:\windows\tmp\default.bak</pre>
[caption id="attachment_4258" align="alignnone" width="720"]<a href="https://neosmart.net/blog/wp-content/uploads/sites/5/2013/08/reg_backupfiles.png"><img class="wp-image-4258 size-full" src="https://neosmart.net/blog/wp-content/uploads/sites/5/2013/08/reg_backupfiles.png" alt="Backing up current registry hives" width="720" height="396" /></a> Backing up current registry hives[/caption]
<pre>delete c:\windows\system32\config\system
delete c:\windows\system32\config\software
delete c:\windows\system32\config\sam
delete c:\windows\system32\config\security
delete c:\windows\system32\config\default</pre>
[caption id="attachment_4259" align="alignnone" width="720"]<a href="https://neosmart.net/blog/wp-content/uploads/sites/5/2013/08/reg_delfiles.png"><img class="wp-image-4259 size-full" src="https://neosmart.net/blog/wp-content/uploads/sites/5/2013/08/reg_delfiles.png" alt="Deleting current registry hives" width="720" height="396" /></a> Deleting current registry hives[/caption]
<pre>copy c:\windows\repair\system c:\windows\system32\config\system
copy c:\windows\repair\software c:\windows\system32\config\software
copy c:\windows\repair\sam c:\windows\system32\config\sam
copy c:\windows\repair\security c:\windows\system32\config\security
copy c:\windows\repair\default c:\windows\system32\config\default</pre>
[caption id="attachment_5022" align="alignnone" width="720"]<a href="https://neosmart.net/blog/wp-content/uploads/sites/5/2014/06/reg_restorefiles.png"><img class="size-full wp-image-5022" src="https://neosmart.net/blog/wp-content/uploads/sites/5/2014/06/reg_restorefiles.png" alt="Restoring registry hives from a repair folder" width="720" height="396" /></a> Restoring registry hives from a repair folder[/caption]</li>
 	<li>Type <code>exit</code> and remove your CD:
<pre>exit</pre>
</li>
 	<li>Press <kbd>Enter</kbd></li>
 	<li>Restart your computer</li>
</ol>
Right after the boot process is completed successfully, it is possible to either backup all user data and reinstall Windows from scratch, or follow the procedure described in the <a href="https://web.archive.org/web/20150621152804/https://support.microsoft.com/en-us/kb/307545">Windows KB corrupted registry article</a> to manually restore the system registry to a more newer version that was backed up by System Restore.

For more details on Windows XP System Restore, <a title="Restore Windows XP guide" href="https://neosmart.net/wiki/windows-system-restore/#Restore_Windows_XP">go to our Restore Windows XP - Windows System Restore guide</a>.
<h3>Fix #10: Repair the EFI bootloader</h3>
Windows 8/8.1/10 feature a EFI bootloader that you repair if the commands from Rebuild the BCD don't work.

To do so, follow these steps:
<ol>
 	<li>Restart your computer and boot from the Windows DVD/USB</li>
 	<li>Click Repair your computer, then Troubleshoot, Advanced Options, and then Command Prompt</li>
 	<li>Type these commands and press Enter after each:
<pre>diskpart
sel disk 0
list vol</pre>
</li>
 	<li>Check the "Fs" column and find the item that has "FAT32" at this "Fs" column. The EFI partition is formatted under FAT32.</li>
 	<li>If, for example, the number for the EFI item is "1", type this command:
<pre>sel vol 1</pre>
</li>
 	<li>Now you need to assign a letter to the partition, a unique letter that isn't already available on your computer (for example, <code>y:\</code>):
<pre>assign letter=y:</pre>
</li>
 	<li>When this message appears - <em>DiskPart successfully assigned the drive letter or mount point</em> - type <code>exit</code> to quit the utility software
<pre>exit</pre>
</li>
 	<li>Type this command, but replace <code>y:\</code> with the letter of your choice:
<pre>cd /d y:\EFI\Microsoft\Boot\</pre>
</li>
 	<li>Type this command:
<pre>bootrec /fixboot</pre>
</li>
 	<li>Type this command to backup the old BCD:
<pre>ren BCD BCD.backup</pre>
</li>
 	<li>Type this command to recreate the BCD. Remember to replace <code>y:\</code>, if needed:
<pre>bcdboot c:\Windows /l en-us /s y: /f ALL</pre>
</li>
 	<li>Type <code>exit</code>, hit <kbd>Enter</kbd> and remove the disk from your disk tray</li>
 	<li>Restart the PC</li>
</ol>
<h3>Fix #11: Other fixes</h3>
If none of the fixes above work, try any of these tips too:
<ul>
 	<li>If you installed a new hardware piece recently, try to remove it and then restart your computer</li>
 	<li>Make sure all hard disk cables are connected properly</li>
 	<li>If you installed any device drivers, try booting into Safe Mode and uninstall that particular driver and then restart your computer. Make sure the driver is compatible with your Windows version</li>
</ul>
<h2>More Information</h2>
<h3>Linked Entries</h3>
<ul>
 	<li><a href="https://neosmart.net/wiki/bootrec/">bootrec</a></li>
 	<li><a href="https://neosmart.net/wiki/chkdsk/">chkdsk</a></li>
</ul>
[partial name="partial_moreinfo" versions="xp,vista,7,8,10,server2003,server2008,server2012"]