locked
Vista Home Premium won't sleep 2nd time RRS feed

  • Question

  • People,  

    My Vista Home Premium PC won't sleep a 2nd time. Everytime I start the sleep process the 2nd time the Vista machine just turns the screen into black, does something that triggers a bit of hard drive activity and then just hangs. After a while, 1 minute?, the pc reboots itself. And when entered the boot menu, Vista recognized it wasn't turned off correctly. Then when Vista has been launched again the self-diagnostics of Vista suggests that I should try to install KB938194. But when I try this, the KB executable fails by stating that "this update is not applicable to my system". What a bummer.  

    I already tried a lot: 
    - tweaking with powercfg.exe, disabling hibernate, disabling sleep, disabling the hybrid sleep, enabling the stuff again. - removing the inherit {resumeloadersettings} entry in the "resume from hibernate" section with bcdedit.exe.
    - reviewing the eventlog records in the system log. Can't find anything helpful there.  
    - tracing the process with the xbootmgr.exe tool from the Windows Performance Tools kit. It succeeds with tracing the first sleep process (generates a nice 20 MB file I can view with xperf.exe), but it clearly fails the 2nd sleep process since the trace process is never finished the right way, resulting in an etl-file of 0 bytes (too bad!).

    Nothing of this has helped me!

    Do you guys have any tips & tricks left?

    Sometimes I think the sleep process just fails because it is blocked by something (hardware? usb devices?). I even have the idea that alt-F4 and alt-tab sequences result in a little bit of hard drive activity. Is it possible to prevent Vista to go to black directly and instead to show some insightful information about the steps it is undertaking as part of the sleep process? This could definitely help!  

    Regards, 
    Carl
    Thursday, April 30, 2009 12:12 PM

Answers

  • Hi,

     

    Thank you for writing back and providing the information.

     

    I am sorry that debugging is beyond what we can do in the forum because of the nature of forum support. I'd like to recommend that you contact Microsoft Customer Support Service (CSS) for assistance so that this problem can be resolved efficiently. To obtain the phone numbers for specific technology request please take a look at the web site listed below:

     

    http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS

     

    If you are outside the US please see http://support.microsoft.com for regional support phone numbers.

     

    Having said that, I would still provide you the following and hope this can help:

     

    1. Adjust Power Management of the NICs.

    1)  Click Start, right click on Computer and choose Properties.

    2)  Click Device Manager.

    3)  Navigate to your NIC, right click on it and choose Properties.

    4)  Go to Power Management tab.

    5)  Please uncheck “Allow this device to wake the computer." Please uncheck this for all your NICs with the steps above.

    6)  Restart the computer and check if it works.

     

    2.  Disconnect all the connections and sleep to see if it works.

     

    3.  If a new driver for the NIC is available, please remove the older version and try this one.

     

    If the issue persists, please contact Microsoft Customer Support Service (CSS) for further troubleshooting. I hope the problem will be resolved soon. Thanks! 


    Nicholas Li - MSFT
    Thursday, May 14, 2009 10:19 AM
    Moderator

All replies

  •  

    Hi Carl,

     

    Thank you for your post.

     

    May I know if some changes have been made on the computers recently before the issue occurred?

     

    If everything worked before, a quick solution is to restore the system back to the previous status when the issue didn’t occur with System Restore.

    (Note: Performing a system restore may cause the loss of the current system settings; therefore, before doing this, please make sure that the system restore point is not too old and set a restore point for the current status.)

     

    Based on my research, I would like suggest the following:

     

    1.    Make sure that the computer is virus free.

     

    2.    Poor contact or short circuit may wake up the computer. Please check all the power button or other buttons or keys which can wake the computer.

     

    3.    Reconfigure the Power Options:

     

    1)    Please go to “Control Panel – Power Options” and click the link “Change plan settings” link of your current power plan.

    2)    On “Edit Plan Settings”, click “Restore default settings for this plan” and then click “Yes”.

    3)    Go to “change advanced power settings”.

    4)    On the “Advanced settings” window, click “change settings that are currently unavailable” if it exists. Then click “Restore plan defaults” and click “Yes”. Then Click “OK” to save the settings and close this window.

    5)    After the steps above, the Power Options are reset to default. Please reconfigure your personalized power settings and then check if it works.

     

    4.    Temporarily unplug the unnecessary devices (such as second hard drive, Optical Disk Drive or some particular specifications) to test the issue.

     

    5.    Please refer the following Knowledge Base to troubleshoot the issue:

     

    A computer that is running Windows Vista appears to sleep and then immediately wake

    http://support.microsoft.com/kb/927821

     

    6.    Please perform a Clean Boot to check the issue.

     

    Clean boot

    =================

    1)     Click the Start Button type "msconfig" (without quotation marks) in the Search box, and then press Enter.

    Note: If prompted, please click Continue on the User Account Control (UAC) window.

    2)   Click the "Services" tab, check the "Hide All Microsoft Services" box and click "Disable All" (if it is not gray).

    3)   Click the "Startup" tab, click "Disable All" and click "OK".

     

    Then, restart the computer. When the "System Configuration Utility" window appears, please check the "Don't show this message or launch the System Configuration Utility when Windows starts" box and click OK.

     

    NOTE: we can go back to normal boot by running msconfig again and checking on Normal Startup in the General tab.

     

    In the Clean Boot Environment, the third party services and applications are disabled, please monitor if the issue reoccurs.

     

    If the problem does not occur, it indicates that the problem is related to one application or service we have disabled. You may use the MSCONFIG tool again to re-enable the disabled item one by one to find out the culprit.

     

    If the issue persists, please check the Event Log, “Windows Logs – System” and check the entries "Power-Troubleshooter" to see what woke the system.

     

    Hope this helps. Thanks.


    Nicholas Li - MSFT
    • Marked as answer by Nicholas LiModerator Monday, May 11, 2009 4:05 AM
    • Unmarked as answer by cveld Tuesday, May 12, 2009 8:29 PM
    Monday, May 4, 2009 9:42 AM
    Moderator
  • Hi Nicholas,

    Thanks for your extensive reply. I followed up a few of your suggestions.

    Ad 1. McAfee does not report anything in particular.
    Ad 2. It is not a problem of the system unexpectedly waking, it is about the system that is not able to sleep the 2nd time.
    Ad 3. I tested this. Did not resolve the issue.
    Ad 4. Haven't tested this yet.
    Ad 5. See my reply to item 2.
    Ad 6. I tested this. Did not resolve the issue, unfortunately! Good suggestion though.

    I discovered that the system makes a minidump every time the 2nd sleep fails and results in a reboot.
    So I started analyzing these minidumps using windbg.exe. 
    1. It appears that the device driver of my wlan card is causing a blocked IRP whatever that may be.
    2. I deactived my wlan card via network settings and tried a 2nd sleep again. This time the ndiswan.sys device driver appears to cause a blocked IRP.

    Frankly I had vmware and virtual pc network drivers installed, not officially supported by Vista, but were working fine until recently. I deinstalled them right away. May be there is still some troubling footprint left here...

    Either way, I am still lost here.  Why is ndiswan.sys, a standard Vista device driver, as part of the basic networking stack, causing this?
    Is there some way to recover from this?

    Here the complete !analyze -v report for both cases.

    I hope you or someone else can help me solve this!

    Regards,
    Carl

    ================= 1, wlan card still activated

    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: 854576b0, Physical Device Object of the stack
    Arg3: 8553e380, Functional Device Object of the stack
    Arg4: 84ec4e28, The blocked IRP

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


    DRVPOWERSTATE_SUBCODE:  3

    IRP_ADDRESS:  84ec4e28

    DEVICE_OBJECT: 8553e380

    DRIVER_OBJECT: 8691d2b8

    IMAGE_NAME:  MRVW13B.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  45397999

    MODULE_NAME: MRVW13B

    FAULTING_MODULE: 82f66000 MRVW13B

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  INTEL_CPU_MICROCODE_ZERO

    BUGCHECK_STR:  0x9F

    PROCESS_NAME:  System

    CURRENT_IRQL:  2

    LAST_CONTROL_TRANSFER:  from 8224eb5c to 822e80e3

    STACK_TEXT:  
    82310acc 8224eb5c 0000009f 00000003 854576b0 nt!KeBugCheckEx+0x1e
    82310b28 8224e6ac 82310b94 82310c50 82329401 nt!PopCheckIrpWatchdog+0x1ad
    82310b68 822d1c40 823294e0 00000000 4fb8e830 nt!PopCheckForIdleness+0x343
    82310c88 822d1876 82310cd0 82310d02 82310cd8 nt!KiTimerListExpire+0x367
    82310ce8 822d13c3 00000000 00000000 005fda88 nt!KiTimerExpiration+0x2a0
    82310d50 822cfedd 00000000 0000000e 00000000 nt!KiRetireDpcList+0xba
    82310d54 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x49


    STACK_COMMAND:  kb

    FOLLOWUP_NAME:  MachineOwner

    FAILURE_BUCKET_ID:  0x9F_IMAGE_MRVW13B.sys

    BUCKET_ID:  0x9F_IMAGE_MRVW13B.sys

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


    ================= 2, wlan card deactived

    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: 84247c70, Physical Device Object of the stack
    Arg3: 8667e030, Functional Device Object of the stack
    Arg4: 86954378, The blocked IRP

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


    DRVPOWERSTATE_SUBCODE:  3

    IRP_ADDRESS:  86954378

    DEVICE_OBJECT: 8667e030

    DRIVER_OBJECT: 8670a648

    IMAGE_NAME:  ndiswan.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  47919110

    MODULE_NAME: ndiswan

    FAULTING_MODULE: 8d362000 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 82245b5c to 822df0e3

    STACK_TEXT:  
    82307acc 82245b5c 0000009f 00000003 84247c70 nt!KeBugCheckEx+0x1e
    82307b28 822456ac 82307b94 82307c50 82320401 nt!PopCheckIrpWatchdog+0x1ad
    82307b68 822c8c40 823204e0 00000000 18866170 nt!PopCheckForIdleness+0x343
    82307c88 822c8800 82307cd0 86764f02 82307cd8 nt!KiTimerListExpire+0x367
    82307ce8 822c83c3 00000000 00000000 00416425 nt!KiTimerExpiration+0x22a
    82307d50 822c6edd 00000000 0000000e 00000000 nt!KiRetireDpcList+0xba
    82307d54 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
    ---------


    Tuesday, May 12, 2009 8:26 PM
  • Hi,

     

    Thank you for writing back and providing the information.

     

    I am sorry that debugging is beyond what we can do in the forum because of the nature of forum support. I'd like to recommend that you contact Microsoft Customer Support Service (CSS) for assistance so that this problem can be resolved efficiently. To obtain the phone numbers for specific technology request please take a look at the web site listed below:

     

    http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS

     

    If you are outside the US please see http://support.microsoft.com for regional support phone numbers.

     

    Having said that, I would still provide you the following and hope this can help:

     

    1. Adjust Power Management of the NICs.

    1)  Click Start, right click on Computer and choose Properties.

    2)  Click Device Manager.

    3)  Navigate to your NIC, right click on it and choose Properties.

    4)  Go to Power Management tab.

    5)  Please uncheck “Allow this device to wake the computer." Please uncheck this for all your NICs with the steps above.

    6)  Restart the computer and check if it works.

     

    2.  Disconnect all the connections and sleep to see if it works.

     

    3.  If a new driver for the NIC is available, please remove the older version and try this one.

     

    If the issue persists, please contact Microsoft Customer Support Service (CSS) for further troubleshooting. I hope the problem will be resolved soon. Thanks! 


    Nicholas Li - MSFT
    Thursday, May 14, 2009 10:19 AM
    Moderator
  • Hello,

    Don't know if this may help in your case.  I had the same problem.  Though my problem started with not going into sleep mode sucessfully at all - found out that this was due to an older version of a Microsoft Intellimouse driver - installed  the latest driver and it went to sleep the first time but not the second.  After lengthy calls with tech support that resulted in absolutely no improvement (even had to send in the laptop so they could replace the motherboard); I finally found out (no thanks to tech support) that my problem was due to non-HP branded memory that I had bought to provide the laptop with the max amount of memory.  For me it is either due to non-HP branded memory or the system can't actually utilize the max amount of RAM they say it can - don't know which, and I am not going to replace the memory again (already did that twice) with the very expensive branded memory.  Still don't understand why it will work fine the first time and have problems the second.  I decided to disable sleep mode and have the system go into hibernation upon lid closure - this works on my system and is better than buying the branded memory or using less total memory.

    Hope this helps
    Wednesday, June 3, 2009 11:32 PM
  • Hey don't know if you've solved it yet but i had a similar issue after i did a clean install of Windows 7. My laptop would sleep or hibernate first time after a clean boot no problem. However if i tried to sleep or hibernate a 2nd time it would blank the screen and hang but not sleep. I tried different drivers etc but didn't resolve it until now. I did two things... 1.) disabled the screensaver, 2.) re-ticked the "allow computer to turn off this device to save power" option under Power Management of various devices.

    This solved the problem. I don't know whether it was the screensaver or the power management settings of the devices that solved it but it was one of those.... i could do a simple test and let you know for sure which one it was but it's late and i can't be bothered so you can figure it instead.

    BTW i googled for hours and hours to figure this one out cause very few people reported the same problem with it failing to sleep or hibernate on the 2nd attempt.

    Cheers

    J
    Friday, June 5, 2009 10:44 AM
  • Hi bgiaw, thanks for your suggestion. I also had a clean installed Windows 7 PC (RC 7100) and it had exactly the same issue of hanging after a second sleep.

    This was gone by going to the "device manager"
    For all the "USB Root Hubs" select "properties" then "power management". Here tick "allow computer to turn off this device to save power".
    Same goes for the "network adapters".

    Now the system goes to sleep and wakes up fine everytime.
    Hope this also holds for vista.
    Cheers E
     
    Friday, August 7, 2009 9:48 PM
  • I am still trying to resolve the issue. Followed your suggestion regarding the "allow computer to turn off this device to save power". I walked through several scenarios: 
    1. It was activated, I unchecked it, and then tried 2 times sleeping. No improvement.
    2. I rechecked it, and then tried 2 times sleeping. Still no improvements.

    I always get the following windbg analysis:
    It indeed seems having something to do with a device driver, especially some component within the ndiswan stack.

    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: 86d8f030, Functional Device Object of the stack
    Arg4: a8bf3578, The blocked IRP

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


    DRVPOWERSTATE_SUBCODE:  3

    IRP_ADDRESS:  a8bf3578

    DEVICE_OBJECT: 86d8f030

    DRIVER_OBJECT: 86e7e510

    IMAGE_NAME:  ndiswan.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  47919110

    MODULE_NAME: ndiswan

    FAULTING_MODULE: 833cd000 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 82449b5c to 824e30e3

    STACK_TEXT:  
    8250bacc 82449b5c 0000009f 00000003 84648848 nt!KeBugCheckEx+0x1e
    8250bb28 824496ac 8250bb94 8250bc50 82524401 nt!PopCheckIrpWatchdog+0x1ad
    8250bb68 824ccc40 825244e0 00000000 d19332d0 nt!PopCheckForIdleness+0x343
    8250bc88 824cc800 8250bcd0 86df8702 8250bcd8 nt!KiTimerListExpire+0x367
    8250bce8 824cc3c3 00000000 00000000 0081b2ee nt!KiTimerExpiration+0x22a
    8250bd50 824caedd 00000000 0000000e 00000000 nt!KiRetireDpcList+0xba
    8250bd54 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
    ---------

    Sunday, August 9, 2009 8:54 PM