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 3 Apr 2010 09:30 William B. Lurie wrote: > William B. Lurie wrote: >> William B. Lurie wrote: >>> John John - MVP wrote: >>>> 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 >>> John, I believe you asked me to get this Loaded Modules list: >>> >>> (Sorry it's so long, but......) so I snipped it. >> >> Now results on Clone system with latest ATI driver and >> with your ATI error-out-of-your-hair fix, John: >> >> Ran the usual 2.3 hour attempt to hibernate. Started as always >> with clean boot and with emptied Events logs. After 2.3 hours, I >> jiggled the mouse and it came alive, as usual. It had not hibernated. >> There were *no* events in that interval, recorded in the Events Log. I >> checked Services and found I had set Error Reporting as Manual, Event Log >> Automatic, WIA Disabled. I checked Drivers and found ati2mtag Running. >> >> This was a good news-bad news thing to me, John. Good news that >> I didn't get the ATI Error. Good news that I didn't get *any* errors, >> but bad news that it didn't hibernate. It's after 10 PM now and >> I can't wait up to see what you're going to make of this (or what I sent >> earlier), and what to do next. I might as well set up the Clone >> to run again overnight, making sure I have everything set right. > Continuing on next morning. Overnight run, would have expected it to > be just a repeat of previous, since I made no changes. Not true, > but nothing *bad* showed up. See these: > >> 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 1516 DcomLaunch, TermService > svchost.exe 1624 RpcSs > svchost.exe 1780 AudioSrv, CryptSvc, Dhcp, EventSystem, > FastUserSwitchingCompatibility, helpsvc, > lanmanserver, lanmanworkstation, Netman, > Nla, RasMan, SENS, SharedAccess, > ShellHWDetection, TapiSrv, Themes, > winmgmt, > WZCSVC > explorer.exe 640 N/A > cmd.exe 1688 N/A > tasklist.exe 420 N/A > wmiprvse.exe > > Type Date Time Source Category Event User Computer > Information 4/2/2010 10:12:55 PM Service Control Manager > None 7036 N/A COMPAQ-2006 > Information 4/2/2010 10:12:55 PM Service Control Manager > None 7036 N/A COMPAQ-2006 > Information 4/2/2010 10:12:55 PM Service Control Manager > None 7036 N/A COMPAQ-2006 > Information 4/2/2010 10:12:55 PM Service Control Manager > None 7035 Compaq_Owner COMPAQ-2006 > Information 4/2/2010 10:12:55 PM Service Control Manager > None 7036 N/A COMPAQ-2006 > Information 4/2/2010 10:12:55 PM Service Control Manager > None 7036 N/A COMPAQ-2006 > Information 4/2/2010 10:12:55 PM Service Control Manager > None 7036 N/A COMPAQ-2006 > Information 4/2/2010 10:12:55 PM Service Control Manager > None 7036 N/A COMPAQ-2006 > Information 4/2/2010 10:12:55 PM Service Control Manager > None 7035 SYSTEM COMPAQ-2006 > Information 4/2/2010 10:12:55 PM Service Control Manager > None 7035 SYSTEM COMPAQ-2006 > Information 4/2/2010 10:12:55 PM Service Control Manager > None 7035 SYSTEM COMPAQ-2006 > Information 4/2/2010 10:12:55 PM Service Control Manager > None 7036 N/A COMPAQ-2006 > Information 4/2/2010 10:11:08 PM Tcpip None 4201 > N/A COMPAQ-2006 > Information 4/2/2010 10:11:26 PM eventlog None 6005 > N/A COMPAQ-2006 > Information 4/2/2010 10:11:26 PM eventlog None 6009 > N/A COMPAQ-2006 > Information 4/2/2010 10:10:34 PM eventlog None 6006 > N/A COMPAQ-2006 > Information 4/2/2010 10:10:33 PM Service Control Manager > None 7036 N/A COMPAQ-2006 > Information 4/2/2010 10:09:57 PM Service Control Manager > None 7036 N/A COMPAQ-2006 > Information 4/2/2010 10:09:57 PM Service Control Manager > None 7036 N/A COMPAQ-2006 > Information 4/2/2010 10:09:57 PM Service Control Manager > None 7036 N/A COMPAQ-2006 > Information 4/2/2010 10:09:57 PM Service Control Manager > None 7035 Compaq_Owner COMPAQ-2006 > Information 4/2/2010 10:09:57 PM Service Control Manager > None 7036 N/A COMPAQ-2006 > Information 4/2/2010 10:09:57 PM Service Control Manager > None 7036 N/A COMPAQ-2006 > Information 4/2/2010 10:09:57 PM Service Control Manager > None 7035 SYSTEM COMPAQ-2006 > Information 4/2/2010 10:09:57 PM Service Control Manager > None 7036 N/A COMPAQ-2006 > Information 4/2/2010 10:09:57 PM Service Control Manager > None 7036 N/A COMPAQ-2006 > Information 4/2/2010 10:09:57 PM Service Control Manager > None 7035 SYSTEM COMPAQ-2006 > Information 4/2/2010 10:09:57 PM Service Control Manager > None 7035 SYSTEM COMPAQ-2006 > Information 4/2/2010 10:09:57 PM Service Control Manager > None 7036 N/A COMPAQ-2006 > Information 4/2/2010 10:08:10 PM Tcpip None 4201 > N/A COMPAQ-2006 > Information 4/2/2010 10:08:29 PM eventlog None 6005 > N/A COMPAQ-2006 > Information 4/2/2010 10:08:29 PM eventlog None 6009 > N/A COMPAQ-2006 > Information 4/2/2010 9:52:13 PM eventlog None 6006 > N/A COMPAQ-2006 > Information 4/2/2010 9:50:01 PM Service Control Manager > None 7035 Compaq_Owner COMPAQ-2006 > > Event Type: Information > Event Source: Service Control Manager > Event Category: None > Event ID: 7035 > Date: 4/2/2010 > Time: 10:12:55 PM > User: COMPAQ-2006\Compaq_Owner > Computer: COMPAQ-2006 > Description: > The Remote Access Connection Manager service was successfully sent a > start control. > > For more information, see Help and Support Center at > http://go.microsoft.com/fwlink/events.asp. > > Notice, no ati2 problems. A lot of information calls but > no complaints or errors. But no sign of it going to hibernation. > So at first glance, we have it all fixed, but the goal we set > out for, we have not achieved. I'm going back there to see what happens > if I set it to hibernate after only 1 hour. Maybe you'll have some > comment...... I find it surprising that you installed new Catalyst drivers but that no ATI services or processes show up in the Net Start or Tasklist results... Did you go in Services.msc and disable them? See my other post about reinstalling the drivers. Also, do not use screen savers while you try to fix this. When you come back to the machine after two hours what do you see? Is the screen just black? Or...? John
From: William B. Lurie on 3 Apr 2010 10:35 John John - MVP wrote: > William B. Lurie wrote: >> William B. Lurie wrote: >>> William B. Lurie wrote: >>>> John John - MVP wrote: >>>>> 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 >>>> John, I believe you asked me to get this Loaded Modules list: >>>> >>>> (Sorry it's so long, but......) so I snipped it. >>> >>> Now results on Clone system with latest ATI driver and >>> with your ATI error-out-of-your-hair fix, John: >>> >>> Ran the usual 2.3 hour attempt to hibernate. Started as always >>> with clean boot and with emptied Events logs. After 2.3 hours, I >>> jiggled the mouse and it came alive, as usual. It had not hibernated. >>> There were *no* events in that interval, recorded in the Events Log. >>> I checked Services and found I had set Error Reporting as Manual, >>> Event Log >>> Automatic, WIA Disabled. I checked Drivers and found ati2mtag Running. >>> >>> This was a good news-bad news thing to me, John. Good news that >>> I didn't get the ATI Error. Good news that I didn't get *any* errors, >>> but bad news that it didn't hibernate. It's after 10 PM now and >>> I can't wait up to see what you're going to make of this (or what I sent >>> earlier), and what to do next. I might as well set up the Clone >>> to run again overnight, making sure I have everything set right. >> Continuing on next morning. Overnight run, would have expected it to >> be just a repeat of previous, since I made no changes. Not true, >> but nothing *bad* showed up. See these: >> >>> 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 1516 DcomLaunch, TermService >> svchost.exe 1624 RpcSs >> svchost.exe 1780 AudioSrv, CryptSvc, Dhcp, EventSystem, >> FastUserSwitchingCompatibility, helpsvc, >> lanmanserver, lanmanworkstation, Netman, >> Nla, RasMan, SENS, SharedAccess, >> ShellHWDetection, TapiSrv, Themes, >> winmgmt, >> WZCSVC >> explorer.exe 640 N/A >> cmd.exe 1688 N/A >> tasklist.exe 420 N/A >> wmiprvse.exe >> >> Type Date Time Source Category Event User Computer >> Information 4/2/2010 10:12:55 PM Service Control Manager >> None 7036 N/A COMPAQ-2006 >> Information 4/2/2010 10:12:55 PM Service Control Manager >> None 7036 N/A COMPAQ-2006 >> Information 4/2/2010 10:12:55 PM Service Control Manager >> None 7036 N/A COMPAQ-2006 >> Information 4/2/2010 10:12:55 PM Service Control Manager >> None 7035 Compaq_Owner COMPAQ-2006 >> Information 4/2/2010 10:12:55 PM Service Control Manager >> None 7036 N/A COMPAQ-2006 >> Information 4/2/2010 10:12:55 PM Service Control Manager >> None 7036 N/A COMPAQ-2006 >> Information 4/2/2010 10:12:55 PM Service Control Manager >> None 7036 N/A COMPAQ-2006 >> Information 4/2/2010 10:12:55 PM Service Control Manager >> None 7036 N/A COMPAQ-2006 >> Information 4/2/2010 10:12:55 PM Service Control Manager >> None 7035 SYSTEM COMPAQ-2006 >> Information 4/2/2010 10:12:55 PM Service Control Manager >> None 7035 SYSTEM COMPAQ-2006 >> Information 4/2/2010 10:12:55 PM Service Control Manager >> None 7035 SYSTEM COMPAQ-2006 >> Information 4/2/2010 10:12:55 PM Service Control Manager >> None 7036 N/A COMPAQ-2006 >> Information 4/2/2010 10:11:08 PM Tcpip None 4201 >> N/A COMPAQ-2006 >> Information 4/2/2010 10:11:26 PM eventlog None 6005 >> N/A COMPAQ-2006 >> Information 4/2/2010 10:11:26 PM eventlog None 6009 >> N/A COMPAQ-2006 >> Information 4/2/2010 10:10:34 PM eventlog None 6006 >> N/A COMPAQ-2006 >> Information 4/2/2010 10:10:33 PM Service Control Manager >> None 7036 N/A COMPAQ-2006 >> Information 4/2/2010 10:09:57 PM Service Control Manager >> None 7036 N/A COMPAQ-2006 >> Information 4/2/2010 10:09:57 PM Service Control Manager >> None 7036 N/A COMPAQ-2006 >> Information 4/2/2010 10:09:57 PM Service Control Manager >> None 7036 N/A COMPAQ-2006 >> Information 4/2/2010 10:09:57 PM Service Control Manager >> None 7035 Compaq_Owner COMPAQ-2006 >> Information 4/2/2010 10:09:57 PM Service Control Manager >> None 7036 N/A COMPAQ-2006 >> Information 4/2/2010 10:09:57 PM Service Control Manager >> None 7036 N/A COMPAQ-2006 >> Information 4/2/2010 10:09:57 PM Service Control Manager >> None 7035 SYSTEM COMPAQ-2006 >> Information 4/2/2010 10:09:57 PM Service Control Manager >> None 7036 N/A COMPAQ-2006 >> Information 4/2/2010 10:09:57 PM Service Control Manager >> None 7036 N/A COMPAQ-2006 >> Information 4/2/2010 10:09:57 PM Service Control Manager >> None 7035 SYSTEM COMPAQ-2006 >> Information 4/2/2010 10:09:57 PM Service Control Manager >> None 7035 SYSTEM COMPAQ-2006 >> Information 4/2/2010 10:09:57 PM Service Control Manager >> None 7036 N/A COMPAQ-2006 >> Information 4/2/2010 10:08:10 PM Tcpip None 4201 >> N/A COMPAQ-2006 >> Information 4/2/2010 10:08:29 PM eventlog None 6005 >> N/A COMPAQ-2006 >> Information 4/2/2010 10:08:29 PM eventlog None 6009 >> N/A COMPAQ-2006 >> Information 4/2/2010 9:52:13 PM eventlog None 6006 >> N/A COMPAQ-2006 >> Information 4/2/2010 9:50:01 PM Service Control Manager >> None 7035 Compaq_Owner COMPAQ-2006 >> >> Event Type: Information >> Event Source: Service Control Manager >> Event Category: None >> Event ID: 7035 >> Date: 4/2/2010 >> Time: 10:12:55 PM >> User: COMPAQ-2006\Compaq_Owner >> Computer: COMPAQ-2006 >> Description: >> The Remote Access Connection Manager service was successfully sent a >> start control. >> >> For more information, see Help and Support Center at >> http://go.microsoft.com/fwlink/events.asp. >> >> Notice, no ati2 problems. A lot of information calls but >> no complaints or errors. But no sign of it going to hibernation. >> So at first glance, we have it all fixed, but the goal we set >> out for, we have not achieved. I'm going back there to see what >> happens if I set it to hibernate after only 1 hour. Maybe you'll have >> some >> comment...... > > I find it surprising that you installed new Catalyst drivers but that no > ATI services or processes show up in the Net Start or Tasklist > results... Did you go in Services.msc and disable them? See my other > post about reinstalling the drivers. > > Also, do not use screen savers while you try to fix this. When you come > back to the machine after two hours what do you see? Is the screen just > black? Or...? > > John Okay, John, I'll UNinstall the drivers and reinstall. I had just let it install, figuring it would write over the old, or do what it needed to do. Yes, screen savers are off. When I go back after 2 hours, it is at Desktop with all icons, but somewhat earlier a glance showed all black screen. As for disabling in services.msc .... I believe I reported what they were set for, but I'll check when I go there now. BTW ... a 1.5 hour run this morning with hibernate set at 1 hour......same result, it just didn't hibernate.
From: Unknown on 3 Apr 2010 11:17 Wholeheartedly agree with you. He's the best (and is an MVP) on all newsgroups. "William B. Lurie" <billurie(a)nospam.net> wrote in message news:O4YWWMr0KHA.3652(a)TK2MSFTNGP04.phx.gbl... > 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 ........ >>
From: John John - MVP on 3 Apr 2010 11:55 Thanks for the compliment... or surely you jest. Some in these groups have forgotten more than I will ever know... John Unknown wrote: > Wholeheartedly agree with you. He's the best (and is an MVP) on all > newsgroups. > "William B. Lurie" <billurie(a)nospam.net> wrote in message > news:O4YWWMr0KHA.3652(a)TK2MSFTNGP04.phx.gbl... >> 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 ........ >
From: Unknown on 3 Apr 2010 12:54
Don't be modest. I've followed your posts for a long time and you're the best. (Most intelligent). "John John - MVP" <audetweld(a)nbnot.nb.ca> wrote in message news:%23bX5TY00KHA.4420(a)TK2MSFTNGP02.phx.gbl... > Thanks for the compliment... or surely you jest. Some in these groups > have forgotten more than I will ever know... > > John > > Unknown wrote: >> Wholeheartedly agree with you. He's the best (and is an MVP) on all >> newsgroups. >> "William B. Lurie" <billurie(a)nospam.net> wrote in message >> news:O4YWWMr0KHA.3652(a)TK2MSFTNGP04.phx.gbl... >>> 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 ........ >> |