This Article solved my problem, although it’s for windows 2000 it works like a charm on windows 2003 too:
You receive a “Stop 0x0000007B” error message when you try to start your computer after you move the dynamic hard disk
This is the only article on support.microsoft.com that describes this problem correctly and provides a solution. This “APPLIES TO: Microsoft Windows 2000” but works on 2003 too which is good since there is no article for 2003 for this problem.
This is one of the few article that was written by experts who know what they are talking about, and contains real information on the inner workings of the system. Most of the troubleshooting manuals are just PR bullshit or written for illiterate ppl.
Just to be on the safe side here is the solution:
BSoD: STOP: 0x0000007b (0xf881b84c,0xc0000034,0x00000000,0x00000000)
Means: 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. (or 2003)
• You remove the hard disk from the computer, and then install the hard disk in a second Windows 2000-based computer. (or 2003)
• You import the hard disk to a disk group that contains dynamic disks on the second Windows 2000-based computer. (or 2003)
• You return the hard disk from the second computer to 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.
- 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. ([HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\dmio\Boot Info\Primary Disk Group])
Back up the registry before you modify it!
To delete this key, follow these steps:
1. Boot from an other windows.
2. Run Regedt32 / regedit
3. In Registry Editor, click HKEY_LOCAL_MACHINE, and then on the File menu, click Load Hive…
4. Locate the “corrupt” System file that contains the hive of the operating system that needs fixing (%SystemRootOfCorruptWin%\System32\Config\System.)
5. type Temp in the Key Name box, and then click OK
6. Navigate to HKEY_LOCAL_MACHINE\Temp\SYSTEM\ControlSet*\Services\dmio\Boot Info\Primary Disk Group
7. Right-click the Primary Disk Group registry key, and then click Delete.
8. (repeat 6.,7. for every ControlSet )
9. Click Temp, and then on the File menu, click Unload Hive…, and then click Yes.
10. quit regedit, shut down windows
11. Boot the fixed windows
It’s hard to find info on this code that does not just say “is usually caused by a missing or corrupt driver”.
might be useful:
How to troubleshoot the stop error 0x0000007B?
How to troubleshoot “Stop 0x0000007B” error messages that occur when you run Windows 2000 Setup
How to troubleshoot “Stop 0x0000007B” error messages in Windows 2000