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 No comments

130 answers

Sort by: Newest
  1. Anonymous
    2018-02-11T18:00:58+00:00

    Adrenalin 18.2 Getting this Issue since november also. Frustrating. Turning off fastboot didn't help.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2018-02-09T11:31:07+00:00

    Yes, that is the one.

    I am trying that fast restart option with 3 customers to see if it resolves issue. Basically disable fast start up in Power Options for 'Choose what the power buttons do'

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2018-02-08T19:03:52+00:00

    Hmm.  We don't use Chrome. It's installed, but we don't use it. So I'm not sure that's related, but we can look to see if turning off its own hardware acceleration features, when it's not running, has any effect.

    Thus far the "non-fast-start" option seems to have solved our problem.  Fingers still crossed though.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2018-02-08T18:26:56+00:00

    I tested all the proposed solutions, with no results, including a fresh install of Windows. What seems to work was disable hardware accelerarion in Google Chrome settings. More than 2 months without a single restart. Today I re-enable that option and my computer restarted again, what seems to prove, at least in my case, that Google Chrome is causing the issue.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  5. Anonymous
    2018-02-08T18:16:39+00:00

    I am not replying to this specific post, but I see no way to just add a fresh post to this thread.   I posted something on page 4 that worked for me.  I haven't updated any drivers or anything, I've just been letting Windows update.  I haven't had the reboot or error message since, and that was in late November, 2017.   Quoted:

    "I had the problem again today, and I came across this possible solution, which may have worked for someone else.

    I turned off "fast startup".  I don't know if this will help or not.  I have not been experiencing this issue often, so I won't know for a while if this helps or not until more time has gone by.  I had this happen on November 20 and then again today.

    To turn off "fast startup",  from within the Control Panel, choose Power Options.   Then Choose what the power button does.  Then "Settings that are currently unavailable", then remove the checkmark from "Turn on fast startup (recommended)".  Save the changes, turn off computer.  Then turn it back on.  Booting up everything takes longer, which might be annoying, but experiencing possible file corruption due to these reboots would be a lot worse, I think.  YMMV. 

    Good luck.  I'll post one way or the other if this works.  I would give it a couple of weeks before I would deem the problem resolved."

    I know with all different configurations of computers, this may not work for everyone, but it did work for me, and it wasn't difficult to do.  :)

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments