From: William B. Lurie on
Jose wrote:
> On Feb 14, 7:03 am, "Gerry" <ge...(a)nospam.com> 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........
From: JD on
William B. Lurie wrote:
> JD wrote:
>> William B. Lurie wrote:
>>> SNIP <
>>> **************************************************************
>>> I'd like to reopen this informative discussion, and add
>>> the details of three *events* which seem to be applicable
>>> to my system's failing to go to hibernate, and sometimes
>>> not even to Screen Saver (!). Any explanations will be
>>> appreciated.
>>> **********************************************************
>>> Event Type: Error
>>> Event Source: Service Control Manager
>>> Event Category: None
>>> Event ID: 7026
>>> Date: 2/15/2010
>>> Time: 6:06:25 AM
>>> User: N/A
>>> Computer: COMPAQ-2006
>>> Description:
>>> The following boot-start or system-start driver(s) failed to load:
>>> ftsata2
>>> KLIF
>>>
>>> For more information, see Help and Support Center at
>>> http://go.microsoft.com/fwlink/events.asp.
>>> ************************************************************
>>> Event Type: Failure Audit
>>> Event Source: Security
>>> Event Category: Policy Change
>>> Event ID: 615
>>> Date: 2/13/2010
>>> Time: 6:38:44 AM
>>> User: NT AUTHORITY\NETWORK SERVICE
>>> Computer: COMPAQ-2006
>>> Description:
>>> IPSec Services: IPSec Services failed to get the complete
>>> list of network interfaces on the machine. This can be a potential
>>> security hazard to the machine since some of the network interfaces
>>> may not get the protection as desired by the applied IPSec filters.
>>> Please run IPSec monitor snap-in to further diagnose the problem.
>>> *********************************************************************
>>> Event Type: Error
>>> Event Source: Service Control Manager
>>> Event Category: None
>>> Event ID: 7026
>>> Date: 2/15/2010
>>> Time: 6:06:25 AM
>>> User: N/A
>>> Computer: COMPAQ-2006
>>> Description:
>>> The following boot-start or system-start driver(s) failed to load:
>>> ftsata2
>>> KLIF
>>>
>>> For more information, see Help and Support Center at
>>> http://go.microsoft.com/fwlink/events.asp.
>>> ******************************************************
>>
>> Did you make any changes to your computer around the same time you
>> noticed your problems?
>>
>> I went to http://www.ask.com and entered the two programs that are not
>> loading:
>>
>> ftsata2
>>
>> http://www.file.net/process/ftsata2.sys.html
>>
>> http://forums11.itrc.hp.com/service/forums/questionanswer.do?admit=109447626+1266240824138+28353475&threadId=1163749
>>
>>
>> KLIF
>>
>> http://www.file.net/process/klif.sys.html
>>
>> Do you use any anti-malware or anti-spyware programs?
>>
> Yes, I have one anti-malware program installed but turned
> it off two weeks ago when this ATI stuff started. msconfig has it not
> loading on startup.

How about a couple of free programs that you run on demand? Take a look at:

Malwarebytes' Anti-Malware http://www.malwarebytes.org/mbam.php

SUPERAntiSpyware Free Edition http://www.superantispyware.com/

Download the free versions. That's all you need.

Read about them before you run them, make sure they won't conflict with
your current software (they shouldn't but you never know) and let's make
sure you machine is clean.

And if you've read along here, the logging of these errors default is
ON. Sometimes people reply here with great authority when they don't
really know what they're talking about.

I don't know what is causing your problem(s) but I'm trying to help you
to figure it out on your own. You know, teach a man to fish, don't just
give him a fish.

Maybe I missed your reply so I'll ask again. What changed on your
computer about the time you noticed these problems?

--
JD..
From: Jose on
On Feb 15, 9:24 am, "William B. Lurie" <billu...(a)nospam.net> wrote:
> Jose wrote:
> > On Feb 14, 7:03 am, "Gerry" <ge...(a)nospam.com> 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
From: William B. Lurie on
Jose wrote:
> On Feb 15, 9:24 am, "William B. Lurie" <billu...(a)nospam.net> wrote:
>> Jose wrote:
>>> On Feb 14, 7:03 am, "Gerry" <ge...(a)nospam.com> 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.
From: William B. Lurie on
JD wrote:
> William B. Lurie wrote:
>> JD wrote:
>>> William B. Lurie wrote:
>>>> SNIP <
>>>> **************************************************************
>>>> I'd like to reopen this informative discussion, and add
>>>> the details of three *events* which seem to be applicable
>>>> to my system's failing to go to hibernate, and sometimes
>>>> not even to Screen Saver (!). Any explanations will be
>>>> appreciated.
>>>> **********************************************************
>>>> Event Type: Error
>>>> Event Source: Service Control Manager
>>>> Event Category: None
>>>> Event ID: 7026
>>>> Date: 2/15/2010
>>>> Time: 6:06:25 AM
>>>> User: N/A
>>>> Computer: COMPAQ-2006
>>>> Description:
>>>> The following boot-start or system-start driver(s) failed to load:
>>>> ftsata2
>>>> KLIF
>>>>
>>>> For more information, see Help and Support Center at
>>>> http://go.microsoft.com/fwlink/events.asp.
>>>> ************************************************************
>>>> Event Type: Failure Audit
>>>> Event Source: Security
>>>> Event Category: Policy Change
>>>> Event ID: 615
>>>> Date: 2/13/2010
>>>> Time: 6:38:44 AM
>>>> User: NT AUTHORITY\NETWORK SERVICE
>>>> Computer: COMPAQ-2006
>>>> Description:
>>>> IPSec Services: IPSec Services failed to get the complete
>>>> list of network interfaces on the machine. This can be a potential
>>>> security hazard to the machine since some of the network interfaces
>>>> may not get the protection as desired by the applied IPSec filters.
>>>> Please run IPSec monitor snap-in to further diagnose the problem.
>>>> *********************************************************************
>>>> Event Type: Error
>>>> Event Source: Service Control Manager
>>>> Event Category: None
>>>> Event ID: 7026
>>>> Date: 2/15/2010
>>>> Time: 6:06:25 AM
>>>> User: N/A
>>>> Computer: COMPAQ-2006
>>>> Description:
>>>> The following boot-start or system-start driver(s) failed to load:
>>>> ftsata2
>>>> KLIF
>>>>
>>>> For more information, see Help and Support Center at
>>>> http://go.microsoft.com/fwlink/events.asp.
>>>> ******************************************************
>>>
>>> Did you make any changes to your computer around the same time you
>>> noticed your problems?
>>>
>>> I went to http://www.ask.com and entered the two programs that are not
>>> loading:
>>>
>>> ftsata2
>>>
>>> http://www.file.net/process/ftsata2.sys.html
>>>
>>> http://forums11.itrc.hp.com/service/forums/questionanswer.do?admit=109447626+1266240824138+28353475&threadId=1163749
>>>
>>>
>>>
>>> KLIF
>>>
>>> http://www.file.net/process/klif.sys.html
>>>
>>> Do you use any anti-malware or anti-spyware programs?
>>>
>> Yes, I have one anti-malware program installed but turned
>> it off two weeks ago when this ATI stuff started. msconfig has it not
>> loading on startup.
>
> How about a couple of free programs that you run on demand? Take a look at:
>
> Malwarebytes' Anti-Malware http://www.malwarebytes.org/mbam.php
>
> SUPERAntiSpyware Free Edition http://www.superantispyware.com/
>
> Download the free versions. That's all you need.
>
> Read about them before you run them, make sure they won't conflict with
> your current software (they shouldn't but you never know) and let's make
> sure you machine is clean.
>
> And if you've read along here, the logging of these errors default is
> ON. Sometimes people reply here with great authority when they don't
> really know what they're talking about.
>
> I don't know what is causing your problem(s) but I'm trying to help you
> to figure it out on your own. You know, teach a man to fish, don't just
> give him a fish.
>
> Maybe I missed your reply so I'll ask again. What changed on your
> computer about the time you noticed these problems?
>
I thought I mentioned that I *did* install MBAM, in this time
frame, but, suspecting it as the cause, I have removed it from ram
and from the start-up list, so it should not be the cause.
Ditto the other item previously recommended, installed, tried,
but disabled.