PC Processors

[hoppiez]

GPU: MSI RX 6600 XT

CPU: Ryzen 5 5600X w/ PBO enabled

Motherboard: MSI MPG B550 Gaming Plus

PSU: EVGA 600W 80+ Gold

RAM: 16GBx2 G.Skill Ripjaws w/ XMP enabled

OS Ver: Win 10 Version 22H2 (OS Build 19045.3930)

GPU Driver: 23.12.1

BIOS ver: American Megatrends International LLC. 1.C0 (03/13/2023)

Chipset Version: 5.08.02.027

Boot Drive: Samsung 980 1TB NVMe

The Crash: Happens maybe once every 2-3 weeks, so it is rare. However, this is the 3rd or 4th time it happened, so I am concerned. Randomly while gaming, the screen freezes black and at the same time there is a buzzing noise. Only a few seconds pass and the computer reboots.

Checking Event Viewer, I have multiple errors including the Critical Event 41, Kernel Power. At the same time of the crash, there is also two Event ID 18 error WHEA-Logger, which indicates a hardware failure. I downloaded WinDbg to do a bugcheck analysis on the .dmp files located in the WHEA folder: Windows/LiveKernelReports/WHEA, here are the results:

Spoiler

************* Preparing the environment for Debugger Extensions Gallery repositories **************
ExtensionRepository : Implicit
UseExperimentalFeatureForNugetShare : true
AllowNugetExeUpdate : true
AllowNugetMSCredentialProviderInstall : true
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.015 seconds
----> Repository : UserExtensions, Enabled: true, Packages count: 0
----> Repository : LocalInstalled, Enabled: true, Packages count: 36

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

Loading Dump File [C:\Windows\LiveKernelReports\WHEA\WHEA-20240120-0017.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 19045 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0xfffff801`65400000 PsLoadedModuleList = 0xfffff801`6602a790
Debug session time: Sat Jan 20 00:17:24.274 2024 (UTC - 5:00)
System Uptime: 0 days 0:00:04.868
Loading Kernel Symbols
...............................................................
................................................................
...........
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000082`8d9c2018). Type ".hh dbgerr001" for details
Mini Kernel Dump does not contain unloaded driver list
For analysis of this file, run !analyze -v
nt!LkmdTelCreateReport+0x13e:
fffff801`65d856c6 488b03 mov rax,qword ptr [rbx] ds:002b:ffffa901`632a1f70=????????????????
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: 0000000000000000, Machine Check Exception
Arg2: ffffa90163411840, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: 00000000baa00000, High order 32-bits of the MCi_STATUS value.
Arg4: 000000000002010b, Low order 32-bits of the MCi_STATUS value.

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

*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: hal!_WHEA_PROCESSOR_GENERIC_ERROR_SECTION ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: hal!_WHEA_PROCESSOR_GENERIC_ERROR_SECTION ***
*** ***
*************************************************************************

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 2546

Key : Analysis.Elapsed.mSec
Value: 2542

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: 264

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

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

Key : Bugcheck.Code.LegacyAPI
Value: 0x124

Key : Dump.Attributes.AsUlong
Value: 18

Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1

Key : Failure.Bucket
Value: LKD_0x124_0_AuthenticAMD_PROCESSOR__UNKNOWN_IMAGE_AuthenticAMD.sys

Key : Failure.Hash
Value: {f59f17e7-f24e-04f5-3f16-e9425b2acba5}

BUGCHECK_CODE: 124

BUGCHECK_P1: 0

BUGCHECK_P2: ffffa90163411840

BUGCHECK_P3: baa00000

BUGCHECK_P4: 2010b

FILE_IN_CAB: WHEA-20240120-0017.dmp

DUMP_FILE_ATTRIBUTES: 0x18
Kernel Generated Triage Dump
Live Generated Dump

PROCESS_NAME: smss.exe

STACK_TEXT:
ffffbe8a`4992f150 fffff801`65d6095f : ffffa901`63411820 00000000`00000000 ffffa901`63411840 00000000`00000022 : nt!LkmdTelCreateReport+0x13e
ffffbe8a`4992f690 fffff801`65d60856 : ffffa901`63411820 fffff801`00000000 00000082`00000000 00000082`8daff9d0 : nt!WheapReportLiveDump+0x7b
ffffbe8a`4992f6d0 fffff801`65bd3e7d : 00000000`00000001 ffffbe8a`4992fb40 00000082`8daff9d0 00000000`0000020c : nt!WheapReportDeferredLiveDumps+0x7a
ffffbe8a`4992f700 fffff801`65a883f7 : 00000000`00000000 ffffa901`62431030 00000000`00000103 00000000`00000000 : nt!WheaCrashDumpInitializationComplete+0x59
ffffbe8a`4992f730 fffff801`65811238 : ffffa901`630e0000 ffffa901`6243ed80 ffffbe8a`4992fb40 ffffa901`00000000 : nt!NtSetSystemInformation+0x1f7
ffffbe8a`4992fac0 00007ffe`8e2f0554 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000082`8daff978 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffe`8e2f0554

MODULE_NAME: AuthenticAMD

IMAGE_NAME: AuthenticAMD.sys

STACK_COMMAND: .cxr; .ecxr ; kb

FAILURE_BUCKET_ID: LKD_0x124_0_AuthenticAMD_PROCESSOR__UNKNOWN_IMAGE_AuthenticAMD.sys

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {f59f17e7-f24e-04f5-3f16-e9425b2acba5}

Followup: MachineOwner

All components are less than a year old including the motherboard, only the PSU is about 4-5 years old. No refurbished or used parts. I only have PBO and XMP enabled in terms of overclocking. I tend to raise my minimum frequency of my 6600 XT in AMD overlay to 2600 MHz, as the max is normally 2700 MHz. I also lowered the GPU voltage slightly from 1150 to 1100. VRAM tuning with fast timing + 2180 MHz frequency.

I'm most concerned there is a hardware issue with my PC. I know I can troubleshoot all day and try a ton of fixes... but I've troubleshooted problems like this in the past and with it happening only once every few weeks, it will be very hard.

Any ideas on what I can monitor and if this really is likely a hardware issue? Like I said, the PSU is the only thing that was in my old system (that would crash occasionally), yet having the PSU being the culprit sounds very unlikely.

Thanks

[FunkZ]

---

@hoppiez wrote:

I only have PBO and XMP enabled in terms of overclocking. I tend to raise my minimum frequency of my 6600 XT in AMD overlay to 2600 MHz, as the max is normally 2700 MHz. I also lowered the GPU voltage slightly from 1150 to 1100. VRAM tuning with fast timing + 2180 MHz frequency.

---

What settings are you using with "PBO Enabled"? Have you increased frequency and/or used curve optimizer to adjust voltage?

What is the XMP speed of the memory?

Have you tried leaving the graphics card on the Default preset?

[waldo_36]

Same thing happening to me, and I have current thread going if you're interested to compare what you're experiencing. I'm starting to see a lot more of these posts come up everywhere, because I couldn't find anything similar before I posted last week. I'm saying for sure, but seems like a larger issue than what we might be able to fix.