7 Replies Latest reply on Oct 12, 2016 5:45 PM by Intel Corporation

    BSOD IRQL_NOT_LESS_OR_EQUAL netwbw02.sys wireless AC-7260


      I'm suddenly getting a BSOD after updating to the latest windows 10 build (1607).  This started right after the update.  In fact, I sometimes get a BSOD, and sometimes  I lose my internet.  I'll still have the wifi connection, but it will say no internet.  If I toggle the wifi off then on it reconnects with internet with no problem.  I was having ZERO issues until the latest update.  My laptop is an Acer Aspire-V3 772G-9460


      Currently using driver version  Here's the dump file from the latest BSOD:




      Microsoft (R) Windows Debugger Version 10.0.14321.1024 AMD64

      Copyright (c) Microsoft Corporation. All rights reserved.





      Loading Dump File [C:\Windows\Minidump\100616-11546-01.dmp]

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



      Symbol search path is: srv*

      Executable search path is:

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

      Product: WinNt, suite: TerminalServer SingleUserTS

      Built by: 14393.206.amd64fre.rs1_release.160915-0644

      Machine Name:

      Kernel base = 0xfffff801`9480c000 PsLoadedModuleList = 0xfffff801`94b10080

      Debug session time: Thu Oct  6 08:44:23.856 2016 (UTC - 6:00)

      System Uptime: 1 days 1:01:07.420

      Loading Kernel Symbols





      Loading User Symbols

      Loading unloaded module list



      *                                                                             *

      *                        Bugcheck Analysis                                    *

      *                                                                             *




      Use !analyze -v to get detailed debugging information.



      BugCheck D1, {8, 2, 0, fffff805d951c138}



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

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

      Probably caused by : Netwbw02.sys ( Netwbw02+3c138 )



      Followup:     MachineOwner




      0: kd> !analyze -v


      *                                                                             *

      *                        Bugcheck Analysis                                    *

      *                                                                             *





      An attempt was made to access a pageable (or completely invalid) address at an

      interrupt request level (IRQL) that is too high.  This is usually

      caused by drivers using improper addresses.

      If kernel debugger is available get stack backtrace.


      Arg1: 0000000000000008, memory referenced

      Arg2: 0000000000000002, IRQL

      Arg3: 0000000000000000, value 0 = read operation, 1 = write operation

      Arg4: fffff805d951c138, address which referenced memory



      Debugging Details:






      DUMP_CLASS: 1






      BUILD_VERSION_STRING:  10.0.14393.206 (rs1_release.160915-0644)






      SYSTEM_PRODUCT_NAME:  Aspire V3-772G



      SYSTEM_SKU:  Aspire V3-772G_0781_1.15



      SYSTEM_VERSION:  V1.15



      BIOS_VENDOR:  Insyde Corp.



      BIOS_VERSION:  V1.15



      BIOS_DATE:  03/07/2014









      BASEBOARD_VERSION:  Type2 - Board Version



      DUMP_TYPE:  2



      BUGCHECK_P1: 8



      BUGCHECK_P2: 2



      BUGCHECK_P3: 0



      BUGCHECK_P4: fffff805d951c138



      READ_ADDRESS: fffff80194bb2338: Unable to get MiVisibleState




      CURRENT_IRQL:  2





      fffff805`d951c138 488b4008        mov     rax,qword ptr [rax+8]



      CPU_COUNT: 8



      CPU_MHZ: 893



      CPU_VENDOR:  GenuineIntel



      CPU_FAMILY: 6



      CPU_MODEL: 3c






      CPU_MICROCODE: 6,3c,3,0 (F,M,S,R)  SIG: 1E'00000000 (cache) 1E'00000000 (init)












      PROCESS_NAME:  System






      ANALYSIS_SESSION_TIME:  10-06-2016 10:19:53.0144



      ANALYSIS_VERSION: 10.0.14321.1024 amd64fre



      TRAP_FRAME:  ffffd300d012b9d0 -- (.trap 0xffffd300d012b9d0)

      NOTE: The trap frame does not contain all registers.

      Some register values may be zeroed or incorrect.

      rax=0000000000000000 rbx=0000000000000000 rcx=ffff868a2d146dd0

      rdx=ffff868a2f8181c0 rsi=0000000000000000 rdi=0000000000000000

      rip=fffff805d951c138 rsp=ffffd300d012bb60 rbp=0000000000000000

      r8=0000000000000003  r9=0000000000000000 r10=ffff868a2253e4f0

      r11=0000000000000018 r12=0000000000000000 r13=0000000000000000

      r14=0000000000000000 r15=0000000000000000

      iopl=0         nv up ei pl zr na po nc


      fffff805`d951c138 488b4008        mov     rax,qword ptr [rax+8] ds:00000000`00000008=????????????????

      Resetting default scope



      LAST_CONTROL_TRANSFER:  from fffff80194961429 to fffff801949562b0




      ffffd300`d012b888 fffff801`94961429 : 00000000`0000000a 00000000`00000008 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx

      ffffd300`d012b890 fffff801`9495fa07 : 00000000`00000000 ffff868a`2a1276a0 ffff868a`2f8181c0 ffff868a`2629b000 : nt!KiBugCheckDispatch+0x69

      ffffd300`d012b9d0 fffff805`d951c138 : 00000000`00000000 00000000`00000000 ffff868a`2f8181c0 ffff868a`2629b010 : nt!KiPageFault+0x247

      ffffd300`d012bb60 00000000`00000000 : 00000000`00000000 ffff868a`2f8181c0 ffff868a`2629b010 ffff868a`2f8181c0 : Netwbw02+0x3c138





      STACK_COMMAND:  kb



      THREAD_SHA1_HASH_MOD_FUNC:  07c5760dc6d755d8e28ef47808e657cc562053d9



      THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  deb1ebb3f5348600846a5e13a638b18e59ac6205



      THREAD_SHA1_HASH_MOD:  3bbec4877b3f0af5445f1909e9fd7302cdb43072





      fffff805`d951c138 488b4008        mov     rax,qword ptr [rax+8]



      FAULT_INSTR_CODE:  8408b48






      SYMBOL_NAME:  Netwbw02+3c138



      FOLLOWUP_NAME:  MachineOwner



      MODULE_NAME: Netwbw02



      IMAGE_NAME:  Netwbw02.sys









      FAILURE_BUCKET_ID:  AV_Netwbw02!unknown_function



      BUCKET_ID:  AV_Netwbw02!unknown_function



      PRIMARY_PROBLEM_CLASS:  AV_Netwbw02!unknown_function



      TARGET_TIME:  2016-10-06T14:44:23.000Z



      OSBUILD:  14393









      OS_REVISION: 0



      SUITE_MASK:  272



      PRODUCT_TYPE:  1






      OSNAME:  Windows 10



      OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS






      USER_LCID:  0



      OSBUILD_TIMESTAMP:  2016-09-15 10:21:59



      BUILDDATESTAMP_STR:  160915-0644



      BUILDLAB_STR:  rs1_release



      BUILDOSVER_STR:  10.0.14393.206









      FAILURE_ID_HASH_STRING:  km:av_netwbw02!unknown_function



      FAILURE_ID_HASH:  {a415ca6b-2045-2b98-1496-68c4348fccff}

        • 1. Re: BSOD IRQL_NOT_LESS_OR_EQUAL netwbw02.sys wireless AC-7260
          Intel Corporation
          This message was posted on behalf of Intel Corporation

          Hello DerrickRay, 

          We understand you're experiencing some connectivity issues and BSoD errors after upgrading to the latest build of Windows® 10. Our recommendation in this case is to make sure your wireless drivers are up to date. You can also check with your computer manufacturer to see if a BIOS update is available.

          • You can find the latest drivers for your computer in the following page from Acer*: x.
          • Since your Original Equipment Manufacturer (OEM) does not provide a driver, you can try the latest Intel® PROSet/Wireless Software and Drivers for Windows® 10
          • Did this wireless adapter come preinstalled, or was it purchased separately as an upgrade?
          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. We do not offer support for any third party tool mentioned here.

          Best regards,
          Carlos A.
          • 2. Re: BSOD IRQL_NOT_LESS_OR_EQUAL netwbw02.sys wireless AC-7260

            My wireless driver is up to date as far as I know.  I'm using version, which appears to be the most up to date version for the wireless card that I am using.


            I also have the latest BIOS version.


            I purchased this wireless card as an upgrade.  It was working flawlessly until the latest windows update was installed.  In fact, just before typing this response I lost my wifi and had to toggle it off then back on to get re-connected to the internet.

            • 3. Re: BSOD IRQL_NOT_LESS_OR_EQUAL netwbw02.sys wireless AC-7260
              Intel Corporation
              This message was posted on behalf of Intel Corporation

              Hello DerrickRay,

              Keep in mind that only OEMs and their authorized representatives are allowed to install/upgrade these adapters. Even though this wireless adapter did not originally give you any problems, it's possible that a Windows* update could have triggered a compatibility issue.

              Please review this articles:

              In a best effort basis, I can recommend for you to perform a clean installation of your wireless drivers. Hopefully this will resolve your issue:


              Note: After uninstalling your wireless drivers, you will lose WiFi connectivity. We recommend downloading the latest drivers and saving them to an easy to find location first. Or having the option to connect using a wired connection.



              1. Remove WiFi components 
                1. Uninstall driver from Device Manager*. If prompted, choose remove driver.
                2. Remove Intel® PROSet/Wireless Software and Drivers from Programs and Features in the Control Panel.
              2. Remove temporary files 
                1. Press Windows* Key + R to open the run box. Type Cleanmgr.exe. Press OK.
                2. Select your boot drive (usually C:\)
                3. Check Temporary Files and uncheck everything else. Press OK.
              3. Remove hidden temporary folders 
                1. Go to %USERPROFILE%\AppData\Roaming\
                2. Delete the "Intel" folder found here.
              4. Install the latest version of the Intel® PROSet/Wireless Software and Drivers. 
                1. Choose to Customize.
                2. Select all options available.


              If the problem persists after this troubleshooting, you can try temporarily disabling your antivirus or VPN software, as it could be altering the way your driver behaves.


              Hope this information helps.


              Best regards,
              Carlos A.

              • 4. Re: BSOD IRQL_NOT_LESS_OR_EQUAL netwbw02.sys wireless AC-7260

                Followed all of the steps outlined above.  Lost wifi connectivity probably about 10 hours later.


                For the record, I'm using windows defender as my antivirus and am not running any VPN software.  My guess is that the latest updates to windows has created some sort of compatibility issue with this wifi driver.  Not sure what other steps I can take at this point.

                • 5. Re: BSOD IRQL_NOT_LESS_OR_EQUAL netwbw02.sys wireless AC-7260
                  Intel Corporation
                  This message was posted on behalf of Intel Corporation

                  Hello DerrickRay,

                  Since what you're doing is not supported, our recommendation would be to contact the manufacturer of your computer to see if this wireless adapter is approved for your system. They may also be able to recommend a supported replacement.

                  Carlos A.

                  • 6. Re: BSOD IRQL_NOT_LESS_OR_EQUAL netwbw02.sys wireless AC-7260

                    With all due respect that's nonsense.  If that were the case this chip would have been giving me problems right from the start.  What I think I'll do is press the issue with Microsoft as it seems it is their update that is at the root of the issue.  Bottom line is that an incompatibility was recently created and it should be fixable on one end or the other.

                    • 7. Re: BSOD IRQL_NOT_LESS_OR_EQUAL netwbw02.sys wireless AC-7260
                      Intel Corporation
                      This message was posted on behalf of Intel Corporation

                      Hello DerrickRay,

                      I understand your point, specially considering the adapter worked before. Regrettably wireless integrations do limit our support options since we're only able to provide a generic driver, and have no way of finding the specific driver from the OEM the adapter was intended for.

                      Hopefully Microsoft* will be able to provide a solution, or a future update might resolve the problem. 

                      Carlos A.