Microsoft KB Archive/113573

= STOP Message 0x0000007B Problems with Second SCSI Controller =

Article ID: 113573

Article Last Modified on 10/31/2006

-

APPLIES TO


 * Microsoft Windows NT Advanced Server 3.1
 * Microsoft Windows NT Workstation 3.1
 * Microsoft Windows NT Advanced Server 3.1

-



This article was previously published under Q113573



SYMPTOMS
After you add a second SCSI controller and reboot the computer, the following STOP error message appears:

STOP: 0x0000007B INACCESSIBLE BOOT DEVICE



CAUSE
Windows NT is loading the recently added SCSI controller (miniport) before the previously installed SCSI boot controller.



RESOLUTION
WARNING: Using the Registry Editor incorrectly can cause serious, system- wide problems that may require you to reinstall Windows NT to correct them. Microsoft cannot guarantee that any problems resulting from the use of the Registry Editor can be solved. Use this tool at your own risk.

The configuration settings that control SCSI miniport load order are in the registry in the key(s):   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\"DeviceName" These values determine how the SCSI device loads:  - Start:REG_DWORD:0   Value of 0x0 for autostart, 0x4 for disabled - Tag:REG_DWORD:0xC   Determines load order of SCSI miniport drivers - Type:REG_DWORD:0x1  0x1 (device driver) Here is how to adjust the load order of SCSI miniport drivers:


 * 1) If you are getting a STOP message, reboot using the last known good configuration.
 * 2) Load the second SCSI driver using Windows NT setup.
 * 3) Before rebooting, open the Registry using REGEDT32 and edit the keys that apply to your SCSI controller. Make sure the Tag value for the SCSI boot controller has a lower value than the recently added controller. Swapping the two existing values avoids conflicts with other controllers.
 * 4) Shutdown and restart Windows NT.

