Event viewer

http://en.wikipedia.org/wiki/IPsec Read Standards status

Important Information
Call AT&T for Help on IPSec AT&T is the one making the Error
I Believe it's Not Norton or Windows do it
But your .AT&T routers firewall is running IPsec with IPv6



"William B. Lurie" wrote in message
...
Bruce Chambers wrote:
William B. Lurie wrote:
You nice folks led me to Event Viewer not too long ago, and
in studying it, I find under Applications that Automatic Live
Update is being run every 3 hours. It isn't my Norton Anti-
Virus Live Update, and I do not allow Windows Live Update to
run. Or at least I think I have it set so that I run Windows
Update when I choose to do so.

How can I track down what is running so often, and preventing
my system from hibernating as a result?

Thank you.



Many applications now install automatic update "features," so it's a
bit hard to narrow it down. Do you have, for instance, Java or Acrobat
Reader installed? Both have automatic updates features that the computer
user is not warned about when installing them. Also, while I don't think
this is the cause in this particular case, do you have your WinXP clock
configured to automatically synchronize with an Internet time server?
(Haven't used WinXP for a couple of years, so I've forgotten some of the
details, such as the frequency of those checks.)

To try narrowing down which application is doing this, double-click
on the pertinent entry in the application log to see if it will identify
a specific executable file's name. You can also use MSConfig to see what
is starting with the computer. Also, just in case someone tried to be
clever, you can check for Scheduled Tasks that would show up in the usual
"Startup" locations.


Thanks for the added clues, Bruce. I do get notices about
downloading updates for Adobe Reader, but never Java. The
only clock reset that I have pings an atomic clock site,
but only on my request.

As I messaged, I found in Norton System Works a place
that ostensibly turns off auto updates, and I'll look
again tomorrow to see what happened overnight.

And it's back to hibernating after an hour so maybe
the intrusions have ceased.

http://en.wikipedia.org/wiki/IPsec Read Standards status

Important Information
Call AT&T for Help on IPSec AT&T is the one making the Error
I Believe it's Not Norton or Windows do it
But your .AT&T routers firewall is running IPsec with IPv6



"William B. Lurie" wrote in message
...
Bruce Chambers wrote:
William B. Lurie wrote:
You nice folks led me to Event Viewer not too long ago, and
in studying it, I find under Applications that Automatic Live
Update is being run every 3 hours. It isn't my Norton Anti-
Virus Live Update, and I do not allow Windows Live Update to
run. Or at least I think I have it set so that I run Windows
Update when I choose to do so.

How can I track down what is running so often, and preventing
my system from hibernating as a result?

Thank you.



Many applications now install automatic update "features," so it's a
bit hard to narrow it down. Do you have, for instance, Java or Acrobat
Reader installed? Both have automatic updates features that the computer
user is not warned about when installing them. Also, while I don't think
this is the cause in this particular case, do you have your WinXP clock
configured to automatically synchronize with an Internet time server?
(Haven't used WinXP for a couple of years, so I've forgotten some of the
details, such as the frequency of those checks.)

To try narrowing down which application is doing this, double-click
on the pertinent entry in the application log to see if it will identify
a specific executable file's name. You can also use MSConfig to see what
is starting with the computer. Also, just in case someone tried to be
clever, you can check for Scheduled Tasks that would show up in the usual
"Startup" locations.


Thanks for the added clues, Bruce. I do get notices about
downloading updates for Adobe Reader, but never Java. The
only clock reset that I have pings an atomic clock site,
but only on my request.

As I messaged, I found in Norton System Works a place
that ostensibly turns off auto updates, and I'll look
again tomorrow to see what happened overnight.

And it's back to hibernating after an hour so maybe
the intrusions have ceased.

http://www.att.com/esupport/search.j...01&x=22& y=10

"William B. Lurie" wrote in message
...
Gerry wrote:
William

http://www.eventid.net/display.asp?e...ri ty&phase=1
Thanks for the referral, Gerry. I appreciate your effort
to be helpful.....but I found nothing there that would help
me understand the source of the message, or lead me to a
solution. I surmise that I am just not up to it.

http://www.att.com/esupport/search.j...01&x=22& y=10

"William B. Lurie" wrote in message
...
Gerry wrote:
William

http://www.eventid.net/display.asp?e...ri ty&phase=1
Thanks for the referral, Gerry. I appreciate your effort
to be helpful.....but I found nothing there that would help
me understand the source of the message, or lead me to a
solution. I surmise that I am just not up to it.

On Feb 14, 7:03*am, "Gerry" wrote:
Jose

Do you have success audits enabled?

Obviously the answer is Yes; otherwise there would not be any reports!
The computer has Windows XP Home Edition installed. I have never altered
the default with regard to Auditing Entries. I realise as a result of
Peter's response that I could and that the Security tabs can be
displayed if a default is changed.http://www.dougknox.com/xp/tips/xp_security_tab.htm

What is the point in investigating a Success Audit? An Audit Failure
makes more sense because it is reporting some wrong. Understanding a
Failure could pinpoint what is causing a problem. I have seen Failures
in the past but not recently.


If I am not looking into a problem, I will turn all that stuff off.
It is extra I/O I don't need and would rather my CPU time be spent
doing things I want. I find no use for the constant logging of
routine events. I don't look at my Event Log unless I am suspicious
of a problem which is almost never - or trying to help someone else
with their problem which is often. My event logs are no longer
intellectually stimulating.

If other folks want to log all that stuff, more power to 'em. I just
chose not to! It is also possible that with my tinkering over the
years my XP has been installed, I changed some of the Event Log
settings so they may not match yours. Maybe we are not even talking
about the same things anymore.

Okay - I don't to get bogged down with it and would rather move on.

The OP still does't seem to be able to hibernate reliably, his screen
saver doesn't work, he does not have SP3, has not said the hotfix to
fix hibernating for SP2 was installed, and has not described the SP3
anomalies.

I think I'll just watch that for a while!

On Feb 14, 7:03*am, "Gerry" wrote:
Jose

Do you have success audits enabled?

Obviously the answer is Yes; otherwise there would not be any reports!
The computer has Windows XP Home Edition installed. I have never altered
the default with regard to Auditing Entries. I realise as a result of
Peter's response that I could and that the Security tabs can be
displayed if a default is changed.http://www.dougknox.com/xp/tips/xp_security_tab.htm

What is the point in investigating a Success Audit? An Audit Failure
makes more sense because it is reporting some wrong. Understanding a
Failure could pinpoint what is causing a problem. I have seen Failures
in the past but not recently.


If I am not looking into a problem, I will turn all that stuff off.
It is extra I/O I don't need and would rather my CPU time be spent
doing things I want. I find no use for the constant logging of
routine events. I don't look at my Event Log unless I am suspicious
of a problem which is almost never - or trying to help someone else
with their problem which is often. My event logs are no longer
intellectually stimulating.

If other folks want to log all that stuff, more power to 'em. I just
chose not to! It is also possible that with my tinkering over the
years my XP has been installed, I changed some of the Event Log
settings so they may not match yours. Maybe we are not even talking
about the same things anymore.

Okay - I don't to get bogged down with it and would rather move on.

The OP still does't seem to be able to hibernate reliably, his screen
saver doesn't work, he does not have SP3, has not said the hotfix to
fix hibernating for SP2 was installed, and has not described the SP3
anomalies.

I think I'll just watch that for a while!

Jose wrote:
On Feb 14, 7:03 am, "Gerry" wrote:
Jose

Do you have success audits enabled?
Obviously the answer is Yes; otherwise there would not be any reports!
The computer has Windows XP Home Edition installed. I have never altered
the default with regard to Auditing Entries. I realise as a result of
Peter's response that I could and that the Security tabs can be
displayed if a default is changed.http://www.dougknox.com/xp/tips/xp_security_tab.htm

What is the point in investigating a Success Audit? An Audit Failure
makes more sense because it is reporting some wrong. Understanding a
Failure could pinpoint what is causing a problem. I have seen Failures
in the past but not recently.


If I am not looking into a problem, I will turn all that stuff off.
It is extra I/O I don't need and would rather my CPU time be spent
doing things I want. I find no use for the constant logging of
routine events. I don't look at my Event Log unless I am suspicious
of a problem which is almost never - or trying to help someone else
with their problem which is often. My event logs are no longer
intellectually stimulating.

If other folks want to log all that stuff, more power to 'em. I just
chose not to! It is also possible that with my tinkering over the
years my XP has been installed, I changed some of the Event Log
settings so they may not match yours. Maybe we are not even talking
about the same things anymore.

Okay - I don't to get bogged down with it and would rather move on.

The OP still does't seem to be able to hibernate reliably, his screen
saver doesn't work, he does not have SP3, has not said the hotfix to
fix hibernating for SP2 was installed, and has not described the SP3
anomalies.

I think I'll just watch that for a while!

Jose, I'm willing to stop logging except while we're trouble-shooting.
I imagine I can find out how, but that's a side issue. The screen-saver
works *most* of the time, except when these events prevent it.
SP3 forced things on me that I didn't like and don't recall what
they were, and couldn't undo except by going back to SP2. One of them
I think had to do with automatic live update for Windows, which
I most assuredly resented. The hotfix you mentioned seems to be a KB fix
that I'd welcome a link to........

Jose wrote:
On Feb 14, 7:03 am, "Gerry" wrote:
Jose

Do you have success audits enabled?
Obviously the answer is Yes; otherwise there would not be any reports!
The computer has Windows XP Home Edition installed. I have never altered
the default with regard to Auditing Entries. I realise as a result of
Peter's response that I could and that the Security tabs can be
displayed if a default is changed.http://www.dougknox.com/xp/tips/xp_security_tab.htm

What is the point in investigating a Success Audit? An Audit Failure
makes more sense because it is reporting some wrong. Understanding a
Failure could pinpoint what is causing a problem. I have seen Failures
in the past but not recently.


If I am not looking into a problem, I will turn all that stuff off.
It is extra I/O I don't need and would rather my CPU time be spent
doing things I want. I find no use for the constant logging of
routine events. I don't look at my Event Log unless I am suspicious
of a problem which is almost never - or trying to help someone else
with their problem which is often. My event logs are no longer
intellectually stimulating.

If other folks want to log all that stuff, more power to 'em. I just
chose not to! It is also possible that with my tinkering over the
years my XP has been installed, I changed some of the Event Log
settings so they may not match yours. Maybe we are not even talking
about the same things anymore.

Okay - I don't to get bogged down with it and would rather move on.

The OP still does't seem to be able to hibernate reliably, his screen
saver doesn't work, he does not have SP3, has not said the hotfix to
fix hibernating for SP2 was installed, and has not described the SP3
anomalies.

I think I'll just watch that for a while!

Jose, I'm willing to stop logging except while we're trouble-shooting.
I imagine I can find out how, but that's a side issue. The screen-saver
works *most* of the time, except when these events prevent it.
SP3 forced things on me that I didn't like and don't recall what
they were, and couldn't undo except by going back to SP2. One of them
I think had to do with automatic live update for Windows, which
I most assuredly resented. The hotfix you mentioned seems to be a KB fix
that I'd welcome a link to........

On Feb 15, 9:24*am, "William B. Lurie" wrote:
Jose wrote:
On Feb 14, 7:03 am, "Gerry" wrote:
Jose

Do you have success audits enabled?
Obviously the answer is Yes; otherwise there would not be any reports!
The computer has Windows XP Home Edition installed. I have never altered
the default with regard to Auditing Entries. I realise as a result of
Peter's response that I could and that the Security tabs can be
displayed if a default is changed.http://www.dougknox.com/xp/tips/xp_security_tab.htm

What is the point in investigating a Success Audit? An Audit Failure
makes more sense because it is reporting some wrong. Understanding a
Failure could pinpoint what is causing a problem. I have seen Failures
in the past but not recently.

If I am not looking into a problem, I will turn all that stuff off.
It is extra I/O I don't need and would rather my CPU time be spent
doing things I want. *I find no use for the constant logging of
routine events. *I don't look at my Event Log unless I am suspicious
of a problem which is almost never - or trying to help someone else
with their problem which is often. *My event logs are no longer
intellectually stimulating.

If other folks want to log all that stuff, more power to 'em. I just
chose not to! *It is also possible that with my tinkering over the
years my XP has been installed, I changed some of the Event Log
settings so they may not match yours. *Maybe we are not even talking
about the same things anymore.

Okay - I don't to get bogged down with it and would rather move on.

The OP still does't seem to be able to hibernate reliably, his screen
saver doesn't work, he does not have SP3, has not said the hotfix to
fix hibernating for SP2 was installed, and has not described the SP3
anomalies.

I think I'll just watch that for a while!

Jose, I'm willing to stop logging except while we're trouble-shooting.
I imagine I can find out how, but that's a side issue. The screen-saver
works *most* of the time, except when these events prevent it.
SP3 forced things on me that I didn't like and don't recall what
they were, and couldn't undo except by going back to SP2. One of them
I think had to do with automatic live update for Windows, which
I most assuredly resented. The hotfix you mentioned seems to be a KB fix
that I'd welcome a link to........

I thought I sent all that aready - maybe to somebody else:

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

On Feb 15, 9:24*am, "William B. Lurie" wrote:
Jose wrote:
On Feb 14, 7:03 am, "Gerry" wrote:
Jose

Do you have success audits enabled?
Obviously the answer is Yes; otherwise there would not be any reports!
The computer has Windows XP Home Edition installed. I have never altered
the default with regard to Auditing Entries. I realise as a result of
Peter's response that I could and that the Security tabs can be
displayed if a default is changed.http://www.dougknox.com/xp/tips/xp_security_tab.htm

What is the point in investigating a Success Audit? An Audit Failure
makes more sense because it is reporting some wrong. Understanding a
Failure could pinpoint what is causing a problem. I have seen Failures
in the past but not recently.

If I am not looking into a problem, I will turn all that stuff off.
It is extra I/O I don't need and would rather my CPU time be spent
doing things I want. *I find no use for the constant logging of
routine events. *I don't look at my Event Log unless I am suspicious
of a problem which is almost never - or trying to help someone else
with their problem which is often. *My event logs are no longer
intellectually stimulating.

If other folks want to log all that stuff, more power to 'em. I just
chose not to! *It is also possible that with my tinkering over the
years my XP has been installed, I changed some of the Event Log
settings so they may not match yours. *Maybe we are not even talking
about the same things anymore.

Okay - I don't to get bogged down with it and would rather move on.

The OP still does't seem to be able to hibernate reliably, his screen
saver doesn't work, he does not have SP3, has not said the hotfix to
fix hibernating for SP2 was installed, and has not described the SP3
anomalies.

I think I'll just watch that for a while!

Jose, I'm willing to stop logging except while we're trouble-shooting.
I imagine I can find out how, but that's a side issue. The screen-saver
works *most* of the time, except when these events prevent it.
SP3 forced things on me that I didn't like and don't recall what
they were, and couldn't undo except by going back to SP2. One of them
I think had to do with automatic live update for Windows, which
I most assuredly resented. The hotfix you mentioned seems to be a KB fix
that I'd welcome a link to........

I thought I sent all that aready - maybe to somebody else:

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

Jose wrote:
On Feb 15, 9:24 am, "William B. Lurie" wrote:
Jose wrote:
On Feb 14, 7:03 am, "Gerry" wrote:
Jose
Do you have success audits enabled?
Obviously the answer is Yes; otherwise there would not be any reports!
The computer has Windows XP Home Edition installed. I have never altered
the default with regard to Auditing Entries. I realise as a result of
Peter's response that I could and that the Security tabs can be
displayed if a default is changed.http://www.dougknox.com/xp/tips/xp_security_tab.htm
What is the point in investigating a Success Audit? An Audit Failure
makes more sense because it is reporting some wrong. Understanding a
Failure could pinpoint what is causing a problem. I have seen Failures
in the past but not recently.
If I am not looking into a problem, I will turn all that stuff off.
It is extra I/O I don't need and would rather my CPU time be spent
doing things I want. I find no use for the constant logging of
routine events. I don't look at my Event Log unless I am suspicious
of a problem which is almost never - or trying to help someone else
with their problem which is often. My event logs are no longer
intellectually stimulating.
If other folks want to log all that stuff, more power to 'em. I just
chose not to! It is also possible that with my tinkering over the
years my XP has been installed, I changed some of the Event Log
settings so they may not match yours. Maybe we are not even talking
about the same things anymore.
Okay - I don't to get bogged down with it and would rather move on.
The OP still does't seem to be able to hibernate reliably, his screen
saver doesn't work, he does not have SP3, has not said the hotfix to
fix hibernating for SP2 was installed, and has not described the SP3
anomalies.
I think I'll just watch that for a while!
Jose, I'm willing to stop logging except while we're trouble-shooting.
I imagine I can find out how, but that's a side issue. The screen-saver
works *most* of the time, except when these events prevent it.
SP3 forced things on me that I didn't like and don't recall what
they were, and couldn't undo except by going back to SP2. One of them
I think had to do with automatic live update for Windows, which
I most assuredly resented. The hotfix you mentioned seems to be a KB fix
that I'd welcome a link to........

I thought I sent all that aready - maybe to somebody else:

http://support.microsoft.com/kb/909095
Thanks, I installed that KB item. Had not seen it before.

Jose wrote:
On Feb 15, 9:24 am, "William B. Lurie" wrote:
Jose wrote:
On Feb 14, 7:03 am, "Gerry" wrote:
Jose
Do you have success audits enabled?
Obviously the answer is Yes; otherwise there would not be any reports!
The computer has Windows XP Home Edition installed. I have never altered
the default with regard to Auditing Entries. I realise as a result of
Peter's response that I could and that the Security tabs can be
displayed if a default is changed.http://www.dougknox.com/xp/tips/xp_security_tab.htm
What is the point in investigating a Success Audit? An Audit Failure
makes more sense because it is reporting some wrong. Understanding a
Failure could pinpoint what is causing a problem. I have seen Failures
in the past but not recently.
If I am not looking into a problem, I will turn all that stuff off.
It is extra I/O I don't need and would rather my CPU time be spent
doing things I want. I find no use for the constant logging of
routine events. I don't look at my Event Log unless I am suspicious
of a problem which is almost never - or trying to help someone else
with their problem which is often. My event logs are no longer
intellectually stimulating.
If other folks want to log all that stuff, more power to 'em. I just
chose not to! It is also possible that with my tinkering over the
years my XP has been installed, I changed some of the Event Log
settings so they may not match yours. Maybe we are not even talking
about the same things anymore.
Okay - I don't to get bogged down with it and would rather move on.
The OP still does't seem to be able to hibernate reliably, his screen
saver doesn't work, he does not have SP3, has not said the hotfix to
fix hibernating for SP2 was installed, and has not described the SP3
anomalies.
I think I'll just watch that for a while!
Jose, I'm willing to stop logging except while we're trouble-shooting.
I imagine I can find out how, but that's a side issue. The screen-saver
works *most* of the time, except when these events prevent it.
SP3 forced things on me that I didn't like and don't recall what
they were, and couldn't undo except by going back to SP2. One of them
I think had to do with automatic live update for Windows, which
I most assuredly resented. The hotfix you mentioned seems to be a KB fix
that I'd welcome a link to........

I thought I sent all that aready - maybe to somebody else:

http://support.microsoft.com/kb/909095
Thanks, I installed that KB item. Had not seen it before.

On Feb 15, 11:07*am, "William B. Lurie" wrote:
Jose wrote:
On Feb 15, 9:24 am, "William B. Lurie" wrote:
Jose wrote:
On Feb 14, 7:03 am, "Gerry" wrote:
Jose
Do you have success audits enabled?
Obviously the answer is Yes; otherwise there would not be any reports!
The computer has Windows XP Home Edition installed. I have never altered
the default with regard to Auditing Entries. I realise as a result of
Peter's response that I could and that the Security tabs can be
displayed if a default is changed.http://www.dougknox.com/xp/tips/xp_security_tab.htm
What is the point in investigating a Success Audit? An Audit Failure
makes more sense because it is reporting some wrong. Understanding a
Failure could pinpoint what is causing a problem. I have seen Failures
in the past but not recently.
If I am not looking into a problem, I will turn all that stuff off.
It is extra I/O I don't need and would rather my CPU time be spent
doing things I want. *I find no use for the constant logging of
routine events. *I don't look at my Event Log unless I am suspicious
of a problem which is almost never - or trying to help someone else
with their problem which is often. *My event logs are no longer
intellectually stimulating.
If other folks want to log all that stuff, more power to 'em. I just
chose not to! *It is also possible that with my tinkering over the
years my XP has been installed, I changed some of the Event Log
settings so they may not match yours. *Maybe we are not even talking
about the same things anymore.
Okay - I don't to get bogged down with it and would rather move on.
The OP still does't seem to be able to hibernate reliably, his screen
saver doesn't work, he does not have SP3, has not said the hotfix to
fix hibernating for SP2 was installed, and has not described the SP3
anomalies.
I think I'll just watch that for a while!
Jose, I'm willing to stop logging except while we're trouble-shooting.
I imagine I can find out how, but that's a side issue. The screen-saver
works *most* of the time, except when these events prevent it.
SP3 forced things on me that I didn't like and don't recall what
they were, and couldn't undo except by going back to SP2. One of them
I think had to do with automatic live update for Windows, which
I most assuredly resented. The hotfix you mentioned seems to be a KB fix
that I'd welcome a link to........

I thought I sent all that aready - maybe to somebody else:

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

* Thanks, I installed that KB item. Had not seen it before.

Good.

Reboot, set your hibernate to something like 5 minutes and see how it
goes.

XP needs to think your system is idle before it will hibernate. If
you are running some scan (at least for me) the scan has to complete,
then the hibernate countdown starts.

Try not to troubleshoot too many things at once - just fix one thing
at a time.

On Feb 15, 11:07*am, "William B. Lurie" wrote:
Jose wrote:
On Feb 15, 9:24 am, "William B. Lurie" wrote:
Jose wrote:
On Feb 14, 7:03 am, "Gerry" wrote:
Jose
Do you have success audits enabled?
Obviously the answer is Yes; otherwise there would not be any reports!
The computer has Windows XP Home Edition installed. I have never altered
the default with regard to Auditing Entries. I realise as a result of
Peter's response that I could and that the Security tabs can be
displayed if a default is changed.http://www.dougknox.com/xp/tips/xp_security_tab.htm
What is the point in investigating a Success Audit? An Audit Failure
makes more sense because it is reporting some wrong. Understanding a
Failure could pinpoint what is causing a problem. I have seen Failures
in the past but not recently.
If I am not looking into a problem, I will turn all that stuff off.
It is extra I/O I don't need and would rather my CPU time be spent
doing things I want. *I find no use for the constant logging of
routine events. *I don't look at my Event Log unless I am suspicious
of a problem which is almost never - or trying to help someone else
with their problem which is often. *My event logs are no longer
intellectually stimulating.
If other folks want to log all that stuff, more power to 'em. I just
chose not to! *It is also possible that with my tinkering over the
years my XP has been installed, I changed some of the Event Log
settings so they may not match yours. *Maybe we are not even talking
about the same things anymore.
Okay - I don't to get bogged down with it and would rather move on.
The OP still does't seem to be able to hibernate reliably, his screen
saver doesn't work, he does not have SP3, has not said the hotfix to
fix hibernating for SP2 was installed, and has not described the SP3
anomalies.
I think I'll just watch that for a while!
Jose, I'm willing to stop logging except while we're trouble-shooting.
I imagine I can find out how, but that's a side issue. The screen-saver
works *most* of the time, except when these events prevent it.
SP3 forced things on me that I didn't like and don't recall what
they were, and couldn't undo except by going back to SP2. One of them
I think had to do with automatic live update for Windows, which
I most assuredly resented. The hotfix you mentioned seems to be a KB fix
that I'd welcome a link to........

I thought I sent all that aready - maybe to somebody else:

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

* Thanks, I installed that KB item. Had not seen it before.

Good.

Reboot, set your hibernate to something like 5 minutes and see how it
goes.

XP needs to think your system is idle before it will hibernate. If
you are running some scan (at least for me) the scan has to complete,
then the hibernate countdown starts.

Try not to troubleshoot too many things at once - just fix one thing
at a time.

Jose wrote:
On Feb 12, 6:10 am, "William B. Lurie" wrote:
You nice folks led me to Event Viewer not too long ago, and
in studying it, I find under Applications that Automatic Live
Update is being run every 3 hours. It isn't my Norton Anti-
Virus Live Update, and I do not allow Windows Live Update to
run. Or at least I think I have it set so that I run Windows
Update when I choose to do so.

How can I track down what is running so often, and preventing
my system from hibernating as a result?

Thank you.

Provide more information:

Minimize back and forth Q&A and eliminate guesswork and assumptions:

Click Start, Run and in the box enter:

msinfo32

Click OK, and when the System Summary info appears, click Edit, Select
All, Copy and then paste
back here.

There will be some personal information (like System Name and User
Name), and whatever appears to
be private information to you, just delete from the pasted
information.

What are your system settings regarding Hibernation? Mine is set to
hibernate after 30 minutes of inactivity, but I can also hibernate
anytime. Which does not work for you?

Has hibernation ever worked?

If you click Start, Turn Off Computer and press the Shift key, does
the Stand By button turn into a Hibernate button and then if you click
Hibernate does your system enter hibernation?

Let's see this event you see:

Look in the Event Viewer for clues around the time of the incident

Here is a method to post the specific information about individual
events.

To see the Event Viewer logs, click Start, Settings, Control Panel,
Administrative Tools, Event Viewer.

A shortcut to Event Viewer is to click Start, Run and in the box
enter:

%SystemRoot%\system32\eventvwr.msc

Click OK to launch the Event Viewer.

The most interesting logs are usually the Application and System.
Some logs may be almost or completely empty.
Not every event is a problem, some are informational messages that
things are working okay and some are warnings.
No event should defy reasonable explanation.

Each event is sorted by Date and Time. Errors will have red Xs,
Warnings will have yellow !s.
Information messages have white is. Not every Error or Warning event
means there is a serious issue.
Some are excusable at startup time when Windows is booting. Try to
find just the events at the date
and time around your problem.

If you double click an event, it will open a Properties windows with
more information. On the right are
black up and down arrow buttons to scroll through the open events. The
third button that looks like
two pages on top of each other is used to copy the event details to
your Windows clipboard.

When you find an interesting event that occurred around the time of
your issue, click the third button
under the up and down arrows to copy the details and then you can
paste the details (right click, Paste
or CTRL-V) the detail text back here for analysis.

To get a fresh start on any Event Viewer log, you can choose to clear
the log (backing up the log is offered),
then reproduce your issue, then look at just the events around the
time of your issue.

Okay, Jose, one mo' time:

Event Type: Error
Event Source: ati2mtag
Event Category: CRT
Event ID: 45062
Date: 2/16/2010
Time: 1:03:13 PM
User: N/A
Computer: COMPAQ-2006
Description:
CRT invalid display type
Data:
0000: 00 00 00 00 01 00 5a 00 ......Z.
0008: 2c 00 00 00 06 b0 00 c0 ,....°.À
0010: 00 00 00 00 00 00 00 00 ........
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........

The above is the Event that occurs every time the
Power Options is invoked (I think). How do I
find out what it doesn't like about my CRT?