Windows 10: A critical system process, C:\WINDOWS\system32\lsass.exe, failed with status code c0000374....

I just upgraded from Windows 7 to Windows 10 Version 20H2 OS Build 19042.572. Now the Windows restarts following this error seen in Event Viewer each time I attempt to manage user accounts via Computer Management or Control Panel.


A critical system process, C:\WINDOWS\system32\lsass.exe, failed with status code c0000374. The machine must now be restarted.

There seem to be a few hits for this error on Windows Server but not Windows 10. The OS is patched to date. A/V scanning found nothing. Windows "Reset this PC" did not help. SFC /scannow didn't help. Suggestions?

:)

 

A critical system process, C:\Windows\system32\lsass.exe, failed with status code 1073741819

Hi,

since 05.07.2020 my Laptop HP Pavilion always reboots with the following message:





Sometimes the user cant login and there is only the login button and nothing else is possible.

Sometimes there is the messsage "Error while login with service local session manager". RPC Server is not availible.

I think the error with the RPC Server is just a result of the real error.

Here is what I found out and how I tried to localize the real error:

- Starting windows in safe mode is totally OK and everything works fine.

- Starting windows in safe mode with network settings, works only if:

• Network adapter is deactivated in device manager

When windows safe mode with network settings is started up and I activete the network adapter in device manager again everything works also fine until I add a wired LAN Connection. When the laptop is online blue message appear that I need to restart my computer.

So it has to do something with the internet...

The windows event log says the following:

A critical system process, C:\Windows\system32\lsass.exe, failed with status code 1073741819

What I figured out so far is that the Isass.exe is there to grant permissions to the user if it fails the computer will restart (what happen in normal mode with my computer ).

Google says, that the new Juni Release in Win10 from 2020 is not working and causing this error on some devices:

https://www.thewindowsclub.com/critical-system-process-cwindowssystem32lsass-exe-failed

But their are no updates installed, when I look in safe mode in the "installed upadates section". Also with power shell and command Get-Hotfixes I can only see old updates and no new ones.

The second point in the above mentioned article was to disable the fast startup mode in the energy settings. Since I can only start in safe mode a disabeld fast startup with regedit:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Power → HiberbootEnabled → 0 off

But this also doesnt help.

Another topic what I found was the lSAAS virus, but this was in 2004.

I hope you can help me somehow.

In short:

- In normal mode pc boots all the time

- In safe mode with network settings and connected to the internet pc reboots

- In safe mode everything works fine

Regards,

Dominik

 

Any news on an update to stop the recent blue-screens-of-death ?

The crash in that article means lsasss error, which is a known issue as acknowledged by MS. This is different to a stop code problem, which is also called BSOD.

"The Local Security Authority Subsystem Service (LSASS) file (lsass.exe) might fail on some devices with the error message, 'A critical system process, C:\WINDOWS\system32\lsass.exe, failed with status code c0000008. The machine must now be restarted',"

Did you try installing the patches released yesterday?

 

Remote desktop causing "Your PC will automatically restart in 1 minute"

This happened to me as well; also, I noticed a unique error in the Event Viewer just before the computer crashed:

"A critical system process, C:\Windows\system32\lsass.exe, failed with status code c0000409. The machine must now be restarted." (also error code c0000374)

I was worried my computer was failing, and started running memtest and sfc /scannow, but in the end adding a password to the remote Windows 10 computer was all it took to fix the problem.