X61 Vista waking from sleep and rebooting

[sorenj]

I believe this problem has been noted by a few other users in this forum.  The
Intel Pro/Wireless 3945ABG device causes the laptop to wake from sleep mode
with a blue screen followed by reboot.

here's what windbg implicates

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 00000003, A device object has been blocking an Irp for too long a time
Arg2: 8590eb70, Physical Device Object of the stack
Arg3: 883f4030, Functional Device Object of the stack
Arg4: 8d941008, The blocked IRP

Debugging Details:
------------------


DRVPOWERSTATE_SUBCODE:  3

IRP_ADDRESS:  8d941008

DEVICE_OBJECT: 883f4030

DRIVER_OBJECT: 883fd238

IMAGE_NAME:  NETw4v32.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4784aba4

MODULE_NAME: NETw4v32

FAULTING_MODULE: 8f800000 NETw4v32

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  ScanningProcess

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from 82045b6c to 820df163

STACK_TEXT: 
8059dd6c 82045b6c 0000009f 00000003 8590eb70 nt!KeBugCheckEx+0x1e
8059ddc8 820456bc 8059de34 8059def0 82120401 nt!PopCheckIrpWatchdog+0x1ad
8059de08 820c8d00 821204e0 00000000 68a53da0 nt!PopCheckForIdleness+0x343
8059df28 820c8936 8059df70 8059df02 8059df78 nt!KiTimerListExpire+0x367
8059df88 820c8483 00000000 00000000 007beddc nt!KiTimerExpiration+0x2a0
8059dff4 820c69f5 b1087690 00000000 00000000 nt!KiRetireDpcList+0xba
8059dff8 b1087690 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x45
WARNING: Frame IP not in any known module. Following frames may be wrong.
820c69f5 00000000 0000001b 00c7850f bb830000 0xb1087690


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  0x9F_IMAGE_NETw4v32.sys

BUCKET_ID:  0x9F_IMAGE_NETw4v32.sys

Followup: MachineOwner
---------

Note that this driver is 11.5.1.8 which was released on 1/8/2007
It is the latest available on Lenovo System update

Intel lists a more recent driver 11.5.1.15, but as always they recommend getting
drivers only from the OEM.

Have tried to open this issue with anyone in Lenovo tech support, but all they will
tell me is that I have to reinstall the whole operating system.  I already know that won't
address what is going wrong.

[promer]

This has been a very frustrating problem with my X61. Any updated information on an updated driver?

Have others found ways to put the machine to sleep or hibernate that reduce the chances of a BSD on awakening? E.g. by turning the radio off first?  

[sorenj]

Yes, this happens a lot...

Perhaps I should try to get a new network card.  Perhaps I should try contacting Intel directly.


Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
Copyright (c) Microsoft Corporation. All rights reserved.


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

Symbol search path is: SRV*c:\local cache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2008 Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6001.18000.x86fre.longhorn_rtm.080118-1840
Kernel base = 0x8204e000 PsLoadedModuleList = 0x82165c70
Debug session time: Thu Jun 12 23:19:46.752 2008 (GMT-4)
System Uptime: 1 days 20:10:49.659
Loading Kernel Symbols
..................................................................................................................................................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, 859095a0, 884e9030, 879d28a0}

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

Followup: MachineOwner
---------

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

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 00000003, A device object has been blocking an Irp for too long a time
Arg2: 859095a0, Physical Device Object of the stack
Arg3: 884e9030, Functional Device Object of the stack
Arg4: 879d28a0, The blocked IRP

Debugging Details:
------------------


DRVPOWERSTATE_SUBCODE:  3

IRP_ADDRESS:  879d28a0

DEVICE_OBJECT: 884e9030

DRIVER_OBJECT: 884ec368

IMAGE_NAME:  NETw4v32.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4784aba4

MODULE_NAME: NETw4v32

FAULTING_MODULE: 8f804000 NETw4v32

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from 82081b6c to 8211b163

STACK_TEXT: 
82143acc 82081b6c 0000009f 00000003 859095a0 nt!KeBugCheckEx+0x1e
82143b28 820816bc 82143b94 82143c50 85951601 nt!PopCheckIrpWatchdog+0x1ad
82143b68 82104d00 8215c4e0 00000000 54defbd0 nt!PopCheckForIdleness+0x343
82143c88 821048c0 82143cd0 8a7dbb02 82143cd8 nt!KiTimerListExpire+0x367
82143ce8 82104483 00000000 00000000 009b91e0 nt!KiTimerExpiration+0x22a
82143d50 82102f9d 00000000 0000000e 00000000 nt!KiRetireDpcList+0xba
82143d54 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x49


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  0x9F_IMAGE_NETw4v32.sys

BUCKET_ID:  0x9F_IMAGE_NETw4v32.sys

Followup: MachineOwner
---------

[stephanpark]

I'm having a similar if more convoluted problem with my 4965AGN, I'm going to give Debugging dump reader a try.

My situation is a BSOD with message "A driver has overrun a stack-based buffer. This overrun could potentially allow a malicious user to gain control of this machine."  This happens if I try to repair the connection, or if I try to install the latest drivers.

I assumed the drivers had become corrupted from a botched R&R rebuild, but that does not seem to be it.  My install of Kaspersky then became suspect after this http://forum.kaspersky.com/index.php?showtopic=70891&pid=668185&st=0&#entry668185

This could also be a virus for my issue but I'll watch this thread.

I can't justify a return of the brand new machine, but if this is hardware or vender driver as seems here....I'll have to pass on X61 and wait for X300's price to come down.


Message Edited by stephanpark on 06-22-2008 07:38 AM

[sorenj]

After trying repeatedly to get to someone at Lenovo who recommends something
besides reinstalling the whole operating system, and contacting Intel I decided to
follow Intel's advice and download the latest driver for my card (ignoring the OEM
driver)

Note that I do not use Access Connections, but just the plain old Windows Vista
networking.

http://downloadcenter.intel.com/Detail_Desc.aspx?agr=N&Inst=Yes&ProductID=2259&DwnldID=15806&strOSs=...

The new driver installed smoothly, and so far no problems with Sleep.
I'm now using 11.5.1.15 with my X61.

[icantux]

Hi folks,

One simple way to overcome this issue (particularly as they relate to Intel cards more than the Atheros-based units), is to disable one simple "power" option on the hardware.

Turn off (uncheck) the option "Allow this device to bring the computer out of standby" located in the device manager/power management options for the card (Intel 3945 or 4965).

You can then still use Lenovo's drivers without anymore hiccups. Better that way in any case, because you can turn the card on/off using Fn-F5, otherwise  if you use Intel's stock drivers then you'll lose that capability.

Hope this helps!
Steve

[sorenj]

I had already disabled this option, it had no effect on my BSOD problems
while in sleep.

[sorenj]

Drat!  I spoke too soon - it still crashes, same module - this time it happened when
trying to enter sleep (eh, it took forever, I lost interest and went to work - later in the day
I got the following crash dump)
*** WARNING: Unable to verify timestamp for NETw4v32.sys
*** ERROR: Module load completed but symbols could not be loaded for NETw4v32.sys
Probably caused by : NETw4v32.sys

Followup: MachineOwner
---------

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

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 00000003, A device object has been blocking an Irp for too long a time
Arg2: 859096b0, Physical Device Object of the stack
Arg3: 883ef380, Functional Device Object of the stack
Arg4: 84fd81e8, The blocked IRP

Debugging Details:
------------------


DRVPOWERSTATE_SUBCODE:  3

IRP_ADDRESS:  84fd81e8

DEVICE_OBJECT: 883ef380

DRIVER_OBJECT: 884ea030

IMAGE_NAME:  NETw4v32.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  47d903b8

MODULE_NAME: NETw4v32

FAULTING_MODULE: 8f005000 NETw4v32

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from 82076b6c to 82110163

STACK_TEXT: 
82138acc 82076b6c 0000009f 00000003 859096b0 nt!KeBugCheckEx+0x1e
82138b28 820766bc 82138b94 82138c50 00000001 nt!PopCheckIrpWatchdog+0x1ad
82138b68 820f9d00 821514e0 00000000 6e856de0 nt!PopCheckForIdleness+0x343
82138c88 820f98c0 82138cd0 8a7d5b02 82138cd8 nt!KiTimerListExpire+0x367
82138ce8 820f9483 00000000 00000000 00d82fcd nt!KiTimerExpiration+0x22a
82138d50 820f7f9d 00000000 0000000e 00000000 nt!KiRetireDpcList+0xba
82138d54 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x49


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  0x9F_IMAGE_NETw4v32.sys

BUCKET_ID:  0x9F_IMAGE_NETw4v32.sys

Followup: MachineOwner
---------



This is the NETw4v32.sys file version 11.5.1.15
dated 3/13/2008

I certainly wish that Lenovo or Intel would work with someone to fix this problem.

Is it a hardware problem?  Maybe I should try to get a replacement card?

But, others have complained about this same problem.