Results 1 to 10 of 10
  1. #1
    New Lounger
    Join Date
    Dec 2009
    Location
    Smack Dab in the Middle
    Posts
    20
    Thanks
    4
    Thanked 1 Time in 1 Post

    Unable to locate what Intel device 0xA111 is. Anyone?

    I'm getting a string of errors today and in Device Mgr I'm not finding anything complaining. Checked for devices by type and connection as well as looking for the memory location in resource by type and connection.

    This is a Dell Prec 3520 running Win10 Pro and I've updated the drivers except for the Bios update. (The Bios update wouldn't load under WinPE).
    The Vendor is Intel (0x8086) but I can't find any listings for a device (0xA111) associated with Intel. (Gigabyte seems to have this device ID as a webcam)

    Log Name: System
    Source: Microsoft-Windows-WHEA-Logger
    Date: 5/10/2017 11:31:01 AM
    Event ID: 17
    Task Category: None
    Level: Warning
    Keywords:
    User: LOCAL SERVICE
    Computer: l
    Description:
    A corrected hardware error has occurred.


    Component: PCI Express Root Port
    Error Source: Advanced Error Reporting (PCI Express)


    Busevice:Function: 0x0:0x1C:0x0
    Vendor IDevice ID: 0x8086:0xA111
    Class Code: 0x30400


    The details view of this entry contains further information.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    <System>
    <Provider Name="Microsoft-Windows-WHEA-Logger" Guid="{C26C4F3C-3F66-4E99-8F8A-39405CFED220}" />
    <EventID>17</EventID>
    <Version>0</Version>
    <Level>3</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2017-05-10T17:31:01.818622000Z" />
    <EventRecordID>3728296</EventRecordID>
    <Correlation ActivityID="{6D5F632D-A95C-4734-A858-6AE66363B638}" />
    <Execution ProcessID="1404" ThreadID="14668" />
    <Channel>System</Channel>
    <Computer>LT-DEL-3520-</Computer>
    <Security UserID="S-1-5-19" />
    </System>
    <EventData>
    <Data Name="ErrorSource">4</Data>
    <Data Name="FRUId">{00000000-0000-0000-0000-000000000000}</Data>
    <Data Name="FRUText">
    </Data>
    <Data Name="ValidBits">0xdf</Data>
    <Data Name="PortType">4</Data>
    <Data Name="Version">0x101</Data>
    <Data Name="Command">0x10</Data>
    <Data Name="Status">0x406</Data>
    <Data Name="Bus">0x0</Data>
    <Data Name="Device">0x1c</Data>
    <Data Name="Function">0x0</Data>
    <Data Name="Segment">0x0</Data>
    <Data Name="SecondaryBus">0x0</Data>
    <Data Name="Slot">0x0</Data>
    <Data Name="VendorID">0x8086</Data>
    <Data Name="DeviceID">0xa111</Data>
    <Data Name="ClassCode">0x30400</Data>
    <Data Name="DeviceSerialNumber">0x0</Data>
    <Data Name="BridgeControl">0x0</Data>
    <Data Name="BridgeStatus">0x0</Data>
    <Data Name="UncorrectableErrorStatus">0x0</Data>
    <Data Name="CorrectableErrorStatus">0x1000</Data>
    <Data Name="HeaderLog">00000000000000000000000000000000</Data>
    <Data Name="Length">672</Data>
    <Data Name="RawData">435045521002FFFFFFFF020002000000020 00000A0020000011F11000A051114000000000000000000000 0000000000000000000000000000000000000000000BDC407C F89B7184EB3C41F732CB571311FC093CF161AFC4DB8BC9C4DA F67C1040E2F51471CC5D201000000000000000000000000000 00000000000000000000010010000D00000000003000001000 00054E995D9C1BB0F43AD91B44DCB3C6F35000000000000000 00000000000000000020000000000000000000000000000000 000000000000000E0010000C00000000003000000000000ADC C7698B447DB4BB65E16F193C4F3DB000000000000000000000 00000000000030000000000000000000000000000000000000 000000000DF000000000000000400000001010000100006040 0000000868011A1000403001C0000000000000000000000000 0000000000000108042010180000027001100134C720243001 17000B22C00000040010800000000000000370800000004000 00000000000000000000000000000000001000114000000000 00001001100060000100000002000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000004301000000000000000200000 0000000E906090000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 000000000</Data>
    </EventData>
    </Event>
    Last edited by Lex Rex; 2017-05-12 at 11:33. Reason: removed computer name specifics.

  2. #2
    New Lounger
    Join Date
    Dec 2009
    Location
    Smack Dab in the Middle
    Posts
    20
    Thanks
    4
    Thanked 1 Time in 1 Post
    I was able to update the bios and the errors are no longer generated but I'm still curious what device was causing all of the trouble. I suppose I could call Dell but in past experience I've found that they don't have a lot more information then I normally do by searching the internet.

  3. #3
    Super Moderator
    Join Date
    Aug 2012
    Location
    Durham UK
    Posts
    7,467
    Thanks
    181
    Thanked 984 Times in 936 Posts
    There are quite a few links when you Google whea logger event id 17 that may help.

    Normally when you have VEN & DEV Nos you can enter them into this PCI Database - http://pcidatabase.com/ but when you enter 8086 and A111 it returns nothing found.

  4. The Following User Says Thank You to Sudo For This Useful Post:

    Lex Rex (2017-05-11)

  5. #4
    New Lounger
    Join Date
    Dec 2009
    Location
    Smack Dab in the Middle
    Posts
    20
    Thanks
    4
    Thanked 1 Time in 1 Post
    Thanks Sudo, pcidatabase.com has been a friend to me for some years now when I used to provision a new computer using Kace I could install the specific drivers for the computer during the Windows installation. Sometimes Kace wouldn't find the driver through it's (Dell) database and I could find them there. The fingerprint readers always seemed to throw a flag during the driver installs and knowing/finding the device ID numbers were priceless in getting the computer setup.
    This is the first time I've run into a device that isn't listed anywhere.

  6. #5
    Super Moderator
    Join Date
    Aug 2012
    Location
    Durham UK
    Posts
    7,467
    Thanks
    181
    Thanked 984 Times in 936 Posts
    As a BIOS update fixed it, it mustn't have been a device driver in the normal sense.

    Did you do a Google search and were any of the links of help in understanding why you got that error ?

  7. #6
    New Lounger
    Join Date
    Dec 2009
    Location
    Smack Dab in the Middle
    Posts
    20
    Thanks
    4
    Thanked 1 Time in 1 Post
    Unfortunately not. The laptop has been running fine and to be honest I just stumbled on the event while I was comparing another computer's event log with my computer's event log to try to diagnose the other computer's issue. I have no idea how long it has been triggering that warning since it filled the log. I checked Windows\System32\winevt\ for anything further and outside that event everything looks like a brand new 3 month old laptop. Reliability Monitor never indicated a problem - go figure. taskmgr didn't even indicate anything exceptional going on with the CPU only running about 3% and Net and Disk @ 0%.

    I'm sure I'm making too much out of this but in this day and age where the average malicious code writer is smarter then me I get a little tense when I can't find out what something is with the wealth of information that is online.

  8. #7
    WS Lounge VIP mrjimphelps's Avatar
    Join Date
    Dec 2009
    Location
    USA
    Posts
    3,920
    Thanks
    517
    Thanked 465 Times in 434 Posts
    Quote Originally Posted by Sudo View Post
    There are quite a few links when you Google whea logger event id 17 that may help.

    Normally when you have VEN & DEV Nos you can enter them into this PCI Database - http://pcidatabase.com/ but when you enter 8086 and A111 it returns nothing found.
    Interestingly, if you enter 8086 as the vendor, and leave the device field blank, you get Intel. (I wonder how Intel got the number 8086?)

  9. #8
    Administrator Rick Corbett's Avatar
    Join Date
    Dec 2009
    Location
    South Glos., UK
    Posts
    3,462
    Thanks
    153
    Thanked 942 Times in 757 Posts
    Quote Originally Posted by mrjimphelps
    I wonder how Intel got the number 8086?
    Because Intel released the 8086 microprocessor (in 1978) and chose that vendor ID before anyone else.

  10. #9
    WS Lounge VIP mrjimphelps's Avatar
    Join Date
    Dec 2009
    Location
    USA
    Posts
    3,920
    Thanks
    517
    Thanked 465 Times in 434 Posts
    I knew that they sold the 8086 processor -- I was trying to be humorous by saying that. Even though the 8088 was the first big hit of the x86 line, there were lots of others which all ended in 6, and that's likely why they chose 8086 rather than 8088.

    To let you know when my first IT job was, my boss selected '286' as our office alarm code. Also, he had the 286, and I had the 8088. (Bummer!)

  11. #10
    New Lounger
    Join Date
    Dec 2009
    Location
    Smack Dab in the Middle
    Posts
    20
    Thanks
    4
    Thanked 1 Time in 1 Post
    I swear, I did more with my 8088 then I ever did with my 286. BBS's were just a dialup away.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •