Consistent BSOD's that stemming from SonicWall Global VPN Client

I have a Windows 10 Laptop (Dell) that consistently reboots when the user is at home and trying to get work done via VPN through the SonicWall Global VPN Client. There are 50 dmp files in the attached zip file, so plenty to analyze. From the ones that I looked at, all the fault modules seemed to be one kind of a networking driver or another.

What I'm hoping to figure out is what I can do about it. I know that the VPN client is part of the problem, but it is at the latest version available (4.9.9.1016). I'm hoping you fine folks could maybe point me in the direction of something else that I can do to fix the BSOD problem.

Thanks so much!

The dumpfiles are blaming Dnelwf64.sys

Code:

   *******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 139, {3, fffff803cd6cae40, fffff803cd6cad98, 0}

*** WARNING: Unable to verify timestamp for dnelwf64.sys
*** ERROR: Module load completed but symbols could not be loaded for dnelwf64.sys
Probably caused by : dnelwf64.sys ( dnelwf64+1cc5 )

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C2, {7, 126c, 0, ffffe0012197c1b0}

*** WARNING: Unable to verify timestamp for dnelwf64.sys
*** ERROR: Module load completed but symbols could not be loaded for dnelwf64.sys
unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPagedPoolEnd
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
GetUlongFromAddress: unable to read from fffff8026cb55b78
Probably caused by : nwifi.sys ( nwifi!Dot11PacketConverterReturnPacket+d2 )

dnelwf64 Tue Oct 13 20:21:22 2015
Driver Description: Citrix Deterministic Networks DNE Driver (Cisco VPN Client)
Driver Update Site: http://www.citrix.com/lang/English/lp/lp_1680845.asp
Sonicwall recommends to uninstall all other VPN clients, is this a leftover file ?

In the event viewer under Problem devices:

SonicWALL Virtual NIC ROOT\SWVNIC\0000 This device is disabled.

Check this and enable this device.
And also: swvnic.sys Mon Feb 23 04:04:50 2009
Driver Description: SonicWALL Virtual Miniport Driver
Driver Update Site: Software and Security Support


Your network drivers are predating windows 10
e1d65x64 Thu Jun 18 18:37:56 2015
Driver Description: Intel Pro/1000 Network Adapter driver
Driver Update Site: Drivers & Software
or OEM
NETwew01 Tue Jan 06 17:19:19 2015
Driver Description: Intel Wireless WiFi Link Driver
Driver Update Site: OEM
or
Drivers & Software
Your supportpage for this laptop is Product Support | Dell US


Hope this give you some clues/startingpoint to fix this BSODproblem.

This is a fresh Windows 10 install from media created with MS's tools, so if the Citrix driver is in there, then the SonicWall install must have put it there. I'm guessing it's dependent on it. That Citrix link is dead.

I believe that it is normal for the SonicWall NIC to be disabled until it's called into use by the VPN client.

I'll get those Intel drivers updated for sure. Not sure how an old version got installed.

It might be worth noting, that I did the same bug check on some of the .dmp files. The latest one shows the same thing that you saw, but almost every one I tried had a different module at fault, but they were all networking related from what I could tell. Not sure what to make of that info though.

Updated LAN and WLAN drivers and there was no blue screen this weekend. Hopefully we're over the hump.