BSOD at random moments, LSA package not signed, causing unexpected behavior with Credential Guard

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.

I am the only user and the admin of this system.
No third party virus scan, I use Microsoft Defender.

So what happens.

If I check my eventviewer, system afterwards I see multiple entries regarding:

LSA (LsaSrv):

LSA package is not signed as expected. This can cause unexpected behavior with Credential Guard.

PackageName: negoexts

Event ID: 6155

This warning repeats a couple times with each different package names all at the same time:

• PackageName: kerberos
• PackageName: msv1_0
• PackageName: tspkg
• PackageName: pku2u
• PackageName: cloudap
• PackageName: wdigest
• PackageName: schannel
• PackageName: sfapm

Before it adds:

Information:
IsolatedUserMode:
Secure Trustlet NULL Id 0 and Pid 0 started with status STATUS_SUCCESS.

And then,

LSA (LsaSrv):

LSA package is not signed as expected. This can cause unexpected behavior with Credential Guard.

PackageName: msv1_0

Following by the next:

Information:

Directory-Services-SAM

Event ID: 16962

Remote calls to the SAM database are being restricted using the default security descriptor: O:SYG:SYD:(A;;RC;;;BA).

For more information please see http://go.microsoft.com/fwlink/?LinkId=787651.

Followed by the same event with the following descriptions:

The domain is configured with the following minimum password length-related settings.

MinimumPasswordLength: 0

RelaxMinimumPasswordLengthLimits: 0

MinimumPasswordLengthAudit: -1

For more information see https://go.microsoft.com/fwlink/?LinkId=2097191.

And lastly

The security account manager is now logging periodic summary events for remote clients that call legacy password change or set RPC methods.

For more information please see https://go.microsoft.com/fwlink/?linkid=2150956.

And after this the BSOD happens with a log warning

Warning:
Win32k
Event ID: 263

A pointer device has no information about the monitor it is attached to.

I don't know if it is helpful but the event concerning the BugCheck says this:

The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000de (0x0000000000000002, 0xffffbb0a7782e390, 0xffffbb0a7700e390, 0x0000000599c948c0). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 3aa0d25e-bc13-4552-9c06-e6e43a18bf93.

What is the cause of this issue?

Is this yet another bug? It seems to happen at random, I am not doing anything specific when it occurs nor can I make it happen myself.

Other than this I experience no bugs whatsoever.

https://drive.google.com/file/d/1WfbJcrP8hsyB78Ly_P-RVisWvESRTiU1/view?usp=sharing

This is the dmp file btw, let me know if this works and if not I will adjust or upload it elsewhere.