WHEA Logger - A fatal hardware error has occurred

Question

Hi there,

I've been trying to debug a WHEA error that I've gotten randomly since I've built my new PC running Windows 11.

Below are the details of the error from Event Viewer:

- System 

  - Provider 

   [ Name]  Microsoft-Windows-WHEA-Logger 
   [ Guid]  {c26c4f3c-3f66-4e99-8f8a-39405cfed220} 
 
   EventID 46 
 
   Version 0 
 
   Level 2 
 
   Task 0 
 
   Opcode 0 
 
   Keywords 0x8000000000000000 
 
  - TimeCreated 

   [ SystemTime]  2023-07-10T11:41:37.0746924Z 
 
   EventRecordID 19928 
 
  - Correlation 

   [ ActivityID]  {4f3d8e77-beef-453a-b504-2a66390fba4e} 
 
  - Execution 

   [ ProcessID]  8960 
   [ ThreadID]  9768 
 
   Channel System 
 
   Computer PC 
 
  - Security 

   [ UserID]  S-1-5-19 
 

- EventData 

  ErrorSource 3 
  FRUId {00000000-0000-0000-0000-000000000000} 
  FRUText  
  ValidBits 0x2 
  ErrorStatus 0x0 
  PhysicalAddress 0x147102400 
  PhysicalAddressMask 0x0 
  Node 0x0 
  Card 0x0 
  Module 0x0 
  Bank 0x0 
  Device 0x0 
  Row 0x0 
  Column 0x0 
  BitPosition 0x0 
  RequesterId 0x0 
  ResponderId 0x0 
  TargetId 0x0 
  ErrorType 0 
  Extended 0 
  RankNumber 0 
  CardHandle 0 
  ModuleHandle 0 
  Length 1019 
  RawData 435045521002FFFFFFFF04000100000002000000FB03000018290B000A0717140000000000000000000000000000000000000000000000000000000000000000BDC407CF89B7184EB3C41F732CB57131FE6FF5E89C91C54CBA8865ABE14913BB9BFAF87223B3D901020000000000000000000000000000000000000000000000A00100005000000000030000010000001411BCA5646FDE4EB8633E83ED7C83B100000000000000000000000000000000010000000000000000000000000000000000000000000000F0010000C00000000003000000000000ADCC7698B447DB4BB65E16F193C4F3DB00000000000000000000000000000000010000000000000000000000000000000000000000000000B0020000240100000003000000000000011D1E8AF94257459C33565E5CC3F7E800000000000000000000000000000000010000000000000000000000000000000000000000000000D4030000270000000003000000000000A13248C3C302524CA9F19F1D5D7723FC0000000000000000000000000000000003000000000000000000000000000000000000000000000002000000000000000000000000000000002410470100000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000007F010000000000000002040300010000100FA2000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000D000000000000000000000000000000000000000000000000000000000000000000000000000000030000000200000075EB597423B3D9010D000000000000000000000000000000000000000100000059080C06000880B4002410470100000000000000000000000A0000000D00000000000000B00001000000000000000000F9010000030000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000003B00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000010000000000000000000000FF00000000000000000000000000000000000000000000000000 

Answer 1

Hello,

The WHEA (Windows Hardware Error Architecture) error you're encountering can be challenging to diagnose, but I'll do my best to help you understand the information provided in the Event Viewer log.

The Event ID 46 indicates a hardware error event. Here's a breakdown of the information in the log:

ErrorSource: 3

This value represents the source of the error. In this case, it indicates a memory-related error.

FRUId: {00000000-0000-0000-0000-000000000000}

FRU stands for "Field Replaceable Unit." This value represents the specific hardware component associated with the error. In this case, it's not specified or recognized.

ValidBits: 0x2

This value indicates which fields in the error record contain valid information. In this case, the bits 0 and 1 are valid.

ErrorStatus: 0x0

The error status field provides additional information about the error. In this case, the value is 0, indicating no specific error status.

PhysicalAddress: 0x147102400

This value represents the physical memory address associated with the error. It helps identify the location where the error occurred.

PhysicalAddressMask: 0x0

The physical address mask field indicates which bits of the physical address are relevant. In this case, the value is 0, indicating that all bits are relevant.

Node, Card, Module, Bank, Device, Row, Column, BitPosition: 0x0

These fields specify the location of the memory error within the system. In this case, all values are 0, suggesting that the exact location is not specified or recognized.

RequesterId, ResponderId, TargetId: 0x0

These fields identify the components involved in the memory transaction. In this case, all values are 0, suggesting that no specific components are identified.

ErrorType: 0

The error type field indicates the type of error encountered. In this case, the value is 0, which doesn't provide specific information about the error type.

Extended: 0

This field indicates whether the error record contains extended information. In this case, the value is 0, suggesting that there is no extended information available.

RankNumber, CardHandle, ModuleHandle: 0

These fields provide additional identification information about the memory module, card, and rank. In this case, all values are 0, indicating that no specific identification information is available.

Length: 1019

The length field specifies the length of the error record in bytes. In this case, it's 1019 bytes.

RawData: 435045521002FFFFFFFF04000100000002000000FB03000018290B000A07171400000000000000000000000000000000000000

This field contains the raw data associated with the error. It's represented in hexadecimal format and typically requires interpretation based on the hardware manufacturer's specifications.

Based on the provided information, it appears that there was a memory-related error, but the exact details of the error and the hardware component involved are not clear. To further investigate the issue, you may need to gather additional information or consult with the hardware manufacturer or a technical expert who can analyze the raw data and provide more insights.

I used AI provided by ChatGPT to formulate part of this response. I have verified that the information is accurate before sharing it with you.

--If the reply is helpful, please Upvote and Accept as answer--