Windows 10: Latest Intel Chipset Device Software

Page 3 of 20 FirstFirst 1234513 ... LastLast

  1. Posts : 881
    Windows XP/7/8/8.1/10, Linux, Android, FreeBSD Unix
       15 Aug 2015 #21

    jds63 said: View Post
    hmm..Firefox does not like that site, even though i am not looking for this driver

    Attachment 31598
    Interesting, this site has been around for ages as I've gotten drivers from there since WinXP in 2002.
      My ComputerSystem Spec


  2. Posts : 3,033
    Windows 10 Pro 64 bit
       15 Aug 2015 #22

    Almighty1 said: View Post
    Interesting, this site has been around for ages as I've gotten drivers from there since WinXP in 2002.
    Want a safer one, http://www.guru3d.com/files-details/...-download.html otherwise try your manufacturer's site, be better off, i would not go to these types of sites personally.
      My ComputerSystem Spec

  3.    15 Aug 2015 #23

    jds63 said: View Post
    Alleviate the confusion go to Dell Website put in your laptop model number and check downloads for Windows 10 whichever bit 32 or 64bit
    Laptop is too old to have new drivers, about 2 years.

    petr23 said: View Post
    You don't have to - your PC will run fine/same as with Win 7 ...

    Thanks for the confirmation, that's what I thought.
      My ComputerSystem Spec


  4. Posts : 558
    Windows 10
       15 Aug 2015 #24

    I was confused about all of this Intel chipset stuff and what should my laptop be using and i got a direct response from the man himself "Fernando" who runs his specialized "Win /Raid forums.

    This is what he said to me :

    I personally do not care about the Intel Chipset Device INF files and have never run the installer of any Intel Chipset Device Software. When the Devce Manager should show me a yellow "missing driver" sign for an Intel device, I do a right click onto it, choose the options "Update driver software" > "Browse my computer", hit the "Browse" button, navigate to the folder, which contains the already extracted Intel Chipset Device INF files, which are suitable for my special system. Then the OS will find the correct INF file itself, install it and theyellow mark has gone.
    Since the Intel 6-Series Chipsets are not really new, you can use any Intel Chipset Device INF Files Set, which has been released by Intel within the last 4 years.
    Sorry about the underlining, didn't mean to do that , seems he is saying just use whatever "inf" files are compatible with your system is what i gather.
      My ComputerSystem Spec


  5. Posts : 881
    Windows XP/7/8/8.1/10, Linux, Android, FreeBSD Unix
       15 Aug 2015 #25

    jds63 said: View Post
    Want a safer one, http://www.guru3d.com/files-details/...-download.html otherwise try your manufacturer's site, be better off, i would not go to these types of sites personally.
    Manufacturers site is too slow and they haven't updated anything since 2011, at least for ASUS. I've always been getting things from these types of sites since 2001 and earlier and they have been fine as long as you know what sites are good and what isn't, besides the fact that I and and others modifies nVidia/ATI drivers for laptops that uses their video cards but unsupported by the official driver. I wouldn't trust virus scanners or browsers saying something is bad as there is always the false positives. guru3d link is for 10.1.2.8, the link I mentioned is for 10.1.2.9 which is newer and guru3d does mention 10.1.2.9 in another thread which goes back to stations drivers. Maybe it's flagging it all because the site is in Russian or something.

    ***NEW*** Intel Chipset driver 10.1.2.9 - Guru3D.com Forums
      My ComputerSystem Spec


  6. Posts : 146
    Windows 10 Pro 64bit
       16 Aug 2015 #26

    Why are those "Intel" drivers just in Russian and on Russian sites? Where are the official links to 10.1.2.9? If you google for 10.1.2.9 you wont find any serious links at all, nowhere.
      My ComputerSystem Spec


  7. Posts : 3,033
    Windows 10 Pro 64 bit
       16 Aug 2015 #27

    Almighty1 said: View Post
    Manufacturers site is too slow and they haven't updated anything since 2011, at least for ASUS. I've always been getting things from these types of sites since 2001 and earlier and they have been fine as long as you know what sites are good and what isn't, besides the fact that I and and others modifies nVidia/ATI drivers for laptops that uses their video cards but unsupported by the official driver. I wouldn't trust virus scanners or browsers saying something is bad as there is always the false positives. guru3d link is for 10.1.2.8, the link I mentioned is for 10.1.2.9 which is newer and guru3d does mention 10.1.2.9 in another thread which goes back to stations drivers. Maybe it's flagging it all because the site is in Russian or something.

    ***NEW*** Intel Chipset driver 10.1.2.9 - Guru3D.com Forums

    Are you having trouble with drivers have now, they are from 2011 ? What Intel Chipset Software Driver do you have now ? Before looking for this one, which Intel does not even show to have 10.1.2.9 as 10.1.2.8 is newest one shown even at my motherboard site. ASUS is or was pretty good for this last time i had them, hard to believe do not update anymore, maybe for your board only.

    Truthfully and this is my humble opinion, i would not trust these sites no matter how long they have been around and i see your point not being able to get them from your manufacturer. Did you try to use Intel's site ? Even Intel MEI is not right, why would these sites have it and not Intel's site.

    Firefox has had updates recently to improve on security, so if it tells me not to go there i won't chance it, since i do not know of it.
      My ComputerSystem Spec


  8. Posts : 146
    Windows 10 Pro 64bit
       16 Aug 2015 #28

    I get bsod trying an update with those 10.1.2.9 Intel drivers

    Code:
    Microsoft (R) Windows Debugger Version 10.0.10240.9 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    
    
    Loading Dump File [C:\Temp\MEMORY.DMP]
    Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.
    
    
    
    
    ************* Symbol Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       srv*c:\cache*http://msdl.microsoft.com/download/symbols
    Symbol search path is: srv*c:\cache*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    No .natvis files found at C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\Visualizers.
    Windows 10 Kernel Version 10240 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 10240.16430.amd64fre.th1.150807-2049
    Machine Name:
    Kernel base = 0xfffff803`59818000 PsLoadedModuleList = 0xfffff803`59b3d030
    Debug session time: Sun Aug 16 20:31:13.599 2015 (UTC + 2:00)
    System Uptime: 0 days 2:46:22.305
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ........................................................
    Loading User Symbols
    
    
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    
    Use !analyze -v to get detailed debugging information.
    
    
    BugCheck 113, {1f, ffffe00098b52b80, 0, 0}
    
    
    Probably caused by : dxgkrnl.sys ( dxgkrnl!ADAPTER_RENDER::NotifyDeferredDestructionComplete+8f )
    
    
    Followup:     MachineOwner
    ---------
    
    
    5: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    
    VIDEO_DXGKRNL_FATAL_ERROR (113)
    The dxgkrnl has detected that a violation has occurred. This resulted
    in a condition that dxgkrnl can no longer progress.  By crashing, dxgkrnl
    is attempting to get enough information into the minidump such that somebody
    can pinpoint the crash cause. Any other values after parameter 1 must be
    individually examined according to the subtype.
    Arguments:
    Arg1: 000000000000001f, The subtype of the bugcheck:
    Arg2: ffffe00098b52b80
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    
    
    Debugging Details:
    ------------------
    
    
    
    
    SYSTEM_SKU:  To Be Filled By O.E.M.
    
    
    SYSTEM_VERSION:  To Be Filled By O.E.M.
    
    
    BIOS_DATE:  07/01/2013
    
    
    BASEBOARD_PRODUCT:  Z77 Extreme6
    
    
    BASEBOARD_VERSION:                        
    
    
    BUGCHECK_P1: 1f
    
    
    BUGCHECK_P2: ffffe00098b52b80
    
    
    BUGCHECK_P3: 0
    
    
    BUGCHECK_P4: 0
    
    
    CPU_COUNT: 8
    
    
    CPU_MHZ: d48
    
    
    CPU_VENDOR:  GenuineIntel
    
    
    CPU_FAMILY: 6
    
    
    CPU_MODEL: 3a
    
    
    CPU_STEPPING: 9
    
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    
    BUGCHECK_STR:  0x113
    
    
    PROCESS_NAME:  System
    
    
    CURRENT_IRQL:  0
    
    
    ANALYSIS_VERSION: 10.0.10240.9 amd64fre
    
    
    LAST_CONTROL_TRANSFER:  from fffff801c1ff3c3d to fffff80359965d00
    
    
    STACK_TEXT:  
    ffffd000`afe54828 fffff801`c1ff3c3d : 00000000`00000113 00000000`0000001f ffffe000`98b52b80 00000000`00000000 : nt!KeBugCheckEx
    ffffd000`afe54830 fffff801`c207c63f : ffffe000`98b52b80 ffffe000`9c46c401 ffffe000`9c46c4b0 00000000`00000000 : watchdog!WdLogEvent5_WdCriticalError+0xcd
    ffffd000`afe54870 fffff801`c671fe3f : ffffe000`98c14ba0 ffffd000`afe549a0 ffffe000`9c46c4b0 ffffe000`98bbe840 : dxgkrnl!ADAPTER_RENDER::NotifyDeferredDestructionComplete+0x8f
    ffffd000`afe548a0 fffff801`c672531b : ffffe000`98c0b000 ffffffff`00000000 ffffc000`86eadb40 ffffe000`9c46c4b0 : dxgmms2!VIDMM_GLOBAL::ProcessDeferredCommand+0xa3f
    ffffd000`afe54a40 fffff801`c6728f5d : ffffe000`98c0b000 ffffe000`98c0b000 00000000`00000000 ffffd000`afe54b99 : dxgmms2!VIDMM_WORKER_THREAD::ProcessPendingTerminations+0xa3
    ffffd000`afe54af0 fffff803`598fe948 : ffffe000`95679800 ffffd000`afe54c00 fffff803`59b7b100 fffff803`5996ad00 : dxgmms2!VIDMM_WORKER_THREAD::Run+0x9c1
    ffffd000`afe54c00 fffff803`5996ade6 : fffff803`59b7b180 ffffe000`98bbe840 fffff803`59bf1740 00000000`00000000 : nt!PspSystemThreadStartup+0x58
    ffffd000`afe54c60 00000000`00000000 : ffffd000`afe55000 ffffd000`afe4f000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
    
    
    
    
    STACK_COMMAND:  kb
    
    
    FOLLOWUP_IP: 
    dxgkrnl!ADAPTER_RENDER::NotifyDeferredDestructionComplete+8f
    fffff801`c207c63f eb03            jmp     dxgkrnl!ADAPTER_RENDER::NotifyDeferredDestructionComplete+0x94 (fffff801`c207c644)
    
    
    SYMBOL_STACK_INDEX:  2
    
    
    SYMBOL_NAME:  dxgkrnl!ADAPTER_RENDER::NotifyDeferredDestructionComplete+8f
    
    
    FOLLOWUP_NAME:  MachineOwner
    
    
    MODULE_NAME: dxgkrnl
    
    
    IMAGE_NAME:  dxgkrnl.sys
    
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  55bebfed
    
    
    BUCKET_ID_FUNC_OFFSET:  8f
    
    
    FAILURE_BUCKET_ID:  0x113_dxgkrnl!ADAPTER_RENDER::NotifyDeferredDestructionComplete
    
    
    BUCKET_ID:  0x113_dxgkrnl!ADAPTER_RENDER::NotifyDeferredDestructionComplete
    
    
    PRIMARY_PROBLEM_CLASS:  0x113_dxgkrnl!ADAPTER_RENDER::NotifyDeferredDestructionComplete
    
    
    ANALYSIS_SOURCE:  KM
    
    
    FAILURE_ID_HASH_STRING:  km:0x113_dxgkrnl!adapter_render::notifydeferreddestructioncomplete
    
    
    FAILURE_ID_HASH:  {5460b617-b6dd-456e-0f7a-45a24c5cf63d}
    
    
    Followup:     MachineOwner
    ---------
    
    
    5: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    
    VIDEO_DXGKRNL_FATAL_ERROR (113)
    The dxgkrnl has detected that a violation has occurred. This resulted
    in a condition that dxgkrnl can no longer progress.  By crashing, dxgkrnl
    is attempting to get enough information into the minidump such that somebody
    can pinpoint the crash cause. Any other values after parameter 1 must be
    individually examined according to the subtype.
    Arguments:
    Arg1: 000000000000001f, The subtype of the bugcheck:
    Arg2: ffffe00098b52b80
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    
    
    Debugging Details:
    ------------------
    
    
    
    
    SYSTEM_SKU:  To Be Filled By O.E.M.
    
    
    SYSTEM_VERSION:  To Be Filled By O.E.M.
    
    
    BIOS_DATE:  07/01/2013
    
    
    BASEBOARD_PRODUCT:  Z77 Extreme6
    
    
    BASEBOARD_VERSION:                        
    
    
    BUGCHECK_P1: 1f
    
    
    BUGCHECK_P2: ffffe00098b52b80
    
    
    BUGCHECK_P3: 0
    
    
    BUGCHECK_P4: 0
    
    
    CPU_COUNT: 8
    
    
    CPU_MHZ: d48
    
    
    CPU_VENDOR:  GenuineIntel
    
    
    CPU_FAMILY: 6
    
    
    CPU_MODEL: 3a
    
    
    CPU_STEPPING: 9
    
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    
    BUGCHECK_STR:  0x113
    
    
    PROCESS_NAME:  System
    
    
    CURRENT_IRQL:  0
    
    
    ANALYSIS_VERSION: 10.0.10240.9 amd64fre
    
    
    LAST_CONTROL_TRANSFER:  from fffff801c1ff3c3d to fffff80359965d00
    
    
    STACK_TEXT:  
    ffffd000`afe54828 fffff801`c1ff3c3d : 00000000`00000113 00000000`0000001f ffffe000`98b52b80 00000000`00000000 : nt!KeBugCheckEx
    ffffd000`afe54830 fffff801`c207c63f : ffffe000`98b52b80 ffffe000`9c46c401 ffffe000`9c46c4b0 00000000`00000000 : watchdog!WdLogEvent5_WdCriticalError+0xcd
    ffffd000`afe54870 fffff801`c671fe3f : ffffe000`98c14ba0 ffffd000`afe549a0 ffffe000`9c46c4b0 ffffe000`98bbe840 : dxgkrnl!ADAPTER_RENDER::NotifyDeferredDestructionComplete+0x8f
    ffffd000`afe548a0 fffff801`c672531b : ffffe000`98c0b000 ffffffff`00000000 ffffc000`86eadb40 ffffe000`9c46c4b0 : dxgmms2!VIDMM_GLOBAL::ProcessDeferredCommand+0xa3f
    ffffd000`afe54a40 fffff801`c6728f5d : ffffe000`98c0b000 ffffe000`98c0b000 00000000`00000000 ffffd000`afe54b99 : dxgmms2!VIDMM_WORKER_THREAD::ProcessPendingTerminations+0xa3
    ffffd000`afe54af0 fffff803`598fe948 : ffffe000`95679800 ffffd000`afe54c00 fffff803`59b7b100 fffff803`5996ad00 : dxgmms2!VIDMM_WORKER_THREAD::Run+0x9c1
    ffffd000`afe54c00 fffff803`5996ade6 : fffff803`59b7b180 ffffe000`98bbe840 fffff803`59bf1740 00000000`00000000 : nt!PspSystemThreadStartup+0x58
    ffffd000`afe54c60 00000000`00000000 : ffffd000`afe55000 ffffd000`afe4f000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
    
    
    
    
    STACK_COMMAND:  kb
    
    
    FOLLOWUP_IP: 
    dxgkrnl!ADAPTER_RENDER::NotifyDeferredDestructionComplete+8f
    fffff801`c207c63f eb03            jmp     dxgkrnl!ADAPTER_RENDER::NotifyDeferredDestructionComplete+0x94 (fffff801`c207c644)
    
    
    SYMBOL_STACK_INDEX:  2
    
    
    SYMBOL_NAME:  dxgkrnl!ADAPTER_RENDER::NotifyDeferredDestructionComplete+8f
    
    
    FOLLOWUP_NAME:  MachineOwner
    
    
    MODULE_NAME: dxgkrnl
    
    
    IMAGE_NAME:  dxgkrnl.sys
    
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  55bebfed
    
    
    BUCKET_ID_FUNC_OFFSET:  8f
    
    
    FAILURE_BUCKET_ID:  0x113_dxgkrnl!ADAPTER_RENDER::NotifyDeferredDestructionComplete
    
    
    BUCKET_ID:  0x113_dxgkrnl!ADAPTER_RENDER::NotifyDeferredDestructionComplete
    
    
    PRIMARY_PROBLEM_CLASS:  0x113_dxgkrnl!ADAPTER_RENDER::NotifyDeferredDestructionComplete
    
    
    ANALYSIS_SOURCE:  KM
    
    
    FAILURE_ID_HASH_STRING:  km:0x113_dxgkrnl!adapter_render::notifydeferreddestructioncomplete
    
    
    FAILURE_ID_HASH:  {5460b617-b6dd-456e-0f7a-45a24c5cf63d}
    
    
    Followup:     MachineOwner
    ---------
      My ComputerSystem Spec


  9. Posts : 881
    Windows XP/7/8/8.1/10, Linux, Android, FreeBSD Unix
       16 Aug 2015 #29

    jds63 said: View Post
    Are you having trouble with drivers have now, they are from 2011 ? What Intel Chipset Software Driver do you have now ? Before looking for this one, which Intel does not even show to have 10.1.2.9 as 10.1.2.8 is newest one shown even at my motherboard site. ASUS is or was pretty good for this last time i had them, hard to believe do not update anymore, maybe for your board only.

    Truthfully and this is my humble opinion, i would not trust these sites no matter how long they have been around and i see your point not being able to get them from your manufacturer. Did you try to use Intel's site ? Even Intel MEI is not right, why would these sites have it and not Intel's site.

    Firefox has had updates lately to improve on security, so tells me not to go there i won't why chance it sure not only place as you have seen.
    It's not trouble with drivers but rather I wanted to keep things to the latest on Win10 after the upgrade. Intel's site has always been behind as drivers are usually always leaked on other sites first. In this case, it's for my ASUS G74SX Notebook since my desktop is still running WinXP on a ASUS P4C800-E Deluxe in which Intel drivers had no longer supported it since I think version 6 or earlier.

    I have seen lots of false positives just like Norton had been deleting all of my Netgear R7000 router firmware files flagging it as unsafe when they are the official versions from both Netgear and DD-WRT. Manufacturers usually only release drivers whenever they feel like it as long as the existing drivers work, no different than nVidia drivers are obsolete if you base it on the manufacturers site while I'm using the drivers directly from nVidia that is updated with GeForce Experience. Manufacturers don't really want to support multiple versions of some driver or software so they will just release whatever ships with the system or motherboard, otherwise they will be putting more money into support which is nearly non-existent.
      My ComputerSystem Spec


  10. Posts : 881
    Windows XP/7/8/8.1/10, Linux, Android, FreeBSD Unix
       16 Aug 2015 #30

    I've been running 10.1.2.9 drivers since 22 hours ago and haven't had any problems. Besides, didn't someone say that Intel Chipset Drivers are really INF files and not actual driver binaries so it doesn't come with binaries to cause a BSOD.
      My ComputerSystem Spec


 
Page 3 of 20 FirstFirst 1234513 ... LastLast

Related Threads
Latest AMD Chipset Drivers Released in Drivers and Hardware
Latest AMD Crimson Chipset Drivers Released WHQL version: 16.12.2 Release Date: January 23rd 2017 Supports: Windows 7, Windows 8.1, and Windows 10 32-bit AMD Chipset Drivers Download
gang i've been here before but cannot remember what I used. need to custom-set resolution to modern 1366x768 on a inspiron 530 core 2 machine using intel's g33 family i get 1280x768 - this is build 10074 and a lot of strange things here. no place to...
anyone here running Win10 on AMD notebook, Zacate family ? just wondering how many drivers I'll be missing and how to find. I'm wanting to try this on Lenovo Thinkpad X120e 10 is running swell on my A4-3300m based HP G4-1117dx except for...
Windows 10 as an EFI device in General Support
I have a Acer Travelmate B113 Laptop which I have recently installed windows 10 on, however when it comes to booting the laptop, I have to go into the boot selection menu and select EFI: Windows Boot Manager. I have tried setting this option as the...
No Device Driver found in Installation and Upgrade
Hi, I'm attempting to dual boot windows 7 and Windows 10 preview, however when I run the setup I get up to point where it wants me to choose the drive where I want to install, but before I get to that point I get the following message. "A...
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 23:33.
Find Us