Troubleshooting stop 0x7B and stop 0xED.

As Carrona.org says:

[FONT=&quot]STOP 0x0000007B: INACCESSIBLE_BOOT_DEVICE [/FONT][FONT=&quot]STOP 0x000000ED: UNMOUNTABLE_BOOT_VOLUME [/FONT]Troubleshooting stop 0x7B and stop 0xED are different from those other bugchecks, because crash dumps are not obtained in these two cases, as there two bugchecks don’t allow to computer to boot up; neither in normal mode nor in safe mode. And that is why specific troubleshooting strategy is required for those cases.[FONT=&quot]What may resist the access to the boot files? If we list the possibilities up, out job becomes sort of easier. So let us list those possibilities up. [/FONT]

1. [FONT=&quot]Changed storage/SATA controller mode;[/FONT]
2. [FONT=&quot]Boot sequence error;[/FONT]
3. [FONT=&quot]File system problem;[/FONT]
4. [FONT=&quot]A problematic device driver;[/FONT]
5. [FONT=&quot]Virus infection;[/FONT]
6. [FONT=&quot]Improper boot parameters; and[/FONT]
7. [FONT=&quot]Hard drive failure.[/FONT][FONT=&quot]
   * If the HDD is not failing, then the easiest way to solve these two BSODs is to perform a Clean Reinstall.
   [/FONT]
   • Clean Install Windows 7
     
   • Clean Reinstall - Windows 7
   [FONT=&quot]
   [/FONT]

[FONT=&quot]Let us discuss them in detail.
[/FONT]





[FONT=&quot]Generally there are three possible storage controller modes available, viz[/FONT]

• [FONT=&quot]IDE/ATA/SATA[/FONT]
• [FONT=&quot]AHCI[/FONT]
• [FONT=&quot]RAID[/FONT]

[FONT=&quot]Windows boots using the storage controller mode on which it is originally installed. So, if by any chance the storage controller mode is changed to something other, then it will refuse to boot up. [/FONT]
[FONT=&quot]In this case, boot into the BIOS setup. Notice very minutely what is set as the controller mode, and remember it*. Now apply the other mode available. Save the change and exit from BIOS setup. [/FONT]
[FONT=&quot]Now try to boot to the computer. If it still does not boot, apply the other remaining mode. See how it goes.[/FONT]

[FONT=&quot]If windows fail to boot with all the available storage controller modes, then storage controller is not the reason behind the issue. Apply the initial mode back (that you need to remember* properly) and shift to the next possibility.
[/FONT]




If the HDD/SSD containing the boot files is not accessible due to boot sequence error, that is also to be rectified within BIOS setup.





The file system on the HDD also may cause such a BSOD. Disc Check Commands are useful to detect those problems and attempts for possible recovery.

1. Open a Command Prompt at Boot.
2. Run Chkdsk from Command Prompt (Option Two of How to Run Disk Check in Windows 7)

For switches, /r and /f are recommended.





It may be very hard in this case where windows refuses to boot. But if it is anyhow to possible to boot to System Recovery Options, then it may be attempted to detect the failing device driver.
Boot to System Recovery Options . Try Safe Mode with Command Prompt. In the command prompt .... enter the command ....

• start msconfig

It will open the system configuration window, with the "general" tab selected.

• Click the "startup" tab. Click "Disable all" > Apply > OK.
• Click on "services" tab. Check the "Hide all Microsoft Services"; Click "Disable all" > Apply > OK

Then try to boot again normally. Is it failing still?

If so, boot to System Recovery Options once again. Try Enable Boot Logging. It will create a file named ntbtlog.txt. Collect it and upload it. If you cannot do it within windows, Boot with a live Linux disc and collect it in a USB stick, use the usb stick in another computer and upload it. Some of the members of the SevenForums will check your upload and guide you to the next.





A virus or a malware, a rootkit or a bootkit (boot sector virus) may cause such a BSOD. In this case it is needed to scan the system with a bootable virus scanner.

There are a few of such scanners available. Windows Defender Offline is a good one to do this job.




It may be seen that the boot files are not accessible because the right partition is not marked as active. To know the partitions and flags, it is best to use the Partition Wizard bootable CD.

In this case what is needed to do is ….

1. If the 100 MB System Reserved partition is not a primary partition, convert the System Reserved Partition to a primary partition
2. Mark the System Reserved partition as active
3. Run Startup Repair for three separate times, with restarts in between every single run to recreate the boot files in that location. (http://www.sevenforums.com/tutorials/105541-startup-repair-run-3-separate-times.html)

A failing hard drive is the most common cause of a stop 0x7B or a stop 0xED BSOD. In order to detect it, a bootable disc check tool is needed.

Seatools for DOS is the best way to test the HDD in such a situation.
It is better to take the long test using Seatools For DOS.

If errors are detected, the HDD is needed to be replaced.

​