Intel Chipset Software Installation 10.1.2.8 WHQL Download

Discussion in 'Frontpage news' started by Hilbert Hagedoorn, Jul 21, 2015.

  1. Hilbert Hagedoorn

    Hilbert Hagedoorn Don Vito Corleone Staff Member

    Messages:
    48,509
    Likes Received:
    18,809
    GPU:
    AMD | NVIDIA
  2. snorge

    snorge Guest

    Messages:
    122
    Likes Received:
    0
    GPU:
    gtx 970 SLI
    What important things does it update? Most people seem to claim installing these is pretty useless. I personally always like to have the latest drivers even if they don't do much lol.
     
  3. Agent-A01

    Agent-A01 Ancient Guru

    Messages:
    11,640
    Likes Received:
    1,143
    GPU:
    4090 FE H20
    This adds drivers to X99 platform, previously x99 didnt have any
     
  4. thatguy91

    thatguy91 Guest

    It all depends on the Windows version and what chipset you have. The newer the chipset, the more likely you will need it to correctly identify all Intel devices on Windows 8.1 and especially 7. Windows 10 should support most, if not all, current Intel chipsets and devices covered by the inf 's.

    When the device is already properly identified this will simply change the device description, version, and date. They are null drivers, meaning no payload. Any apparent payload in device manager is because some of the included inf's act as an extension to the system machine.inf.

    The 'real' Intel drivers are things like the performance AHCI driver (you don't need the application part) or the Management Engine Interface driver (again you only need the driver), both of these are separate downloads. There are one or two other proper Intel drivers depending on the OS and chipset.
     

  5. Agent-A01

    Agent-A01 Ancient Guru

    Messages:
    11,640
    Likes Received:
    1,143
    GPU:
    4090 FE H20
    These are no longer null drivers
     
  6. thatguy91

    thatguy91 Guest

    Yes they are :), check them out for yourself! They are all basically the same, but with different hardware ID's and devices.

    Here is one for Ivy Bridge:
    Code:
    ; ************************************************************
    ; ************************************************************
    ; **  Filename: IvyBridgeSystem.inf                         **
    ; **  Abstract: Assigns the null driver to devices          **
    ; **            for yellow-bang removal and                 **
    ; **            brands Intel(R) devices                     ** 
    ; ************************************************************
    ; ************************************************************
    
    [Version]
    Signature=$WINDOWS NT$
    Class=System
    ClassGUID={4D36E97D-E325-11CE-BFC1-08002BE10318}
    Provider=%INTEL%
    CatalogFile=IvyBridge.cat
    DriverVer=07/01/2015, 10.1.2.8
    
    [SourceDisksNames]
    
    [SourceDisksFiles]
    
    [ControlFlags]
    ExcludeFromSelect=*
    
    [PackageInfo]
    Name=Chipset
    
    [Manufacturer]
    %INTEL%=INTEL,NT,NTamd64
    
    [INTEL.NT]
    %PCI\VEN_8086&DEV_0150Desc%=Needs_NO_DRV, ,PCI\VEN_8086&DEV_0150
    %PCI\VEN_8086&DEV_0151Desc%=Needs_PCI_DRV,PCI\VEN_8086&DEV_0151
    %PCI\VEN_8086&DEV_0154Desc%=Needs_NO_DRV, ,PCI\VEN_8086&DEV_0154
    %PCI\VEN_8086&DEV_0155Desc%=Needs_PCI_DRV,PCI\VEN_8086&DEV_0155
    %PCI\VEN_8086&DEV_0158Desc%=Needs_NO_DRV, ,PCI\VEN_8086&DEV_0158
    %PCI\VEN_8086&DEV_0159Desc%=Needs_PCI_DRV,PCI\VEN_8086&DEV_0159
    %PCI\VEN_8086&DEV_015CDesc%=Needs_NO_DRV, ,PCI\VEN_8086&DEV_015C
    %PCI\VEN_8086&DEV_015DDesc%=Needs_PCI_DRV,PCI\VEN_8086&DEV_015D
    
    [INTEL.NTamd64]
    %PCI\VEN_8086&DEV_0150Desc%=Needs_NO_DRV, ,PCI\VEN_8086&DEV_0150
    %PCI\VEN_8086&DEV_0151Desc%=Needs_PCI_DRV,PCI\VEN_8086&DEV_0151
    %PCI\VEN_8086&DEV_0154Desc%=Needs_NO_DRV, ,PCI\VEN_8086&DEV_0154
    %PCI\VEN_8086&DEV_0155Desc%=Needs_PCI_DRV,PCI\VEN_8086&DEV_0155
    %PCI\VEN_8086&DEV_0158Desc%=Needs_NO_DRV, ,PCI\VEN_8086&DEV_0158
    %PCI\VEN_8086&DEV_0159Desc%=Needs_PCI_DRV,PCI\VEN_8086&DEV_0159
    %PCI\VEN_8086&DEV_015CDesc%=Needs_NO_DRV, ,PCI\VEN_8086&DEV_015C
    %PCI\VEN_8086&DEV_015DDesc%=Needs_PCI_DRV,PCI\VEN_8086&DEV_015D
    
    [Needs_NO_DRV]
    Include=machine.inf
    Needs=NO_DRV
    
    [Needs_NO_DRV.Services]
    Include=machine.inf
    Needs=NO_DRV.Services
    
    [Needs_PCI_DRV]
    Include=machine.inf
    Needs=PCI_DRV
    
    [Needs_PCI_DRV.Services]
    Include=machine.inf
    Needs=PCI_DRV.Services
    
    [Needs_PCI_DRV.HW]
    Include=machine.inf
    Needs=PCI_DRV.HW
    
    [Strings]
    INTEL="INTEL"
    PCI\VEN_8086&DEV_0150Desc="Xeon(R) processor E3 - 1200 v2/3rd Gen Core processor DRAM Controller - 0150"
    PCI\VEN_8086&DEV_0151Desc="Xeon(R) processor E3 - 1200 v2/3rd Gen Core processor PCI Express Root Port - 0151"
    PCI\VEN_8086&DEV_0154Desc="3rd Gen Core processor DRAM Controller - 0154"
    PCI\VEN_8086&DEV_0155Desc="Xeon(R) processor E3 - 1200 v2/3rd Gen Core processor PCI Express Root Port - 0155"
    PCI\VEN_8086&DEV_0158Desc="Xeon(R) processor E3 - 1200 v2 DRAM Controller - 0158"
    PCI\VEN_8086&DEV_0159Desc="Xeon(R) processor E3 - 1200 v2/3rd Gen Core processor PCI Express Root Port - 0159"
    PCI\VEN_8086&DEV_015CDesc="Xeon(R) processor E3 - 1200 v2/3rd Gen Core processor DRAM Controller - 015C"
    PCI\VEN_8086&DEV_015DDesc="Xeon(R) processor E3 - 1200 v2/3rd Gen Core processor PCI Express Root Port - 015D"
    
    
    
    
    ; Copyright (c) 2003-2015 Intel Corporation
    ; 
    ; ********************************************************************************
    ; Intel is making no claims of usability, efficacy or warranty.
    ; ********************************************************************************
    ; Information in this document is provided in connection with Intel products. No
    ; license, express or implied, by estoppel or otherwise, to any intellectual
    ; property rights is granted by this document. Intel assumes no liability
    ; whatsoever, and Intel disclaims any express or implied warranty, relating to
    ; sale and/or use of Intel products including liability or warranties relating to
    ; fitness for a particular purpose, merchantability, or infringement of any
    ; patent, copyright or other intellectual property right. Intel products are not
    ; intended for use in medical, life saving, or life sustaining applications.
    ; ********************************************************************************
    ; Intel Corporation disclaims all warranties and liabilities for the use of this
    ; document and the information contained herein, and assumes no responsibility for
    ; any errors which may appear in this document, nor does Intel make a commitment
    ; to update the information contained herein. Intel reserves the right to make
    ; changes to this document at any time, without notice.
    ; ********************************************************************************
    ; ********************************************************************************
    ; 
    ; * Third-party brands and names are the property of their respective owners.
    
    I want to draw your attention to the top, where Intel even claims they are null drivers for yellow bang removal in device manager, and brands Intel devices. The last one is the key statement as to why it changes the device in device manager, for branding.

    Further down the list you will see it links to machine.inf, which is the Microsoft system device inf. So, in the device manager for Xeon(R) processor E3 - 1200 v2/3rd Gen Core processor PCI Express Root Port - 0151 it appears it loads a driver (pci.sys), but in fact it is just loading the pci.sys as defined in the machine.inf file. So, what the driver does is nothing more than change the system descriptor for the file to the Intel branded one.

    Every other inf in this 'driver' is the same principle, either linking to the existing machine files or are just descriptor files. This is why they are 'null' drivers. Even if it does remove the yellow bang from the device in device manager, this is simply because the device wasn't out when the last update to the system machine.inf occurred.

    Non null drivers are the proper AHCI driver, the proper MEI driver, Intel network drivers, and under Windows 7 since it doesn't natively have support for them, the Intel USB 3.0 driver and the Intel Serial IO driver (not sure what this does, but there is a Windows 7 driver for it, the latest of which is for Skylake).
     
  7. snorge

    snorge Guest

    Messages:
    122
    Likes Received:
    0
    GPU:
    gtx 970 SLI
    Well I have z97, I always see beta chipset drivers posted on station drivers but never know whether I should bother installing them. Since Windows 10 comes out next week I will probably wait until then and download the latest of everything at the same time.
     
  8. sfektsz

    sfektsz Guest

    Messages:
    48
    Likes Received:
    0
    GPU:
    NVIDIA GTX 770 2GB
  9. xomniversex

    xomniversex Guest

    Messages:
    3
    Likes Received:
    0
    GPU:
    XFX Radeon HD 6970 x 2
    z68 user here on Windows 10.

    Installed these and it caused a myriad of issues including my AMD GPU drivers no longer functioning - even when reinstalled - no 3D acceleration at all after installing.

    Had to use system restore to undo them since there's no uninstaller.

    Going to stick to WU driver updates only for chipset.
     
  10. plopingo

    plopingo Active Member

    Messages:
    63
    Likes Received:
    6
    GPU:
    RTX 3080 PNY XLR8
    What -overall do for the installation ?

    Thanks
     

Share This Page