Crash dump, faulty hardware?

I've got another weird crash dump, my suspicion is that there is some faulty hardware, however I coudn't determine what it could be.
I ran memtest86plus tool for a night and it didn't find any bad memory.
Any suggestions?
The output of !analyze -v follows:

kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common BugCheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8065a0d8fa0, The address that the exception occurred at
Arg3: 0000000000000001, Parameter 0 of the exception
Arg4: 0000000003180006, Parameter 1 of the exception

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2702

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 3088

    Key  : Analysis.Init.CPU.mSec
    Value: 734

    Key  : Analysis.Init.Elapsed.mSec
    Value: 41839

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

    Key  : WER.OS.Branch
    Value: ni_release_svc_prod3

    Key  : WER.OS.Timestamp
    Value: 2023-10-18T18:09:00Z

    Key  : WER.OS.Version
    Value: 10.0.22621.2506


FILE_IN_CAB:  MEMORY.DMP

DUMP_FILE_ATTRIBUTES: 0x1000

BUGCHECK_CODE:  1e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff8065a0d8fa0

BUGCHECK_P3: 1

BUGCHECK_P4: 3180006

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME:  agent.exe

STACK_TEXT:  
fffffd88`4c81d8f8 fffff806`5a2c9805     : 00000000`0000001e ffffffff`c0000005 fffff806`5a0d8fa0 00000000`00000001 : nt!KeBugCheckEx
fffffd88`4c81d900 fffff806`5a236e7c     : 00000000`00001000 ffffba84`2e20a7c0 00000000`00000000 fffffd88`4c81e0e0 : nt!KiDispatchException+0x20dec5
fffffd88`4c81dfe0 fffff806`5a232163     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`42536f49 : nt!KiExceptionDispatch+0x13c
fffffd88`4c81e1c0 fffff806`5a0d8fa0     : fffff806`5a0c9013 fffff806`5a4d947e 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x463
fffffd88`4c81e350 00000000`00000000     : 00000000`00000000 fffff806`5a036e4c 00000000`00000000 00000000`00001001 : nt!MiResolveSharedZeroFault+0x5c0


SYMBOL_NAME:  nt!KiDispatchException+20dec5

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  20dec5

FAILURE_BUCKET_ID:  AV_VRF_nt!KiDispatchException

OS_VERSION:  10.0.22621.2506

BUILDLAB_STR:  ni_release_svc_prod3

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {78585309-2357-40ac-9681-7234dbd4250f}

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

It is far more likely that it is bad kernel mode software than faulty memory.

Thanks for your input. Unfortunately (or fortunately), it's not crashing at the moment. It seems like the crashes were happening in bursts, so I'll just wait for the next series.