Updating Intel Pro Wireless from 17.16.1 to 18.11.0, 18.12.0, or 18.12.1 causes BSOD AC-7265 Windows 7 x64

JSost · ‎09-22-2015

Updating Intel Pro Wireless from version 17.16.1 to 18.12.0 causes a BSOD during the middle of the software/driver update and causes a system reboot. When the computer reboots, it gets another BSOD of when the driver is loaded. The only way to Boot the machine, is to boot into safe mode or go into the BIOS and disable the Wireless adapter. I had no problem with the series 17 Pro Wireless Software/Driver versions 17.13.11, 17.14.00, and 17.16.1. The problem only started appearing with the Series 18 Software/Drivers.

If I download the driver only from the Intel Download Center and install it, I still get the BSOD.

System Specs:

Operating System Windows 7, x64, SP1 with all updates.

Computer Lenovo X1 Carbon gen 3, wireless adapter AC-7265 (wireless and bluetooth adapter)

Contains an Intel Ethernet Connector I218-LM

Current Pro Wireless Adapter software installed is 17.16.1.2 (from Lenovo Website)

Current Bluetooth driver installed 17.1.1501.512 (from Lenovo Website)

Intel I218-LM Driver version 12.12.80.1955 (from Lenovo Website)

Crash Dump file contents with 18.12.0 Pro Wireless Driver:

Microsoft (R) Windows Debugger Version 6.3.9600.17336 AMD64

Loading Dump File [G:\Mini Dump x1 Gen 3\Crash Dump 18.12.0 From Lenovo\092215-8892-01.dmp]

Mini Kernel Dump File: Only registers and stack trace are available

************* Symbol Path validation summary **************

Response Time (ms) Location

Deferred SRV*c:\symbols*http://msdl.microsoft.com/download/symbols http://msdl.microsoft.com/download/symbols

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols http://msdl.microsoft.com/download/symbols

Executable search path is:

Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 7601.18933.amd64fre.win7sp1_gdr.150715-0600

Machine Name:

Kernel base = 0xfffff800`0301f000 PsLoadedModuleList = 0xfffff800`03266730

Debug session time: Tue Sep 22 00:29:15.559 2015 (UTC - 5:00)

System Uptime: 0 days 0:00:02.761

Loading Kernel Symbols

...............................................................

................................................................

.

Loading User Symbols

*** WARNING: Unable to verify timestamp for Netwsw02.sys

*** ERROR: Module load completed but symbols could not be loaded for Netwsw02.sys

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff88005413f02, fffff880037e6688, fffff880037e5ee0}

Probably caused by : Netwsw02.sys ( Netwsw02+ff02 )

Followup: MachineOwner

---------

3: kd> !analyze -v

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)

This is a very common bugcheck. Usually the exception address pinpoints

the driver/function that caused the problem. Always note this address

as well as the link date of the driver/image that contains this address.

Some common problems are exception code 0x80000003. This means a hard

coded breakpoint or assertion was hit, but this system was booted

/NODEBUG. This is not supposed to happen as developers should never have

hardcoded breakpoints in retail code, but ...

If this happens, make sure a debugger gets connected, and the

system is booted /DEBUG. This will let us see why this breakpoint is

happening.

Arguments:

Arg1: ffffffffc0000005, The exception code that was not handled

Arg2: fffff88005413f02, The address that the exception occurred at

Arg3: fffff880037e6688, Exception Record Address

Arg4: fffff880037e5ee0, Context Record Address

Debugging Details:

------------------

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP:

Netwsw02+ff02

fffff880`05413f02 488b10 mov rdx,qword ptr [rax]

EXCEPTION_RECORD: fffff880037e6688 -- (.exr 0xfffff880037e6688)

ExceptionAddress: fffff88005413f02 (Netwsw02+0x000000000000ff02)

ExceptionCode: c0000005 (Access violation)

ExceptionFlags: 00000000

NumberParameters: 2

Parameter[0]: 0000000000000000

Parameter[1]: 0000000000000000

Attempt to read from address 0000000000000000

CONTEXT: fffff880037e5ee0 -- (.cxr 0xfffff880037e5ee0;r)

rax=0000000000000000 rbx=fffffa80084f3470 rcx=0000000000000000

rdx=0000000000000000 rsi=fffff880037e6980 rdi=0000000000000018

rip=fffff88005413f02 rsp=fffff880037e68c0 rbp=fffff880037e69f9

r8=fffff880037e68d0 r9=0000000000000001 r10=0000000000000004

r11=fffff880037e6660 r12=0000000000000000 r13=fffff88005752eb0

r14=fffffa8008207470 r15=00000000ffffffff

iopl=0 nv up ei ng nz na po nc

cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286

Netwsw02+0xff02:

fffff880`05413f02 488b10 mov rdx,qword ptr [rax] ds:002b:00000000`00000000=????????????????

Last set context:

rax=0000000000000000 rbx=fffffa80084f3470 rcx=0000000000000000

rdx=0000000000000000 rsi=fffff880037e6980 rdi=0000000000000018

rip=fffff88005413f02 rsp=fffff880037e68c0 rbp=fffff880037e69f9

r8=fffff880037e68d0 r9=0000000000000001 r10=0000000000000004

r11=fffff880037e6660 r12=0000000000000000 r13=fffff88005752eb0

r14=fffffa8008207470 r15=00000000ffffffff

iopl=0 nv up ei ng nz na po nc

cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286

Netwsw02+0xff02:

fffff880`05413f02 488b10 mov rdx,qword ptr [rax] ds:002b:00000000`00000000=????????????????

Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: NULL_DEREFERENCE

PROCESS_NAME: System

CURRENT_IRQL: 0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 0000000000000000

READ_ADDRESS: GetPointe...

ASouz7 · ‎09-23-2015

Jstar333,

We understand your frustration. If the Wireless Adapter came installed by factory, Intel recommends that use the drivers provided by Lenovo*. The drivers found in our download center are generic and even though they are newer, they may not be compatible with your system.

JSost · ‎09-23-2015

Drivers Versions 18.11.0 and 18.12.0 were provided by Lenovo. The Crash Dump file was driver 18.12.0 provided by Lenovo. The only Driver I got from Intel Download Center was 18.12.1. All three drivers resulted in a BSOD,

ASouz7 · ‎09-24-2015

Jstar333,

Is this wireless card the original one that came installed by factory? if that is so, our first recommendation is for you to contact your computer manufacturer and see if they have any customized updates. if they do, perform a clean uninstall first, and then reeinstall the drivers back from the OEM. If by any chance the original card was replaced, it is important that you know that Intel does support integration and consulting with the computer manufacturer is important for possible solutions. Check this link for further information on this matter http://www.intel.com/support/wireless/wlan/sb/cs-011644.htm Intel® Wi-Fi Products — Regulatory Information Regarding Hardware Installation or Upgrade

JSost · ‎09-24-2015

The wireless card was installed by the manufacture (Lenovo).

I finally got the Series 18 Driver to load !

Lenovo had the newest driver 18.20.0 on their Website. I tried installing it and got the same BSOD, with the same parameters.

To get it to load, this is what I did.

step 1: Uninstall The Intel Proset/Wireless Software. In Windows 7 Control Panel, Programs and Features uninstall The Intel Proset/Wireless Software. I selected the option to Save Current Settings. Reboot computer.

step 2: Uninstall Ac-7265 Device and Drivers. In Windows 7 Device Manager go to Network adapters, select Intel Dual Band Wireless-AC 7265. Click to uninstall device and check the box to "Delete the driver software for this device". Reboot the computer and make sure the network device is listed as an unknown device in the Device Manager. If it is not listed as an Unknown Device, keep uninstalling until it is.

step 3: Install new Intel Proset/Wireless Software and Driver (18.20.00).

Step 2 was the one that allowed the new driver to install. Step1 was added as an extra precaution. I image my hard drive so I can reload the operating system sector as many times as needed until I find a solution.

ASouz7 · ‎09-24-2015

Jstar333,

We are glad to know it is working and thanks for sharing your solution. Should you need more assistance to us. Please let us know. If you prefer, you also have available other ways to contact us.

Use this link: http://www.intel.com/p/en_US/support/contactsupport Contact Support