BSOD Domain Controller STOP: c00002e2 Directory Services could not start

bootloops_zpsa38a4c22

Today our domain controller had a very bad day and had a bootloop after a reboot. I used recording software to capture the blue screen error: STOP: c00002e2 Directory Services could not start

Then we found a nice article to fix this issue. We had a second working domain controller so if you have the same setup you can use this how to, to fix this problem also. All the credits go to dbutch1976

  1. Restart the server and press F8 key, select Directory Services restore mode.
  2. Log in with the local administrator username and password (hope you remember what you set it to!).
  3. Type cd \windows\system32
  4. type NTDSUTIL
  5. type activate instance NTDS
  6. type files
  7. If you encounter an error stating that the Jet engine could not be initialized exit out of ntdsutil.
  8. type cd\
  9. type md backupad
  10. type cd \windows\ntds
  11. type copy ntds.dit c:\backupad
  12. type cd \windows\system32
  13. type esentutl /g c:\windows\ntds\ntds.dit
  14. This will perform an integrity check, (the results indicate that the jet database is corrupt)
  15. Type esentutl /p   c:\windows\ntds\ntds.dit
  16. Agree with the prompt
  17. type cd \windows\ntds
  18. type move *.log c:\backupad   (or just delete the log files)

This should complete the repair.  To verify that the repair has worked successfully:

  1. type cd \windows\system32
  2. type ntdsutil
  3. type activate instance ntds
  4. type files        (you should no longer get an error when you do this)
  5. type info       (file info should now appear correctly)

Source: https://social.technet.microsoft.com/Forums/windowsserver/en-US/771b97ad-4e1c-4e7c-8617-91601224dd7f/server-core-2008-r2-blue-screen?forum=winserverManagement

Author: Thomas Faddegon

Bla bla bla