Event ID 20 - WHEA-Logger - AMD Northbridge

Anonymous
2013-01-02T19:01:25+00:00

Since resolving an issue with my ATI Video Driver recently, I have started getting the following errors, once a day, which cause my system to restart unexpectedly.

I believe this to be a driver issue, even though it looks like a hardware issue.

When it happens, I am usually watching TV on it via my XBOX Media Center Extender.

Event ID 20 - WHEA-Logger

A fatal hardware error has occurred.

Component: AMD Northbridge

Error Source: Machine Check Exception

Error Type: HyperTransport Watchdog Timeout Error

Processor APIC ID: 0

The details view of this entry contains further information.

My Computer is a Dell XPS 7100 with an AMD Phenom II X6 1045T Processor and ATI Radeon HD 5700 Series graphics adaptor.

All Dell diagnostics run cleanly and successfully.

Can anyone advise what to do to investigate further please?

Windows for home | Previous Windows versions | Devices and drivers

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

130 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2017-11-23T02:26:22+00:00

    I have the same problem, that starts after the Fall Creators Update.

    A fatal hardware error has occurred.

    Component: AMD Northbridge

    Error Source: Machine Check Exception

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2017-11-23T13:15:29+00:00

    Why isn't anyone giving us any solution?

    Was this answer helpful?

    0 comments
  3. Anonymous
    2017-11-23T14:59:23+00:00

    Does anyone know what triggers this error? Any response will be appreciated

    Was this answer helpful?

    0 comments
  4. Anonymous
    2017-11-27T01:58:34+00:00

    News nothing exciting:

    Since my last post here (11 days ago) I reinstalled the BIOS and updated the AMD drivers. But today the problem has happened again.

    It was the second time that the problem happened shortly after Windows started. But there is no apparent trigger.

    I do not know what to try anymore... Last thing I thought was to reinstall Windows, but it's a lot of work to install and configure all the programs again.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2017-11-27T02:13:06+00:00

    I'm testing Windows 10 Creators Update today and I'll not update to FCU. I'll post here the results later.

    Was this answer helpful?

    0 comments