Hi,
For a study, I would like to know the differences between two Intel Chipset driver versions (example: delta changes/fixes/improvements from v9.4.0.1026 and v10.0.27)
In the Intel websites, I don't get this information. can you please update from where can I get these information?
I would like to know the known issues/bugs in the previous release and fixes/improvements/new features in the next release.
Appreciate your help!
I am getting these recurring errors in the IOCAgentLog event log:
Source: IOCAgent, Event ID: 0
General: 2017-01-27 14:02:59,952 [38] ERROR ProviderManager.SecurepayBcaProvisioner - Exception during BCA-SGX provisioning
System.Runtime.InteropServices.SEHException (0x80004005): External component has thrown an exception.
at Intel.Pabe.Factor.SgxProvider.AbortProvision(SgxProvider* , UInt32 )
at BCAXInterface.SgxProvider.Provision(String provisionUrl, String providerUrl)
at ProviderManager.SecurepayBcaProvisioner.<>c__DisplayClass16_0.<StartProvisioningAsync>b__0()
I am also getting other Intel related errors:
Source: Service Control Manager, Event ID: 7011
General: A timeout (30000 milliseconds) was reached while waiting for a transaction response from the Intel(R) Online Connect Helper service.
Source: IntelDalJhi, Event ID: 4
General: Intel(R) Dynamic Application Loader Host Interface Service initialization failure - the spooler applet is invalid.
OS is Windows 10 Pro 64-bit version 1607 build 14393.693, MSI Motherboard Intel ME version 11.6.1.1142, Intel MEI driver version 11.6.0.1032.
Please can anyone advise?
hi , i wanna overclock my e8400 , but unfortunately i can't install xtu
Intel(R) HM76 Express Chipset LPC Controller - 1E59
i am not able to find the update plzz help
I am trying to decode and encode H264 codec on Intel® Xeon® E3-1200 v4 Family with C226 chipset as well as Intel® Xeon® E3-1200 and E3-1500 v5 Family with C236 chipset with Intel Media SDK 2016.
Can Intel Media SDK 2016 decode and encode H264 codec on Intel® Xeon® E3-1200 v4 Family with C226 chipset as well as Intel® Xeon® E3-1200 and E3-1500 v5 Family with C236 chipset?
Or only Intel Media SDK 2017 is supported on Intel® Xeon® E3-1200 v4 Family with C226 chipset as well as Intel® Xeon® E3-1200 and E3-1500 v5 Family with C236 chipset?
We have found following information in [ https://software.intel.com/en-us/intel-media-server-studio/details ].
Intel Media Server Studio supports the following platforms with integrated graphics:
I have tested decoding and encoding H264 codec on 4th / 5th / 6th Generation Intel® Core™ processors with Intel Media SDK 2016 and it works.
But I have no experience on Intel® Xeon® E3-1200 v4 Family with C226 chipset and Intel® Xeon® E3-1200 and E3-1500 v5 Family with C236 chipset.
Thank you.
I have just run the Intel Driver Update Utility, and it says that my Intel Chipset Device Software needs updating from version 10.0.14393.0 to version 10.1.1.14. But it also says, "See detailed description to make sure you need this file." How do I ascertain if I need this file/update?
Hi,
I have to configure a RMM software on a couple of machines which have some Intel stuff on-board. I thought the easiest way would be to monitor the Windows Event logs, but I don't know in which event logs and under which source name the Intel stuff reports.
Some Examples:
* Intel Network Connections
* Intel Graphic Driver
* Intel Management Engine Components
* Intel Rapid Storage Technology
* Intel Security Assist
* Intel USB 3.0 Host Controller Adaptation Driver
* ...
I know not everything is important, and needs to be monitored. But for Example The Intel Rapid Storage Technology should be in charge of the harddisks, and it would be nice to know if there is a problem.
Thanks for any information/help,
Christian.
Hello,
I have a RAID1 system.
Windows 7 says me that there is a problem with the disk (this means with one of the two disks that make the array).
If one of the two hdd was damaged (but not eliminated from the array), can this affect the performance of the entire RAID system (for example during windows updates)?
The option "Reset disks to non-RAID" during RAID BIOS, could be the solution to find the faulty disk? (I do this excluding from array disk1 and then disk2 randomly)
Choosing "Create RAID volume" after have been chosen "Reset disks to non-RAID" (leaving BIOS hd configuration as RAID), will it do a full entire new copy from disk1 to disk2 or only an incremental copy?
Anyway, if you have understood my problem, can you suggest me a solution?
Thank you.
Hi,
we want to enable client with AMT remotely. I used the AMT Configuration Utility to create a XML file which I can use with the ACUconfig tool.
This works fine, but if I want to connect me to a system it asks for a passcode. How can I set the option user consent to not required?
I found out that I can set option this with the tool ACUconfig.exe ConfigViaUSB, but we doesn't want to use USB sticks on 1000 machines
Best regards
why aren't there any windows 10 drivers for this hardware ?
I recently Installed brand new parts, and ran into some problems and fixed that just to boot up my computer and install all my drivers and The first one is my chipset driver... But when i do it through the CD i got for msi motherboards it just stops at 99%... Well my next plan is to install it thorugh your guys website and even at that it says unknown error can not install. And i get this crash report as follows:
[123C:12BC][2017-02-14T23:09:28]i001: Burn v3.10.0.1519, Windows v10.0 (Build 14393: Service Pack 0), path: C:\Users\Jacob\Downloads\Chipset_10.1.1.42_Public\10.1.1.42\SetupChipset.exe, cmdline: '-burn.unelevated BurnPipe.{FC14747E-D3E5-4DE7-934C-CD1717A1EDC0} {73E299B3-94DC-43DE-B7AC-50A478A56935} 1628 -overall'
[123C:12BC][2017-02-14T23:09:28]i000: Initializing string variable 'CHIPSET_PRODUCT_VERSION' to value '10.1.1.42'
[123C:12BC][2017-02-14T23:09:28]i000: Initializing string variable 'INSTALLER_BUILD_VERSION' to value '3.1'
[123C:12BC][2017-02-14T23:09:28]i000: Initializing string variable 'IIF_ExtractionMapping_SetupChipsetx86.msi' to value ';NullDrivers.cab;NOT VersionNT64'
[123C:12BC][2017-02-14T23:09:28]i000: Initializing string variable 'IIF_ExtractionMapping_SetupChipsetx64.msi' to value ';NullDrivers.cab;VersionNT64'
[123C:12BC][2017-02-14T23:09:29]i000: Setting string variable 'WixBundleLog' to value 'C:\Users\Jacob\AppData\Local\Temp\Intel\Logs\Chipset_20170214230929.log'
[123C:12BC][2017-02-14T23:09:29]i000: Setting string variable 'WixBundleOriginalSource' to value 'C:\Users\Jacob\Downloads\Chipset_10.1.1.42_Public\10.1.1.42\SetupChipset.exe'
[123C:12BC][2017-02-14T23:09:29]i000: Setting string variable 'WixBundleOriginalSourceFolder' to value 'C:\Users\Jacob\Downloads\Chipset_10.1.1.42_Public\10.1.1.42\'
[123C:12BC][2017-02-14T23:09:29]i052: Condition 'VersionNT >= v6.1 OR (VersionNT = v6.0 AND NTProductType = 3)' evaluates to true.
[123C:12BC][2017-02-14T23:09:29]i000: Setting string variable 'WixBundleName' to value 'Intel(R) Chipset Device Software'
[123C:12BC][2017-02-14T23:09:29]i000: Loading managed bootstrapper application.
[123C:12BC][2017-02-14T23:09:29]i000: Creating BA thread to run asynchronously.
[123C:0B30][2017-02-14T23:09:29]i000: ** MBA ** Command line:-overall
[123C:0B30][2017-02-14T23:09:29]i000: Setting string variable 'WixBundleName' to value 'Intel(R) Chipset Device Software'
[123C:0B30][2017-02-14T23:09:29]i000: ** MBA ** Calling Engine.Detect()
[123C:12BC][2017-02-14T23:09:29]i100: Detect begin, 3 packages
[123C:12BC][2017-02-14T23:09:29]i000: Setting string variable 'DotNet35' to value '1'
[123C:12BC][2017-02-14T23:09:29]i000: Setting string variable 'DotNet40Client' to value '1'
[123C:12BC][2017-02-14T23:09:29]i000: Setting string variable 'DotNet40Full' to value '1'
[123C:12BC][2017-02-14T23:09:29]i000: Setting string variable 'DotNet45' to value '394802'
[123C:12BC][2017-02-14T23:09:29]i102: Detected related bundle: {c7f54569-0018-439c-809a-48046a4d4ebc}, type: Upgrade, scope: PerMachine, version: 10.1.1.9, operation: MajorUpgrade
[123C:12BC][2017-02-14T23:09:29]i000: ** MBA ** Related bundle detected: BundleTag: '' ProductCode: '{c7f54569-0018-439c-809a-48046a4d4ebc}' Version: '10.1.1.9' PerMachine: 'True' RelationType: 'Upgrade' Operation: 'MajorUpgrade' Result: 'None'
[123C:12BC][2017-02-14T23:09:29]i052: Condition 'DotNet35 OR DotNet40Client OR DotNet40Full OR (DotNet45 >= 378389)' evaluates to true.
[123C:12BC][2017-02-14T23:09:29]i101: Detected package: DotNet45, state: Present, cached: None
[123C:12BC][2017-02-14T23:09:29]i101: Detected package: SetupChipsetx86.msi, state: Absent, cached: None
[123C:12BC][2017-02-14T23:09:29]i104: Detected package: SetupChipsetx86.msi, feature: NullDriverFeature, state: Absent
[123C:12BC][2017-02-14T23:09:29]i104: Detected package: SetupChipsetx86.msi, feature: PackageVersionFeature, state: Absent
[123C:12BC][2017-02-14T23:09:29]i104: Detected package: SetupChipsetx86.msi, feature: LicenseAgreementFeature, state: Absent
[123C:12BC][2017-02-14T23:09:29]i101: Detected package: SetupChipsetx64.msi, state: Absent, cached: None
[123C:12BC][2017-02-14T23:09:29]i104: Detected package: SetupChipsetx64.msi, feature: NullDriverFeature, state: Absent
[123C:12BC][2017-02-14T23:09:29]i104: Detected package: SetupChipsetx64.msi, feature: PackageVersionFeature, state: Absent
[123C:12BC][2017-02-14T23:09:29]i104: Detected package: SetupChipsetx64.msi, feature: LicenseAgreementFeature, state: Absent
[123C:12BC][2017-02-14T23:09:29]i199: Detect complete, result: 0x0
[123C:12BC][2017-02-14T23:10:06]i200: Plan begin, 3 packages, action: Install
[123C:12BC][2017-02-14T23:10:06]w321: Skipping dependency registration on package with no dependency providers: DotNet45
[123C:12BC][2017-02-14T23:10:06]i052: Condition 'NOT VersionNT64' evaluates to false.
[123C:12BC][2017-02-14T23:10:06]i204: Plan 3 msi features for package: SetupChipsetx86.msi
[123C:12BC][2017-02-14T23:10:06]i203: Planned feature: NullDriverFeature, state: Absent, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None
[123C:12BC][2017-02-14T23:10:06]i203: Planned feature: PackageVersionFeature, state: Absent, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None
[123C:12BC][2017-02-14T23:10:06]i203: Planned feature: LicenseAgreementFeature, state: Absent, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None
[123C:12BC][2017-02-14T23:10:06]i052: Condition 'VersionNT64' evaluates to true.
[123C:12BC][2017-02-14T23:10:06]i204: Plan 3 msi features for package: SetupChipsetx64.msi
[123C:12BC][2017-02-14T23:10:06]i203: Planned feature: NullDriverFeature, state: Absent, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None
[123C:12BC][2017-02-14T23:10:06]i203: Planned feature: PackageVersionFeature, state: Absent, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None
[123C:12BC][2017-02-14T23:10:06]i203: Planned feature: LicenseAgreementFeature, state: Absent, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None
[123C:12BC][2017-02-14T23:10:06]i000: Setting string variable 'WixBundleRollbackLog_SetupChipsetx64.msi' to value 'C:\Users\Jacob\AppData\Local\Temp\Intel\Logs\Chipset_20170214230929_000_SetupChipsetx64.msi_rollback.log'
[123C:12BC][2017-02-14T23:10:06]i000: Setting string variable 'WixBundleLog_SetupChipsetx64.msi' to value 'C:\Users\Jacob\AppData\Local\Temp\Intel\Logs\Chipset_20170214230929_000_SetupChipsetx64.msi.log'
[123C:12BC][2017-02-14T23:10:06]i201: Planned package: DotNet45, state: Present, default requested: Present, ba requested: Present, execute: None, rollback: None, cache: No, uncache: No, dependency: None
[123C:12BC][2017-02-14T23:10:06]i201: Planned package: SetupChipsetx86.msi, state: Absent, default requested: Absent, ba requested: Absent, execute: None, rollback: None, cache: No, uncache: No, dependency: None
[123C:12BC][2017-02-14T23:10:06]i201: Planned package: SetupChipsetx64.msi, state: Absent, default requested: Present, ba requested: Present, execute: Install, rollback: Uninstall, cache: Yes, uncache: No, dependency: Register
[123C:12BC][2017-02-14T23:10:06]i207: Planned related bundle: {c7f54569-0018-439c-809a-48046a4d4ebc}, type: Upgrade, default requested: Absent, ba requested: Absent, execute: Uninstall, rollback: Install, dependency: None
[123C:12BC][2017-02-14T23:10:06]i299: Plan complete, result: 0x0
[123C:0B30][2017-02-14T23:10:06]i000: Setting string variable 'IIF_MSI_SWITCHES' to value 'overall'
[123C:0B30][2017-02-14T23:10:06]i000: ** MBA ** Getting window handle.
[123C:0B30][2017-02-14T23:10:06]i000: ** MBA ** Calling Engine.Apply(). Window handle: 263614
[123C:12BC][2017-02-14T23:10:06]i300: Apply begin
[065C:06EC][2017-02-14T23:10:06]i370: Session begin, registration key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{49bc1e38-39b4-4728-9e75-cbe67ba9a329}, options: 0x7, disable resume: No
[065C:06EC][2017-02-14T23:10:06]i000: Caching bundle from: 'C:\Users\Jacob\AppData\Local\Temp\{49bc1e38-39b4-4728-9e75-cbe67ba9a329}\.be\SetupChipset.exe' to: 'C:\ProgramData\Package Cache\{49bc1e38-39b4-4728-9e75-cbe67ba9a329}\SetupChipset.exe'
[065C:06EC][2017-02-14T23:10:06]i320: Registering bundle dependency provider: {49bc1e38-39b4-4728-9e75-cbe67ba9a329}, version: 10.1.1.42
[065C:06EC][2017-02-14T23:10:06]i371: Updating session, registration key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{49bc1e38-39b4-4728-9e75-cbe67ba9a329}, resume: Active, restart initiated: No, disable resume: No
[065C:0C44][2017-02-14T23:10:06]i305: Verified acquired payload: SetupChipsetx64.msi at path: C:\ProgramData\Package Cache\.unverified\SetupChipsetx64.msi, moving to: C:\ProgramData\Package Cache\{36A16AC6-68D4-44C3-B224-608601D6B353}v10.1.1.42\SetupChipsetx64.msi.
[065C:0C44][2017-02-14T23:10:06]i305: Verified acquired payload: cab4FADBDD6DC6637E75E196F741A3F14D1 at path: C:\ProgramData\Package Cache\.unverified\cab4FADBDD6DC6637E75E196F741A3F14D1, moving to: C:\ProgramData\Package Cache\{36A16AC6-68D4-44C3-B224-608601D6B353}v10.1.1.42\media1.cab.
[065C:06EC][2017-02-14T23:10:06]i323: Registering package dependency provider: {36A16AC6-68D4-44C3-B224-608601D6B353}, version: 10.1.1.42, package: SetupChipsetx64.msi
[065C:06EC][2017-02-14T23:10:06]i301: Applying execute package: SetupChipsetx64.msi, action: Install, path: C:\ProgramData\Package Cache\{36A16AC6-68D4-44C3-B224-608601D6B353}v10.1.1.42\SetupChipsetx64.msi, arguments: ' MSIFASTINSTALL="7" IIF_MSI_SWITCHES="overall" ARPSYSTEMCOMPONENT="1"'
[065C:06EC][2017-02-14T23:10:09]e000: Error 0x80070652: Failed to install MSI package.
[065C:06EC][2017-02-14T23:10:09]e000: Error 0x80070652: Failed to execute MSI package.
[123C:12BC][2017-02-14T23:10:09]e000: Error 0x80070652: Failed to configure per-machine MSI package.
[123C:12BC][2017-02-14T23:10:09]i319: Applied execute package: SetupChipsetx64.msi, result: 0x80070652, restart: None
[123C:12BC][2017-02-14T23:10:09]e000: Error 0x80070652: Failed to execute MSI package.
[065C:06EC][2017-02-14T23:10:09]i318: Skipped rollback of package: SetupChipsetx64.msi, action: Uninstall, already: Absent
[123C:12BC][2017-02-14T23:10:09]i319: Applied rollback package: SetupChipsetx64.msi, result: 0x0, restart: None
[065C:06EC][2017-02-14T23:10:09]i329: Removed package dependency provider: {36A16AC6-68D4-44C3-B224-608601D6B353}, package: SetupChipsetx64.msi
[065C:06EC][2017-02-14T23:10:09]i351: Removing cached package: SetupChipsetx64.msi, from path: C:\ProgramData\Package Cache\{36A16AC6-68D4-44C3-B224-608601D6B353}v10.1.1.42\
[065C:06EC][2017-02-14T23:10:09]i329: Removed package dependency provider: {1B02E5E5-D964-4018-9CB0-9836B78BB375}, package: SetupChipsetx86.msi
[065C:06EC][2017-02-14T23:10:09]i372: Session end, registration key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{49bc1e38-39b4-4728-9e75-cbe67ba9a329}, resume: None, restart: None, disable resume: No
[065C:06EC][2017-02-14T23:10:09]i330: Removed bundle dependency provider: {49bc1e38-39b4-4728-9e75-cbe67ba9a329}
[065C:06EC][2017-02-14T23:10:09]i352: Removing cached bundle: {49bc1e38-39b4-4728-9e75-cbe67ba9a329}, from path: C:\ProgramData\Package Cache\{49bc1e38-39b4-4728-9e75-cbe67ba9a329}\
[065C:06EC][2017-02-14T23:10:09]i371: Updating session, registration key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{49bc1e38-39b4-4728-9e75-cbe67ba9a329}, resume: None, restart initiated: No, disable resume: No
[123C:12BC][2017-02-14T23:10:09]i000: ** MBA ** Apply complete. Status: '-2147023278' Restart: 'None' Result: 'None'
[123C:12BC][2017-02-14T23:10:09]i399: Apply complete, result: 0x80070652, restart: None, ba requested restart: No
[123C:0B30][2017-02-14T23:10:09]e000: ** MBA ** Unknown error.
[123C:0B30][2017-02-14T23:10:12]i000: ** MBA ** ResultCode=1618
[123C:12BC][2017-02-14T23:10:12]i500: Shutting down, exit code: 0x652
[123C:12BC][2017-02-14T23:10:12]i410: Variable: CHIPSET_PRODUCT_VERSION = 10.1.1.42
[123C:12BC][2017-02-14T23:10:12]i410: Variable: DotNet35 = 1
[123C:12BC][2017-02-14T23:10:12]i410: Variable: DotNet40Client = 1
[123C:12BC][2017-02-14T23:10:12]i410: Variable: DotNet40Full = 1
[123C:12BC][2017-02-14T23:10:12]i410: Variable: DotNet45 = 394802
[123C:12BC][2017-02-14T23:10:12]i410: Variable: IIF_ExtractionMapping_SetupChipsetx64.msi = ;NullDrivers.cab;VersionNT64
[123C:12BC][2017-02-14T23:10:12]i410: Variable: IIF_ExtractionMapping_SetupChipsetx86.msi = ;NullDrivers.cab;NOT VersionNT64
[123C:12BC][2017-02-14T23:10:12]i410: Variable: IIF_MSI_SWITCHES = overall
[123C:12BC][2017-02-14T23:10:12]i410: Variable: INSTALLER_BUILD_VERSION = 3.1
[123C:12BC][2017-02-14T23:10:12]i410: Variable: NTProductType = 1
[123C:12BC][2017-02-14T23:10:12]i410: Variable: VersionNT = 10.0.0.0
[123C:12BC][2017-02-14T23:10:12]i410: Variable: VersionNT64 = 10.0.0.0
[123C:12BC][2017-02-14T23:10:12]i410: Variable: WixBundleAction = 4
[123C:12BC][2017-02-14T23:10:12]i410: Variable: WixBundleElevated = 1
[123C:12BC][2017-02-14T23:10:12]i410: Variable: WixBundleLog = C:\Users\Jacob\AppData\Local\Temp\Intel\Logs\Chipset_20170214230929.log
[123C:12BC][2017-02-14T23:10:12]i410: Variable: WixBundleLog_SetupChipsetx64.msi = C:\Users\Jacob\AppData\Local\Temp\Intel\Logs\Chipset_20170214230929_000_SetupChipsetx64.msi.log
[123C:12BC][2017-02-14T23:10:12]i410: Variable: WixBundleManufacturer = Intel(R) Corporation
[123C:12BC][2017-02-14T23:10:12]i410: Variable: WixBundleName = Intel(R) Chipset Device Software
[123C:12BC][2017-02-14T23:10:12]i410: Variable: WixBundleOriginalSource = C:\Users\Jacob\Downloads\Chipset_10.1.1.42_Public\10.1.1.42\SetupChipset.exe
[123C:12BC][2017-02-14T23:10:12]i410: Variable: WixBundleOriginalSourceFolder = C:\Users\Jacob\Downloads\Chipset_10.1.1.42_Public\10.1.1.42\
[123C:12BC][2017-02-14T23:10:12]i410: Variable: WixBundleProviderKey = {49bc1e38-39b4-4728-9e75-cbe67ba9a329}
[123C:12BC][2017-02-14T23:10:12]i410: Variable: WixBundleRollbackLog_SetupChipsetx64.msi = C:\Users\Jacob\AppData\Local\Temp\Intel\Logs\Chipset_20170214230929_000_SetupChipsetx64.msi_rollback.log
[123C:12BC][2017-02-14T23:10:12]i410: Variable: WixBundleTag =
[123C:12BC][2017-02-14T23:10:12]i410: Variable: WixBundleVersion = 10.1.1.42
[123C:12BC][2017-02-14T23:10:12]i007: Exit code: 0x652, restarting: No
: Please help me out with this so i can make my computer run like its meant to run.
I have a system that was built for me using the following components (as listed by Belarc):
Board: Intel Corporation DZ68DB AAG27985-104
Serial Number: BTDB2090013L
Bus Clock: 100 megahertz
BIOS: Intel Corp. DBZ6810H.86A.0032.2011.0928.1502 09/28/2011
3.10 gigahertz Intel Core i5-2400
32 kilobyte primary memory cache
1024 kilobyte secondary memory cache
6144 kilobyte tertiary memory cache
64-bit ready
Multi-core (4 total)
Not hyper-threaded
System memory is 16 GB, OS is Win7 64-bit.
I am trying to find a way to install an ATAPI device, an internal ZIP 100 drive, but the controllers (PCI or PCI-e) that I have tried all seem to conflict with or befuddle the system. An Adaptec SCSI PCI controller can communicate successfully with and external ZIP drive, but so far I have not been able to install one internally. I'm wondering if anyone has a suggestion or solution to this problem.
Thanks for your replies.
Hi there,
I have got an issue with a custom USB 2.0 device (with our own firmware) regarding enumeration and driver installation in windows 7 using USB 3.0 extensible Host Controller driver.
The devices uses the BOS descriptor (OS 1.0) to provide a compatible ID (RNDIS) for selecting the appropriate inf file / driver (rndiscmp.inf / rndiscmp6.sys). This works fine in Windows 7 using (native Microsoft) USB 2.0 driver and also in Windows 8 using USB 3.0 or 2.0 with MS driver (on many different installations). But it does not work in Windows 7 using intel USB 3.0 extensible Host Controller (using a VIA Chipset/driver stack it works!). Analyzing USB traffic I can observe that the Descriptor is requested from the device. Hereupon the compatible ID is sent to the PC but it can not be found in registry and hence it is not used to select the driver automatically (evaluating setupapi.dev). The driver must be chosen manually then.
Actually the USB requests are the same as in the USB 2.0 case but something goes wrong in intel USB 3.0 driver stack.
Does anybody have any idea? Or any additional debugging possibility?
Thank you very much!
Martin
After version 10.1.1.13, some drivers are wrong drver date with 1/1/1970, and So farnotsolved, at version 10.1.1.42, all of them are worng driver date,What the hellwhat the heck!!!!
; ************************************************************
; ************************************************************
; ** Filename: SkylakeSystem.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=Skylake.cat
DriverVer=01/01/1970, 10.1.1.42
Hi,
I used Intel® Driver Update today to see if there was a new chipset driver, and there was a new driver, but every time i try to install it, I get "Unknow error", your program says told me this
Installed Version: 10.0.14393.0
Latest Version: 10.1.1.14
But it will not install driver
I use
Windows 10 64Bit
P5Q-EM Motherboard from ASUS, and the chipset driver there is from 2009
[0AA8:26F4][2017-02-23T20:24:37]i001: Burn v3.7.1224.0, Windows v6.2 (Build 9200: Service Pack 0), path: C:\Users\Tower\Downloads\Intel Components\SetupChipset.exe, cmdline: '-burn.unelevated BurnPipe.{35D389FB-6756-4B38-9711-B39607810130} {C6DB8491-D187-40A9-A4B3-F97AE68717AC} 6956'
[0AA8:26F4][2017-02-23T20:24:37]i000: Initializing string variable 'IIF_ProductVersion' to value '10.1.1.14'
[0AA8:26F4][2017-02-23T20:24:37]i000: Initializing string variable 'IIF_InstallerVersion' to value '3.1.6'
[0AA8:26F4][2017-02-23T20:24:37]i000: Initializing string variable 'IIF_ExtractionMapping_SetupChipsetx86.msi' to value ';NullDrivers.cab;NOT VersionNT64'
[0AA8:26F4][2017-02-23T20:24:37]i000: Initializing string variable 'IIF_ExtractionMapping_SetupChipsetx64.msi' to value ';NullDrivers.cab;VersionNT64'
[0AA8:26F4][2017-02-23T20:24:38]i000: Setting string variable 'WixBundleLog' to value 'C:\Users\Tower\AppData\Local\Temp\Intel\Logs\Chipset_20170223202438.log'
[0AA8:26F4][2017-02-23T20:24:38]i000: Setting string variable 'WixBundleOriginalSource' to value 'C:\Users\Tower\Downloads\Intel Components\SetupChipset.exe'
[0AA8:26F4][2017-02-23T20:24:38]i052: Condition 'VersionNT >= v6.1 OR (VersionNT = v6.0 AND NTProductType = 3)' evaluates to true.
[0AA8:26F4][2017-02-23T20:24:38]i000: Setting string variable 'WixBundleName' to value 'Intel(R) Chipset Device Software'
[0AA8:26F4][2017-02-23T20:24:38]i000: Loading managed bootstrapper application.
[0AA8:26F4][2017-02-23T20:24:38]i000: Creating BA thread to run asynchronously.
[0AA8:2ADC][2017-02-23T20:24:38]i000: ** MBA ** Command line:
[0AA8:2ADC][2017-02-23T20:24:38]i000: Setting string variable 'WixBundleName' to value 'Intel® Chipset Device Software'
[0AA8:2ADC][2017-02-23T20:24:38]i000: ** MBA ** Calling Engine.Detect()
[0AA8:26F4][2017-02-23T20:24:38]i100: Detect begin, 3 packages
[0AA8:26F4][2017-02-23T20:24:38]i000: Setting string variable 'DotNet35' to value '1'
[0AA8:26F4][2017-02-23T20:24:38]i000: Setting string variable 'DotNet40Client' to value '1'
[0AA8:26F4][2017-02-23T20:24:38]i000: Setting string variable 'DotNet40Full' to value '1'
[0AA8:26F4][2017-02-23T20:24:38]i000: Setting string variable 'DotNet45' to value '394802'
[0AA8:26F4][2017-02-23T20:24:38]i052: Condition 'DotNet35 OR DotNet40Client OR DotNet40Full OR (DotNet45 >= 378389)' evaluates to true.
[0AA8:26F4][2017-02-23T20:24:39]i101: Detected package: DotNet45, state: Present, cached: None
[0AA8:26F4][2017-02-23T20:24:39]i101: Detected package: SetupChipsetx86.msi, state: Absent, cached: None
[0AA8:26F4][2017-02-23T20:24:39]i104: Detected package: SetupChipsetx86.msi, feature: NullDriverFeature, state: Absent
[0AA8:26F4][2017-02-23T20:24:39]i104: Detected package: SetupChipsetx86.msi, feature: PackageVersionFeature, state: Absent
[0AA8:26F4][2017-02-23T20:24:39]i104: Detected package: SetupChipsetx86.msi, feature: LicenseAgreementFeature, state: Absent
[0AA8:26F4][2017-02-23T20:24:39]i101: Detected package: SetupChipsetx64.msi, state: Absent, cached: None
[0AA8:26F4][2017-02-23T20:24:39]i104: Detected package: SetupChipsetx64.msi, feature: NullDriverFeature, state: Absent
[0AA8:26F4][2017-02-23T20:24:39]i104: Detected package: SetupChipsetx64.msi, feature: PackageVersionFeature, state: Absent
[0AA8:26F4][2017-02-23T20:24:39]i104: Detected package: SetupChipsetx64.msi, feature: LicenseAgreementFeature, state: Absent
[0AA8:26F4][2017-02-23T20:24:39]i199: Detect complete, result: 0x0
[0AA8:26F4][2017-02-23T20:24:43]i200: Plan begin, 3 packages, action: Install
[0AA8:26F4][2017-02-23T20:24:43]w321: Skipping dependency registration on package with no dependency providers: DotNet45
[0AA8:26F4][2017-02-23T20:24:43]i052: Condition 'NOT VersionNT64' evaluates to false.
[0AA8:26F4][2017-02-23T20:24:43]i204: Plan 3 msi features for package: SetupChipsetx86.msi
[0AA8:26F4][2017-02-23T20:24:43]i203: Planned feature: NullDriverFeature, state: Absent, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None
[0AA8:26F4][2017-02-23T20:24:43]i203: Planned feature: PackageVersionFeature, state: Absent, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None
[0AA8:26F4][2017-02-23T20:24:43]i203: Planned feature: LicenseAgreementFeature, state: Absent, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None
[0AA8:26F4][2017-02-23T20:24:43]i052: Condition 'VersionNT64' evaluates to true.
[0AA8:26F4][2017-02-23T20:24:43]i204: Plan 3 msi features for package: SetupChipsetx64.msi
[0AA8:26F4][2017-02-23T20:24:43]i203: Planned feature: NullDriverFeature, state: Absent, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None
[0AA8:26F4][2017-02-23T20:24:43]i203: Planned feature: PackageVersionFeature, state: Absent, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None
[0AA8:26F4][2017-02-23T20:24:43]i203: Planned feature: LicenseAgreementFeature, state: Absent, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None
[0AA8:26F4][2017-02-23T20:24:43]i000: Setting string variable 'WixBundleRollbackLog_SetupChipsetx64.msi' to value 'C:\Users\Tower\AppData\Local\Temp\Intel\Logs\Chipset_20170223202438_0_SetupChipsetx64.msi_rollback.log'
[0AA8:26F4][2017-02-23T20:24:43]i000: Setting string variable 'WixBundleLog_SetupChipsetx64.msi' to value 'C:\Users\Tower\AppData\Local\Temp\Intel\Logs\Chipset_20170223202438_0_SetupChipsetx64.msi.log'
[0AA8:26F4][2017-02-23T20:24:43]i201: Planned package: DotNet45, state: Present, default requested: Present, ba requested: Present, execute: None, rollback: None, cache: No, uncache: No, dependency: None
[0AA8:26F4][2017-02-23T20:24:43]i201: Planned package: SetupChipsetx86.msi, state: Absent, default requested: Absent, ba requested: Absent, execute: None, rollback: None, cache: No, uncache: No, dependency: None
[0AA8:26F4][2017-02-23T20:24:43]i201: Planned package: SetupChipsetx64.msi, state: Absent, default requested: Present, ba requested: Present, execute: Install, rollback: Uninstall, cache: Yes, uncache: No, dependency: Register
[0AA8:26F4][2017-02-23T20:24:43]i299: Plan complete, result: 0x0
[0AA8:2ADC][2017-02-23T20:24:43]i000: Setting string variable 'IIF_MSI_SWITCHES' to value ''
[0AA8:2ADC][2017-02-23T20:24:43]i000: ** MBA ** Getting window handle.
[0AA8:2ADC][2017-02-23T20:24:43]i000: ** MBA ** Calling Engine.Apply(). Window handle: 5308976
[0AA8:26F4][2017-02-23T20:24:43]i300: Apply begin
[1B2C:1BA4][2017-02-23T20:24:43]i000: Caching bundle from: 'C:\Users\Tower\AppData\Local\Temp\{619e726e-d2b4-4e28-9568-c964fd81ee6c}\.be\SetupChipset.exe' to: 'C:\ProgramData\Package Cache\{619e726e-d2b4-4e28-9568-c964fd81ee6c}\SetupChipset.exe'
[1B2C:1BA4][2017-02-23T20:24:43]i320: Registering bundle dependency provider: {619e726e-d2b4-4e28-9568-c964fd81ee6c}, version: 10.1.1.14
[1B2C:13F4][2017-02-23T20:24:43]i305: Verified acquired payload: SetupChipsetx64.msi at path: C:\ProgramData\Package Cache\.unverified\SetupChipsetx64.msi, moving to: C:\ProgramData\Package Cache\{FEBB7B48-CC1C-4A50-A497-FA21413F6BE9}v10.1.1.14\SetupChipsetx64.msi.
[1B2C:13F4][2017-02-23T20:24:43]i305: Verified acquired payload: cab4FADBDD6DC6637E75E196F741A3F14D1 at path: C:\ProgramData\Package Cache\.unverified\cab4FADBDD6DC6637E75E196F741A3F14D1, moving to: C:\ProgramData\Package Cache\{FEBB7B48-CC1C-4A50-A497-FA21413F6BE9}v10.1.1.14\media1.cab.
[1B2C:1BA4][2017-02-23T20:24:43]i323: Registering package dependency provider: {FEBB7B48-CC1C-4A50-A497-FA21413F6BE9}, version: 10.1.1.14, package: SetupChipsetx64.msi
[1B2C:1BA4][2017-02-23T20:24:43]i301: Applying execute package: SetupChipsetx64.msi, action: Install, path: C:\ProgramData\Package Cache\{FEBB7B48-CC1C-4A50-A497-FA21413F6BE9}v10.1.1.14\SetupChipsetx64.msi, arguments: ' MSIFASTINSTALL="7" IIF_MSI_SWITCHES="" ARPSYSTEMCOMPONENT="1"'
[1B2C:1BA4][2017-02-23T20:24:53]e000: Error 0x80070643: Failed to install MSI package.
[1B2C:1BA4][2017-02-23T20:24:53]e000: Error 0x80070643: Failed to execute MSI package.
[0AA8:26F4][2017-02-23T20:24:53]e000: Error 0x80070643: Failed to configure per-machine MSI package.
[0AA8:26F4][2017-02-23T20:24:53]i319: Applied execute package: SetupChipsetx64.msi, result: 0x80070643, restart: None
[0AA8:26F4][2017-02-23T20:24:53]e000: Error 0x80070643: Failed to execute MSI package.
[1B2C:1BA4][2017-02-23T20:24:53]i301: Applying rollback package: SetupChipsetx64.msi, action: Uninstall, path: C:\ProgramData\Package Cache\{FEBB7B48-CC1C-4A50-A497-FA21413F6BE9}v10.1.1.14\SetupChipsetx64.msi, arguments: ' MSIFASTINSTALL="7" IIF_MSI_SWITCHES="" ARPSYSTEMCOMPONENT="1"'
[1B2C:1BA4][2017-02-23T20:24:55]e000: Error 0x80070643: Failed to uninstall MSI package.
[1B2C:1BA4][2017-02-23T20:24:55]e000: Error 0x80070643: Failed to execute MSI package.
[0AA8:26F4][2017-02-23T20:24:55]e000: Error 0x80070643: Failed to configure per-machine MSI package.
[0AA8:26F4][2017-02-23T20:24:55]i319: Applied rollback package: SetupChipsetx64.msi, result: 0x80070643, restart: None
[1B2C:1BA4][2017-02-23T20:24:55]i329: Removed package dependency provider: {FEBB7B48-CC1C-4A50-A497-FA21413F6BE9}, package: SetupChipsetx64.msi
[1B2C:1BA4][2017-02-23T20:24:55]i351: Removing cached package: SetupChipsetx64.msi, from path: C:\ProgramData\Package Cache\{FEBB7B48-CC1C-4A50-A497-FA21413F6BE9}v10.1.1.14\
[1B2C:1BA4][2017-02-23T20:24:55]i329: Removed package dependency provider: {23312E5E-F714-4F0B-97F5-4A7E2DEFE61E}, package: SetupChipsetx86.msi
[1B2C:1BA4][2017-02-23T20:24:55]i330: Removed bundle dependency provider: {619e726e-d2b4-4e28-9568-c964fd81ee6c}
[1B2C:1BA4][2017-02-23T20:24:55]i352: Removing cached bundle: {619e726e-d2b4-4e28-9568-c964fd81ee6c}, from path: C:\ProgramData\Package Cache\{619e726e-d2b4-4e28-9568-c964fd81ee6c}\
[0AA8:26F4][2017-02-23T20:24:55]i000: ** MBA ** Apply complete. Status: '-2147023293' Restart: 'None' Result: 'None'
[0AA8:26F4][2017-02-23T20:24:55]i399: Apply complete, result: 0x80070643, restart: None, ba requested restart: No
[0AA8:2ADC][2017-02-23T20:24:55]e000: ** MBA ** Unknow Error.
I had to do a fresh in stall of win 7. Every thing went fine. I upgraded to two 2 TB Samsung EVO 850 drives. Rebuild of RAID 1 was moving along fine -then I got a message that "A hard drive is missing - A hard drive has failed and RAID volume is degraded. Replace the failed drive" System is still running fine on one drive.
questions
1) Is there a way that I can attempt a rebuild of RAID 0?
2) Could it be the Intel Matrix Storage Console 8.9 that is the problem?
3) What is the latest version of Intel Matrix Storage Manager that will work with my Asus Sabertooth z77 motherboard?
4) Is there a way to reformat my SSD drive and see if that fixes the problem?
5) Other solutions appreciated..
Thanks
Richard
Hi
I need to have 2 serial ports with the E3800 chipset on a embedded system under Windows 10.
I installed the HSUART drivers from the Win10 Atom E3800 BSP and I still get only exclamation marks on the 2 UART.
I am also not able to have them initialized as legacy COM.
What do I have to do to be able to use these UART as RS232 ports?
Cheers,
McL
https://s4.postimg.org/k29ruvfjh/erro_driver_update_utility.png
tentei atualizar o driver mas nao consigo pelo driver update utility e agora oque faço pra atualizar ??
Hi All,
What exactly should be done to initialize southbridge ICH6-M in AHCI mode? (I suppose that's what BIOS does every time before handing control over to OS)
Many thanks in advance!
This is what regedit shows,
This is what comes up in the device manager,
But this is what I get while trying to update my Chipset driver through Driver Update Utility 2.7. Am I missing something here? Is 13.2.0.1022 my current chipset driver? If so, how could I have a more advanced driver than the latest one? And if not, what is 13.2.0.1022? Why does Intel detect it that way while regedit and device manager does not? I'm really confused whether I should update or not, thanks a lot in advance.