WIA and hibernation again [Windows XP Basics]

Prev: Pressing Change Password -button in WIN XP causes reboot
Next: Microsoft caught pirating somebody's patent again!!!

From: William B. Lurie on 1 Apr 2010 20:28

John John - MVP wrote:
> William B. Lurie wrote:
>> (snip)
>>
>>> At the command prompt do:
>>>
>>> sc config klif start= demand
>>> sc config ftsata2 start= demand
>>>
>>> You should get a ChangeServiceConfig message indicating success or
>>> failure.
>>>
>> Right. They both worked fine, and both showed 'Success'.
>> I hope that's good.
>
> Yes, thats good. The Event Viewer errors relating to these two drivers
> should now disappear.
>
>
>
>> I'll make another run with phone line disconnected,
>> but I've done that before. Meanwhile, you have a record of
>> what my Loaded Modules look like.....can you tell me which
>> ones I must absolutely not delete because the System won't function
>> without them? There aren't that many (I assume you're referring
>> to what the Task Manager shows me).
>
> Reboot the machine and give us a fresh list for the Net Start and
> Tasklist /svc commands.
>
> Keep checking the Event Log to see if new errors are being recorded, if
> you are lucky an event in the log might provide a clue that will lead to
> the cause of the problem. If there are no clues in the Event Log then
> you will have to look at the loaded modules for more clues. Weeding
> through the list of modules is significantly more arduous than disabling
> unneeded services. To see the loaded modules enter the following in the
> Start Menu Run box:
>
> msinfo32 /category SWEnvLoadedModules
>
> John
Okay, what might be good news. Maybe you can kill this one gremlin.

The run I started at 6:25 PM should have run to hibernate at 8:25.

Instead, when I came in to look at 8:05, my desktop was on.
So I discontinued at looked at Event Log. Sure enough, there was
one event (the only one at all) and it was at 7:49. If hibernate had
been set at 1 hr it would have done so. All consistent. This is an
event we've seen before (but not lately).

> Event Type: Error
> Event Source: ati2mtag
> Event Category: CRT
> Event ID: 45062
> Date: 4/1/2010
> Time: 7:49:25 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 ........

I've mentioned this error before but nobody latched onto
it. Since Screen Saver is an issue, maybe this is
the missing link. While I wait for your next comments,
I'll repeat last run exactly, but with screen saver 'none'.

From: John John - MVP on 1 Apr 2010 22:11

William B. Lurie wrote:
> John John - MVP wrote:
>> William B. Lurie wrote:
>>> (snip)
>>>
>>>> At the command prompt do:
>>>>
>>>> sc config klif start= demand
>>>> sc config ftsata2 start= demand
>>>>
>>>> You should get a ChangeServiceConfig message indicating success or
>>>> failure.
>>>>
>>> Right. They both worked fine, and both showed 'Success'.
>>> I hope that's good.
>>
>> Yes, thats good. The Event Viewer errors relating to these two
>> drivers should now disappear.
>>
>>
>>
>>> I'll make another run with phone line disconnected,
>>> but I've done that before. Meanwhile, you have a record of
>>> what my Loaded Modules look like.....can you tell me which
>>> ones I must absolutely not delete because the System won't function
>>> without them? There aren't that many (I assume you're referring
>>> to what the Task Manager shows me).
>>
>> Reboot the machine and give us a fresh list for the Net Start and
>> Tasklist /svc commands.
>>
>> Keep checking the Event Log to see if new errors are being recorded,
>> if you are lucky an event in the log might provide a clue that will
>> lead to the cause of the problem. If there are no clues in the Event
>> Log then you will have to look at the loaded modules for more clues.
>> Weeding through the list of modules is significantly more arduous than
>> disabling unneeded services. To see the loaded modules enter the
>> following in the Start Menu Run box:
>>
>> msinfo32 /category SWEnvLoadedModules
>>
>> John
> Okay, what might be good news. Maybe you can kill this one gremlin.
>
> The run I started at 6:25 PM should have run to hibernate at 8:25.
>
> Instead, when I came in to look at 8:05, my desktop was on.

6:25 to 8:05... that's less than your 2 hour set time to hibernate. It
won't hibernate if you disturb it before its designated hibernate time,
leave it alone for the full 2 hours. If you set the screen saver to
'None' then it's normal for the desktop to remain on.

> So I discontinued at looked at Event Log. Sure enough, there was
> one event (the only one at all) and it was at 7:49. If hibernate had
> been set at 1 hr it would have done so. All consistent. This is an
> event we've seen before (but not lately).
>
>> Event Type: Error
>> Event Source: ati2mtag
>> Event Category: CRT Event ID: 45062
>> Date: 4/1/2010
>> Time: 7:49:25 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 ........
>
> I've mentioned this error before but nobody latched onto
> it. Since Screen Saver is an issue, maybe this is
> the missing link. While I wait for your next comments,
> I'll repeat last run exactly, but with screen saver 'none'.

This at2mtag error was also discussed in an earlier post. It's a bug in
the ATI driver, the solution (which was published in a KB on the ATI
site) was to change a registry setting or roll back the drivers to an
earlier version. ATI has removed the KB article from their site but
even with the newer drivers some users are still seeing the error and
the registry edit is still recommended by experienced ATI users. You
can try the newest ATI drivers and see if it fixes the error, if it
doesn't you should do the registry edit. Get the drivers here:
http://support.amd.com/us/Pages/AMDSupportHub.aspx

John

From: William B. Lurie on 2 Apr 2010 08:03

John John - MVP wrote:
> William B. Lurie wrote:
>> John John - MVP wrote:
>>> William B. Lurie wrote:
>>>> (snip)
>>>>
>>>>> At the command prompt do:
>>>>>
>>>>> sc config klif start= demand
>>>>> sc config ftsata2 start= demand
>>>>>
>>>>> You should get a ChangeServiceConfig message indicating success or
>>>>> failure.
>>>>>
>>>> Right. They both worked fine, and both showed 'Success'.
>>>> I hope that's good.
>>>
>>> Yes, thats good. The Event Viewer errors relating to these two
>>> drivers should now disappear.
>>>
>>>
>>>
>>>> I'll make another run with phone line disconnected,
>>>> but I've done that before. Meanwhile, you have a record of
>>>> what my Loaded Modules look like.....can you tell me which
>>>> ones I must absolutely not delete because the System won't function
>>>> without them? There aren't that many (I assume you're referring
>>>> to what the Task Manager shows me).
>>>
>>> Reboot the machine and give us a fresh list for the Net Start and
>>> Tasklist /svc commands.
>>>
>>> Keep checking the Event Log to see if new errors are being recorded,
>>> if you are lucky an event in the log might provide a clue that will
>>> lead to the cause of the problem. If there are no clues in the Event
>>> Log then you will have to look at the loaded modules for more clues.
>>> Weeding through the list of modules is significantly more arduous
>>> than disabling unneeded services. To see the loaded modules enter
>>> the following in the Start Menu Run box:
>>>
>>> msinfo32 /category SWEnvLoadedModules
>>>
>>> John
>> Okay, what might be good news. Maybe you can kill this one gremlin.
>>
>> The run I started at 6:25 PM should have run to hibernate at 8:25.
>>
>> Instead, when I came in to look at 8:05, my desktop was on.
>
> 6:25 to 8:05... that's less than your 2 hour set time to hibernate. It
> won't hibernate if you disturb it before its designated hibernate time,
> leave it alone for the full 2 hours. If you set the screen saver to
> 'None' then it's normal for the desktop to remain on.
>
>
>> So I discontinued at looked at Event Log. Sure enough, there was
>> one event (the only one at all) and it was at 7:49. If hibernate had
>> been set at 1 hr it would have done so. All consistent. This is an
>> event we've seen before (but not lately).
>>
>>> Event Type: Error
>>> Event Source: ati2mtag
>>> Event Category: CRT Event ID: 45062
>>> Date: 4/1/2010
>>> Time: 7:49:25 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 ........
>>
>> I've mentioned this error before but nobody latched onto
>> it. Since Screen Saver is an issue, maybe this is
>> the missing link. While I wait for your next comments,
>> I'll repeat last run exactly, but with screen saver 'none'.
>
> This at2mtag error was also discussed in an earlier post. It's a bug in
> the ATI driver, the solution (which was published in a KB on the ATI
> site) was to change a registry setting or roll back the drivers to an
> earlier version. ATI has removed the KB article from their site but
> even with the newer drivers some users are still seeing the error and
> the registry edit is still recommended by experienced ATI users. You
> can try the newest ATI drivers and see if it fixes the error, if it
> doesn't you should do the registry edit. Get the drivers here:
> http://support.amd.com/us/Pages/AMDSupportHub.aspx
>
> John
>
I'm in a rush this morning, John, so I won't do useful checking
until after noon. But you're right, the ATI was indeed identified as
a culprit earlier, and I had difficulty removing the bug. Meanwhile
the overnight runs confirm ATI as the major intruder. I'll post the
evidence now and work more later.

> Type Date Time Source Category Event User Computer
> Error 4/2/2010 7:04:05 AM ati2mtag CRT 45062 N/A COMPAQ-2006
> Error 4/2/2010 6:02:37 AM ati2mtag CRT 45062 N/A COMPAQ-2006
> Error 4/2/2010 5:01:19 AM ati2mtag CRT 45062 N/A COMPAQ-2006
> Error 4/2/2010 4:00:00 AM ati2mtag CRT 45062 N/A COMPAQ-2006
> Error 4/2/2010 2:58:42 AM ati2mtag CRT 45062 N/A COMPAQ-2006
> Error 4/2/2010 1:57:25 AM ati2mtag CRT 45062 N/A COMPAQ-2006
> Error 4/2/2010 12:56:07 AM ati2mtag CRT 45062 N/A COMPAQ-2006
> Error 4/1/2010 11:54:47 PM ati2mtag CRT 45062 N/A COMPAQ-2006
> Error 4/1/2010 10:51:15 PM DCOM None 10005 Compaq_Owner COMPAQ-2006
> Error 4/1/2010 10:49:33 PM DCOM None 10005 Compaq_Owner COMPAQ-2006
> Error 4/1/2010 10:44:37 PM ati2mtag CRT 45062 N/A COMPAQ-2006
> Error 4/1/2010 9:52:11 PM ati2mtag CRT 45062 N/A COMPAQ-2006
> Information 4/1/2010 8:37:14 PM Service Control Manager None 7036 N/A COMPAQ-2006
> Information 4/1/2010 8:37:14 PM Service Control Manager None 7036 N/A COMPAQ-2006
> Information 4/1/2010 8:37:14 PM Service Control Manager None 7036 N/A COMPAQ-2006
> Information 4/1/2010 8:37:14 PM Service Control Manager None 7035 Compaq_Owner COMPAQ-2006
> Information 4/1/2010 8:37:14 PM Service Control Manager None 7036 N/A COMPAQ-2006
> Information 4/1/2010 8:37:14 PM Service Control Manager None 7036 N/A COMPAQ-2006
> Information 4/1/2010 8:37:14 PM Service Control Manager None 7036 N/A COMPAQ-2006
> Information 4/1/2010 8:37:14 PM Service Control Manager None 7036 N/A COMPAQ-2006
> Information 4/1/2010 8:37:14 PM Service Control Manager None 7035 SYSTEM COMPAQ-2006
> Information 4/1/2010 8:37:14 PM Service Control Manager None 7035 SYSTEM COMPAQ-2006
> Information 4/1/2010 8:37:14 PM Service Control Manager None 7035 SYSTEM COMPAQ-2006
> Information 4/1/2010 8:37:14 PM Service Control Manager None 7036 N/A COMPAQ-2006
> Error 4/1/2010 8:35:29 PM ntfs Disk 55 N/A COMPAQ-2006
> Error 4/1/2010 8:35:28 PM ntfs Disk 55 N/A COMPAQ-2006
> Information 4/1/2010 8:35:27 PM Tcpip None 4201 N/A COMPAQ-2006
> Information 4/1/2010 8:35:47 PM eventlog None 6005 N/A COMPAQ-2006
> Information 4/1/2010 8:35:47 PM eventlog None 6009 N/A COMPAQ-2006
> Information 4/1/2010 8:34:53 PM eventlog None 6006 N/A COMPAQ-2006
> Information 4/1/2010 8:34:52 PM Service Control Manager None 7036 N/A COMPAQ-2006

Event Type: Information
Event Source: Service Control Manager
Event Category: None
Event ID: 7036
Date: 4/1/2010
Time: 8:37:14 PM
User: N/A
Computer: COMPAQ-2006
Description:
The Remote Access Connection Manager service entered the running state.

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

Event Type: Error
Event Source: ati2mtag
Event Category: CRT
Event ID: 45062
Date: 4/1/2010
Time: 9:52:11 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 ........

Event Type: Error
Event Source: DCOM
Event Category: None
Event ID: 10005
Date: 4/1/2010
Time: 10:49:33 PM
User: COMPAQ-2006\Compaq_Owner
Computer: COMPAQ-2006
Description:
DCOM got error "The service cannot be started, either because it is
disabled or because it has no enabled devices associated with it. "
attempting to start the service MDM with arguments "" in order to run
the server:
{0C0A3666-30C9-11D0-8F20-00805F2CD064}

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

Event Type: Error
Event Source: DCOM
Event Category: None
Event ID: 10005
Date: 4/1/2010
Time: 10:51:15 PM
User: COMPAQ-2006\Compaq_Owner
Computer: COMPAQ-2006
Description:
DCOM got error "The service cannot be started, either because it is
disabled or because it has no enabled devices associated with it. "
attempting to start the service MDM with arguments "" in order to run
the server:
{0C0A3666-30C9-11D0-8F20-00805F2CD064}

(I don't recognize MDM but maybe that's due to running with
no Internet connection).

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

The ati story repeats before the 2 hour deadline time and time again.
The DCOM error is another matter. Comment if you like, I'll be back.....
and this time I *will* go after that driver upgrade or fix, which I
think I downloaded last time. Or maybe I reinstalled a substitute for
the original driver, a "Legacy" which they gave me. I recall I wasn't
happy with it, but now I have a good leader........

From: John John - MVP on 2 Apr 2010 09:55

William B. Lurie wrote:

> Event Type: Error
> Event Source: DCOM
> Event Category: None
> Event ID: 10005
> Date: 4/1/2010
> Time: 10:51:15 PM
> User: COMPAQ-2006\Compaq_Owner
> Computer: COMPAQ-2006
> Description:
> DCOM got error "The service cannot be started, either because it is
> disabled or because it has no enabled devices associated with it. "
> attempting to start the service MDM with arguments "" in order to run
> the server:
> {0C0A3666-30C9-11D0-8F20-00805F2CD064}
>
> (I don't recognize MDM but maybe that's due to running with
> no Internet connection).

MDM is the infamous Machine Debug Manager, something that hardly anyone
other than programmers need to be bothered with. See if Internet
Explorer or other programs are set to use it.

Ignore the title of this article and the problem that it addresses:

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

just go down where you see the 'Internet Options' screenshot and disable
MDM as shown:

3. Click to select the Disable script debugging (Internet Explorer) and
Disable script debugging (Other) check boxes, and then click to clear
the Display a notification about every script error check box.

Click Apply and OK when done.

John

From: William B. Lurie on 2 Apr 2010 12:14

First | Prev | Next | Last
Pages: 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32
Prev: Pressing Change Password -button in WIN XP causes reboot
Next: Microsoft caught pirating somebody's patent again!!!