Intel Chipset Device "Drivers" (= INF files)

Fernando · May 8, 2018, 4:11pm

@salva_vts :
Why do you want to change/modify brandnew Intel Chipset Device INF files? The shown date is wrong, but absolutely irrelevant.

salva_vts · May 8, 2018, 4:14pm

It was only to have the correct date, since previously if I left but not now

Fernando · May 8, 2018, 4:24pm

It doesn’t make sense to modify the wrong dates of all Chipset Device INF files, which will be released by Intel in the future.
Let them as they are (as long as you don’t see any yellow flagged “System devices” within the Device Manager).

SM03 · June 7, 2018, 5:26pm

Hello @Fernando

As per the Station Driver Info, the latest v10.1.17667.8082 WHQL is out today, so can you update the OP along with the original INF as well your modded version with the correct date this time unlike the previous one. & yes, I know you don’t take request & don’t do anything as per anyone’s demand or request so just to make it clearer, read it/ take it as a general comment or statement, just to say.

Fernando · June 7, 2018, 7:55pm

@SM03 :
Thanks fot the hint to the release of a new Intel Chipset Device Software Set published by Station-Drivers, but I had it alreay seen before I have read your post.
I am sorry, but I will not modify and sign all the wrongly dated INF files.
Reason: The execution of this task would be absolutely wasted time and the users would not benefit from it.

@all:
Update of the Start post
Changelog:

new: "Intel Chipset Device Software Set v10.1.17667.8082 WHQL dated 05/14/2018 (original Set with installer)
new: “Latest Intel Chipset Device INF Files v10.1.xx.x Series WHQL” composed at 06/07/2018
(= AIO package with the “pure” original Intel Chipset Device INF files, extracted from the InstallerSet v10.1.17667.8082 WHQL, shown with the wrong date 07/18/1968)

Here are the new version numbers of the INF files for the specific Intel CPU systems:

v10.1.19.1: Denverton
v10.1.17.1: ApolloLake
v10.1.16.4: CannonLake-H
v10.1.15.3: CannonLake-LP
v10.1.14.4: CoffeeLake
v10.1.13.2: Geminilake
v10.1.11.2: KabyLake-PCH-H
v10.1.10.2: Kabylake
v10.1.9.2: Lewisburg
v10.1.8.4: Skylake-E
v10.1.7.2: Skylake
v10.1.6.1: SunrisePoint-H
v10.1.5.1: SunrisePoint-LP
v0.0.0.1: NULL_HECI
v10.1.4.2/v10.1.3.1: all other supported Intel Chipsets/CPU systems

Thanks to Station-Drivers for the source package!
Any feedback is much appreciated.

Regards
Dieter (alias Fernando)

SM03 · June 7, 2018, 8:26pm

So, I’ve to stick with your old modded INF with Certificate & proper dated from Aug 2017 I guess, unless you 'd do it in future.

plutomaniac · June 7, 2018, 8:33pm

If you don’t understand why Fernando is right then you should indeed not bother with INF at all.

trebleta · June 20, 2018, 3:41pm

Hi and thanks for the Drivers Fernando but i do have a question.
I’m using windows 10 on a sort of old pc now its a Gigabyte GA-X58A-UD3R Rev2.0 with a intel I7 950.
I know windows don’t support anything before 2012.
So your your ACHI and Raid drivers install and work great thanks. the default windows 10 raid drivers will wipe and crash the raid array if swap from/to a intel version.
question is the chip-set do i need to install say a Intel 9x chip-set software to get the most from the ACHI/Raid Drivers and my system.
With no chip-set drivers installed everything seem fine, same for if i do install them just in device manager i see correct names from devices.

I know this is not really anything to do with your drivers but well am asking as not sure were the chip-set used to be needed before windows 10

Fernando · June 20, 2018, 8:28pm

@trebleta :
Welcome to the Win-RAID Forum!
The Intel Chipset Device INF files have nothing to do with the on-board Intel SATA AHCI/RAID Controller.
There is no need to install any Intel Chipset Device INF file unless the Device Manager shows a yellow flagged system device.
Regards
Dieter (alias Fernando)

panosxidis · July 6, 2018, 10:50am

Intel Chipset Device Software Version 10.1.17695.8086 WHQL new fernando

tistou77 · July 6, 2018, 10:53am

For Skylake-X, it’s the same drivers versions than v10.1.17667.8082

panosxidis · July 6, 2018, 12:20pm

I have broadwell-e 6950X!!i have one question Fernando!how can clean my chipset drivers and i install new chipset driver?thanks

Fernando · July 6, 2018, 12:42pm

@panosxidis :
Thanks fot the hint to the release of a new Intel Chipset Device Software Set.
There is no need to update the Intel Chipset Device INF files of your system, unless it has an Intel CannonLake-H CPU.

@all:
Update of the Start post
Changelog:

new: "Intel Chipset Device Software Set v10.1.17695.8086 WHQL dated 06/13/2018 (original Set with installer)
new: “Latest Intel Chipset Device INF Files v10.1 Series WHQL” composed at 07/06/2018
(= AIO package with the “pure” original Intel Chipset Device INF files, extracted from the InstallerSet v10.1.17695.8086 WHQL, all shown with the wrong date 07/18/1968)

Here are the new version numbers of the INF files for the specific Intel CPU systems:

v10.1.19.1: Denverton
v10.1.17.1: ApolloLake
v10.1.16.5: CannonLake-H (the only updated ones!)
v10.1.15.3: CannonLake-LP
v10.1.14.4: CoffeeLake
v10.1.13.2: Geminilake
v10.1.11.2: KabyLake-PCH-H
v10.1.10.2: Kabylake
v10.1.9.2: Lewisburg
v10.1.8.4: Skylake-E
v10.1.7.2: Skylake
v10.1.6.1: SunrisePoint-H
v10.1.5.1: SunrisePoint-LP
v0.0.0.1: NULL_HECI
v10.1.4.2/v10.1.3.1: all other supported Intel Chipsets/CPU systems

Thanks to Station-Drivers for the source package!
Any feedback is much appreciated.

Regards
Dieter (alias Fernando)

thurask · July 13, 2018, 5:16pm

https://downloadcenter.intel.com/downloa…s-?product=1201

Intel® Server Chipset Driver for Windows
Version: 10.1.17711.8088

Fernando · July 13, 2018, 6:52pm

@thurask :
Thanks fot the hint to the release of a new Intel Chipset Device Software Set and the download link to Intel’s Downloadcenter.

@all:
Update of the Start post
Changelog:

new: "Intel Chipset Device Software Set v10.1.17711.8088 WHQL dated 07/09/2018 (original Set with installer)
new: “Latest Intel Chipset Device INF Files v10.1 Series WHQL” composed at 07/13/2018
(= AIO package with the “pure” original Intel Chipset Device INF files, extracted from the InstallerSet v10.1.17711.8088 WHQL, all shown with the wrong date 07/18/1968)

These are the new version numbers of the INF files for the specific Intel CPU systems, which really have been updated at 06/28/2018:

v10.1.16.6: CannonLake-H)
v10.1.11.3: KabyLake-PCH-H
v10.1.7.3: Skylake

Any feedback is much appreciated.

Regards
Dieter (alias Fernando)

rankoneads · July 15, 2018, 7:42am

Hmm no idea what happened with these new chipset drivers, but Win7 said 100 times (for every device) that they were unsigned, and I had to confirm every single device.
Also, after installation, my CPU-Z bench score on i9-7940x (Windows 7) went down by a whopping 2500 points.

Chipset driver 10.1.1.45 from motherboard download page CPU-Z score: 7981.8
Chipset driver 10.1.17711.8088 from win-raid CPU-Z score: 5542.6

I wonder what they changed if anything in the Skylake files that could’ve resulted in this devastating of a performance loss? Everything was the exact same before and after. I did a bench run (zero programs open) after the installation… then re-downloaded the motherboard chipset drivers, downgraded, did bench again, and got the score above.

Even weirder… my score is 1300 points higher than a standard 7940x… and 400 points higher than 7960x… wtf? I’ve done no overclocking on this CPU at all…
https://valid.x86.fr/48kgrv

Edit: Something definitely bugged out. Now I run the bench again and got ~5550 with the old chipset driver. That’s crazy.

Fernando · July 15, 2018, 8:43am

@rankoneads :
The Intel Chipset Device INF files have no impact on the performance of the related system.
How did you install them?

This verifies, that your performance drop has nothing to do with the new Intel Chipset Device INF files.

rankoneads · July 15, 2018, 9:53am

I installed the drivers using -overall command as I always do. Every single item made me click “Install unsigned driver”. Which on the x299, there’s like 100 Xeon-related chipset items, so I had to click it every time… and Windows created a system restore every time (and deleted old ones as I only allow 5gb to be used).

Fernando · July 15, 2018, 10:08am

Then you always do something, which doesn’t make sense.
The " -overall" command forces the installation of not required (and maybe even not matching) INF files. Look into your C:\Windows\INF directory for INF files beginning with the letters “oem” and compare the amount of such stored Intel Chipset INF files with the ones, which are really in-use by your system (shown within the “System devices” section of the Device Manager).

rankoneads · July 15, 2018, 10:51am

I’ve always used -overall every time I do a chipset install and never had that happen. Also, when I looked at the specific system devices, the drivers directly said “Unsigned” in Device Manager.