Novo Servidor 2012 R2 Essentials gerando Evento de Falha de Auditoria 4625 Tentativas de Logon SID Nulo

Estou searchndo um problema de login crashdo que está desencadeando nosso softwaire de monitoramento.

Pesquisando o problema, a única outra informação que eu poderia achair que era exatamente o que eu estava vendo, estava aqui: Event 4625 Audit Failure NULL SID falhou logon de networking

Tentando rastreair isso, usei o Process Monitor e configurei 2 filters:
Processo IS lsass.exe
O resultado NÃO É SUCESSO.

Eu então correspondi com os resultados com as tentativas de auditoria com crash e pairece corresponder a estas duas linhas no monitor de process como elas mostrairam cada vez no momento exato da crash de auditoria:

1:05:47.4932903 PM lsass.exe 896 RegOpenKey HKLM\Softwaire\Policies\Microsoft\SystemCertificates\Root\ProtectedRoots NAME NOT FOUND Desired Access: Read 1:05:47.4941867 PM lsass.exe 896 RegQueryValue HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\ForceAutoLockOnLogon NAME NOT FOUND Length: 144 

Não tenho certeza se estou olhando paira o lugair certo paira rastreair isso, ou o que fazer agora. Alguma sugestão?

Eu sou novo no server padrão, então não consegui comentair ou responder na pergunta no link acima, mas ficairia curioso se ele / ela viu os mesmos resultados com o monitor de process.

Aqui está um evento de exibição de events:

 An account failed to log on. Subject: Security ID: SYSTEM Account Name: %domainControllerHostname%$ Account Domain: %NetBIOSDomainName% Logon ID: 0x3E7 Logon Type: 3 Account For Which Logon Failed: Security ID: NULL SID Account Name: Account Domain: Failure Information: Failure Reason: Unknown user name or bad password. Status: 0xC000006D Sub Status: 0xC0000064 Process Information: Caller Process ID: 0x380 Caller Process Name: C:\Windows\System32\lsass.exe Network Information: Workstation Name: %domainControllerHostname% Source Network Address: - Source Port: - Detailed Authentication Information: Logon Process: Schannel Authentication Package: Kerberos Transited Services: - Package Name (NTLM only): - Key Length: 0 This event is generated when a logon request fails. It is generated on the computer where access was attempted. The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Serview service, or a local process such as Winlogon.exe or Services.exe. The Logon Type field indicates the kind of logon that was requested. The most common types aire 2 (interactive) and 3 (network). The Process Information fields indicate which account and process on the system requested the logon. The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases. The authentication information fields provide detailed information about this specific logon request. - Transited services indicate which intermediate services have pairticipated in this logon request. - Package name indicates which sub-protocol was used among the NTLM protocols. - Key length indicates the length of the generated session key. This will be 0 if no session key was requested.