Much slower resume from standby after Windows Update?

[Gary Fritz]

I have a pretty new XP system, about 2 months old. So hopefully it hasn't
had enough time to collect large amounts of cruft yet.

I nearly always use Standby mode instead of shutting my system down. In
the past it woke pretty quickly from Standby -- maybe 20sec from "wiggle
the mouse" to "CRT turns on."

A few days ago I installed the latest updates from Windows Update. I
hadn't been there in a few weeks so there were several updates: KB922582,
KB919007, KB920685, KB920872, and KB890830.

Roughly since I installed those updates, my system takes MUCH longer to
resume from standby. It varies (it always has), but as an example this
morning it took almost 2.5 minutes before the CRT turned on. It's getting
so that Standby takes longer than a full boot!

I don't know 100% that the updates caused this, but I think that's when it
started. I probably installed some applications right around that time
too, but I wouldn't expect a normal app to slow down the wakeup process.

What would cause this? Is there a good way for me to find out what's
slowing it down and maybe speed it up again?

Thanks,
Gary

 

[Rock]

I have a pretty new XP system, about 2 months old. So hopefully it hasn't
had enough time to collect large amounts of cruft yet.

I nearly always use Standby mode instead of shutting my system down. In
the past it woke pretty quickly from Standby -- maybe 20sec from "wiggle
the mouse" to "CRT turns on."

A few days ago I installed the latest updates from Windows Update. I
hadn't been there in a few weeks so there were several updates: KB922582,
KB919007, KB920685, KB920872, and KB890830.

Roughly since I installed those updates, my system takes MUCH longer to
resume from standby. It varies (it always has), but as an example this
morning it took almost 2.5 minutes before the CRT turned on. It's getting
so that Standby takes longer than a full boot!

I don't know 100% that the updates caused this, but I think that's when it
started. I probably installed some applications right around that time
too, but I wouldn't expect a normal app to slow down the wakeup process.

What would cause this? Is there a good way for me to find out what's
slowing it down and maybe speed it up again?

Thanks,
Gary

You can uninstall the updates through add / remove programs one at a time to
see if one of them is the culprit.

 

[Ayush]

Use Hibernation instead of Standby [Save power and much better]

Some applications that run in background can be the cause. Which
applications you installed?

--

Ayush [ Be ''?'' Happy ]

|I have a pretty new XP system, about 2 months old. So hopefully it hasn't
| had enough time to collect large amounts of cruft yet.
|
| I nearly always use Standby mode instead of shutting my system down. In
| the past it woke pretty quickly from Standby -- maybe 20sec from "wiggle
| the mouse" to "CRT turns on."
|
| A few days ago I installed the latest updates from Windows Update. I
| hadn't been there in a few weeks so there were several updates: KB922582,
| KB919007, KB920685, KB920872, and KB890830.
|
| Roughly since I installed those updates, my system takes MUCH longer to
| resume from standby. It varies (it always has), but as an example this
| morning it took almost 2.5 minutes before the CRT turned on. It's getting
| so that Standby takes longer than a full boot!
|
| I don't know 100% that the updates caused this, but I think that's when it
| started. I probably installed some applications right around that time
| too, but I wouldn't expect a normal app to slow down the wakeup process.
|
| What would cause this? Is there a good way for me to find out what's
| slowing it down and maybe speed it up again?
|
| Thanks,
| Gary

 

[Gary Fritz]

Use Hibernation instead of Standby [Save power and much better]

I'm not too worried about the power usage. The front-panel LED on my PC
probably uses more power than it takes to keep the RAM alive.

Standby was always much faster on my last system, so that's what I've
always used. But I just tried Hibernate, and... it can't! I got a
"Windows System Error: Insufficient system resources exist to complete the
API." !

Some googling indicates that a hotfix (KB909095) *or* SP2 is supposed to
fix this, but I already have SP2. It seems to exhibit when you have more
than 1GB of RAM -- I have 2GB.

But http://support.microsoft.com/?kbid=909095 says the hotfix still applies
even you have SP2. I'll try installing it.

Some applications that run in background can be the cause. Which
applications you installed?

Many. But none that I can think of that would have been installed around
the time that the wakeups started taking so long.

You can uninstall the updates through add / remove programs one at a time
to see if one of them is the culprit.

Bleah. What a timewaster. Sounds like my best option, though... :-(

Gary

 

[Pop`]

Gary,

Updates, software installs, and even not doing anything sometimes can be the
cause of that. If Shut Downs (or hibernation) are problems, you can
sometimes clear those with Microsoft's User Profile Hive Cleaner
(UPHClean.exe). It repairs other things too, but it did help me once when
Hibernate refused to function (and I did have it switched on int he
settings). Hibernate was slow, but it did start to work.

Another big helper can be regmon from Sysintermals.com. It does NOT change
any registry settings in any way, but it DOES re-arrange the order of their
running when you use the "optimize" feature. After that, Hibernate started
to work normally.
Hibernate, BTW, is usually slower than Shut Down or Standby because it
has to physically write all of the os information to disk before it can
power off. There's nothign wrong with staying with Standby if you're not
having any problems with it.
I don't know the URL, but MS has a KB about your 2 Gig and Hibernate.
The error message you mention sounds like you need to increase the amount of
RAM Hibernate can use but there might be more to it than that. You have to
give it at least 2 Gig if you have 2 Gig of RAM since it might try to write
2 Gig of data to the drive when it Hibernates.

HTH
Pop`

Use Hibernation instead of Standby [Save power and much better]

I'm not too worried about the power usage. The front-panel LED on my
PC probably uses more power than it takes to keep the RAM alive.

Standby was always much faster on my last system, so that's what I've
always used. But I just tried Hibernate, and... it can't! I got a
"Windows System Error: Insufficient system resources exist to
complete the API." !

Some googling indicates that a hotfix (KB909095) *or* SP2 is supposed
to fix this, but I already have SP2. It seems to exhibit when you
have more than 1GB of RAM -- I have 2GB.

But http://support.microsoft.com/?kbid=909095 says the hotfix still
applies even you have SP2. I'll try installing it.

Some applications that run in background can be the cause. Which
applications you installed?

Many. But none that I can think of that would have been installed
around the time that the wakeups started taking so long.

You can uninstall the updates through add / remove programs one at a
time to see if one of them is the culprit.

Bleah. What a timewaster. Sounds like my best option, though... :-(

Gary

 

[Rock]

Use Hibernation instead of Standby [Save power and much better]

I'm not too worried about the power usage. The front-panel LED on my PC
probably uses more power than it takes to keep the RAM alive.

Standby was always much faster on my last system, so that's what I've
always used. But I just tried Hibernate, and... it can't! I got a
"Windows System Error: Insufficient system resources exist to complete
the
API." !

Some googling indicates that a hotfix (KB909095) *or* SP2 is supposed to
fix this, but I already have SP2. It seems to exhibit when you have more
than 1GB of RAM -- I have 2GB.

But http://support.microsoft.com/?kbid=909095 says the hotfix still
applies
even you have SP2. I'll try installing it.

Some applications that run in background can be the cause. Which
applications you installed?

Many. But none that I can think of that would have been installed around
the time that the wakeups started taking so long.

You can uninstall the updates through add / remove programs one at a time
to see if one of them is the culprit.

Bleah. What a timewaster. Sounds like my best option, though... :-(

Gary

The hotfix should help. I have read posts by others that said it did.

 

[Gary Fritz]

The hotfix should help. I have read posts by others that said it did.

I installed it, and sure enough I can hibernate now. With the large number
of apps I typically run, it takes well over a minute to restore the image,
but that's better than the 2.5mins++ I was seeing with Standby before.

However -- after installing the hotfix, I tried Standby again -- and now it
wakes up in about 7 seconds!!!

Don't ask me why the Hibernate hotfix speeds up Standby wakeup, but I'm not
complaining...

Gary

 

[Gary Fritz]

However -- after installing the hotfix, I tried Standby again -- and
now it wakes up in about 7 seconds!!!

Don't ask me why the Hibernate hotfix speeds up Standby wakeup, but
I'm not complaining...

Hm. Within 1 day, the 7 seconds had stretched to 20. Today (after 2 days)
it's up to 50 seconds. Not a good sign. Whatever the hotfix did to
shorten the wake-up time, it doesn't seem to be sticking... :-(

It's also possible I was mistaken in measuring the original 7 seconds. The
wake-up time seems to vary depending on how long it's been asleep! E.g. I
came into my office this morning and woke up the PC, and it took 50 seconds
to respond. Then I put it into standby again, and immediately woke it up
again, and... 7 seconds. Hm.

Gary

 

[Bob I]

Disconnect the network connection before you let it go to sleep. I will
guess the long wakeup is reestablishing the network connection.

 

[Gary Fritz]

Disconnect the network connection before you let it go to sleep. I
will guess the long wakeup is reestablishing the network connection.

Hm. And it would do that before the system was alive enough to e.g. turn
on the monitor? I can try that as a test, but I'm not going to unhook the
LAN every time I shut it down...

BTW in case I wasn't clear, the 7 / 20 / 50 etc seconds I'm quoting is when
the system first shows any sign of life -- monitor first clicks on, any
pending alarms play their sound, etc. It's not 7 seconds to see something
on the monitor, so it's not because the monitor is already warmed up.

Gary

 

[Bob I]

Until you determine what takes the time, you won't know what takes the time.