1 2 Previous Next 26 Replies Latest reply on Feb 27, 2018 12:50 PM by Intel Corporation

    Intel Dual Band Wireless 8265 causing BSOD in Win10

    Azhur

      Hi, I have an 8265 wifi adapter.  I experience BSOD's randomly on system boot up, maybe every 2- 3 or so.   I see this same topic in earlier posts where someone had the same issue then stated it was resolved,

       

      Here is the debug of mini dump file.  It is flagging the Netwtw06.sys file as the probable cause.

       

       

      Microsoft (R) Windows Debugger Version 10.0.16299.91 AMD64

      Copyright (c) Microsoft Corporation. All rights reserved.

       

       

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

       

      Symbol search path is: srv*

      Executable search path is:

      Windows 10 Kernel Version 16299 MP (8 procs) Free x64

      Product: WinNt, suite: TerminalServer SingleUserTS Personal

      Built by: 16299.15.amd64fre.rs3_release.170928-1534

      Machine Name:

      Kernel base = 0xfffff801`d2c9c000 PsLoadedModuleList = 0xfffff801`d3002fd0

      Debug session time: Sun Jan  7 16:10:30.213 2018 (UTC + 3:00)

      System Uptime: 0 days 4:36:23.158

      Loading Kernel Symbols

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

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

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

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

      Loading User Symbols

      Loading unloaded module list

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

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

      * *

      *                        Bugcheck Analysis                                    *

      * *

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

       

      Use !analyze -v to get detailed debugging information.

       

      BugCheck 50, {ffff960631a00000, 2, fffff801d2e2566f, 2}

       

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

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

       

      Could not read faulting driver name

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

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

      Probably caused by : Netwtw06.sys ( Netwtw06+531eb9 )

       

      Followup:     MachineOwner

      ---------

       

      4: kd> !analyze -v

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

      * *

      *                        Bugcheck Analysis                                    *

      * *

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

       

      PAGE_FAULT_IN_NONPAGED_AREA (50)

      Invalid system memory was referenced.  This cannot be protected by try-except.

      Typically the address is just plain bad or it is pointing at freed memory.

      Arguments:

      Arg1: ffff960631a00000, memory referenced.

      Arg2: 0000000000000002, value 0 = read operation, 1 = write operation.

      Arg3: fffff801d2e2566f, If non-zero, the instruction address which referenced the bad memory

                     address.

      Arg4: 0000000000000002, (reserved)

       

      Debugging Details:

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

       

       

      Could not read faulting driver name

       

      DUMP_CLASS: 1

       

      DUMP_QUALIFIER: 400

       

      BUILD_VERSION_STRING:  10.0.16299.192 (WinBuild.160101.0800)

       

      SYSTEM_MANUFACTURER:  Timi

       

      SYSTEM_PRODUCT_NAME:  TM1701

       

      BIOS_VENDOR:  INSYDE Corp.

       

      BIOS_VERSION:  XMAKB5R0P0200

       

      BIOS_DATE:  09/07/2017

       

      BASEBOARD_MANUFACTURER:  Timi

       

      BASEBOARD_PRODUCT:  TM1701

       

      BASEBOARD_VERSION:  MP

       

      DUMP_TYPE:  2

       

      BUGCHECK_P1: ffff960631a00000

       

      BUGCHECK_P2: 2

       

      BUGCHECK_P3: fffff801d2e2566f

       

      BUGCHECK_P4: 2

       

      READ_ADDRESS: fffff801d3098380: Unable to get MiVisibleState

      Unable to get NonPagedPoolStart

      Unable to get NonPagedPoolEnd

      Unable to get PagedPoolStart

      Unable to get PagedPoolEnd

      ffff960631a00000

       

      FAULTING_IP:

      nt!memcpy+af

      fffff801`d2e2566f 660f7f41e0      movdqa  xmmword ptr [rcx-20h],xmm0

       

      MM_INTERNAL_CODE:  2

       

      CPU_COUNT: 8

       

      CPU_MHZ: 708

       

      CPU_VENDOR:  GenuineIntel

       

      CPU_FAMILY: 6

       

      CPU_MODEL: 8e

       

      CPU_STEPPING: a

       

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

       

      CUSTOMER_CRASH_COUNT:  1

       

      DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

       

      BUGCHECK_STR:  AV

       

      PROCESS_NAME:  System

       

      CURRENT_IRQL:  0

       

      ANALYSIS_SESSION_HOST:  DESKTOP-9J1D3C6

       

      ANALYSIS_SESSION_TIME:  01-07-2018 16:36:07.0613

       

      ANALYSIS_VERSION: 10.0.16299.91 amd64fre

       

      TRAP_FRAME:  ffffb008f7dced90 -- (.trap 0xffffb008f7dced90)

      NOTE: The trap frame does not contain all registers.

      Some register values may be zeroed or incorrect.

      rax=0000000000040000 rbx=0000000000000000 rcx=ffff960631a00020

      rdx=00001dfb99dc0000 rsi=0000000000000000 rdi=0000000000000000

      rip=fffff801d2e2566f rsp=ffffb008f7dcef28 rbp=0000000000000000

      r8=0000000000000000  r9=0000000000000800 r10=00000000ffffffff

      r11=ffff960631a00000 r12=0000000000000000 r13=0000000000000000

      r14=0000000000000000 r15=0000000000000000

      iopl=0         nv up ei ng nz na pe nc

      nt!memcpy+0xaf:

      fffff801`d2e2566f 660f7f41e0      movdqa  xmmword ptr [rcx-20h],xmm0 ds:ffff9606`31a00000=????????????????????????????????

      Resetting default scope

       

      LAST_CONTROL_TRANSFER:  from fffff801d2e3b71d to fffff801d2e116e0

       

      STACK_TEXT: 

      ffffb008`f7dceb18 fffff801`d2e3b71d : 00000000`00000050 ffff9606`31a00000 00000000`00000002 ffffb008`f7dced90 : nt!KeBugCheckEx

      ffffb008`f7dceb20 fffff801`d2cebbbd : 00000000`00000002 ffff9606`31a00000 ffffb008`f7dced90 ffffb008`f7dcecc0 : nt!MiSystemFault+0x15151d

      ffffb008`f7dcebc0 fffff801`d2e2074e : 00000000`00000000 ffffac80`03f95850 00000000`00000000 00000000`00000000 : nt!MmAccessFault+0x23d

      ffffb008`f7dced90 fffff801`d2e2566f : fffff801`d313a48a 00000000`00000000 ffff9606`2a230830 ffff9606`31a00000 : nt!KiPageFault+0x40e

      ffffb008`f7dcef28 fffff801`d313a48a : 00000000`00000000 ffff9606`2a230830 ffff9606`31a00000 ffff9606`2c6e34e0 : nt!memcpy+0xaf

      ffffb008`f7dcef30 fffff801`d313a214 : 00000000`00040000 00000000`00040000 00000000`00c89848 ffffb008`f7dcf030 : nt!CcCopyBytesToUserBuffer+0x4a

      ffffb008`f7dcef80 fffff801`d2cd2cbc : ffff9606`275c8260 00000000`00000000 00000000`00040000 ffff9606`29e58701 : nt!CcMapAndCopyFromCache+0x114

      ffffb008`f7dcf020 fffff80c`3ceb25ee : ffff8502`00000000 ffff8502`00000000 ffff9606`00c89848 ffff8502`00000000 : nt!CcCopyReadEx+0x12c

      ffffb008`f7dcf0b0 fffff80c`3ceb4dff : 00000000`00c89848 ffffb008`f7dcf350 ffff8502`d4653bf0 ffff8502`d4653c48 : NTFS!NtfsCachedRead+0x182

      ffffb008`f7dcf120 fffff80c`3ceb29b8 : ffff9606`303f0558 ffff9606`2b6a3010 00000000`00000064 ffff8502`d4653bf0 : NTFS!NtfsCommonRead+0x224f

      ffffb008`f7dcf320 fffff801`d2cb62d9 : ffff9606`304b4c00 ffff9606`2b6a3010 00000000`00000000 ffff9606`2b6a3440 : NTFS!NtfsFsdRead+0x1d8

      ffffb008`f7dcf3e0 fffff80c`3ba08773 : ffff9606`2b6a3010 ffffb008`f7dcf4c0 ffffb008`f7dcf4d9 00000000`00000000 : nt!IofCallDriver+0x59

      ffffb008`f7dcf420 fffff80c`3ba06db6 : ffffb008`f7dcf4b0 ffffc562`b15b5f10 ffff9606`28349b01 fffff801`d2d5c0c5 : FLTMGR!FltpLegacyProcessingAfterPreCallbacksCompleted+0x1a3

      ffffb008`f7dcf490 fffff801`d2cb62d9 : ffff9606`2b6a3010 fffff801`d3136440 ffffaf80`00009040 00000000`00103100 : FLTMGR!FltpDispatch+0xb6

      ffffb008`f7dcf4f0 fffff801`d3115efe : 00000000`00000000 ffff9606`2c6e34e0 ffff9606`2b6a3488 fffff801`d30b3200 : nt!IofCallDriver+0x59

      ffffb008`f7dcf530 fffff801`d31168fa : 00000000`00000000 00000000`00000000 00000000`00000000 ffffb008`f7dcf7c0 : nt!IopSynchronousServiceTail+0x19e

      ffffb008`f7dcf5e0 fffff801`d2e24203 : 00000000`00000300 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtReadFile+0x68a

      ffffb008`f7dcf6d0 fffff801`d2e15100 : fffff80c`3ef71eb9 fffff80c`3ee242c8 fffff80c`3ee24270 fffff80c`3ee24330 : nt!KiSystemServiceCopyEnd+0x13

      ffffb008`f7dcf8d8 fffff80c`3ef71eb9 : fffff80c`3ee242c8 fffff80c`3ee24270 fffff80c`3ee24330 fffff80c`3ee24300 : nt!KiServiceLinkage

      ffffb008`f7dcf8e0 fffff80c`3ee242c8 : fffff80c`3ee24270 fffff80c`3ee24330 fffff80c`3ee24300 ffffb008`f7dcf930 : Netwtw06+0x531eb9

      ffffb008`f7dcf8e8 fffff80c`3ee24270 : fffff80c`3ee24330 fffff80c`3ee24300 ffffb008`f7dcf930 ffff9606`31a00000 : Netwtw06+0x3e42c8

      ffffb008`f7dcf8f0 fffff80c`3ee24330 : fffff80c`3ee24300 ffffb008`f7dcf930 ffff9606`31a00000 fffff801`00c89848 : Netwtw06+0x3e4270

      ffffb008`f7dcf8f8 fffff80c`3ee24300 : ffffb008`f7dcf930 ffff9606`31a00000 fffff801`00c89848 00000000`00000000 : Netwtw06+0x3e4330

      ffffb008`f7dcf900 ffffb008`f7dcf930 : ffff9606`31a00000 fffff801`00c89848 00000000`00000000 00000000`00000000 : Netwtw06+0x3e4300

      ffffb008`f7dcf908 ffff9606`31a00000 : fffff801`00c89848 00000000`00000000 00000000`00000000 00000000`00000240 : 0xffffb008`f7dcf930

      ffffb008`f7dcf910 fffff801`00c89848 : 00000000`00000000 00000000`00000000 00000000`00000240 00000000`00000000 : 0xffff9606`31a00000

      ffffb008`f7dcf918 00000000`00000000 : 00000000`00000000 00000000`00000240 00000000`00000000 00000000`00000018 : 0xfffff801`00c89848

       

       

      THREAD_SHA1_HASH_MOD_FUNC:  3d6cde47e773f16403bbc07451cb0ace9284a31c

       

      THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  ed0efe6e78434f104d261aa9ca0339c46a8eb59f

       

      THREAD_SHA1_HASH_MOD:  a748b77ec3bc3a3a63336300a46c45387f2d3225

       

      FOLLOWUP_IP:

      Netwtw06+531eb9

      fffff80c`3ef71eb9 33d2            xor     edx,edx

       

      FAULT_INSTR_CODE:  4489d233

       

      SYMBOL_STACK_INDEX:  13

       

      SYMBOL_NAME:  Netwtw06+531eb9

       

      FOLLOWUP_NAME:  MachineOwner

       

      MODULE_NAME: Netwtw06

       

      IMAGE_NAME:  Netwtw06.sys

       

      DEBUG_FLR_IMAGE_TIMESTAMP:  59fb46b2

       

      STACK_COMMAND:  .thread ; .cxr ; kb

       

      BUCKET_ID_FUNC_OFFSET:  531eb9

       

      FAILURE_BUCKET_ID:  AV_INVALID_Netwtw06!unknown_function

       

      BUCKET_ID:  AV_INVALID_Netwtw06!unknown_function

       

      PRIMARY_PROBLEM_CLASS:  AV_INVALID_Netwtw06!unknown_function

       

      TARGET_TIME:  2018-01-07T13:10:30.000Z

       

      OSBUILD:  16299

       

      OSSERVICEPACK:  192

       

      SERVICEPACK_NUMBER: 0

       

      OS_REVISION: 0

       

      SUITE_MASK:  784

       

      PRODUCT_TYPE:  1

       

      OSPLATFORM_TYPE:  x64

       

      OSNAME:  Windows 10

       

      OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS Personal

       

      OS_LOCALE: 

       

      USER_LCID:  0

       

      OSBUILD_TIMESTAMP:  2018-01-01 14:07:05

       

      BUILDDATESTAMP_STR:  160101.0800

       

      BUILDLAB_STR:  WinBuild

       

      BUILDOSVER_STR:  10.0.16299.192

       

      ANALYSIS_SESSION_ELAPSED_TIME:  2037

       

      ANALYSIS_SOURCE:  KM

       

      FAILURE_ID_HASH_STRING:  km:av_invalid_netwtw06!unknown_function

       

      FAILURE_ID_HASH:  {2101a6f1-56d4-96a1-954f-0b4ab4996965}

       

      Followup: MachineOwner

      ---------

        • 1. Re: Intel Dual Band Wireless 8265 causing BSOD in Win10
          Azhur

          SSU report attached

          • 2. Re: Intel Dual Band Wireless 8265 causing BSOD in Win10
            Intel Corporation
            This message was posted on behalf of Intel Corporation

            Hello Azhur,

             

            We understand that you're experiencing random blue screen crashes on Windows 10*.

             

            In the post you mentioned, the customer last action was a clean driver installation. Please try the following:

             

            1. Download and save your driver of choice. You can:
              1. Get the latest system-specific driver from your computer manufacturer support (I tried to search the support site for your Xiaomi TIMI TM1701*, but wasn't able to find one).
              2. Download the Latest Driver for Your Intel® Wireless Adapter.
            2. Uninstall the Intel® PROSet/Wireless Software.
              1. Open Programs and Features (Uninstall a program) from the Control Panel.
              2. Select Uninstall or Change and then Remove.
              3. When prompted, choose to discard settings.
            3. Uninstall your wireless driver. Windows* with an inbox driver may natively support some wireless adapters. You cannot uninstall an inbox driver. Proceed to the next step if you start seeing the same version of the driver installed automatically after it’s uninstalled.
              1. Go to Device Manager.
              2. Expand the Network Adapters category.
              3. Right-click your Intel Wireless Adapter and choose to uninstall it.
              4. Make sure to select the option to Delete the driver software for this device.
            4. Clear out your temporary files.
              1. Press the Windows* key and R key simultaneously to open the run box.
              2. Type in: cleanmgr.exe and press the Enter key or OK.
              3. Place a check mark next to Temporary Files. You can leave everything else checked or unchecked.
              4. Press OK and wait.
            5. Reboot your computer.
            6. Locate the driver you downloaded back in Step 1. Run as administrator and follow the wizard to completion.
            7. (Optional Step) Apply the Recommended Settings for Wireless Connectivity.


            Do you remember if the issue started after a driver or Windows* update?

             

            Best regards,
            Eugenio F.

            • 3. Re: Intel Dual Band Wireless 8265 causing BSOD in Win10
              Azhur

              Hi Eugenio,

              I already try your instruction, it was mentioned in similar post about 8260.

              it is doesn't help me.

              I bought this PC in december, and it is work fine.

              but then, after few windows and drivers updates  -  I have BSOD. now it is almost each time when I switch on my PC.

               

              initial WIFI drivers for Dual Band Wireless 8265 delivered with PC -  was 19.71.0

               

              • 4. Re: Intel Dual Band Wireless 8265 causing BSOD in Win10
                Intel Corporation
                This message was posted on behalf of Intel Corporation

                Hello Azhur,

                What is the exact stop error message that displays on your BSOD crashes?

                Could you uninstall our generic drivers and try using the system specific drivers provided by your computer manufacturer? After some digging, I was able to find the drivers page for your laptop:

                NOTE: Any links provided for third party tools or sites are offered for your convenience and should not be viewed as an endorsement by Intel® of the content, products, or services offered there.

                - Driver Collections for Mi Notebook Air* 12.5" and 13.3"

                You may also want to engage your computer manufacturer:

                - XIAOMI MI* Support

                Please let us know if these make a difference.

                Best regards,
                Carlos A.

                • 5. Re: Intel Dual Band Wireless 8265 causing BSOD in Win10
                  nkaufman

                  Try reverting the drivers back to an older version and check if that works, might have to go a version or 2 or more back.

                   

                  Newer Intel drivers do NOT seem to be fixing issues in some cases, but that is the new Intel, frustrating and disappointing... whether it be graphics drivers or networking drivers. Both of these drivers have been horrendous,

                   

                  Have not looked at other drivers - chipset, storage etc. - who knows what else broken stuff is being released by Intel.

                   

                  Have the standards fallen this low?

                  • 6. Re: Intel Dual Band Wireless 8265 causing BSOD in Win10
                    Intel Corporation
                    This message was posted on behalf of Intel Corporation

                    Hello nkaufman,

                    The drivers posted through our Download Center for wireless adapters are generic versions. Since we only have two retail wireless adapter models , in most cases it's better to use the latest system specific drivers provided through your computer manufacturer, these are the only ones that account for OEM customizations.

                    Best regards,
                    Carlos A.

                    • 7. Re: Intel Dual Band Wireless 8265 causing BSOD in Win10
                      nkaufman

                      Yes Carlos, we do understand that.

                       

                      Most of the users (try doing a poll) normally update drivers through their manufacturers who get their drivers from INTEL.

                       

                      It is only when these drivers create ISSUES that people start looking for solutions. Manufacturers who typically have nothing to do with drivers would only pass along the information to INTEL or ask users to revert to older versions (was much easier to do till Windows 10 made it difficult. ). Unless of course in those rare instances where manufacturers customize drivers instead of just packaging them into an executable.

                       

                      So, as owner of drivers that have been causing issues and as the organization that will be (in most cases) ultimately responsible for a FIX, it is INTEL to own up the issue, investigate and create a fix.

                      • 8. Re: Intel Dual Band Wireless 8265 causing BSOD in Win10
                        Intel Corporation
                        This message was posted on behalf of Intel Corporation

                        Hello nkaufman,

                         

                        Thanks for submitting your feedback. We'll make sure to pass it on to our business unit.

                         

                        Azhur Did you have the chance to install the drivers provided by the OEM?

                         

                        Best regards,
                        Eugenio F.

                        • 9. Re: Intel Dual Band Wireless 8265 causing BSOD in Win10
                          Azhur

                          Hi Eugenio,

                          I tried to delete latest drivers, using your procedures, but after PC reboot it is installed automatically.

                          So I can't install older version on top of new one

                          BR, Alex

                          • 10. Re: Intel Dual Band Wireless 8265 causing BSOD in Win10
                            Intel Corporation
                            This message was posted on behalf of Intel Corporation

                            Hello Azhur,

                            Thanks for your reply.

                            What driver version you get when the system reboots? The latest driver might persist if Intel® PROSet/Wireless Software is still installed or if temporary files are storing the driver.

                            Please double check that Intel® PROSet/Wireless Software is uninstalled and  temporary files are cleaned? If you've already done this, remove the drivers as instructed in one of our previous messages. However, install the driver provided by the OEM before you reboot.

                            Please let us know the results.

                            Best regards,
                            Eugenio F.

                            • 11. Re: Intel Dual Band Wireless 8265 causing BSOD in Win10
                              Azhur

                              Hi,

                              when i delete drivers from device managers menu, and press refresh equipment configuration,

                              drivers itstalled automatictly with lower version then before.

                              I done this procedure 4-5 times, and finally -  oldest one 19.50.1.6.

                              after that, I reboot PC and installed 19.71.1.1 provided by OEM Xiaomi.

                               

                              but then I check device manager info and find a lot of errors 411

                               

                              • 12. Re: Intel Dual Band Wireless 8265 causing BSOD in Win10
                                Intel Corporation
                                This message was posted on behalf of Intel Corporation

                                Hello Azhur,

                                Thanks for the update.

                                Checking Microsoft* Event Viewer documentation, Event ID 411 is related to Task Scheduler Service. These kind of errors are usually solved by the system without end user interference.

                                When these errors comes up, is your wireless connection affected? If so, have you noticed a pattern to it?

                                Also, please let us know if the blue screen errors persisted.

                                Best regards,
                                Eugenio F.

                                • 13. Re: Intel Dual Band Wireless 8265 causing BSOD in Win10
                                  Azhur

                                  Hi Eugenio,

                                  seems, 411 error have no any common with BSOD, I check timestamp for for it.

                                   

                                  But, I still have  blue screen time to time ( one time per day) even after OEM drivers installation

                                  • 14. Re: Intel Dual Band Wireless 8265 causing BSOD in Win10
                                    Intel Corporation
                                    This message was posted on behalf of Intel Corporation

                                    Hello Azhur,

                                    Thanks for your reply.

                                    Please allow us more time to investigate this issue. We'll let you know as soon as we have updates.

                                    Best regards,
                                    Eugenio F.

                                    1 2 Previous Next