WHEA_UNCORRECTABLE_ERROR (124)

Question

Hi,

I have relatively old computer that was built on 09.04.2019

My Hardware:

I9-9900K (stock)

Asus Rog Maximus XI

PSU RM750X Gold power suply

Corsair Hydro H150i

DDR4 2666 Mhz 32 GB

PNY 3060 TI

Everything was working fine up until 08.03.2023 (Does not matter if i run Windows 10 or Windows 11 problem occurred in both).
Random BSODs with WHEA_UNCORRECTABLE_ERROR or Windows just outright freezes (screen gets stuck and only way to get it unstuck is to press power button and restart it).
IT happend constantly fro 08.03.2023 till 18.03.2023

Troubleshooting steps i took:

1. Ran Memory Diagnostic (Passed)
2. Ran Memtest86+ (Passed multiple times)
3. Ran VideoCard Stability Test (2h no problems)
4. Ran Intel Process Diagnostic tool (passed)
5. Clean Installed Windows 10 - did not solve issue
6. Clean install Windows 11 - Did not solve this issue
7. Ran Chkdsk on system drive and HDD (no issues)
8. Ran SFC /scannow (no problems)
9. Switched GPU-s with another PC (identical GPU so PNY 3060 Ti)
10. Updaed BIOS to latest available version (2004)
11. Updated all drivers to latest version
12. Ran Prime95 (All temps ok)
13. Ran Cinebench (all ok)
14. Ran 3D mark (all ok)
15. Took 16 GB of DDR4 2666Mhz and swapped it into my problem PC and swapped 32 GB DDR4 2666Mhz to another pc - For few days did not have any issues (both Pc-s)
16. Reswapped the 32 GB DDR4 2666mhz back to my computer and the test ram back to the other computer

During the above steps crashes happend random in this pattern:

1. Turn PC on in the morning
2. Windows login screen
3. Open Chrome - Freeze
4. Restart system
5. Windows Login screen
6. Open Game (Grid Autosport)
7. Leave it idle at start of race - Freeze
8. Reboot
9. Login Windows - Bsod Whea error
10. Reboot
11. Login Windows - Bsod whea error
12. Reboot
13. Login Windows - everything works fine for a day or 2 and then either next day or some days skipped the same process continues (Either freeze or Bsod).

After 12th step of troubleshooting everything seemed to be working so i assumed it was just ram "reseating" that fixed it but today i suddenly got BSOD again with the same error.
After the BSOD i did the following troubleshooting steps:

1. Reseat memory (take sticks out and put them back in)
2. Updated drivers
3. Run SFC /scannow
4. Run Dism repair image
5. Run Chkdsk
6. Run Intel process Diagnostic tool (passed)
7. Ran memory Diagnostic (passed)

After those 7 troubleshooting steps the computer remained idle as i went to eat lunch and when i cam back it was completely frozen (mouse did not move) and picture was stuck on the last image i was watching.

Current Pattern was out of the blue.

1. Started PC
2. Login Windows
3. Watched some youtube videos
4. Opened outlook to check mails - BSOD Whea error
5. Reboot
   6)Login Windows
6. Opened Skype
7. Idle for max 2 min and it was completely frozen
8. Reboot
9. Ran troubleshoot step 6 (during that step had another BSOD YSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e) Will also add this dump below)
10. After that i did the Ram switch described above and now everything is fine again

Adding memory.dmp of "Whea_Uncorrectable Error)

*******************************************************************************

* *

* 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: ffffcf85d1635028, Address of the nt!_WHEA_ERROR_RECORD structure.

Arg3: 00000000b2000000, High order 32-bits of the MCi_STATUS value.

Arg4: 0000000000030005, Low order 32-bits of the MCi_STATUS value.

Debugging Details:

---

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec 

Value: 2140 

Key  : Analysis.DebugAnalysisManager 

Value: Create 

Key  : Analysis.Elapsed.mSec 

Value: 4290 

Key  : Analysis.IO.Other.Mb 

Value: 3 

Key  : Analysis.IO.Read.Mb 

Value: 0 

Key  : Analysis.IO.Write.Mb 

Value: 12 

Key  : Analysis.Init.CPU.mSec 

Value: 406 

Key  : Analysis.Init.Elapsed.mSec 

Value: 7708 

Key  : Analysis.Memory.CommitPeak.Mb 

Value: 95 

Key  : Bugcheck.Code.DumpHeader 

Value: 0x124 

Key  : Bugcheck.Code.KiBugCheckData 

Value: 0x124 

Key  : Bugcheck.Code.Register 

Value: 0x124 

Key  : Dump.Attributes.AsUlong 

Value: 1000 

Key  : Dump.Attributes.DiagDataWrittenToHeader 

Value: 1 

Key  : Dump.Attributes.ErrorCode 

Value: 0 

Key  : Dump.Attributes.LastLine 

Value: Dump completed successfully. 

Key  : Dump.Attributes.ProgressPercentage 

Value: 100 

Key  : WER.OS.Branch 

Value: ni\_release 

Key  : WER.OS.Timestamp 

Value: 2022-05-06T12:50:00Z 

Key  : WER.OS.Version 

Value: 10.0.22621.1 

FILE_IN_CAB: MEMORY-10-04.DMP

DUMP_FILE_ATTRIBUTES: 0x1000

BUGCHECK_CODE: 124

BUGCHECK_P1: 0

BUGCHECK_P2: ffffcf85d1635028

BUGCHECK_P3: b2000000

BUGCHECK_P4: 30005

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

PROCESS_NAME: OUTLOOK.EXE

STACK_TEXT:

ffff8581100808e8 fffff8043f8f403b : 0000000000000124 0000000000000000 ffffcf85d1635028 00000000b2000000 : nt!KeBugCheckEx

ffff8581100808f0 fffff8043e1b10c0 : 0000000000000000 ffff8581100809c9 ffffcf85d1635028 ffffcf85cad9dc10 : nt!HalBugCheckSystem+0xeb

ffff858110080930 fffff8043f9fe20f : 0000000000000000 ffff8581100809c9 ffffcf85d1635028 aa02e2e9ffea98a1 : PSHED!PshedBugCheckSystem+0x10

ffff858110080960 fffff8043f8f5a6a : ffffcf85cc2abb10 ffffcf85cc2abb10 ffffcf85cad9dc60 fffff8043f7bfe3a : nt!WheaReportHwError+0x38f

ffff858110080a30 fffff8043f8f5eb5 : 0000000000000003 ffffcf8500000003 ffffce877c8c9000 ffffce877c8d0000 : nt!HalpMcaReportError+0xb2

ffff858110080ba0 fffff8043f8f5d54 : ffffcf85ca759ed0 174abccc00000001 0000000000000000 c66b10c400000000 : nt!HalpMceHandlerCore+0x12d

ffff858110080c00 fffff8043f8f5ffd : 0000000000000010 0000000000000001 0000000000000000 eb8d01c7bb3fe47e : nt!HalpMceHandler+0xe0

ffff858110080c40 fffff8043f8f51b2 : 0000000000000000 0000000000000000 ffff858110080ed0 56834c92a87a0dc2 : nt!HalpMceHandlerWithRendezvous+0xc9

ffff858110080c70 fffff8043f8f797b : ffffcf85ca759ed0 165836bb64882560 54948de9314a8dd3 090cdee088f211a7 : nt!HalpHandleMachineCheck+0x62

ffff858110080ca0 fffff8043f95a729 : ef40d2535b1f13be ab042fa31aed1e50 257c7c4c2ac8ff0e 041cccee2476058b : nt!HalHandleMcheck+0x3b

ffff858110080cd0 fffff8043f83b23e : 5f1d63df5cf20bf8 673609e15647378d fe54a0d374180d4c 4334a09a0f955046 : nt!KiHandleMcheck+0x9

ffff858110080d00 fffff8043f83ae53 : 0000000000000010 0000000000000000 ffffe509ff5f0b40 ffff858110080ed0 : nt!KxMcheckAbort+0x7e

ffff858110080e40 fffff8043fadc861 : ffffcf85d82d6080 0000000000000000 ffffcf85f2194080 0000000002bd7000 : nt!KiMcheckAbort+0x2d3

ffffce877c8cf8b0 fffff8043fad90dc : ffffcf85fd5130c0 0000000000100000 0000000000000000 0000000000000001 : nt!ObpReferenceObjectByHandleWithTag+0x101

ffffce877c8cf940 fffff8043fad907b : ffffcf85f2194080 00000000162568d4 0000000000000000 0000000002bd7000 : nt!ObWaitForSingleObject+0x4c

ffffce877c8cf9a0 fffff8043f83e1e5 : 0000000000000000 0000000000000001 ffffce877c8cf9f8 fffffffffffe7960 : nt!NtWaitForSingleObject+0x6b

ffffce877c8cf9e0 0000000077d31cf3 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x25

00000000218aed28 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x77d31cf3

MODULE_NAME: GenuineIntel

IMAGE_NAME: GenuineIntel.sys

STACK_COMMAND: .cxr; .ecxr ; kb

FAILURE_BUCKET_ID: 0x124_0_GenuineIntel_PROCESSOR_MAE_INTERNAL_PARITY_IMAGE_GenuineIntel.sys

OS_VERSION: 10.0.22621.1

BUILDLAB_STR: ni_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {7e2584db-2def-9a86-cc7c-1fcc158fa39a}

Followup: MachineOwner

Common Platform Error Record @ ffffcf85d1635028

---

Record Id : 01d966cad9e9150d

Severity : Fatal (1)

Length : 1003

Creator : Microsoft

Notify Type : Machine Check Exception

Timestamp : 4/10/2023 5:31:59 (UTC)

Flags : 0x00000000

===============================================================================

Section 0 : Processor Generic

---

Descriptor @ ffffcf85d16350a8

Section @ ffffcf85d16351c8

Offset : 416

Length : 192

Flags : 0x00000001 Primary

Severity : Fatal

Proc. Type : x86/x64

Instr. Set : x64

Error Type : Micro-Architectural Error

Flags : 0x00

CPU Version : 0x00000000000906ec

Processor ID : 0x0000000000000003

===============================================================================

Section 1 : x86/x64 Processor Specific

---

Descriptor @ ffffcf85d16350f0

Section @ ffffcf85d1635288

Offset : 608

Length : 64

Flags : 0x00000000

Severity : Fatal

Local APIC Id : 0x0000000000000003

CPU Id : ec 06 09 00 00 08 10 03 - ff fb fa 7f ff fb eb bf

            00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 

            00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 

===============================================================================

Section 2 : x86/x64 MCA

---

Descriptor @ ffffcf85d1635138

Section @ ffffcf85d16352c8

Offset : 672

Length : 292

Flags : 0x00000000

Severity : Fatal

Error : Internal parity (Proc 3 Bank 0)

Status : 0xb200000000030005

===============================================================================

Section 3 : {c34832a1-02c3-4c52-a9f1-9f1d5d7723fc}

---

Descriptor @ ffffcf85d1635180

Section @ ffffcf85d16353ec

Offset : 964

Length : 39

Flags : 0x00000000

Severity : Informational

Adding memory dump of "System_THread_Exception_Not_Handled (7e)

******************************************************************************* * * * Bugcheck Analysis * * * *******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e) This is a very common BugCheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Arguments: Arg1: ffffffffc0000005, The exception code that was not handled Arg2: fffff8064ed4319a, The address that the exception occurred at Arg3: fffff301eba8a398, Exception Record Address Arg4: ffff800008976900, Context Record Address

Debugging Details:

KEY_VALUES_STRING: 1

Key  : AV.Fault
Value: Read

Key  : Analysis.CPU.mSec
Value: 1515

Key  : Analysis.DebugAnalysisManager
Value: Create

Key  : Analysis.Elapsed.mSec
Value: 3876

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

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

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

Key  : Bugcheck.Code.DumpHeader
Value: 0x7e

Key  : Bugcheck.Code.KiBugCheckData
Value: 0x7e

Key  : Bugcheck.Code.Register
Value: 0x7e

Key  : Dump.Attributes.AsUlong
Value: 1000

Key  : Dump.Attributes.DiagDataWrittenToHeader
Value: 1

Key  : Dump.Attributes.ErrorCode
Value: 0

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

Key  : Dump.Attributes.ProgressPercentage
Value: 100

Key  : WER.OS.Branch
Value: ni\_release

Key  : WER.OS.Timestamp
Value: 2022-05-06T12:50:00Z

Key  : WER.OS.Version
Value: 10.0.22621.1

FILE_IN_CAB: MEMORY.DMP

DUMP_FILE_ATTRIBUTES: 0x1000

BUGCHECK_CODE: 7e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff8064ed4319a

BUGCHECK_P3: fffff301eba8a398

BUGCHECK_P4: ffff800008976900

EXCEPTION_RECORD: fffff301eba8a398 -- (.exr 0xfffff301eba8a398) ExceptionAddress: fffff8064ed4319a (nt!MiCheckSlabPfnBitmap+0x000000000000005a) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: ffffffffffffffff Attempt to read from address ffffffffffffffff

CONTEXT: ffff800008976900 -- (.cxr 0xffff800008976900) rax=ffff800008348000 rbx=0000000000000000 rcx=fffffffff84e0c44 rdx=fffff8064f66eee8 rsi=0000000000000001 rdi=00000000004e0c44 rip=fffff8064ed4319a rsp=fffff301eba8a5d8 rbp=ffffdd890eaddba0 r8=007ffffffffc2706 r9=fffff8064f66eee8 r10=0000003fffffffff r11=ffffff3fffffffff r12=ffff91000ea24cc0 r13=00000000004e0c44 r14=fffff8064f66afc0 r15=000000000ea24cc0 iopl=0 nv up ei pl zr na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050246 nt!MiCheckSlabPfnBitmap+0x5a: fffff8064ed4319a 4c0fa300 bt qword ptr [rax],r8 ds:002b:ffff800008348000=0000000000000000 Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

PROCESS_NAME: System

READ_ADDRESS: ffffffffffffffff

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

EXCEPTION_CODE_STR: c0000005

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: ffffffffffffffff

EXCEPTION_STR: 0xc0000005

STACK_TEXT:
fffff301eba8a5d8 fffff8064ec676b7 : 0000000000000000 0000000000000000 ffffdd890eaddba0 0000000000000001 : nt!MiCheckSlabPfnBitmap+0x5a fffff301eba8a5e0 fffff8064ec641af : 00000000004e0c44 ffffd6be00000001 ffff910000000000 0000000000000000 : nt!MiInsertPageInFreeOrZeroedList+0x2f7 fffff301eba8a730 fffff8064ec62d75 : fffffdfef5af8f60 0000000000000001 0000000000000000 ffffdd890e8f7090 : nt!MiZeroPage+0xbaf fffff301eba8a930 fffff8064edc5e0f : ffffdd890e8f7090 0000000000000000 ffffd6be3d9d5000 0000c68400000003 : nt!MiZeroLocalPages+0x715 fffff301eba8aaa0 fffff8064ec0f5b7 : ffffdd890ead2040 0000000000000080 fffff8064edc5d30 f896e800000088b9 : nt!MiZeroNodePages+0xdf fffff301eba8aaf0 fffff8064ee2e364 : ffff8000090a2180 ffffdd890ead2040 fffff8064ec0f560 8910708948087089 : nt!PspSystemThreadStartup+0x57 fffff301eba8ab40 0000000000000000 : fffff301eba8b000 fffff301eba84000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x34

SYMBOL_NAME: nt!MiCheckSlabPfnBitmap+5a

MODULE_NAME: nt

STACK_COMMAND: .cxr 0xffff800008976900 ; kb

IMAGE_NAME: ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET: 5a

FAILURE_BUCKET_ID: AV_nt!MiCheckSlabPfnBitmap

OS_VERSION: 10.0.22621.1

BUILDLAB_STR: ni_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {68e836f3-60ff-39d2-01cc-a42b3aa5a168}

Followup: MachineOwner

Am i on the right track that it might be RAM causing it or is there some way to actually pinpoint which component might cause it?
I rather not buy new PC and i cant switch many parts with other PC (apart from RAM and GPU)
No program has been able to actually tell me what part is faulty and i am honestly out of ideas.

Currently i reswitched the Rams again (from other PC DDR4 16GB (2 sticks) 2666 mhz into my pc and my 32 GB DDR4 (2 sticks) 2666 Mhz into the other pc.
Memtest86+ has been running for 2 and a half hours now and has done 2 passes with no errors on that PC.

What could it possible be that causes such BSOD and how to actually fix it?

Answer 1

Hi Toomas_S,

Do you have your processor overclocked or undervolted?

Do you have an XMP profile set on your RAM?

Answer 2

Hi,

Thank you For the quick reply, i did check the from the manufacturer website.
For Bios side i have the latest they offer

I did look over the Chipset driver and Armoury Crate (Asus software) says i have the latest version.

Is that WHEA_UNCORRECTABLE_ERROR (124) also related to CPU then? (How does switching Ram kits not cause a crash then? Since CPU is always the same) or are we currently discussing about SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e).

The Version of chipset im running is what "System Restore" put me on which is 10.1.18295.8201.
Forgot to mention that today morning i did put Intel Management Engine Interface V2120.100.0.1085 Which i did before running the "Intel process Diagnostic tool" and then hit that BSOD SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e). So from that view the latest driver caused me that BSOD but the "WHEA_UNCORRECTABLE_ERROR (124)" happend before that.

Answer 3

Hi Toomas_S,

Your minidump files indicate a driver associated to your Intel processor is causing the system crashes.

Go to the support page for your ROG MAXIMUS XI HERO Motherboard on the manufacturers website, then from there, download and install the version of Chipset drivers they recommend and while there, check for any BIOS update that may need to be installed

Answer 4

Hi,

Here are the minidumps
041023-7609-01.zip

The earlier timestamp and bigger one is the one that came with when i had the "Whea" BSOD, the other one is from the other BSOD.

In addition i can say that system has not crashed for (7 hours or so) with the other Ram kit and the original ram is still doing "passes on memtest86" currently 4 passes.

Answer 5

Hi Toomas_S,

I am Dave, I will help you with this.

Please upload any minidump files you have for analysis, I will check those to see if they provide any insight into a potential cause of the system crashes.

Open Windows File Explorer.

Navigate to C:\Windows\Minidump

Copy any minidump files onto your Desktop, then zip those up.

Upload the zip file to the Cloud (OneDrive, DropBox... etc.), then choose to share those and get a share link.

Then post the link here to the zip file, so we can take a look for you.