WHEA_UNCORRECTABLE_ERROR – No Trail to Determine Cause

Topic

New Reply

I have a Lenovo laptop that started giving a BSOD with WHEA_UNCORRECTABLE_ERROR and stopping. I can’t point to a recent driver or Windows update that would be causing this issue. The most frustrating aspect is that when the problem occurs there is no dump file created. There is just an event log stating an error occurred attempting to create the dump file.

I have done the following steps to try and determine the problem:

chkdsk, scannow and dism – there are no corrupt components or disk issues. There are no events prior to the crash indicating a problem.

Reset bios – the CPU is not being overclocked (and was not before the trouble started)

Memory test – no issues found.

Lenovo utilities – no issues found for memory, CPU, disk, fan, display, etc.

The problem does not seem to occur if the laptop sits idle. There must be some action taking place by the user to trigger it. It has not occurred thus far in Safe Mode or running the Lenovo utilities from a boot USB.

Based on the only clue I have – failure to create a dump file – perhaps it is a connection issue between the power supply and the internal SSD or the power supply itself?

Looking for methods to determine what the failure is.

Reply | Quote

Replies

Do you have a Restore Point before you started having problems?
Do you have a full disk image backup you can restore?
Open Device Manager – are there errors on any of the devices?

Reply | Quote

dwhitejazz wrote:

It has not occurred thus far in Safe Mode…

That right there suggests that the problem is most likely due to a problem with a driver for a piece of hardware. In Safe Mode, a great many drivers aren’t loaded, only the bare bones ones. So, as @PKCano said above

PKCano wrote:

Open Device Manager – are there errors on any of the devices?

Reply | Quote

There are no errors with any devices in Device Manager.

Moderator’s Note: Caught in spam bucket.

Reply | Quote

dwhitejazz wrote:

BSOD with WHEA_UNCORRECTABLE_ERROR and stopping. I can’t point to a recent driver or Windows update that would be causing this issue. The most frustrating aspect is that when the problem occurs there is no dump file created

WHEA_UNCORRECTABLE_ERROR = your hardware is self-reporting an error detected, usually reported by the CPU but not necessarily the CPU, or reporting hardware, as the root cause.

No dump file indicates that the hard disk/SSD, perhaps page file, is the likely candidate.

Can you access and give the full event log details?

Reply | Quote

volmgr: Dump file creation failed due to error during dump creation.

Event xmlns=http[://]schemas[dot]microsoft.com/win/2004/08/events/event

System Provider=volmgr

EventID Qualifiers=49156161

EventID Version 0

Version Level 2

Level Task 0 Opcode 0

Opcode Keywords 0x80000000000000

Keywords

TimeCreated

SystemTime=2024-08-29T19:37:26.0055823Z

EventRecordID 136925

EventRecordID Correlation

Execution

ProcessID=4

ThreadID=”412

Channel

System

Channel

Computer BeckyDAW

Computer Security System-EventData

Data

\Device\HarddiskVolume3

Data

Binary 000000000100000000000000A10004C000000400010000C000000000000000000000000000000000

Binary

EventData

Event

A corrupt paging file?

Moderator’s Note: Caught in spam bucket due to excessive HTML coding making the post nearly impossible to read. Please use the “text” tab when posting text copied from an event log or a dump file. URL edited to prevent being clickable. This is a near duplicate of the post below.

Reply | Quote

volmgr: Dump file creation failed due to error during dump creation.

http[://]schemas.microsoft[dot]com/win/2004/08/events/event

Provider Name=volmgr

EventID Qualifiers=49156161

EventID Version

Version Level 2

Level Task Opcode 0

Opcode Keywords 0x80000000000000

TimeCreated

SystemTime=2024-11-26T19:47:14.1793445Z

EventRecordID154680

EventRecordID

Correlation

Execution

ProcessID=4

ThreadID=392

Channel

System

Channel

Computer BeckyDAW

Computer Security System Event Data

Data

\Device\HarddiskVolume3

Binary

000000000100000000000000A10004C000000600010000C000000000000000000000000000000000

Corrupt paging file – re-create it somehow?

Moderator’s Note: Caught in spam bucket due to excessive HTML coding making the post nearly impossible to read. Please use the “text” tab when posting text copied from an event log or a dump file. URL edited to prevent being clickable.

Reply | Quote

Error during dump creation could be a disk error.

Do you have a recent image backup? Do you have another machine that you can connect the disk to to perform a backup?
Have you tried reseating memory and disk connections?
Is the machine full of dust?

cheers, Paul

Reply | Quote

So chkdsk came up clear yet the error points to a fault on volume ID 3. There are a few other possibilities other than a bad drive or paging file.

Best work through the steps with the team at Sysnative, it beats thrashing around based on little more than guesswork; follow the instructions here to enable them to check the relevant logs and details in the most logical manner.

1 user thanked author for this post.

RetiredGeek

Reply | Quote