Windows 10: Help Diagnosing WHEA Error? Minidump Included

Lately I've been having issues with my gaming PC with crashes occurring while in game. I've had an extremely tough time figuring out what seems to be the problem. I have been getting Kernel Power event 41 task 63 errors for weeks now. I've finally been able to locate the mini dump file, however I'm having a tough time making much sense of it. If anyone could help it would be greatly appreciated!


************* Path validation summary **************Response Time ms LocationDeferred srv*Symbol search path is: srv*Executable search path is: Windows 10 Kernel Version 19042 MP 12 procs Free x64Product: WinNt, suite: TerminalServer SingleUserTSMachine Name:Kernel base = 0xfffff805`6da00000 PsLoadedModuleList = 0xfffff805`6e62a2f0Debug session time: Wed Jan 13 23:17:48.130 2021 UTC - 5:00System Uptime: 0 days 0:00:07.756Loading Kernel Symbols.........................................................................................................................................................................Loading User SymbolsMini Kernel Dump does not contain unloaded driver listFor analysis of this file, run !analyze -vnt!LkmdTelCreateReport+0x13e:fffff805`6e37e616 488b03 mov rax,qword ptr [rbx] ds:002b:ffffa78b`67bfb5a0=????????????????2: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************WHEA_UNCORRECTABLE_ERROR 124A fatal hardware error has occurred. Parameter 1 identifies the type of errorsource that reported the error. Parameter 2 holds the address of theWHEA_ERROR_RECORD structure that describes the error conditon. Try !errrec Address of the WHEA_ERROR_RECORD structure to get more details.Arguments:Arg1: 0000000000000000, Machine Check ExceptionArg2: ffffa78b656e2b90, Address of the WHEA_ERROR_RECORD structure.Arg3: 00000000baa00000, High order 32-bits of the MCi_STATUS value.Arg4: 000000000002080b, Low order 32-bits of the MCi_STATUS value.Debugging Details:------------------fffff8056e60f330: Unable to get Flags value from nt!KdVersionBlockfffff8056e60f330: Unable to get Flags value from nt!KdVersionBlock**************************************************************************** ****** ****** 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 ****** ****************************************************************************fffff8056e60f330: Unable to get Flags value from nt!KdVersionBlock**************************************************************************** ****** ****** 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: 2874 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on RYANS-PC Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.mSec Value: 2867 Key : Analysis.Memory.CommitPeak.Mb Value: 79 Key : Analysis.System Value: CreateObject Key : WHEA.MCiStatus.Code Value: 0xbaa000000002080b Key : WHEA.MCiStatus.McaError Value: 0x080b Key : WHEA.MCiStatus.ModelError Value: 0x0002 Key : WHEA.MCiStatus.Reserved Value: 0x00a00000ADDITIONAL_XML: 1OS_BUILD_LAYERS: 1DUMP_FILE_ATTRIBUTES: 0x18 Kernel Generated Triage Dump Live Generated DumpBUGCHECK_CODE: 124BUGCHECK_P1: 0BUGCHECK_P2: ffffa78b656e2b90BUGCHECK_P3: baa00000BUGCHECK_P4: 2080bPROCESS_NAME: smss.exeSTACK_TEXT: ffffda8b`de50e190 fffff805`6e3598bf : ffffa78b`656e2b70 00000000`00000000 ffffa78b`656e2b90 00000000`00000022 : nt!LkmdTelCreateReport+0x13effffda8b`de50e6d0 fffff805`6e3597b6 : ffffa78b`656e2b70 fffff805`00000000 0000005f`00000000 0000005f`ae67f640 : nt!WheapReportLiveDump+0x7bffffda8b`de50e710 fffff805`6e1bda59 : 00000000`00000001 ffffda8b`de50eb80 0000005f`ae67f640 00000000`00000208 : nt!WheapReportDeferredLiveDumps+0x7affffda8b`de50e740 fffff805`6dfcf487 : 00000000`00000000 ffffa78b`646aa030 00000000`00000103 00000000`00000000 : nt!WheaCrashDumpInitializationComplete+0x59ffffda8b`de50e770 fffff805`6de071b8 : ffffa78b`65810000 ffffa78b`658c28f0 ffffda8b`de50eb80 ffffa78b`00000000 : nt!NtSetSystemInformation+0x1f7ffffda8b`de50eb00 00007ffd`1d60f4e4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x280000005f`ae67f5e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`1d60f4e4MODULE_NAME: AuthenticAMDIMAGE_NAME: AuthenticAMD.sysSTACK_COMMAND: .thread ; .cxr ; kbFAILURE_BUCKET_ID: LKD_0x124_0_AuthenticAMD_BANK0_MSCOD0002_MCACOD080B_PCC_UC_IMAGE_AuthenticAMD.sysOSPLATFORM_TYPE: x64OSNAME: Windows 10FAILURE_ID_HASH: {8f3e3444-b104-93da-9f44-3abe2cc69f14}Followup: MachineOwner---------2: kd> lmvm AuthenticAMDBrowse full module liststart end module nameMini Kernel Dump does not contain unloaded driver list

:)

 

WHEA Error - Please Help

Everything on my computer has been running flawlessly since building it a few months ago. For the last week, I've been getting random WHEA errors. I assumed they would go away on their own since it was a generic error every time. Today, I got fed up and reinstalled windows. About 15 minutes into the new installation, I get another WHEA error. I googled it and decided to get blue screen viewer to determine the root of the problem. I have no clue how to read this error log though and need help in a big way. Can someone please direct me on how to fix this crap? Let me know what other information is needed. I'm going crazy over here.

 

WHEA Error - Please Help

WHEA Errors 90% of the time are a result of an unstable overclock. sense you said that you are not overclocking than it might be a power supply/delivery issue. i would try and find out what your 3.3v, 5v, and 12v rail reading are. most of the time you can find these in the bios under the hardware monitoring tab. there are other ways to test a power supply but i am not skilled in advanced methods.

if the psu seems alright try giving the cpu a slight overvolt. you may have just got a really bad chip or its just hungry.

edit, why i bring up the power supply is because i had a similar situation were i was getting WHEA errors and just ignored them. after a while the computer would just randomly lock up and i would have to shut it down. ended up being the psu.

 

WHEA Error - Please Help

make sure that the WHEA erros go away to.