Event ID 20 - WHEA-Logger - AMD Northbridge

HAY GUYS GO CHECK OUT ON YOUR SYSTEMS NOW UNDER SYSTEM INFORMATION THE CONFLICTS WITH AMD OR INTEL TO SEE WHAT THE CONFLICTS LIKE AM ADDING HERE IS THE PROBLEM SO GO CHECK OUT ON YOUR SYSTEM NOW OK.

Same issue for me. I've had the HDD and motherboard replaced through warranty. I'm about to get a total laptop replacement... and then I saw this thread.

Does that mean that even if I do get a replacement laptop, I'm STILL going to have the same issue? This is so frustrating.

Log Name:      System

Source:        Microsoft-Windows-WHEA-Logger

Date:          2018-03-12 11:57:55 PM

Event ID:      20

Task Category: None

Level:         Error

Keywords:      

User:          LOCAL SERVICE

Computer:      DESKTOP-T08QT1R

Description:

A fatal hardware error has occurred.

Component: AMD Northbridge

Error Source: Machine Check Exception

Error Type: 11

Processor APIC ID: 0

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>20</EventID>

    <Version>0</Version>

    <Level>2</Level>

    <Task>0</Task>

    <Opcode>0</Opcode>

    <Keywords>0x8000000000000000</Keywords>

    <TimeCreated SystemTime="2018-03-13T02:57:55.687258600Z" />

    <EventRecordID>21346</EventRecordID>

    <Correlation ActivityID="{D00E89F6-7536-4CE2-9E85-F66700684A3D}" />

    <Execution ProcessID="2976" ThreadID="3572" />

    <Channel>System</Channel>

    <Computer>DESKTOP-T08QT1R</Computer>

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

  </System>

  <EventData>

    <Data Name="ErrorSource">3</Data>

    <Data Name="ApicId">0</Data>

    <Data Name="MCABank">4</Data>

    <Data Name="MciStat">0xf2000010000b0c0f</Data>

    <Data Name="MciAddr">0x0</Data>

    <Data Name="MciMisc">0x0</Data>

    <Data Name="ErrorType">11</Data>

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

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

  </EventData>

</Event>

Important news

I've been advised to file a report with Feedback Hub to let Microsoft know about this issue. If you have the same problem, please add some details and upvote to draw attention to it.

Here is a direct link:

https://aka.ms/U6xaqv

(Feedback Hubwill open automatically)

Thank you,

GC.

I have been having this problem since December on three different notebooks (one Asus X555BP and two Acer Aspire E15 E5-553G-T5PB), each one changed by the seller.

The first one, my Asus, presented these anomalous reboots at uneven intervals, the first time a month passed, but it quickly escalated to every morning. It was almost unusable. The second one was replaced after the first time, and the third is the one I'm currently using and with which I experienced this issue this afternoon, again.

I posted a new question here before finding this thread. Alas, I've no solution for you, I'm adding a new reply only to make this thread more visible. At least it's not a hardware problem, though.

An update in early January 2018 resulted in issues with onboard Graphics chips. In particular AMD HD 3000 chipsets. Updating to version 1709 would then prevent you rolling back the Graphics Driver so you would have had to have rolled back the driver before updating from Windows 10 version 1703 to 1709. The rogue update would then automatically install resulting in the resolution changing, large icons and windows not filling the screen etc.

I was unable to find a quick fix at the time and although Microsoft acknowledged the fault they were unable to give a resolution timescale, blaming AMD and vice versa.

I installed Graphics Cards into all computers which resolved this issue. Please note, the Windows update still tries to upgrade these cards but you can install the latest driver from AMD and then block any driver updates from Windows without permission.

Please note that this issue is completely separate from the Northbridge Error issue resulting in computer restarts or freezing.