Avatar of David Haycox
David Haycox
Flag for United Kingdom of Great Britain and Northern Ireland asked on

How to identify component causing "bus fatal error" on Dell PowerEdge T110

A Dell PowerEdge T110 server running Server 2009 R2 has been rebooting because of a BugCheck.  The Dell hardware logs show the following (errors are the same each time the server reboots):

	Tue Mar 21 12:07:51 2017	A runtime critical stop occurred.	
	Tue Mar 21 12:07:24 2017	An OEM diagnostic event occurred.
	Tue Mar 21 12:07:24 2017	A bus fatal error was detected on a component at bus 0 device 28 function 5.	
	Tue Mar 21 12:07:24 2017	A bus fatal error was detected on a component at slot 4.

Open in new window

We have remote access to the server only.  Without physical access, how can we determine which component is causing the problem?

Thanks in advance for any assistance.

Avatar of undefined
Last Comment
David Haycox

8/22/2022 - Mon
Dr. Klahn

So far as I know there's not a utility to show PCI bus slot information.  PCI-Z comes close to what you need, but it does not report slot numbers.

You can get the information out of the Registry, but it is troublesome and requires exact knowledge of what is installed and where ... in other words, you need to already know the information you're trying to find out.

Open the Registry Editor and drill down to HKLM/System/CurrentControlSet/Enum/PCI.  Under this you'll find many, many keys corresponding to every PCI device which is now or has ever been installed in this system.  The LocationInformation field contains information about where that device was when it was last installed in the system.

PCI enumeration in Registry
Here's the nasty part.  Nothing indicates whether that device is in the system.  You have to know what is installed in that slot to know whether that device is installed in that slot.  This could be workable on a system that has never changed since the original installation, but on most systems things have been swapped back and forth, devices have changed, and each slot might have ten potential candidates that have been in that location.  So on most systems, this is not a workable way to find out what's in the system without seeing what's in that slot.  And then of course you already know what's in the slot.
David Haycox

Fantastic, thanks.  By drilling down through the device manager I found this though:

Device Manager extract
So that's not a removable device in any case, it's on the system board I would say.  So if there's a fault with that it'll be either drivers, firmware or a board change?
Dr. Klahn

Log in or sign up to see answer
Become an EE member today7-DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform
Sign up - Free for 7 days
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
ask a question
David Haycox

Great, thanks.  We'll get slot 4 checked out.
Your help has saved me hundreds of hours of internet surfing.

Pity this was closed so quickly, was hoping someone would have ppsted the Linux method and also the generic Dell method of identifying the device. A lot of the time you can't even check via the OS as it won't boot with a PCIe error and all you get is POST error or the LCD display to go on.
David Haycox

Oops, can ask another question easily enough if you think it will be worth it.
David Haycox

Looks like PCI slot 4 is a USB3.0 controller we fitted recently in order to improve backup / restore speed.  We'll investigate it further.
Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.

PCIe 3.0 card?
David Haycox

This one: https://www.startech.com/uk/Cards-Adapters/USB-3.0/Cards/2-Port-USB-3-PCI-Express-Card-with-SATA-Power~PEXUSB3S23

We've fitted many of these to different servers; this will be the first problem.