WHEA_UNCORRECTABLE_ERROR (124)

Question

I've been experiencing system deadlocks/freezes when playing certain games, such as World of Warships and FF14 ever since the last system update. I run every concievable hardware check, fixed windows using DISM, checked memory, ran stress tests on hardware, reinstalled drivers, set my bios to default and made sure my hardware was not overclocked but nothing seems to work.

I've studied the event log for any sign of the cause, but to no avail. My only successful deduction was from scanning the dump files using windows debugging tools. If anyone can help me resolve this problem, I'd very much appreciate it.

The results are here:

Microsoft (R) Windows Debugger Version 10.0.25136.1001 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.

************* Path validation summary ************** Response Time (ms) Location Deferred srv* Symbol search path is: srv* Executable search path is: Missing image name, possible paged-out or corrupt data. Unable to read NonPagedDebugInfo at e5e5e5e5e5e5e5e5 - NTSTATUS 0xC0000141 Unable to load image Unknown\_Module\_e5e5e5e5e5e5e5e5, Win32 error 0n2 *** WARNING: Unable to verify timestamp for Unknown_Module_e5e5e5e5e5e5e5e5 Debugger can not determine kernel base address Missing image name, possible paged-out or corrupt data. Unable to read NonPagedDebugInfo at e5e5e5e5e5e5e5e5 - NTSTATUS 0xC0000141 Unable to read KLDR_DATA_TABLE_ENTRY at e5e5e5e5e5e5e5e5 - NTSTATUS 0xC0000141 WARNING: .reload failed, module list may be incomplete Windows 10 Kernel Version 18362 MP (12 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Edition build lab: 18362.1.amd64fre.19h1\_release.190318-1202 Machine Name: Kernel base = 0xfffff80011e00000 PsLoadedModuleList = 0xfffff80012248190 Debug session time: Thu Jun 25 02:28:28.560 2020 (UTC + 1:00) System Uptime: 13 days 13:15:42.879 Missing image name, possible paged-out or corrupt data. Unable to read NonPagedDebugInfo at e5e5e5e5e5e5e5e5 - NTSTATUS 0xC0000141 Unable to load image Unknown_Module_e5e5e5e5e5e5e5e5, Win32 error 0n2 \*\*\* WARNING: Unable to verify timestamp for Unknown\_Module\_e5e5e5e5e5e5e5e5 Debugger can not determine kernel base address Missing image name, possible paged-out or corrupt data. Unable to read NonPagedDebugInfo at e5e5e5e5e5e5e5e5 - NTSTATUS 0xC0000141 Unable to read KLDR\_DATA\_TABLE\_ENTRY at e5e5e5e5e5e5e5e5 - NTSTATUS 0xC0000141 WARNING: .reload failed, module list may be incomplete Loading Kernel Symbols Missing image name, possible paged-out or corrupt data. Unable to read NonPagedDebugInfo at e5e5e5e5e5e5e5e5 - NTSTATUS 0xC0000141 .Unable to read KLDR\_DATA\_TABLE\_ENTRY at e5e5e5e5e5e5e5e5 - NTSTATUS 0xC0000141

WARNING: .reload failed, module list may be incomplete For analysis of this file, run !analyze -v fffff80011fc23a0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff800178b8cf0=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: ffffd08fa409a038, Address of the nt!_WHEA_ERROR_RECORD structure. Arg3: 0000000000000000 Arg4: 0000000000000000

Debugging Details:

***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.

Missing image name, possible paged-out or corrupt data. Unable to read NonPagedDebugInfo at e5e5e5e5e5e5e5e5 - NTSTATUS 0xC0000141 Unable to read KLDR\_DATA\_TABLE\_ENTRY at e5e5e5e5e5e5e5e5 - NTSTATUS 0xC0000141 WARNING: .reload failed, module list may be incomplete Missing image name, possible paged-out or corrupt data. Unable to read NonPagedDebugInfo at e5e5e5e5e5e5e5e5 - NTSTATUS 0xC0000141 Unable to read KLDR\_DATA\_TABLE\_ENTRY at e5e5e5e5e5e5e5e5 - NTSTATUS 0xC0000141 WARNING: .reload failed, module list may be incomplete Missing image name, possible paged-out or corrupt data. Unable to read NonPagedDebugInfo at e5e5e5e5e5e5e5e5 - NTSTATUS 0xC0000141 Unable to read KLDR\_DATA\_TABLE\_ENTRY at e5e5e5e5e5e5e5e5 - NTSTATUS 0xC0000141 WARNING: .reload failed, module list may be incomplete Missing image name, possible paged-out or corrupt data. Unable to read NonPagedDebugInfo at e5e5e5e5e5e5e5e5 - NTSTATUS 0xC0000141 Unable to read KLDR\_DATA\_TABLE\_ENTRY at e5e5e5e5e5e5e5e5 - NTSTATUS 0xC0000141 WARNING: .reload failed, module list may be incomplete Missing image name, possible paged-out or corrupt data. Unable to read NonPagedDebugInfo at e5e5e5e5e5e5e5e5 - NTSTATUS 0xC0000141 Unable to read KLDR\_DATA\_TABLE\_ENTRY at e5e5e5e5e5e5e5e5 - NTSTATUS 0xC0000141 WARNING: .reload failed, module list may be incomplete Missing image name, possible paged-out or corrupt data. Unable to read NonPagedDebugInfo at e5e5e5e5e5e5e5e5 - NTSTATUS 0xC0000141 Unable to read KLDR\_DATA\_TABLE\_ENTRY at e5e5e5e5e5e5e5e5 - NTSTATUS 0xC0000141 WARNING: .reload failed, module list may be incomplete Missing image name, possible paged-out or corrupt data. Unable to read NonPagedDebugInfo at e5e5e5e5e5e5e5e5 - NTSTATUS 0xC0000141 Unable to read KLDR\_DATA\_TABLE\_ENTRY at e5e5e5e5e5e5e5e5 - NTSTATUS 0xC0000141 WARNING: .reload failed, module list may be incomplete Missing image name, possible paged-out or corrupt data. Unable to read NonPagedDebugInfo at e5e5e5e5e5e5e5e5 - NTSTATUS 0xC0000141 Unable to read KLDR\_DATA\_TABLE\_ENTRY at e5e5e5e5e5e5e5e5 - NTSTATUS 0xC0000141 WARNING: .reload failed, module list may be incomplete Page 1001cf9 too large to be in the dump file. Page 1001cf9 too large to be in the dump file. Missing image name, possible paged-out or corrupt data. Unable to read NonPagedDebugInfo at e5e5e5e5e5e5e5e5 - NTSTATUS 0xC0000141 Unable to read KLDR\_DATA\_TABLE\_ENTRY at e5e5e5e5e5e5e5e5 - NTSTATUS 0xC0000141 WARNING: .reload failed, module list may be incomplete Page 1001cf9 too large to be in the dump file. Page 1001cf9 too large to be in the dump file. Page 1001cf9 too large to be in the dump file. Page 1001cf9 too large to be in the dump file. Missing image name, possible paged-out or corrupt data. Unable to read NonPagedDebugInfo at e5e5e5e5e5e5e5e5 - NTSTATUS 0xC0000141 Unable to read KLDR\_DATA\_TABLE\_ENTRY at e5e5e5e5e5e5e5e5 - NTSTATUS 0xC0000141 WARNING: .reload failed, module list may be incomplete Missing image name, possible paged-out or corrupt data. Unable to read NonPagedDebugInfo at e5e5e5e5e5e5e5e5 - NTSTATUS 0xC0000141 Unable to read KLDR\_DATA\_TABLE\_ENTRY at e5e5e5e5e5e5e5e5 - NTSTATUS 0xC0000141 WARNING: .reload failed, module list may be incomplete Page 1001cf9 too large to be in the dump file. Page 1001cf9 too large to be in the dump file.

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec
Value: 30

Key  : Analysis.DebugAnalysisManager
Value: Create

Key  : Analysis.Elapsed.mSec
Value: 42

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

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

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

Key  : Bugcheck.Code.DumpHeader
Value: 0x124

Key  : Bugcheck.Code.Register
Value: 0x124

Key  : WER.CorruptModuleList
Value: 1

Key  : WER.OS.Branch
Value: 19h1\_release

Key  : WER.OS.Timestamp
Value: 2019-03-18T12:02:00Z

Key  : WER.OS.Version
Value: 10.0.18362.1

FILE_IN_CAB: MEMORY.DMP

BUGCHECK_CODE: 124

BUGCHECK_P1: 4

BUGCHECK_P2: ffffd08fa409a038

BUGCHECK_P3: 0

BUGCHECK_P4: 0

STACK_TEXT:
fffff800178b8ce8 fffff800128ff188 : 0000000000000124 0000000000000004 ffffd08fa409a038 0000000000000000 : 0xfffff80011fc23a0 fffff800178b8cf0 0000000000000124 : 0000000000000004 ffffd08fa409a038 0000000000000000 0000000000000000 : 0xfffff800128ff188 fffff800178b8cf8 0000000000000004 : ffffd08fa409a038 0000000000000000 0000000000000000 fffff80012263d60 : 0x124 fffff800178b8d00 ffffd08fa409a038 : 0000000000000000 0000000000000000 fffff80012263d60 ffffd08fa409a038 : 0x4 fffff800178b8d08 0000000000000000 : 0000000000000000 fffff80012263d60 ffffd08fa409a038 fffff80015d81920 : 0xffffd08f`a409a038

MODULE_NAME: GenuineIntel

IMAGE_NAME: GenuineIntel.sys

STACK_COMMAND: .cxr; .ecxr ; kb

FAILURE_BUCKET_ID: 0x124_4_GenuineIntel__UNKNOWN_IMAGE_GenuineIntel.sys

OS_VERSION: 10.0.18362.1

BUILDLAB_STR: 19h1_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {3ac2a448-0f1c-be1d-61a6-2c69263f9152}

Followup: MachineOwner

Page 1001cf9 too large to be in the dump file. WARNING: Unable to reset page directories

Answer 1

Hi Christopher,

I see the Chipset driver on that support page is very old, download the Intel Driver and Support Assistant from the Intel website and run that to see if it can find a better up to date driver.

Answer 2

Hi Dave,

Thanks for the advice. My main board drivers are https://us.msi.com/Motherboard/X99S-GAMING-7/support here, I'll update my BIOS as soon as I can, which may take a day as I lack the means and experience when it comes to updating BIOS.

Answer 3

Hi Christopher,

That error indicates drive access was the cause of the crash, go to the support page for your PC or 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

Hey Dave.

Thanks for the swift reply, I checked my C:Windows path and could not find a Minidump folder. I did however, experience this from my event logger.

Event 45, volmgr

The system could not sucessfully load the crash dump driver.

Event 46, volmgr

Crash dump initialization failed!

Answer 5

Hi Christopher,

I am Dave, I will help you with this.

Please check to see if your PC is producing any minidump files, 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.