thank you so much you solved my problem with temp reading's on i7 4790k - z97 hd 4600 - I'm using the smbus driver provided by intel desktop utility which is pretty old but works great - the smbus id is PCI\VEN_8086&DEV_8CA2&SUBSYS_85341043&REV_00 - (smbus 2.0 driver installed) dated 2012 but it get resources when installing the driver from any inf no resources are allocated, my question is are there any newer driver's that work ? fyi in Microsoft update catalog site there are Broadcom driver's for the same PCI\VEN_8086&DEV_8CA2&SUBSYS_85341043&REV_00 hardware number they are newer and allocate resources to the device any idea's ?
Nice to know that the article helped.
On Intel Download Center https://downloadcenter.intel.com/ , search for Intel® Chipset Device Software (INF Update Utility) or Intel® Server Chipset Drive.
You can download the 10.1.1.42 Intel driver for chipsets.
1 of 1 people found this helpful
Hey yeah my eye's popped when I noticed a new chipset inf was released the .42 has its own set of problem - like
1. user with old chipset's inf installed must use the -overall command to update
2. the date of the driver is off dated to 1.1.1970
3. when installed smbus driver from this new inf smbus if off no resources are allocated and temp seems to be on the high end
I found only those 2 driver work best
1.the driver from intel desktop utility [installed Intel(R) PCH SMBus Controller - 8CA2 (Intel(R) SMBus 2.0 Driver)] for PCI\VEN_8086&DEV_8CA2&SUBSYS_85341043&REV_00
2. Broadcom driver for same smbus hardware stated its a 8086(intel) (cant give u to much info on it)
Can confirm just experienced the same results myself. Had to use -overall from an elevated cmd window after I tried first manually downgrading to 10.1.1.14 from 10.1.1.38 as a workaround (when initially trying to update from .38 to .42 failed to work properly). Do driver date stamps matters?! :thinking:
(NOTE: I did not install Windows pushed version of 10.1.1.38; as I'm very selective with Windows Updates, but rather the one recommended by my board's manufacturer ASUS who had posted this as a INF update so could this be a problem with all .38 installations or is this related to the currently offered 10.1.1.42 package installer or both?)
Windows7 x64 OS SP1 Home Premium
Asus Z170-E board
I think its the new inf .42 had the same problem with latest server inf too
and date don't hurt but will generate bug's I think
This message was posted on behalf of Intel Corporation
Some peers are suggesting to install the INF with -overall command line.
See the list of switches below: