Solved

Domain Controller not booting with BSOD message PROCESS1_INITIALIZATION_FAILED and hex code 0x0000006B

Posted on 2014-10-16
9
864 Views
Last Modified: 2016-02-25
Hello,

We have a single domain controller Active Directory environment that has a non-booting DC.  The DC is a Virtual Server (VMWare) running Windows 2008 R2 Standard.  We have backups (Veeam Software) but they all restore to the same error that the original server has....we really should have performed a disaster recovery drill to test, alas we did not :(

BSOD error:  PROCESS1_INITIALIZATION_FAILED with a hex code of:  0x0000006B.

We have about 15 revisions of this server on backup, but ALL of them restore to the same result.  We are able to boot into recovery console and access the file system of the server, and we have tried the popularly posted solution to this issue of deleting the "c:\windows\system32\codeintegrity\bootcat.cache" file, to no avail.  

I can get access to all of the Operating system files to pull things OUT of this server (database files, etc...) to try and transplant the Active Directory database into another server...or be able to do other repairs to trey and get the system to boot.  VEEAM SOFTWARE does not have any SYSTEM STATE backups or anything else that can be pulled out, so we can't help there.  

Any help is appreciated, we are in a desperate situation...it seems that we may be looking at re-building the domain, which would mean reloading MS Exchange and all other domain-based applications as WELL as re-joining all PC's to the domain...obviously not a pretty ending.

Thank you!
0
Comment
Question by:jkeegan123
  • 3
  • 2
  • 2
  • +2
9 Comments
 
LVL 38

Expert Comment

by:Philip Elder
ID: 40385903
May I offer a suggestion?

Create a new VMDK (virtual hard disk) that is the same size as the system disk on the DC.

Detach the corrupted one and attach this new one.

Run your restore routine from the last backup into the new VMDK. Does it restore okay?
0
 
LVL 78

Expert Comment

by:David Johnson, CD, MVP
ID: 40385923
boot from a recovery cd, enter a command prompt then
Delete the  x:\windows\system32\codeintegrity\Bootcat.cache file, and then restart the computer.
0
 
LVL 5

Author Comment

by:jkeegan123
ID: 40385937
@David Johnson:  I mentioned above that we've tried this suggestion, AND by the way, it is the "D" drive that you perform that file rename / delete on, not the "X" drive, the "X" drive is the recovery disc NOT the damaged OS.  But thank you for trying.
0
 
LVL 34

Expert Comment

by:Seth Simmons
ID: 40386726
We have a single domain controller...

that was the first mistake

...to try and transplant the Active Directory database into another server...

that won't work

my first question would be, did something change?
that is an odd error for a virtual machine unless there is some sort of corruption with the vmdk
if you don't have a good backup, looks like it will be a busy weekend for you
0
 
LVL 19

Expert Comment

by:Zaheer Iqbal
ID: 40386782
Got this below from technet

https://social.technet.microsoft.com/Forums/windows/en-US/9ea22a8a-3bcc-4d5a-aab7-7c62b75241b6/process1initializationfailed

Question

I had the exact same issue and I was able to fix it.
Error STOP: 0x0000006B
 
The file: Bootcat.cache was corrupted, I am not sure how it happened, I ran spybot and spybot had me rebooot the computer to remove files but I don't think it was from Spybot.
 
All you have to do is delete the file: bootcat.cache from %SystemRoot%\system32\codeintegrity
 
I used the instructions from KB981833:
http://support.microsoft.com/kb/981833
After I moved the bootcat.cache to another location then computer boot up and no more BSOD and Spybot continued to ran at startup.
0
 
LVL 5

Accepted Solution

by:
jkeegan123 earned 0 total points
ID: 40398424
As I mentioned, I did try replacing the bootcat.cache file to no avail.
To the person indicating that not having a 2nd domain controller was a mistake, yes that was a mistake, that is why I mentioned it.  I was sharing this experience for the betterment of the overall community, not so that people can gloat over it.

The resolution to this issue was:

- Boot to recovery console
- Navigate to \Windows\WinSXS\Pending.xml - this indicates that there are PENDING ACTIONS for the Windows installation.  This is what was causing the BSOD during boot - the system was in a state such that the pending actions initiation were causing the machine to panic.  The cause of this was that the system had a power outage and during the reboot, the system had a subsequent power outage, and the 2nd power outage interrupted a PRE-BOOT update completion for some Windows updates.  

To resolve, we had to roll back the pending actions using the following:
- From recovery console, enter:
DISM /image:D:\  /cleanup-image  /revertpendingactions

* note:  D:\ is used because the system mounted in recovery console as "D".  The actual system drive when the system boots is "C:\"

* This is the Deplyment Image Servicing and Management CLI, more info about this command can be found here:  http://msdn.microsoft.com/en-us/library/jj980032(v=winembedded.81).aspx
0
 
LVL 34

Expert Comment

by:Seth Simmons
ID: 40398502
none of our suggestions helped because you failed to provide important details
you said nothing about multiple power outages or windows updates installing
0
 
LVL 19

Expert Comment

by:Zaheer Iqbal
ID: 40401744
Agree with Seth - Full info was not provided.
0
 
LVL 5

Author Closing Comment

by:jkeegan123
ID: 40406019
No solution offered a resolution.
0

Join & Write a Comment

Restoring deleted objects in Active Directory has been a standard feature in Active Directory for many years, yet some admins may not know what is available.
In this article, I will show you HOW TO: Create your first Windows Virtual Machine on a VMware vSphere Hypervisor 6.5 (ESXi 6.5) Host Server, the Windows OS we will install is Windows Server 2016.
To efficiently enable the rotation of USB drives for backups, storage pools need to be created. This way no matter which USB drive is installed, the backups will successfully write without any administrative intervention. Multiple USB devices need t…
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles from a Windows Server 2008 domain controller to a Windows Server 2012 domain controlle…

762 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

18 Experts available now in Live!

Get 1:1 Help Now