<

Recover from 0x0000007b BSoD: A Special Case

Published on
14,382 Points
8,282 Views
1 Endorsement
Last Modified:
Approved
I don't know how many times you've seen 0x0000007b when your Windows XP dies in a solemn blue.  I've certainly seen my share.  This article is only meant to discuss a specific condition that caused it: disk cloning.  This is the time that you aren't careful enough to use a more capable tool, such as Acronis' TI with Universal Restore, so your newly imaged system falls flat on a different hard drive controller.  This could also happen if you just physically attach a hard drive to a different computer that has a different HD controller.  Microsoft has a very good KB article explaining how you can preempt (to a degree) this kind of problem BEFORE you clone or migrate.

So what if you weren't that careful?  You forgot to take precautions, and you didn't use the right tool.  Sometimes you don't want to, or simply unable to go back and try again (say your source machine is gone for good).  All is not lost.  You don't necessarily have to go through a lengthy repair installation, which will surely fix things in most cases.  

Try MS KB307545.  All you need to do is drop into Recovery Console and copy the system hive file under Repair directory to replace the one in System32/config, which is used by the system to boot and run things.

I'm not entirely sure why that would help in this scenario.  My theory is that the repair copy of system, which was saved at install time, is a more "generic" version for things from HAL layer on down.  Using it Windows XP would be able to survive more device structures and boot up.  I can give one example this saved me time.  I was doing P2V (physical to virtual) from an old TIB image (Acronis) to VMWare Server 2, using VMWare Converter 4.   This trick let me get past 0x0000007b without repair installing XP.
1
Comment
Author:techhealth
6 Comments
 
LVL 4

Expert Comment

by:advserver
This did not correct the 7B problem for me :(
0
 
LVL 11

Author Comment

by:techhealth

How did 7b start happening?  My article deals with cloning/moving hard drive to a dissimilar HD controller scenario.  If that's not the cause for the 7b error, it won't really help.
0
 
LVL 1

Expert Comment

by:v-2samrc
The 7b error is commonly found with RAID drivers.
0
 
LVL 5

Expert Comment

by:pinascode
i hvae found that a bios setting for the hdd, when changed from ahci to ata worked for me. mine was a DELL 1520
0
 
LVL 11

Author Comment

by:techhealth
7b, or some other serious errors, will definitely come about if you tinker with BIOS settings on hdd controller (switching between RAID/AHCI/ATA) with installed Windows, so be really careful.  The article isn't about addressing those causes.
0
 
LVL 10

Expert Comment

by:Tony Barkdull
7b errors I have seen stem from updating hardware drivers via Windows update. One should NEVER apply driver updates via Windows Updaes because they are generic and UNTESTED from the PC manufacturer or the hardware Vendor. Always update drivers via the Manufacturer website.

  That being said, if you are imaging with ANY tool, make sure the target PC has the same hardware controller and the source PC, or you are just asking for headaches. The 7b errors you see may be from incompatible hardware in your target machines.
0

Join & Write a Comment

Two types of users will appreciate AOMEI Backupper Pro: 1 - Those with PCIe drives (and haven't found cloning software that works on them). 2 - Those who want a fast clone of their boot drive (no re-boots needed) and it can clone your drive wh…
From store locators to asset tracking and route optimization, learn how leading companies are using Google Maps APIs throughout the customer journey to increase checkout conversions, boost user engagement, and optimize order fulfillment. Powered …

Keep in touch with Experts Exchange

Tech news and trends delivered to your inbox every month