Help Diagnosing WHEA Error? Minidump Included

R

RyanWill

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) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19042 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff805`6da00000 PsLoadedModuleList = 0xfffff805`6e62a2f0
Debug session time: Wed Jan 13 23:17:48.130 2021 (UTC - 5:00)
System Uptime: 0 days 0:00:07.756
Loading Kernel Symbols
...............................................................
................................................................
..........................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
For analysis of this file, run
!analyze -v
nt!LkmdTelCreateReport+0x13e:
fffff805`6e37e616 488b03 mov rax,qword ptr [rbx] ds:002b:ffffa78b`67bfb5a0=????????????????
2: 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
WHEA_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 Exception
Arg2: 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!KdVersionBlock
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 ***
*** ***
*************************************************************************
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: 0x00a00000


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

DUMP_FILE_ATTRIBUTES: 0x18
Kernel Generated Triage Dump
Live Generated Dump

BUGCHECK_CODE: 124

BUGCHECK_P1: 0

BUGCHECK_P2: ffffa78b656e2b90

BUGCHECK_P3: baa00000

BUGCHECK_P4: 2080b

PROCESS_NAME: smss.exe

STACK_TEXT:
ffffda8b`de50e190 fffff805`6e3598bf : ffffa78b`656e2b70 00000000`00000000 ffffa78b`656e2b90 00000000`00000022 : nt!LkmdTelCreateReport+0x13e
ffffda8b`de50e6d0 fffff805`6e3597b6 : ffffa78b`656e2b70 fffff805`00000000 0000005f`00000000 0000005f`ae67f640 : nt!WheapReportLiveDump+0x7b
ffffda8b`de50e710 fffff805`6e1bda59 : 00000000`00000001 ffffda8b`de50eb80 0000005f`ae67f640 00000000`00000208 : nt!WheapReportDeferredLiveDumps+0x7a
ffffda8b`de50e740 fffff805`6dfcf487 : 00000000`00000000 ffffa78b`646aa030 00000000`00000103 00000000`00000000 : nt!WheaCrashDumpInitializationComplete+0x59
ffffda8b`de50e770 fffff805`6de071b8 : ffffa78b`65810000 ffffa78b`658c28f0 ffffda8b`de50eb80 ffffa78b`00000000 : nt!NtSetSystemInformation+0x1f7
ffffda8b`de50eb00 00007ffd`1d60f4e4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
0000005f`ae67f5e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`1d60f4e4


MODULE_NAME:
AuthenticAMD

IMAGE_NAME: AuthenticAMD.sys

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: LKD_0x124_0_AuthenticAMD_BANK0_MSCOD0002_MCACOD080B_PCC_UC_IMAGE_AuthenticAMD.sys

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {8f3e3444-b104-93da-9f44-3abe2cc69f14}

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

2: kd> lmvm AuthenticAMD
Browse full module list
start end module name
Mini Kernel Dump does not contain unloaded driver list


Continue reading...
 
Back
Top Bottom