lsass.exe error and reboot on Server 2016

Question

Hello! I have server 2016 and for about a month I can't solve the problem.
Server sometimes reboots, the message in the log is
Faulting application name: lsass.exe, version: 10.0.14393.4704, time stamp: 0x615be0cd
Faulting module name: ntdll.dll, version: 10.0.14393.5006, time stamp: 0x621ef21b
Exception code: 0xc0000005
Fault offset: 0x0000000000066203
Faulting process id: 0x7c0
Faulting application start time: 0x01d880df3c43cb5b
Faulting application path: C:\Windows\system32\lsass.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll

The process wininit.exe has initiated the restart of computer Server on behalf of user for the following reason: No title for this reason could be found
Reason Code: 0x50006
Shutdown Type: restart
Comment: The system process 'C:\Windows\system32\lsass.exe' terminated unexpectedly with status code -1073741819. The system will now shut down and restart.

I spent a lot of time looking for information on how to solve this problem.
I found news that some updates are causing this problem and I need to remove them, but I don’t have problematic updates installed
Also found this:
Windows Servers domain controllers might restart unexpectedly After installing updates released January 11, 2022, DCs might restart unexpectedly after receiving an Lsass.exe error.
2022-01-11 Resolved in KB5010790

But update KB5010790 cannot be installed on my server. Written not applicable
Today I found information that KB5010790 has been absorbed by the latest update KB5014702
I installed it yesterday. But today the server rebooted again with the same error. So the update didn't fix the problem.
Help please with it

Answer 1

Is this a domain controller?

Answer 2

Yes it is a domain controller with group policies

Answer 3

If it were me, I would not spend much time with this. The simplest and safest thing to do is stand up a new one for replacement.

I'd use dcdiag / repadmin tools to verify health correcting all errors found before starting any operations. Then stand up the new 2016, patch it fully, license it, join existing domain, add active directory domain services, promote it also making it a GC (recommended), transfer FSMO roles over (optional), transfer pdc emulator role (optional), use dcdiag / repadmin tools to again verify health, when all is good you can decommission / demote old one.

--please don't forget to upvote and Accept as answer if the reply is helpful--

Answer 4

I think I was able to solve the problem without reinstalling the system. The problem was in the software.

I had CryptoPRO CSP 5.0.11455 (Fury) installed

I followed the instructions and the problem has not been observed for two weeks. I'm still monitoring the situation.