• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Hibernation/Standby issue

BigMonty

Member
Whenever the computer goes to hibernation or standby mode it comes back right after 10 seconds. Not only the laptop does not stay in the hibernation, I have to restart the computer each time after I close the lid. Whenever I open the lid, the screen remains blank but I can see all the power lights are on. Only way i can use the machine is by shutting down by pressing the power button and restart all over again. It is really driving me crazy. Can any of the wonderful people around here help me?

By the way, I did all the following things and it still did not help.

1. Cleaned up with Ad-aware, Crap Cleaner, CleanUp
2. Run antivirus
3. I have run Hijack_this and fixed a win_logon DLL but still does not work.
4. Checked all the basic power options.
5. I have even gone to bios settings.

Even though I did the above things does not mean I did all the things right. I might have missed quite a few tricks. Any help would be highly appreciated.

Rusho
 
A lot of this depends on the specific brand of your notebook and its BIOS. I find hibernation to be an abomination - and not 100% reliable. Standby also has bugs. I have my notebook set so that when I close the lid, it simply shuts of the LCD display - nothing more. That is easily done in Windows Power Options, and can be tested by simply pressing the tiny button the lids pushes when it closes. It should just turn on and off.

Whether to power off or shut the lid is a choice based on a lot of factors, not the least of which is the time you expect to be away. For more than an hour - turn it off completely.

If you have all the settings correct and the screen remains back, check your screen saver settings. That also comes into play.
 
You don't mention the OS or level, but all of the issues I used to have with Hibernation went away went I went to XP SP2. Just a thought...
 
What brand/model notebook? As was stated ensure you're running the latest BIOS revision as this most likely a hardware related issue. If you dont have luck with your post here you may want to contact your OEM regarding this issue.
I find hibernation to be an abomination - and not 100% reliable.
So long as you have decent hardware it shouldn't be a problem. I've been using hibernation religiously since Windows 2000 and it's uncommon that I'll have a problem (I always go in/out of hibernation and rarely ever shut down). Notebooks I've had in that timeframe include an IBM thinkpad and 3 Dell Latitude notebooks (most currently a D610).

-Erik
 
So long as you have decent hardware it shouldn't be a problem. I've been using hibernation religiously since Windows 2000 and it's uncommon that I'll have a problem (I always go in/out of hibernation and rarely ever shut down). Notebooks I've had in that timeframe include an IBM thinkpad and 3 Dell Latitude notebooks (most currently a D610).

I've had the same experience. I use hibernation almost religiosly also and don't ever recall having a problem with it.

BTW my current notebook is a D610 also. Great machine.
 
One of the main reasons for this situation is the common Mix Up between Hibernation to Standby/Power saving,

Hibernation requires the computer to be SHUT OFF totally.

When you shut down the computer while Hibernation is On, the current state of the RAM is saved to the Hard Drive

When you switch the computer On, the system loads back the content of the RAM from the Hard Drive to the RAM and thus brings back the computer to the exact point of pervious shut down.

In other Words, Hibernation is NOT related to Standby/Power and there is no reason to confabulate.

Some Laptop has in the BIOS can be set to Go to Deep Power Saving and in the process they save a Snap Shot of the RAM as well, but it Not the way Windows work with Hibernation.

So if you have a Problem it probably due to some conflict between the Standby/Power saving setting in the Mobo BIOs, and a Windows Standby settings.

:sun:
 
BTW my current notebook is a D610 also. Great machine.
I liked the D600 form factor a bit better than the D610 (a little smaller, felt "better" hard to describe). But yes I agree it's a good machine. The D610 also has a Radeon X300, which wasnt an option on the D600...
 
Hibernation requires the computer to be SHUT OFF totally.

A clarification. It allows this, it does not require this. (For example, wake on lan is fully supported by hibernation, so the system is not totally off..)

Bill

 
Originally posted by: bsobel
Hibernation requires the computer to be SHUT OFF totally.

A clarification. It allows this, it does not require this. (For example, wake on lan is fully supported by hibernation, so the system is not totally off..)

Bill
To further Clarify.😉

If we want to be Orthodox about it, while using ATX Power supply you might say that as long as the computer is plugged to a "Live" 110VAC outlet the system is Never Totally Off. The ATX maintains live level of Voltage on certain part of the Mobo and if the Mobo is WOL ready it is one of parts that get Juice while the computer is Off.

However, when you switch the computer Off, the CPU, Memory, HD, Video, etc., they are all Off. Hibernation and WOL need this type of Off to work as designed.

A WOL capable NIC stays passively connected to the Network, and has hard coded into the its chipset a capacity to detect Magic Packet and then provide a change in Voltage status that is similar to what the On switch is doing, when the Magic Package is detected it would Switch On the computer.

In contrast under Standby/Power saving. The parts mentioned above might be set to a power reduction state but the computer is Not Off.

When a computer that is connected to a LAN lapses into Standby you do not need WOL (or Magic Packet) any action at the NIC's "door step" would Prompt it to get out of Standby, provided the Mobo's BIOS is set to Resume on PCI event.

You might find exception and mix and match in some Laptop since many manufacturers are desperate to save every drop of "Juice" and thus resort to creative setting that are propriety in nature.

:sun:
 
When a computer that is connected to a LAN lapses into Standby you do not need WOL (or Magic Packet) any action at the NIC's "door step" would Prompt it to get out of Standby, provided the Mobo's BIOS is set to Resume on PCI event.

Agreed with everything you said, except that people wind up running in a config like the above quote. In that mode any traffic wakes the machine, even dhcp requests from other clients, as such it's pretty useless...

Bill

 
Originally posted by: severtki
You don't mention the OS or level, but all of the issues I used to have with Hibernation went away went I went to XP SP2. Just a thought...


Thanks for your reply. My OS is XP service pack 2. It had been working fine for at least one year and now suddenly this.

http://www.cincomsmalltalk.com/userblog...iew?showComments=true&entry=3302843044

On the above link, I found quite a few people complain about this. I tried their method but no joy so far.
 
My machine is IBM Thinkpad R51. Its BIOS setting is kind of little bit different than my old machine. I will try to look into it again and let you know. BTW, thanks for your reply.
 
Originally posted by: spyordie007
BTW my current notebook is a D610 also. Great machine.
I liked the D600 form factor a bit better than the D610 (a little smaller, felt "better" hard to describe). But yes I agree it's a good machine. The D610 also has a Radeon X300, which wasnt an option on the D600...
I had a D600 for a short time before and I agree the form factor was a little better. Slightly thinner than the current design. The addition of 2 extra USB ports on the D610 made up for that though. Unfortunately mine does not the Radeon X300 card but just the Intel GMA. Good enough for the work I do on it, but bad for games.
 
Originally posted by: spyordie007
Good enough for the work I do on it, but bad for games.
I havent played any games on it; I just like the X300 chipset because I get the pretty GUI when I boot into Vista 😉

Blah blah blah rub it in why don't ya? I'm hoping at least some of the new visual effects will be available on the Intel GMA by the time Vista is released.

 
Originally posted by: JackMDS
The problem is with the term Wake On LAN (WOL).

Wake entails getting out of Sleep, which is more like getting out of Standby Mode.

Wake On LAN does not wake any thing, it would be more appropriate to call it: ?Start ON on LAN?, or ?Switch On on LAN?.

:sun:

P.S. If some one does not know how to use WOL see here, Wake On LAN (WOL) - Start a Network Computer Remotely from your Network or through the Internet.
I will explain it a little further, but it is off topic. WuOL/WOL is different in ACPI versions. MS supports ACPI 1.3 in W2K and XP. They have said in the past they will support 2.0 in Vista. In 1.3, WOL was supposed to only work from a Sleep state, per the spec. 3Com coded it that way and a 3Com 905B/C card would only wake if in a sleep state (Suspend). Intel, on the other hand, would wake from Off. Waking from Off is part of 2.0, but 1.3 says it will not wake from off, only sleep. Arrgggggggggg. So, older 3Com cards will on WuOL from Off, but Intel and Broadcom will.

(I purposely did not use S states and D states as I would have to find my old freaking notes on D0-D3 and S0-S5 or is it S6 - I think D0 is really "Off" but do not want to confuse it as I do not remember the exact states at the moment)
 
Back
Top