Stop 0x00000007b, (0xB84c2528, 0xc0000034, 0x00000000, 0x00000000)

Kletos

Honorable
Dec 3, 2013
24
0
10,510
Wondering if anyone has any clue to this particular flavor of the 07b BSOD.

After a MB failure and replacement, I installed three XP systems in separate partitions of a 1 Tb drive, one of them a bare bones pony for just diagnostic and management purposes. They all three worked fine until I copied into one of them the data from backup. I then got this endless rebooting on the given STOP code. Since all three worked fine before the data transfer, and the other two still after, I presume it has to be a driver problem rather than one of the other things that commonly cause the 07b.

Does the second element (0xB84C3524) give any useful clue? With several thousand drivers installed, it is hardly practical to isolate them one by one to identify the culprit.
 

xcrossroadsx

Distinguished
Dec 13, 2011
247
1
18,860
A 7b BSOD means INACCESSIBLE_BOOT_DEVICE, translating to the computer not being able to load Windows correctly from the drive. This is most typically caused by incorrectly configured drivers, BIOS, or bad hardware. Since you said you transferred data, I am led to believe that either 1) when transferring the data the storage controller driver was somehow overwritten, leading to incompatibility with your current storage controller on the new motherboard, 2) that the data transfer failed in some way and corrupted the boot partition, or most likely 3) that you replaced boot.ini, ntldr, or ntdetect.com on the new install. Normally the last two are pretty universal, meaning that boot.ini is most likely the culprit. You want to make sure that boot.ini is how it should be, and if it isn't boot into an XP recovery console, bind to that OS, and run bootcfg /rebuild. That should rebuild your boot.ini correctly.
If the correct storage controller driver was loaded, it should be as simple as replacing that .sys file with the correct one (obtained from either the motherboard's manufacturer's website or the storage controller's manufacturer's website).

If it is the second, which is the least likely, running chkdsk /r should fix that.

Unfortunately the first paremeter doesn't give me enough information to narrow down the issue much. The first parameter in the 7b BSOD is "The address of a UNICODE_STRING structure, or the address of the device object that could not be mounted," which I am unfortunately not technically savvy enough to parse. Good luck!
 

Kletos

Honorable
Dec 3, 2013
24
0
10,510
I was hoping the second parameter might give a clue. Apparently that is not the case, at least not yet.

The referenced KB article gives me to believe the problem might be that copying in the data from backup corrupts the registry system hive. The backup data store is a clean copy of one-half a broken mirror, taken while the mirror was still intact and shortly before the failing MB was replaced. The system was fully functional when the backup was made, though intermittently a bit flaky due to bad capacitors in the MB

I eliminated a boot sector problem because other XP installations working from the same boot sector files do just fine. I edit the boot.ini file manually, keep a copy as boot.bak to overwrite the modified file every time I redo the XP install.

I eliminated a hardware problem for the same reason -- other XP installations on the same hard drive and other hardware do just fine.

Which leaves me with a corrupted driver or registry system hive. I think I will look for the significant hive in a new clean installation, before copying in any data, save it to a remote location, then try to copy it back in after copying in the data from backup. The worst thing that could happen would be I would have to wipe the partition and start over again.

Incidentally, the new MB is a duplicate of the previous one, same model, We updated the bios, which couldn't be the problem, because the other installations work.