Random freezes and/or BSOD with general use

[cwburns32]

Hello all,

It's been a while since I've posted here but just recently my Alienware m14x R2 has started randomly locking up completely to the point where I have to do a hard shut down. This happens at sporadic times - sometimes it will just power up and it will happen 2 minutes in to use and other times it might happen 40 minutes later. When using the laptop in safe mode it never happens which leads me to believe it is software related - fingers crossed though as a new mobo on these puppies is like upwards of +$500.

I have already performed a few different restores and even used AlienRespawn to bring me back to factory stock but the issue still persists which makes my software issue theory a little less likely.

I know I have to follow the BSOD crash instructions for this but those don't occur hardly as often as the random lock ups - also BSOD are hard to replicate as I have no idea what sets it off.

Any help or suggestions would be great.

 

[aritra2116]

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 http://www.sevenforums.com/tutorials/92394-sf-diagnostic-tool-using-troubleshooting.html 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.

 

[cwburns32]

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.

 

[aritra2116]

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.
http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html
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.
http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html
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, http://www.sevenforums.com/tutorials/697-system-restore-point-create.html before enabling DV.

Tip:

If you fail to get on the Desktop because of DV, http://www.sevenforums.com/tutorials/666-advanced-boot-options.html > http://www.sevenforums.com/tutorials/69585-safe-mode.html. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
If you cannot boot in http://www.sevenforums.com/tutorials/69585-safe-mode.html too, do a http://www.sevenforums.com/tutorials/700-system-restore.html to a point you made earlier.

 

[cwburns32]

I will do all this when I get off of work. I have a few PCs so I can run the Men tests right away and let it go through 8 passes like you mentioned. I thought that error had to do with WiFi adapter... I could be wrong but when I did a little hunting it appeared to be my WiFi adapter. Updated that driver as it was way out of date but will still run tests like you mentioned above and get back to you.

 

[aritra2116]

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

 

[Boozad]

It is your Intel WiFi driver:

*** 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 : [B][COLOR=Red]NETwNs64.sys[/COLOR][/B] ( NETwNs64+3c0d2 )

Followup: MachineOwner

It's pretty old and needs updating.

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:        [B][COLOR=Red]Fri Dec 02 06:50:55 2011[/COLOR][/B] (4ED8754F)
    CheckSum:         00AE9BA3
    ImageSize:        00B36000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Check the Alienware site for an updated version.

 

[cwburns32]

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

I will run the tests and report back - just got home from work.

It is your Intel WiFi driver:

*** 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 : [B][COLOR=Red]NETwNs64.sys[/COLOR][/B] ( NETwNs64+3c0d2 )

Followup: MachineOwner

It's pretty old and needs updating.

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:        [B][COLOR=Red]Fri Dec 02 06:50:55 2011[/COLOR][/B] (4ED8754F)
    CheckSum:         00AE9BA3
    ImageSize:        00B36000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Check the Alienware site for an updated version.

Just updated the driver yesterday evening and no BSOD or random reboots just yet. Going to run the test that aritra suggested just in case though.

EDIT: And literally seconds after I typed this my laptop locked up on me and I was forced to hard reboot.

EDIT 2: Memtest is up and running will report back after 8 passes or when an error occurs.

 

[aritra2116]

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.

 

[cwburns32]

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.

 

[aritra2116]

Good. We got some dumps indicating Avast Antivirus. Uninstall it using this tool.

Avast Software Uninstall Utility Download

And replace it with Microsoft Security Essentials and Malwarebytes Free (optional but very useful).

Microsoft Security Essentials - Microsoft Windows

Malwarebytes | Free Anti-Malware & Internet Security Software

Post back with more DV results if it freezes again.

 

[cwburns32]

Good. We got some dumps indicating Avast Antivirus. Uninstall it using this tool.

Avast Software Uninstall Utility Download

And replace it with Microsoft Security Essentials and Malwarebytes Free (optional but very useful).

Microsoft Security Essentials - Microsoft Windows

Malwarebytes | Free Anti-Malware & Internet Security Software

Post back with more DV results if it freezes again.

I have had 3 random freezes (not BSODs) occur since running DV after removing Avast and installing MSE - DV still running now, no freezes in a few hours now. I can pull the logs but don't they only dump on BSODs?

 

[aritra2116]

I think you should wait for another BSOD before putting the logs up. And also, could you publish a screenshot of a Speccy summary report? You can download it from piriform.com

 

[cwburns32]

I think you should wait for another BSOD before putting the logs up. And also, could you publish a screenshot of a Speccy summary report? You can download it from piriform.com

Been running DV for 16 hours now - 4 random freezes, no BSOD. I am uploading a DM log collector file I ran after the lockups - no dumps pulled but I don't know if there is any useful information in the rest of those files so I am uploading it anyway. Also attached is a capture of my Speccy summary report.

 

[aritra2116]

I'm busy with some work right now so I hope someone else catches up with this thread. Also, try running /sfc scannow command in Safe mode with command prompt.

 

[cwburns32]

I'm busy with some work right now so I hope someone else catches up with this thread. Also, try running /sfc scannow command in Safe mode with command prompt.

I understand that you are busy. I appreciate the help thus far. I did sfc /scannow in Safe Mode and I intended on uploading the CBS file, however, I was denied access to file when I was trying to view it on my OS - I am running as an administrator so I don't see why I'd be denied access. Hopefully someone else can chime in and help out.

I don't have any information on this laptop and nothing that I have to backup. I do have the Windows 7 Alienware Disc and the Alienware Resource DVD. I could just partition the drives and reinstall from scratch and hope the problem goes away and if it doesn't then I would assume it's hardware related $$$$$$$$ - I could be wrong on this but am unsure.

EDIT: I opened the file in notepad through an elevated cmd and then saved it to the desktop to remove the access restriction. Now the txt file is too big to upload to here. Will upload to dropbox and share here shortly.

https://www.dropbox.com/s/nerw3tvz7m30yir/CBS Log.txt

 

[aritra2116]

Hmm, what did the SFC scan say? Did it say that it found errors and fixed them/could not fix some of them or does it say that it found no integrity violations?

 

[cwburns32]

Hmm, what did the SFC scan say? Did it say that it found errors and fixed them/could not fix some of them or does it say that it found no integrity violations?

SFC said found corrupt files but could not fix all of them - more details can be found in the CBS log file. That's exactly what it said upon completion.

 

[aritra2116]

Ok, so if it has to do with system files, then I guess repair install is the best thing to do but before that, have you done malware scans recently? If yes, then do a Custom Scan with Malwarebytes and select all the drives. If it finds anything, quarantine it and post the log it makes. After that, do this.

http://www.sevenforums.com/tutorials/3413-repair-install.html

 

[NoelDP]

There is NO obvious need for a repair install - or worse, a clean install.

The SFC scan showed the following problem...

2014-07-21 11:37:53, Info                  CSI    00000304 [SR] Repairing 1 components
2014-07-21 11:37:53, Info                  CSI    00000305 [SR] Beginning Verify and Repair transaction
2014-07-21 11:37:53, Info                  CSI    00000306 Manifest hash for component [ml:280{140},l:184{92}]"amd64_a69ab2e06a57e0c36f0741338d888e44_31bf3856ad364e35_7.1.7601.18351_none_168d02fc611e1de8" does not match expected value. 
 Expected:{l:32 b:8571f9bcf4e096687cf1401f625f0e93afa381a54da316375ed2fad5290781ae}
 Found:{l:32 b:1c56c84448dec77bece6d3d7b129c32479b966d5d0d2187e52f63778750cda4e}.
2014-07-21 11:37:53, Info                  CSI    00000307 Unable to load manifest for component [ml:280{140},l:184{92}]"amd64_a69ab2e06a57e0c36f0741338d888e44_31bf3856ad364e35_7.1.7601.18351_none_168d02fc611e1de8"
2014-07-21 11:37:53, Info                  CSI    00000308 [SR] Cannot verify component files for a69ab2e06a57e0c36f0741338d888e44, Version = 7.1.7601.18351, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (TRUE)
2014-07-21 11:37:53, Info                  CSI    00000309 Repair results created:
POQ 129 starts:
 
POQ 129 ends.
2014-07-21 11:37:53, Info                  CSI    0000030a [SR] Repair complete
2014-07-21 11:37:53, Info                  CSI    0000030b [SR] Committing transaction

This may be the tip of the iceberg -


Please download and save the CheckSUR tool from http://support.microsoft.com/kb/947821
(you'll need to look in the details for Windows 7, downloading from the Microsoft Download Center)

Run it - The tool can take anywhere from 5 mins to a couple of hours to run (or 'Install') depending on how much it has to do, and may exit silently - it may appear to freeze for most of that time, but be patient.
The result is logged in the C:\Windows\Logs\CBS\CheckSUR.log file - and an archive …\checksur.persist.log file

Then zip the CheckSUR.log and upload it to your reply.