Does an Active Directory Error Lead to Abnormal Operation?

Question

Active Directory

Windows Server 2019 is not running. In principle, the system can be used and even programs work. But after installing Active Directory services and promoting the server to the level of a domain controller, the system crashes. The first time an error occurs

ATTEMPTED_WRITE_TO_READONLY_MEMORY

This error appears only once and after that the server crashes steadily with the PAGE_FAULT_IN_NONPAGED_AREA error. Errors often appear:

SYSTEM_SERVICE_EXCEPTION

and

KMODE_EXCEPTION_NOT_HANDLED

We began to deal with the problem and found a very interesting fact. It turns out that the error is related to the kernel file

ntoskrnl.exe

Although the Windows error log says that the problem with

Active directory.

So where is the problem anyway? Why can't the system register itself in Active Directory? Why doesn't AD DS always start?
What's the matter and how to solve problems with the server?

Answer 1

There is a problem with hardware or drivers.
Kernel errors like this occur precisely when the driver and the device cannot agree.
This is due to a malfunction of the hardware, or a flaw in the driver that cannot work normally in your combination - no one will tell you, because even MS does not test the server on unknown assemblies.
In the most ideal case, you can google on English-language resources, there may be enthusiasts who could encounter and solve such a problem. But it is not solved by setting.
Again, don't associate the blue screen with an ActiveDirectory error. For proper debugging, you need to learn more about the tools, programming and giblets of Windows. The active directory obviously falls for a different reason.
And in your case, I would change the iron. If Windows is licensed, I would try to contact support.