3 Replies Latest reply on Jun 18, 2015 9:34 AM by kevin_intel





      I purchased a brand new HP Spectre X360 with i7 processor with Windows 8.1.

      In some cases I get the windows bleu screen with :

      DRIVER_IRQL_NOT_LESS_OR_EQUAL  netwbw02.sys.


      Is the solution an update of the Wifi driver?

      Isn't it strange that this happens with a brand new high end laptop?


      grt, Wim

        • 1. Re: netwbw02.sys

          Hello WimJJJ,


          There are some reports from customer In the Microsoft community about this and it seems this could be caused by the router or access point:



          NOTE: These links are being offered for your convenience and should not be viewed as an endorsement by Intel of the content, products, or services offered there.


          Try updating the BIOS of the computer and update the wireless driver. Testing another connection would do the trick.


          Kevin M

          • 2. Re: netwbw02.sys

            I also meet same issue for many times at my Spectre x360, which is not related with the WIFI route or access point.

            Even if uninstall all WIDI related software/drivers and update to latest WLAN driver from HP website, the BSOD still occur...


            Any solution?



            The following is parts of dump file.


            READ_ADDRESS:  ffffe00425df8b78


            CURRENT_IRQL:  2




            fffff800`bf34ef1a 43399cac7c1b0000 cmp     dword ptr [r12+r13*4+1B7Ch],ebx


            CUSTOMER_CRASH_COUNT:  1




            BUGCHECK_STR:  AV


            PROCESS_NAME:  System


            ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre


            DPC_STACK_BASE:  FFFFD001417A2FB0


            TRAP_FRAME:  ffffd0014179a630 -- (.trap 0xffffd0014179a630)

            NOTE: The trap frame does not contain all registers.

            Some register values may be zeroed or incorrect.

            rax=0000000000000002 rbx=0000000000000000 rcx=fffff8026eef00b0

            rdx=fffffffffd15b2c8 rsi=0000000000000000 rdi=0000000000000000

            rip=fffff800bf34ef1a rsp=ffffd0014179a7c0 rbp=ffffd0014179a8c0

            r8=0000000000000000  r9=0000000000000000 r10=0000000000000000

            r11=ffffe000243affb8 r12=0000000000000000 r13=0000000000000000

            r14=0000000000000000 r15=0000000000000000

            iopl=0         nv up ei ng nz na pe nc


            fffff800`bf34ef1a 43399cac7c1b0000 cmp     dword ptr [r12+r13*4+1B7Ch],ebx ds:00000000`00001b7c=????????

            Resetting default scope


            LAST_CONTROL_TRANSFER:  from fffff8026ed667e9 to fffff8026ed5aca0



            ffffd001`4179a4e8 fffff802`6ed667e9 : 00000000`0000000a ffffe004`25df8b78 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx

            ffffd001`4179a4f0 fffff802`6ed6503a : 00000000`00000000 00000000`00000000 ffffe000`1fb8a800 ffffe000`25d4b050 : nt!KiBugCheckDispatch+0x69

            ffffd001`4179a630 fffff800`bf34ef1a : 00000000`00000000 ffffd001`4179a8c0 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a

            ffffd001`4179a7c0 00000000`00000000 : ffffd001`4179a8c0 00000000`00000000 00000000`00000000 ffffd001`4179a960 : Netwbw02+0x64f1a



            STACK_COMMAND:  kb




            fffff800`bf34ef1a 43399cac7c1b0000 cmp     dword ptr [r12+r13*4+1B7Ch],ebx


            SYMBOL_STACK_INDEX:  3


            SYMBOL_NAME: Netwbw02+64f1a


            FOLLOWUP_NAME:  MachineOwner


            MODULE_NAME: Netwbw02


            IMAGE_NAME:  Netwbw02.sys


            DEBUG_FLR_IMAGE_TIMESTAMP:  54857262


            FAILURE_BUCKET_ID:  AV_Netwbw02+64f1a


            BUCKET_ID:  AV_Netwbw02+64f1a


            ANALYSIS_SOURCE:  KM


            FAILURE_ID_HASH_STRING:  km:av_netwbw02+64f1a


            FAILURE_ID_HASH:  {fc89cfb0-6ad8-cff2-117d-b4ea381177a6}


            Followup: MachineOwner


            • 3. Re: netwbw02.sys

              Thank you for providing this information. This specific error is related to the wireless Driver so you should post your question here:



              Another very good idea is to report this to the Computer Manufacture so they can handle and support your product.


              Kevin M