WHEA-Logger says Fatal Hardware Error Occurred

Christopher Alex 0 Reputation points
2024-05-09T22:43:44.5666667+00:00

Hello, I've been having a persistent error where my computer crashes when it's put to sleep. In the event viewer, I see the following fatal error but haven't been able to debug it. Any help would be appreciated. Thank you!

System specs:

RAM: 64.0 GB (63.9 GB usable)

CPU: Intel(R) Core(TM) i7-10875H CPU @ 2.30GHz 2.30 GHz

Windows 10 Home, version 22H2, OS Build:19045.4291

CRASH LOG:

Log Name: System

Source: Microsoft-Windows-WHEA-Logger

Date: 5/9/2024 3:31:47 PM

Event ID: 1

Task Category: None

Level: Error

Keywords: WHEA Error Event Logs

User: LOCAL SERVICE

Computer: z7

Description:

A fatal hardware error has occurred. A record describing the condition is contained in the data section of this event.

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

<System>

<Provider Name="Microsoft-Windows-WHEA-Logger" Guid="{c26c4f3c-3f66-4e99-8f8a-39405cfed220}" />

<EventID>1</EventID>

<Version>0</Version>

<Level>2</Level>

<Task>0</Task>

<Opcode>0</Opcode>

<Keywords>0x8000000000000002</Keywords>

<TimeCreated SystemTime="2024-05-09T22:31:47.0016998Z" />

<EventRecordID>110453</EventRecordID>

<Correlation ActivityID="{3f9d3a77-bc88-4d9b-b450-44edbaedf670}" />

<Execution ProcessID="5040" ThreadID="5848" />

<Channel>System</Channel>

<Computer>z7</Computer>

<Security UserID="S-1-5-19" />

</System>

<EventData>

<Data Name="Length">298</Data>

<Data Name="RawData">435045521002FFFFFFFF010001000000070000002A010000121E1600090518143C60C1835215A74887D114D9467D7765000000000000000000000000000000008D7C2157665EFB4480339B74CACEDF5B03F83300702E884E992C6F26DAF3DB7A55BEC9C77AA1DA01080000000000000000000000000000000000000000000000C8000000620000000003020001000000000000000000000000000000000000000000000000000000000000000000000001000000000000000000000000000000000000000000000053544F52504F525401006200000003000100080011000000C09B751EC866EB119775806E6F6E6963730074006F0072006E0076006D006500000000000000000000000000000000004E564D6520202020004E564D65204341352D3844313032342000</Data>

</EventData>

</Event>

Windows 10
Windows 10
A Microsoft operating system that runs on personal computers and tablets.
10,814 questions
Windows Hardware Performance
Windows Hardware Performance
Windows: A family of Microsoft operating systems that run across personal computers, tablets, laptops, phones, internet of things devices, self-contained mixed reality headsets, large collaboration screens, and other devices.Hardware Performance: Delivering / providing hardware or hardware systems or adjusting / adapting hardware or hardware systems.
1,557 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Wesley Li 5,330 Reputation points
    2024-05-10T09:35:12.4066667+00:00

    Hello

    The error message you provided indicates a fatal hardware error, but it doesn't specify the exact component causing the issue. However, WHEA (Windows Hardware Error Architecture) errors are often related to hardware issues such as CPU, RAM, or motherboard problems. Since the error occurs when your computer is put to sleep, it's possible that a specific component is failing to enter sleep mode properly.

    Here are some steps you can take to troubleshoot and potentially resolve the issue:

    Check BIOS/UEFI Settings: Ensure that your BIOS/UEFI settings are configured correctly, especially those related to power management and sleep states. Consider updating your BIOS/UEFI firmware to the latest version if available.

    Test RAM: Run a memory diagnostic tool (e.g., Windows Memory Diagnostic, MemTest86) to check for any issues with your RAM. Faulty RAM can cause various hardware errors and system instability.

    Check CPU Temperatures: Monitor your CPU temperatures to ensure they are within safe limits, especially when the system is under load. Overheating can sometimes trigger hardware errors.

    Hardware Testing: If possible, try testing individual hardware components (e.g., CPU, RAM, motherboard) in another system or replace them with known-good components to isolate the faulty hardware.