As we understand, your PC is using a Gigabyte WiFi adapter based on the Intel® Dual Band Wireless-AC 8260, and had BSOD's after installing the driver from Intel® Download Center.
We advise you to contact Gigabyte Support to check on this issue. This type of add-on cards incorporate OEM hardware and may require customized drivers to work properly.
The drivers recommended by Intel® Driver Utility, or found at Intel® Download Center, are generic and may not work with some OEM configurations. Intel recommends that you obtain and use the software provided by the manufacturer.
Install Intel® Wireless Drivers and Software
If the new driver is not working, you may check with Gigabyte if they have an updated version, or you may use a previous driver if it works well with your computer.
I don't believe that Gigabyte support are going to be able to help with this because I am pretty sure that they just ship the original Intel installer for the PROSet Wireless software and driver. I'm a software developer, and one of the first things I did when I encountered the problem was to look at the properties of the netwtw04.sys driver. I found that it was version V22.214.171.124, was built on 7/24/16, and was digitally signed by Intel. So unless Intel builds and digitally signs custom OEM drivers (which I seriously doubt), that would seem to be a strong indication that they are not shipping a custom OEM driver.
I have contacted Gigabyte support anyway, but I'm pretty sure they are going to come back and say that they just ship your installer.
In this case, Gigabyte support would be the best source for support, since they are the manufacturer of the add-on card. Please check with them for assistance as well.
Here are some of the actions that may help to prevent BSOD's:
- Contact the Motherboard Manufacturer and make sure you update the computer BIOS.
- Try using the card in a different PCIe Slot.
- Go the Device Manager, under network adapters, look for the AC 8260 Wireless Adapter and open the properties. Go to the "Power Management" tab and toggle Off/On the option "Allow the computer to turn off this devices to save power". Then check if the behavior changes.
- Disable Fast Startup (Hybrid Boot) in Windows® 10
Try my solution: Latest versions (19.1.0 and 19.0.1) of Intel® Wireless-AC 7260 Plus Bluetooth* (7260HMW) WIFI driver (netwbw02.sys) on Win 10 64-bit is causing frequent system crashes e.g. Intel wireless driver package version 18.40.0. In my case, it stopped the crashes and it maintains stable connection so far....wonder how bad these 19.x.x drivers are....
New update: No, with 18.40.0 version I had one crash, and it did start to lose the connection more often than before....Possibly because in my setup, I have a primary router three floors up, an extender advertising the same SID for both 2.4 and 5 GHz bands in my den...something about the roaming may not work quite well I think...However v. 18.40 drivers seem in general more stable than v. 19 drivers.
I will also try Johnathan suggestion of disabling hybrid fast boot...and report the results with various drivers.
My issue is that I have an AC router, N-extender, 2.4 and 5 GHz bands, and twp mini-PCI-slots in my laptop...plus the different driver versions...many possibilities to test the setup so please give me some time, and I will gladly share the result if I find the solution
Thanks for the info. Very interesting. I too am finding that the 18 version is working great and is stable.
We are glad to know that the previous driver version works better for you. We will forward your feedback about this matter to the proper resources.
Feel free to let us know if you have any additional comments or questions about this topic.
I'd like to add that I have installed the 8260 m.2 card in my pc, and was having many blue screens in Windows 10 as well. I downgraded the driver to 18.40. as JackMark suggested, and haven't had a crash yet.
This is clearly a problem with the drivers, not the motherboard.
We are taking you feedback about the driver into consideration. If you are still having issues and require further assistance, let us know the following information:
- Was the adapter built from factory to your PC?
- Was it working fine before?
- At which time does it fail? Is there are specific task being done when this happens?
- Provide additional system details (PC model, driver version, BIOS version, etc.)
My situation is that this is a PC that I have recently built from components. Everything was running absolutely perfectly after the build, it's running a brand new install of the latest public build of Windows 10 x64, and was originally connected via one of the four gigabit Ethernet ports on the motherboard (an ASRock Rack EP2C602-4L/D16, brand new, latest BIOS, etc.). The motherboard doesn't have on-board Wi-Fi or Bluetooth, so I purchased and installed a Gigabyte GC-WB867D-I REV 4.2, which is basically an Intel AC 8260 mounted on a PCI express board. I installed the drivers provided with the card - frequent crashes. I followed the Intel Driver Update Utility when it suggested a later version - frequent crashes. then I experimented and reverted the older 126.96.36.199 version. Since doing so I have used the system for quite a few hours over last weekend, and have had no issues - not a single crash.
I am not aware of any specific action that causes the crash. I have seen it crash on several occasions before I was even able to complete a Windows login. On other occasions I have been able to use the system (including WiFi and Bluetooth via the card) for a few minutes, but not much longer that that before encountering a crash. Sometimes I have been working in an app, other times I have just been looking at the desktop at the time of a crash. The only constant is that with the later drivers installs, it crashes VERY frequently, so I would expect to be able to reproduce the issue pretty easily if needed.
I can't help wondering if the problem is some edge-case related to multi-threaded code. The reason I say this is that my system isn't exactly what you would call a typical configuration. It has two XEON E5-2670 processors, meaning that it has 16 physical cores and supports 32 concurrent threads. It also has 128GB of RAM. Not sure why that would make a difference, but it's something that is definitely not a "normal" configuration.
Unfortunately I am working out of town for the next two weeks, so I don't currently have access to the system, but I would be more than happy to work with you on this issue when I return. Perhaps you want to try to get some Windows crash dumps or something; a minidump is probably "doable", but trying for a full memory dump probably isn't a good idea due to the amount of RAM present. Let me know if there is anything I can do to help diagnose the issue.
Since you are using a non-standard configuration, we advise you to use the Intel® PROSet/Wireless Software version 18.50 that is working well in your system.
We are continuously working to improve our products and drivers, and we will consider your input about this matter.
My PC was also build from personally-selected components.
Motherboard: Asus Z170I Pro Gaming (I removed the WiFi card that came in the board and replaced it with an Intel 8260)
CPU: Intel Core i7 6700K
RAM: Corsair Vengeance LPX 32GB (2x16GB) DDR4 2133
Graphics: Nvidia GTX 1080 FE
In your case, keep in mind that we do not support custom integrations. The end user is not authorized to install Intel® wireless adapters. They can only be installed by the manufacturer or its authorized representative:
Regulatory Information Regarding Hardware Installation or Upgrade
If the system does not work well with the latest driver after applying the recommendations provided in this thread, then we advise you use the driver that works well, or check with the Computer Manufacturer for assistance.
Of course I don't expect you to support custom setups. There are almost infinite permutations of hardware available, and it's not your responsibility to make sure your drivers work on all of them. I've worked in the software industry, and even wrote a few drivers myself! I completely understand.
I'm just reiterating that it is indeed the driver causing the issue.