Random freezes and/or BSOD with general use

If you already have had BSODs, then you must already have some dumps. Check the Minidump folder under your Windows folder. If you don't have your BSOD settings to create a Minidump, then open Computer, right click and select properties. From there, click on Advanced system settings and under the Starup and Recovery section, click on settings. Under the writing debugging information section, select Small memory dump (256 KB) and click OK. Also, if you have another computer and a USB drive, download the SF Diagnostic Tool from this link SF Diagnostic Tool - Using for Troubleshooting and put it on the USB. Start the problem computer in Safe mode and insert the USB in the problem computer and right click the application and click Run as Administrator and follow the steps given in the link. Get the files generated by the tool on the USB and upload it here with the other computer. This will give you a bit time before your computer freezes again. Some BSODs are software related but it is hard to know if it really is or not without having the dumps.

Okay I do have a dmp file from a blue screen that just occurred a few minutes ago but it was when Kernel memory dump was selected - I just now changed it to Small memory dump (256 KB). I can provide you with that if that helps. I do have two other PCs will download SF Diagnostics tool now, run that and provide you with the files.

P.S. I am currently on my laptop and all is well but this is normal as it locks up or BSOD at very random times.

EDIT: I ran SF Diagnostic tool and it did not create a folder on my desktop. I know it says in instructions that if it isn't creating a file then the default locations in the registry is messed up but I don't see how.

I do see in my C:/Windows msinfo32 MEMORY.DMP and ntbtlog files that were created when I originally ran the diagnostic tool.

EDIT 2: I used the DM log collector way to get you what you need - attached is zip file.

Because the dumps show the cause to be NETwNs64.sys and the BugCheckCode is 0xDEADDEAD, it is kind of hard to understand what is really causing your error. Our best shot might be running memtest86+ and Driver Verifier.

Test your RAM modules for possible errors.
RAM - Test with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

If it does not show any error, enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

Information:
Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

Warning:
Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using http://www.piriform.com/ccleaner looking at Tools > System Restore.

If there is no points, System Restore Point - Create before enabling DV.

Tip:

If you fail to get on the Desktop because of DV, Advanced Boot Options > Safe Mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
If you cannot boot in Safe Mode too, do a System Restore to a point you made earlier.

It may be the network driver but you can do a memtest86+ anyway and run Driver Verifer thereafter. I'd get a BSOD professional if you want because this is the first time I am helping someone with their BSOD issues. You know, experience comes with practice

It is your Intel WiFi driver:

Code:

*** WARNING: Unable to verify timestamp for NETwNs64.sys
*** ERROR: Module load completed but symbols could not be loaded for NETwNs64.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck DEADDEAD, {f00004b, 125025b, 12a622ce, 36a8005e}

Probably caused by : NETwNs64.sys ( NETwNs64+3c0d2 )

Followup: MachineOwner

It's pretty old and needs updating.

Code:

0: kd> lmvm NETwNs64
start             end                 module name
fffff880`05a67000 fffff880`0659d000   NETwNs64 T (no symbols)           
    Loaded symbol image file: NETwNs64.sys
    Image path: \SystemRoot\system32\DRIVERS\NETwNs64.sys
    Image name: NETwNs64.sys
    Timestamp:        Fri Dec 02 06:50:55 2011 (4ED8754F)
    CheckSum:         00AE9BA3
    ImageSize:        00B36000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Check the Alienware site for an updated version.

Leave it overnight. It will do its job. If it find errors with any one of the RAM sticks, then take them all out except one and run memtest separately on each for 8 passes.

aritra2116 said:

Leave it overnight. It will do its job. If it find errors with any one of the RAM sticks, then take them all out except one and run memtest separately on each for 8 passes.

10 passes, no issues. Going to run DV now and will report back.

EDIT: Within minutes of running DV... no BSOD but a random "freeze" where I was forced to hard reboot. Rebooted and DV still running. I'd imagine no dump was created from this random freeze?

EDIT 2: After the random lock up I had two BSODs occur in a matter of an hour. Should I use DM Log Collector to get you the information you require? SF Diagnostic Tool does not create the file after the process is complete.

EDIT 3: I went ahead and got you the zip of the dump files through DM Log Collector as I am assuming you'll need this. Attached.