Intel NUC 13 Pro (Arena Canyon) review
Endorfy Arx 700 Air chassis review
Beelink SER5 Pro (Ryzen 7 5800H) mini PC review
Crucial T700 PCIe 5.0 NVMe SSD Review - 12GB/s
Sapphire Radeon RX 7600 PULSE review
Gainward GeForce RTX 4060 Ti GHOST review
Radeon RX 7600 review
ASUS GeForce RTX 4060 Ti TUF Gaming review
MSI GeForce RTX 4060 Ti Gaming X TRIO review
GeForce RTX 4060 Ti 8GB (FE) review
Download Intel Chipset Software Installation v10.0.27 WHQL
You can now download the Intel Chipset Software Installation 10.0.27 WHQL driver. This new release included a number of fixes yet also adds support for 6th Gen Intel Core and Intel 100 Series chipset family (Skylake).
Download AMD Catalyst 15.4.1 Freesync Driver - 05/09/2015 01:01 PM
You can now download an AMD Catalyst 15.4.1 Freesync driver - this release enables optimisations and fixes for some AMD FreeSync technology capable products and displays while retaining all previous...
Download Nvidia GeForce 352.63 Windows 10 pre-release driver - 04/29/2015 05:07 PM
If you are trying out Windows 10, the preview build then give this Nvidia driver a try. This driver, version 352.63, is the latest recommended driver for all pre-release Windows 10 testing. Download...
Download Final Fantasy XIV: Heavensward Benchmark - 04/29/2015 12:51 PM
You can now download the Final Fantasy XIV: Heavensward Benchmark. If you're a fan of the genre or simply want a new tool to measure your system's performance, you should grab the Heavensward Benc...
Samsung Magician 4.6 Download - 04/24/2015 06:05 PM
Samsung released Samsung Magician 4.6, this build adds support for new SSDs and offers performance optimizations with the 840 EVO series. As weird as it is, Samsung has limited the number of downloa...
Download: Realtek HD Audio 2.76 driver - 04/22/2015 03:13 PM
Realtek has released its 2.76 HD Audio driver compatible with Microsoft’s Windows Vista, 7, 8, and 8.1 operating systems (both 32- and 64-bit variants). Realtek’s present driver a...
thatguy91
Senior Member
Posts: 6640
Joined: 2010-08-27
Senior Member
Posts: 6640
Joined: 2010-08-27
#5068080 Posted on: 05/11/2015 10:39 PM
No, there is no reason. The only reason to install them in the first place is so Windows correctly identifies system components.
The 'drivers' couldn't be clearer as such, the payload in the chipset driver all have this at the very top:
The only difference between the above files and the ones for SMBUS, Win7/8, thermal, and USB is the name of the file and the change in the description to suit the device. For instance, Assigns the null driver to USB devices for yellow-bang removal.
The same all for:
IvyTown, Haswell-E, Wellsburg, Sky Lake, Sky Lake-E, Sunrise Point-LP, Sunrise Point-H, KabyLake, Cannon Lake-LP, Cannon Lake-H, Broadwell-DE, Knights Landing, and Coleto Creek.
%IntelDeviceDesc%=Needs_NO_DRV, , PCI\VEN_8086&DEV_xxxx
(where xxxx is the individual device name, for any and all of the individual chipset files)
After the device ID's, they all have:
Include=machine.inf
Needs=NO_DRV
Include=machine.inf
Needs=NO_DRV.Services
INTEL="Intel"
IntelDeviceDesc="Intel Device"
So, there you go
. Now, I would still run it 'just in case' Windows hasn't identified something, or identified it correctly, but it's not like the AHCI drivers, or HECI (Intel ME) drivers, they are separate. They also typically include the actual driver a program which in most cases isn't necessary. For instance, if you install the whole Intel RST package you have the unnecessary tray thing, which is probably only 'useful' for RAID. For Intel ME, the functions provided by the Intel ME programs isn't at all beneficial, but the driver is okay.
For Windows 7 which doesn't have native USB 3.0 you also need the Intel USB driver if you have and Intel USB 3.0 controller.
No, there is no reason. The only reason to install them in the first place is so Windows correctly identifies system components.
The 'drivers' couldn't be clearer as such, the payload in the chipset driver all have this at the very top:
; ************************************************************
; ************************************************************
; ** Filename: Chipset_System.inf **
; ** Abstract: Assigns the null driver to System **
; ** devices for yellow-bang removal. **
; ************************************************************
; ************************************************************
; ************************************************************
; ** Filename: Chipset_System.inf **
; ** Abstract: Assigns the null driver to System **
; ** devices for yellow-bang removal. **
; ************************************************************
; ************************************************************
The only difference between the above files and the ones for SMBUS, Win7/8, thermal, and USB is the name of the file and the change in the description to suit the device. For instance, Assigns the null driver to USB devices for yellow-bang removal.
The same all for:
IvyTown, Haswell-E, Wellsburg, Sky Lake, Sky Lake-E, Sunrise Point-LP, Sunrise Point-H, KabyLake, Cannon Lake-LP, Cannon Lake-H, Broadwell-DE, Knights Landing, and Coleto Creek.
%IntelDeviceDesc%=Needs_NO_DRV, , PCI\VEN_8086&DEV_xxxx
(where xxxx is the individual device name, for any and all of the individual chipset files)
After the device ID's, they all have:
Include=machine.inf
Needs=NO_DRV
Include=machine.inf
Needs=NO_DRV.Services
INTEL="Intel"
IntelDeviceDesc="Intel Device"
So, there you go
. Now, I would still run it 'just in case' Windows hasn't identified something, or identified it correctly, but it's not like the AHCI drivers, or HECI (Intel ME) drivers, they are separate. They also typically include the actual driver a program which in most cases isn't necessary. For instance, if you install the whole Intel RST package you have the unnecessary tray thing, which is probably only 'useful' for RAID. For Intel ME, the functions provided by the Intel ME programs isn't at all beneficial, but the driver is okay.
For Windows 7 which doesn't have native USB 3.0 you also need the Intel USB driver if you have and Intel USB 3.0 controller.
tsunami231
Senior Member
Posts: 13878
Joined: 2003-05-24
Senior Member
Posts: 13878
Joined: 2003-05-24
#5068107 Posted on: 05/11/2015 11:23 PM
long winded version of it dont really mater.
And yes i have installed the whole RST package I have not bother to remove it and just install the drivers as i have 1 less service going in the back ground
I fiqured the next time bother to reinstall windows i will go this root, of just drivers for the RST but for now i just see the point
long winded version of it dont really mater.
And yes i have installed the whole RST package I have not bother to remove it and just install the drivers as i have 1 less service going in the back ground
I fiqured the next time bother to reinstall windows i will go this root, of just drivers for the RST but for now i just see the point
Click here to post a comment for this news story on the message forum.
Senior Member
Posts: 13878
Joined: 2003-05-24
you know i rarely if ever both update chipset drivers, i still using 9.3.0.1019 according to the Intel directory in program files (x86) though registry say 10.0.13 and the back up of the chipset driver i have says 10.0.13.0
IS there point to even update it seeing i still using x58, not that i ever seen any diffrence from installing that and another install them on x58 every work right most the drivers it is supposed to update still show date before 2010 and that was with the overall command