Question BSOD Bugcheck Analysis with total system freeze.

[SugarTech]

Issue: Complete and total system freezes at arbitrary moments, most often when laptop is idle/not doing much. I can only do a hard reset and a power cycle to get it going again. Works perfectly fine in Safe Mode. Out of Safe Mode issues return.

I never get a BSOD actually, but there was one miracle moment when I did get one. I never thought I'd be happy to see a BSOD because then I'd have something to go on. Crash info below. From my own research where others had similar issues I read that it's possible "intelppm" service is not providing enough power to my CPU? Can anyone please provide some insight and why the crashes disappear in Safe Mode? Does that indicate it's a services issue and not a hardware issue?

What I've tried in roughly this order:
- Windows updates
- Checked for corrupt files.
- Checked and rechecked all possible drivers I could update.
- Put power plan on high performance
- Scanned for malware/viruses.
- Change Registry value for Intelppm to disable power throttling. Didn't help.
- Repair reinstall of Windows 11.
- Temperatures stay around the 50 C or below and fans work fine.

System:
Asus Rog Strix (4 years old)
Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz 2.59 GHz
16.0 GB RAM (15.9 GB usable)
Intel(R) UHD Graphics 630 & GeForce GTX 1660 Ti
Wireless-AC 9560
Windows 11 Home 23H2

*******************************************************************************
* *
* 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: 0000000000000000, Machine Check Exception
Arg2: ffffa90ee3413028, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000800400, Low order 32-bits of the MCi_STATUS value.

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

*** Type referenced: hal!_WHEA_PROCESSOR_GENERIC_ERROR_SECTION ***

*************************************************************************

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 3296

Key : Analysis.Elapsed.mSec
Value: 5201

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

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

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

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

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

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

Key : Bugcheck.Code.LegacyAPI
Value: 0x124

Key : Bugcheck.Code.TargetModel
Value: 0x124

Key : Failure.Bucket
Value: 0x124_0_GenuineIntel_PROCESSOR__UNKNOWN_IMAGE_GenuineIntel.sys

Key : Failure.Hash
Value: {5371cb52-c3d9-558e-47d4-d31c09567ca2}

Key : WER.OS.Branch
Value: ni_release

Key : WER.OS.Version
Value: 10.0.22621.1

BUGCHECK_CODE: 124

BUGCHECK_P1: 0

BUGCHECK_P2: ffffa90ee3413028

BUGCHECK_P3: be000000

BUGCHECK_P4: 800400

FILE_IN_CAB: 072724-28500-01.dmp

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffff8680`6f0ec8e8 fffff807`348ffa5b : 00000000`00000124 00000000`00000000 ffffa90e`e3413028 00000000`be000000 : nt!KeBugCheckEx
ffff8680`6f0ec8f0 fffff807`32da10c0 : 00000000`00000000 ffff8680`6f0ec9c9 ffffa90e`e3413028 ffffa90e`dabff4d0 : nt!HalBugCheckSystem+0xeb
ffff8680`6f0ec930 fffff807`34a0e7df : 00000000`00000000 ffff8680`6f0ec9c9 ffffa90e`e3413028 89481824`6c894810 : PSHED!PshedBugCheckSystem+0x10
ffff8680`6f0ec960 fffff807`3490148a : ffffa90e`e381aaf0 ffffa90e`e381aaf0 ffffa90e`dabff520 fffff807`347813de : nt!WheaReportHwError+0x38f
ffff8680`6f0eca30 fffff807`349018e0 : 00000000`00000005 ffffa90e`00000003 ffff8382`018a1000 ffff8382`018a8000 : nt!HalpMcaReportError+0xb2
ffff8680`6f0ecba0 fffff807`34901774 : ffffa90e`da758e10 438b4c22`00000001 00000000`00000000 48000000`0000000c : nt!HalpMceHandlerCore+0x138
ffff8680`6f0ecc00 fffff807`34901a19 : 00000000`0000000c 00000000`00000001 00000000`00000000 8b4cf18b`4ddb3330 : nt!HalpMceHandler+0xe0
ffff8680`6f0ecc40 fffff807`34900bd2 : 00000000`00000000 00000000`00000000 ffff8680`6f0eced0 f33b4809`76000000 : nt!HalpMceHandlerWithRendezvous+0xc9
ffff8680`6f0ecc70 fffff807`3490338b : ffffa90e`da758e10 48000000`8024848d 248c8d48`1874c23b 0004b841`00000080 : nt!HalpHandleMachineCheck+0x62
ffff8680`6f0ecca0 fffff807`34969ca9 : 00ffffff`25000000 0348078b`48d80348 24843b48`c60349c3 8d4c4777`00000090 : nt!HalHandleMcheck+0x3b
ffff8680`6f0eccd0 fffff807`3482833e : 24848b44`ffffdebc ffe08141`00000080 74f8558b`4800ffff 8b480874`f23b480d : nt!KiHandleMcheck+0x9
ffff8680`6f0ecd00 fffff807`34827f53 : 00000000`00000010 00000000`00000000 00000000`00000004 ffff8680`6f0eced0 : nt!KxMcheckAbort+0x7e
ffff8680`6f0ece40 fffff807`7d08156f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x2d3
ffff8382`018a74c8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : intelppm!MWaitIdle+0x1f


MODULE_NAME: GenuineIntel

IMAGE_NAME: GenuineIntel.sys

STACK_COMMAND: .cxr; .ecxr ; kb

FAILURE_BUCKET_ID: 0x124_0_GenuineIntel_PROCESSOR__UNKNOWN_IMAGE_GenuineIntel.sys

OS_VERSION: 10.0.22621.1

BUILDLAB_STR: ni_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {5371cb52-c3d9-558e-47d4-d31c09567ca2}

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

 

[SugarTech]

ok after making my initial post I came across this article and now I'm questioning this too!