Thinkpads Forum

Hi Folks,

A couple months ago, my T400 stopped being able to hibernate. Now, when I try to hibernate, the screen goes blanks, the hard drive cranks for 10-15 seconds, and I get the login screen again (with all my programs still running, etc). It's as if I locked my screen.

I was messing around with services and stuff when this first happened (turning things off I didn't think I needed), but I'm not sure that's what caused the problem. I have since restored my services to their default states, but the problem persists. I have tried disabling and re-enabling hibernation, and deleting the hiberfil.sys file, all to no avail. There are no logs in the event viewer which indicate anything wrong relating to hibernation. The problem persists with clean booting (i.e. no startup programs, only microsoft services). Sleeping works just fine. No restore point is available from prior to when the problem started.

Anyone else have this problem? Any ideas on what I might do?

Thanks,
Allie

Win 7 Pro x64
T400 2764-CTO
Discrete Graphics
6 GB RAM
500 GB HDD
fully updated

I have what I think is a similar problem. I have discovered what I think is a solution to my problem, maybe it's related to yours. I cannot hibernate or sleep on a random basis since installing Win 7, more often than not I would have a problem. I have tried uninstalling Access Connections and other fixes I found around with Google, even shutting off wireless with the physical switch on the front of my X60s before trying to hibernate. Every thing I tried seemed to work, but then didn't. I finally discovered what was keeping me from hibernating. I have a mapped drive which sits on my router in a seagate freeagent dockstar network adapter. If the drive is available, I have no problem hibernating. If the network connection to the mapped drive is unavailable (which happens occasionally for unrelated reasons) then I cannot hibernate. Once I get mapped properly again, I am good to go. I suggest you check to see if there are any network resource that Windows is trying to connect or disconnect from/to. If it cannot, it may result in a hang while trying to sleep or hibernate. This has resolved my frustration in trying to troubleshoot this problem.

Mike

Try looking through the network adapter's "Wake on Link" settings; maybe some network activity is causing the machine to wake back up as soon as it goes to hibernate. Likewise, look in the BIOS for wake on battery operation settings. I once had my ancient desktop restart immediately after shutting down, which was due to improper wake on ______ settings (can't remember exactly what).

@colonel: thanks for the reply. All network adapters have their wake functions disabled, and wake timers are disabled in the power plan.

@mpcook: nice thought. i don't have any mapped drives. i do have a printer, which i've tried removing, but no joy.

any other ideas? this is killing me.

thanks,
allie

You could try to run system file checker -
http://www.sevenforums.com/tutorials/15 ... ecker.html

already ran sfc, should have mentioned that...

but JOY TO THE WORLD! I ran some random stuff I found about a similar problem in Vista, and, BANG! It works. Holy crap.

See http://social.technet.microsoft.com/for ... 53166adcc/ for the full ref, but in a nutshell:

First I ran disk partition to assign a drive letter to win 7's hidden partition, then I ran the following (thanks to darrell gorter):
1. Run CMD.EXE as administrator
2. Run the following command: bcdedit -enum all
Look for "Resume from Hibernate" in the output from the command above(example below):
Resume from Hibernate
---------------------
identifier {3d8d3081-33ac-11dc-9a41-806e6f6e6963}
device partition=C:
path \Windows\system32\winresume.exe
description Windows Vista (TM) Enterprise (recovered)
inherit {resumeloadersettings}
filedevice partition=C:
filepath \hiberfil.sys
pae Yes
debugoptionenabled No
3. Once you have found it, copy the value for identifier (in this example - {3d8d3081-33ac-11dc-9a41-806e6f6e6963})
4. Run the following command: bcdedit /deletevalue {3d8d3081-33ac-11dc-9a41-806e6f6e6963} inherit
5. Test hibernation

I have NO IDEA what BCD stores are. I can't believe this worked.

Aargh! Wait!

Turns out the BCDedit stuff *wasn't* the fix! The fix is assigning a drive letter to my hidden partition! This ties in with some other problems I've been having, I think: my machine is having trouble assigning drive letters to some USB devices (http://www.sevenforums.com/crashes-debu ... post878813), and when I hit F8 on startup, I don't get the safe boot menu (i just get a key stuck error).

So: any ideas now? Seems like windows is having trouble accessing certain volumes, or something like that? argh!

I have a similar issue on my x201, hibernating doesn't start sometimes after sleep when on battery, sometimes it "windows error recovery"s on restart (and i think can poweroff at random too). Not sure what the direct cause of all that is, but I have found disabling wake timers in the bios prevents the notebook from waking up from sleep in order to hibernate.

@6502: if assigning a drive letter to your hidden partition doesn't completely fix your problem, then our problems are quite different. I've *never* had any problems with sleep, and my hibernation behavior is *not* erratic. It *never* works, unless I assign a drive letter to the hidden parititon, in which case it *always* works. Disabling timers, etc, has nothing to do with my problem, unfortunately.

mpcook wrote:I have what I think is a similar problem. I have discovered what I think is a solution to my problem, maybe it's related to yours. I cannot hibernate or sleep on a random basis since installing Win 7, more often than not I would have a problem.....

As it turns out, I am still searching for a solution. The problem seems to go away for a while, then it returns. I suspect it is related to power settings, but I am still trying to solve!

Mike

@mpcook: I'm quite sure that our problems are not the same. I have no problem sleeping. My issues stem from something having to do with recognizing the hidden partition. When I move my BCD store to the C drive, my problems go away. Of course, that's not a good solution as bitlocker requires the BCD Store to be on the hidden partition.