Windows 10: Netwbw02.sys crash on all Threshold and Redstone builds (so far) RRS feed

  • Question

  • I seem to have random BSOD which during the crash seems to have no information. However, memory dumps point to Netwbw02.sys - Intel's WiFi driver. My card is Dual-Band Wireless AC 3160. However, this seems to affect only build 10586 and everything above, including the two builds of RedStone so far. 

    Unfortunately, these are all full memory dumps including the kernel, so I'm reluctant to share them publicly. Unlike Microsoft Connect, there seems to be no option to share files confidentially with Microsoft here, nor am I sure if this is to be filed here (considering it is the official driver installed through Windows Update), or has to be filed with Intel. Please let me know how to proceed there.

    The call stack, and module:

    1: kd> lmvm Netwbw02
    Browse full module list
    start             end                 module name
    fffff801`6d400000 fffff801`6d789000   Netwbw02   (no symbols)           
        Loaded symbol image file: Netwbw02.sys
        Image path: \SystemRoot\System32\drivers\Netwbw02.sys
        Image name: Netwbw02.sys
        Browse all global symbols  functions  data
        Timestamp:        Tue Nov 03 20:00:10 2015 (5638C4F2)
        CheckSum:         00364A95
        ImageSize:        00389000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    1: kd> k
     # Child-SP          RetAddr           Call Site
    00 ffffd001`00e627a8 fffff801`6d460470 nt!KeBugCheckEx
    01 ffffd001`00e627b0 fffff801`6d5f7475 Netwbw02+0x60470
    02 ffffd001`00e627f0 fffff801`6d5f8fe0 Netwbw02+0x1f7475
    03 ffffd001`00e62840 fffff801`6d5f55fa Netwbw02+0x1f8fe0
    04 ffffd001`00e62870 fffff801`6d5f5e3c Netwbw02+0x1f55fa
    05 ffffd001`00e628f0 fffff801`6d5f30b4 Netwbw02+0x1f5e3c
    06 ffffd001`00e62980 fffff801`6d45c3de Netwbw02+0x1f30b4
    07 ffffd001`00e629d0 fffff801`6800aa4e Netwbw02+0x5c3de
    08 ffffd001`00e62a00 fffff801`6802105d ndis!ndisQueuedMiniportDpcWorkItem+0x24e
    09 ffffd001`00e62b40 fffff802`f6c96125 ndis!ndisReceiveWorkerThread+0x21d
    0a ffffd001`00e62c10 fffff802`f6dd4916 nt!PspSystemThreadStartup+0x41
    0b ffffd001`00e62c60 00000000`00000000 nt!KiStartSystemThread+0x16

    Memory dump summary:

    Windows 10 Kernel Version 10586 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 10586.63.amd64fre.th2_release.160104-1513
    Machine Name:
    Kernel base = 0xfffff802`f6c8d000 PsLoadedModuleList = 0xfffff802`f6f6bc70
    Debug session time: Thu Feb  4 16:48:04.575 2016 (UTC + 5:30)
    System Uptime: 0 days 0:44:06.398
    Probably caused by : Netwbw02.sys ( Netwbw02+60470 )
    1: kd> !analyze -v
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    Unknown bugcheck code (dead039e)
    Unknown bugcheck description
    Arg1: 00000000121e0009
    Arg2: 00000000012507ba
    Arg3: 0000000011af0000
    Arg4: 0000000000000000
    Debugging Details:
    Page 3c0 not present in the dump file. Type ".hh dbgerr004" for details
    Page 3c0 not present in the dump file. Type ".hh dbgerr004" for details
    Page 3c0 not present in the dump file. Type ".hh dbgerr004" for details
    BUILD_VERSION_STRING:  10586.63.amd64fre.th2_release.160104-1513
    SYSTEM_MANUFACTURER:  Hewlett-Packard
    SYSTEM_VERSION:  Type1ProductConfigId
    BIOS_VENDOR:  Insyde
    BIOS_DATE:  12/16/2015
    DUMP_TYPE:  1
    BUGCHECK_P1: 121e0009
    BUGCHECK_P2: 12507ba
    BUGCHECK_P3: 11af0000
    BUGCHECK_P4: 0
    CPU_COUNT: 4
    CPU_MHZ: 95a
    CPU_VENDOR:  GenuineIntel
    CPU_MODEL: 3d
    CPU_MICROCODE: 6,3d,4,0 (F,M,S,R)  SIG: 1F'00000000 (cache) 1F'00000000 (init)
    PROCESS_NAME:  System
    ANALYSIS_SESSION_TIME:  02-15-2016 04:43:06.0676
    ANALYSIS_VERSION: 10.0.10586.567 amd64fre
    LAST_CONTROL_TRANSFER:  from fffff8016d460470 to fffff802f6dcf770
    ffffd001`00e627a8 fffff801`6d460470 : 00000000`dead039e 00000000`121e0009 00000000`012507ba 00000000`11af0000 : nt!KeBugCheckEx
    ffffd001`00e627b0 fffff801`6d5f7475 : ffffe000`59475e30 ffffe000`5b3d6360 ffffd001`01df8004 01d15f3d`b7713300 : Netwbw02+0x60470
    ffffd001`00e627f0 fffff801`6d5f8fe0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : Netwbw02+0x1f7475
    ffffd001`00e62840 fffff801`6d5f55fa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : Netwbw02+0x1f8fe0
    ffffd001`00e62870 fffff801`6d5f5e3c : ffffe000`59475e30 ffffe000`5b3d6360 ffffe000`56bd7002 ffffe000`5b3d63ff : Netwbw02+0x1f55fa
    ffffd001`00e628f0 fffff801`6d5f30b4 : ffffe000`00000001 ffffe000`5b3a0910 00000000`80000000 ffffe000`5b3fea90 : Netwbw02+0x1f5e3c
    ffffd001`00e62980 fffff801`6d45c3de : ffffd001`00100100 ffffd001`00e62b00 ffffe000`5bb49b90 00000000`00000000 : Netwbw02+0x1f30b4
    ffffd001`00e629d0 fffff801`6800aa4e : 00000000`00000000 ffffe000`5c94e140 fffff802`f6fbe000 fffff802`f6c8d000 : Netwbw02+0x5c3de
    ffffd001`00e62a00 fffff801`6802105d : ffffe000`56bda960 ffffe000`56bda940 00000000`00000000 ffffe000`5bb49f08 : ndis!ndisQueuedMiniportDpcWorkItem+0x24e
    ffffd001`00e62b40 fffff802`f6c96125 : 00000005`b19bbdff ffffe000`56bd7040 fffff801`68020e40 00000000`00000001 : ndis!ndisReceiveWorkerThread+0x21d
    ffffd001`00e62c10 fffff802`f6dd4916 : ffffd001`00100180 ffffe000`56bd7040 fffff802`f6c960e4 000f0000`00000000 : nt!PspSystemThreadStartup+0x41
    ffffd001`00e62c60 00000000`00000000 : ffffd001`00e63000 ffffd001`00e5d000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
    THREAD_SHA1_HASH_MOD_FUNC:  d6542606b54115d676ac94db3f1c19ea8bfe00cf
    THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  8a17892fe8c49e3c723a5239c48d73c57346f1db
    THREAD_SHA1_HASH_MOD:  1353aca65042148828d894ce673a89c61fbb0d02
    fffff801`6d460470 cc              int     3
    FAULT_INSTR_CODE:  cccccccc
    SYMBOL_NAME:  Netwbw02+60470
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: Netwbw02
    IMAGE_NAME:  Netwbw02.sys
    FAILURE_BUCKET_ID:  0xDEAD039E_Netwbw02!Unknown_Function
    BUCKET_ID:  0xDEAD039E_Netwbw02!Unknown_Function
    PRIMARY_PROBLEM_CLASS:  0xDEAD039E_Netwbw02!Unknown_Function
    TARGET_TIME:  2016-02-04T11:18:04.000Z
    OSBUILD:  10586
    SUITE_MASK:  272
    OSNAME:  Windows 10
    OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS
    USER_LCID:  0
    OSBUILD_TIMESTAMP:  2016-01-05 06:58:56
    BUILDDATESTAMP_STR:  160104-1513
    BUILDLAB_STR:  th2_release
    BUILDOSVER_STR:  10.0.10586.63.amd64fre.th2_release.160104-1513
    FAILURE_ID_HASH_STRING:  km:0xdead039e_netwbw02!unknown_function
    FAILURE_ID_HASH:  {9dc68c07-92db-c4b0-7fc8-ffb7888f90fc}

    Cross-posted from:

    Thursday, May 19, 2016 12:25 PM

All replies

  • What driver and you using, the device manufacture or Intel's? Intel have newer drivers it appears, have you tried those?
    Thursday, May 19, 2016 5:43 PM
  • Prasanna,

    I haven't noticed an unknown bugcheck code results.

    For memory dumps, if convenient, please check and see if you could generate any small memory dump, then upload them into OneDrive and post the shared link here.

    If Access is concerned, you may enable audit regarding the download action, we will try to download it within one or two days.

    Currently the symbol files are only available up to Windows 10 march 2016, which is the build 14295, so if you have installed newer version, then WinDbg might not be able to output the proper information.

    In addition, you may also submit this through Windows Feedback Tool, as this is also insist in the Insider builds.


    Please mark the reply as an answer if you find it is helpful.

    If you have feedback for TechNet Support, contact

    Friday, May 20, 2016 5:07 AM
  • Mr. Happy, 

    I've tried the drivers from both HP (the device manufacturer), as well as Intel. Both seems to have these issues. Still unable to narrow down the specific scenarios of the issues, but I do have a much newer dumps. This is relatively speaking quite old since the dump is nearly 3 months old (On a complete aside, that feels great to say). I've accumulated the dumps, just didn't find the time to analyze them. Will upload them soon.  

    Friday, May 20, 2016 6:39 AM
  • Thanks. I shall upload them to one drive and share them. And regarding the symbols, I may not even have posted this if this was on an Insider build, as that isn't completely unexpected for driver manufacturers to take time to catch up. However, this is on the Retail build (10586), which is what's making it troublesome. 

    I do have more of these BSOD (where B stands for both Blue and Brown incidentally. Didn't know that the Windows Team changed colors, or perhaps it is an indication of something?). I'll upload the newer ones and share them here.  

    Friday, May 20, 2016 6:47 AM
  • I've added everything here: 

    2016-Q1-Kernel-Netwbw02.sys (Folder with all dumps)

    They contain different dumps with different versions of the drivers, and Windows updates as and when it was released. Each of them seems to have mild variations in their stacks (Possible multiple issues). There are several mini dumps as well as full dumps.

    Full dumps






    Please let me know when the full dumps are downloaded, so I can remove them. Thanks.

    Tuesday, May 24, 2016 11:48 AM
  • Hi Prasanna,

    I am trying to download the file, as it is large, it needs some time (around half hours) to finish downloading.

    I will check the dumps once I finished downloading, there might be some time delay before I share any results here.

    Thank you for your patience.


    Please mark the reply as an answer if you find it is helpful.

    If you have feedback for TechNet Support, contact

    Wednesday, May 25, 2016 3:27 AM
  • Hello Michael,

    Is there any update on this?
    This crash happened again recently two days ago, multiple times. 
    Also, oddly the BSOD seemed to have crashed as well on the 100% mark. (Never restarted on its own.) 

    There's one full dump of a 0xdead039e error (which restarted correctly), and also several instances where BSOD directly 
    indicated Netwbw02.sys as the faulting module with DRIVER_IRQL_NOT_LESS_OR_EQUAL error (which got stuck on 100%). Error number that was also noticed during another crash was: 0xdead7495. 

    However all the stack traces point to the mild variations of Netwbw02.sys again. This driver seems to be very buggy.

    I've upload the new minidumps (the last 3 by date), as well one full dump. 

    While, I'll leave the minidumps as it is, please let me know once you have the full dumps, so that I may stop sharing them. 


    - Prasanna V. Loganathar

    Thursday, June 16, 2016 11:05 AM
  • This is the call stack for the IRQL error on the same driver:
    (The lastest 2 minidumps)

    0: kd> k
     # Child-SP          RetAddr           Call Site
    00 fffff801`89802248 fffff801`24460470 nt!KeBugCheckEx
    01 fffff801`89802250 00000000`dead7495 Netwbw02+0x60470
    02 fffff801`89802258 00000000`121e0009 0xdead7495
    03 fffff801`89802260 00000000`0125027e 0x121e0009
    04 fffff801`89802268 00000000`11af0000 0x125027e
    05 fffff801`89802270 00000000`00000000 0x11af0000

    I've quickly summarized all the different types of errors with the Netwbw02.sys and its call stacks, here on my blog.

    Probably could help:

    - Prasanna V. Loganathar

    Thursday, June 16, 2016 3:38 PM
  • Hi Prasanna,

    Apologize for the late response.

    As you already shared, those dumps are all points to Netwbw02.sys, and checked your blog also, one thing to remind is that if you would like to share the full dump with Microsoft directly, please take use fo Windows Feebdack Tool, that is the way much faster than the way from my side. :)

    As suggested in the support article below:

    If the problem is caused by the driver that you are developing, make sure that the function that was executing at the time of the bug check is not marked as pageable or does not call any other inline functions that could be paged out.

    So here I would suggest to contact Intel for additional assistance, see if they could offer any further good suggestion, or share some information regarding the driver updates.


    Please mark the reply as an answer if you find it is helpful.

    If you have feedback for TechNet Support, contact

    Friday, June 17, 2016 6:18 AM