Hibernate not working

[Industrial One]

This worked in the past on this very same computer, but then a couple
months later I noticed I couldn't hibernate anymore. If I try, the
computer will shut down and then turn back on with a message "Not
enough resources to complete the API." What's this about?

 

[BillW50]

In

This worked in the past on this very same computer, but then a couple
months later I noticed I couldn't hibernate anymore. If I try, the
computer will shut down and then turn back on with a message "Not
enough resources to complete the API." What's this about?

Are you running XP-SP2? Then you probably need this update.

KB909095
The computer occasionally does not hibernate and you receive an
"Insufficient System Resources Exist to Complete the API" error message
in Windows XP...

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

 

[mm]

In


Are you running XP-SP2? Then you probably need this update.

KB909095
The computer occasionally does not hibernate and you receive an
"Insufficient System Resources Exist to Complete the API" error message
in Windows XP...

I thought you folks knew everything, but it occurs to me: You didn't
google on the OP's error messsage/description, did you, to find this?
Is that what we pay you for?

 

[Industrial One]

In


Are you running XP-SP2? Then you probably need this update.

KB909095
The computer occasionally does not hibernate and you receive an
"Insufficient System Resources Exist to Complete the API" error message
in Windows XP...

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

I second mm's message. Although I don't remember this fix
specifically, I did search around google and try a couple fixes, none
of which worked. That page does not describe my problem. I can't
hibernate period, not just "occasionally" and I don't buy that shit
about memory. It worked before perfectly with 4GB of DD3 RAM on this
exact same machine.

Yes I am on SP2.

 

[BillW50]

In

I thought you folks knew everything, but it occurs to me: You didn't
google on the OP's error messsage/description, did you, to find this?
Is that what we pay you for?

Actually no, I didn't Google this. As I know KB909095 very well and I
have used it often myself. ;-)

 

[BillW50]

In

I second mm's message. Although I don't remember this fix
specifically, I did search around google and try a couple fixes, none
of which worked. That page does not describe my problem. I can't
hibernate period, not just "occasionally" and I don't buy that shit
about memory. It worked before perfectly with 4GB of DD3 RAM on this
exact same machine.

Yes I am on SP2.

I didn't buy it either. As mine was working perfectly fine with 2GB
before and then one day I couldn't hibernate either. Same error as you
get. I installed the patch anyway and the problem has never came back
again.

 

[Paul]

I second mm's message. Although I don't remember this fix
specifically, I did search around google and try a couple fixes, none
of which worked. That page does not describe my problem. I can't
hibernate period, not just "occasionally" and I don't buy that shit
about memory. It worked before perfectly with 4GB of DD3 RAM on this
exact same machine.

Yes I am on SP2.

I only know a few tidbits for stuff like this.

You can start with a copy of "dumppo". It's a small utility (13,072 bytes)
that runs in a command window.

ftp://ftp.microsoft.com/Products/Oemtest/v1.1/WOSTest/Tools/Acpi/dumppo.exe

If I run this command

dumppo cap

I get a line like this

System states supported.: S1 S3 S4 S5

S3 is suspend to RAM, while S4 is hibernate.

That state list, can be affected by the BIOS. You might find references
to S1, S1&S3 in the BIOS or the like. Changing the BIOS setting, can
prevent Windows from using the ACPI states denied by the BIOS. Sometimes,
something as simple as replacing the CMOS battery, can result in a loss
of full ACPI functionality.

Once you correct the BIOS setting, you can use "dumppo" to do an
"administrative override" and fix the list. There is an example
of doing that here.

http://forums.pcper.com/showthread.php?p=1825058&postcount=31

Other things you can look at, are the HAL currently being used.
Open Device Manager, click the "Computer" entry, and check to
see whether an ACPI HAL is in usage. For example, mine right now is:

ACPI Multiprocessor PC

and ACPI is the thing that gives the S1 S3 S4 S5 type states.

That doesn't explain your symptoms, but its a couple areas you
can quickly verify.

Paul

 

[SC Tom]

In

Actually no, I didn't Google this. As I know KB909095 very well and I have
used it often myself. ;-)

But they pay you? Cool! Where do I apply? I need a retirement job just to
buy gas

 

[mm]

In

Actually no, I didn't Google this. As I know KB909095 very well and I
have used it often myself. ;-)

My gosh, you do know everything!

 

[mm]

I only know a few tidbits for stuff like this.

You can start with a copy of "dumppo". It's a small utility (13,072 bytes)
that runs in a command window.

ftp://ftp.microsoft.com/Products/Oemtest/v1.1/WOSTest/Tools/Acpi/dumppo.exe

If I run this command

dumppo cap

I get a line like this

System states supported.: S1 S3 S4 S5

S3 is suspend to RAM, while S4 is hibernate.

That state list, can be affected by the BIOS. You might find references
to S1, S1&S3 in the BIOS or the like. Changing the BIOS setting, can
prevent Windows from using the ACPI states denied by the BIOS. Sometimes,
something as simple as replacing the CMOS battery, can result in a loss
of full ACPI functionality.

Wow, dummpo is great. I got:
E:\Downloads-ShouldBeXP>dumppo
dumppo: cap ps bs admin ac dc

E:\Downloads-ShouldBeXP>dumppo cap
power capabilties
System power capabilties
Power Button Present....: TRUE
Sleep Button Present....: TRUE
Lid Present.............: FALSE
System states supported.: S1 S4 S5
Hiber file reserved.....: TRUE
Thermal control.........: FALSE
CPU Throttle control....: TRUE
Processor min throttle..: 7
Processor trottle scale.: 100 (1%)
Some disk will spindown.: TRUE
System batteries present: FALSE
System batteries scale..: (G:0 C:0) (G:0 C:0) (G:0 C:0)
Ac on line wake ability.: Unspecified
Lid wake ability........: Unspecified
RTC wake ability........: S4 - hibernate
Min device wake.........: Unspecified
Default low latency wake: Unspecified

There are about 7 things up there that I didn't know, and about my own
computer. Now I just have to find out what they mean! If I can't
find it out by reading, I'll tell you which ones they are.

I will note that I'm missing s2 and s3! But stand-by and hibernate
work, so they must be other s numbers

Once you correct the BIOS setting, you can use "dumppo" to do an
"administrative override" and fix the list. There is an example
of doing that here.

http://forums.pcper.com/showthread.php?p=1825058&postcount=31

Good reading!

 

[BillW50]

In

My gosh, you do know everything!

ROTFL! No not really. I actually know very little. ;-)

 

[Roy]

I second mm's message. Although I don't remember this fix
specifically, I did search around google and try a couple fixes, none
of which worked. That page does not describe my problem. I can't
hibernate period, not just "occasionally" and I don't buy that shit
about memory. It worked before perfectly with 4GB of DD3 RAM on this
exact same machine.

Yes I am on SP2.

==
SP3 should help solve your "problem"...any legitimate reason for NOT
installing it?
==

 

[Roy]

This worked in the past on this very same computer, but then a couple
months later I noticed I couldn't hibernate anymore. If I try, the
computer will shut down and then turn back on with a message "Not
enough resources to complete the API." What's this about?

==
First thing I did with Windows XP was eliminate Hibernate as it is
PROBLEMATIC.
==

 

[BillW50]

In

==
SP3 should help solve your "problem"...any legitimate reason for NOT
installing it?
==

Well in my case, some of my XP computers does have only SP2. Three
reasons for this.

1) Some older applications doesn't work with SP3. One of them is OE6.
:-(

2) Some computers doesn't have enough storage for SP3 to install.
Especially 4GB SSD on the motherboard netbooks.

3) No new features as far as the user is concern. So why bother?

 

[BillW50]

In

==
First thing I did with Windows XP was eliminate Hibernate as it is
PROBLEMATIC.
==

When I get a computer that doesn't hibernate, I fix it so it does. Then
it does so for the entire life of the computer. ;-)

 

[Roy]

In


Well in my case, some of my XP computers does have only SP2. Three
reasons for this.

1) Some older applications doesn't work with SP3. One of them is OE6.
:-(

2) Some computers doesn't have enough storage for SP3 to install.
Especially 4GB SSD on the motherboard netbooks.

3) No new features as far as the user is concern. So why bother?

==
I still use OE6 every day with my computer. No problem with SP3 at
all.
==

 

[BillW50]

In

Which applications?
OE6 works here with SP3. I was using IE6 (and OE6), but finally bit
the bullet and went to IE8, which I think still uses "OE6" (and I am
using it right now).

I eventually (reluctantly) went over to IE8, since some sites were
complaining, and a few wouldn't even work, as I recall (and I think
online banking was one of them). But IE8 still uses OE6, I do
believe. (It has been updated in some of its DLLs, of course, but I
think it's still called OE6).

Note: I'm assuming by "OE6" you mean Outlook Express 6, which I think
was the last version released, anyway.

Yes, OE6 means Outlook Express v6. And what broke is compacting and it
can often fail with folders.dbx under SP3.

But what else did you find that didn't work with SP3 over there, Bill?

Microsoft's EWF for one. If you install SP3, EWF protection becomes
worthless.

In my case, I was kinda forced into it, to try to resolve (and did!)
an annoying, intermittent, svchost bug that was bugging the heck out
of me. And that "upgrade" resolved it, once and for all.
Otherwise I'd have probably been content to stick with SP2. Although
I think there are some applications that require SP3 now.

Everything found in SP3 can virtually be found in hot fixes as well.
Like while that KB909095 is already in SP3. But you can use KB909095
with SP2 if you rather do it that way.

 

[BillW50]

In

==
I still use OE6 every day with my computer. No problem with SP3 at
all.
==

OE6 has a nasty habit of crashing during compacting if you have SP3
installed with folder.dbx. I discovered some work around, but it does
work just fine with SP2. And Microsoft has no plans on fixing any SP3
bugs.

 

[Tim Meddick]

I also prefer OE6 as my email / newsreader client, and have had no problems
with it since upgrading to SP3 over two years ago.

I thought I'd also mention the fact that in my own computer's BIOS
settings, is one that relates to disabling the "Save-to-RAM Suspend
State" - if this setting *was* disabled, then "hibernate" would simply not
work and I suspect the error messages would be the same as you are
currently receiving.

I know that "Paul" had mentioned BIOS settings in his contributions to this
thread, and it is worth checking out the BIOS, don't you think?

==

Cheers, Tim Meddick, Peckham, London.

 

[BillW50]

In

I also prefer OE6 as my email / newsreader client, and have had no
problems with it since upgrading to SP3 over two years ago.

I never did either. Then one day, BINGO! All hell broke loose. Just like
hibernation worked fine for years and then out of the blue it didn't.

I thought I'd also mention the fact that in my own computer's BIOS
settings, is one that relates to disabling the "Save-to-RAM Suspend
State" - if this setting *was* disabled, then "hibernate" would
simply not work and I suspect the error messages would be the same as
you are currently receiving.

I know that "Paul" had mentioned BIOS settings in his contributions
to this thread, and it is worth checking out the BIOS, don't you
think?

Paul is very smart, no doubt about it. Although KB909095 will indeed
solve the problem I have no doubt as it always does.