Windows 10: BSOD at random moments, LSA package not signed, causing unexpected behavior with Credential...

This is the second time this has happened, so I am not making note of this because I don't know what to do about it.This is a brand new system I've had since November, no issues whatsoever.In the past 2 weeks I've had 2 BSOD's, both while browsing and doing nothing of importance really and I can't figure out what is really wrong here.My system is up to date with updates, after the first BSOD I checked if there were any and made sure all were installed and up to date.I am using PRO btw, not sure if it matters but I wanted to make that known.So what happens.If I check my eventviewer, system afte

:)

 

How to fix LSA package is not signed as expected event log entries?

I did a fresh install of windows 11 with only drivers supplied by the install. The 10 errors: LSA package is not signed as expected. This can cause unexpected behavior with Credential Guard. Is still there.

 

How to fix LSA package is not signed as expected event log entries?

Each time my PC boot I also have 10 event Warnings ID 6155 "LSA package is not signed as expected. This can cause unexpected behavior with Credential Guard" with the paquets: msv1_0, sfapm, schannel, wdigest, cloudap, pku2u, tspkg, msv1_0, kerberos, negoexts.

And I have an event Error ID 28 Kernel Event Tracing "provider {77811378-e885-4ac2-a580-bc86e4f1bc93}. Error: 0xC0000005" that seems related with the warning because it is caused by the running process Lsalso.exe (Credential Guard & VBS Key Isolation"

In Regedit, I have HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa.

I have fixed:

"RunAsPPL"=dword:00000001

Any ideas???

 

How to fix LSA package is not signed as expected event log entries?

I get the exact same events logged on every reboot. I'm on Win11 22H2 Version 10.0.22621.963. These warnings have been logging on every reboot for a long time. Would be nice to know why, and if this logging can stop via a fix. Or at least have some information or utility provided to find out why the packages are not signed as expected, especially as at least one is a Microsoft binary.

I've checked registry settings for everything listed in this thread, changed password, etc., to no avail.