Windows 10: Can't figure out what's causing this BSOD

Can someone help me figure out what's causing this BSOD? It's Win 10 Pro (1909). I've made sure the drivers and BIOS are up to date already and ran sfc /scannow that did repair some errors.

************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 18362 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff803`3dc00000 PsLoadedModuleList = 0xfffff803`3e048170
Debug session time: Sun May 24 03:45:19.966 2020 (UTC - 4:00)
System Uptime: 0 days 7:48:37.087
Loading Kernel Symbols
...............................................................
................................................................
..........................................................
Loading User Symbols
Loading unloaded module list
.........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff803`3ddc2390 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffc204`a5f5ec20=00000000000000ef
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************


CRITICAL_PROCESS_DIED (ef)
A critical system process died
Arguments:
Arg1: ffffc30f868de400, Process object or thread object
Arg2: 0000000000000000, If this is 0, a process died. If this is 1, a thread died.
Arg3: 0000000000000000
Arg4: 0000000000000000


Debugging Details:
------------------




KEY_VALUES_STRING: 1


Key : Analysis.CPU.Sec
Value: 4


Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-7001FCV


Key : Analysis.DebugData
Value: CreateObject


Key : Analysis.DebugModel
Value: CreateObject


Key : Analysis.Elapsed.Sec
Value: 8


Key : Analysis.Memory.CommitPeak.Mb
Value: 70


Key : Analysis.System
Value: CreateObject




ADDITIONAL_XML: 1


BUGCHECK_CODE: ef


BUGCHECK_P1: ffffc30f868de400


BUGCHECK_P2: 0


BUGCHECK_P3: 0


BUGCHECK_P4: 0


PROCESS_NAME: services.exe


CRITICAL_PROCESS: services.exe


EXCEPTION_RECORD: ffffc30f868de9c0 -- (.exr 0xffffc30f868de9c0)
ExceptionAddress: 0000000000000000
ExceptionCode: 00000000
ExceptionFlags: 00000000
NumberParameters: 0


ERROR_CODE: (NTSTATUS) 0x8a9d0080 - <Unable to get error code text>


BLACKBOXBSD: 1 (!blackboxbsd)




BLACKBOXNTFS: 1 (!blackboxntfs)




BLACKBOXPNP: 1 (!blackboxpnp)




BLACKBOXWINLOGON: 1


CUSTOMER_CRASH_COUNT: 1


EXCEPTION_STR: 0x0


STACK_TEXT:
ffffc204`a5f5ec18 fffff803`3e4cb6c9 : 00000000`000000ef ffffc30f`868de400 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffffc204`a5f5ec20 fffff803`3e3ecd27 : ffffc30f`868de400 fffff803`3dc88065 ffffc30f`868de400 fffff803`3dc880e0 : nt!PspCatchCriticalBreak+0x115
ffffc204`a5f5ecc0 fffff803`3e270330 : ffffc30f`00000000 00000000`00000000 ffffc30f`868de400 ffffc30f`868de400 : nt!PspTerminateAllThreads+0x17b06b
ffffc204`a5f5ed30 fffff803`3e26ff59 : ffffffff`ffffffff ffffc204`a5f5ee60 ffffc30f`868de400 00000000`00000000 : nt!PspTerminateProcess+0xe0
ffffc204`a5f5ed70 fffff803`3ddd3c15 : 00007ff7`000002e0 ffffc30f`8a9d0080 ffffc30f`868de400 ffffc204`a5f5efb0 : nt!NtTerminateProcess+0xa9
ffffc204`a5f5ede0 fffff803`3ddc61b0 : fffff803`3de5ade8 ffffc204`a5f5f958 ffffc204`a5f5f958 ffffc204`a5f5efb0 : nt!KiSystemServiceCopyEnd+0x25
ffffc204`a5f5ef78 fffff803`3de5ade8 : ffffc204`a5f5f958 ffffc204`a5f5f958 ffffc204`a5f5efb0 00007ff7`778d9000 : nt!KiServiceLinkage
ffffc204`a5f5ef80 fffff803`3ddd431d : ffffc30f`868de9c0 fffff803`3dcdcf9d 00000000`00003200 ffffc204`a5f5fa00 : nt!KiDispatchException+0x15c6f8
ffffc204`a5f5f820 fffff803`3ddd0503 : ffffc30f`8a9d0080 00000000`00000000 00000000`00000000 ffffc30f`880e63e0 : nt!KiExceptionDispatch+0x11d
ffffc204`a5f5fa00 00007ffa`3563e312 : 00000000`00000000 0000007b`00000000 00007ffa`356bfe3e 0000007b`6dc815f0 : nt!KiPageFault+0x443
0000007b`6dc81560 00000000`00000000 : 0000007b`00000000 00007ffa`356bfe3e 0000007b`6dc815f0 00007ff7`778d9000 : 0x00007ffa`3563e312




SYMBOL_NAME: nt!PspCatchCriticalBreak+115


MODULE_NAME: nt


IMAGE_NAME: ntkrnlmp.exe


IMAGE_VERSION: 10.0.18362.836


STACK_COMMAND: .thread ; .cxr ; kb


BUCKET_ID_FUNC_OFFSET: 115


FAILURE_BUCKET_ID: 0xEF_services.exe_BUGCHECK_CRITICAL_PROCESS_8a9d0080_nt!PspCatchCriticalBreak


OS_VERSION: 10.0.18362.1


BUILDLAB_STR: 19h1_release


OSPLATFORM_TYPE: x64


OSNAME: Windows 10


FAILURE_ID_HASH: {75391164-75b8-6cfe-6772-ef09b855b2cc}


Followup: MachineOwner
---------

:)

 

Help figuring out BSOD error nlem64nt.sys

Original thread here. Help figuring out BSOD error nlem64nt.sys

Unfortunately, it is locked. nlem64nt.sys is used by NetLib encryptonizer. We had a similar issue with this causing a PFN File List Corrupt BSOD and their support confirmed we needed to upgrade. Hopefully this will help someone out in the future.

 

BSOD Hardware Caused???

they do weird things like that, which all seem like something else is failing.
One of the worst things to diagnose, they seem to only quit when they want to.

Memtest is a good next step, if you rule out RAM and Power Supply make sure you disconnect all unnecessary peripherals and try to start the system with as little hardware as possible, if it works then, you can narrow down the culprit by trial and error.

the follow was taken from some website:

It's very difficult to determine if a failure is caused by the CPU because many other components can cause the same symptom when they fail.

1. System fails to boot
2. System re-boots intermittently
3. General Protection Fault
4. Illegal Operation
5. Stop Error, or BSoD (Blue Screen OfDeath)

Actually, CPUs rarely fail, and about the only way to determine if the CPU is causing the failure is to swap it out with a known working CPU of the same type and speed. Since this is difficult, the best bet is to first rule out every other possibility.

Before suspecting the CPU, rule out all the possibilities listed below.

1. The Operating System
2. A peripheral port device
3. A bad memory module
4. The hard disk drive
5. The power supply
6. The motherboard

If you have ruled out out all the other possibilities, investigate the items listed below.

1. Overheating
2. A short circuit
3. ESD

 

Random BSOD while browsing internet


BitDefender is nothing special. mwac.sys causes BSODs anywhere.
A tiny documentation can be found here: Solved Random BSODs - Windows 10 Forums
In that very thread, the suggested action apparently worked.

The storage and network filters of any third party antivirus can cause BSODs. Neither MBAM nor BitDefender is any special. For a regular antivirus, it may be shifted to an alternative; but MBAM has no alternative. So a clean install of the said program is the most feasible first step.
As far as the first step is not failing, it is better to not think for the second step. Because the BSODs are not universal, failure at the first step is not universal; and success at the second step is also not universal.
That is why I posted that my suggestion may work, or may not. Let us see where it goes.

 

BSOD Hardware Caused???

they do weird things like that, which all seem like something else is failing.
One of the worst things to diagnose, they seem to only quit when they want to.

Memtest is a good next step, if you rule out RAM and Power Supply make sure you disconnect all unnecessary peripherals and try to start the system with as little hardware as possible, if it works then, you can narrow down the culprit by trial and error.

the follow was taken from some website:

It's very difficult to determine if a failure is caused by the CPU because many other components can cause the same symptom when they fail.

1. System fails to boot
2. System re-boots intermittently
3. General Protection Fault
4. Illegal Operation
5. Stop Error, or BSoD (Blue Screen OfDeath)

Actually, CPUs rarely fail, and about the only way to determine if the CPU is causing the failure is to swap it out with a known working CPU of the same type and speed. Since this is difficult, the best bet is to first rule out every other possibility.

Before suspecting the CPU, rule out all the possibilities listed below.

1. The Operating System
2. A peripheral port device
3. A bad memory module
4. The hard disk drive
5. The power supply
6. The motherboard

If you have ruled out out all the other possibilities, investigate the items listed below.

1. Overheating
2. A short circuit
3. ESD

 

Random BSOD while browsing internet


BitDefender is nothing special. mwac.sys causes BSODs anywhere.
A tiny documentation can be found here: Solved Random BSODs - Windows 10 Forums
In that very thread, the suggested action apparently worked.

The storage and network filters of any third party antivirus can cause BSODs. Neither MBAM nor BitDefender is any special. For a regular antivirus, it may be shifted to an alternative; but MBAM has no alternative. So a clean install of the said program is the most feasible first step.
As far as the first step is not failing, it is better to not think for the second step. Because the BSODs are not universal, failure at the first step is not universal; and success at the second step is also not universal.
That is why I posted that my suggestion may work, or may not. Let us see where it goes.