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: Most helpful
  1. Anonymous
    2015-05-14T21:02:21+00:00

    Hi, i don't know if you've resolved your problem but i had a similar problem and i found my solution for it so i figured i'd share it with you all! I am using Windows 8.1 with AMD 8370fx CPU and AMD Radeon 290x GPU.

    I experienced frequent but random reboots whenever i used my computer, it could happen after several hours of playing or within 10 minutes from startup and when i checked my windows log i had an issue with my hardware (i thought atleast), it was about my AMD Northbridge, and happend all the time i was crashing, and since i just formated windows and had a new cooling system installed for my CPU i figured it was Hardware related, but i started to see beyond that and ruling out hardware issues after trying several stresstests and such e.x prime95, memtest86 and plugging out and putting back memorycard, GPU etc.

    And i noticed i had another error in my log, the AODdriver 4.2 failed to start. After some reasearch i found that AODdriver was related to AMD overdrive so..

    Solution:

    I did a clean install of ALL my AMD and ATI drivers, unistalled them all with the AMD cleanup tool.

    and reinstalled some (not AMD contolpanel though) with the AMD driver manager but some manually like chipset and such.

    but most important i found my AOD driver was 4.3, but it search for 4.2 which didnt exist.

    So i went in to Regedit.exe, Local machine -> SYSTEM -> Currentcontrolset -> Services -> AODdriver 4.2 and just deleted it. after that i've had nomore crashes after three days and lots of computer time!

    Hope i helped someone since i struggled so long with this!

    Was this answer helpful?

    30+ people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2017-11-27T02:24:21+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".  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.

    Was this answer helpful?

    8 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2013-01-03T11:55:23+00:00

    Hi Rob L,

    I see that you get error Event ID 20 - WHEA-Logger on Windows 8 computer. I will help you with this issue.

    Method 1.

    I would suggest you to update the graphics driver and the chip set driver from the manufacturer’s website and check if that help.

    You may download the drivers here: http://support.amd.com/us/gpudownload/Pages/index.aspx

    Steps to update the driver.

    1-Press Windows key + X and select Device Manager.

    2-Right click graphics driver and select update driver.

    3-Follow the on screen directions to complete and remember to restart the computer.

    Note: Modifying BIOS/ complementary metal oxide semiconductor (CMOS) settings incorrectly can cause serious problems that may prevent your computer from booting properly. Microsoft cannot guarantee that any problems resulting from the configuring of BIOS/CMOS settings can be solved. Modifications of the settings are at your own risk.

    Method 2.

    If the update driver does not help, then you may uninstall the driver and then reinstall it to check if that helps. You may first download the required driver from the manufacturer website and save it before uninstalling the driver from the computer.

    Steps to uninstall the driver.

    1-Press Windows key + X and select Device Manager.

    2-Right click graphics driver and select Uninstall.

    3-Follow the on screen directions to complete and remember to restart the computer.

    Method 3.

    To run the System File Checker you will need to open an elevated Command Prompt. This can be done by:

    • Enter the Start screen
    • Press Windows key + C on your keyboard to show the Charms bar. (If you are using a touch screen: touch the right edge of the screen and swipe your finger toward the center of the screen to show the Charms bar)
    • Click Search
    • Type Command Prompt into the Search field
    • Right click Command Prompt (If you are using a touch screen: Touch and hold your finger to the Command Prompt, slide your finger down until you see an outline around the tile, and finally release your finger from the screen.)
    • Click Run as administrator

    Enter the command: sfc /scannow

    Note: If you are using a touch screen you can open the touch keyboard for the Command Prompt by tapping the keyboard icon displayed on your Taskbar near the System tray.

    Method 4.

    Run a full computer scan with the Microsoft Safety Scanner to make sure that the computer is free from viruses.

    Microsoft Safety Scanner: http://www.microsoft.com/security/scanner/en-us/default.aspx

    Safety Scanner Disclaimer: There could be a loss of data while performing a scan using Microsoft safety scanner to eliminate viruses if any.

    Method 5.

    You may also post this question in this AMD support forums here: http://support.amd.com/us/gpudownload/Pages/index.aspx

    Let us know if you need further help with any windows issue. We will be glad to help.

    Was this answer helpful?

    4 people found 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