Share via

WHEA_UNCORRECTABLE_ERROR (124)

Anonymous
2024-03-01T20:23:33+00:00

Hello there!

As of building a new PC recently im getting the error above while gaming. Two times it was a green screen freeze, and the last time it was a green screen freeze with white cubes on the screen. All three times I had to restart the PC with the power button. I bought a RX 6600 after I put the PC together. Before it i've had a GTX 1050 TI in the same system, with that I've encountered no errors. I've ran OCCT stability tests, testmem5 with anta777 absolut cfg, corecycler and Intel Processor Diagnostic Tool...all without any errors. I've also updated the BIOS. I'd like to also add that before there green screen WHEA error crashes I've got amduw23g stopped responding and has successfully recovered errors with the latest drivers. After this I've rolled back to the 23.11.1 driver only...and now i'm getting the error above. All of this is happened only while gaming as I've already mentioned before.

These are the exact components of the PC:

INTEL CORE I3-12100F without any OC

MSI PRO H610M-E DDR4

KINGSTON FURY 16GB BEAST DDR4 3200MHZ CL16 KIT KF432C16BBK2/16 (now without XMP)

XFX Speedster SWFT 210 AMD Radeon RX 6600 Core 8GB

SILICON POWER 512GB P34A80 M.2 PCIE M.2 2280 SP512GBP34A80M28

ToshibaP300 3.5 3TB 7200rpm 64MB SATA3 (HDWD130UZSVA)

SEASONIC B12 BC 650W

And this is the error, with details:

...............................................................
................................................................
................
Loading User Symbols
PEB is paged out (Peb.Ldr = 0000005c`ec9d3018).  Type ".hh dbgerr001" for details
Mini Kernel Dump does not contain unloaded driver list
For analysis of this file, run !analyze -v
nt!LkmdTelCreateReport+0x1d4:
fffff801`2a874e38 0f1f440000      nop     dword ptr [rax+rax]
4: 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: 0000000000000007, BOOT Error
Arg2: ffffa80f52714020, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000
Arg4: 0000000000000000

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 453

    Key  : Analysis.Elapsed.mSec
    Value: 1927

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x124

    Key  : Dump.Attributes.AsUlong
    Value: 18

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Failure.Bucket
    Value: LKD_0x124_7_GenuineIntel__UNKNOWN_IMAGE_GenuineIntel.sys

    Key  : Failure.Hash
    Value: {5ea80f6a-69bf-5d6f-8fd2-cd87deb91a03}

BUGCHECK_CODE:  124

BUGCHECK_P1: 7

BUGCHECK_P2: ffffa80f52714020

BUGCHECK_P3: 0

BUGCHECK_P4: 0

FILE_IN_CAB:  WHEA-20240301-2034.dmp

DUMP_FILE_ATTRIBUTES: 0x18
  Kernel Generated Triage Dump
  Live Generated Dump

PROCESS_NAME:  smss.exe

STACK_TEXT:  
ffffe103`e7e2ee70 fffff801`2a807157     : ffffa80f`52714000 00000000`00000000 ffffa80f`52714020 0000005c`ecc7fa78 : nt!LkmdTelCreateReport+0x1d4
ffffe103`e7e2f3b0 fffff801`2a80704e     : ffffa80f`52714000 ffffe103`e7e2faa0 00000000`00000000 00000000`00000000 : nt!WheapReportLiveDump+0x7b
ffffe103`e7e2f3f0 fffff801`2a64eb95     : 00000000`00000001 ffffe103`e7e2faa0 00000000`00000000 00000000`00000000 : nt!WheapReportDeferredLiveDumps+0x7a
ffffe103`e7e2f420 fffff801`2a54fca1     : 00000000`00000000 00000000`00000000 00000000`00000001 fffff801`2f0aa22c : nt!WheaCrashDumpInitializationComplete+0x59
ffffe103`e7e2f450 fffff801`2a22bce5     : ffffa80f`54eb7080 00000000`00000000 00000000`0000022c 00000000`00000001 : nt!NtSetSystemInformation+0x971
ffffe103`e7e2fa20 00007ff8`8b092a84     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
0000005c`ecc7fa18 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff8`8b092a84

MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

FAILURE_BUCKET_ID:  LKD_0x124_7_GenuineIntel__UNKNOWN_IMAGE_GenuineIntel.sys

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {5ea80f6a-69bf-5d6f-8fd2-cd87deb91a03}

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

4: kd> !errrec ffffa80f52714020
===============================================================================
Common Platform Error Record @ ffffa80f52714020
-------------------------------------------------------------------------------
Record Id     : 01da6c0f682d1e43
Severity      : Fatal (1)
Length        : 28896
Creator       : Microsoft
Notify Type   : BOOT Error Record
Timestamp     : 3/1/2024 19:34:01 (UTC)
Flags         : 0x00000002 PreviousError

===============================================================================
Section 0     : Firmware Error Record Reference
-------------------------------------------------------------------------------
Descriptor    @ ffffa80f527140a0
Section       @ ffffa80f527142e0
Offset        : 704
Length        : 2592
Flags         : 0x00000000
Severity      : Fatal

===============================================================================
Section 1     : Firmware Error Record Reference
-------------------------------------------------------------------------------
Descriptor    @ ffffa80f527140e8
Section       @ ffffa80f52714d00
Offset        : 3296
Length        : 544
Flags         : 0x00000000
Severity      : Fatal

===============================================================================
Section 2     : Firmware Error Record Reference
-------------------------------------------------------------------------------
Descriptor    @ ffffa80f52714130
Section       @ ffffa80f52714f20
Offset        : 3840
Length        : 72
Flags         : 0x00000000
Severity      : Fatal

It says GeniuneIntel so im totally unsure now whether it's the GPU or the CPU or something else that's faulty here, and what i'm supposed to do.

Thanks for any help.
Windows for home | Windows 11 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

8 answers

Sort by: Most helpful
  1. Igor Leyko 111K Reputation points Independent Advisor
    2024-03-06T22:46:51+00:00

    This may mean insufficient power for the new card.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2024-03-06T22:26:19+00:00

    Well the 1050 Ti has a power consumption of 75-90 Watts and the RX 6600 has around 100-110. Still, since I have no problems now that I switched back to the old GPU, that could mean the new one was faulty, right?

    Was this answer helpful?

    0 comments No comments
  3. Igor Leyko 111K Reputation points Independent Advisor
    2024-03-06T18:56:15+00:00

    I may suppose these cards have different power consumption.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2024-03-06T09:05:50+00:00

    Thank you Igor for the reply, and sorry for not answering.

    I've actually switched back to my old GPU. I've had no errors, no crashes so far with this one. Of course I know this GPU is good because i've been using it for 5 years without any problems ever. The other GPU I've bought, the RX 6600 was used when I bought it. The seller stated that it is in excellent, working condititon, still with 35 months of warranty. The seller also has more than 200 positive ratings (which i know don't really mean anything nowadays). So i don't know what the problem could've been, maybe some driver issues caused it.

    Was this answer helpful?

    0 comments No comments
  5. Igor Leyko 111K Reputation points Independent Advisor
    2024-03-02T00:57:51+00:00

    Hi,

    My name is Igor, it's a pleasure for me to help others and I'll try to help you.

    Please try to re-write BIOS or update it to the latest one (Feb 2024), re-seat CPU with careful contact cleaning. Check this CPU in another motherboard. Unfortunately, even new CPUs may be faulty in rare cases.

    GenuineIntel.sys manages CPU power saving.

    Was this answer helpful?

    0 comments No comments