Intel Chipset Device "Drivers" (= INF files)

sbrocca · April 6, 2017, 11:19pm

Hi Dieter, and thanks for your prompt reply

Mobile 6th/7th Generation Intel(R) Processor Family I/O PMC - 9D21.
Could be useful to know that I recently noticed many WHEA-Logger EventID 17 to happen for both Mobile 6th Generation Intel(R) Processor Family I/O PCI Express Root Port #5 - 9D14 (related to Ethernet network adapter Realtek PCIe GBE Family Controller) and Mobile 6th Generation Intel(R) Processor Family I/O PCI Express Root Port #6 - 9D15 (related to Wireless network adapter Qualcomm Atheros QCA9377).
As a first aid, I have disabled only Port #5 - 9D14 and Ethernet Network Adapter, which I do not use, leaving Port #6 - 9D15 and Wireless Network Adapter.
Obviously, every WHEA-Logger warning about Port #6 - 9D14 have disappeared, and those related to Port #6 - 9D15 still persisted.
Well, 4 days ago, after updating Bios of my laptop Asus X756UX-T4187T to the latest X756UXK-AS304, even the WHEA-Logger EventID 17 related to Port #6 - 9D15 were gone.
I still haven’t (the time for) re-enable the Ethernet Network Adapter, but I guess disappeared even the warnings related to Port #6 - 9D14

So, resuming: these devices, all in the same PCI Express Root in Device Manager:
A. Gave WHEA-Logger EventID 17:
- Mobile 6th Generation Intel(R) Processor Family I/O PCI Express Root Port #5 - 9D14
- Mobile 6th Generation Intel(R) Processor Family I/O PCI Express Root Port #6 - 9D15
B. Claim "Missing driver":
- Mobile 6th/7th Generation Intel(R) Processor Family I/O PMC - 9D21
- Mobile 6th/7th Generation Intel(R) Processor Family I/O SMBUS - 9D23
- Mobile 6th/7th Generation Intel(R) Processor Family I/O Thermal subsystem - 9D31
C. Claim that "isn’t using any resources because it has a problem"
- Mobile 6th/7th Generation Intel(R) Processor Family I/O PMC - 9D21

The latest found over the Asus site: 10.1.1.27 version.

Honestly, I don’t remeber…
Please, consider that my former laptop suddenly died (very unlucked and destructive fall…) and the new one Asus X756UX-T4187T went with W10 onboard; as I use my laptop (with W7) at work, I hadn’t - and haven’t - so much time to spent in learning about new O.S…
So, in a week-end I took my notebook, formatted the HDD (I hate bloatware!) and made a fresh install of the O.S.
The story could become long… In short: Firstly I added a brand new SSD onto the m.2 port (wich is port #1) and made some mess with the UEFI Bios (a new for me as well) to force boot (setted for HDD onto port #0) by SSD.
So I reinstalled the O.S. several times, and I cannot say whether the last one I installed the drivers manually (surely without -overall command) or not.
Anyway, trying to solve recent WHEA-Logger problem, I for sure made the latest esperiments by running the installer.

And that’s it.

Wow, maybe I wrote too much: really thanks for reading all this!

Fernando · April 7, 2017, 11:11am

@sbrocca :
Thanks for your detailed answers.

All the listed devices belong to the "SunrisePoint-LP" platform and are managed by the Intel Chipset Device INF files named "SunrisePoint-LPsystem.inf" (designed for the DeviceIDs 9D14, 9D15, 9D21 and 9D23) and "SunrisePoint-LPSystemThermal.inf" (valid for the DeviceID DEV_9D31). The latest version 10.1.1.42 of the "SunrisePoint-LP" INF files are attached (don’t worry about the shown date, they are brandnew).
According to the text of the related INF files
a) the devices with the following DeviceIDs do not need any driver: 9D21, 9D23 and 9D31 (the fact, that you got a "Missing driver" flag for all of them, indicates, that the correct Intel Chipset INF files have not been installed) and
b) the devices with the following DeviceIDs need a real PCI driver (= *.sys file), which is not part of the Intel Chipset Device Software: 9D14 and 9D15.
So the question regarding the devices with the DeviceIDs 9D14 9D15 is, why the appropriate PCI driver has not been properly installed, and regarding the devices with the DeviceIDs 9D21, 9D23 and 9D31, why the appropriate INF files (see attachment) haven’t been installed.

Your specific problems may be caused by the manufacturer of your notebook. ASUS may have put components into your model X756UX-T4187T, which belong to different Intel chipset variants with the result, that the OS installed "wrong" (not matching) Intel chipset INF files.
Note: I have tried to find out the exact chipset of your ASUS notebook, but I couldn’t get any information about it while browsing the net.
To get rid of the Device Manager messages, I recommend to do a fresh install of Win10 v1703.
Once the OS is up and you have additionally installed all available Windows Updates, have a look into the Device Manager for yellow flagged devices. If you should find any, do a right click onto them, choose the "Update Driver Software" > "Browse my Computer" options and navigate to the INF files I have attached.
Please report here about your results.

SunrisePoint-LP.rar (14.8 KB)

sbrocca · April 7, 2017, 3:22pm

Yep, I agree with you.

Please, let me point out that 9D14 and 9D15 do not seem to have any problems with drivers (better: no problems - or missing driver warning - is shown about them) nowadays: the issues was only with WHEA-Logger EventID 17, that has been luckily resolved by updating Bios. (BTW: I re-enable 9D14 and the related Ethernet Network Adapter: as guessed, no more WHEA-Logger warnings).

As you taught me, this wouldn’t be a real problem, 'cause it’d be just a matter of name showed uncorrectly, right?
So, at the moment I haven’t any real issue related to chipset but 9D21, that "isn’t using any resources because it has a problem".
To be short, I didn’t explain the reason why I am concerned about this device: if I’m not wrong, it is related to PCM - Power Management Controller.
A couple of weeks ago, my notebook frooze while exiting from hybernation state; this happened two or three times.
The examination of dump file revealed the culprit to be Pdc.sys, which is often related to hardware or driver problems.
While I was going through this matter, Asus released X756UXK-AS304 Bios update: as told before, from this update on, my laptop never more freeze. On top, this Bios update solved the mentioned WHEA-Logger problem.
I don’t know if the pcd.sys problem has been actually resolved by updating Bios, or it has been just a coincidence.
And having a problem with a device which is related to Power Management don’t let me feel real sheltered.

I already knew SunrisePoint INF and tried with no result, as "the best driver for this device is already installed" or similar; the same result with the latest ones you kindly attached.
As I am using my laptop at work, I honestly have no chance to do a fresh installa of W10 in a short time.
Anyway, for what I can seee, at present time this matter have no impact on performances and - above all - reliability and stability of my notebook.
Thus, crossing my fingers and keeping in mind: "if it works, do not fix", I would wait and see until all will keep going fine.
Nevertheless, as I am really inquisitive, stubborn and, as told above, not calm enough, I would like at least to know what the heck is this "problem".

Asus is embarrassingly poor of technical info about its product, and I wasn’t able as well to find out the exact chipset model by surfing the web.
Anyway, Speccy shows this about motherboard:
Chipset Vendor: Intel
Chipset Model: ID5904
Chipset Revision: 02
Southbridge Vendor: Intel
Southbridge Model: ID9D58
Southbridge Revision: 21,
and CPUID shows this about chipset:
Northbridge: Intel Kaby Lake rev. 02
Southbridge: Intel Kaby Lake-Y PCH rev. 21

Fernando · April 7, 2017, 4:50pm

@sbrocca :
Thanks for the detailed reply. So obviously all your problems have been solved by a BIOS update (I suspect, that ASUS has corrected the related HardwareIDs).

You have gotten this misleading message, because Intel has put the date 01/01/1970 into all the INF files of the latest Intel Chipset Software Sets and the Windows Operating Systems just read this date and compare it with the date of the currently installed INF file and prefers to keep the seemingly newer "driver" (it is only a text file, no real driver).
Nevertheless you can get the a INF files installed, which I had attached, by forcing the installation (using the "Let me pick…" option, hitting the "Have Disk" button and navigating to the related INF file).

sbrocca · April 7, 2017, 6:05pm

@Fernando :
Thank you again for your promptness and skill: I appreciate your effort to help me, definitely.

I suspect too.

Yes, I understood the matter of the "fake" driver and past date, and did the forced installation in that way.
Anyway, even if the right version 10.1.1.42 is now shown, I still cannot get rid of the last problem, for what the damned 9D21 "isn’t using any resources because it has a problem"…

Fernando · April 7, 2017, 6:18pm

As long as it "isn’t using any resources" (= doesn’t have any negative impact on your system’s performance) and as long your system is running fine, this message shouldn’t matter. I still believe, that the misleading message is caused by ASUS and not by Intel’s Chipset Device INF files.

plutomaniac · April 8, 2017, 2:35pm

Intel Chipset Device Software v10.1.2.84 PV (January 18, 2017)

Details:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35

Intel® Xeon Phi® Processor x200 product family
Intel® Xeon® Processor E7-4800/8800 v4 product family
Intel® Xeon® Processor E7-4800/8800 v3 product family
Intel® Xeon® Processor E7-4800/8800 v2 product family
Intel® Xeon® Processor E7-2600 v4 product family
Intel® Xeon® Processor E5-2600 v4 product family
Intel® Xeon® Processor E5-2600 v3 product family
Intel® Xeon® Processor E5-2600 v2 product family
Intel® Xeon® processor E3-1500 v5 product family
Intel® Xeon® processor E3-1200 v6 product family
Intel® Xeon® processor E3-1200 v5 product family
Intel® Xeon® processor E3-1200 v4 product family
Intel® Xeon® processor E3-1200 v3 product family
Intel® Xeon® processor E3-1200 v2 product family
Intel® Xeon® Processor D-1500 product family
3rd Gen Intel® Core® i7 processor product family
4th Gen Intel® Core® i7 processor product family
5th Gen Intel® Core® i7 processor product family
6th Gen Intel® Core® i7 processor product family
Intel® Atom™ Processor S1200 product family
Intel® Atom™ Processor C3000 product family
Intel® Atom™ Processor C2000 product family
Intel® C610 series chipset
Intel® C600 series chipset
Intel® C230 series chipset family
Intel® C220 series chipset family
Intel® C210 series chipset family
Intel® C200 series chipset family
Intel® 100 series chipset family
Intel® X99 chipset family
Intel® X79 series chipset family
Intel® 8 series chipset family
Intel® 7 series chipset family
Intel® 6 series chipset family
Intel® Communications Chipset 8900 Series

EDIT by Fernando: I have put the details code into a "spoiler" (to save space)

SetupChipset.rar (3 MB)

nikos_xatz · April 8, 2017, 4:32pm

I was thinking that 10.1.2.xx is for the X series and 10.1.1.xx is for Z series…
but in the description number 3 says Intel 100 series ? !
what is better for my Z170 MotherBoard ???

EDIT by Fernando: Unneeded part of the fully quoted post removed (to save space)

Fernando · April 8, 2017, 4:50pm

Yes, there are some chipsets/CPU platforms, which are supported by both Intel Chipset Device Software Sets.

It doesn’t matter, to which series (v10.1.1.xx or v10.1.2.xx) the Intel Chipset Device Software Set belongs - as long as the Set contains INF files, which do support your special system.

@plutomaniac :
Thanks for the info regarding the Intel Chipset Device Software v10.1.2.84 dated 01/18/2017.
By the way - the lates available Intel Chipset Device Software Set, which belongs to the v10.1.2.xx series, is v10.1.2.85 dated 02/01/2017 and has already been offered by me >here< on 15th March.

nikos_xatz · April 8, 2017, 4:56pm

Also there is non Performance difference between this two chipsets ???
Thanks Fernando…

Fernando · April 8, 2017, 5:10pm

There are performance differences between different chipsets, but these differences have nothing to do with the used Intel Chipset Device Software Set version.

plutomaniac · April 8, 2017, 5:22pm

The first post says 80, that’s why I thought it’s new. That changelog also mentions why the date set is intentional.

nikos_xatz · April 8, 2017, 5:26pm

Thank you Fernando…

Fernando · April 8, 2017, 5:33pm

Yes, on the first view the start post is misleading, but I have mentioned it very clearly, that there are newer (but extremely old dated) Sets available.
Maybe i should offer the latest Sets within the start post despite their misleading INF file dates.

Yes, that was indees an interesting info, but - to be honest - I do not really understand the explanatory statement by Intel.

plutomaniac · April 8, 2017, 5:43pm

I believe that the latest pack version needs to be at the first post, no matter the dates. They are clearly set to 1970 intentionally. I don’t know what they mean by the “SMBus issue” but I can guess:

Windows cannot find driver for some device, Chipset INF installs placeholder driver with modern date, Windows does not offer a proper driver for said device because its date might be older that the placeholder’s, the user ends up with a placeholder driver at a device which needs a proper one (RST, ME, USB etc) and thus has problems. For example, at my HM65 I have RST 12.9.4.1000 (2014) installed. If I apply a Chipset INF with a date of 2017, Windows will not replace it with a proper RST driver and I’ll be having bad performance. Setting the date back to 1970 resolves that, Windows will not complain about missing driver and if Windows Update can find a proper/newer driver it will get replaced as expected.

Fernando · April 8, 2017, 5:59pm

@plutomaniac :
You are right - I will put the latest Intel Chipset Device Software Sets of the v10.1.1.xx and v10.1.2.xx series into the start post.
Thank you for your explanation, which sounds to be comprehensible regarding the INF files, which are just placeholders for real drivers (RST/Heci/USB), but I cannot understand why Intel has recently started to put these old dates into all INF files of the latest Intel Chipset Device Software Sets, although >90% of the Intel Chipset Devices neither need nor will ever use a real driver.

@all:
The AIO Set, which I am offering within the start post, contains the latest available Intel Chipset Device INF files with the correct date of their compilation, but the Set doesn’t contain placeholders for the HECI and RST drivers.

plutomaniac · April 8, 2017, 6:22pm

Well, they must have a reason. Maybe some devices need/have a proper driver at older OS but it’s not needed at newer ones (example: USB3 Intel driver at Windows 7 –> driver not needed at Windows 8 as it’s part of the OS), or maybe it’s easier to sign then in bulk at the same date etc. No matter the actual reason, the entire Chipset INF installation is usually a matter of appearance/aesthetics, even more so for the date reported. So it doesn’t matter. As long as we offer here the Chipset INF utilities which support the latest devices and assign better Device Manager names, everyone is covered.

Fernando · April 9, 2017, 1:07pm

@ all:
Following the advice given by plutomaniac, I have decided to update the start post and to present the latest original Intel Chipset Device Software Sets and their included “pure” INF files, although they have been misleadingly dated 01/01/1970 by Intel.

Update of the Start post
Changelog:

new: “Original Intel Chipset Device Software v10.1.1.42 WHQL” dated 01/18/2017 (Original Set with Installer, all included INF files INF Files compiled in January 2017, but misleadingly dated 01/01/1970)
new: “Original Intel Chipset Device Software v10.1.2.85 WHQL” dated 02/14/2017 (Original Set with Installer, all included INF files compiled in February 2017, but misleadingly dated 01/01/1970)
new: “Latest Intel Chipset Device INF Files v10.1.x.xx WHQL” composed at 04/09/2017 (= AIO package with the “pure” original Intel Chipset Device INF files v10.1.142 resp. v10.1.2.85, all compiled by Intel in 2017, but shown with the wrong date 01/01/1970)

Any feedback is much appreciated.
If you should find any Intel chipset device, which is not supported by my original resp. modded “All-in-One packages”, please let me know it.

Regards
Dieter (alias Fernando)

khanmein · April 9, 2017, 1:24pm

@Fernando how come the digital signer is not Windows?

Intel(R) 9 Series Chipset Family PCI Express Root Port 1 - 8C90
Intel(R) 9 Series Chipset Family SMBus Host Controller - 8CA2
Intel(R) H97 Chipset LPC Controller - 8CC6

Driver Version: 10.1.1.42
Digital Signer: Win-RAID CA

Fernando · April 9, 2017, 1:34pm

@khanmein :
Within which package did you find the related INF file(s)?

If you have used my "Latest Intel Chipset Device INF Files v10.1.x.xx mod+signed by Fernando", it has been me, who gave the related INF file(s) the Win-RAID CA signature.
By the way: Usually it is Microsoft (not Windows, who gives the drivers resp. INF files its digitally "WHQL" stamp.