Our forums are currently in maintenance mode and the ability to post is disabled. We will be back up and running as soon as possible. Thanks for your patience!



Stop screen - 2000 Pro OS can't be found - pls help

By BrendaCA ·
My business computer using Windows 2000 Pro was hit by a power surge (despite my surge protector) and now shows the blue screen with "Stop: 0x0000007B" etc. after the title screen. We tried to upgrade to XP Pro w/a new CD, but it wanted to do a new install because it couldn't find the old OS and I don't want to lose everything. (I do have my files backed up.) Then I tried to re-boot 2000 from that CD to try to repair whatever was wrong, and it could not find the original OS either. My IT consultant (I'm not an IT person) finally said to call Microsoft which I am loathe to do, but will if I have to. I do not have an Emergency Recovery Disk since this computer came from my former company. Can anyone help me? I would be so grateful.

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Answers

Collapse -

Try MHDD32

by IC-IT In reply to Stop screen - 2000 Pro OS ...

Download this ISO, create the CD, read the documentation, and let it run a few loops.
Set the program to repair and conduct a loop test. Let it run at least three times through. I have had a lot of luck recovering drives with this program. (I have no affiliation with them).

Collapse -

Booting error.

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)

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.
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.

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 ( How to back up and restore the registry in Windows
1. 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.
2. On the second computer, click Start, click Run, type regedt32 in the Open box, and then click OK.
3. In Registry Editor, click HKEY_LOCAL_MACHINE, and then on the Registry menu, click Load Hive.
4. 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.
5. Click Open, type Temp in the Key Name box, and then click OK.
6. Double-click HKEY_LOCAL_MACHINE, and then double-click Temp.
7. Double-click ControlSet00n, where n is the number of the control set.
8. Double-click Services, double-click dmio, and then click Boot Info.
9. Right-click the Primary Disk Group registry key, and then click Delete.
10. Repeat steps 7 through 9 for each instance of ControlSet00n that appears in the HKEY_LOCAL_MACHINE\Temp subkey.
11. Click Temp, and then on the Registry menu, click Unload Hive, and then click Yes.
12. Quit Registry Editor.
13. Shut down the second computer, and then remove the hard disk that is from the first computer.
14. 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.

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)
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.
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)*********

;*********** Generic_ESDI_Hard_Disk_Controller **********

;*********** Aztech IDE Controller **********************

;*********** Device ID for generic Dual PCI IDE *********

;************Acer Labs Inc ******************************

;************Appian Technology **************************

;************CMD Technology *****************************

;************Compaq *************************************

;*************Intel *************************************

;*************PC Technology *****************************

;*************Silicon Integrated System *****************

;*************Symphony Labs *****************************

;*************Promise Technology ************************

;*************VIA Technologies, Inc. ********************

Please post back if you have any more problems or questions.

Collapse -

Actual Stop msg

by BrendaCA In reply to Booting error.

Thank you for responding. (I enjoyed Finland when I visited there.)

My error msg (which resulted from a power surge, not from moving anything) is
Stop: 0x0000007B (0x81873030, 0xC0000032, 0x00000000, 0x00000000)INACCESSIBLE_BOOT_DEVICE

which is different from the examples you cite. I had looked at TechNet and I can't find any reference to my situation and Stop msg. Additionally, the computer won't let me go into safe mode. Please let me know if you have other ideas or questions for me. Thanks again.

Collapse -

If you don't want to risk losing

by ComputerCookie In reply to Actual Stop msg

any data, I would;

- Buy a new HDD
- Install XP
- Connect your old HDD as a slave and retieve your data.

Any queries please post back.


Collapse -

My post is complicated, unless you are good at probing,

It will be hard to get to the part in the registry to rectify it. I do quite a lot of fixing in the registry because of one thing or another not being correct. Sorry for the complicated post, but there really is no quick fix for this type of thing. When you had the power surge, the drive does not know if it has been moved or not, the part the operating system is looking for is not the correct function or is missing, hence the complicated post.

Please post back if you have any more problems or questions.

Collapse -

By the way, what part of Finland did you go and see?.


Collapse -

What has likely happened

by IC-IT In reply to Actual Stop msg

is the drive got a hard error during the unexpected power loss.
MHDD will (usually) fix the errors.

Collapse -

Buy a new

by Jacky Howe In reply to Stop screen - 2000 Pro OS ...

hard drive, upgrade to XP Pro by installing from the XP Pro CD and restore your Backup.

Let us know how you get on.

Collapse -


by BrendaCA In reply to Stop screen - 2000 Pro OS ...

I would like to thank everyone who responded to my plea. It turned out not to be a hardware problem. We (my IT friend and I) installed XP Pro, then used it to repair 2000, and then upgraded to XP. So no new HDD. I did have to reinstall some hardware, and of course McAfee has been a pain, but it is all working now and my files are safe.

Collapse -

Good to see

by Jacky Howe In reply to Thanks

that you are up and running.

Related Discussions

Related Forums