Windows 10: WHEA-Logger crashe

Hello All!My computer has been restarting lately while playing games. Using Event ID, I have notice this error.A fatal hardware error has occurred.Component: MemoryError Source: Machine Check ExceptionThe details view of this entry contains further information.I was wondering if anyone could help me resolve this?Much Thanks

:)

 

WHEA-Logger warning

WHEA-Logger warning constantly

How to fix

 

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 Error 19

When I installed the January 2018 cumulative update, I started getting consistent WHEA-Logger errors about every 60 seconds. Here's what's in the event viewer:

A corrected hardware error has occurred.

Reported by component: Processor Core

Error Source: Corrected Machine Check

Error Type: Internal parity error

Processor APIC ID: 2

I also started getting random blue/green screen crashes. I did a system restore to before the update, and everything went back to normal: no logger errors and no crashes. I waited for the next cumulative update (KB4058258), then installed that figuring that
the problem would be sorted out.

Nope. The logger errors are back. The system hasn't crashed yet, but I'm living in dread. Looks like I'll roll back to the pre-January state so that I can keep working without fearing for loss of data.

Does anyone know a fix/workaround for this? Please don't suggest doing clean Windows install or a reset. In addition to making a mess of things, it's not relevant. This is simple: remove the update and the problem goes away. Apply the update problem comes
back. It's the update. It's not my Windows installation. Thanks!