WIA and hibernation again
in [Windows XP Basics]
|
Prev: Pressing Change Password -button in WIN XP causes reboot
Next: Microsoft caught pirating somebody's patent again!!!
From: John John - MVP on 4 Apr 2010 08:11 William B. Lurie wrote: > But it's working...twice went 2 hours and hibernated. So it's fixed? John
From: William B. Lurie on 4 Apr 2010 11:38 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.
From: William B. Lurie on 4 Apr 2010 15:12 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.
From: William B. Lurie on 4 Apr 2010 19:34 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 here: > 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.
From: John John - MVP on 4 Apr 2010 21:33
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 |