Windows 10: WHEA Logger Error Event 18 with Windows 11. ESET Internet Security appears to be the culprit.

Just curious if anyone has expertise on the WHEA Logger Error Event 18 with Windows 11. I have done a bit of research and troubleshooting surrounding this error message. I had just purchased a new PC on March 20, 2023. After getting this message I returned the unit and received a replacement one. Long story short. I ended up getting 2 new replacement units after my initial purchase. At that point I was able to boot the system up at the store and didn't get the issue. Returning home I began methodically installing software slowly to try and see what might be the culprit. It seems it was actua

:)

 

WHEA logger, event 18

Hi iRicked ,



Welcome to the Microsoft Community Forum.

I hope you're doing well today.

I truly understand that you are having an issue with your PC that crashed out while playing a game. Let's work on this together for us to fix the issue.

I would like to ask , when does this issue started?

You may click the link below showing related issue that you are having, kindly follow the steps from the link.

Whea Logger event 18 - Microsoft Community





We look forward to your response. If you have other clarifications about this matter, you can get back to us by replying to this post.



Sincerely,

Fatima

Microsoft Community

 

WHEA-logger event 18

Hey I experienced this error last night and today and I'm not sure really what to do or how to go about fixing the problem

Log Name: System

Source: Microsoft-Windows-WHEA-Logger
Date: 10/9/2020 7:00:15 AM
Event ID: 18
Task Category: None
Level: Error
Keywords:
User: LOCAL SERVICE
Computer: DESKTOP-QUU67B6
Description:
A fatal hardware error has occurred.

Reported by component: Processor Core
Error Source: Machine Check Exception
Error Type: Cache Hierarchy Error
Processor APIC ID: 11

The details view of this entry contains further information.
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>18</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2020-10-09T11:00:15.7624093Z" />
<EventRecordID>3375</EventRecordID>
<Correlation ActivityID="{f0c443d6-ec0e-4991-bd1c-cc072f069310}" />
<Execution ProcessID="3572" ThreadID="4044" />
<Channel>System</Channel>
<Computer>DESKTOP-QUU67B6</Computer>
<Security UserID="S-1-5-19" />
</System>
<EventData>
<Data Name="ErrorSource">3</Data>
<Data Name="ApicId">11</Data>
<Data Name="MCABank">5</Data>
<Data Name="MciStat">0xbea0000000000108</Data>
<Data Name="MciAddr">0x1007ffac73423d9</Data>
<Data Name="MciMisc">0xd01a0ffe00000000</Data>
<Data Name="ErrorType">9</Data>
<Data Name="TransactionType">2</Data>
<Data Name="Participation">256</Data>
<Data Name="RequestType">0</Data>
<Data Name="MemorIO">256</Data>
<Data Name="MemHierarchyLvl">0</Data>
<Data Name="Timeout">256</Data>
<Data Name="OperationType">256</Data>
<Data Name="Channel">256</Data>
<Data Name="Length">936</Data>
<Data Name="RawData">435045521002FFFFFFFF03000100000002000000A803000008000B00090A14140000000000000000000000000000000000000000000000000000000000000000BDC407CF89B7184EB3C41F732CB57131FE6FF5E89C91C54CBA8865ABE14913BBAA5065582B9ED60102000000000000000000000000000000000000000000000058010000C00000000003000001000000ADCC7698B447DB4BB65E16F193C4F3DB0000000000000000000000000000000001000000000000000000000000000000000000000000000018020000800000000003000000000000B0A03EDC44A19747B95B53FA242B6E1D0000000000000000000000000000000001000000000000000000000000000000000000000000000098020000100100000003000000000000011D1E8AF94257459C33565E5CC3F7E8000000000000000000000000000000000100000000000000000000000000000000000000000000007F010000000000000002010000000000100F87000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000B00000000000000000000000000000000000000000000000000000000000000000000000000000007000000000000000B00000000000000100F870000080C0B0B32D87EFFFB8B170000000000000000000000000000000000000000000000000000000000000000F50157A5EFE3DE43AC72249B573FAD2C03000000000000009F00020600000000D92334C7FA7F00010000000000000000000000000000000000000000000000000200000002000000AA1ED2592B9ED601090000000000000000000000000000000000000005000000080100000000A0BED92334C7FA7F000100000000FE0F1AD0000000000B00000000000000B00005000000004D0000000079000000230000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000001B00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000</Data>
</EventData>
</Event>

 

WHEA-logger events

if it gets really spamy you can turn ASPM off in the bios and disable pci-e power-savings from the power control panel but I would just leave it
the error is literally meaningless the event logger captures thousands of events per-day\
almost all of them the user never needs to worrie about