WIA and hibernation again

William B. Lurie wrote:
William B. Lurie wrote:
John John - MVP wrote:
William B. Lurie wrote:

But it's working...twice went 2 hours and hibernated.

So it's fixed?

John
I wish that were so, John, but I rechecked and am pretty
sure I had it set for 1 hour (cockpit error). I made two
runs this morning, carefully, making sure it was set for
1 hour, and with the two ATIs set for disabled, and again
with the 2 ATIs set for automatic, it recorded many many
normal events at start of the run, and absolutely no events
when I terminated each run after 2+ hours.

I will now try ATI services on manual. Cancel my glowing
report. One hour has always been good.

Well, I'm embarrassed and bloodied but unbowed. I can't find
settings for ATI and WIA to replicate the hibernation at 2 hours
report. I just have to disregard that as a mistake. But now to
recap.

On the plus side, John, your fix......I haven't seen an ati2-based
event since, so that has to be solid. But we can use this as a base
and move on. We feel that one of the 'services' is doing it, but
to cancel services one at a time and see what allows it to hibernate
and not kill something vital doesn't sound practical to me.
And I'm running all tests starting with Clean Boot, which is an
effort (and has its own inconsistencies in what msconfig shows and
does).

I'm curious enough to want to take my third drive (with another clone
on it) and do *only* the ATI error fix, and see what happens. It gives
us another test bed to work in, one that hasn't had a potful of messing
around with. I think I'll set that up to run, and maybe this evening
it will tell something (probably not), and by then maybe you hearty
help-mates will give me some more advice.

I did just that. And it was informative. See the
Systems Events Log which I'll post he

Type Date Time Source Category Event User Computer
Error 4/4/2010 6:49:38 PM W32Time None 29 N/A COMPAQ-2006
Error 4/4/2010 6:49:38 PM W32Time None 17 N/A COMPAQ-2006
Information 4/4/2010 6:49:22 PM Service Control Manager None 7036 N/A COMPAQ-2006
Error 4/4/2010 6:49:19 PM ati2mtag CRT 45062 N/A COMPAQ-2006
Error 4/4/2010 6:21:34 PM W32Time None 29 N/A COMPAQ-2006
Error 4/4/2010 6:21:34 PM W32Time None 17 N/A COMPAQ-2006
Error 4/4/2010 6:06:33 PM W32Time None 29 N/A COMPAQ-2006
Error 4/4/2010 6:06:33 PM W32Time None 17 N/A COMPAQ-2006
Information 4/4/2010 6:06:18 PM Service Control Manager None 7036 N/A COMPAQ-2006
Error 4/4/2010 6:06:14 PM ati2mtag CRT 45062 N/A COMPAQ-2006
Error 4/4/2010 5:20:19 PM W32Time None 29 N/A COMPAQ-2006
Error 4/4/2010 5:20:19 PM W32Time None 17 N/A COMPAQ-2006
Error 4/4/2010 5:05:19 PM W32Time None 29 N/A COMPAQ-2006
Error 4/4/2010 5:05:19 PM W32Time None 17 N/A COMPAQ-2006
Information 4/4/2010 5:05:01 PM Service Control Manager None 7036 N/A COMPAQ-2006
Error 4/4/2010 5:04:59 PM ati2mtag CRT 45062 N/A COMPAQ-2006
Information 4/4/2010 5:04:56 PM Tcpip None 4201 N/A COMPAQ-2006
Error 4/4/2010 4:17:08 PM W32Time None 29 N/A COMPAQ-2006
Error 4/4/2010 4:17:08 PM W32Time None 17 N/A COMPAQ-2006
Error 4/4/2010 3:47:08 PM W32Time None 29 N/A COMPAQ-2006
Error 4/4/2010 3:47:08 PM W32Time None 17 N/A COMPAQ-2006
Information 4/4/2010 3:32:42 PM Service Control Manager None 7036 N/A COMPAQ-2006
Information 4/4/2010 3:32:41 PM Service Control Manager None 7035 SYSTEM COMPAQ-2006
Information 4/4/2010 3:32:31 PM Service Control Manager None 7036 N/A COMPAQ-2006
Information 4/4/2010 3:32:31 PM Service Control Manager None 7036 N/A COMPAQ-2006
Information 4/4/2010 3:32:30 PM Service Control Manager None 7035 SYSTEM COMPAQ-2006
Information 4/4/2010 3:32:26 PM Service Control Manager None 7035 SYSTEM COMPAQ-2006
Information 4/4/2010 3:32:26 PM Service Control Manager None 7035 SYSTEM COMPAQ-2006
Information 4/4/2010 3:32:26 PM SRTSP None 2003 N/A COMPAQ-2006
Information 4/4/2010 3:32:11 PM Service Control Manager None 7036 N/A COMPAQ-2006
Information 4/4/2010 3:32:11 PM Service Control Manager None 7036 N/A COMPAQ-2006
Information 4/4/2010 3:32:11 PM Service Control Manager None 7036 N/A COMPAQ-2006
Information 4/4/2010 3:32:11 PM Service Control Manager None 7036 N/A COMPAQ-2006
Information 4/4/2010 3:32:11 PM Service Control Manager None 7035 SYSTEM COMPAQ-2006
Information 4/4/2010 3:32:11 PM Service Control Manager None 7035 SYSTEM COMPAQ-2006
Information 4/4/2010 3:32:11 PM Service Control Manager None 7035 Compaq_Owner COMPAQ-2006
Information 4/4/2010 3:32:11 PM Service Control Manager None 7036 N/A COMPAQ-2006
Information 4/4/2010 3:32:11 PM Service Control Manager None 7036 N/A COMPAQ-2006
Information 4/4/2010 3:32:11 PM Service Control Manager None 7035 SYSTEM COMPAQ-2006
Information 4/4/2010 3:32:11 PM Service Control Manager None 7036 N/A COMPAQ-2006
Information 4/4/2010 3:32:11 PM Service Control Manager None 7035 SYSTEM COMPAQ-2006
Error 4/4/2010 3:32:11 PM Service Control Manager None 7026 N/A COMPAQ-2006
Error 4/4/2010 3:32:08 PM W32Time None 29 N/A COMPAQ-2006
Error 4/4/2010 3:32:08 PM W32Time None 17 N/A COMPAQ-2006
Error 4/4/2010 3:31:53 PM W32Time None 29 N/A COMPAQ-2006
Error 4/4/2010 3:31:53 PM W32Time None 17 N/A COMPAQ-2006
Error 4/4/2010 3:30:40 PM ati2mtag CRT 45062 N/A COMPAQ-2006
Information 4/4/2010 3:30:20 PM Tcpip None 4201 N/A COMPAQ-2006
Information 4/4/2010 3:30:47 PM eventlog None 6005 N/A COMPAQ-2006
Information 4/4/2010 3:30:47 PM eventlog None 6009 N/A COMPAQ-2006
Information 4/4/2010 3:29:30 PM eventlog None 6006 N/A COMPAQ-2006
Information 4/4/2010 3:29:22 PM Service Control Manager None 7036 N/A COMPAQ-2006

Note that many many of the errors are due to W32Time, because,
disconnected from the line, it couldn't synchronize the system clock.
We don't worry about those. And everything at 3:47 PM and earlier are
part of the setting up.

Then we come to the ati2mtag Error at 5:04 .... I thought out ATI fix
would prevent that. And again at 6:06 .... and at 6:49 .... all ati2mtag
errors.

I think it was an interesting test. But a distraction from the
cleaner system on the first clone. What do you think I should do
next, John? Remember I am not able today to run a system and have
it hibernate at 2 hours. I'd love to get back to that status.

William B. Lurie wrote:

On the plus side, John, your fix......I haven't seen an ati2-based
event since, so that has to be solid. But we can use this as a base
and move on.

What is the make and model number of your video card? Is this a dual
monitor card? Is the monitor plugged into monitor 1?

John

William B. Lurie wrote:

I'm curious enough to want to take my third drive (with another clone
on it) and do *only* the ATI error fix, and see what happens.

Take your third drive and do a clean installation of Windows XP on it.
Enough fiddling about with clones...

John

John John - MVP wrote:
William B. Lurie wrote:

I'm curious enough to want to take my third drive (with another clone
on it) and do *only* the ATI error fix, and see what happens.

Take your third drive and do a clean installation of Windows XP on it.
Enough fiddling about with clones...

John
(A) I really can't do that, John. I didn't buy a retail XP, I
have nothing more than the working system, HP's on-board
recovery partition, and no CD. I have no way to start with
a clean installation. Even if I could, you know that I
have so many apps, I'd probably never end up with a
work-a-day system. Now to your other query (separately).

John John - MVP wrote:
William B. Lurie wrote:

On the plus side, John, your fix......I haven't seen an ati2-based
event since, so that has to be solid. But we can use this as a base
and move on.

What is the make and model number of your video card?

I'll see if I can dig that out. I think AIDA will list it, or
maybe StartControl Panel will lead me to it.

Is this a dual monitor card?
This is a simple middle-of-the-line OEM HP Presario system,
certainly with only one jack to connect a single monitor to.
I think the answer is negative.

Is the monitor plugged into monitor 1? It's plugged into the one and only
access jack.

John

John John - MVP wrote:
William B. Lurie wrote:

On the plus side, John, your fix......I haven't seen an ati2-based
event since, so that has to be solid. But we can use this as a base
and move on.

What is the make and model number of your video card?

**** From Device Manager: ATI Radeon XPRESS 200 Series
****
Is that it?

Is this a dual
monitor card? Is the monitor plugged into monitor 1?

John

John John - MVP wrote:
William B. Lurie wrote:

On the plus side, John, your fix......I haven't seen an ati2-based
event since, so that has to be solid. But we can use this as a base
and move on.

What is the make and model number of your video card? Is this a dual
monitor card? Is the monitor plugged into monitor 1?

John

A bit mo

"Installed driver: ati2dvag 6.14.10.6806"......

If I recall correctly, the error did not occur if ATI was disabled? It
hibernated with ATI disabled?
ATI stated all released levels of their driver experience the error. Can you
obtain a new video card and
driver and try it? Nvidia card?
"William B. Lurie" wrote in message
...
John John - MVP wrote:
William B. Lurie wrote:

I'm curious enough to want to take my third drive (with another clone
on it) and do *only* the ATI error fix, and see what happens.

Take your third drive and do a clean installation of Windows XP on it.
Enough fiddling about with clones...

John
(A) I really can't do that, John. I didn't buy a retail XP, I
have nothing more than the working system, HP's on-board
recovery partition, and no CD. I have no way to start with
a clean installation. Even if I could, you know that I
have so many apps, I'd probably never end up with a
work-a-day system. Now to your other query (separately).

Unknown wrote:
If I recall correctly, the error did not occur if ATI was disabled? It
hibernated with ATI disabled?
ATI stated all released levels of their driver experience the error. Can you
obtain a new video card and
driver and try it? Nvidia card?

UNk, as I mentioned to John yesterday, I have no video 'card' as such.
The drivers are in software supplied by HP with the machine. What I did
do was to get the latest issue of the Radeon 200 drivers and I've
been running for a week or more with no difference that I can detect.
It has always hibernated well when set for 1 hour, never when set
for 2 hours. It would be a can of worms for me to obtain a "new video
card and driver", unless you know some painless way. See the post I'm
about to send to John. It reaffirms my present status.

"William B. Lurie" wrote in message
...
John John - MVP wrote:
William B. Lurie wrote:

I'm curious enough to want to take my third drive (with another clone
on it) and do *only* the ATI error fix, and see what happens.
Take your third drive and do a clean installation of Windows XP on it.
Enough fiddling about with clones...

John
(A) I really can't do that, John. I didn't buy a retail XP, I
have nothing more than the working system, HP's on-board
recovery partition, and no CD. I have no way to start with
a clean installation. Even if I could, you know that I
have so many apps, I'd probably never end up with a
work-a-day system. Now to your other query (separately).

William B. Lurie wrote:
(snip)

You can set all the services to Manual start if you want but I don't
know if it will change anything, give it a try and find out. Keep
these three services to Automatic start:

Event Log
Plug & Play
Remote Procedure Call (RPC)

Set all the other services to manual or disabled. After you do this
try to hibernate the machine manually or in less than one hour (to
make sure that it can actually hibernate with the minimal set of
services).

John
Okay, John, will do....later.
But for now, I'd like to report that my clone system is
running, with clean boot, such that it does hibernate
at 1 hour, giving no unexplainable event msgs or errors,
and no sign of the dreaded ati2mtag or whatever it is.

I followed above procedures, John, with eminent success (so far).
Stripping down to just those few, it hibernated at two hours!
Did it twice to make sure.
So I changed the first ten to automatic and again, it hibernated at
two hours. I did it twice to be sure.
So I changed the next 15 or so, and it did NOT go to 2 hours. Here are
the Events. Critical timing is that it started at 7:43, should have
gone to 9:45, but things happened around 8:15, and desktop came on
and I discontinued, to capture Events Monitor and pass them along.
Perhaps you can interpret what they say, and tell me how to fix it,
maybe by disabling some culprit......or do I search one suspect at a
time until I find it? Got any clues? What is "Ci"?


Event Type: Information
Event Source: Ci
Event Category: CI Service
Event ID: 4103
Date: 4/6/2010
Time: 8:16:59 AM
User: N/A
Computer: COMPAQ-2006
Description:
Master merge has completed on c:\system volume information\catalog.wci.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


Type Date Time Source Category Event User Computer
Information 4/6/2010 8:16:59 AM Ci CI Service 4103 N/A COMPAQ-2006
Information 4/6/2010 8:16:30 AM Ci CI Service 4109 N/A COMPAQ-2006
Information 4/6/2010 7:43:57 AM Ci CI Service 4144 N/A COMPAQ-2006
Information 4/6/2010 7:43:57 AM Ci CI Service 4144 N/A COMPAQ-2006
Information 4/6/2010 7:43:56 AM Ci CI Service 4137 N/A COMPAQ-2006
Information 4/6/2010 7:43:22 AM Imapi Helper None 0 N/A COMPAQ-2006
Error 4/6/2010 7:41:42 AM COM+ (98) 4691 N/A COMPAQ-2006
Error 4/6/2010 7:41:42 AM MSDTC Client (10) 4427 N/A COMPAQ-2006
Information 4/6/2010 7:37:36 AM IDriverT None 0 N/A COMPAQ-2006
Warning 4/6/2010 12:15:07 AM EventSystem (54) 4353 N/A COMPAQ-2006
Warning 4/6/2010 12:15:07 AM EventSystem (52) 4356 N/A COMPAQ-2006
Warning 4/6/2010 12:15:07 AM EventSystem (54) 4353 N/A COMPAQ-2006
Warning 4/6/2010 12:15:07 AM EventSystem (52) 4356 N/A COMPAQ-2006
Information 4/6/2010 12:13:19 AM ASP.NET 2.0.50727.0 None 1076 N/A COMPAQ-2006


I can go back and narrow it down, but it would be nice to go back to the
state where it ran 2 hours, and add just whatever you think is the bad
actor.......

William B. Lurie wrote:
William B. Lurie wrote:
(snip)

You can set all the services to Manual start if you want but I don't
know if it will change anything, give it a try and find out. Keep
these three services to Automatic start:

Event Log
Plug & Play
Remote Procedure Call (RPC)

Set all the other services to manual or disabled. After you do this
try to hibernate the machine manually or in less than one hour (to
make sure that it can actually hibernate with the minimal set of
services).

John
Okay, John, will do....later.
But for now, I'd like to report that my clone system is
running, with clean boot, such that it does hibernate
at 1 hour, giving no unexplainable event msgs or errors,
and no sign of the dreaded ati2mtag or whatever it is.

I followed above procedures, John, with eminent success (so far).
Stripping down to just those few, it hibernated at two hours!
Did it twice to make sure.
So I changed the first ten to automatic and again, it hibernated at
two hours. I did it twice to be sure.

That is progress...


So I changed the next 15 or so, and it did NOT go to 2 hours.

And there is the clue to your problem. Keep notes of your changes and
keep on narrowing things down. One of these 15 services prevented
hibernation, keep on whittling the list down, cut out 8 of the 15
services and see if things change. If it does hibernate move on to the
other 7 services, if it doesn't hibernate cut the 8 services list down
to 4 and try it again... and so on until you pinpoint it down to the
culprit.


Here are
the Events. Critical timing is that it started at 7:43, should have
gone to 9:45, but things happened around 8:15, and desktop came on
and I discontinued, to capture Events Monitor and pass them along.
Perhaps you can interpret what they say, and tell me how to fix it,
maybe by disabling some culprit......or do I search one suspect at a
time until I find it? Got any clues? What is "Ci"?


Event Type: Information
Event Source: Ci
Event Category: CI Service Event ID: 4103
Date: 4/6/2010
Time: 8:16:59 AM
User: N/A
Computer: COMPAQ-2006
Description:
Master merge has completed on c:\system volume information\catalog.wci.

That is caused by the Indexing Service. If you want you can read about
the Master Merge in these search results:

http://search.yahoo.com/search;_ylt=...r2=sfp&iscqry=

You can disable the Indexing Service and see if things change.



I can go back and narrow it down, but it would be nice to go back to the
state where it ran 2 hours, and add just whatever you think is the bad
actor.......

I don't know who the bad actor is, you will have to keep on with the
trial and error and find that bad actor! Remember what I said
earlier... "sometimes you need dogged determination to get to the bottom
of some of these problems".

John

John John - MVP wrote:
William B. Lurie wrote:
William B. Lurie wrote:
(snip)

You can set all the services to Manual start if you want but I don't
know if it will change anything, give it a try and find out. Keep
these three services to Automatic start:

Event Log
Plug & Play
Remote Procedure Call (RPC)

Set all the other services to manual or disabled. After you do this
try to hibernate the machine manually or in less than one hour (to
make sure that it can actually hibernate with the minimal set of
services).

John
Okay, John, will do....later.
But for now, I'd like to report that my clone system is
running, with clean boot, such that it does hibernate
at 1 hour, giving no unexplainable event msgs or errors,
and no sign of the dreaded ati2mtag or whatever it is.

I followed above procedures, John, with eminent success (so far).
Stripping down to just those few, it hibernated at two hours!
Did it twice to make sure.
So I changed the first ten to automatic and again, it hibernated at
two hours. I did it twice to be sure.

That is progress...


So I changed the next 15 or so, and it did NOT go to 2 hours.

And there is the clue to your problem. Keep notes of your changes and
keep on narrowing things down. One of these 15 services prevented
hibernation, keep on whittling the list down, cut out 8 of the 15
services and see if things change. If it does hibernate move on to the
other 7 services, if it doesn't hibernate cut the 8 services list down
to 4 and try it again... and so on until you pinpoint it down to the
culprit.


Here are
the Events. Critical timing is that it started at 7:43, should have
gone to 9:45, but things happened around 8:15, and desktop came on
and I discontinued, to capture Events Monitor and pass them along.
Perhaps you can interpret what they say, and tell me how to fix it,
maybe by disabling some culprit......or do I search one suspect at a
time until I find it? Got any clues? What is "Ci"?


Event Type: Information
Event Source: Ci
Event Category: CI Service Event ID: 4103
Date: 4/6/2010
Time: 8:16:59 AM
User: N/A
Computer: COMPAQ-2006
Description:
Master merge has completed on c:\system volume information\catalog.wci.

That is caused by the Indexing Service. If you want you can read about
the Master Merge in these search results:

http://search.yahoo.com/search;_ylt=...r2=sfp&iscqry=


You can disable the Indexing Service and see if things change.



I can go back and narrow it down, but it would be nice to go back to the
state where it ran 2 hours, and add just whatever you think is the bad
actor.......

I don't know who the bad actor is, you will have to keep on with the
trial and error and find that bad actor! Remember what I said
earlier... "sometimes you need dogged determination to get to the bottom
of some of these problems".

John
Right, John, I agree heartily. It will take some time, but I will
go back to what was good (first batch of changes from base state)
and start adding. Index will be the first that I re-enable after
I get back to a good 2 hour run. The ball is in my court; I will
crawl along toward what I hope will be a solution.
Bill

William B. Lurie wrote:
John John - MVP wrote:
William B. Lurie wrote:
William B. Lurie wrote:
(snip)

You can set all the services to Manual start if you want but I
don't know if it will change anything, give it a try and find out.
Keep these three services to Automatic start:

Event Log
Plug & Play
Remote Procedure Call (RPC)

Set all the other services to manual or disabled. After you do
this try to hibernate the machine manually or in less than one hour
(to make sure that it can actually hibernate with the minimal set
of services).

John
Okay, John, will do....later.
But for now, I'd like to report that my clone system is
running, with clean boot, such that it does hibernate
at 1 hour, giving no unexplainable event msgs or errors,
and no sign of the dreaded ati2mtag or whatever it is.

I followed above procedures, John, with eminent success (so far).
Stripping down to just those few, it hibernated at two hours!
Did it twice to make sure.
So I changed the first ten to automatic and again, it hibernated at
two hours. I did it twice to be sure.

That is progress...


So I changed the next 15 or so, and it did NOT go to 2 hours.

And there is the clue to your problem. Keep notes of your changes and
keep on narrowing things down. One of these 15 services prevented
hibernation, keep on whittling the list down, cut out 8 of the 15
services and see if things change. If it does hibernate move on to
the other 7 services, if it doesn't hibernate cut the 8 services list
down to 4 and try it again... and so on until you pinpoint it down to
the culprit.


Here are
the Events. Critical timing is that it started at 7:43, should have
gone to 9:45, but things happened around 8:15, and desktop came on
and I discontinued, to capture Events Monitor and pass them along.
Perhaps you can interpret what they say, and tell me how to fix it,
maybe by disabling some culprit......or do I search one suspect at a
time until I find it? Got any clues? What is "Ci"?


Event Type: Information
Event Source: Ci
Event Category: CI Service Event ID: 4103
Date: 4/6/2010
Time: 8:16:59 AM
User: N/A
Computer: COMPAQ-2006
Description:
Master merge has completed on c:\system volume information\catalog.wci.

That is caused by the Indexing Service. If you want you can read
about the Master Merge in these search results:

http://search.yahoo.com/search;_ylt=...r2=sfp&iscqry=


You can disable the Indexing Service and see if things change.



I can go back and narrow it down, but it would be nice to go back to the
state where it ran 2 hours, and add just whatever you think is the bad
actor.......

I don't know who the bad actor is, you will have to keep on with the
trial and error and find that bad actor! Remember what I said
earlier... "sometimes you need dogged determination to get to the
bottom of some of these problems".

John
Right, John, I agree heartily. It will take some time, but I will
go back to what was good (first batch of changes from base state)
and start adding. Index will be the first that I re-enable after
I get back to a good 2 hour run. The ball is in my court; I will
crawl along toward what I hope will be a solution.

Let us know what you find out!

John

John John - MVP wrote:
William B. Lurie wrote:
John John - MVP wrote:
William B. Lurie wrote:
William B. Lurie wrote:
(snip)

You can set all the services to Manual start if you want but I
don't know if it will change anything, give it a try and find
out. Keep these three services to Automatic start:

Event Log
Plug & Play
Remote Procedure Call (RPC)

Set all the other services to manual or disabled. After you do
this try to hibernate the machine manually or in less than one
hour (to make sure that it can actually hibernate with the minimal
set of services).

John
Okay, John, will do....later.
But for now, I'd like to report that my clone system is
running, with clean boot, such that it does hibernate
at 1 hour, giving no unexplainable event msgs or errors,
and no sign of the dreaded ati2mtag or whatever it is.

I followed above procedures, John, with eminent success (so far).
Stripping down to just those few, it hibernated at two hours!
Did it twice to make sure.
So I changed the first ten to automatic and again, it hibernated at
two hours. I did it twice to be sure.

That is progress...


So I changed the next 15 or so, and it did NOT go to 2 hours.

And there is the clue to your problem. Keep notes of your changes
and keep on narrowing things down. One of these 15 services
prevented hibernation, keep on whittling the list down, cut out 8 of
the 15 services and see if things change. If it does hibernate move
on to the other 7 services, if it doesn't hibernate cut the 8
services list down to 4 and try it again... and so on until you
pinpoint it down to the culprit.


Here are
the Events. Critical timing is that it started at 7:43, should have
gone to 9:45, but things happened around 8:15, and desktop came on
and I discontinued, to capture Events Monitor and pass them along.
Perhaps you can interpret what they say, and tell me how to fix it,
maybe by disabling some culprit......or do I search one suspect at a
time until I find it? Got any clues? What is "Ci"?


Event Type: Information
Event Source: Ci
Event Category: CI Service Event ID: 4103
Date: 4/6/2010
Time: 8:16:59 AM
User: N/A
Computer: COMPAQ-2006
Description:
Master merge has completed on c:\system volume
information\catalog.wci.

That is caused by the Indexing Service. If you want you can read
about the Master Merge in these search results:

http://search.yahoo.com/search;_ylt=...r2=sfp&iscqry=


You can disable the Indexing Service and see if things change.



I can go back and narrow it down, but it would be nice to go back to
the
state where it ran 2 hours, and add just whatever you think is the bad
actor.......

I don't know who the bad actor is, you will have to keep on with the
trial and error and find that bad actor! Remember what I said
earlier... "sometimes you need dogged determination to get to the
bottom of some of these problems".

John
Right, John, I agree heartily. It will take some time, but I will
go back to what was good (first batch of changes from base state)
and start adding. Index will be the first that I re-enable after
I get back to a good 2 hour run. The ball is in my court; I will
crawl along toward what I hope will be a solution.

Let us know what you find out!

John
Now 10 OM. I did as I said I would. Started with stripped, bare system.
Hibernation 2 hours okay.
I added Indexing *only*. It ran to 2 hours and hibernated perfectly.
No significant entries into events log.

In a way this was good news......and in another way, bad news.
Obvious next step. Keep Indexing Automatic along with your 3 basic
automatics, and start adding one at a time, the stuff that ended up,
in combination, causing the malfunction. Tedious......actually
tedious squared, or tedious factorial, I'm not sure which.

Your comments welcome, John, but the course seems pretty obvious.

William B. Lurie wrote:
John John - MVP wrote:
William B. Lurie wrote:
John John - MVP wrote:
William B. Lurie wrote:
William B. Lurie wrote:
(snip)

You can set all the services to Manual start if you want but I
don't know if it will change anything, give it a try and find
out. Keep these three services to Automatic start:

Event Log
Plug & Play
Remote Procedure Call (RPC)

Set all the other services to manual or disabled. After you do
this try to hibernate the machine manually or in less than one
hour (to make sure that it can actually hibernate with the
minimal set of services).

John
Okay, John, will do....later.
But for now, I'd like to report that my clone system is
running, with clean boot, such that it does hibernate
at 1 hour, giving no unexplainable event msgs or errors,
and no sign of the dreaded ati2mtag or whatever it is.

I followed above procedures, John, with eminent success (so far).
Stripping down to just those few, it hibernated at two hours!
Did it twice to make sure.
So I changed the first ten to automatic and again, it hibernated at
two hours. I did it twice to be sure.

That is progress...


So I changed the next 15 or so, and it did NOT go to 2 hours.

And there is the clue to your problem. Keep notes of your changes
and keep on narrowing things down. One of these 15 services
prevented hibernation, keep on whittling the list down, cut out 8
of the 15 services and see if things change. If it does hibernate
move on to the other 7 services, if it doesn't hibernate cut the 8
services list down to 4 and try it again... and so on until you
pinpoint it down to the culprit.


Here are
the Events. Critical timing is that it started at 7:43, should have
gone to 9:45, but things happened around 8:15, and desktop came on
and I discontinued, to capture Events Monitor and pass them along.
Perhaps you can interpret what they say, and tell me how to fix it,
maybe by disabling some culprit......or do I search one suspect at a
time until I find it? Got any clues? What is "Ci"?


Event Type: Information
Event Source: Ci
Event Category: CI Service Event ID: 4103
Date: 4/6/2010
Time: 8:16:59 AM
User: N/A
Computer: COMPAQ-2006
Description:
Master merge has completed on c:\system volume
information\catalog.wci.

That is caused by the Indexing Service. If you want you can read
about the Master Merge in these search results:

http://search.yahoo.com/search;_ylt=...r2=sfp&iscqry=


You can disable the Indexing Service and see if things change.



I can go back and narrow it down, but it would be nice to go back
to the
state where it ran 2 hours, and add just whatever you think is the bad
actor.......

I don't know who the bad actor is, you will have to keep on with the
trial and error and find that bad actor! Remember what I said
earlier... "sometimes you need dogged determination to get to the
bottom of some of these problems".

John
Right, John, I agree heartily. It will take some time, but I will
go back to what was good (first batch of changes from base state)
and start adding. Index will be the first that I re-enable after
I get back to a good 2 hour run. The ball is in my court; I will
crawl along toward what I hope will be a solution.

Let us know what you find out!

John
Now 10 OM. I did as I said I would. Started with stripped, bare system.
Hibernation 2 hours okay.
I added Indexing *only*. It ran to 2 hours and hibernated perfectly.
No significant entries into events log.

In a way this was good news......and in another way, bad news.
Obvious next step. Keep Indexing Automatic along with your 3 basic
automatics, and start adding one at a time, the stuff that ended up,
in combination, causing the malfunction. Tedious......actually
tedious squared, or tedious factorial, I'm not sure which.

Your comments welcome, John, but the course seems pretty obvious.

Follow-on next morning. I stretched too far. In addition to 5 basic
plus Indexing, I added five more, and it blew again. And it isn't
trivial to diagnose why, from the Log. Back to adding just one at a
time. More later.