Dell laptop with Windows 7 won’t enter standby, hibernate, sleep, crashes with BSOD after screen has turned off

In case anyone else encounters this particular issue….

In January/early February 2015 my Dell laptop suddenly stopped going into standby. The screen turned off, but the machine didn’t go to sleep for a long time. Usually I forced a shutdown with the power button.

It took quite a while before I got around to debugging this, but a few days ago I did, and it appears that the problem was a very old Intel Wifi driver -specifically for the Centrino 6205 Advanced-N module. The driver being used was dated 21.12.2010 (version 14.0.1.2). I don’t know how this driver came to be used, but when I downloaded and installed the most recent driver package for the 6205 from Intel (version 17.14.0), I still wound up with the same driver.
The solution for me was to download a driver package from last year – version 15.13.0.2 (driver date 22.07.2014). Now sleep works again.

I don’t know how this happened – perhaps an installation failure with the most recent drivers caused Windows to default back to using original drivers for the chipset?

In any event – I debugged this through getting BSOD info in event viewer and dump files, and used WinDbg to open the dump files. I then googled for keywords, notably for the “probably caused by NETwNs64.sys” driver.

Cheers,

Are

 

And here’s the dump file:

Microsoft (R) Windows Debugger Version 6.3.9600.17237 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\Minidump32715-15132-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`04b64c32?
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`0426d022?
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`00b9a3c0?

************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.22943.amd64fre.win7sp1_ldr.150126-1511
Machine Name:
Kernel base = 0xfffff800`03056000 PsLoadedModuleList = 0xfffff800`03299890
Debug session time: Thu Mar 26 16:26:17.591 2015 (UTC + 1:00)
System Uptime: 0 days 5:31:23.299
Loading Kernel Symbols
………………………………………………………
……………………………………………………….
…….Unable to load image Unknown_Module_00000000`00000000, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Unable to add module at 00000000`00000000

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

Loading User Symbols
Loading unloaded module list
…………………
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa8006b81060, fffff80000b9a3d8, fffffa800e62cbd0}

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

Followup: MachineOwner
———

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa8006b81060, Physical Device Object of the stack
Arg3: fffff80000b9a3d8, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: fffffa800e62cbd0, The blocked IRP

Debugging Details:
——————

DRVPOWERSTATE_SUBCODE: 3

IRP_ADDRESS: fffffa800e62cbd0

DEVICE_OBJECT: fffffa8008243050

DRIVER_OBJECT: fffffa800864c060

IMAGE_NAME: NETwNs64.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4d10df1b

MODULE_NAME: NETwNs64

FAULTING_MODULE: fffff880058a4000 NETwNs64

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

BUGCHECK_STR: 0x9F

PROCESS_NAME: System

CURRENT_IRQL: 2

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre

DPC_STACK_BASE: FFFFF80000BA0FB0

STACK_TEXT:
fffff800`00b9a388 fffff800`0313a8e2 : 00000000`0000009f 00000000`00000003 fffffa80`06b81060 fffff800`00b9a3d8 : nt!KeBugCheckEx
fffff800`00b9a390 fffff800`030d4b3c : fffff800`00b9a4c0 fffff800`00b9a4c0 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string’+0x336b0
fffff800`00b9a430 fffff800`030d49d6 : fffffa80`0e67e588 fffffa80`0e67e588 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`00b9a4a0 fffff800`030d48be : 0000002e`4b5ebc4c fffff800`00b9ab18 00000000`001372c2 fffff800`0324aac8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9aaf0 fffff800`030d46a7 : 0000000c`a17a7fc2 0000000c`001372c2 0000000c`a17a7f52 00000000`000000c2 : nt!KiTimerExpiration+0x1be
fffff800`00b9ab90 fffff800`030c1b8a : fffff800`03246e80 fffff800`03254cc0 00000000`00000002 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9ac40 00000000`00000000 : fffff800`00b9b000 fffff800`00b95000 fffff800`00b9ac00 00000000`00000000 : nt!KiIdleLoop+0x5a

STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

FAILURE_BUCKET_ID: X64_0x9F_3_POWER_DOWN_IMAGE_NETwNs64.sys

BUCKET_ID: X64_0x9F_3_POWER_DOWN_IMAGE_NETwNs64.sys

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:x64_0x9f_3_power_down_image_netwns64.sys

FAILURE_ID_HASH: {1414b9aa-01f9-e8c4-5871-cad7a5477240}

Followup: MachineOwner
———