WHEA_UNCORRECTABLE_ERROR

Question

Over last few months, my desktop PC has been randomly crashing with the following error. My windows dump file is showing the following. Can anyone help me determine which hardware failure this is related to?

Microsoft (R) Windows Debugger Version 10.0.22473.1005 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: 
Unable to read NT module Base Name string at 34e99da1`6af7142e - NTSTATUS 0xC0000141
Missing image name, possible paged-out or corrupt data.
Unable to load image Unknown_Module_50a8b0bf`9eb6c4b4, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_50a8b0bf`9eb6c4b4
Debugger can not determine kernel base address
Unable to read NT module Base Name string at 34e99da1`6af7142e - NTSTATUS 0xC0000141
Missing image name, possible paged-out or corrupt data.
Unable to read KLDR_DATA_TABLE_ENTRY at 3a5d3ba8`344224ad - NTSTATUS 0xC0000141
WARNING: .reload failed, module list may be incomplete
Windows 10 Kernel Version 19041 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff800`46e00000 PsLoadedModuleList = 0xfffff800`47a2a2d0
Debug session time: Wed Nov 17 21:18:46.814 2021 (UTC + 8:00)
System Uptime: 0 days 23:23:16.448
Page 9a3e610991 too large to be in the dump file.
Page cf4866fe75 too large to be in the dump file.
Unable to read NT module Base Name string at 34e99da1`6af7142e - NTSTATUS 0xC0000141
Missing image name, possible paged-out or corrupt data.
Unable to load image Unknown_Module_50a8b0bf`9eb6c4b4, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_50a8b0bf`9eb6c4b4
Debugger can not determine kernel base address
Unable to read NT module Base Name string at 34e99da1`6af7142e - NTSTATUS 0xC0000141
Missing image name, possible paged-out or corrupt data.
Unable to read KLDR_DATA_TABLE_ENTRY at 3a5d3ba8`344224ad - NTSTATUS 0xC0000141
WARNING: .reload failed, module list may be incomplete
Loading Kernel Symbols
Unable to read NT module Base Name string at 34e99da1`6af7142e - NTSTATUS 0xC0000141
Missing image name, possible paged-out or corrupt data.
.Unable to read KLDR_DATA_TABLE_ENTRY at 3a5d3ba8`344224ad - NTSTATUS 0xC0000141

Image path too long, possible corrupt data.
Loading unloaded module list
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Missing image name, possible paged-out or corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.
WARNING: .reload failed, module list may be incomplete
For analysis of this file, run !analyze -v
fffff800`471fe04f 440f286190      movaps  xmm12,xmmword ptr [rcx-70h] ds:fffff889`4a77e990=00000000000000000000000000000000

Answer 1

Hi xien86

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.

Answer 2

Hi xien86, glad to help!

Answer 3

Thank you Dave. I will try that.

Answer 4

Hi xien86

Sorry, I was offline.

Your minidump files indicate that it is the device driver (nvlddmkm.sys) on your Nvidia graphics card that is causing the system to crash

You should completely remove the current Nvidia device driver using the widely available free DDU utility, then restart your PC and go to the support page for your PC on the manufacturer's website to download and install their recommended version of the Nvidia device driver.

Answer 5

Thanks Dave. Very much appreciate your offer.

I have zipped the minidump files below. https://drive.google.com/file/d/1JmeOo629I3CsaGPTKCEu4WHYU6-hXdXO/view?usp=sharing

To describe the crashes further. The symptoms seem to be random and can occur at random times even when the computer is idle.

Sometimes I would get a black screen with the fans spinning up to maximum. Sometimes a black screen with fans at normal speed. Sometimes a BSOD with WHEA_UNCORRECTABLE_ERROR and stuck at 0%.