[SOLVED] windows 11 fatal error results in crash

Status
Not open for further replies.
Nov 24, 2021
1
0
10
been getting this error before all my crashes, is my ram bad?

"A fatal hardware error has occurred.

Component: Memory
Error Source: Machine Check Exception

The details view of this entry contains further information."

More info:
Log Name: System
Source: WHEA-Logger
Event ID: 46
level: Error
User: LOCAL SERVICE
OpCode: Info

And here is the annoying "details view" as mentioned above:
-System

-Provider
[ Name] Microsoft-Windows-WHEA-Logger
[ Guid] {c26c4f3c-3f66-4e99-8f8a-39405cfed220}

EventID46

Version0

Level2

Task0

Opcode0

Keywords0x8000000000000000

-TimeCreated
[ SystemTime] 2021-11-24T22:03:16.4105273Z

EventRecordID2887

-Correlation
[ ActivityID] {4cf9cdd8-7697-4d29-b910-78942e1176ab}

-Execution
[ ProcessID] 3600
[ ThreadID] 3916

ChannelSystem

ComputerMonke

-Security
[ UserID] S-1-5-19

-EventData

ErrorSource3

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

FRUText

ValidBits0x2

ErrorStatus0x0

PhysicalAddress0x100000100e2bb00

PhysicalAddressMask0x0

Node0x0

Card0x0

Module0x0

Bank0x0

Device0x0

Row0x0

Column0x0

BitPosition0x0

RequesterId0x0

ResponderId0x0

TargetId0x0

ErrorType0

Extended0

RankNumber0

CardHandle0

ModuleHandle0

Length1019

RawData435045521002FFFFFFFF04000100000002000000FB03000009031600180B15140000000000000000000000000000000000000000000000000000000000000000BDC407CF89B7184EB3C41F732CB57131FE6FF5E89C91C54CBA8865ABE14913BBD2371A107FE1D701020000000000000000000000000000000000000000000000A00100005000000000030000010000001411BCA5646FDE4EB8633E83ED7C83B100000000000000000000000000000000010000000000000000000000000000000000000000000000F0010000C00000000003000000000000ADCC7698B447DB4BB65E16F193C4F3DB00000000000000000000000000000000010000000000000000000000000000000000000000000000B0020000240100000003000000000000011D1E8AF94257459C33565E5CC3F7E800000000000000000000000000000000010000000000000000000000000000000000000000000000D4030000270000000003000000000000A13248C3C302524CA9F19F1D5D7723FC000000000000000000000000000000000300000000000000000000000000000000000000000000000200000000000000000000000000000000BBE2000100000100000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000007F010000000000000002010100010000820F80000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000A0000000000000000000000000000000000000000000000000000000000000000000000000000000300000002000000C7084E117FE1D70108000000000000000000000000000000000000000000000035010C00002880BE00BBE2000100000100000000FE0F1AD00A0000000A00000000000000B0000000000000000000000035000000270000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000001B00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000010000000000000000000000FF00000000000000000000000000000000000000000000000000
 
Solution
Most likely. If you have more than one stick of ram, try keeping in only one at a time and trying to isolate which stick could be faulty, and if that comes to no avail, there is a possibility that your ram is faulty. This usually occurs when you have 2 different types of memory in the same system.

eatfood768

Reputable
Aug 24, 2018
8
1
4,515
Most likely. If you have more than one stick of ram, try keeping in only one at a time and trying to isolate which stick could be faulty, and if that comes to no avail, there is a possibility that your ram is faulty. This usually occurs when you have 2 different types of memory in the same system.
 
  • Like
Reactions: FarginOG
Solution
Status
Not open for further replies.