Windows 7 / Getting Started

Stop 0x7B or INACCESSIBLE_BOOT_DEVICE

The Stop 0x7B message indicates that Windows has lost access to the system partition or boot volume during the startup process. Installing incorrect device drivers when installing or upgrading storage adapter hardware typically causes Stop 0x7B errors. Stop 0x7B errors could also indicate a possible virus infection.

Interpreting the Message

This Stop message has four parameters:

  1. The address of a Unicode string data structure representing the Advanced RISC Computing (ARC) specification name of the device at which you attempted startup.
  2. Pointer to ARC name string in memory.
  3. This value is 0x00 (zero).
  4. This value is 0x00 (zero).

The first parameter typically contains two separate pieces of data. For example, if the parameter is 0x00800020, 0x0020 is the actual length of the Unicode string and 0x0080 is the maximum ARC name string length. The next parameter contains the address of the buffer. This address is in system space, so the high-order bit is set.

If the file system is unable to mount the boot device or simply does not recognize the data on the boot device as a file system structure, the following parameter definition applies:

  1. The address of the device object that could not be mounted.
  2. Error code value or 0x00 (zero).
  3. This value is 0x00 (zero).
  4. This value is 0x00 (zero).

The value of the first parameter determines whether the parameter is a pointer to an ARC name string (ARC names are a generic method of identifying devices within the ARC environment) or a device object because a Unicode string never has an odd number of bytes, and a device object always has a Type code of 0003.

The second parameter is very important, because it can indicate whether the Stop 0x7B message was caused by file system issues or problems with storage hardware and drivers. Values of 0xC000034 or 0xC000000E typically indicate:

  • Disks or storage controllers that are failing, defective, or improperly configured.
  • Storage-related drivers or programs (tape management software, for example) that are not fully compatible with Windows.

Resolving the Problem

The following suggestions are specific to Stop 0x7B errors. For additional troubleshooting suggestions that apply to all Stop errors, see the section titled "Stop Message Checklist" later in this tutorial.

  • During I/O system initialization, the controller or driver for the startup device (typically the hard disk) might have failed to initialize the necessary hardware. File system initialization might have failed because of disk or controller failure or because the file system did not recognize the data on the boot device.
  • Repartitioning disks, adding new disks, or upgrading to a new disk controller might cause the information in the Windows Boot Manager or boot configuration data (BCD) file to become outdated. If this Stop message occurs after you install new disks to your system, edit the BCD file or adjust the Boot Manager parameters to allow the system to start. If the error occurs after upgrading the disk controller, verify that the new hardware is functioning and correctly configured.
  • Verify that the system firmware and disk controller BIOS settings are correct and that the storage device was properly installed. If you are unsure, consult your computer's documentation about restoring default firmware settings or configuring your system to auto-detect settings. If the error occurs during Windows setup, the problem might be due to unsupported disk controller hardware. In some cases, drivers for new hardware are not in the Driver.cab library, and you need to provide additional drivers to complete Windows setup successfully. If this is the case, follow the hardware manufacturer's instructions when installing drivers. Periodically check for driver and firmware updates.
  • Hard disk corruption can also cause this Stop message.
  • Problems that cause 0x7B errors might also cause Stop 0xED errors. For more information about Stop 0xED messages, see the section titled "Stop 0xED or UNMOUNTABLE_ BOOT_VOLUME" later in this tutorial.

More Info For more information about Stop 0x7B messages, see the Knowledge Base at http://support.microsoft.com/. Search the Knowledge Base using the keywords 0x0000007B, 0x7B, and Txtsetup.oem. Specifically, refer to Knowledge Base article 935806.

[Previous] [Contents] [Next]

In this tutorial:

  1. Troubleshooting Stop Messages
  2. Stop Message Overview
  3. Identifying the Stop Error
  4. Finding Troubleshooting Information
  5. Stop Messages
  6. Bugcheck Information
  7. Technical Information
  8. Debug Port and Dump Status Information
  9. Types of Stop Errors
  10. Memory Dump Files
  11. Configuring Small Memory Dump Files
  12. Configuring Kernel Memory Dump Files
  13. Configuring Complete Memory Dump Files
  14. How to Manually Initiate a Stop Error and Create a Dump File
  15. Using Memory Dump Files to Analyze Stop Errors
  16. Using Windows 7 Error Reporting
  17. Using Symbol Files and Debuggers
  18. Being Prepared for Stop Errors
  19. Record and Save Stop Message Information
  20. Check Software Disk Space Requirements
  21. Install a Kernel Debugger and Symbol Files
  22. Stop 0xA or IRQL_NOT_LESS_OR_EQUAL
  23. Stop 0x1E or KMODE_EXCEPTION_NOT_HANDLED
  24. Understanding Kernel Stack Overflows
  25. Stop 0x24 or NTFS_FILE_SYSTEM
  26. Stop 0x2E or DATA_BUS_ERROR
  27. Stop 0x3B or SYSTEM_SERVICE_EXCEPTION
  28. Stop 0x3F or NO_MORE_SYSTEM_PTES
  29. Stop 0x50 or PA GE_FAULT_IN_NONPA GED_AREA
  30. Stop 0x77 or KERNEL_STACK_INPA GE_ERROR
  31. Stop 0x7A or KERNEL_DATA_INPA GE_ERROR
  32. Stop 0x7B or INACCESSIBLE_BOOT_DEVICE
  33. Stop 0x7F or UNEXPECTED_KERNEL_MODE_TRAP
  34. Stop 0x9F or DRIVER_POWER_STATE_FAILURE
  35. Stop 0xBE or ATTEMPTED_WRITE_TO_READONLY_MEMORY
  36. Stop 0xC2 or BAD_POOL_CALLER
  37. Stop 0xCE or DRIVER_UNLOADED_WITHOUT_CANCELLING_ PENDING_OPERATIONS
  38. Stop 0xD1 or IRQL_NOT_LESS_OR_EQUAL
  39. Stop 0xD8 or DRIVER_USED_EXCESSIVE_PTES
  40. Stop 0xEA or THREAD_STUCK_IN_DEVICE_DRIVER
  41. Stop 0xED or UNMOUNTABLE_BOOT_VOLUME
  42. Stop 0xFE or BUGCODE_USB_DRIVER
  43. Stop 0x00000124
  44. Stop 0xC000021A or STATUS_SYSTEM_PROCESS_TERMINATED
  45. Stop 0xC0000221 or STATUS_IMAGE_CHECKSUM_MISMATCH
  46. Hardware Malfunction Messages
  47. Stop Message Checklist
  48. Check Your Software
  49. Use the Last Known Good Configuration
  50. Restart the System in Safe Mode
  51. Check Event Viewer Logs
  52. Install Compatible Antivirus Tools
  53. Report Your Errors
  54. Install Operating System and Driver Updates
  55. Install and Use a Kernel Debugger
  56. Check Your Hardware
  57. Check for Nondefault Firmware Settings
  58. Check for Non-Default Hardware Clock Speeds
  59. Check by Running Hardware Diagnostic Tools
  60. Check for SCSI Disk and Controller Settings
  61. Check Memory Compatibility
  62. Check by Temporarily Removing Devices
  63. Check by Replacing a Device