XPS 15 9550 crash in nwifi.sys driver with Windows 10

:emotion-2:

There's a new BIOS update that listed as 'Urgent ' on your Dell Product Support page. I suggest you update BIOS to latest version and see if that will make a difference.

Thanks LSUFAN51!

The BIOS update must have been released soon after my post :)  I've applied the update.  I'll give it a few weeks to see how it runs.  Like I said, the crashes are irregular (but frustrating nonetheless).

Thanks for the update.....:emotion-2:

Unfortunately, the crash keeps on occurring.  I've even tried to re-install the 'Killer Wireless-AC 1535 Driver' by Killer Networking.  What is not very helpful is the fact that the install ALWAYS informs me that the driver on my system is out-of-date even though the version numbers match.

In my recent observations, I've seen reference to 'bwcW10x64' - this is part of the Killer Wireless Networking driver. There are some suggestions online regarding 'bwcW10x64', but they haven't proved useful.  It was for this reason that I attempted to update the driver for the wireless card

Second observation is that the BSOD is most easily replicated when merely selecting the wireless icon in the Windows 10 system tray - the icon that sits near the clock at the bottom right-hand side of the screen.

I've attached the latest crash dump. This is the latest stack trace:

************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred srv*c:\Symbols*msdl.microsoft.com/.../symbols
Symbol search path is: srv*c:\Symbols*msdl.microsoft.com/.../symbols
Executable search path is:
Windows 10 Kernel Version 14393 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 14393.693.amd64fre.rs1_release.161220-1747
Machine Name:
Kernel base = 0xfffff803`a9c13000 PsLoadedModuleList = 0xfffff803`a9f18060
Debug session time: Mon Jan 30 09:08:34.820 2017 (UTC + 0:00)
System Uptime: 0 days 0:00:52.719
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
................................................................
.........
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {decafc37, 2, 0, fffff8067fafdcec}

*** WARNING: Unable to verify timestamp for bwcW10x64.sys
*** ERROR: Module load completed but symbols could not be loaded for bwcW10x64.sys
Probably caused by : nwifi.sys ( nwifi!MP6ReturnNBL+30 )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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.
Arguments:
Arg1: 00000000decafc37, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff8067fafdcec, address which referenced memory

Debugging Details:
------------------

DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 10.0.14393.693 (rs1_release.161220-1747)

SYSTEM_MANUFACTURER: Dell Inc.

SYSTEM_PRODUCT_NAME: XPS 15 9550

SYSTEM_SKU: 06E4

BIOS_VENDOR: Dell Inc.

BIOS_VERSION: 1.2.19

BIOS_DATE: 12/22/2016

BASEBOARD_MANUFACTURER: Dell Inc.

BASEBOARD_PRODUCT: 0N7TVV

BASEBOARD_VERSION: A01

DUMP_TYPE: 2

BUGCHECK_P1: decafc37

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff8067fafdcec

READ_ADDRESS: fffff803a9fba338: Unable to get MiVisibleState
00000000decafc37

CURRENT_IRQL: 2

FAULTING_IP:
nwifi!MP6ReturnNBL+30
fffff806`7fafdcec 488b7a28 mov rdi,qword ptr [rdx+28h]

CPU_COUNT: 8

CPU_MHZ: a20

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 5e

CPU_STEPPING: 3

CPU_MICROCODE: 6,5e,3,0 (F,M,S,R) SIG: 9E'00000000 (cache) 9E'00000000 (init)

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: AV

PROCESS_NAME: System

ANALYSIS_SESSION_HOST: DESKTOP-RNQ6CLG

ANALYSIS_SESSION_TIME: 01-31-2017 11:41:54.0276

ANALYSIS_VERSION: 10.0.14321.1024 amd64fre

TRAP_FRAME: ffffc881164fca50 -- (.trap 0xffffc881164fca50)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=ffff9d885f532640
rdx=00000000decafc0f rsi=0000000000000000 rdi=0000000000000000
rip=fffff8067fafdcec rsp=ffffc881164fcbe0 rbp=ffffc881164fccd9
r8=0000000000000001 r9=ffff9d885f4f41f0 r10=ffff9d885f4f41f0
r11=ffff9d885da66020 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nwifi!MP6ReturnNBL+0x30:
fffff806`7fafdcec 488b7a28 mov rdi,qword ptr [rdx+28h] ds:00000000`decafc37=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff803a9d68829 to fffff803a9d5d6f0

STACK_TEXT:
ffffc881`164fc908 fffff803`a9d68829 : 00000000`0000000a 00000000`decafc37 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffffc881`164fc910 fffff803`a9d66e07 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffffc881`164fca50 fffff806`7fafdcec : ffffc881`164fcc59 ffff9d88`5fc98b01 00000000`00000000 ffff9d88`5a5a75f0 : nt!KiPageFault+0x247
ffffc881`164fcbe0 fffff806`78fb4533 : fffff806`7fb03740 ffffc881`164fccd9 ffff9d88`5da4cc08 ffff9d88`00000000 : nwifi!MP6ReturnNBL+0x30
ffffc881`164fcc10 fffff806`79008a81 : ffff9d88`5f95a510 ffffc881`164fcc90 00000000`00000012 ffff9d88`5a8b4e40 : ndis!ndisCallReceiveCompleteHandler+0x33
ffffc881`164fcc50 fffff806`78fe0153 : ffff9d88`5f4f41f0 ffff9d88`5f4f41f0 00000000`00000000 fffff806`7b1ade00 : ndis!ndisInvokeNextReceiveCompleteHandler+0x101
ffffc881`164fcd30 fffff806`7b1addec : ffff9d88`5da58c70 ffff9d88`5f4f41f0 ffff9d88`5f4f4101 fffff806`7b1ae301 : ndis!NdisFReturnNetBufferLists+0x21d83
ffffc881`164fcdb0 ffff9d88`5da58c70 : ffff9d88`5f4f41f0 ffff9d88`5f4f4101 fffff806`7b1ae301 00000000`00000001 : bwcW10x64+0xddec
ffffc881`164fcdb8 ffff9d88`5f4f41f0 : ffff9d88`5f4f4101 fffff806`7b1ae301 00000000`00000001 00000000`00000035 : 0xffff9d88`5da58c70
ffffc881`164fcdc0 ffff9d88`5f4f4101 : fffff806`7b1ae301 00000000`00000001 00000000`00000035 ffff9d88`5f4f41f0 : 0xffff9d88`5f4f41f0
ffffc881`164fcdc8 fffff806`7b1ae301 : 00000000`00000001 00000000`00000035 ffff9d88`5f4f41f0 fffff806`7b1ada8a : 0xffff9d88`5f4f4101
ffffc881`164fcdd0 00000000`00000001 : 00000000`00000035 ffff9d88`5f4f41f0 fffff806`7b1ada8a 00000000`00000000 : bwcW10x64+0xe301
ffffc881`164fcdd8 00000000`00000035 : ffff9d88`5f4f41f0 fffff806`7b1ada8a 00000000`00000000 00000000`0000dcb1 : 0x1
ffffc881`164fcde0 ffff9d88`5f4f41f0 : fffff806`7b1ada8a 00000000`00000000 00000000`0000dcb1 00000000`00000000 : 0x35
ffffc881`164fcde8 fffff806`7b1ada8a : 00000000`00000000 00000000`0000dcb1 00000000`00000000 00000000`00000000 : 0xffff9d88`5f4f41f0
ffffc881`164fcdf0 00000000`00000000 : 00000000`0000dcb1 00000000`00000000 00000000`00000000 ffff9d88`5f4f41f0 : bwcW10x64+0xda8a

STACK_COMMAND: kb

THREAD_SHA1_HASH_MOD_FUNC: c3e4cc9b9ade6f0c52ef5022c68a906d3e91fcdb

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 86753b735e193b9275749cd9373308748e819691

THREAD_SHA1_HASH_MOD: be3925f56222e3ebb3cf229c9cec46ae019b1590

FOLLOWUP_IP:
nwifi!MP6ReturnNBL+30
fffff806`7fafdcec 488b7a28 mov rdi,qword ptr [rdx+28h]

FAULT_INSTR_CODE: 287a8b48

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: nwifi!MP6ReturnNBL+30

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nwifi

IMAGE_NAME: nwifi.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 57899aff

IMAGE_VERSION: 10.0.14393.0

BUCKET_ID_FUNC_OFFSET: 30

FAILURE_BUCKET_ID: AV_nwifi!MP6ReturnNBL

BUCKET_ID: AV_nwifi!MP6ReturnNBL

PRIMARY_PROBLEM_CLASS: AV_nwifi!MP6ReturnNBL

TARGET_TIME: 2017-01-30T09:08:34.000Z

OSBUILD: 14393

OSSERVICEPACK: 693

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: 2016-12-21 06:50:57

BUILDDATESTAMP_STR: 161220-1747

BUILDLAB_STR: rs1_release

BUILDOSVER_STR: 10.0.14393.693

ANALYSIS_SESSION_ELAPSED_TIME: 38a5

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:av_nwifi!mp6returnnbl

FAILURE_ID_HASH: {13bbec0b-8f52-6a23-7a4f-7af1ac11bde9}

Followup: MachineOwner
---------

Also experiencing the same issue on Dell XPS 13 9360

Also experiencing this issue on Dell XP13 9360 with no solution.

And I am experiencing a similar problem after installing the 1.2.19 BIOS.

I see you are running VBox... have you explored any possible problems with it.  The drivers seem to be from 2017 but no way for me to know if they could be involved.

The bwcW10x64 does seem to be involved.  But I don't have the nwifi.sys driver on my system so perhaps it is related to the Killer wireless.. Who manufacturers that device, Qualcomm?

There is also a little older driver which you might want to check.

fffff806`7c2c0000 fffff806`7c2ec000   ccSetx64   (deferred)            

   Image path: \SystemRoot\system32\drivers\NSTx64\7DE070B0.02A\ccSetx64.sys

   Image name: ccSetx64.sys

   Browse all global symbols  functions  data

   Timestamp:        Mon Sep 23 22:58:04 2013 (52410DCC)

Thanks for the additional feedback.  As an aside note, I have got in touch with Killer Networking to analyze the issue.  Thus far, I sent them a log/analytics file they requested.  FYI, this is a Rivet Networks company.

Saltgrass, I did consider a problem with the VirtualBox driver.   How do I handle that? Try uninstalling?  I'd rather not go down that route..

I believe the ccSetx64 belongs to 'Norton Identity Safe' (Password Manager) by Symantec.  I'll try uninstall that and see if the problems still exists. Can I ask what pointed you there?  Was it merely the date of the driver?

Thanks.

Hi, I have the same problem, but I need VirtualBox with network support for my work so I replaced wifi adapter for one from Intel (www.windowscentral.com/dell-xps-wifi-fix-upgrade-wireless) and everything is fine now...