From: William B. Lurie on
William B. Lurie wrote:
> 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 did the MDM correction, John. And I downloaded the ATI Catalyst v10.3
> full suite. I'll install it in my clone and see wha' hoppen. When I
> downloaded some time ago, they led me to a v10.2 Legacy suite that
> I didn't like (but I don't remember why).

And now the latest news...... I installed the full ATI downloaded
Catalyst system, did the Clean Boot and made a 2+ hour run. Results
below. The interruption every hour is still there. And the
Events errors are the same ati2mtag. Nothing else of consequence.
Run started 12:27 ... events occurred at 1:11 2:13 and then 2:49.
I will get the loaded module list, which I haven't done yet.
I thought new drivers would fix the ATI error.......

> These Windows services are started:
>
> COM+ Event System
> Cryptographic Services
> DCOM Server Process Launcher
> DHCP Client
> Event Log
> Fast User Switching Compatibility
> Help and Support
> IPSEC Services
> Network Connections
> Network Location Awareness (NLA)
> Plug and Play
> Protected Storage
> Remote Access Connection Manager
> Remote Procedure Call (RPC)
> Security Accounts Manager
> Server
> Shell Hardware Detection
> System Event Notification
> Telephony
> Terminal Services
> Themes
> Windows Audio
> Windows Firewall/Internet Connection Sharing (ICS)
> Windows Management Instrumentation
> Wireless Zero Configuration
> Workstation
>
> The command completed successfully.
>
> Image Name PID Services
> ========================= ====== =============================================
> System Idle Process 0 N/A
> System 4 N/A
> smss.exe 1200 N/A
> csrss.exe 1280 N/A
> winlogon.exe 1312 N/A
> services.exe 1356 Eventlog, PlugPlay
> lsass.exe 1368 PolicyAgent, ProtectedStorage, SamSs
> svchost.exe 1528 DcomLaunch, TermService
> svchost.exe 1624 RpcSs
> svchost.exe 1796 AudioSrv, CryptSvc, Dhcp, EventSystem,
> FastUserSwitchingCompatibility, helpsvc,
> lanmanserver, lanmanworkstation, Netman,
> Nla, RasMan, SENS, SharedAccess,
> ShellHWDetection, TapiSrv, Themes, winmgmt,
> WZCSVC
> explorer.exe 652 N/A
> ctfmon.exe 1416 N/A
> cmd.exe 1620 N/A
> tasklist.exe 2036 N/A
> wmiprvse.exe 1748 N/A
>
> Event Type: Error
> Event Source: ati2mtag
> Event Category: CRT
> Event ID: 45062
> Date: 4/2/2010
> Time: 2:13:08 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: ati2mtag
> Event Category: CRT
> Event ID: 45062
> Date: 4/2/2010
> Time: 2:13:08 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 ........
From: Unknown on
Do a Google search for 'CRT Event ID 45062'
"William B. Lurie" <billurie(a)nospam.net> wrote in message
news:OE4MLrp0KHA.4548(a)TK2MSFTNGP06.phx.gbl...
> William B. Lurie wrote:
>> 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 did the MDM correction, John. And I downloaded the ATI Catalyst v10.3
>> full suite. I'll install it in my clone and see wha' hoppen. When I
>> downloaded some time ago, they led me to a v10.2 Legacy suite that
>> I didn't like (but I don't remember why).
>
> And now the latest news...... I installed the full ATI downloaded
> Catalyst system, did the Clean Boot and made a 2+ hour run. Results below.
> The interruption every hour is still there. And the
> Events errors are the same ati2mtag. Nothing else of consequence.
> Run started 12:27 ... events occurred at 1:11 2:13 and then 2:49.
> I will get the loaded module list, which I haven't done yet.
> I thought new drivers would fix the ATI error.......
>
>> These Windows services are started:
>>
>> COM+ Event System
>> Cryptographic Services
>> DCOM Server Process Launcher
>> DHCP Client
>> Event Log
>> Fast User Switching Compatibility
>> Help and Support
>> IPSEC Services
>> Network Connections
>> Network Location Awareness (NLA)
>> Plug and Play
>> Protected Storage
>> Remote Access Connection Manager
>> Remote Procedure Call (RPC)
>> Security Accounts Manager
>> Server
>> Shell Hardware Detection
>> System Event Notification
>> Telephony
>> Terminal Services
>> Themes
>> Windows Audio
>> Windows Firewall/Internet Connection Sharing (ICS)
>> Windows Management Instrumentation
>> Wireless Zero Configuration
>> Workstation
>>
>> The command completed successfully.
>>
>> Image Name PID Services
>> ========================= ======
>> =============================================
>> System Idle Process 0 N/A
>> System 4 N/A
>> smss.exe 1200 N/A
>> csrss.exe 1280 N/A
>> winlogon.exe 1312 N/A
>> services.exe 1356 Eventlog, PlugPlay
>> lsass.exe 1368 PolicyAgent, ProtectedStorage, SamSs
>> svchost.exe 1528 DcomLaunch, TermService
>> svchost.exe 1624 RpcSs
>> svchost.exe 1796 AudioSrv, CryptSvc, Dhcp, EventSystem,
>> FastUserSwitchingCompatibility, helpsvc, lanmanserver,
>> lanmanworkstation, Netman, Nla, RasMan, SENS, SharedAccess,
>> ShellHWDetection, TapiSrv, Themes, winmgmt, WZCSVC
>> explorer.exe 652 N/A
>> ctfmon.exe 1416 N/A
>> cmd.exe 1620 N/A
>> tasklist.exe 2036 N/A
>> wmiprvse.exe 1748 N/A
>> Event Type: Error
>> Event Source: ati2mtag
>> Event Category: CRT Event ID: 45062
>> Date: 4/2/2010
>> Time: 2:13:08 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: ati2mtag
>> Event Category: CRT Event ID: 45062
>> Date: 4/2/2010
>> Time: 2:13:08 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 ........


From: Unknown on
Your problem has been reported to ATI and they stated it also occurs with
catalyst 7.9.
IE the problem occurs with every release level.
"Unknown" <unknown(a)unknown.kom> wrote in message
news:eTIBcKq0KHA.840(a)TK2MSFTNGP06.phx.gbl...
> Do a Google search for 'CRT Event ID 45062'
> "William B. Lurie" <billurie(a)nospam.net> wrote in message
> news:OE4MLrp0KHA.4548(a)TK2MSFTNGP06.phx.gbl...
>> William B. Lurie wrote:
>>> 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 did the MDM correction, John. And I downloaded the ATI Catalyst v10.3
>>> full suite. I'll install it in my clone and see wha' hoppen. When I
>>> downloaded some time ago, they led me to a v10.2 Legacy suite that
>>> I didn't like (but I don't remember why).
>>
>> And now the latest news...... I installed the full ATI downloaded
>> Catalyst system, did the Clean Boot and made a 2+ hour run. Results
>> below. The interruption every hour is still there. And the
>> Events errors are the same ati2mtag. Nothing else of consequence.
>> Run started 12:27 ... events occurred at 1:11 2:13 and then 2:49.
>> I will get the loaded module list, which I haven't done yet.
>> I thought new drivers would fix the ATI error.......
>>
>>> These Windows services are started:
>>>
>>> COM+ Event System
>>> Cryptographic Services
>>> DCOM Server Process Launcher
>>> DHCP Client
>>> Event Log
>>> Fast User Switching Compatibility
>>> Help and Support
>>> IPSEC Services
>>> Network Connections
>>> Network Location Awareness (NLA)
>>> Plug and Play
>>> Protected Storage
>>> Remote Access Connection Manager
>>> Remote Procedure Call (RPC)
>>> Security Accounts Manager
>>> Server
>>> Shell Hardware Detection
>>> System Event Notification
>>> Telephony
>>> Terminal Services
>>> Themes
>>> Windows Audio
>>> Windows Firewall/Internet Connection Sharing (ICS)
>>> Windows Management Instrumentation
>>> Wireless Zero Configuration
>>> Workstation
>>>
>>> The command completed successfully.
>>>
>>> Image Name PID Services =========================
>>> ====== =============================================
>>> System Idle Process 0 N/A System 4
>>> N/A smss.exe 1200 N/A csrss.exe
>>> 1280 N/A winlogon.exe 1312 N/A services.exe
>>> 1356 Eventlog, PlugPlay lsass.exe 1368 PolicyAgent,
>>> ProtectedStorage, SamSs svchost.exe 1528 DcomLaunch,
>>> TermService svchost.exe 1624 RpcSs svchost.exe
>>> 1796 AudioSrv, CryptSvc, Dhcp, EventSystem,
>>> FastUserSwitchingCompatibility, helpsvc, lanmanserver,
>>> lanmanworkstation, Netman, Nla, RasMan, SENS, SharedAccess,
>>> ShellHWDetection, TapiSrv, Themes, winmgmt, WZCSVC explorer.exe
>>> 652 N/A ctfmon.exe 1416 N/A cmd.exe
>>> 1620 N/A tasklist.exe 2036 N/A wmiprvse.exe
>>> 1748 N/A Event Type: Error
>>> Event Source: ati2mtag
>>> Event Category: CRT Event ID: 45062
>>> Date: 4/2/2010
>>> Time: 2:13:08 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: ati2mtag
>>> Event Category: CRT Event ID: 45062
>>> Date: 4/2/2010
>>> Time: 2:13:08 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 ........
>
>


From: William B. Lurie on
Dear UNk:
My system was and is way past Catalyst 7.9 ... The one
I just downloaded and installed is 10.3, and it replaces
an earlier one, in the 9 series (I haven't got the number handy).
Going back to a still earlier version is impractical. Where
would I find it, and shouldn't later versions have problems solved,
not introduced anew?(I know....two steps forward, one step back).

Right now I've taken John's avice and have 10.3 in place.....and
still giving the ati2mtag error.

BTW, I went to your link and saw a lot of fixing DCOM but I
didn't see fixing ati2mtag ...maybe I missed it.


Unknown wrote:
> Your problem has been reported to ATI and they stated it also occurs with
> catalyst 7.9.
> IE the problem occurs with every release level.
> "Unknown" <unknown(a)unknown.kom> wrote in message
> news:eTIBcKq0KHA.840(a)TK2MSFTNGP06.phx.gbl...
>> Do a Google search for 'CRT Event ID 45062'
>> "William B. Lurie" <billurie(a)nospam.net> wrote in message
>> news:OE4MLrp0KHA.4548(a)TK2MSFTNGP06.phx.gbl...
>>> William B. Lurie wrote:
>>>> 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 did the MDM correction, John. And I downloaded the ATI Catalyst v10.3
>>>> full suite. I'll install it in my clone and see wha' hoppen. When I
>>>> downloaded some time ago, they led me to a v10.2 Legacy suite that
>>>> I didn't like (but I don't remember why).
>>> And now the latest news...... I installed the full ATI downloaded
>>> Catalyst system, did the Clean Boot and made a 2+ hour run. Results
>>> below. The interruption every hour is still there. And the
>>> Events errors are the same ati2mtag. Nothing else of consequence.
>>> Run started 12:27 ... events occurred at 1:11 2:13 and then 2:49.
>>> I will get the loaded module list, which I haven't done yet.
>>> I thought new drivers would fix the ATI error.......
>>>
>>>> These Windows services are started:
>>>>
>>>> COM+ Event System
>>>> Cryptographic Services
>>>> DCOM Server Process Launcher
>>>> DHCP Client
>>>> Event Log
>>>> Fast User Switching Compatibility
>>>> Help and Support
>>>> IPSEC Services
>>>> Network Connections
>>>> Network Location Awareness (NLA)
>>>> Plug and Play
>>>> Protected Storage
>>>> Remote Access Connection Manager
>>>> Remote Procedure Call (RPC)
>>>> Security Accounts Manager
>>>> Server
>>>> Shell Hardware Detection
>>>> System Event Notification
>>>> Telephony
>>>> Terminal Services
>>>> Themes
>>>> Windows Audio
>>>> Windows Firewall/Internet Connection Sharing (ICS)
>>>> Windows Management Instrumentation
>>>> Wireless Zero Configuration
>>>> Workstation
>>>>
>>>> The command completed successfully.
>>>>
>>>> Image Name PID Services =========================
>>>> ====== =============================================
>>>> System Idle Process 0 N/A System 4
>>>> N/A smss.exe 1200 N/A csrss.exe
>>>> 1280 N/A winlogon.exe 1312 N/A services.exe
>>>> 1356 Eventlog, PlugPlay lsass.exe 1368 PolicyAgent,
>>>> ProtectedStorage, SamSs svchost.exe 1528 DcomLaunch,
>>>> TermService svchost.exe 1624 RpcSs svchost.exe
>>>> 1796 AudioSrv, CryptSvc, Dhcp, EventSystem,
>>>> FastUserSwitchingCompatibility, helpsvc, lanmanserver,
>>>> lanmanworkstation, Netman, Nla, RasMan, SENS, SharedAccess,
>>>> ShellHWDetection, TapiSrv, Themes, winmgmt, WZCSVC explorer.exe
>>>> 652 N/A ctfmon.exe 1416 N/A cmd.exe
>>>> 1620 N/A tasklist.exe 2036 N/A wmiprvse.exe
>>>> 1748 N/A Event Type: Error
>>>> Event Source: ati2mtag
>>>> Event Category: CRT Event ID: 45062
>>>> Date: 4/2/2010
>>>> Time: 2:13:08 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: ati2mtag
>>>> Event Category: CRT Event ID: 45062
>>>> Date: 4/2/2010
>>>> Time: 2:13:08 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 ........
>>
>
>
From: William B. Lurie on
Went there again, UN, and read many many posts, all
describing the same problem, and no solution I could find
other than going back to earlier versions (7). I doubt
that I could get it if I wanted it, and doubt that I'd
go way back and ignore what must have been real improvements
since then. Interesting that nobody has a solution, altho' I
though John was leading me to one. Let's believe in him; he
makes the most sense.

Unknown wrote:
> Do a Google search for 'CRT Event ID 45062'
> "William B. Lurie" <billurie(a)nospam.net> wrote in message
> news:OE4MLrp0KHA.4548(a)TK2MSFTNGP06.phx.gbl...
>> William B. Lurie wrote:
>>> 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 did the MDM correction, John. And I downloaded the ATI Catalyst v10.3
>>> full suite. I'll install it in my clone and see wha' hoppen. When I
>>> downloaded some time ago, they led me to a v10.2 Legacy suite that
>>> I didn't like (but I don't remember why).
>> And now the latest news...... I installed the full ATI downloaded
>> Catalyst system, did the Clean Boot and made a 2+ hour run. Results below.
>> The interruption every hour is still there. And the
>> Events errors are the same ati2mtag. Nothing else of consequence.
>> Run started 12:27 ... events occurred at 1:11 2:13 and then 2:49.
>> I will get the loaded module list, which I haven't done yet.
>> I thought new drivers would fix the ATI error.......
>>
>>> These Windows services are started:
>>>
>>> COM+ Event System
>>> Cryptographic Services
>>> DCOM Server Process Launcher
>>> DHCP Client
>>> Event Log
>>> Fast User Switching Compatibility
>>> Help and Support
>>> IPSEC Services
>>> Network Connections
>>> Network Location Awareness (NLA)
>>> Plug and Play
>>> Protected Storage
>>> Remote Access Connection Manager
>>> Remote Procedure Call (RPC)
>>> Security Accounts Manager
>>> Server
>>> Shell Hardware Detection
>>> System Event Notification
>>> Telephony
>>> Terminal Services
>>> Themes
>>> Windows Audio
>>> Windows Firewall/Internet Connection Sharing (ICS)
>>> Windows Management Instrumentation
>>> Wireless Zero Configuration
>>> Workstation
>>>
>>> The command completed successfully.
>>>
>>> Image Name PID Services
>>> ========================= ======
>>> =============================================
>>> System Idle Process 0 N/A
>>> System 4 N/A
>>> smss.exe 1200 N/A
>>> csrss.exe 1280 N/A
>>> winlogon.exe 1312 N/A
>>> services.exe 1356 Eventlog, PlugPlay
>>> lsass.exe 1368 PolicyAgent, ProtectedStorage, SamSs
>>> svchost.exe 1528 DcomLaunch, TermService
>>> svchost.exe 1624 RpcSs
>>> svchost.exe 1796 AudioSrv, CryptSvc, Dhcp, EventSystem,
>>> FastUserSwitchingCompatibility, helpsvc, lanmanserver,
>>> lanmanworkstation, Netman, Nla, RasMan, SENS, SharedAccess,
>>> ShellHWDetection, TapiSrv, Themes, winmgmt, WZCSVC
>>> explorer.exe 652 N/A
>>> ctfmon.exe 1416 N/A
>>> cmd.exe 1620 N/A
>>> tasklist.exe 2036 N/A
>>> wmiprvse.exe 1748 N/A
>>> Event Type: Error
>>> Event Source: ati2mtag
>>> Event Category: CRT Event ID: 45062
>>> Date: 4/2/2010
>>> Time: 2:13:08 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: ati2mtag
>>> Event Category: CRT Event ID: 45062
>>> Date: 4/2/2010
>>> Time: 2:13:08 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 ........
>
>