System Freeze at Windows 11 Logon Screen...."WHEA...A fatal hardware error has occurred"

Question

I sometimes face a very unusual issue. When I power on and/or restart my PC, the pc would be totally locked out and frozen at windows 11 logon/lock screen and I can see that even the HDD/SDD activity LED is totally unresponsive which indicates that the overall system gets frozen. The only way to get out of that is by HARD-POWER OFF my pc using the POWER button on the case since mouse keyboard wouldn't response at all. It doesn't happen very often, but I have faced it almost 5 to 7 times in the last 2 months. I found in the event viewer that A fatal hardware error has occurred generated by WHEA. I have extracted the dump file contents and I can paste here or upload the word file in which I saved the entire text. Here is the detailed text from the WHEA dump file extracted using WinDbg.

I sometimes tinker around with my CPU Lite Load option in the MSI BIOS since my i5 13600KF sometimes reach 80 Degrees and I also want to check out these features to further my knowledge on them. I recently updated my BIOS to the latest version, and I manually set the CPU Lite Load from AUTO:12 > 10 if I recall correctly. Other than that, I am using XMP for my Corsair Vengeance to achieve its advertised 5200 MHz speeds as on default settings it would stay at 4800 MHz.

I am attaching both the EVENT VIEWER and the original DUMP File

My system specifications are:

Motherboard: MSI Z690 Edge Wi-Fi
CPU: Intel Core i5 13600KF
RAM: Corsair Vengeance DDR5 16GB x 2 RGB 5200 MHz but using Intel XMP 1 to attain 5200 MHz..By default it stays at 4800 MHz
Drives: 1 Samsung 980 1TB NVME M.2 + 1 Samsung EVO 860 + 1 Samsung EVO 840 SATA SSDs.

GPU: MSI GeForce 3060 Ventus 3X OC 12GB GDDR6 >> seated in PCIe x 16 slot.
CPU Cooler: CoolerMaster MasterLiquid 360ML V2 ARGB
OS INFO: Windows 11 Pro Version 23H2 Build No. 22631.2428

************* Preparing the environment for Debugger Extensions Gallery repositories **************
   ExtensionRepository : Implicit
   UseExperimentalFeatureForNugetShare : false
   AllowNugetExeUpdate : false
   AllowNugetMSCredentialProviderInstall : false
   AllowParallelInitializationOfLocalRepositories : true

   -- Configuring repositories
      ----> Repository : LocalInstalled, Enabled: true
      ----> Repository : UserExtensions, Enabled: true

>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds

************* Waiting for Debugger Extensions Gallery to Initialize **************

>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.031 seconds
   ----> Repository : UserExtensions, Enabled: true, Packages count: 0
   ----> Repository : LocalInstalled, Enabled: true, Packages count: 36

Microsoft (R) Windows Debugger Version 10.0.25877.1004 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\LiveKernelReports\WHEA\WHEA-20231208-2041.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*
Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 22631 MP (20 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0xfffff803`1be00000 PsLoadedModuleList = 0xfffff803`1ca130c0
Debug session time: Fri Dec  8 20:41:22.592 2023 (UTC + 5:00)
System Uptime: 0 days 0:00:03.254
Loading Kernel Symbols
...............................................................
................................................................
...............................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 0000001a`3f972018).  Type ".hh dbgerr001" for details
Mini Kernel Dump does not contain unloaded driver list
For analysis of this file, run !analyze -v
nt!LkmdTelCreateReport+0x1d4:
fffff803`1c8781d8 0f1f440000      nop     dword ptr [rax+rax]
6: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
nt!_WHEA_ERROR_RECORD structure that describes the error condition. Try !errrec Address of the nt!_WHEA_ERROR_RECORD structure to get more details.
Arguments:
Arg1: 0000000000000007, BOOT Error
Arg2: ffffbe8f4c214020, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000
Arg4: 0000000000000000

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 686

    Key  : Analysis.Elapsed.mSec
    Value: 14421

    Key  : Analysis.IO.Other.Mb
    Value: 1

    Key  : Analysis.IO.Read.Mb
    Value: 0

    Key  : Analysis.IO.Write.Mb
    Value: 1

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x124

    Key  : Dump.Attributes.AsUlong
    Value: 18

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Failure.Bucket
    Value: LKD_0x124_7_GenuineIntel__UNKNOWN_IMAGE_GenuineIntel.sys

    Key  : Failure.Hash
    Value: {5ea80f6a-69bf-5d6f-8fd2-cd87deb91a03}


BUGCHECK_CODE:  124

BUGCHECK_P1: 7

BUGCHECK_P2: ffffbe8f4c214020

BUGCHECK_P3: 0

BUGCHECK_P4: 0

FILE_IN_CAB:  WHEA-20231208-2041.dmp

DUMP_FILE_ATTRIBUTES: 0x18
  Kernel Generated Triage Dump
  Live Generated Dump

PROCESS_NAME:  smss.exe

STACK_TEXT:  
fffff38b`6b154e70 fffff803`1c809817     : ffffbe8f`4c214000 00000000`00000000 ffffbe8f`4c214020 0000001a`3faff4a8 : nt!LkmdTelCreateReport+0x1d4
fffff38b`6b1553b0 fffff803`1c80970e     : ffffbe8f`4c214000 fffff38b`6b155aa0 00000000`00000000 00000000`00000000 : nt!WheapReportLiveDump+0x7b
fffff38b`6b1553f0 fffff803`1c6576b5     : 00000000`00000001 fffff38b`6b155aa0 00000000`00000000 00000000`00000000 : nt!WheapReportDeferredLiveDumps+0x7a
fffff38b`6b155420 fffff803`1c554a21     : 00000000`00000000 00000000`00000000 00000000`00000001 fffff803`1f50a22c : nt!WheaCrashDumpInitializationComplete+0x59
fffff38b`6b155450 fffff803`1c2274e5     : ffffbe8f`4cb86080 00000000`00000000 00000000`0000022c 00000000`00000001 : nt!NtSetSystemInformation+0x971
fffff38b`6b155a20 00007ffc`d2ff2b04     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
0000001a`3faff448 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffc`d2ff2b04


MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

FAILURE_BUCKET_ID:  LKD_0x124_7_GenuineIntel__UNKNOWN_IMAGE_GenuineIntel.sys

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {5ea80f6a-69bf-5d6f-8fd2-cd87deb91a03}

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