4 Replies Latest reply on Sep 12, 2018 2:05 PM by Intel Corporation

    BSOD with netwtw06.sys when switching AP


      We have 25 Lenovo T480s computers that have been BSOD for the last couple months. Recently we used Driver Verifier and were able to consistently replicate the BSOD when the netwtw06.sys was selected using Driver Verifier. We've been able to trigger the BSOD by walking with the laptop which I think the change in access point is causing the blue screen. We've updated the driver versions from 20.50 to 20.60 and the issue still occurs. We've tested with slightly older models that have earlier driver versions and the issue does not occur. Any ideas or thoughts would be helpful!

        • 1. Re: BSOD with netwtw06.sys when switching AP
          Al Hill

          What specific T480 do you have (provide specifics)?

          What operating system are you running?

          What is the processor model number?

          Are you using the driver from the Lenovo site?

          From where are you getting your drivers?


          Provide the information and someone will be able to help you.


          P.S.  Personally, I would never use a tool like driver verifier.



          • 2. Re: BSOD with netwtw06.sys when switching AP

            Below is one of our dump files.

            -T480s Type 20L7-002EUS

            -Windows 10 Enterprise 1803

            -Processor is i5-8350U

            We were originally using the drivers from Lenovo, but saw that Intel had newer ones so we tried that as well.




            1: kd> !analyze -v


            *                                                                             *

            *                        Bugcheck Analysis                                    *

            *                                                                             *



            An exception happened while executing a system service routine.


            Arg1: 00000000c0000005, Exception code that caused the bugcheck

            Arg2: fffff802e59366a1, Address of the instruction which caused the bugcheck

            Arg3: ffffc208f86c6b00, Address of the context record for the exception that caused the bugcheck

            Arg4: 0000000000000000, zero.

            Debugging Details:


            KEY_VALUES_STRING: 1

            TIMELINE_ANALYSIS: 1

            DUMP_CLASS: 1

            DUMP_QUALIFIER: 400

            BUILD_VERSION_STRING:  16299.431.amd64fre.rs3_release_svc_escrow.180502-1908


            SYSTEM_PRODUCT_NAME:  20HF0011US

            SYSTEM_SKU:  LENOVO_MT_20HF_BU_Think_FM_ThinkPad T470s

            SYSTEM_VERSION:  ThinkPad T470s

            BIOS_VENDOR:  LENOVO

            BIOS_VERSION:  N1WET35W (1.14 )

            BIOS_DATE:  07/12/2017


            BASEBOARD_PRODUCT:  20HF0011US

            BASEBOARD_VERSION:  SDK0J40697 WIN

            DUMP_TYPE:  2

            BUGCHECK_P1: c0000005

            BUGCHECK_P2: fffff802e59366a1

            BUGCHECK_P3: ffffc208f86c6b00

            BUGCHECK_P4: 0

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



            fffff802`e59366a1 f00fc18600020000 lock xadd dword ptr [rsi+200h],eax

            CONTEXT:  ffffc208f86c6b00 -- (.cxr 0xffffc208f86c6b00)

            rax=00000000ffffffff rbx=ffff8009bfb9b6c0 rcx=0000000000000011

            rdx=ffff8009bfb9b670 rsi=4f15c47fb48419ae rdi=00000000000000b6

            rip=fffff802e59366a1 rsp=ffffc208f86c74f0 rbp=ffff8009b252b4a0

            r8=0000000000000001  r9=0000000000000000 r10=0000000000000000

            r11=0000000000000000 r12=0000000000000000 r13=0000000000000000

            r14=ffff8009bfb9b670 r15=0000000000000000

            iopl=0         nv up ei ng nz na po nc

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


            fffff802`e59366a1 f00fc18600020000 lock xadd dword ptr [rsi+200h],eax ds:002b:4f15c47f`b4841bae=????????

            Resetting default scope

            CPU_COUNT: 4

            CPU_MHZ: a98

            CPU_VENDOR:  GenuineIntel

            CPU_FAMILY: 6

            CPU_MODEL: 8e

            CPU_STEPPING: 9

            CPU_MICROCODE: 6,8e,9,0 (F,M,S,R)  SIG: 62'00000000 (cache) 62'00000000 (init)

            BLACKBOXBSD: 1 (!blackboxbsd)

            BLACKBOXPNP: 1 (!blackboxpnp)

            CUSTOMER_CRASH_COUNT:  1


            BUGCHECK_STR:  0x3B

            PROCESS_NAME:  SearchFilterHost.exe

            CURRENT_IRQL:  0


            ANALYSIS_SESSION_TIME:  06-19-2018 09:19:22.0390

            ANALYSIS_VERSION: 10.0.17134.12 amd64fre

            LAST_CONTROL_TRANSFER:  from fffff802e5936516 to fffff802e59366a1


            ffffc208`f86c74f0 fffff802`e5936516 : 00000000`00000000 ffff8009`bfb9b6a0 ffff8009`bfb9b670 00000000`00000000 : nt!ObpFreeObject+0x131

            ffffc208`f86c7550 fffff802`e552f6c6 : 00000000`00000000 00000000`00000000 00000000`00000000 ffff8009`bfb9b6f0 : nt!ObpRemoveObjectRoutine+0x86

            ffffc208`f86c75b0 fffff802`e595a3cb : 00000000`ffff8004 ffff8009`b252b4a0 ffff8009`00000001 ffff8009`bfb9b6c0 : nt!ObfDereferenceObjectWithTag+0xc6

            ffffc208`f86c75f0 fffff802`e59f9145 : 00000000`00000000 fffff802`e552e7b4 ffff8009`bd7f7700 ffff8009`bd8a5098 : nt!ObCloseHandleTableEntry+0x25b

            ffffc208`f86c7730 fffff802`e59e04a9 : ffff8009`bd8a5060 00000000`00000000 ffff8009`bbca7080 ffffffff`ffffff01 : nt!ExSweepHandleTable+0xc5

            ffffc208`f86c77e0 fffff802`e599053d : ffffffff`ffffffff ffff8009`bbca7080 ffff8009`bbca7080 ffff8009`00000000 : nt!ObKillProcess+0x35

            ffffc208`f86c7810 fffff802`e5914f03 : ffff8009`bbca7080 ffff950f`69e1b900 ffffc208`f86c7a80 00000000`00000000 : nt!PspRundownSingleProcess+0x121

            ffffc208`f86c7890 fffff802`e59dc6cf : 00000000`00000000 ffffc208`f86c7a01 00000002`8d23b000 ffff8009`bd7f7700 : nt!PspExitThread+0x583

            ffffc208`f86c7990 fffff802`e5625363 : 00000000`0000376c ffff8009`bd7f7700 ffff8009`bbca7080 00000106`f33e0730 : nt!NtTerminateProcess+0xeb

            ffffc208`f86c7a00 00000000`595b9e3d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13

            00000002`8d13f7a8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x595b9e3d

            THREAD_SHA1_HASH_MOD_FUNC:  5f041c223d6d56e5b50919d5e6ce29f4ce085e7c

            THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  92fbc344c2d38d0722203ebf00779feb4669ef7a

            THREAD_SHA1_HASH_MOD:  bc100a5647b828107ac4e18055e00abcbe1ec406



            fffff802`e59366a1 f00fc18600020000 lock xadd dword ptr [rsi+200h],eax

            FAULT_INSTR_CODE:  86c10ff0

            SYMBOL_STACK_INDEX:  0

            SYMBOL_NAME:  nt!ObpFreeObject+131

            FOLLOWUP_NAME:  MachineOwner

            MODULE_NAME: nt

            IMAGE_NAME:  ntkrnlmp.exe

            DEBUG_FLR_IMAGE_TIMESTAMP:  5aeaa6a2

            IMAGE_VERSION:  10.0.16299.431

            STACK_COMMAND:  .cxr 0xffffc208f86c6b00 ; kb

            BUCKET_ID_FUNC_OFFSET:  131

            FAILURE_BUCKET_ID:  0x3B_nt!ObpFreeObject

            BUCKET_ID:  0x3B_nt!ObpFreeObject

            PRIMARY_PROBLEM_CLASS:  0x3B_nt!ObpFreeObject

            TARGET_TIME:  2018-06-15T15:16:54.000Z

            OSBUILD:  16299

            OSSERVICEPACK:  431


            OS_REVISION: 0

            SUITE_MASK:  272

            PRODUCT_TYPE:  1

            OSPLATFORM_TYPE:  x64

            OSNAME:  Windows 10

            OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS


            USER_LCID:  0

            OSBUILD_TIMESTAMP:  2018-05-03 02:05:22

            BUILDDATESTAMP_STR:  180502-1908

            BUILDLAB_STR:  rs3_release_svc_escrow

            BUILDOSVER_STR:  10.0.16299.431.amd64fre.rs3_release_svc_escrow.180502-1908


            ANALYSIS_SOURCE:  KM

            FAILURE_ID_HASH_STRING:  km:0x3b_nt!obpfreeobject

            FAILURE_ID_HASH:  {c6c66008-ecfb-6f68-152f-8955ff35bc66}

            Followup:     MachineOwner

            • 3. Re: BSOD with netwtw06.sys when switching AP
              Intel Corporation
              This message was posted on behalf of Intel Corporation

               Hello ajones12345,
              Thank you for joining the Intel Communities.
              There is newer version of the wireless adapter which is version and I would like you to give it a try.  You may download it from this link https://downloadcenter.intel.com/download/27989/Intel-PROSet-Wireless-Software-and-Drivers-for-Windows-10?product=94150
              Please try doing a clean installation of the wireless driver.  This link will give you the steps https://www.intel.com/content/www/us/en/support/articles/000022173/network-and-i-o/wireless-networking.html
              If issue persists try changing Wi-Fi Roaming Aggressiveness Setting.  This link will show you how https://www.intel.com/content/www/us/en/support/articles/000005546/network-and-i-o/wireless-networking.html
              Let me know if issue persists or not.
              Fred D.

              • 4. Re: BSOD with netwtw06.sys when switching AP
                Intel Corporation
                This message was posted on behalf of Intel Corporation

                Hello ajones12345,
                I was wondering if you still need assistance regarding the blue screen of death you are having in the computer.  In case you still need assistance just let me know.
                Fred D.