Windows 8.1 sleep/hibernate issues

I have some issues with sleep and hibernation on my freshly installed Windows 8.1
Hibernation gets triggered properly after the set number of minutes, however, instead of going back to the previous state, a hard boot takes place. hilberfile.sys has the current time stamp, so I suspect it's an issue with waking up, not with going to sleep.
I also tried the sleep mode as an alternative. It seems to go to sleep correctly, however, there's no chance to wake the computer up. I tried mouse, keyboard, power button - nothing. I hold the power button for 5 seconds, and a hard boot takes place. Seems
to be another problem with waking up.
Any ideas for further analysis on this issue?
BIOS is up to date, and on default settings (I've skipped the latest Beta update though).
Best wishes,
Jan

Hi,
My computer also encountered the similar problem. in my opinion, it is too old, even didn’t had corresponding driver of Windows 8.
For this problem, I would like recommend you upgrade all the hardware driver to be latest, especially the Graphic driver and power management driver(if accessible).
You can use Driver Verifier to check the driver problem.
Please refer to the link below for more details about how to use Driver Verifier to identify driver issues.
http://support.microsoft.com/kb/244617
In addition, please try to disable hibernation for test.
For the BSOD problem, you can zip up the minidump files in the C:\Windows\Minidump folder and make available (provide link) via Windows Live SkyDrive. We may could find some caused reason about this problem
Roger Lu
TechNet Community Support

Similar Messages

  • Resume from Sleep / Hibernate issues

    Hi all,
    First time poster. I have a Helix and am running into a heap of resume from sleep (and hibernate) issues.
    The sleep issues tend to happen overnight - I do not have this issue if I sleep the machine and then wake it up 5-10 minutes later (e.g. moving between meetings at work). However, when I attempt to wake the machine up in the morning, it fails to resume from sleep, and instead boots from scratch.
    Typically, when the unit is in this state, the status led on the lid is rapidly blinking (which I believe means that it's trying to enter sleep) Since there is nothing in the Windows event log during the overnight period, I'm wondering whether it's trying to enter a deeper sleep mode and failing.
    This happens every second day or so. Which is really frustrating as a tend to lose some work.
    I tried enabling hibernate as a trial, to see if that would avoid the issue, but resuming from hibernate fails as well. At least I get a Windows event log entry for this (source: kernel-power. The unit fails to resume from hibernate with status 0xC000000D)
    I have the September 10 BIOS update, and am running Windows 8.1 Enterprise (though I had the issue with Windows 8 as well).
    Any ideas on how I can troubleshoot this?
    Regards
    AC

    Windows 8: In Windows 8, the default shutdown behavior puts the system into hybrid shutdown (S4) and all devices are put into D3. Remote wake from hybrid shutdown (S4) or classic shutdown (S5) is completely unsupported. In Windows 8, NICs are explicitly not armed for wake in both the classic shutdown (S5) and hybrid shutdown (S4) cases because users expect zero power consumption and battery drain in the shutdown state. This behavior removes the possibility of spurious wakes when explicit shutdown was requested. As a result, Wake-On-LAN is only ever supported from sleep (S3) or hibernate (S4) in Windows 8.
    Note that in Windows 8, hybrid shutdown (S4) stops user sessions but the contents of kernel sessions are written to hard disk. This enables faster boot.
    http://msdn.microsoft.com/en-us/library/windows/desktop/aa373229(v=vs.85).aspx
    From the Helix User Guide:
    •Slow blinking: The tablet is in sleep mode.
    •Fast blinking: The tablet is entering hibernation mode or sleep mode.
    That was my reason for clarifying if hybrid-sleep was enabled; since it's the default setting and you noted that the LED was blinking fast. Does the LED ever stop blinking fast?
    There can/may be multiple log entries during a normal sleep operation,  because "the system uses the lowest-powered sleep state supported by all enabled wake-up devices." If one of those devices wakes the system (this does not mean power on) then the logs will report the devices and will likely return to a another level of sleep, but this does not mean full power loss or empty logs.
    If the system has successfully entered sleep state, then you should see the following message in System Event logs. 
    Event 42, Kernel - Power
    This system is entering sleep.
    Sleep Reason: Button or lid
    When the system is successfully woke you will see a System Event Log similar to this:
    Event 1, Power - Troubleshooter
    The system has returned from a low power state.
    Sleep time: 2013-10-08T01:42:25.XXXXXXXX
    Wake time: 2013-10-08T05:53:21.XXXXXXXX
    However, there will be other events in the logs after sleep and prior to this wake period, such as hardware device issues(My helix has Bluetooth device warnings, nfc driver warnings and some other nondescript hardware errors), kernel messages (about boot manager, boot options, etc.).
    Have you changed the behavior of the power button?
    You also can program the power buttons so that by pressing the power button you can shutdown the tablet or put it into sleep or hibernation mode. To achieve this, you need to change your power plan settings. To access power plan settings, do the following:
    From the desktop, tap the battery status icon in the Windows notification area.
    Tap More power options.
    In the navigation panel, tap Choose what the power buttons do
    Follow the onscreen instructions to configure settings.
    Lastly, when you updated to Windows 8.1, did you format the whole C:\ (mSATA) drive?
    Helix: 3697 CTO.
    Thinkpad user since IBM. I do not work for Lenovo or any entity working for Lenovo.

  • Maintenance Windows - Scheduled Reboot Sleep/Hibernate

    Given an appropriately scheduled maintenance window and a properly configured set of client settings (computer restart), what is the expected behavior for a client computer that enters standby/hibernate during the countdown and doesn't resume until after
    it has ended?
    I have been running a few tests in my environment and I'm finding that clients resuming from standby/hibernate are being forced to reboot immediately. Sometimes before I am able to hit ctrl+alt+delete and login.
    Is this expected?

    Is this expected?
    I think this is expected. More details from Rebootcoordinator.log would be helpful.
    Anoop C Nair -
    @anoopmannur :: MY Site:
     www.AnoopCNair.com ::
    FaceBook:
     ConfigMgr(SCCM) Page ::
    Linkedin:
     Linkedin<

  • Satellite Pro A210 PSAFHE - Windows 7 - freezes after sleep/hibernate

    I have a Satellite Pro A210 PSAFHE running dual boot Windows XP/7
    Using Windows 7 - either 32 or 64 - the system always freezes after sleep/hibernate.
    This never happens with XP which sleeps and hibernates OK..
    There are no drivers at all for this notebook on the site http://eu.computers.toshiba-europe.com/innovation/download_drivers_bios.jsp?service=EU
    I like System 7 and use it on my other computers but without sleep/hibernate I will revert to XP.

    Hi
    > There are no drivers at all for this notebook on the site http://eu.computers.toshiba-europe.com/innovation/download_drivers_bios.jsp?service=EU
    Sorry mate but you are wrong.
    All Win 7 drivers for Satellite Pro A210 are released on the Toshiba European driver page I recommend checking it again
    Since this issue does not appear using Win XP, I can say for sure that this has nothing to do with the hardware but its a software related issue
    I recommend updating the graphic card driver
    Furthermore there is a new BIOS for Sat Pro A210 PSAFHEits v2.0
    Check if you are using the latest version

  • HP 15t j000 will not wake from sleep/hibernate Windows 8,8.1,10

    HP 15t j000 will not wake from sleep/hibernate Windows 8,8.1,10. I have to restart. I've searched high and low for answer to this. I've seen videos, played with power settings.  I hoped each Windows system upgrade would fix the problem. No go. Anyone with any ideas?

    Hi , Thank you for your query.  I understand that after upgrading to Windows 10, it will not wake from sleep mode unless you restart. The first step I would try is to disable "Hybrid Boot' or "Hybrid Shutdown.  This can be done by turning off "Fast Startup" Fast Startup - Turn On or Off in Windows 10 Next try running the "Update Troubleshooter"  Windows Update troubleshooter. Once launched, it should show a screen like this. Use the second option "Background Intelligent Transfer Service", it should lead to a force update of 'Windows Updates' that may not be automatically being applied, that could fix some of these issues.
      Here is a link to HP PCs - Sleep and Hibernate Issues (Windows 10, 8) that may also help.  To say thanks for replying please click the thumbs up button below.If this yielded a solution please choose solution provided to help other people find this information.  Best of Luck! 

  • How long will it take to fix the 'Windows 10 won't sleep, hibernate or shutdown' problem?

    Here, first take this System Info: OS Name Microsoft Windows 10 Home Single Language
    Version 10.0.10240 Build 10240
    Other OS Description Not Available
    OS Manufacturer Microsoft Corporation
    System Name DESKTOP-RJEGINM
    System Manufacturer Hewlett-Packard
    System Model HP Pavilion 15 Notebook PC
    System Type x64-based PC
    System SKU G8D90PA#ACJ
    Processor Intel(R) Core(TM) i5-4210U CPU @ 1.70GHz, 2401 Mhz, 2 Core(s), 4 Logical Processor(s)
    BIOS Version/Date Insyde F.42, 18-Mar-15
    SMBIOS Version 2.8
    Embedded Controller Version 77.53
    BIOS Mode UEFI
    BaseBoard Manufacturer Hewlett-Packard
    BaseBoard Model Not Available
    BaseBoard Name Base Board
    Platform Role Mobile
    Secure Boot State Off
    PCR7 Configuration Binding Not Possible
    Windows Directory C:\Windows
    System Directory C:\Windows\system32
    Boot Device \Device\HarddiskVolume2
    Locale United States
    Hardware Abstraction Layer Version = "10.0.10240.16392"
    Time Zone India Standard Time
    Installed Physical Memory (RAM) 4.00 GB
    Total Physical Memory 3.93 GB
    Available Physical Memory 1.80 GB
    Total Virtual Memory 5.31 GB
    Available Virtual Memory 2.84 GB
    Page File Space 1.38 GB
    Page File C:\pagefile.sys
    Hyper-V - VM Monitor Mode Extensions Yes
    Hyper-V - Second Level Address Translation Extensions Yes
    Hyper-V - Virtualization Enabled in Firmware No
    Hyper-V - Data Execution Protection Yes So many HP users all over the world are reporting the inability of their notebooks to go to sleep, hibernate or shut down after upgrading to Windows 10 from Windows 8.1. What are you guys doing about this? At least provide some information on whether you have even taken notice to this problem or not! There won't be a point of a fix once the hard-disk is gone because of all the hard resets.

    It's not just HP,  but Dell too.   Suggest switching the power options settings to "never" and always shutting down Windows before closing the lid.  PITA,  but avoids all those 'hard stops' doing any damage. I've partly fixed the issue on my machine by updating all the drivers to very latest,  shutting down and rebooting,  then shutting down,  removing the battery pack,  holding down the power button for at least 30 seconds,  then replacing the battery and booting up as usual.   So far,  this has fixed the "sleep" problem,  but HIbernate is still not working.     I've a Dell machine,  but a lot of the Hardware is common to the HP laptops - Intel Video etc. Steve

  • BSOD VIDEO_DXGKRNL_FATAL_ERROR after sleep/hibernate on windows 8.1 HP Zbook 14

    I have a new HP ZBook Mobile 14 workstation that I have upgraded to windows 8.1.
    Unfortunately after it has gone to sleep/hibernate the machine will always BSOD referencing VIDEO_DXGKRNL_FATAL_ERROR when I try to wake it up. I have tried uninstalling and re-installing all the drivers but am not having any joy. I have also disabled
    fast start up and hibernate from the power options but that has not improved the situation.
    I have put the mini dumps on OneDrive: MiniDumps
    Any help would be greatly appreciated!
    Cheers, James

    James
    Ouch 21 crashes in a week.  These were related to your video driver (igdkmd64.sys) causing DirectX to fail.  There is a known problem with the March 2014 drivers (yours) and the July 2014 drivers.  As a first step I would remove the current
    driver and revert back to a driver that is at least 6 months older at least until they release a less buggy driver.  This is one of those times when a newer driver isnt better.
    Microsoft (R) Windows Debugger Version 6.3.9600.17029 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    Loading Dump File [C:\Users\Ken\Desktop\New folder\083014-10375-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    ************* Symbol Path validation summary **************
    Response Time (ms) Location
    Deferred srv*C:\Symbols*http://msdl.microsoft.com/download/symbols
    Symbol search path is: srv*C:\Symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    Machine Name:
    Kernel base = 0xfffff802`d8607000 PsLoadedModuleList = 0xfffff802`d88d12d0
    Debug session time: Sat Aug 30 09:42:27.923 2014 (UTC - 4:00)
    System Uptime: 0 days 0:43:20.664
    Loading Kernel Symbols
    Loading User Symbols
    Loading unloaded module list
    * Bugcheck Analysis *
    Use !analyze -v to get detailed debugging information.
    BugCheck 113, {17, ffffe000b97f5010, 0, 0}
    *** WARNING: Unable to verify timestamp for igdkmd64.sys
    *** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
    Probably caused by : dxgkrnl.sys ( dxgkrnl!DXGADAPTER::SetPowerComponentActiveCB+44 )
    Followup: MachineOwner
    1: kd> !analyze -v
    * Bugcheck Analysis *
    VIDEO_DXGKRNL_FATAL_ERROR (113)
    The dxgkrnl has detected that a violation has occurred. This resulted
    in a condition that dxgkrnl can no longer progress. By crashing, dxgkrnl
    is attempting to get enough information into the minidump such that somebody
    can pinpoint the crash cause. Any other values after parameter 1 must be
    individually examined according to the subtype.
    Arguments:
    Arg1: 0000000000000017, The subtype of the bugcheck:
    Arg2: ffffe000b97f5010
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    Debugging Details:
    CUSTOMER_CRASH_COUNT: 1
    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
    BUGCHECK_STR: 0x113
    PROCESS_NAME: System
    CURRENT_IRQL: 0
    ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre
    LAST_CONTROL_TRANSFER: from fffff8001d99c9ca to fffff802d875afa0
    STACK_TEXT:
    ffffd000`20945a18 fffff800`1d99c9ca : 00000000`00000113 00000000`00000017 ffffe000`b97f5010 00000000`00000000 : nt!KeBugCheckEx
    ffffd000`20945a20 fffff800`1d82e990 : ffffe000`b97f5010 ffffe000`badcf880 ffffd000`20945a88 00000000`00000018 : watchdog!WdLogEvent5_WdCriticalError+0xce
    ffffd000`20945a60 fffff800`1f096e8c : ffffe000`b99f9000 00000000`00000001 00000000`00000000 00000000`00000000 : dxgkrnl!DXGADAPTER::SetPowerComponentActiveCB+0x44
    ffffd000`20945a90 ffffe000`b99f9000 : 00000000`00000001 00000000`00000000 00000000`00000000 ffffe000`c0a918e0 : igdkmd64+0x3be8c
    ffffd000`20945a98 00000000`00000001 : 00000000`00000000 00000000`00000000 ffffe000`c0a918e0 fffff800`1f093c22 : 0xffffe000`b99f9000
    ffffd000`20945aa0 00000000`00000000 : 00000000`00000000 ffffe000`c0a918e0 fffff800`1f093c22 ffffe000`c0689880 : 0x1
    STACK_COMMAND: kb
    FOLLOWUP_IP:
    dxgkrnl!DXGADAPTER::SetPowerComponentActiveCB+44
    fffff800`1d82e990 4869cf08020000 imul rcx,rdi,208h
    SYMBOL_STACK_INDEX: 2
    SYMBOL_NAME: dxgkrnl!DXGADAPTER::SetPowerComponentActiveCB+44
    FOLLOWUP_NAME: MachineOwner
    MODULE_NAME: dxgkrnl
    IMAGE_NAME: dxgkrnl.sys
    DEBUG_FLR_IMAGE_TIMESTAMP: 539a2a6c
    IMAGE_VERSION: 6.3.9600.17210
    BUCKET_ID_FUNC_OFFSET: 44
    FAILURE_BUCKET_ID: 0x113_dxgkrnl!DXGADAPTER::SetPowerComponentActiveCB
    BUCKET_ID: 0x113_dxgkrnl!DXGADAPTER::SetPowerComponentActiveCB
    ANALYSIS_SOURCE: KM
    FAILURE_ID_HASH_STRING: km:0x113_dxgkrnl!dxgadapter::setpowercomponentactivecb
    FAILURE_ID_HASH: {e8253e80-8827-02a0-2ed9-269d46938eb3}
    Followup: MachineOwner
    1: kd> !analyze -v
    * Bugcheck Analysis *
    VIDEO_DXGKRNL_FATAL_ERROR (113)
    The dxgkrnl has detected that a violation has occurred. This resulted
    in a condition that dxgkrnl can no longer progress. By crashing, dxgkrnl
    is attempting to get enough information into the minidump such that somebody
    can pinpoint the crash cause. Any other values after parameter 1 must be
    individually examined according to the subtype.
    Arguments:
    Arg1: 0000000000000017, The subtype of the bugcheck:
    Arg2: ffffe000b97f5010
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    Debugging Details:
    CUSTOMER_CRASH_COUNT: 1
    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
    BUGCHECK_STR: 0x113
    PROCESS_NAME: System
    CURRENT_IRQL: 0
    ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre
    LAST_CONTROL_TRANSFER: from fffff8001d99c9ca to fffff802d875afa0
    STACK_TEXT:
    ffffd000`20945a18 fffff800`1d99c9ca : 00000000`00000113 00000000`00000017 ffffe000`b97f5010 00000000`00000000 : nt!KeBugCheckEx
    ffffd000`20945a20 fffff800`1d82e990 : ffffe000`b97f5010 ffffe000`badcf880 ffffd000`20945a88 00000000`00000018 : watchdog!WdLogEvent5_WdCriticalError+0xce
    ffffd000`20945a60 fffff800`1f096e8c : ffffe000`b99f9000 00000000`00000001 00000000`00000000 00000000`00000000 : dxgkrnl!DXGADAPTER::SetPowerComponentActiveCB+0x44
    ffffd000`20945a90 ffffe000`b99f9000 : 00000000`00000001 00000000`00000000 00000000`00000000 ffffe000`c0a918e0 : igdkmd64+0x3be8c
    ffffd000`20945a98 00000000`00000001 : 00000000`00000000 00000000`00000000 ffffe000`c0a918e0 fffff800`1f093c22 : 0xffffe000`b99f9000
    ffffd000`20945aa0 00000000`00000000 : 00000000`00000000 ffffe000`c0a918e0 fffff800`1f093c22 ffffe000`c0689880 : 0x1
    STACK_COMMAND: kb
    FOLLOWUP_IP:
    dxgkrnl!DXGADAPTER::SetPowerComponentActiveCB+44
    fffff800`1d82e990 4869cf08020000 imul rcx,rdi,208h
    SYMBOL_STACK_INDEX: 2
    SYMBOL_NAME: dxgkrnl!DXGADAPTER::SetPowerComponentActiveCB+44
    FOLLOWUP_NAME: MachineOwner
    MODULE_NAME: dxgkrnl
    IMAGE_NAME: dxgkrnl.sys
    DEBUG_FLR_IMAGE_TIMESTAMP: 539a2a6c
    IMAGE_VERSION: 6.3.9600.17210
    BUCKET_ID_FUNC_OFFSET: 44
    FAILURE_BUCKET_ID: 0x113_dxgkrnl!DXGADAPTER::SetPowerComponentActiveCB
    BUCKET_ID: 0x113_dxgkrnl!DXGADAPTER::SetPowerComponentActiveCB
    ANALYSIS_SOURCE: KM
    FAILURE_ID_HASH_STRING: km:0x113_dxgkrnl!dxgadapter::setpowercomponentactivecb
    FAILURE_ID_HASH: {e8253e80-8827-02a0-2ed9-269d46938eb3}
    Followup: MachineOwner
    1: kd> lmvm dxgkrnl
    start end module name
    fffff800`1d818000 fffff800`1d999000 dxgkrnl (pdb symbols) c:\symbols\dxgkrnl.pdb\9D44B2A5938E41528DA86348D6D1F5C21\dxgkrnl.pdb
    Loaded symbol image file: dxgkrnl.sys
    Mapped memory image file: c:\symbols\dxgkrnl.sys\539A2A6C181000\dxgkrnl.sys
    Image path: \SystemRoot\System32\drivers\dxgkrnl.sys
    Image name: dxgkrnl.sys
    Timestamp: Thu Jun 12 18:32:12 2014 (539A2A6C)
    CheckSum: 00185C7C
    ImageSize: 00181000
    File version: 6.3.9600.17210
    Product version: 6.3.9600.17210
    File flags: 0 (Mask 3F)
    File OS: 40004 NT Win32
    File type: 3.7 Driver
    File date: 00000000.00000000
    Translations: 0409.04b0
    CompanyName: Microsoft Corporation
    ProductName: Microsoft® Windows® Operating System
    InternalName: dxgkrnl.sys
    OriginalFilename: dxgkrnl.sys
    ProductVersion: 6.3.9600.17210
    FileVersion: 6.3.9600.17210 (winblue_gdr.140612-1509)
    FileDescription: DirectX Graphics Kernel
    LegalCopyright: © Microsoft Corporation. All rights reserved.
    Wanikiya and Dyami--Team Zigzag

  • Ethernet not connecting when resuming from sleep/hibernate

    I use my mac (Win7) in clamshell mode quite often, and I leave the cables connected (ethernet, power, display, etc). I have noticed since installing the 3.0 Boot Camp drivers that the ethernet connection is not recognized after resuming from sleep/hibernate. I need to disconnect the cable and re-plug it in for the system to recognize the network. Anyone else seeing this?

    Look through Power Options for sleep and network. There should be sleep, low power, etc. And if possible, maybe you can manually update drivers from the vendor (not Apple). And if Windows or your update doesn't work as well, then you can just as easy use Device Manager and "rollback" the last driver upgrade - a great feature. Also, use those Create/Restore Check Points.
    I use to have trouble, got tired of having this issue, and bought a new modem to replace my 5 yr old model. Problem gone. Same can happen regarding routers, sometimes a firmware update, but I had one router that had been superceeded by 4th generation and no firmware patch anymore.

  • System locks up coming out of sleep/hibernate

    Hi,
    We have three Latitude E6430 notebooks running Windows 7 Enterprise x64. This is a licensed copy from MS and has not been customized in anyway by us. All three systems have the exact same configuration. Two of these systems lock up when we try to resume
    from sleep or hibernation. The logon prompt comes up but we are unable to enter the password or move the pointer around. The system has to be hard rebooted to get it functioning again. The third notebook that does not exhibit this issue has graphics driver
    v8.15.10.2639 but those same drivers do not resolve the issue on these two systems. We have tried updating the BIOS, chipset and graphics drivers but issue persists. Tried different graphics driver versions (from Dell support site and Intel) but no go. Dell
    sent motherboard and processor replacement for one of the systems but issue was not resolved. For testing, Dell tech support asked their engineer to install the OEM copy supplied by Dell (Windows 7 Professional x64) and the issue was not noticed. We then
    installed our Enterprise copy and issue's immediately back again.
    Issue occurs irrespective of how sleep/hibernate is triggered: manual, automatic (timed) or lid closure.
    Issue occurs irrespective of power source, AC power or only battery.
    Issue occurs even if lid close action is set to 'Turn Off Display' only.
    However, if hibernation is disabled the issue does not occur. System could be in sleep or with only the display turned off for hours and it still responds normally after waking up as long as hibernate is disabled.
    All three systems have,
    Intel Core i7-3540M Processor (Dual Core, 4M Cache, 3.0 GHz, w/HD Graphics 4000)
    8GB (2x4GB) 1600MHz DDR3L Memory
    500GB Solid State Hybrid Drive
    Any help would be much appreciated.
    Thanks, Muggy

    Hi,
    After waking form hiberbation, have you tried to unplug the mouse then re-plug it back in for a test. Meanwhile keep the latest drivers for the the mouse and keyboard.
    And untick this option: Allow the computer to turn off this device to save power in device manager\mouse and keyboard device\properties\power management.
    Please also perform a memory test and hard disk test with instructions in the following links
    Run Diagnostics to Check Your System for Memory Problems
    http://technet.microsoft.com/en-us/magazine/ff700221.aspx
    Check your hard disk for errors in Windows 7
    http://support.microsoft.com/kb/2641432/en-us
    Yolanda Zhu
    TechNet Community Support

  • Windows 8.1 pro WIFI issues

    After updating to windows 8.1 pro from windows 8.1 preview, wifi is showing "No internet access". no issue with router as it is working on other devices.
    Tried disable-enable.
    tried re install.
    tried updating driver.
    nothing seems to work.
    any help will be appreciated.
    Thank you. 

    Hi,
    According to your description, I suggest you try the following method to check the results.
    1:Boot into Safe Mode with networking.
    2:Disable Windows 8.1 fast startup feature, and turn off and turn on the computer to check the issue:
    Please refer to this article: Disable Windows 8 fast startup (hibernate file)
    http://nvidia.custhelp.com/app/answers/detail/a_id/3152/~/disable-windows-8-fast-startup-(hibernate-file)
    For all I know, the steps in this link also apply to Windows 8.1.
    Regards,
    Kelvin_Hsu
    TechNet Community Support

  • Windown 8.1 shuts down when I click on Sleep/Hibernate

    I  have recently installed windows 8.1 and i have noticed that every time I click on sleep/hibernate, it shuts down the laptop and I loose all my work. Please provide a solution for this.
    Thanks!

    every time I click on sleep/hibernate, it shuts down the laptop and I loose all my work.
    In my case of this symptom, I think there is a correlation with updating, so if I can remember to, I may try preventing network connections too.  I have also threatened to try using Scheduling to prevent unattended updating.  That was for Surface
    RT which explicitly does not allow a simpler GPO solution.  However, now that I have seen the same problem happen on Surface Pro I guess I should at least try the GPO solution on it.  Thanks for the reminder.   ; )
    http://answers.microsoft.com/en-us/surface/forum/surf2-surfupdate/a0-bugcheck/8fb37372-d10e-4978-bbe2-e7e95a83eaa3
    <quote>
    GPEdit finds in  Configure Automatic Updates   "Note: This policy does not apply to Windows RT."
    </quote>
    According to Event Viewer there was some kind of automatic updating done on my Surface Pro this morning and some kind of power problems but these details are even more obscure than they were on the Surface RT.  I should probably enable the same "highly
    detailed status messages" on the Surface Pro.
    Robert Aldwinckle

  • X200 cannot sleep/hibernate after WWAN has been used

    Since upgrading to Windows 7 I experience problem using Sleep or Hibernate.
    If I have been using WWAN (the Ericsson card) the computer will not Sleep or Hibernate afterwards (sometimes it will work, maybe 1 out of 10 times). The computer will start preparing for Sleep/Hibernate and will switch off the screen. But it never finished (caps lock will not work, but the HD LED can be seen blinking every 3 second or so) and will stay on until the battery is drained or a hard reset is performed.
    It was working ok in the beginning after installing Window 7, but stopped working somes in june/juli this year.
    /MF

    HI, thanks, but I know I can set a new password. I just wanted to get my old one back cos I have used it a long time & can therefore remember it.

  • Sleep, hibernate or off?

    Recently bought a T61, and so far everything seems to work well. Unlike the complaints I saw on various forums, Lenovo seems to be very efficient in product build-up and delivery (built my T61 on 12/28, and it was shipped on 12/31, received on 1/2). In order to take good care of my new laptop, I am wondering when the laptop is not in use, is it good to put it to sleep, hibernate or just turn it off? Thanks!

    Hello,
    In sleep mode, the computer powers down all of the components it can, slows down the rest and saves the state of the system (documents, running programs and so forth) in memory.  This allows it to resume very quickly, at the expense of continuing to use a trickle of current to power things.  If the power level becomes critical while in sleep mode, the computer goes into hibernation.
    In hibernation mode, the computer saves the state of the system to disk and powers down the system.  When power is re-applied, the system loads the machine state from the hibernation file on the disk.  This allows the applicatins and programs you were using after a longer period of time, but is slower to resume operation then sleep mode.
    Here are a couple of articles from Microsoft's web site that explain things in more detail:
    Turn off a computer:  Frequently Asked Questions
    Windows Vista Power Management (blog entry)
    From looking at the first link, Microsoft seems to recommend sleep mode for most computer usage scenarios, but if you are planning on not using the computer for more than a day then you might want to go with hibernation mode.
    Regards,
    Aryeh Goretsky
    I am a volunteer and neither a Lenovo nor a Microsoft employee. • Dexter is a good dog • Dexter je dobrý pes
    S230u (3347-4HU) • X220 (4286-CTO) • W510 (4318-CTO) • W530 (2441-4R3) • X100e (3508-CTO) • X120e (0596-CTO) • T61p (6459-CTO) • T43p (2678-H7U) • T42 (2378-R4U) • T23 (2648-LU7)
      Deutsche Community   Comunidad en Español Русскоязычное Сообщество

  • U2415, DaisyChain sleep/wakeup issue

    I recently bought 2 U2415 monitors, manufactured in Dec 2014 and daisy chained them to my laptop. I can't get them to respond after waking my laptop from sleep mode. There have been many posts on this display port sleep/wakeup issue, wasn't sure if it was affecting all monitors, or if its a cable issue,  or its a display firmware issue. I tried with different laptops and it's the same issue. I am currently using the stock cable provided by Dell.

    What are the 20 digit serial numbers?
    CN-0PVJVW-74261-4CP-11DL
    CN-0PVJVW-74261-4CN-0FNL
    Are both laptops DP 1.2 qualified?
    Yes both have Intel 4400 Graphics
    What specific laptops?
    HP elitebook and Dell inspiron
    Operating systems?
    Windows 7 and windows 8.1
    Video cards?
    Intel HD 4400
    Video card driver versions?
    10.18.10.3540
    DP or mDP out on the laptops?
    DP out

  • X201s not properly going to sleep / hibernate / shutdown mode and instead gets piping hot

    My 3.5 year old X201s that has been working like a charm has developed a nasty problem:
    None of the "normal" methods to get the system to "turn off" seems to be working any longer. The OS (Win7Pro-32bit) does its normal thing during  sleep / hibernate / shutdown, the screen eventually goes blank but the system never goes into the appropriate powered down state. The area under the CPU becomes hot and the system is totally unresponsive to Fn button, mouse button, lid opening, power button press.
    More specifically:
    "Start->Shutdown" or single Power button press results in battery LED solidly lit, no "beep". Systemis  unresponsive to subsequent normal power on.
    "Fn+F4 Sleep" or Close Lid  results in Battery and Moon LED solidly lit, single "beep". System is unresponsive to any subsequent normal wakeup attempts.
    "Fn+F4 Hibernate" results in Battery and Power and LED solidly lit, moon blinking, no "beep". System is unresponsive to any subsequent normal wakeup attempts.
    In all cases, I have to press and hold the power button for 5 sec (at which point all LEDs turn off as they should) to then be able to normally boot the system again. Upon booting, Windows does not complain of any improper shutdown and boots normally from scratch (sleep/shutdown scenario) and in the hibernate scenario, resumes properly.
    I have the latest BIOS and Thinkvantage updates installed, have turned off Blutooth, disabled "always-on USB" , have also uninstalled Thinkvantage Power Manager but have not seen any change.
    Reading some of the other threads on here about aging thermal paste and hot running CPUs, could this have fried some of my Power management circuitry?
    Could an overheated
    Any insight would be much appreciated!

    Some follow-up:
    - I applied the Intel ME firmware update 6.1.32.1076, see
    http://support.lenovo.com/en_US/detail.page?Legacy​DocID=MIGR-77175  
    but this did not fix anything.
    - Reinstalled latest Lenovo Power Manager and driver, - no luck.
    - Recovered original factory image, - still the same ill-behavior.
    Has anyone had experience with sending out of warranty laptops to Lenovo for repair (likely motherboard replacement)?

Maybe you are looking for