5 Replies Latest reply on Sep 24, 2015 1:04 PM by aleki_intel

    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

    Jstar333

      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

      Copyright (c) Microsoft Corporation. All rights reserved.

       

       

      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

      Symbol search path is: SRV*c:\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

      1. 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: GetPointerFromAddress: unable to read from fffff800032d0100

      GetUlongFromAddress: unable to read from fffff800032d01c0

      0000000000000000 Nonpaged pool

       

      FOLLOWUP_IP:

      Netwsw02+ff02

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

       

      BUGCHECK_STR:  0x7E

       

      ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

       

      LAST_CONTROL_TRANSFER: from fffffa80084f3470 to fffff88005413f02

       

      STACK_TEXT:

      fffff880`037e68c0 fffffa80`084f3470 : fffff880`037e6980 fffffa80`085af118 fffffa80`08207470 fffff880`0566cf20 : Netwsw02+0xff02

      fffff880`037e68c8 fffff880`037e6980 : fffffa80`085af118 fffffa80`08207470 fffff880`0566cf20 fffff880`05409ef3 : 0xfffffa80`084f3470

      fffff880`037e68d0 fffffa80`085af118 : fffffa80`08207470 fffff880`0566cf20 fffff880`05409ef3 fffff880`037e6960 : 0xfffff880`037e6980

      fffff880`037e68d8 fffffa80`08207470 : fffff880`0566cf20 fffff880`05409ef3 fffff880`037e6960 fffff880`037e69f9 : 0xfffffa80`085af118

      fffff880`037e68e0 fffff880`0566cf20 : fffff880`05409ef3 fffff880`037e6960 fffff880`037e69f9 00000000`00000024 : 0xfffffa80`08207470

      fffff880`037e68e8 fffff880`05409ef3 : fffff880`037e6960 fffff880`037e69f9 00000000`00000024 00000000`00000001 : Netwsw02+0x268f20

      fffff880`037e68f0 fffff880`037e6960 : fffff880`037e69f9 00000000`00000024 00000000`00000001 fffff880`0566cf20 : Netwsw02+0x5ef3

      fffff880`037e68f8 fffff880`037e69f9 : 00000000`00000024 00000000`00000001 fffff880`0566cf20 fffff880`0574b678 : 0xfffff880`037e6960

      fffff880`037e6900 00000000`00000024 : 00000000`00000001 fffff880`0566cf20 fffff880`0574b678 fffff880`037e69f9 : 0xfffff880`037e69f9

      fffff880`037e6908 00000000`00000001 : fffff880`0566cf20 fffff880`0574b678 fffff880`037e69f9 00000000`00000000 : 0x24

      fffff880`037e6910 fffff880`0566cf20 : fffff880`0574b678 fffff880`037e69f9 00000000`00000000 00000000`00000024 : 0x1

      fffff880`037e6918 fffff880`0574b678 : fffff880`037e69f9 00000000`00000000 00000000`00000024 fffff880`054b6d6d : Netwsw02+0x268f20

      fffff880`037e6920 fffff880`037e69f9 : 00000000`00000000 00000000`00000024 fffff880`054b6d6d 00000000`00000000 : Netwsw02+0x347678

      fffff880`037e6928 00000000`00000000 : 00000000`00000024 fffff880`054b6d6d 00000000`00000000 fffffa80`00000000 : 0xfffff880`037e69f9

       

       

      SYMBOL_STACK_INDEX: 0

       

      SYMBOL_NAME: Netwsw02+ff02

       

      FOLLOWUP_NAME: MachineOwner

       

      MODULE_NAME: Netwsw02

       

      IMAGE_NAME: Netwsw02.sys

       

      DEBUG_FLR_IMAGE_TIMESTAMP:  55a76cdd

       

      STACK_COMMAND: .cxr 0xfffff880037e5ee0 ; kb

       

      FAILURE_BUCKET_ID: X64_0x7E_Netwsw02+ff02

       

      BUCKET_ID: X64_0x7E_Netwsw02+ff02

       

      ANALYSIS_SOURCE: KM

       

      FAILURE_ID_HASH_STRING: km:x64_0x7e_netwsw02+ff02

       

      FAILURE_ID_HASH: {b359ce94-8093-8605-d339-5f2baade5df9}

       

      Followup: MachineOwner