BSOD when using ad-hoc

Hello all, I originally ran into a bsod that pointed to a video driver. Jumped on NVidia site got the driver. That worked well until recently. Haven't changed any settings since but now i'm getting one related to Memory failure. I've ran memtest several times, no faults found on any of them. Chased a few more threads, nothing really helped...so, here I am.
I used bluescreenview to capture the offending driver and it comes up with "ntoskml.exe" and "ndis.sys" as the culprits. Now I've uninstalled and reinstalled most of my drivers trying to chase down the last bsod epidemic I encountered. I'm hoping everything was properly reinstalled and I don't look foolish. I can't seem to locate the problem though. The only correlation I've found that causes it is while ad-hoc'ing my phone to watch youtube using landline internet instead of my data(wifi is disabled for phones, so that's my workaround). Anyway, I've attached the zip file y'all requested below though. Any help would be much appreciated. Thanks in advance

Hi there,

My bluescreen analysis is showing an probem with the Intel Wifi driver. I think it has something to do with the adhoc connection:

Code:

0x0000001A:    MEMORY_MANAGEMENT (2018-02-21 19:59:53) [Windows 10] 
 
CAUSED BY:     Netwbw02.sys [2016-10-09] * Intel® Wireless WiFi Link Driver - Intel® Wireless WiFi Link Adapter * => https://downloadcenter.intel.com/default.aspx  
               nvlddmkm.sys [2018-01-23] * nVidia Video drivers * => http://www.nvidia.com/Download/index.aspx  
 
PROCESS:       System 
 
Usual causes:  Device driver, memory, kernel

Code:

Name    [00000004] Intel(R) Dual Band Wireless-AC 7260
Adapter Type    Ethernet 802.3
Product Type    Intel(R) Dual Band Wireless-AC 7260
Installed    Yes
PNP Device ID    PCI\VEN_8086&DEV_08B1&SUBSYS_C0708086&REV_BB\4&33C74B69&0&00E2
Last Reset    2/21/2018 2:44 PM
Index    4
Service Name    NETwNb64
IP Address    192.168.10.52
IP Subnet    255.255.254.0
Default IP Gateway    192.168.10.1
DHCP Enabled    Yes
DHCP Server    192.168.254.200
DHCP Lease Expires    12/31/1969 11:02 PM
DHCP Lease Obtained    12/31/1969 7:02 PM
MAC Address    ‪A4:C4:94:DB:33:FF‬
Memory Address    0xED200000-0xED2FFFFF
IRQ Channel    IRQ 4294967292
Driver    c:\windows\system32\drivers\netwbw02.sys (18.33.5.1, 3.36 MB (3,525,896 bytes), 11/9/2016 10:15 PM)

Please run those two setups to update you Intel drivers:

https://downloadmirror.intel.com/274...et64_Win10.exe

https://downloadmirror.intel.com/274...0_64_Win10.exe

Upgraded both drivers but am now getting a crash with no bluescreen. This is the same chasing I did earlier with the video card. Do have the new dump file below. Thank you for your previous help.

Will check tommorow morning

Did u run memtest in the correct version for minimum 8 passes?

But its surely something with the adhoc connection:

Code:

0x00000133:    [SPECIAL] DPC_WATCHDOG_VIOLATION (2018-02-22 18:37:37) [Windows 10] 
 
CAUSED BY:     Netwbw02.sys [2017-10-31] * Intel® Wireless WiFi Link Driver - Intel® Wireless WiFi Link Adapter * => https://downloadcenter.intel.com/default.aspx  
               nvlddmkm.sys [2018-01-23] * nVidia Video drivers * => http://www.nvidia.com/Download/index.aspx  
 
PROCESS:       System

In eventlog u can see following:

At 11:35:37 theres an warning the network driver is beginning to reset

Code:

Event[11130]:
  Log Name: System
  Source: Microsoft-Windows-NDIS
  Date: 2018-02-22T11:35:37.638
  Event ID: 10400
  Task: N/A
  Level: Warning
  Opcode: Info
  Keyword: N/A
  User: N/A
  User Name: N/A
  Computer: Yodasdaddy13
  Description: 
The network interface "Intel(R) Dual Band Wireless-AC 7260" has begun resetting.  There will be a momentary disruption in network connectivity while the hardware resets. Reason: The network driver requested that it be reset. This network interface has reset 3 time(s) since it was last initialized.

After this theres is an message which is shown up 50 times in a row something with the network adapter/driver:

Code:

Event[11131]:
  Log Name: System
  Source: NETwNb64
  Date: 2018-02-22T11:35:37.638
  Event ID: 5010
  Task: N/A
  Level: Information
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Yodasdaddy13
  Description: 
N/A


Event[11132]:
  Log Name: System
  Source: NETwNb64
  Date: 2018-02-22T11:35:37.638
  Event ID: 5010
  Task: N/A
  Level: Information
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Yodasdaddy13
  Description: 
N/A


Event[11133]:
  Log Name: System
  Source: NETwNb64
  Date: 2018-02-22T11:35:37.638
  Event ID: 5010
  Task: N/A
  Level: Information
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Yodasdaddy13
  Description: 
N/A


Event[11134]:
  Log Name: System
  Source: NETwNb64
  Date: 2018-02-22T11:35:37.972
  Event ID: 5000
  Task: N/A
  Level: Information
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Yodasdaddy13
  Description: 
N/A


Event[11135]:
  Log Name: System
  Source: NETwNb64
  Date: 2018-02-22T11:35:37.972
  Event ID: 5002
  Task: N/A
  Level: Information
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Yodasdaddy13
  Description: 
N/A


Event[11136]:
  Log Name: System
  Source: NETwNb64
  Date: 2018-02-22T11:35:37.972
  Event ID: 5002
  Task: N/A
  Level: Information
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Yodasdaddy13
  Description: 
N/A


Event[11137]:
  Log Name: System
  Source: NETwNb64
  Date: 2018-02-22T11:35:37.972
  Event ID: 5002
  Task: N/A
  Level: Information
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Yodasdaddy13
  Description: 
N/A


Event[11138]:
  Log Name: System
  Source: NETwNb64
  Date: 2018-02-22T11:35:37.972
  Event ID: 5002
  Task: N/A
  Level: Information
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Yodasdaddy13
  Description: 
N/A


Event[11139]:
  Log Name: System
  Source: NETwNb64
  Date: 2018-02-22T11:35:37.972
  Event ID: 5002
  Task: N/A
  Level: Information
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Yodasdaddy13
  Description: 
N/A


Event[11140]:
  Log Name: System
  Source: NETwNb64
  Date: 2018-02-22T11:35:37.972
  Event ID: 5002
  Task: N/A
  Level: Information
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Yodasdaddy13
  Description: 
N/A


Event[11141]:
  Log Name: System
  Source: NETwNb64
  Date: 2018-02-22T11:35:37.972
  Event ID: 5002
  Task: N/A
  Level: Information
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Yodasdaddy13
  Description: 
N/A


Event[11142]:
  Log Name: System
  Source: NETwNb64
  Date: 2018-02-22T11:35:37.972
  Event ID: 5002
  Task: N/A
  Level: Information
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Yodasdaddy13
  Description: 
N/A


Event[11143]:
  Log Name: System
  Source: NETwNb64
  Date: 2018-02-22T11:35:37.972
  Event ID: 5002
  Task: N/A
  Level: Information
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Yodasdaddy13
  Description: 
N/A


Event[11144]:
  Log Name: System
  Source: NETwNb64
  Date: 2018-02-22T11:35:37.972
  Event ID: 5002
  Task: N/A
  Level: Information
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Yodasdaddy13
  Description: 
N/A


Event[11145]:
  Log Name: System
  Source: NETwNb64
  Date: 2018-02-22T11:35:37.972
  Event ID: 5002
  Task: N/A
  Level: Information
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Yodasdaddy13
  Description: 
N/A


Event[11146]:
  Log Name: System
  Source: NETwNb64
  Date: 2018-02-22T11:35:37.972
  Event ID: 5002
  Task: N/A
  Level: Information
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Yodasdaddy13
  Description: 
N/A


Event[11147]:
  Log Name: System
  Source: NETwNb64
  Date: 2018-02-22T11:35:37.972
  Event ID: 5002
  Task: N/A
  Level: Information
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Yodasdaddy13
  Description: 
N/A


Event[11148]:
  Log Name: System
  Source: NETwNb64
  Date: 2018-02-22T11:35:37.972
  Event ID: 5002
  Task: N/A
  Level: Information
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Yodasdaddy13
  Description: 
N/A


Event[11149]:
  Log Name: System
  Source: NETwNb64
  Date: 2018-02-22T11:35:37.972
  Event ID: 5002
  Task: N/A
  Level: Information
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Yodasdaddy13
  Description: 
N/A


Event[11150]:
  Log Name: System
  Source: NETwNb64
  Date: 2018-02-22T11:35:37.972
  Event ID: 5002
  Task: N/A
  Level: Information
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Yodasdaddy13
  Description: 
N/A


Event[11151]:
  Log Name: System
  Source: NETwNb64
  Date: 2018-02-22T11:35:37.972
  Event ID: 5002
  Task: N/A
  Level: Information
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Yodasdaddy13
  Description: 
N/A


Event[11152]:
  Log Name: System
  Source: NETwNb64
  Date: 2018-02-22T11:35:37.972
  Event ID: 5002
  Task: N/A
  Level: Information
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Yodasdaddy13
  Description: 
N/A


Event[11153]:
  Log Name: System
  Source: NETwNb64
  Date: 2018-02-22T11:35:37.972
  Event ID: 5002
  Task: N/A
  Level: Information
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Yodasdaddy13
  Description: 
N/A


Event[11154]:
  Log Name: System
  Source: NETwNb64
  Date: 2018-02-22T11:35:37.972
  Event ID: 5002
  Task: N/A
  Level: Information
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Yodasdaddy13
  Description: 
N/A


Event[11155]:
  Log Name: System
  Source: NETwNb64
  Date: 2018-02-22T11:35:37.972
  Event ID: 5002
  Task: N/A
  Level: Information
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Yodasdaddy13
  Description: 
N/A


Event[11156]:
  Log Name: System
  Source: NETwNb64
  Date: 2018-02-22T11:35:37.972
  Event ID: 5002
  Task: N/A
  Level: Information
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Yodasdaddy13
  Description: 
N/A


Event[11157]:
  Log Name: System
  Source: NETwNb64
  Date: 2018-02-22T11:35:37.972
  Event ID: 5002
  Task: N/A
  Level: Information
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Yodasdaddy13
  Description: 
N/A


Event[11158]:
  Log Name: System
  Source: NETwNb64
  Date: 2018-02-22T11:35:37.972
  Event ID: 5002
  Task: N/A
  Level: Information
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Yodasdaddy13
  Description: 
N/A


Event[11159]:
  Log Name: System
  Source: NETwNb64
  Date: 2018-02-22T11:35:37.972
  Event ID: 5002
  Task: N/A
  Level: Information
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Yodasdaddy13
  Description: 
N/A


Event[11160]:
  Log Name: System
  Source: NETwNb64
  Date: 2018-02-22T11:35:37.972
  Event ID: 5002
  Task: N/A
  Level: Information
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Yodasdaddy13
  Description: 
N/A


Event[11161]:
  Log Name: System
  Source: NETwNb64
  Date: 2018-02-22T11:35:37.972
  Event ID: 5002
  Task: N/A
  Level: Information
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Yodasdaddy13
  Description: 
N/A


Event[11162]:
  Log Name: System
  Source: NETwNb64
  Date: 2018-02-22T11:35:37.972
  Event ID: 5002
  Task: N/A
  Level: Information
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Yodasdaddy13
  Description: 
N/A


Event[11163]:
  Log Name: System
  Source: NETwNb64
  Date: 2018-02-22T11:35:37.972
  Event ID: 5002
  Task: N/A
  Level: Information
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Yodasdaddy13
  Description: 
N/A


Event[11164]:
  Log Name: System
  Source: NETwNb64
  Date: 2018-02-22T11:35:37.972
  Event ID: 5002
  Task: N/A
  Level: Information
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Yodasdaddy13
  Description: 
N/A


Event[11165]:
  Log Name: System
  Source: NETwNb64
  Date: 2018-02-22T11:35:37.972
  Event ID: 5002
  Task: N/A
  Level: Information
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Yodasdaddy13
  Description: 
N/A


Event[11166]:
  Log Name: System
  Source: NETwNb64
  Date: 2018-02-22T11:35:37.972
  Event ID: 5002
  Task: N/A
  Level: Information
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Yodasdaddy13
  Description: 
N/A


Event[11167]:
  Log Name: System
  Source: NETwNb64
  Date: 2018-02-22T11:35:37.972
  Event ID: 5002
  Task: N/A
  Level: Information
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Yodasdaddy13
  Description: 
N/A


Event[11168]:
  Log Name: System
  Source: NETwNb64
  Date: 2018-02-22T11:35:37.972
  Event ID: 5002
  Task: N/A
  Level: Information
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Yodasdaddy13
  Description: 
N/A


Event[11169]:
  Log Name: System
  Source: NETwNb64
  Date: 2018-02-22T11:35:37.972
  Event ID: 5002
  Task: N/A
  Level: Information
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Yodasdaddy13
  Description: 
N/A


Event[11170]:
  Log Name: System
  Source: NETwNb64
  Date: 2018-02-22T11:35:37.972
  Event ID: 5002
  Task: N/A
  Level: Information
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Yodasdaddy13
  Description: 
N/A


Event[11171]:
  Log Name: System
  Source: NETwNb64
  Date: 2018-02-22T11:35:37.972
  Event ID: 5002
  Task: N/A
  Level: Information
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Yodasdaddy13
  Description: 
N/A


Event[11172]:
  Log Name: System
  Source: NETwNb64
  Date: 2018-02-22T11:35:37.972
  Event ID: 5002
  Task: N/A
  Level: Information
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Yodasdaddy13
  Description: 
N/A


Event[11173]:
  Log Name: System
  Source: NETwNb64
  Date: 2018-02-22T11:35:37.972
  Event ID: 5002
  Task: N/A
  Level: Information
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Yodasdaddy13
  Description: 
N/A


Event[11174]:
  Log Name: System
  Source: NETwNb64
  Date: 2018-02-22T11:35:37.972
  Event ID: 5002
  Task: N/A
  Level: Information
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Yodasdaddy13
  Description: 
N/A


Event[11175]:
  Log Name: System
  Source: NETwNb64
  Date: 2018-02-22T11:35:37.972
  Event ID: 5002
  Task: N/A
  Level: Information
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Yodasdaddy13
  Description: 
N/A


Event[11176]:
  Log Name: System
  Source: NETwNb64
  Date: 2018-02-22T11:35:37.972
  Event ID: 5002
  Task: N/A
  Level: Information
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Yodasdaddy13
  Description: 
N/A


Event[11177]:
  Log Name: System
  Source: NETwNb64
  Date: 2018-02-22T11:35:37.972
  Event ID: 5002
  Task: N/A
  Level: Information
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Yodasdaddy13
  Description: 
N/A

But as u can see theres also the nvidia driver shown up. U should reinstall it using DDU:

Display Driver Uninstaller: How to use Display Driver Uninstaller (DDU) is a small software that can help the user to uninstall the display driver from the users PC. It can uninstall the driver for all the lead display chip developers, viz. Nvidia, AMD and Intel.

Can you provide us with the kernel memory dump please? Its located in C:\Windows\MEMORY.DMP.
You can upload it to an cloud service like dropbox or onedrive.

1) Please increase the free space in drive C: so that there is 30 GB or more free space.

Drive: C:
Free Space: 16.5 GB
Total Space: 121.3 GB
File System: NTFS
Model: SanDisk SD7SB3Q128G1002

Code:

Event[11244]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2018-02-22T11:41:02.463
  Event ID: 1018
  Task: N/A
  Level: Information
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Yodasdaddy13
  Description: 
The dump file at location: C:\WINDOWS\MEMORY.DMP was deleted because the disk volume had less than 25 GB free space.

Well, i cleared out enough space to capture a dump file but haven't crashed since doing so. Will continue to observe and report findings tomorrow if unchanged.

Well, since the storage has been freed up i've had two system hang-ups. Neither have created a bluescreen and neither have created a minidump. I have searched the event viewer but don't see anything that is presenting a stop error except where i have to power cycle the machine. Any ideas where to look?

Please upload a new log collector log