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: ------------------
FAULTING_MODULE: 8f800000 NETw4v32
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
Followup: MachineOwner ---------
Note that this driver is 18.104.22.168 which was released on 1/8/2007 It is the latest available on Lenovo System update
Intel lists a more recent driver 22.214.171.124, 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.
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
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.
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.
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.
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
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