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-26T16:15:11+00:00

    Bumping this thread to let microsoft know. Crazy there's no fix as of yet, I was about to send my apu into warranty.

    my specs:

    -A10 7850k

    -getting the issue since black friday.

    I used to never update my pc, but since I bought my WMR  headset and had to install the fall creator's update I now have these sudden error 20 crashes, so I second you guys: the update is the culprit there.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2018-02-21T10:14:29+00:00

    Hello,

    Yes to confirm, my 3 customers have not experienced the restart issue since disabling fast start and fingers crossed, I am not getting the freezing on my FX-6350 PC anymore.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2018-02-21T09:30:15+00:00

    Very glad I found this thread. I had like many others tried everything to no good result, will deactivate fast startup and see what happens.

    To add further evidence to the fall update causing the issue, see below, quite remarkable how obvious it seems now! (1709 installed 31/01 17:02:54), odd how there is one crash reported 4 minutes before this though? (highlighted). 

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2018-02-16T06:21:47+00:00

    "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".  

    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.  

    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.  :)

    After months of searches and even taking my PC to the warranty service, I stumbled upon this thread, turned off fast startup and haven't had a single reboot for 2 weeks now! Whoever came up with this idea is a genius!

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2018-02-15T17:09:18+00:00

    I feel so foolish now. I started getting this problem in the month of December right after the Fall's update. One day my computer refused to boot up ( only LEDs and Fans were working no display output). I thought those restarts finally came to this and fried my MoBo. Bought a new motherboard(same model) and went back to June 2016 build. Tried all I could to not let Windows 10 update automatically. But I was fed up with the constant bothering and did it and BAM the issue again started. MICROSOFT ACTUALLY OWES ME 80$ WTF

    Was this answer helpful?

    0 comments No comments