- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have Xeon E5 2690 V4 x 2 with C610 chipset runinng Windows 10 Pro version 10.0.19045.
Somehow I have device with no driver. Device manager says it is performance counter.
I have been looking for the driver but I cannot find any.
The information of the device is "PCI\VEN_8086&DEV_8D23&SUBSYS_00000000&REV_05".
So, this is Intel's device but no result came back even though searching in the Intel support page.
Does anyonw know how to solve this situation?
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello HarryK,
Thank you for posting in the community!
To ensure you receive the most specialized assistance, we have a dedicated forum that addresses these specific concerns. Therefore, I will be moving this discussion to our Server Forum. This will allow our knowledgeable community and experts to provide you with timely and accurate solutions.
Best regards,
Norman S.
Intel Customer Support Engineer
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi HarryK,
Thank you for trusting Intel with your business. As with all good things, your product has reached the end of its interactive technical support life. However, you can find [Intel® Xeon® Processor E5-2690 v4 (35M Cache, 2.60 GHz)] recommendations at Intel Community forums and additional information at the Discontinued Products website. It is our pleasure to continue to serve you with the next generation of Intel innovation at Intel.com.
Please find the attached PCN document:
https://cdrdv2-public.intel.com/809759/PCN116910-01.pdf
Regards,
Sazzy_Intel
Intel Customer Support Technician
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thank you very much for your reply.
Does it mean there will be no other information given for this question in this forum?
I should be issuing the another query to other forum?
I just simply want to where I can get the driver of DEV_8D23 of Intel for Windows10 which I do not know that is the special device for Xeon e5 or not.
Is there any possibility to get any information here?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
No, don't worry about the forum. The (lack of) handling of discontinued products is awful - and at a time when Intel needs to be demonstrating top notch customer support. Idiocy.
To your problem, have you tried installing the Chipset Device Software (a.k.a. INF Update) package for your motherboard/system? I believe this should resolve the device in question.
Best way to install this package, which ensures all devices are updated, is as follows
- Download the ZIP file from the motherboard/system manufacturers website.
- Extract this ZIP file to a temporary folder.
- Open a Command window and set the current directory to this temporary folder.
- Run command ".\SetupChipset.exe -overall".
- Reboot.
- Delete temporary folder.
Hope this helps,
...S
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thank yo very much for your reply.
Actully I have downloaded the original and updated drivers for the motherboard vendor site and installed them.
As the result, only device that no driver applied was DEV_8D23 of VEN_8086.
I tired it again today but situation sustains.
May be it re-installation of Windows10 work for this kind of trouble.
Any idea?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Did you reinstall the Chipset Device Software package using the process I detailed above? If not, try that.
I looked in the C600 Series Chipset datasheet as well as in both volumes of the Xeon E5 v4 Family datasheet. None of these documents list 8D23 as being a valid device identifier, though it does fall in one of the id ranges used by the chipset. I also did a separate search on the web, but got no hits at all. Not trying to cast doubt, but are you sure that this is the device identifier that is appearing?
If you are sure, then I think that the ICS agent (@NormanS_Intel) is going to have to go to the processor team with this query.
...S
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I keep getting "access denied" while typing in. Am I banned?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thank you very much for continuing support for this matter.
Attached image is what I can download from my motherboard site as the updated drivers for Intel. The very bottom one is the chipset drivers v10.1.17667.8082. It contains infinst_autol.exe without manual but not SetupChipset.exe.
It seems like infinst_autol.exe accepts the parameter -overall so I ran "infinst_autol.exe -overall".
But the result is the same.
The second from bottom is IATA_CD.exe.
I also have the original driver & software DVD that contains Chipset INF file. The execution file is infinst_autol.exe but the version is V10.1.2.77(looks this one is newer).
The image "proterty.jpg" attached is the screen shot of property/detail of the device from device manager after I ran the above command and reboot the system.
The strings next to the "other device" symbol is performance counter in Japanese which may not represent what it is...
I googled DEV_8D23 but no result returned.
I also searched DEV_8D23 @ https://www.catalog.update.microsoft.com/Home.aspx though no results given.
I tried numbers of different driver updater software and Microsoft Update for potential resolution to find the driver for this device.
That's where I am now.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
As I said, @NormanS_Intel will need to go back to the development team and find out what this device actually is and why it isn't being resolved (or what secondary package is necessary to resolve it).
...S
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I am not quite sure but I should post this matter to @NormanS_Intel community separately, correct?
Sorry for my ignorants and lack of comprehension to the post.

- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page