Event ID 20 - WHEA-Logger - AMD Northbridge

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.

Hi there, 

Thanks for this.

The system file checker did find a problem "Repairing corrupted file [ml:60{30},l:58{29}]"??\C:\WINDOWS\SysWOW64\en-US"[l:46{23}]"windows.ui.xaml.dll.mui" from store"

It also noted many rows where it said

"[DIRSD OWNER WARNING] ...."

and also many where it said

"Ignoring duplicate ownership for directory "

Do these matter?

I then rebooted and re-ran the file checker, and it has said there are no problems.

I'll now have to wait and see if the problem happens again.

Thanks,

• Rob Lightbody

Since doing this, it has now crashed and restarted TWICE tonight.

Windows 8 has been an unmitigated disaster for me, I wish I hadn't upgraded from Windows 7.  Its been problem after problem.

Last avenue is AMD support, but that doesn't look hopeful.

Hi Rob L,

Thanks for the reply.

I would suggest you to perform the steps mentioned under M1, M2 and M4 from my previous post to let us know the status.

Thanks.

I've done method 1.  No updated driver available.

I've done method 2, it still crashed after I did this.

I've done method 3, it found problems, but then crashed and rebooted twice after that.

I've done method 4, all clear, never had a virus on any PC I've owned.

So I'm on to method 5.  I'm also going to try a beta driver of the next version of the AMD Catalyst driver, which sounds like it might help.