BSOD sometime during sleep, Ntoskrnl seems to be at fault

kevdlandrig · 16 Aug 2013

I already checked the other threads for my specific problem, and I couldn't find it although I spent several hours looking for the problem on the interwebz.

I've been putting my computer to sleep, go to bed, and when I wake up, I often find that the computer has BSOD'd sometime during the night. I have never actually seen the BSOD happen. From what I have seen of other people's problems with this, people typically have a bad hard drive or memory issues. This is not the case for me. I have already run several hard disk checks with WD's software, and I ran memtest overnight. neither returned a single error. I thought there might be an issue with the computer switching from sleep mode to hibernate, so I changed the delay between going to sleep and switching to hibernate to about three days. The issue persists. At this point I seem to have exhausted the knowledge of the forums so I am attaching my SF diagnostic.

If you need any more information I would be happy to oblige.

Dsprague · 16 Aug 2013

It looks like your problem is being caused by your wireless driver:

Code:

Unable to load image \SystemRoot\system32\DRIVERS\NETwNs64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for NETwNs64.sys
*** ERROR: Module load completed but symbols could not be loaded for NETwNs64.sys
 \Driver\NETwNs64

Please update the driver from here: https://downloadcenter.intel.com/Default.aspx

kevdlandrig · 16 Aug 2013

Alrighty, I've installed the driver, and I will advise you on the situation in a few weeks(or sooner if the problem reoccurs). Just wondering though, why was bluescreenview pointing to ntoskrnl if the problem was really somewhere else? Did I miss something?

Dsprague · 16 Aug 2013

In all likely hood yes, ntoskrnl is the core of the operating system, and often times what happens is a driver (in this case your wireless driver) will do something it shouldn't and the core (ntoskrnl) will detect this and force a crash (bluescreen) to save its self and other very important files from possible corruption by the bad data. you have to understand too that debugging a BSOD is something that requires a good understanding of various components of the opreating system, how they work, and a properly configured copy of the windbg debugging program if you want more information see these threads, they are very helpful: Crash and lockup debug 'How To' - Windows 7 Help Forums

kevdlandrig · 18 Aug 2013

The bluescreen happened again last night. I looked at bluescreenview, which pointed to ntoskrnl again, so I think that it is safe to assume that the cause is some residual of the old wireless drivers. I am going to attempt to completely uninstall the wireless driver and any parts of it I can find tomorrow morning if no one stops me. Any advice on the process? I'm also attaching the new dump for analysis in case that is not the issue.

Dsprague · 20 Aug 2013

It does appear that it is your wireless drivers once again,though the driver, at least according to the dump files, is up to date. let me see if I can get some one else to take a look at this.

x BlueRobot · 20 Aug 2013

Code:

0: kd> lmvm b57nd60a
start             end                 module name
fffff880`04732000 fffff880`04799000   b57nd60a T (no symbols)           
    Loaded symbol image file: b57nd60a.sys
    Image path: \SystemRoot\system32\DRIVERS\b57nd60a.sys
    Image name: b57nd60a.sys
    Timestamp:        Tue Feb 15 03:58:31 2011 (4D59F9E7)
    CheckSum:         00072A2A
    ImageSize:        00067000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Your Broadcom NetXtreme Gigabit Ethernet driver seems to be causing problems, please update the driver from here - Ethernet NIC Driver Downloads | Broadcom

kevdlandrig · 20 Aug 2013

I updated the Broadcom adapter, and then had an unrelated breakthrough. If I press the power button to sleep the computer, and then immediately close the lid, the computer has the screen off, but will react (as in beep or something) when I press the WiFi switch or plug in the power. The computer will otherwise act like it is frozen. About fifteen minutes later, the computer will bluescreen. (I finally saw it last night because I opened the lid again when I saw it was acting funny)

One other thing. I noticed that my computer came with a Bluetooth module, but I can't seem to detect it on the hardware level. Could this be somehow related? Im attaching yet another dump of the most recent two bluescreens as well.

EDIT/UPDATE My computer is now bluescreening on every sleep, so I decided to run verifier.exe I selected 'create standard settings' and 'automatically select all drivers installed on this computer'. I promptly got a bluescreen upon restarting. Here is the newest grab all.

x BlueRobot · 21 Aug 2013

Scan for any missing, modified or corrupted protected Windows files with:

SFC /SCANNOW Command - System File Checker

Follow these instructions, enabling Driver Verifier on all drivers will cause unreliable crashes, also please enable the Special Pool option:

Run Driver Verifier to scan for any corrupted drivers which may be causing problems, this program works by running various stress tests on drivers, in order to produce a BSOD which will locate the driver; run for least 24 hours:

Driver Verifier - Enable and Disable

Information

Additional Help - Using Driver Verifier to identify issues with Drivers

kevdlandrig · 24 Aug 2013

Ive been running the verifier for a few days now, but I haven't bluescreened because of it. The verifier is currently set to not check the microsoft stuff. should I be looking at that two?