Menu Close

WHEA Logger Error Event ID 17

How to fix These Errors in your Windows Event Logs

If you have WHEA Logger errors in Windows event viewer, here is how to fix it. ​We are posting this fix as a courtesy, so hope it saves you from hours of frustration. If it works for you drop us a quick email to let us know it helped you. Feel free to send to others here as well.

The QuadStation Traveler

Laptop plus 2 x super thin USB Monitors and it all fits in the tough travel case. Connect a 4 screen via HDMI ! A laptop on a mission:

QuadStation TravelerHardware in this test:

Intel DX58SO motherboard, ATI FireMV 2250 and FirePro 2450 video cards

Before you begin:

  • ​It is critical that you have the correct ATI drivers loaded for your video card or this fix will not work. For example, if you have let Windows install default drivers (WDDM) it will not work.
  • Go to Device Manager/Display Adapter properties and verify that you have the correct drivers loaded before proceeding.
  • There are 2 parts to this fix, make sure you do BOTH parts.

The Problem:

  • ​WHEA LOGGER ERROR 17, 18,19 etc) over and over again in windows/System LOGS sometimes just minutes apart.
  • You could also get other errors in device manager under the SYSTEM DEVICES section in one or MORE of your PCI Express Root Port items.
  • Many posts online reporting this problem with no solution. Updating drivers, bios nothing works but this. ​
  • There are 2 parts to this fix. You will cross reference the Windows log with the bangs in device manager.

How to identify:

​1. First, start by looking at the Windows logs to get more detail. Then open Windows Event Logs/System and locate the WHEA Logger errors. The event ID might be 17, 18, 19 etc or any other number.

2. Next, double click on the error in the logs then click on the DETAILS tab. Expand the SYSTEM details.

3. Look specifically for BUS, DEVICE and FUNCTION numbers. (This is how you will identify which item in device manager is causing the problem.)

4. Leave that open, now open Device manager and scroll down to System Devices section. You will probably see a bang in there that will look something like this but the numbers on the far right will be different. You could have one or more instances. Repeat FIX for each one

a. ‘Intel(r)5520/5500/x58 i/o hub pci express root port 3- 340a’ 

b. ‘Intel(r)5520/5500/x58 i/o hub pci express root port 7- 340e’ etc

Double click on each of these PCI Express Root Port items in device manager and note the LOCATION which will be something like this PCI bus 0, device 3, function 0. Find the one that matches what you found in Windows logs then proceed.

How to Fix It

Fix Part 1:

  1. First, cross reference the error in the Windows system log with the item in device manager with the same BUS, DEVICE, FUNCTION location.
  2. Then double click on that item and go to driver tab and update driver, manually update by click browse, Let me Choose…
  3. From the compatible hardware driver list choose: PCI Express Standard Root Port driver.
  4. Click Next to complete the driver update.

Repeat for EACH of the errors but only if they have a different BUS, DEVICE LOCATION. If they are all the same it is not necessary.

Fix Part 2:

  1. ​Open windows Services (Start menu>Computer > right click > manage > services)
  2. Locate: AMD or ATI External Events Utility 
  3. Right click > Properties > Stop > Select the Startup Type> DISABLE, and make sure on the RECOVERY tab they all say TAKE NO ACTION.
  4. Reboot.

This should take care of it. Keep an eye on your windows event logs. If other errors occur again, repeat process above with the identifier numbers to resolve all errors individually.

NTI QuadStation ComputersMultiple Monitor Computer Systems