Server 2012R2 Crash after failed IDMU password sync

Question

Our 2012Dc`s Crash after event 8197:
Error in connecting to Host at the specified port. 
host = 192.168.168.192 
port = 6677 
Please check if the host is up and is running SSOD on the specified port. Winsock error is in the message data.
Followed by event 1000:
Faulting application name: lsass.exe, version: 6.3.9600.16384, time stamp: 0x5215e25f
Faulting module name: ntdll.dll, version: 6.3.9600.17031, time stamp: 0x530895af
Exception code: 0xc0000008
Fault offset: 0x000000000009ca6a
Faulting process id: 0x224
Faulting application start time: 0x01cf9566b19c1df0
Faulting application path: C:\Windows\system32\lsass.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 94688131-01b7-11e4-80d2-005056802892
Faulting package full name: 
Faulting package-relative application ID: 
Resulting in event 1015:
A critical system process, C:\Windows\system32\lsass.exe, failed with status code c0000008.  The machine must now be restarted.
And after 1 minute it restarts.
Looks like exacly the same problem as this:
http://social.technet.microsoft.com/Forums/en-US/b8fe4bc0-a656-4c1f-8d7a-30e148169324/idmu-password-synchronisation-crash-windows-2012?forum=winserverDS
unfortunately no solution is given here.
Please help

Answer 1

Hi Vincent,
Looks like other people have encountered the same issue as you do, here is a similar thread below I have come across:
IDMU Password synchronisation crash Windows 2012
http://social.technet.microsoft.com/Forums/windowsserver/en-US/b8fe4bc0-a656-4c1f-8d7a-30e148169324/idmu-password-synchronisation-crash-windows-2012?forum=winserverDS
According to Bob, he solved the issue by removing NIS and PSYNC features, you may have a try.
In addition, please also consider consulting experts from corresponding third party forums to get this issue solved more efficiently.
Best Regards,
Amy