Knowledge Base

How to troubleshoot "Stop 0x0000007B" error messages in Windows 2000

Article ID: 822052

Article Last Modified on 1/30/2007

APPLIES TO

Microsoft Windows 2000 Server
Microsoft Windows 2000 Advanced Server
Microsoft Windows 2000 Professional Edition

Important This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows registry

SUMMARY

This article describes how to troubleshoot "Stop 0x0000007B" error messages that may occur on your Microsoft Windows 2000-based computer. In certain situations, you may receive an error message that is similar to the following on a blue screen on your Windows 2000-based computer:

- - STOP 0x0000007B (parameter1, parameter2, parameter3, parameter4)

INACCESSIBLE_BOOT_DEVICE

The "Stop 0x0000007B" error message is a Windows 2000 Executive character-mode Stop error message. It can be caused by various issues. It may indicate that either a failure occurred during input/output (I/O) system initialization when the driver for the boot device initializes the device that Microsoft Windows is trying to start from, or that the file system did not initialize because it did not recognize the data that is stored on the boot device. This error message may occur in the following situations:

If Windows is installed on an unsupported disk or small computer system interface (SCSI) controller.
After the installation of a new SCSI adapter or disk controller.
When the disk was repartitioned with the system partition.

This article describes both general and specific troubleshooting steps that you can use when you receive this error message on your Windows 2000-based computer.

Note This article does not discuss how to troubleshoot "Stop 0x0000007B" error messages that occur during Windows 2000 Setup or when you install a Windows 2000 Setup. To troubleshoot "Stop 0x0000007B" error messages that may occur when you run Setup to install Windows 2000 or when you install a Windows 2000 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

822051 How to troubleshoot "Stop 0x0000007B" error messages that occur when you run Windows 2000 Setup

General troubleshooting procedures

Before you troubleshoot a "Stop 0x0000007B" error message, read the contents of this article to determine if any one of the specific issues that are listed later in this article applies to you. If they do not, use the following general troubleshooting steps:

If you recently added new hardware, remove the new hardware or reconfigure it so that it does not conflict with the resources of any other installed controllers.

If an IRQ or I/O port address conflict exists between the boot controller and another controller, Windows 2000 may display a "Stop 0x0000007B" error message. Check the Microsoft Hardware Compatibility List (HCL) to make sure that the hardware that you want to add and its drivers are compatible with Windows 2000. For more information about the HCL, visit the following Microsoft Web site:

http://www.microsoft.com/whdc/hcl/default.mspx

For information about the hardware that you want to install, contact the hardware manufacturer.
Use the Last Known Good Configuration feature. Using the Last Known Good Configuration feature may resolve the problem if you recently installed a device driver that is incompatible with your boot controller.

When you use the Last Known Good Configuration feature, you start your computer by using the most recent settings that worked. This feature restores registry information and driver settings that were in effect the last time that the computer started successfully. Use this feature when you cannot start Windows after you make a change to the computer (for example, if you install or you upgrade a device driver).

To start the computer by using the Last Known Good Configuration feature, follow these steps:
1. Restart the computer.
2. Press F8 when you receive the following message:
  
  Please select the operating system to start.
3. On the Windows Advanced Option menu, use the arrow keys to select Last Known Good Configuration, and then press ENTER.
4. If you are running other operating systems on the computer, click Microsoft Windows 2000 from the list that appears, and then press ENTER.
  
  Warning After you start your computer by using the Last Known Good Configuration feature, changes that you made since the last successful startup are lost.
  
  If you can start your computer by using the Last Known Good Configuration feature, the last change that you made to the computer (for example, the installation of a driver) may be the cause of the problem. To troubleshoot a problem, you can either remove or update the driver, and then test Windows to determine whether the problem is resolved.
Use an Emergency Repair Disk (ERD). If you have an ERD, use it to troubleshoot the problem. You can use the emergency repair process to repair the system files, the partition boot sector, and the startup environment.

For more information about the emergency repair feature, click the following article number to view the article in the Microsoft Knowledge Base:

231777 How to create an Emergency Repair Disk in Windows 2000
Read the contents of the following article in the Microsoft Knowledge Base to determine whether any one of the troubleshooting steps apply to your situation:

122926 Troubleshooting Stop 0x0000007B or "0x4,0,0,0" error

Specific troubleshooting procedures

Boot sector viruses

You may receive a "Stop 0x0000007B" error message if your computer is infected with a boot sector virus. Use an antivirus program to check your computer for viruses. Additionally, check any floppy disks for viruses before you use them again.

For more information about how to help protect the boot sector from viruses, click the following article number to view the article in the Microsoft Knowledge Base:

122221 How to protect boot sector from viruses in Windows

Microsoft does not provide software that can detect or remove computer viruses. If you suspect or confirm that your computer is infected with a virus, obtain current antivirus software. For a list of antivirus software manufacturers, click the following article number to see the article in the Microsoft Knowledge Base:

49500 List of Antivirus Software Vendors

List of specific issues

The following list contains information about specific situations where a "Stop 0x0000007B" error message may occur. Click the link or links that you want for more information about how to troubleshoot the problem:

You receive a "Stop 0x0000007B" error message when you try to start your computer after you move the dynamic hard disk
A "Stop 0x0000007B" error message occurs after you move the system disk to another computer
A "Stop 0x0000007B" error message occurs after you update the PERC2 SCSI driver on a Dell PowerEdge 2450 server
A "Stop 0x0000007B" error message occurs if you disable Diskperf when other filter drivers are loaded
A "Stop: 0x0000007B" error message occurs when you start your computer to a mirrored dynamic disk
A "Stop 0x0000007B" error message occurs when you start your computer after you install a new motherboard
A "Stop 0x0000007B" error message occurs when you convert a basic disk that contains the boot partition to a dynamic disk
Using Sysprep may result in a "Stop 0x0000007B" error message on some computers
You receive a "Stop 0x00000058 FTDISK_INTERNAL_ERROR" error message when you start your computer to a shadow drive from a broken basic mirror
A "Stop 0x0000007B" error message occurs after you remove Roxio Easy CD Creator 5 Platinum
A "Stop 0x0000007B" error message occurs when you start your computer after you install Iomega IomegaWare 3.1
A "Stop 0x0000007B" error message occurs after you install Iomega Tools
A "Stop 0x0000007B" error message occurs after you remove Veritas Open Transaction Manager

back to the top

You receive a "Stop 0x0000007B" error message when you try to start your computer after you move the dynamic hard disk

When you start your Windows 2000-based computer, you receive the following Stop error message:

STOP: 0x0000007b (0xf881b84c,0xc0000034,0x00000000,0x00000000)
INACCESSIBLE_BOOT_DEVICE

0xc00000034 STATUS_OBJECT_NAME_NOT_FOUND

Cause

This error message may occur if the primary disk group identity of the hard disk does not match the primary disk group identity that is stored in the registry. This mismatch may occur if all the following conditions are true:

You configure the hard disk that contains the system partition as a dynamic disk on a computer that is running Windows 2000.
You remove the hard disk from the computer, and then install the hard disk in a second Windows 2000-based computer.
You import the hard disk to a disk group that contains dynamic disks on the second Windows 2000-based computer.
You return the hard disk from the second computer to the first computer.

Resolution

To resolve this problem, use Registry Editor to delete the Primary Disk Group registry key from the registry of the computer that does not start. To delete this key, follow these steps.

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

Remove the hard disk that contains the system partition from the computer that does not start, install the hard disk in the second computer, and then start the second computer.
On the second computer, click Start, click Run, type regedt32 in the Open box, and then click OK.
In Registry Editor, click HKEY_LOCAL_MACHINE, and then on the Registry menu, click Load Hive.
Locate, and then click the System file that contains the hive of the first computer's operating system.

Note The System file is in the Drive:\Winnt\System32\Config folder, where Drive is the drive letter of the hard disk that is from the first computer.

Click Open, type Temp in the Key Name box, and then click OK.
Double-click HKEY_LOCAL_MACHINE, and then double-click Temp.
Double-click ControlSet00n, where n is the number of the control set.
Double-click Services, double-click dmio, and then click Boot Info.
Right-click the Primary Disk Group registry key, and then click Delete.
Repeat steps 7 through 9 for each instance of ControlSet00n that appears in the HKEY_LOCAL_MACHINE\Temp subkey.
Click Temp, and then on the Registry menu, click Unload Hive, and then click Yes.
Quit Registry Editor.
Shut down the second computer, and then remove the hard disk that is from the first computer.
Reinstall the hard disk in the first computer, and then start the first computer.

In Windows 2000, there can be only one dynamic disk group. When you move a dynamic disk from one computer to a second computer that already contains dynamic disks, the primary disk group identity on the disk is changed, and the disk is merged into the second computer's dynamic disk database. However, the primary disk group identity that is stored in the registry of the operating system on the disk is not changed. When you return the hard disk to the first computer, the mismatch between the new primary disk group identity and the primary disk group identity that is stored in the registry causes the error.

For more information about dynamic disk numbering, click the following article numbers to view the articles in the Microsoft Knowledge Base:

222470 Dynamic disk numbering and the DmDiag.exe tool

222189 Description of disk groups in Windows Disk Management

A "Stop 0x0000007B" error message occurs after you move the system disk to another computer

When you move the system (boot) disk of one Windows 2000-based computer to another computer, you may receive the following error message when you try to start the other computer:

- - STOP: 0x0000007B (0xF741B84C,0xC0000034,0x00000000,0x00000000)

INACCESSIBLE_BOOT_DEVICE

Cause

This problem occurs if the computer that you moved the system disk to uses different hardware than the original Windows 2000-based computer. For example, this problem occurs if you move the system hard disk to a back up computer that is a different model that the original computer. In this situation, the registry entries and drivers for the mass storage controller hardware in the backup computer are not installed in Windows.

There are several different chipsets that are available for integrated device electronics (IDE) controllers, and each chipset uses a different Plug-n-Play (PNP) ID to identify it. The PNP-ID information of mass storage controllers for the backup computer must be in the registry so that Windows can initialize the correct drivers when you start the computer.

Resolution

The supported method of moving a Windows 2000 installation to new hardware is documented in the following article in the Microsoft Knowledge Base:

249694 How to move a Windows 2000 installation to different hardware

However, for a disaster recovery method, do the following as appropriate for your situation:

Use the same hardware for the backup computer.
Replace the problem hardware components in the backup computer with the same manufacturer, make, and model as the components in the computer that you are backing up.
Use the same make and model of SCSI controller in the new computer, if the system disk is a SCSI disk.
If the system disk is an IDE disk, use the same type of motherboard that has the same type of IDE chipset, and the same PNP-ID as the original computer.

For SCSI-based system disks, you can prime the registry, and make sure that the drivers that you want are installed if you install the SCSI controller that is used by the backup computer before you transfer the system disk contents. Windows PNP detects the controller, sets up the critical registry entries, and then copies the appropriate driver.

After you verify that the SCSI controller appears in Device Manager, you can safely remove the alternate controller. If you have to move the system drive to another computer that has the same make and model of SCSI controller later, Windows can start successfully because it already used that controller one time and retains the correct configuration information.

Additional information

Although Microsoft does not support the following method, you can import or merge the required registry entries and copy the drivers ahead of time to support the IDE controllers that are natively supported by Windows. This method may enable system drives that you moved to start successfully. However, other hardware differences may result in other problems. This solution can provide support for IDE controllers whose PNP-ID matches the following list. However, if you want to determine ahead of time the IDE controllers that are used in your current and backup computers, you can search the %SystemRoot%\Setupapi.log file for the PNP-ID that is detected during Setup. After you determine the PNP-IDs that are used in your computers, you can choose to merge or to populate the registry with only the PNP-IDs that you need.

The following list is a list of the PNP-IDs of natively supported IDE controllers in Windows:

;***********(Standard IDE ATA/ATAPI controllers)*********
   Primary_IDE_Channel=%systemroot%\inf\mshdc.inf
   Secondary_IDE_Channel=%systemroot%\inf\mshdc.inf

   ;*********** Generic_ESDI_Hard_Disk_Controller **********
   *PNP0600=%systemroot%\inf\mshdc.inf

   ;*********** Aztech IDE Controller **********************
   *AZT0502=%systemroot%\inf\mshdc.inf
 
   ;*********** Device ID for generic Dual PCI IDE *********
   PCI\CC_0101=%systemroot%\inf\mshdc.inf

   ;************Acer Labs Inc ******************************
   PCI\VEN_10B9&DEV_5215=%systemroot%\inf\mshdc.inf
   PCI\VEN_10B9&DEV_5219=%systemroot%\inf\mshdc.inf
   PCI\VEN_10B9&DEV_5229=%systemroot%\inf\mshdc.inf

   ;************Appian Technology **************************
   PCI\VEN_1097&DEV_0038=%systemroot%\inf\mshdc.inf

   ;************CMD Technology *****************************
   PCI\VEN_1095&DEV_0640=%systemroot%\inf\mshdc.inf
   PCI\VEN_1095&DEV_0646=%systemroot%\inf\mshdc.inf

   ;************Compaq ************************************* 
   PCI\VEN_0E11&DEV_AE33=%systemroot%\inf\mshdc.inf

   ;*************Intel *************************************
   PCI\VEN_8086&DEV_1222=%systemroot%\inf\mshdc.inf
   PCI\VEN_8086&DEV_1230=%systemroot%\inf\mshdc.inf
   PCI\VEN_8086&DEV_7010=%systemroot%\inf\mshdc.inf
   PCI\VEN_8086&DEV_7111=%systemroot%\inf\mshdc.inf
   PCI\VEN_8086&DEV_2411=%systemroot%\inf\mshdc.inf
   PCI\VEN_8086&DEV_2421=%systemroot%\inf\mshdc.inf
   PCI\VEN_8086&DEV_7199=%systemroot%\inf\mshdc.inf

   ;*************PC Technology *****************************
   PCI\VEN_1042&DEV_1000=%systemroot%\inf\mshdc.inf

   ;*************Silicon Integrated System *****************
   PCI\VEN_1039&DEV_0601=%systemroot%\inf\mshdc.inf
   PCI\VEN_1039&DEV_5513=%systemroot%\inf\mshdc.inf

   ;*************Symphony Labs *****************************
   PCI\VEN_10AD&DEV_0001=%systemroot%\inf\mshdc.inf
   PCI\VEN_10AD&DEV_0150=%systemroot%\inf\mshdc.inf

   ;*************Promise Technology ************************
   PCI\VEN_105A&DEV_4D33=%systemroot%\inf\mshdc.inf

   ;*************VIA Technologies, Inc. ********************
   PCI\VEN_1106&DEV_0571=%systemroot%\inf\mshdc.inf

To import this information, follow these steps on two different test computers that display the "Stop 0x0000007B" error message after you change drives between computers. After you follow these steps on each test computer, you should be able to move the hard disks and start both computers without receiving the error message. However, note that other hardware differences may result in other issues. To do this, follow these steps:

Copy the following information into Notepad, and then save the file to a floppy disk as Mergeide.reg.

Note Make sure that you save the file by using a .reg extension and not a .txt extension.

********* START COPY FROM HERE ************* 

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\primary_ide_channel]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="atapi"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\secondary_ide_channel]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="atapi"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\*pnp0600]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="atapi"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\*azt0502]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="atapi"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\gendisk]
"ClassGUID"="{4D36E967-E325-11CE-BFC1-08002BE10318}"
"Service"="disk"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#cc_0101]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_0e11&dev_ae33]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1039&dev_0601]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"


[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1039&dev_5513]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1042&dev_1000]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_105a&dev_4d33]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1095&dev_0640]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1095&dev_0646]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1097&dev_0038]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_10ad&dev_0001]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_10ad&dev_0150]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_10b9&dev_5215]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_10b9&dev_5219]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_10b9&dev_5229]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1106&dev_0571]
"Service"="pciide"
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_1222]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_1230]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_2411]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_2421]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_7010]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_7111]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_7199]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"

;Add driver for Atapi (requires atapi.sys in drivers directory)

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\atapi]
"ErrorControl"=dword:00000001
"Group"="SCSI miniport"
"Start"=dword:00000000
"Tag"=dword:00000019
"Type"=dword:00000001
"DisplayName"="Standard IDE/ESDI Hard Disk Controller"
"ImagePath"=hex(2):53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,44,00,\ 
  52,00,49,00,56,00,45,00,52,00,53,00,5c,00,61,00,74,00,61,00,70,00,69,00,2e,\ 
  00,73,00,79,00,73,00,00,00

;Add driver for intelide (requires intelide.sys in drivers directory)

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\IntelIde]
"ErrorControl"=dword:00000001
"Group"="System Bus Extender"
"Start"=dword:00000000
"Tag"=dword:00000004
"Type"=dword:00000001
"ImagePath"=hex(2):53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,44,00,\ 
  52,00,49,00,56,00,45,00,52,00,53,00,5c,00,69,00,6e,00,74,00,65,00,6c,00,69,\ 
  00,64,00,65,00,2e,00,73,00,79,00,73,00,00,00


;Add driver for pciide (requires pciide.sys and pciidex.sys in drivers directory)

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PCIIde]
"ErrorControl"=dword:00000001
"Group"="System Bus Extender"
"Start"=dword:00000000
"Tag"=dword:00000003
"Type"=dword:00000001
"ImagePath"=hex(2):53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,44,00,\ 
  52,00,49,00,56,00,45,00,52,00,53,00,5c,00,70,00,63,00,69,00,69,00,64,00,65,\ 
  00,2e,00,73,00,79,00,73,00,00,00
                        
************ END COPY HERE ***************

Extract the Atapi.sys, the Intelide.sys, the Pciide.sys, and the Pciidex.sys files from the %SystemRoot%\Driver Cache\i386\Driver.cab file, or copy them to the %SystemRoot%\System32\Drivers folder from the most-recently installed service pack distribution media if the service pack is already installed on your computer.
In Microsoft Windows Explorer, right-click the Mergeide.reg file that is located on floppy disk drive, and then click Merge.
Click Yes when you are prompted to confirm that you want to add the information in the Mergeide.reg file to the registry.
Shut down the computer, and then move the system disk drive to the other test computer where you received the "Stop 0x0000007b" error message, and then start the other test computer.

A "Stop 0x0000007B" error message occurs after you update the PERC2 SCSI driver on a Dell PowerEdge 2450 server

When you update the drivers for your SCSI controller from the Microsoft Windows Update Web site, you may receive a Stop error message that is similar to the following on a blue screen when you restart the computer:

- - STOP: 0x0000007B (0xF201B848, 0xC0000034, 0x00000000, 0x00000000)

INACCESSIBLE_BOOT_DEVICE

Cause

This problem may occur when you update the SCSI controller drivers for the PERC2 RAID array controller on a Dell PowerEdge 2450 server, and either one of the following conditions is true:

You do not update the firmware on the PERC2 RAID array controller before you install the SCSI driver from the Windows Update Web site.
The Afamgt "Fast Utility" UpperFilter driver is loaded in the Windows registry.

Resolution

To resolve this problem, use the following methods in the order that they appear. Continue to Method 2 only if Method 1 is does not resolve the problem, and continue to Method 3 only if Method 2 does not resolve the problem.

Method 1: Replace the Perc2.sys driver file

Replace the updated Perc2.sys driver file with the correct version for the firmware level of your SCSI RAID controller. To do so, follow these steps.

Note If you previously updated the firmware of your RAID controller, obtain the correct version of the Perc2.sys driver from Dell. You cannot use the version of the file that is included with the OpenManage CD-ROM that was included with the hardware. To obtain the correct version of the Perc2.sys file, either contact Dell or visit the following Dell FTP Web site:

ftp://ftp.dell.com/scsi-raid

Use the Windows 2000 CD-ROM to start the computer, and then press F6 to install a third-party SCSI or RAID driver.

Note You may have to change your BIOS settings before you can start your computer from the CD-ROM or DVD-ROM drive. For more information about how to configure your computer to start from the CD-ROM or DVD-ROM drive, see your computer's documentation or contact your computer manufacturer.

Press S to specify an additional device, and then insert the floppy disk that contains the correct driver for the firmware revision that your PERC2 RAID controller has installed.
Press R to repair a Windows 2000 installation.
Press C to use Recovery Console.
Type the number that represents the Windows 2000 installation that you want to repair, and then when you are prompted to, type the Administrator password.
At the command prompt, type cd system32\drivers, and then press ENTER.
Rename the Perc2.sys driver file that is dated 10.29.01.

To do so, type ren perc2.sys perc2.old at the command prompt, and then press ENTER.

Copy the correct version of the Perc2.sys file from the floppy disk to the Winnt\System32\Drivers folder.

To do so, at the command prompt, type copy a:\perc2.sys, and then press ENTER.

Type exit to exit Recovery Console and restart the computer.

If Windows does not start successfully, go to Method 2.

Method 2: Remove the Afamgt filter driver

Remove the Afamgt filter driver from the Windows registry. To do so, follow these steps.

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

Perform a parallel installation of Windows 2000.

For more information about how to do so, click the following article number to view the article in the Microsoft Knowledge Base:

266465 How to perform a parallel installation of Windows 2000 or Windows Server 2003
From the new installation of Windows, start Registry Editor, and then locate the HKEY_LOCAL_MACHINE registry key.
On the Registry menu, click Load Hive.
Locate the SystemRoot\System32\Config folder of the original Windows installation, click the System file, and then click Open.
In the Load Hive box, type test, and then click OK.

The HKEY_LOCAL_MACHINE hive of the original Windows installation is loaded as a subkey of the current HKEY_LOCAL_MACHINE registry key.
Delete the AFAMGT data item from the UpperFilters value in the following registry location of the loaded registry hive:

HKEY_LOCAL_MACHINE\test\ControlSet001\Control\Class\{4D36E967-E325-11CE-BFC1-08002 BE10318}

Value: UpperFilters
Data: AFAMGT Unload the registry hive

To do so, click the test key, and then click Unload Hive on the Registry menu.
Click Yes to confirm the unloading of the test registry key and all its subkeys.
Quit Registry Editor, and then restart the computer to the original Windows installation.

If Windows does not start successfully, go to Method 3.

Method 3: Update the RAID controller firmware

Update the firmware of the RAID controller to the latest revision. For information about how to update the firmware, see the documentation that was included with the device, or contact Dell. To contact Dell, visit the following Dell Web site:

http://support.dell.com

A "Stop: 0x0000007B" error message occurs when you start your computer to a mirrored dynamic disk

If you use software mirroring on dynamic disks for your boot partition, you may receive the following error message when you start and when you shutdown your computer:

STOP: 0x0000007B (0x817bdee8, 0xc0000010, 0x00000000, 0x00000000) Inaccessible_Boot_Device

Note The second parameter in the error message is defined as:

0xc0000010 STATUS_INVALID_DEVICE_REQUEST

Cause

This problem may occur in situations when the primary boot disk at some time reported some unrecoverable disk I/O errors, and has failed redundancy. This causes the primary boot volume to be flagged with a "recover" status in the Logical Disk Manager (LDM) database, and prevents booting to the stale volume.

Resolution

To work around this problem, use a fault tolerance (FT) boot floppy to restart the computer to the operating system that is located on the shadow drive.

For more information about how to create a boot floppy, click the following article number to view the article in the Microsoft Knowledge Base:

119467 How to create a bootable disk for an NTFS or FAT partition

After you restart your computer to the operating system on the shadow drive, start Disk Management, right-click the primary drive (it should have a yellow triangle displayed next to it that indicates that it needs attention), and then click Reactivate disk to remove the recover flag and start regeneration. After the mirror is regenerated and healthy, you can restart your computer as you do normally to the primary drive.

However, make sure that you investigate why the primary drive had I/O errors and to correct the problem to prevent the reoccurrence of this problem. Check the system event log for event messages that are logged by the Dmio event source before the startup problem.

Note If the unrecoverable disk I/O errors that caused this problem only occurred early in the boot process, the system event log may not contain any messages about the failed redundancy until after you successfully start your computer to the shadow drive.

When you use dynamic disk mirroring for the operating system disk before you restart the computer, look in Disk Management to make sure that the mirrored volume and dynamic disks are in a healthy state and do not show errors. If errors appear, take action to correct the error or errors by reactivating the disk to reset the LDM flags. If this action does not succeed, restart your computer to the shadow drive by using a fault tolerance (FT) boot floppy disk for the next scheduled restart.

A "Stop 0x0000007B" error message occurs when you start your computer after you install a new motherboard

When you start your computer after you install a new motherboard, you may receive the following error message on a blue screen:

STOP: 0x0000007B: (parameter1, parameter2, parameter3, parameter4)
INACCESSIBLE_BOOT_DEVICE

Cause

This problem may occur if the new motherboard contains an embedded IDE controller that uses a different chipset than the original motherboard.

Resolution

To resolve this problem, restart Windows 2000 Setup and then repair the Windows 2000 installation. To do so, follow these steps:

Start your computer by using the Windows 2000 Setup floppy disks or from the Windows 2000 CD-ROM.

Note To start your computer from the Windows 2000 CD-ROM, your computer must be configured to start from the CD-ROM drive or DVD drive. For more information about how to configure the computer to start from the CD-ROM drive or DVD drive, see the documentation that came with your personal computer or contact the manufacturer.

At the Welcome to Setup screen, press ENTER.
Read the license agreement, and then when you are prompted to accept the Windows 2000 licensing agreement, press F8.
Select your current installation of Windows 2000 (if it is not already selected), and then press R.
Follow the instructions that appear on the screen to repair your installation of Windows 2000.

You receive a "Stop 0x00000058 FTDISK_INTERNAL_ERROR" error message when you start your computer to a shadow drive from a broken basic mirror

With Windows 2000 you can upgrade a Microsoft Windows NT 4.0-based server where the operating system disk is software mirrored, without first having to break the mirror. Windows 2000 has certain restrictions that are associated with basic disks and earlier fault tolerant sets such as mirrors. One restriction is that you cannot boot from a "stale" or out-of-sync primary drive to the shadow drive.

If for any reason your primary operating system drive does not work or goes offline while it is in a software-mirrored configuration, Windows 2000 continues to run from the shadow drive. If you perform a typical shutdown at this point and revive the primary operating system drive, you cannot use the primary drive to boot back into the functioning shadow drive. This is apparent only if you already have an entry in the Boot.ini file that points to the shadow drive operating system, and then you try to use that entry after the primary drive does not pass redundancy. In this situation, you receive a "Stop 0x00000058 FTDISK_INTERNAL_ERROR" error message when you try to boot to either the primary or the shadow operating system disk. If you then remove or turn off the shadow drive and then try to boot into the stale primary drive, you receive a "Stop 0x0000007B INACCESSIBLE_BOOT_DEVICE" error message. This is also a protection mechanism because the most current data is on the shadow drive.

Note The information in this article only applies to basic disks, and does not apply to dynamic disks.

To guard against data loss and to fully recover from the "Stop 0x00000058 FTDISK_INTERNAL_ERROR" error message, follow these steps:

Use a Windows NT fault tolerant boot floppy disk to start your computer to the shadow (secondary) system drive.

For more information about how to create a boot disk, click the following article number to view the article in the Microsoft Knowledge Base:

119467 How to create a bootable disk for an NTFS or FAT partition
In Windows 2000, follow these steps:
1. Click Start, point to Settings, and then click Control Panel.
2. Double-click Administrative Tools, and then double-click Computer Management.
3. Double-click Storage, and then click Disk Management.
4. Right-click the mirror partition, and then click Resynchronize Mirror.
  
  When the status of the mirror appears as Healthy, shutdown, and then restart your computer.
5. Start your computer to the healthy primary operating system drive.
Note Mirrored dynamic disk operating system drives do not have this restriction. In a similar situation, if you use mirrored dynamic disks, you do not receive the "Stop 0x00000058 FTDISK_INTERNAL_ERROR" error message when you start your computer to the shadow drive. This is one of the advantages that dynamic disks have over basic disks.

A "Stop 0x0000007B" error message occurs after you remove Roxio Easy CD Creator 5 Platinum

When you restart the computer after you remove Roxio Easy CD Creator 5 Platinum, you may receive a Stop error message on a blue screen that is similar to the following:

- - STOP: 0x0000007B (0xF741B84C, 0xC0000034, 0x00000000, 0x00000000)

INACCESSIBLE_BOOT_DEVICE

You may also receive this error message when you reinstall Roxio Easy CD Creator 5 Platinum edition.

Cause

This problem may occur if the PrtSeqRd.sys UpperFilters driver registry entry that was added by Easy CD Creator 5 Platinum Setup is not removed when you remove Easy CD Creator 5 Platinum. When you remove the program, the PrtSeqRd.sys driver file is removed, but the UpperFilters entry may remain in the registry. In this situation, you may receive a "Stop 0x0000007B" error message when you start Windows.

Resolution

To resolve this problem, use the following methods in the order that they appear. Try the next method only if the previous method does not resolve this problem.

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
Method 1: Use a backup registry System hive to edit the registry

To do this, follow these steps

Start the computer by using the Windows 2000 CD-ROM.

Note You may have to change your BIOS settings before you can start your computer from the CD-ROM or DVD-ROM drive. For more information about how to configure your computer to start from the CD-ROM or DVD-ROM drive, see your computer's documentation or contact your computer manufacturer.
If you need a third-party hard disk controller, press S to specify an additional device, and then insert the floppy disk that contains the correct driver for the hard disk controller.
Press R to select Repair, and then press C to select Recovery Console.
Type the number that represents the Windows 2000 installation that you want to repair, and then when you are prompted to, type the Administrator password.
Change to the %windir%\System32\Config folder, rename the System file to System.old, and then copy the System file from the %windir%\Repair\System folder.

To do so, type the following lines at the command prompt Drive:\WinNT prompt (where Drive is the drive, and WinNT is the folder where Windows 2000 is installed), and then press ENTER after each line:

cd system32\config
ren system system.old
copy C:\winnt\repair\system

The following information appears:
```
1 file(s) copied.
```
Type exit, press ENTER to exit Recovery Console, and then restart Windows.

Note If Windows does not start successfully, go to "Method 2: Disable the Easy CD Creator Services" in this article, and do not follow the remaining steps in this method.
Log on to Windows as Administrator.
Click Start, click Run, in the Open box, type regedt32, and then click OK.
Click HKEY_LOCAL_MACHINE, and then on the Registry menu, click Load Hive.
Locate the C:\Winnt\System32\Config folder, click System.old, and then click Open.
In the Key Name box, type test, and then click OK.

The original System hive is loaded under the current HKEY_LOCAL_MACHINE hive as test.
Locate, and then click the following registry subkey: '

HKEY_LOCAL_MACHINE\test\ControlSet001\Control\Class\{4D36E965-E325-11CE-BFC1-08002BE10318}
In the right pane, click LowerFilters, and then on the Edit menu, click Delete.

Click Yes to confirm the deletion.
In the right pane, click UpperFilters, and then on the Edit menu, click Delete.

Click Yes to confirm the deletion.
Locate, and then click the following registry subkey: '

HKEY_LOCAL_MACHINE\test\ControlSet001\Control\Class\{4D36E967-E325-11CE-BFC1-08002BE10318}
In the right pane, double-click UpperFilters.
In the Data box, delete the PrtSeqRd.sys entry, and then click OK.

If you are prompted to permit Registry Editor to remove the empty string, click OK.
Locate, and then click the following registry subkey: '

HKEY_LOCAL_MACHINE\test\ControlSet001\Services
Disable the services that correspond to the following registry subkeys (if they are present) by changing the Start value to 4:

Cdr4_2K
Cdralw2k
Cdudf dvd_2K
Mmc_2K
PrtSeqRd
Pwd_2K
UdfReadr

To do this, click a subkey (for example, click Cdr4_2K), in the right pane, double-click Start, in the Data box, type 4, and then click OK.
Repeat steps 12 through 19 for all other ControlSet00xxx entries (where xxx is a number) under the HKEY_LOCAL_MACHINE\test registry subkey--for example, ControlSet002.
Unload the System.old registry hive. To do so, follow these steps:
1. Click test, and then on the Registry menu, click Unload Hive.
2. Click Yes to confirm the unloading of the test key and all its subkeys.
Quit Registry Editor, and then reload the original registry System hive. To do so, follow these steps:
1. Shut down the computer, and then start the computer by using the Windows 2000 CD-ROM.
2. If you need a third-party hard disk controller, press S to specify an additional device, and then insert the floppy disk that contains the correct driver for the hard disk controller.
3. Press R to select Repair, and then press C to select Recovery Console.
4. Type the number that represents the Windows 2000 installation that you want to repair, and then when you are prompted to, type the Administrator password.
5. Change to the %windir%\System32\Config folder, rename the System file to System.xxx, and then rename the System.old file to System.
  
  To do so, type the following lines at the Drive:\WinNT prompt (where Drive is the drive, and WinNT is the folder where Windows 2000 is installed), pressing ENTER after each line:
  
  cd system32\config
  ren system system.xxx
  ren system.old system
6. Type exit, and then press ENTER to exit Recovery Console.
7. Restart the computer normally.

Method 2: Disable the Easy CD Creator Services

Start the computer by using the Windows 2000 CD-ROM.
If you need a third-party hard disk controller, press S to specify an additional device, and then insert the floppy disk that contains the correct driver for the hard disk controller.
Press R to select Repair, and then press C to select Recovery Console.
Type the number that represents the Windows 2000 installation that you want to repair, and then when you are prompted, type the Administrator password.
Change to the %windir%\System32\Config folder, rename the System file to System.xxx, and then rename the System.old file to System.

To do so, type the following lines at the Drive:\WinNT prompt (where Drive is the drive, and WinNT is the folder where Windows 2000 is installed), pressing ENTER after each line:

cd system32\config
ren system system.xxx
ren system.old system
Change to the %windir%\System32\Drivers folder.

To do this, type the following line at the command prompt, and then press ENTER:

cd C:\WinNT\System32\Drivers
At the command prompt, type the following lines, and then press ENTER after each line:

ren prtseqrd.sys prtseqrd.old
copy diskperf.sys prtseqrd.sys
Disable the following Roxio services, if they are present:

Cdr4_2K
Cdralw2k
Cdudf dvd_2K
Mmc_2K
PrtSeqRd
Pwd_2K
UdfReadr

To do so, type disable ServiceName, and then press ENTER, where ServiceName is the name of one of the services that is in the list. For example, type disable cdr4_2k, and then press ENTER.
If the following files are present in the C:\WinNT\System32\Drivers folder, rename the files to use the .old extension:

Cdr4_2K.sys
Cdralw2k.sys
Cdudf.sys

To do so, follow these steps:
1. At the command prompt, type dir cdr4_2k.sys, and then press ENTER.
  
  If the file name appears, type ren cdr4_2K.sys cdr4_2K.old, and then press ENTER.
2. At the command prompt, type dir cdralw2k.sys, and then press ENTER.
  
  If the file name appears, type ren cdralw2k.sys cdralw2k.old, and then press ENTER.
3. At the command prompt, type dir cdudf.sys, and then press ENTER.
  
  If the file name appears, type ren cdudf.sys cdudf.old, and then press ENTER
Type exit, and then press ENTER to exit Recovery Console and restart the computer.
Start the computer by using the Windows 2000 CD-ROM, press ENTER to set up Windows, and then press R to repair the current Windows installation.

Method 3: Edit the System hive from a parallel Windows installation

Perform a parallel installation of Windows.

For more information about how to do so, click the following article number to view the article in the Microsoft Knowledge Base:

266465 How to perform a parallel installation of Windows 2000 or Windows Server 2003
In the new installation of Windows, click Start, and then click Run.

In the Open box, type regedit, and then click OK.
Locate, and then click the HKEY_LOCAL_MACHINE key.
On the Registry menu, click Load Hive.
Locate the %SystemRoot%\System32\Config folder of the original Windows installation, click the System file, and then click Open.
In the Load Hive box, type test, and then click OK.

The System hive of the original Windows installation is loaded under the current HKEY_LOCAL_MACHINE hive as test.
Repeat steps 12 through 19 of the "Method 1: Use a Backup Registry System Hive to Edit the Registry" section earlier in this article to edit the test registry subkey.
Unload the test registry subkey. To do so, follow these steps:
1. Click test, and then on the Registry menu, click Unload Hive.
2. Click Yes to confirm the unloading of the test key and all its subkeys.
Quit Registry Editor, and then restart the computer to the original Windows installation.

If you cannot start the computer to the original Windows installation, use the Windows 2000 CD-ROM to start the computer, press ENTER to set up Windows, and then press R to repair the current Windows installation.

A "Stop 0x0000007B" error message occurs when you start your computer after you install Iomega IomegaWare 3.1

When you try to start your computer, you may receive an error message that is similar to the following:

STOP 0x0000007B (parameter1, parameter2, parameter3, parameter4)
INACCESSIBLE_BOOT_DEVICE

Cause

This problem may occur if Iomega IomegaWare version 3.1 is installed on the computer.

Resolution

To resolve this problem, use the following methods in the order that they are presented.

Method 1

Use Recovery Console to restore the computer. To do so, follow these steps:
1. Start the computer by using the Windows 2000 CD-ROM.
  
  Note You may have to change your BIOS settings before you can start your computer from the CD-ROM or DVD-ROM drive. For more information about how to configure your computer to start from the CD-ROM or DVD-ROM drive, see your computer's documentation or contact your computer manufacturer.
2. Press R to select Repair, and then press C to select Recovery Console.
3. Type the number that represents the Windows 2000 installation that you want to repair, and then when you are prompted to, type the Administrator password.
4. Change to the %windir%\System32\Config folder, rename the System file to System.old, and then copy the System file from the %windir%\Repair\System folder.
  
  To do so, type the following lines at the Drive:\WinNT prompt (where Drive is the drive, and WinNT is the folder where Windows 2000 is installed), and then press ENTER after each line:
  
  cd system32\config
  ren system system.old
  copy C:\WinNT\repair\system
5. Type exit, and then press ENTER.
6. Start your computer as you normally do.
  
  If you can start your computer as you normally do, go to Step 2 of this method and then follow the remaining steps in this method. If you cannot start your computer as you normally do, go to Method 2.
Edit the registry. To do so, follow these steps.
Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
1. Click Start, and then click Run.
2. In the Open box, type regedt32, and then click OK.
3. Locate, and then click the following registry key:
  
  HKEY_LOCAL_MACHINE
4. On the Registry menu, click Load Hive, and then load the Windows\System32\Config\System.old hive.
5. When you are prompted to specify a name, type Test.
6. Locate, and then click the following keys, where xxx represents numbers such as 001 and 002:
  
  ControlSetxxx\Control\Class\{4D36E965-E325-11CE-BFC1-08002BE10318}
  ControlSetxxx\Control\Class\{4D36E967-E325-11CE-BFC1-08002BE10318}
7. Delete the LowerFilters entry for each of the keys in step 2f.
8. Under ControlSetxxx\Services, disable the services that correspond to the following registry subkeys by changing the Start value to 4:
  
  Iomdisk
  Iomega Activity Disk2
  IomegaAccess
  ZipToA
  
  To do this, click a subkey (for example, click Iomdisk), in the right pane, double-click Start, in the Data box, type 4, and then click OK.
9. On the Registry menu, click Unload Hive, and then unload the Windows\System32\Config\System.old hive.
10. Quit Registry Editor.
Restore the System file. To do so, follow these steps:
1. Start the computer by using the Windows 2000 CD-ROM.
2. Press R to select Repair, and then press C to select Recovery Console.
3. Type the number that represents the Windows 2000 installation that you want to repair, and then when you are prompted to, type the Administrator password.
4. Change to the %windir%\System32\Config folder, rename the System file to System.xxx, and then rename the System.old file to System. To do so, type the following lines at the Drive:\WinNT prompt (where Drive is the drive, and WinNT is the folder where Windows 2000 is installed), and then press ENTER after each line:
  
  cd system32\config
  ren system system.xxx
  ren system.old system
5. Type exit, and then press ENTER to exit Recovery Console.
Start your computer as you normally do, and then remove the IomegaWare program from your computer by using the Add/Remove Programs tool in Control Panel.

Method 2

If you cannot start your computer as you normally do after you follow step 1 of Method 1, follow these steps:

Use Recovery Console to undo the system restore. To do so, follow these steps:
1. Start the computer by using the Windows 2000 CD-ROM.
2. Press R to select Repair, and then press C to select Recovery Console.
3. Type the number that represents the Windows 2000 installation that you want to repair, and then when you are prompted to, type the Administrator password.
4. Change to the %windir%\System32\Config folder, rename the System file to System.xxx, and then rename the System.old file to System.
  
  To do so, type the following lines at the Drive:\WinNT prompt (where Drive is the drive, and WinNT is the folder where Windows 2000 is installed), pressing ENTER after each line:
  
  cd system32\config
  ren system system.xxx
  ren system.old system
Rename, and then copy the Iomdisk.sys drivers.

To do so, at the command prompt, type the following lines, pressing ENTER after each line:

cd WinNT\system32\drivers
ren iomdisk.sys iomdisk.old
copy atapi.sys iomdisk.sys
Disable Iomega services. To do so, follow these steps:
1. At the command prompt, type listsvc, and then locate the following Iomega services:
  - Iomdisk
  - Iomega Activity Disk2
  - IomegaAccess
  - ZipToA
2. For each service in the list, type disable ServiceName, where ServiceName is the name of the service that you want to disable.
Perform an in-place upgrade of Windows 2000.

For more information about how to perform an in-place upgrade of Windows 2000, click the following article number to view the article in the Microsoft Knowledge Base:

292175 How to perform an in-place upgrade of Windows 2000
Remove the IomegaWare program from your computer by using the Add/Remove Programs tool in Control Panel.

A "Stop 0x0000007B" error message occurs after you install Iomega Tools

After you install Iomega Tools on your computer, you may receive an error message that is similar to the following:

STOP 0x0000007B (parameter1, parameter2, parameter3, parameter4)
INACCESSIBLE_BOOT_DEVICE

Cause

This problem may occur in situations where there is an issue with the Iomega ATAPI driver that is preventing Windows from starting correctly.

Resolution

To resolve this problem, follow these steps:

Start the computer by using the Windows 2000 CD-ROM.
Press R to select Repair, and then press C to select Recovery Console.
Type the number that represents the Windows 2000 installation that you want to repair, and then when you are prompted to, type the Administrator password.
To disable the Iomega drivers, type the following command at the Recovery Console command prompt, and then press ENTER:

disable imgatapi
To determine whether the Iomega Atapi service is still set to Boot, type the following line, and then press ENTER:

listsvc
Do one of the following, as appropriate to your situation:
- If the Iomega Atapi service is set to Boot, type exit, and then press ENTER to restart the computer.
- If the Iomega Atapi service is set to Disabled, type the following lines, and then press ENTER after each line:
  
  enable atapi service_boot_start
  exit
Remove the IomegaWare program from your computer by using the Add/Remove Programs tool in Control Panel.

A "Stop 0x0000007B" error message occurs after you remove Veritas Open Transaction Manager

After you remove Veritas Open Transaction Manager from your computer, you may receive one of the following error messages when you restart your computer:

STOP 0x0000007B (parameter1, parameter2, parameter3, parameter4)
INACCESSIBLE_BOOT_DEVICE

STOP 0x00000050 (parameter1, parameter2, parameter3, parameter4)
PAGE_FAULT_IN_NONPAGED_AREA

Using the Last Known Good Configuration feature to start your computer by using the most recent settings that worked correctly does not resolve the problem.

Veritas Open Transaction Manager is a component of Veritas Backup Exec.

Cause

This may occur if certain registry entries that are added by Veritas Open Transaction Manager when you install the program are not removed when you remove the program, and these registry entries are preventing your computer from starting correctly.

Resolution

To resolve this , manually remove the remaining references to the Otman5 driver from the registry. To do so, you first have to install a parallel copy of Windows 2000 to a separate folder, and then use Registry Editor to modify the System hive in the registry. To do so, follow these steps:

Perform a parallel installation of Windows.

For more information about how to do so, click the following article number to view the article in the Microsoft Knowledge Base:

266465 How to perform a parallel installation of Windows 2000 or Windows Server 2003
In the new installation of Windows, click Start, and then click Run.

In the Open box, type regedit, and then click OK.
Locate, and then click the HKEY_LOCAL_MACHINE key.
On the Registry menu, click Load Hive.
Locate the %SystemRoot%\System32\Config folder of the original Windows installation, click the System file, and then click Open.
In the Load Hive box, type test, and then click OK.

The System hive of the original Windows installation is loaded under the current HKEY_LOCAL_MACHINE hive as test.
Locate, and then click the following registry key: '

HKEY_LOCAL_MACHINE\Test\Select

Make a note of the value of the Default entry.

For example, the value may be 0x1.
Locate, and then click the following registry key, where x is the number that you determined earlier in step 7: '

ControlSet00x\Control\Class\{4D36E967-E325-11CE-BFC1-08002BE10318}
In the right pane, double-click the UpperFilters value, and then remove the Otman5 line.
Locate, and then click the following registry key, where x is the number that you determined earlier in step 7: '

ControlSet00x\Control\Class\{71A27CDD-812A-11D0-BEC7-08002BE2092F}
In the right pane, double-click the UpperFilters value, and then remove the Otman5 line.
Unload the test registry subkey. To do so, follow these steps:
1. Click test, and then on the Registry menu, click Unload Hive.
2. Click Yes to confirm the unloading of the test key and all its subkeys.
Quit Registry Editor, and then restart the computer to the original Windows installation.

The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.

REFERENCES

For more information about how to use Recovery Console, click the following article numbers to view the articles in the Microsoft Knowledge Base:

301645 How to use Recovery Console on a computer that does not start in Windows 2000

216417 How to install the Windows Recovery Console

For more information about how to disable a service or device that prevents Windows from starting correctly, click the following article number to view the article in the Microsoft Knowledge Base:

165748 How to disable a service or device that prevents NT from booting

For more information about how to troubleshoot startup problems in Windows 2000, click the following article number to view the article in the Microsoft Knowledge Base:

315396 How to troubleshoot startup problems in Windows 2000

For information about how to contact Dell, Roxio, Iomega, and Veritas, click the appropriate article number in the following list to view the article in the Microsoft Knowledge Base:

65416 Hardware and software vendor contact information, A-K

60781 Hardware and software vendor contact information, L-P

60782 Hardware and software vendor contact information, Q-Z

Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.

Additional query words: VSP 0x7b

Keywords: kberrmsg kbhowtomaster kbinfo KB822052

Microsoft KB Archive/822052

Contents

How to troubleshoot "Stop 0x0000007B" error messages in Windows 2000

SUMMARY

General troubleshooting procedures

Specific troubleshooting procedures

Boot sector viruses

List of specific issues

You receive a "Stop 0x0000007B" error message when you try to start your computer after you move the dynamic hard disk

Cause

Resolution

A "Stop 0x0000007B" error message occurs after you move the system disk to another computer

Cause

Resolution

Additional information

A "Stop 0x0000007B" error message occurs after you update the PERC2 SCSI driver on a Dell PowerEdge 2450 server

Cause

Resolution

A "Stop: 0x0000007B" error message occurs when you start your computer to a mirrored dynamic disk

Cause

Resolution

A "Stop 0x0000007B" error message occurs when you start your computer after you install a new motherboard

Cause

Resolution

You receive a "Stop 0x00000058 FTDISK_INTERNAL_ERROR" error message when you start your computer to a shadow drive from a broken basic mirror

A "Stop 0x0000007B" error message occurs after you remove Roxio Easy CD Creator 5 Platinum

Cause

Resolution

A "Stop 0x0000007B" error message occurs when you start your computer after you install Iomega IomegaWare 3.1

Cause

Resolution

A "Stop 0x0000007B" error message occurs after you install Iomega Tools

Cause

Resolution

A "Stop 0x0000007B" error message occurs after you remove Veritas Open Transaction Manager

Cause

Resolution

REFERENCES