BSoD - BcCode: Deaddead

Question

Hi there,

In the last few weeks I've been experiencing issues and regularly encountering the Deaddead BSoD.

Typically, the events leading up to it are as follows.

WiFi loses internet connection but remains connected to network. 

Troubleshooter then tries to fix it leading to BSoD.

After a few restarts and attempts at troubleshooting it establishes that the WiFi adapter is disabled and will either fix it or BSoD again.

For some reason I am struggling to figure out how to get the details it gives you after the unexpected shutdown, but all the minidumps created can be downloaded as a .rar file from onedrive here, including sysinfo:

https://1drv.ms/u/s!AuUE15QuVJEIgR3IxkAHeT7iGZpb

I have not recently installed any new software or hardware.

Running windows 7 64bit on a Toshiba Satellite p850-12z

Malwarebytes scan showed nothing, nor did Microsoft Security essentials.

All help is gratefully received, if you need more information I will gladly provide it.

Thank you in advance!

Answer 1

MANUALLY_INITIATED_CRASH1 (deaddead)

The user manually initiated this crash dump.

Arguments:

Arg1: 000000000f000101

Arg2: 000000000125025b

Arg3: 0000000012a70000

Arg4: 0000000000000000

Debugging Details:

*** WARNING: Unable to verify timestamp for NETwNs64.sys

*** ERROR: Module load completed but symbols could not be loaded for NETwNs64.sys

fffff8800b01d000 fffff8800bb53000   NETwNs64 T (no symbols)          

    Loaded symbol image file: NETwNs64.sys

    Image path: \SystemRoot\system32\DRIVERS\NETwNs64.sys

    Image name: NETwNs64.sys

    Browse all global symbols  functions  data

    Timestamp:        Mon Jan  9 04:44:39 2012 (4F0AB707)

 NETwNs64.sys is a driver that belongs to your Intel(R) Wireless WiFi Link 5000 Series Adapter Driver for Windows 7

As you can see, the driver is four yrs old and needs updating.

Check the link below for a newer version.

Drivers & Software.

http://support.toshiba.com/drivers

Note: IF the crashing persists after the driver update, uninstall McAfee, and try another AV, preferably, MSE ( Microsoft Security Essentials)

edit: Running MSE, McAfee alongside each other was your problem. The were conflicting. Like I said, remove McAfee, using the tool linked below, so you are sure, there are no leftover files.

How to uninstall McAfee Windows security software using the Consumer Products Removal tool.

https://service.mcafee.com/webcenter/portal/cp/home/articleview;jsessionid=3Alocai999Ogl6o93WI1z_nD7TJyYZW_N0i6MM8y8s3ussKA3fpI!-5810101!465567595?articleId=TS101331&_afrLoop=5692927301329296#!%40%40%3F_afrLoop%3D5692927301329296%26articleId%3DTS101331%26centerWidth%3D100%2525%26leftWidth%3D0%2525%26rightWidth%3D0%2525%26showFooter%3Dfalse%26showHeader%3Dfalse%26_adf.ctrl-state%3D8agehhote_4

Download the MCPR tool from http://us.mcafee.com/apps/supporttools/mcpr/mcpr.asp

Answer 2

You are welcome.

Answer 3

Thank you very much for taking the time to reply!

Driver has been updated, McAfee removed. Had no idea it still had a presence on my computer - uninstalling it was the very first thing I did.

I will see how things go and will report back if problem is fixed!

Thanks!