Skip to main content

BSOD 7B when cloning a PC joined to Active Directory

Thread needs solution

We used to use Clonezilla to clone our PC's a few years ago, and that worked fine.

However suddenly cloning refused to work without warning on any PC, no matter the model.  Upon trying to boot Windows there would be this annoying 7B BSOD.
After a serious amount of trouble shooting we found that we had to remove the PC from AD before cloning (even though for years it worked fine without this step and I can find nothing online saying you should need to do this).

Move on a couple more years and we now use MS BitLocker adding more pain to the process.
So I realise that True Image now supports BitLocker - great, so I'm now trying a trial of 11.7.

Backup process appears to work from Windows, and so does the restore using the bootable media - however it's the same problem, the 7B BSOD.
Now I assume it's going to work if I remove the PC from AD first, but this is now more painful as it needs to be backed up from within Windows, ideally while they are still using the PC.

So the question is, have you any idea what could have changed on our Active Directory to prevent a clone being taken and causing this 7B BSOD?  We are wondering if our central IT pushed some setting out to prevent it and won't tell us - is that even possible?
Almost all of the clones are simply to upgrade the capacity of the hard drive without needing to reinstall.

Thanks!

0 Users found this helpful

Try this on your pre-cloned image:

[ABR-82971] Acronis Universal Restore does not automatically set '0' as the "DisableCDDB" value data in the key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\PnP. It leads to a system crash with error 0x0000007B ("INACCESSIBLE_BOOT_DEVICE").

Note: The fix works only if the "DisableCDDB" value is created locally (not through Group Policy).

 

 

Hello James,

This does look like it might be related to the setting described here: https://support.microsoft.com/en-us/kb/2773300

If this is set through a Group Policy -- which is very probable considering the fact that taking the machine out of the domain fixes the BSOD -- our product will not be able to make the change automatically during restore because we can't yet touch GP settings.

But we are working on functionality that would allow Group Policy settings to change during restore, which will fix this issue in a future update of the product. 

 

Wow thanks it was that indeed!

Changing those two registry keys to "0" before cloning allows the clone to boot..