Friday, January 04, 2013 11:35 PM
Just replaced a failed motherboard in a Dell Poweredge 2800.
After reassembly, the system goes through post, and after 3 passes of the progress bar, system reboots.
In safe mode, and system No Reboot on failure: Enabled set, system BSOD with 0X0000007B
If No Reboot is NOT enabled, in safe mode, system reboots at acpitabl.dat
Following a previous post, I pulled power, took out BIOS battery for a few minutes, and restarted
Other than getting a fast error about SCSI configuration issues could cause loss od data, I stopped.
Lost now on what to do.
Saturday, January 05, 2013 3:26 AM
0x7b == INACCESSIBLE BOOT DEVICE so with the mobo change the disk controller has undoubtably changed. I'd try loading the controller driver also from floppy. For the floppy to successfully boot Windows 2003 the disk must contain the "NT" boot sector. Format a diskette (on a Windows XP/2003 machine, not a DOS/Win9x, so the "NT" boot sector gets written to the floppy), then copy ntldr, ntdetect.com, and boot.ini to it. Edit the boot.ini to give it a correct ARC path for the machine you wish to boot.
In order for this to work you'll want to change the arc path in boot.ini from multi syntax to scsi syntax to indicate that Windows 2003 will load a boot device driver and use that driver to access the boot partition. Then also copy the correct manufacturer scsi driver to the floppy but renamed to ntbootdd.sys
Something like this below;
scsi(0)disk(0)rdisk(0)partition(1)\Windows="Windows 2003 0,1"
scsi(0)disk(0)rdisk(0)partition(2)\Windows="Windows 2003 0,2"
scsi(0)disk(1)rdisk(0)partition(1)\Windows="Windows 2003 1,1"
scsi(0)disk(1)rdisk(0)partition(2)\Windows="Windows 2003 1,2"
Regards, Dave Patrick ....
Microsoft Certified Professional
Microsoft MVP [Windows]
Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
Monday, January 07, 2013 3:16 AMModerator
You may refer to this KB
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:249694However, for a disaster recovery method, do the following as appropriate for your situation:(http://support.microsoft.com/kb/249694/ )How to move a Windows 2000 installation to different hardware
- 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.
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.
TechNet Subscriber Support
- Marked As Answer by Cheers ZHANGMicrosoft Contingent Staff, Moderator Thursday, January 10, 2013 8:42 AM