Hello there folkes,
I truly hope someone can help me since I'm not much of a wiz when it comes to all this.
Today, 2 weeks after I received my new pc, I randomly got the WHEA UNCORRECTABLE ERROR Blue Screen, and from what I can find via Google, it seems to be either bad hardware, or bad drivers.
I've managed to open up the dump file, and it told me this;
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: ffffa90d88b79028, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000
Arg4: 0000000000000000
So, what I can see and understand from this, it seems my Graphics card may be mounted wrong?
When I bought the computer, I didnt get a new graphics card or new harddisks since I already had them. so, now I worry that I might have borked the installation somehow..
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Heres the full message I got after using "!analyze -v":
I truly hope someone can help me since I'm not much of a wiz when it comes to all this.
Today, 2 weeks after I received my new pc, I randomly got the WHEA UNCORRECTABLE ERROR Blue Screen, and from what I can find via Google, it seems to be either bad hardware, or bad drivers.
I've managed to open up the dump file, and it told me this;
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: ffffa90d88b79028, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000
Arg4: 0000000000000000
So, what I can see and understand from this, it seems my Graphics card may be mounted wrong?
When I bought the computer, I didnt get a new graphics card or new harddisks since I already had them. so, now I worry that I might have borked the installation somehow..
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Heres the full message I got after using "!analyze -v":
Code:
Microsoft (R) Windows Debugger Version 10.0.22549.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff806`0cc00000 PsLoadedModuleList = 0xfffff806`0d82a2d0
Debug session time: Fri Mar 11 17:52:17.058 2022 (UTC + 1:00)
System Uptime: 0 days 4:40:55.635
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.....................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000016`9a6f8018). Type ".hh dbgerr001" for details
Loading unloaded module list
...........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff806`0cff7620 48894c2408 mov qword ptr [rsp+8],rcx ss:ffffe580`14f5acd0=0000000000000124
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
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: ffffa90d88b79028, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000
Arg4: 0000000000000000
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 2171
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 6096
Key : Analysis.Init.CPU.mSec
Value: 811
Key : Analysis.Init.Elapsed.mSec
Value: 443196
Key : Analysis.Memory.CommitPeak.Mb
Value: 99
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: MEMORY.DMP
BUGCHECK_CODE: 124
BUGCHECK_P1: 4
BUGCHECK_P2: ffffa90d88b79028
BUGCHECK_P3: 0
BUGCHECK_P4: 0
HARDWARE_VENDOR_ID: 10DE
HARDWARE_DEVICE_ID: 21C4
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXWINLOGON: 1
PROCESS_NAME: RimWorldWin64.exe
STACK_TEXT:
ffffe580`14f5acc8 fffff806`0d0b442a : 00000000`00000124 00000000`00000004 ffffa90d`88b79028 00000000`00000000 : nt!KeBugCheckEx
ffffe580`14f5acd0 fffff806`0ad415b0 : 00000000`00000000 ffffa90d`88b79028 ffffa90d`88ba64b0 ffffa90d`88b79028 : nt!HalBugCheckSystem+0xca
ffffe580`14f5ad10 fffff806`0d1b636e : 00000000`00000000 ffffe580`14f5adb9 ffffa90d`88b79028 ffffa90d`88ba64b0 : PSHED!PshedBugCheckSystem+0x10
ffffe580`14f5ad40 fffff806`10ef36b3 : 00000000`00000001 00000000`00000001 ffffa90d`88ba44b0 ffffa90d`88bd5010 : nt!WheaReportHwError+0x46e
ffffe580`14f5ae20 fffff806`10ef3ea6 : ffffe580`14dfd800 ffffe580`14f5aec0 ffffe580`14dfd970 0000388e`402d95d5 : pci!ExpressRootPortAerInterruptRoutine+0x26b
ffffe580`14f5ae80 fffff806`10ef3f69 : ffffe580`14dfd8c0 00000125`3741a8f0 ffffe580`14f5afb0 00000000`00000f00 : pci!ExpressRootPortInterruptRoutine+0x46
ffffe580`14f5aee0 fffff806`0cf3b3f1 : 00000000`00000000 ffffa90d`84fec000 00000000`00000286 fffff806`00000002 : pci!ExpressRootPortMessageRoutine+0x9
ffffe580`14f5af10 fffff806`0cede215 : fffff806`12561e30 00000000`00008201 ffffe580`14f41180 ffffe580`14f5afc0 : nt!KiInterruptMessageDispatch+0x11
ffffe580`14f5af40 fffff806`0cff8e4f : ffff8588`b7927ac0 ffffe580`14dfd8c0 00000122`89155d50 fffff806`0cff90ca : nt!KiCallInterruptServiceRoutine+0xa5
ffffe580`14f5af90 fffff806`0cff9117 : 00000124`06b1c810 00000000`00000000 ffff8588`b7927ac0 ffffa90d`b8b1bb50 : nt!KiInterruptSubDispatch+0x11f
ffff8588`b7927a40 00000122`75e1a16a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatch+0x37
00000016`9a8ee340 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00000122`75e1a16a
MODULE_NAME: GenuineIntel
IMAGE_NAME: GenuineIntel.sys
STACK_COMMAND: .cxr; .ecxr ; kb
FAILURE_BUCKET_ID: 0x124_4_GenuineIntel_PCIEXPRESS_VENID_10DE_DEVID_21C4_RECEIVER_OVERFLOW_IMAGE_GenuineIntel.sys
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {e9830829-b293-2ea2-331c-05ac2f35d343}
Followup: MachineOwner
---------
2: kd> !errrec ffffa90d88b79028
===============================================================================
Common Platform Error Record @ ffffa90d88b79028
-------------------------------------------------------------------------------
Record Id : 01d835411fad9c22
Severity : Fatal (1)
Length : 672
Creator : Microsoft
Notify Type : PCI Express Error
Timestamp : 3/11/2022 16:52:17 (UTC)
Flags : 0x00000000
===============================================================================
Section 0 : PCI Express
-------------------------------------------------------------------------------
Descriptor @ ffffa90d88b790a8
Section @ ffffa90d88b79138
Offset : 272
Length : 208
Flags : 0x00000001 Primary
Severity : Fatal
Port Type : Root Port
Version : 1.1
Command/Status: 0x0010/0x0407
Device Id :
VenId:DevId : 8086:7abc
Class code : 030400
Function No : 0x04
Device No : 0x1c
Segment : 0x0000
Primary Bus : 0x00
Second. Bus : 0x00
Slot : 0x0000
Dev. Serial # : 0000000000000000
Express Capability Information @ ffffa90d88b7916c
Device Caps : 00008001 Role-Based Error Reporting: 1
Device Ctl : 0007 ur FE NF CE
Dev Status : 0014 ur FE nf ce
Root Ctl : 0008 fs nfs cs
AER Information @ ffffa90d88b791a8
Uncorrectable Error Status : 00020000 ur ecrc mtlp ROF uc ca cto fcp ptlp sd dlp und
Uncorrectable Error Mask : 00000000 ur ecrc mtlp rof uc ca cto fcp ptlp sd dlp und
Uncorrectable Error Severity : 00062010 ur ecrc MTLP ROF uc ca cto FCP ptlp sd DLP und
Correctable Error Status : 00000000 adv rtto rnro dllp tlp re
Correctable Error Mask : 00000000 adv rtto rnro dllp tlp re
Caps & Control : 00000011 ecrcchken ecrcchkcap ecrcgenen ecrcgencap FEP
Header Log : 00000000 00000000 00000000 00000000
Root Error Command : 00000000 fen nfen cen
Root Error Status : 00000000 MSG# 00 fer nfer fuf mur ur mcr cer
Correctable Error Source ID : 00,00,00
Correctable Error Source ID : 00,00,00
===============================================================================
Section 1 : Processor Generic
-------------------------------------------------------------------------------
Descriptor @ ffffa90d88b790f0
Section @ ffffa90d88b79208
Offset : 480
Length : 192
Flags : 0x00000000
Severity : Informational
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
No valid data fields are present.
Last edited:
Facebook
Twitter
Instagram