cancel
Showing results for 
Search instead for 
Did you mean: 

PC Processors

MysticalPanties
Journeyman III

WHEA_UNCORRECTABLE_ERROR Ryzen 9 5900X

I built a new PC recently, the parts I've used are

  • AMD Ryzen 9 5900X 3.7 GHz 12-Core Processor
  • Noctua NH-D15 82.5 CFM CPU Cooler
  • NZXT N7 B550 ATX AM4 Motherboard
  • 2x Corsair Vengeance RGB Pro 16 GB (2 x 8 GB) DDR4-3200 CL16 Memory
  • Samsung 980 1 TB M.2-2280 PCIe 3.0 X4 NVME Solid State Drive
  • Asus Noctua OC GeForce RTX 3070 LHR 8 GB Video Card
  • Corsair RM850x (2021) 850 W 80+ Gold Certified Fully Modular ATX Power Supply

I'm using Windows 11 and randomly when I'm playing Dota 2 I get this hard crash. It doesn't happen in other more demanding titles like Cyberpunk 2077, I can play that for hours and get no crashes.

I'm at a loss here I think I've done everything I can think of

  1. I've checked integrity of the install of the game
  2. I've reseated the RAM
  3. I've reinstalled the GPU
  4. I've replugged in every power cord on the motherboard
  5. I've updated the BIOs
  6. I've replaced the whole motherboard
  7. I've reinstalled windows.

I've installed WinDbg so I can actually look at the .dmp files the crash creates, but I can't figure out what the problem is.

So, do I need to send my processor back to get RMA'd?

Here's one of the .dmp files they all display the same info

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


Loading Dump File [C:\Windows\Minidump\121822-6625-01.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 22621 MP (24 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff806`71200000 PsLoadedModuleList = 0xfffff806`71e12fc0
Debug session time: Sun Dec 18 10:05:54.782 2022 (UTC - 6:00)
System Uptime: 0 days 0:10:04.376
Loading Kernel Symbols
...............................................................
................................................................
......................................................
Loading User Symbols
Loading unloaded module list
.........
For analysis of this file, run !analyze -vnt!KeBugCheckEx:
fffff806`71628700 48894c2408      mov     qword ptr [rsp+8],rcx ss:ffffe200`ee1e5940=0000000000000124
7: 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: ffffa38929b5f028, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: 00000000fc800800, High order 32-bits of the MCi_STATUS value.
Arg4: 00000000060c0859, 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_MEMORY_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_MEMORY_ERROR_SECTION                ***
***                                                                   ***
*************************************************************************

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1828

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 1834

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

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

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

    Key  : Bugcheck.Code.DumpHeader
    Value: 0x124

    Key  : Bugcheck.Code.Register
    Value: 0x124

    Key  : Dump.Attributes.AsUlong
    Value: 1008

    Key  : Dump.Attributes.DiagDataWrittenToHeader
    Value: 1

    Key  : Dump.Attributes.ErrorCode
    Value: 0

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Dump.Attributes.LastLine
    Value: Dump completed successfully.

    Key  : Dump.Attributes.ProgressPercentage
    Value: 0


FILE_IN_CAB:  121822-6625-01.dmp

DUMP_FILE_ATTRIBUTES: 0x1008
  Kernel Generated Triage Dump

BUGCHECK_CODE:  124

BUGCHECK_P1: 0

BUGCHECK_P2: ffffa38929b5f028

BUGCHECK_P3: fc800800

BUGCHECK_P4: 60c0859

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  dota2.exe

STACK_TEXT:  
ffffe200`ee1e5938 fffff806`716f487b     : 00000000`00000124 00000000`00000000 ffffa389`29b5f028 00000000`fc800800 : nt!KeBugCheckEx
ffffe200`ee1e5940 fffff806`6d9c10c0     : 00000000`00000000 ffffe200`ee1e5a19 ffffa389`29b5f028 ffffa389`272ef690 : nt!HalBugCheckSystem+0xeb
ffffe200`ee1e5980 fffff806`717febff     : 00000000`00000000 ffffe200`ee1e5a19 ffffa389`29b5f028 2289e6bd`2ec9e6b9 : PSHED!PshedBugCheckSystem+0x10
ffffe200`ee1e59b0 fffff806`716f62aa     : ffffa389`2ef2d900 ffffa389`2ef2d900 ffffa389`272ef6e0 fffff806`715bfdaa : nt!WheaReportHwError+0x38f
ffffe200`ee1e5a80 fffff806`716f66f5     : 00000000`00000007 ffffa389`00000000 00000000`00000000 00000000`00000000 : nt!HalpMcaReportError+0xb2
ffffe200`ee1e5bf0 fffff806`716f6594     : ffffa389`27150540 e0a1d10e`00000000 ffffe200`ee1e5e00 449efd60`00000000 : nt!HalpMceHandlerCore+0x12d
ffffe200`ee1e5c50 fffff806`716f5a26     : ffffa389`27150540 ffffe200`ee1e5ef0 00000000`00000000 663cffa1`6a7cffa5 : nt!HalpMceHandler+0xe0
ffffe200`ee1e5c90 fffff806`716f81bb     : ffffa389`27150540 e23bf60d`ee7bf609 e133412f`ed73412b da03d38f`d643d38b : nt!HalpHandleMachineCheck+0x96
ffffe200`ee1e5cc0 fffff806`7175af39     : 7d3448c3`717448c7 4604da63`4a44da67 fba9666c`f7e96668 c099f4cc`ccd9f4c8 : nt!HalHandleMcheck+0x3b
ffffe200`ee1e5cf0 fffff806`7163a53e     : 67ae6f80`6bee6f84 5c9efd20`50defd24 5f964a02`53d64a06 64a6d8a2`68e6d8a6 : nt!KiHandleMcheck+0x9
ffffe200`ee1e5d20 fffff806`7163a153     : 00000000`00000000 00000000`00000000 00000000`ffffffff ffffe200`ee1e5ef0 : nt!KxMcheckAbort+0x7e
ffffe200`ee1e5e60 00007ffe`fa552894     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x2d3
0000002b`60bfe130 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffe`fa552894


MODULE_NAME: AuthenticAMD

IMAGE_NAME:  AuthenticAMD.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

FAILURE_BUCKET_ID:  0x124_0_AuthenticAMD_MEMORY__UNKNOWN_FATAL_IMAGE_AuthenticAMD.sys

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {b0905187-9dbc-d607-4dc5-8630b9eddb7f}

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

0 Likes
0 Replies