WHEA_UNCORRECTABLE_ERROR

Apurv Bargale 1 Reputation point
2022-10-10T19:22:48.51+00:00

I have a ASUS X507UA laptop with intel core i3 7th gen processor with 4 gb ram. from last couple of months i have been experiencing this blue screen/sudden crash issue in my laptop. Just doing normal surfing or doing regular work on my laptop and suddenly a blue screen appears with a message WHAE_UNCORRECTABLE_ERROR. I had tried changing ram to new one and installing fresh copy of windows 10 OS. But still problem persists. Just during normal internet surfing system crashes. I had debugging the minidump files using windbg tool but some how I am not able to interpret the error message. Also I had used bluescreenview tool to further investigate the issue but it also states that some driver might be causing this issue. Please help me in resolving this problem. For further assistance I have attached the dump file below. Any help would be appreciated.

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

Loading Dump File [C:\Windows\Minidump\100622-21812-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 19041 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff80139400000 PsLoadedModuleList = 0xfffff8013a02a1d0
Debug session time: Thu Oct 6 20:30:41.376 2022 (UTC + 5:30)
System Uptime: 0 days 0:09:17.122
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.............
Loading User Symbols
Loading unloaded module list
..............
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff801397f6f20 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff8013cc7dcd0=0000000000000124
0: 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: 0000000000000004, PCI Express Error
Arg2: ffffcd84107d4028, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000
Arg4: 0000000000000000

Debugging Details:

------------------

***WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec  
Value: 9264  

Key  : Analysis.DebugAnalysisManager  
Value: Create  

Key  : Analysis.Elapsed.mSec  
Value: 14230  

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

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

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

Key  : Bugcheck.Code.DumpHeader  
Value: 0x124  

Key  : Bugcheck.Code.KiBugCheckData  
Value: 0x124  

Key  : Bugcheck.Code.Register  
Value: 0x124  

Key  : WER.OS.Branch  
Value: vb_release  

Key  : WER.OS.Timestamp  
Value: 2019-12-06T14:06:00Z  

Key  : WER.OS.Version  
Value: 10.0.19041.1  

FILE_IN_CAB: 100622-21812-01.dmp

BUGCHECK_CODE: 124

BUGCHECK_P1: 4

BUGCHECK_P2: ffffcd84107d4028

BUGCHECK_P3: 0

BUGCHECK_P4: 0

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
fffff8013cc7dcc8 fffff801398b3eaa : 0000000000000124 0000000000000004 ffffcd84107d4028 0000000000000000 : nt!KeBugCheckEx
fffff8013cc7dcd0 fffff801353715b0 : 0000000000000000 ffffcd84107d4028 ffffcd84108624b0 ffffcd84107d4028 : nt!HalBugCheckSystem+0xca
fffff8013cc7dd10 fffff801399b5d5e : 0000000000000000 fffff8013cc7ddb9 ffffcd84107d4028 ffffcd84108624b0 : PSHED!PshedBugCheckSystem+0x10
fffff8013cc7dd40 fffff8013b083523 : 0000000000000001 0000000000000001 ffffcd84108604b0 ffffcd84107d10d0 : nt!WheaReportHwError+0x46e
fffff8013cc7de20 fffff8013b083d16 : ffffb6010cff0b00 fffff8013cc7dec0 ffffb6010cff0bf0 ffffcd841011d000 : pci!ExpressRootPortAerInterruptRoutine+0x26b
fffff8013cc7de80 fffff8013b083dd9 : ffffb6010cff0b40 fffff80139728831 0000000000000000 ffffcd8410105000 : pci!ExpressRootPortInterruptRoutine+0x46
fffff8013cc7dee0 fffff8013973b241 : ffffcd8410f50f43 fffff80100400a02 fffff8013bd571a0 0000000000007101 : pci!ExpressRootPortMessageRoutine+0x9
fffff8013cc7df10 fffff801396de055 : 0000000000000008 fffff8013cc7df20 000000000000000c ffff72a5530a3e21 : nt!KiInterruptMessageDispatch+0x11
fffff8013cc7df40 fffff801397f874f : fffff8013cc6ea50 ffffb6010cff0b40 000000000000079c 0000012edb67e392 : nt!KiCallInterruptServiceRoutine+0xa5
fffff8013cc7df90 fffff801397f8a17 : fffff8013cc6eaf0 0000000000000001 0000000000040046 fffff801396172a8 : nt!KiInterruptSubDispatch+0x11f
fffff8013cc6e9d0 fffff801397faa4a : 0000000000000000 fffff8013a126a00 ffffcd8410f63100 000000000000079c : nt!KiInterruptDispatch+0x37
fffff8013cc6eb60 0000000000000000 : fffff8013cc6f000 fffff8013cc68000 0000000000000000 0000000000000000 : nt!KiIdleLoop+0x5a

MODULE_NAME: GenuineIntel

IMAGE_NAME: GenuineIntel.sys

STACK_COMMAND: .cxr; .ecxr ; kb

FAILURE_BUCKET_ID: 0x124_4_GenuineIntel_PCIEXPRESS_RECEIVER_OVERFLOW_IMAGE_GenuineIntel.sys

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {292b172a-d242-4fa5-ed33-089eb4b12cc5}

Followup: MachineOwner
-----
.......................................................................................................................................................................................................................................................................................................................
Microsoft (R) Windows Debugger Version 10.0.25200.1003 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\Minidump\101022-18703-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 19041 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff80667c00000 PsLoadedModuleList = 0xfffff8066882a290
Debug session time: Mon Oct 10 20:50:08.579 2022 (UTC + 5:30)
System Uptime: 0 days 0:17:54.324
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..............
Loading User Symbols
Loading unloaded module list
...........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff80667ff8fa0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff8066d880cd0=0000000000000124
0: 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: 0000000000000004, PCI Express Error
Arg2: ffff9f0fb17dd028, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000
Arg4: 0000000000000000

Debugging Details:

------------------

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec  
Value: 11875  

Key  : Analysis.DebugAnalysisManager  
Value: Create  

Key  : Analysis.Elapsed.mSec  
Value: 116758  

Key  : Analysis.IO.Other.Mb  
Value: 8  

Key  : Analysis.IO.Read.Mb  
Value: 0  

Key  : Analysis.IO.Write.Mb  
Value: 11  

Key  : Analysis.Init.CPU.mSec  
Value: 781  

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

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

Key  : Bugcheck.Code.DumpHeader  
Value: 0x124  

Key  : Bugcheck.Code.Register  
Value: 0x124  

Key  : WER.OS.Branch  
Value: vb_release  

Key  : WER.OS.Timestamp  
Value: 2019-12-06T14:06:00Z  

Key  : WER.OS.Version  
Value: 10.0.19041.1  

FILE_IN_CAB: 101022-18703-01.dmp

BUGCHECK_CODE: 124

BUGCHECK_P1: 4

BUGCHECK_P2: ffff9f0fb17dd028

BUGCHECK_P3: 0

BUGCHECK_P4: 0

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
fffff8066d880cc8 fffff806680b44da : 0000000000000124 0000000000000004 ffff9f0fb17dd028 0000000000000000 : nt!KeBugCheckEx
fffff8066d880cd0 fffff80665fa15b0 : 0000000000000000 ffff9f0fb17dd028 ffff9f0fb18084b0 ffff9f0fb17dd028 : nt!HalBugCheckSystem+0xca
fffff8066d880d10 fffff806681b662e : 0000000000000000 fffff8066d880db9 ffff9f0fb17dd028 ffff9f0fb18084b0 : PSHED!PshedBugCheckSystem+0x10
fffff8066d880d40 fffff8066bc939b3 : 0000000000000001 0000000000000001 ffff9f0fb18064b0 ffff9f0fb17d80d0 : nt!WheaReportHwError+0x46e
fffff8066d880e20 fffff8066bc941a6 : ffff8c001ddbfb00 fffff8066d880ec0 ffff8c001ddbfbf0 ffff9f0fb111c000 : pci!ExpressRootPortAerInterruptRoutine+0x26b
fffff8066d880e80 fffff8066bc94269 : ffff8c001ddbfb40 fffff80667f2a481 0000000000000000 ffff9f0fb1105000 : pci!ExpressRootPortInterruptRoutine+0x46
fffff8066d880ee0 fffff80667f3c9c1 : ffff9f0fb1ea0f43 fffff80600400a02 fffff8066c986ed0 0000000000006101 : pci!ExpressRootPortMessageRoutine+0x9
fffff8066d880f10 fffff80667e08a45 : 0000000000000008 fffff8066d880f20 000000000000000c ffffca6a7a8c5703 : nt!KiInterruptMessageDispatch+0x11
fffff8066d880f40 fffff80667ffa7cf : fffff8066d871a50 ffff8c001ddbfb40 00000000000007dc 000002442654467e : nt!KiCallInterruptServiceRoutine+0xa5
fffff8066d880f90 fffff80667ffaa97 : fffff80664c65180 0000000000000001 0000000000040046 fffff80667ed3158 : nt!KiInterruptSubDispatch+0x11f
fffff8066d8719d0 fffff80667ffcafa : 0000000000000000 fffff80668927a00 ffff9f0fb831b080 00000000000007dc : nt!KiInterruptDispatch+0x37
fffff8066d871b60 0000000000000000 : fffff8066d872000 fffff8066d86b000 0000000000000000 0000000000000000 : nt!KiIdleLoop+0x5a

MODULE_NAME: GenuineIntel

IMAGE_NAME: GenuineIntel.sys

STACK_COMMAND: .cxr; .ecxr ; kb

FAILURE_BUCKET_ID: 0x124_4_GenuineIntel_PCIEXPRESS_RECEIVER_OVERFLOW_IMAGE_GenuineIntel.sys

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {292b172a-d242-4fa5-ed33-089eb4b12cc5}

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

.............................................................................................................................................................................................................................................................................................................

Thanks & Regards,
Apurv

Windows 10
Windows 10
A Microsoft operating system that runs on personal computers and tablets.
10,848 questions
0 comments No comments
{count} votes

3 answers

Sort by: Most helpful
  1. Dave Patrick 426.2K Reputation points MVP
    2022-10-10T19:35:00.567+00:00

    You can follow along here.
    https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x124---whea-uncorrectable-error

    --please don't forget to upvote and Accept as answer if the reply is helpful--


  2. Docs 15,231 Reputation points
    2022-10-11T07:20:44.63+00:00

    BSOD with bugcheck WHEA 124 are almost always caused by malfunctioning hardware.

    Other causes could be overclocking, thermal problems, and very rarely misbehaving drivers.

    Log files can be collected then scanned and read to see if any problems were already reported.

    If the problem is hardware then the cost of servicing + refurbished hardware must be compared to the cost of a new computer.

    .
    .
    .
    .
    .

    Please remember to vote and to mark the replies as answers if they help.

    On the bottom of each post there is:

    Propose as answer = answered the question

    On the left side of each post there is /\ with a number: click = a helpful post
    .
    .
    .
    .
    .


  3. Docs 15,231 Reputation points
    2022-10-11T22:21:34.15+00:00

    It is rare to be able to use Windows to identify the malfunctioning hardware causing BSOD bugcheck 124.

    Often software stress tests are used on CPU and GPU.
    However swap testing is typically required to identify malfunctioning hardware.
    There are very few hardware components on a laptop that can be swap tested.
    Also there is no software test for the motherboard.

    Windows may have found some problems and recorded them in the log files.

    Please run the V2 log collector and post a share link into this thread using one drive, drop box, or google drive.

    https://www.tenforums.com/bsod-crashes-debugging/2198-bsod-posting-instructions.html

    https://www.elevenforum.com/t/bsod-posting-instructions.103/

    .
    .
    .
    .
    .

    Please remember to vote and to mark the replies as answers if they help.

    On the bottom of each post there is:

    Propose as answer = answered the question

    On the left side of each post there is /\ with a number: click = a helpful post
    .
    .
    .
    .
    .

    0 comments No comments