Exchange is crashing our domain controller


So here is an interesting problem. Over the past few days we have been migrating from an unreliable DC runnign server 2008 to a new DC running server 2016. We have moved ADDS, certificate services, DNS, DCHP although we ran into some bumps in the road it is all done and the old domain controller running 2008 has been demoted and the roles removed.

Now here is the interesting part.

We have Exchange 2010 running on server 2008R2 on the network which connects to the active directory. It sees the new domain controller and everything works as usual except for one thing,

If I open the EMC and then click on "mailboxes" to add and assign new mailboxes, it will instantly crash our domain controller.

The error that we get in the event log on the 2016 domain controller just before it crashes is:

Event ID: 1015
A critical system process, C:\Windows\system32\lsass.exe, failed with status code c0000005.  The machine must now be restarted.

As well as

Event ID: 1000

Faulting application name: lsass.exe, version: 10.0.14393.0, time stamp: 0x57899b4c
Faulting module name: msvcrt.dll, version: 7.0.14393.0, time stamp: 0x57899b47
Exception code: 0xc0000005
Fault offset: 0x000000000005c7a0
Faulting process id: 0x288
Faulting application start time: 0x01d22a5efa3470a5
Faulting application path: C:\Windows\system32\lsass.exe
Faulting module path: C:\Windows\System32\msvcrt.dll
Report Id: 6893cc25-892d-4f9e-a84c-9b2937f85b6e
Faulting package full name: 
Faulting package-relative application ID: 

I have no idea what is going on. Any help would be greatly appreciated.

asked on Server Fault Oct 20, 2016 by Kyle Vaughan • edited Jun 18, 2020 by Gryu

2 Answers


Not sure if anyone is still having this issue - but we increased our Domain Controller's RAM from 2GB to 4GB and the issue corrected.


If anyone encounters the same error I am having and both exchange running on 2008 R2 and domain controller running on server 2016 are VMware virtual machines residing on the same host, move one virtual machine to a different host and problem solved.

answered on Server Fault Oct 20, 2016 by Kyle Vaughan

User contributions licensed under CC BY-SA 3.0