Vista won't sleep a 2nd time!

[Carl]

Hi people,

I hope you can help me.
When I sleep Vista a 2nd time, this always eventually results in a
crash by ndiswan.sys: A device object has been blocking an Irp for too
long a time
I hope this can be resolved!
May be I should do something with the verifier tool to analyze it
more?

What happens the 2nd time I click sleep:
- The screen turns dark as usual
- Vista is roaring my hard drive for a bit
- This ends in a killing silence (normally in a shut down )
- just wait for 5 mins or something
- a blue screen presents itself (not sure)
- the computer reboots automatically (because default config tells
that it may reboot directly after a bluescreen)

When rebooted Vista reports that the system ended unexpectedly.
I ran windbg several times on the crash dumps with the !analyze -v
cmd, and every time the report is more or less the same:

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: 84648848, Physical Device Object of the stack
Arg3: 86be6030, Functional Device Object of the stack
Arg4: 861c7a18, The blocked IRP

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


DRVPOWERSTATE_SUBCODE: 3

IRP_ADDRESS: 861c7a18

DEVICE_OBJECT: 86be6030

DRIVER_OBJECT: 86ce5030

IMAGE_NAME: ndiswan.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 47919110

MODULE_NAME: ndiswan

FAULTING_MODULE: 83181000 ndiswan

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: INTEL_CPU_MICROCODE_ZERO

BUGCHECK_STR: 0x9F

PROCESS_NAME: System

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from 8244fb5c to 824e90e3

STACK_TEXT:
82511acc 8244fb5c 0000009f 00000003 84648848 nt!KeBugCheckEx+0x1e
82511b28 8244f6ac 82511b94 82511c50 8252a401 nt!PopCheckIrpWatchdog
+0x1ad
82511b68 824d2c40 8252a4e0 00000000 b1204840 nt!PopCheckForIdleness
+0x343
82511c88 824d2800 82511cd0 86ce9c02 82511cd8 nt!KiTimerListExpire
+0x367
82511ce8 824d23c3 00000000 00000000 002d5f24 nt!KiTimerExpiration
+0x22a
82511d50 824d0edd 00000000 0000000e 00000000 nt!KiRetireDpcList+0xba
82511d54 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x49


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

FAILURE_BUCKET_ID: 0x9F_IMAGE_ndiswan.sys

BUCKET_ID: 0x9F_IMAGE_ndiswan.sys

Followup: MachineOwner

 

[Jon]

You could try and pinpoint the faulty device or software by

1. One by one disconnecting devices - your networking / internet devices
sound the most likely culprits
2. Uninstalling software packages, especially those related to networking
etc

and after each step trying your 'sleeping twice experiment' to see at which
point it's resolved.

Once you've identified the faulty device or software, then go to the
relevant website for update drivers etc.

 

[Carl]

To what extent do you think it is sufficient to disable the network
devices?
I disabled both my network adapters but didn't add up to the solution.
Sleeping twice still resulted in an eventual blue screen/reboot.
Maybe I should try sleeping twice leaving the hardware out of my
system. I can only remove my WLAN adapter, since the gigabit LAN is on-
board of my motherboard.

Why should a disabled network device result in a time-out / no
response?
I hope to talk to a ndiswan expert one day who can help me diagnosing
what would be the component that is faulting.
Can't see anything in my installed software list that could have
anything to do with ndiswan. I already deinstalled every virtual
network driver I had added from vmware and virtualpc.

 

[Jon]

I don't really know, but those are the sort of things I'd try too.

Another thing that might be worth trying would be to disable power
management for those network adapters.

You can do this via the 'Power Management' tab for the device in 'Device
Manager' by clearing the "Allow the computer to turn off this device to save
power check box"

Also turning off things like 'Remote assistance' might help

Control Panel > System > Advanced System Settings > Remote (tab)

Good luck with the trouble-shooting.

--
Jon


To what extent do you think it is sufficient to disable the network
devices?
I disabled both my network adapters but didn't add up to the solution.
Sleeping twice still resulted in an eventual blue screen/reboot.
Maybe I should try sleeping twice leaving the hardware out of my
system. I can only remove my WLAN adapter, since the gigabit LAN is on-
board of my motherboard.

Why should a disabled network device result in a time-out / no
response?
I hope to talk to a ndiswan expert one day who can help me diagnosing
what would be the component that is faulting.
Can't see anything in my installed software list that could have
anything to do with ndiswan. I already deinstalled every virtual
network driver I had added from vmware and virtualpc.

 

[Ashton Crusher]

I had similar problems and I'm not sure it's solvable. My NEW HP
before any updates would go to sleep and wake up perfectly every time.
Then after the very first round of windows updates (this was about 18
months ago) it would no longer handle "sleep" properly. Sometimes it
would work right for one sleep cycle but on the second cycle it would
crash. So I gave up on sleep and turned it off. I also found that
just doing "shut down" no longer worked properly. Now it will often
shut down but after about 10 seconds the power light comes back on and
the hard drives all spin but it doesn't boot. It will sit like that
forever. I have to hold the power button down for the 20 seconds or
so and then it finally shuts off and stays shut off.