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: William B. Lurie on 27 Mar 2010 12:20 MSE? I don't recognize it. Maybe Google will..... Unknown wrote: > Have you looked into using MSE? > "William B. Lurie" <billurie(a)nospam.net> wrote in message > news:ugsTbITzKHA.1796(a)TK2MSFTNGP02.phx.gbl... >> Dear Unk: >> Thanks for working with me. I'll let John comment more on >> your list, but Norton Anti-Virus is my main protection and >> I don't leave home without it. I could, of course, disconnect from >> the phone line and disable it to see if somehow that's the cause. >> One thing at a time..... >> >> Unknown wrote: >>> William; I compared my services with yours since my system does not fail >>> to hibernate. >>> I'll post the differences. Do a Google search for 'viewpoint manager >>> services'. Looks suspicious. >>> I would also suspect Norton AntiVirus. >>> Differences (not on my system) are: >>> LexBce Server >>> lxct device >>> Norton AntiVirus-------I would definately get rid of this. >>> Pervasive PSQL Workgroup Engine >>> Speed Disk Service------Part of Norton >>> Viewpoint Manager Service >>> >>> >>> "William B. Lurie" <billurie(a)nospam.net> wrote in message >>> news:OPnYAYRzKHA.5940(a)TK2MSFTNGP02.phx.gbl... >>>> John John - MVP wrote: >>>>> If I understand correctly, you have the machine set to hibernate after >>>>> 2 hours of inactivity but it can't enter the hibernation state because >>>>> something keeps it awake... >>>>> >>>>> This is what I would try: >>>>> >>>>> Reboot the machine and don't do anything whatsoever after it boots, >>>>> leave it alone for the time set for hibernation and see if it does >>>>> hibernate. >>>>> >>>>> If it doesn't hibernate I would then try a clean boot and once again >>>>> not touch the machine for the set time and see if it does hibernate. >>>>> >>>>> http://support.microsoft.com/kb/310353 >>>>> How to configure Windows XP to start in a "clean boot" state >>>>> >>>>> John >>>> John, I followed instructions. Touched NOTHING for 4 hours >>>> (hibernate set at 2). Power-on light on tower was flashing >>>> and it never went to hibernate. I'll read the Clean Boot instructions >>>> again. Last time I thought it was quite an effort, but this is >>>> this time. Maybe this evening. >
From: Unknown on 27 Mar 2010 12:25 Windows Security Essentials. "William B. Lurie" <billurie(a)nospam.net> wrote in message news:OyV7olczKHA.1236(a)TK2MSFTNGP06.phx.gbl... > MSE? I don't recognize it. Maybe Google will..... > > Unknown wrote: >> Have you looked into using MSE? >> "William B. Lurie" <billurie(a)nospam.net> wrote in message >> news:ugsTbITzKHA.1796(a)TK2MSFTNGP02.phx.gbl... >>> Dear Unk: >>> Thanks for working with me. I'll let John comment more on >>> your list, but Norton Anti-Virus is my main protection and >>> I don't leave home without it. I could, of course, disconnect from >>> the phone line and disable it to see if somehow that's the cause. >>> One thing at a time..... >>> >>> Unknown wrote: >>>> William; I compared my services with yours since my system does not >>>> fail to hibernate. >>>> I'll post the differences. Do a Google search for 'viewpoint manager >>>> services'. Looks suspicious. >>>> I would also suspect Norton AntiVirus. >>>> Differences (not on my system) are: >>>> LexBce Server >>>> lxct device >>>> Norton AntiVirus-------I would definately get rid of this. >>>> Pervasive PSQL Workgroup Engine >>>> Speed Disk Service------Part of Norton >>>> Viewpoint Manager Service >>>> >>>> >>>> "William B. Lurie" <billurie(a)nospam.net> wrote in message >>>> news:OPnYAYRzKHA.5940(a)TK2MSFTNGP02.phx.gbl... >>>>> John John - MVP wrote: >>>>>> If I understand correctly, you have the machine set to hibernate >>>>>> after 2 hours of inactivity but it can't enter the hibernation state >>>>>> because something keeps it awake... >>>>>> >>>>>> This is what I would try: >>>>>> >>>>>> Reboot the machine and don't do anything whatsoever after it boots, >>>>>> leave it alone for the time set for hibernation and see if it does >>>>>> hibernate. >>>>>> >>>>>> If it doesn't hibernate I would then try a clean boot and once again >>>>>> not touch the machine for the set time and see if it does hibernate. >>>>>> >>>>>> http://support.microsoft.com/kb/310353 >>>>>> How to configure Windows XP to start in a "clean boot" state >>>>>> >>>>>> John >>>>> John, I followed instructions. Touched NOTHING for 4 hours >>>>> (hibernate set at 2). Power-on light on tower was flashing >>>>> and it never went to hibernate. I'll read the Clean Boot instructions >>>>> again. Last time I thought it was quite an effort, but this is >>>>> this time. Maybe this evening. >>
From: William B. Lurie on 27 Mar 2010 12:29 William B. Lurie wrote: > John John - MVP wrote: >> William B. Lurie wrote: >>> William B. Lurie wrote: >>>> John John - MVP wrote: >>>>> >>>>> If I understand correctly, you have the machine set to hibernate >>>>> after 2 hours of inactivity but it can't enter the hibernation >>>>> state because something keeps it awake... >>>>> >>>>> This is what I would try: >>>>> >>>>> Reboot the machine and don't do anything whatsoever after it boots, >>>>> leave it alone for the time set for hibernation and see if it does >>>>> hibernate. >>>>> >>>>> If it doesn't hibernate I would then try a clean boot and once >>>>> again not touch the machine for the set time and see if it does >>>>> hibernate. >>>>> >>>>> http://support.microsoft.com/kb/310353 >>>>> How to configure Windows XP to start in a "clean boot" state >>>>> >>>>> John >>>> >>>> John, I followed instructions. Touched NOTHING for 4 hours >>>> (hibernate set at 2). Power-on light on tower was flashing >>>> and it never went to hibernate. I'll read the Clean Boot instructions >>>> again. Last time I thought it was quite an effort, but this is >>>> this time. Maybe this evening. >>> >>> I took another small step, John. I like to try new things on my Clone >>> system before I take a chance with my Main Drive......so I printed >>> out KB310353 and followed its Method 2 on my clone system. It was very >>> easy, and I did it and immediately went away for 2-3/4 hours ......and >>> when I returned, the power light on my tower was blinking, the screen >>> was on, and was not even in Screen Saver mode, which to me means that >>> some Event occurred. It goes to Screen Saver at 10 minutes. I undid the >>> msconfig changes and returned here, to my Master Drive. >>> >>> So I would judge that Clean Boot didn't show any difference. What's >>> your next advice? >> >> Take a look in the Event Viewer and see if anything relevant is >> logged. Check the log on the clone too. >> >> John > The scene changes again, John. I just heard from Symantec, that Norton > AntiVirus does do Idle Time Scan. I had it set for "Quarterly" so it > should not have interfered. But with their help, I reset it to *never* > and maybe that will be the answer. I can live with no idle time scans. > So put my other testing on hold while I find out if hibernate now > works right. Three hours later. At 8:55 I set Idle Scan at Never, rebooted, and went away. Three hours later, it had not gone into hibernation, and Events Log showed *no* events in that period, but was obviously alive and recording things. I am of the opinion that Norton Anti-Virus is not the source of the problem. And I'm not about to change horses and use MSE (as Unk just suggested). There has to be a reason why it doesn't hibernate after 2 hours, and the events log doesn't show it. I'm going back to Clone, Disable Norton, do a Clean Boot, and let 3 hours go by, and look at Events Log as you suggested, John. I won't be back on until 1600 EDT.
From: William B. Lurie on 27 Mar 2010 19:03 William B. Lurie wrote: > William B. Lurie wrote: >> John John - MVP wrote: >>> William B. Lurie wrote: >>>> William B. Lurie wrote: >>>>> John John - MVP wrote: >>>>>> >>>>>> If I understand correctly, you have the machine set to hibernate >>>>>> after 2 hours of inactivity but it can't enter the hibernation >>>>>> state because something keeps it awake... >>>>>> >>>>>> This is what I would try: >>>>>> >>>>>> Reboot the machine and don't do anything whatsoever after it >>>>>> boots, leave it alone for the time set for hibernation and see if >>>>>> it does hibernate. >>>>>> >>>>>> If it doesn't hibernate I would then try a clean boot and once >>>>>> again not touch the machine for the set time and see if it does >>>>>> hibernate. >>>>>> >>>>>> http://support.microsoft.com/kb/310353 >>>>>> How to configure Windows XP to start in a "clean boot" state >>>>>> >>>>>> John >>>>> >>>>> John, I followed instructions. Touched NOTHING for 4 hours >>>>> (hibernate set at 2). Power-on light on tower was flashing >>>>> and it never went to hibernate. I'll read the Clean Boot instructions >>>>> again. Last time I thought it was quite an effort, but this is >>>>> this time. Maybe this evening. >>>> >>>> I took another small step, John. I like to try new things on my Clone >>>> system before I take a chance with my Main Drive......so I printed >>>> out KB310353 and followed its Method 2 on my clone system. It was very >>>> easy, and I did it and immediately went away for 2-3/4 hours ......and >>>> when I returned, the power light on my tower was blinking, the screen >>>> was on, and was not even in Screen Saver mode, which to me means that >>>> some Event occurred. It goes to Screen Saver at 10 minutes. I undid the >>>> msconfig changes and returned here, to my Master Drive. >>>> >>>> So I would judge that Clean Boot didn't show any difference. What's >>>> your next advice? >>> >>> Take a look in the Event Viewer and see if anything relevant is >>> logged. Check the log on the clone too. >>> >>> John >> The scene changes again, John. I just heard from Symantec, that Norton >> AntiVirus does do Idle Time Scan. I had it set for "Quarterly" so it >> should not have interfered. But with their help, I reset it to *never* >> and maybe that will be the answer. I can live with no idle time scans. >> So put my other testing on hold while I find out if hibernate now >> works right. > Three hours later. At 8:55 I set Idle Scan at Never, rebooted, > and went away. Three hours later, it had not gone into hibernation, > and Events Log showed *no* events in that period, but was > obviously alive and recording things. I am of the opinion that > Norton Anti-Virus is not the source of the problem. And I'm not about > to change horses and use MSE (as Unk just suggested). There has to > be a reason why it doesn't hibernate after 2 hours, and the events > log doesn't show it. > > I'm going back to Clone, Disable Norton, do a Clean Boot, and let 3 > hours go by, and look at Events Log as you suggested, John. I won't > be back on until 1600 EDT. I didn't do it right, and will do it again later this evening. Sorry.
From: William B. Lurie on 27 Mar 2010 23:10
William B. Lurie wrote: > William B. Lurie wrote: >> William B. Lurie wrote: >>> John John - MVP wrote: >>>> William B. Lurie wrote: >>>>> William B. Lurie wrote: >>>>>> John John - MVP wrote: >>>>>>> >>>>>>> If I understand correctly, you have the machine set to hibernate >>>>>>> after 2 hours of inactivity but it can't enter the hibernation >>>>>>> state because something keeps it awake... >>>>>>> >>>>>>> This is what I would try: >>>>>>> >>>>>>> Reboot the machine and don't do anything whatsoever after it >>>>>>> boots, leave it alone for the time set for hibernation and see if >>>>>>> it does hibernate. >>>>>>> >>>>>>> If it doesn't hibernate I would then try a clean boot and once >>>>>>> again not touch the machine for the set time and see if it does >>>>>>> hibernate. >>>>>>> >>>>>>> http://support.microsoft.com/kb/310353 >>>>>>> How to configure Windows XP to start in a "clean boot" state >>>>>>> >>>>>>> John >>>>>> >>>>>> John, I followed instructions. Touched NOTHING for 4 hours >>>>>> (hibernate set at 2). Power-on light on tower was flashing >>>>>> and it never went to hibernate. I'll read the Clean Boot instructions >>>>>> again. Last time I thought it was quite an effort, but this is >>>>>> this time. Maybe this evening. >>>>> >>>>> I took another small step, John. I like to try new things on my Clone >>>>> system before I take a chance with my Main Drive......so I printed >>>>> out KB310353 and followed its Method 2 on my clone system. It was very >>>>> easy, and I did it and immediately went away for 2-3/4 hours ......and >>>>> when I returned, the power light on my tower was blinking, the screen >>>>> was on, and was not even in Screen Saver mode, which to me means that >>>>> some Event occurred. It goes to Screen Saver at 10 minutes. I undid >>>>> the >>>>> msconfig changes and returned here, to my Master Drive. >>>>> >>>>> So I would judge that Clean Boot didn't show any difference. What's >>>>> your next advice? >>>> >>>> Take a look in the Event Viewer and see if anything relevant is >>>> logged. Check the log on the clone too. >>>> >>>> John >>> The scene changes again, John. I just heard from Symantec, that >>> Norton AntiVirus does do Idle Time Scan. I had it set for "Quarterly" >>> so it >>> should not have interfered. But with their help, I reset it to *never* >>> and maybe that will be the answer. I can live with no idle time scans. >>> So put my other testing on hold while I find out if hibernate now >>> works right. >> Three hours later. At 8:55 I set Idle Scan at Never, rebooted, >> and went away. Three hours later, it had not gone into hibernation, >> and Events Log showed *no* events in that period, but was >> obviously alive and recording things. I am of the opinion that >> Norton Anti-Virus is not the source of the problem. And I'm not about >> to change horses and use MSE (as Unk just suggested). There has to >> be a reason why it doesn't hibernate after 2 hours, and the events >> log doesn't show it. >> >> I'm going back to Clone, Disable Norton, do a Clean Boot, and let 3 >> hours go by, and look at Events Log as you suggested, John. I won't >> be back on until 1600 EDT. > > I didn't do it right, and will do it again later this evening. Sorry. I think I did it right this time, John, and it still didn't go to hibernate, and left events periodically in Events Log. I'll let it run all night tonight, and have more data in the morning, and will b extra keerful this time. Mwanwhile, perhaps these are of value: > These Windows services are started: > > Application Layer Gateway Service > Automatic Updates > COM+ Event System > Cryptographic Services > DCOM Server Process Launcher > DHCP Client > Distributed Link Tracking Client > DNS Client > Error Reporting Service > Event Log > Fast User Switching Compatibility > Help and Support > IPSEC Services > Network Connections > Network Location Awareness (NLA) > Plug and Play > Print Spooler > Protected Storage > Remote Access Connection Manager > Remote Procedure Call (RPC) > Secondary Logon > Security Accounts Manager > Server > Shell Hardware Detection > SSDP Discovery Service > System Event Notification > Task Scheduler > TCP/IP NetBIOS Helper > Telephony > Terminal Services > Themes > WebClient > Windows Audio > Windows Firewall/Internet Connection Sharing (ICS) > Windows Image Acquisition (WIA) > Windows Management Instrumentation > Windows Time > 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 1284 N/A winlogon.exe 1316 N/A services.exe 1360 Eventlog, PlugPlay lsass.exe 1372 PolicyAgent, ProtectedStorage, SamSs svchost.exe 1532 DcomLaunch, TermService svchost.exe 1632 RpcSs svchost.exe 1784 AudioSrv, CryptSvc, Dhcp, ERSvc, EventSystem, FastUserSwitchingCompatibility, helpsvc, lanmanserver, lanmanworkstation, Netman, Nla, RasMan, Schedule, seclogon, SENS, SharedAccess, ShellHWDetection, TapiSrv, Themes, TrkWks, W32Time, winmgmt, wuauserv, WZCSVC svchost.exe 1872 Dnscache svchost.exe 232 LmHosts, SSDPSRV spoolsv.exe 556 Spooler explorer.exe 816 N/A svchost.exe 904 WebClient svchost.exe 976 stisvc PrintScreen.exe 1864 N/A alg.exe 1712 ALG cmd.exe 1728 N/A tasklist.exe 652 N/A wmiprvse.exe 1136 N/A I am able to send some more before I shut down. Note the Events Log.....I left it at around 7:48 and came back and saw that it was not going to hibernate, at 10:36 .... meanwhile please note the events in betweem which I guess are what caused it not to hibernate. The 7036's. Maybe you can make something of this, John. I do think I did it right this time. > Type Date Time Source Category Event User Computer > Information 3/27/2010 10:56:32 PM Service Control Manager None 7036 N/A COMPAQ-2006 > Information 3/27/2010 10:56:32 PM Service Control Manager None 7036 N/A COMPAQ-2006 > Information 3/27/2010 10:56:32 PM Service Control Manager None 7036 N/A COMPAQ-2006 > Information 3/27/2010 10:56:32 PM Service Control Manager None 7035 SYSTEM COMPAQ-2006 > Information 3/27/2010 10:56:32 PM Service Control Manager None 7036 N/A COMPAQ-2006 > Information 3/27/2010 10:56:32 PM Service Control Manager None 7035 Compaq_Owner COMPAQ-2006 > Information 3/27/2010 10:56:32 PM Service Control Manager None 7036 N/A COMPAQ-2006 > Information 3/27/2010 10:56:32 PM Service Control Manager None 7036 N/A COMPAQ-2006 > Information 3/27/2010 10:56:32 PM Service Control Manager None 7036 N/A COMPAQ-2006 > Information 3/27/2010 10:56:32 PM Service Control Manager None 7035 SYSTEM COMPAQ-2006 > Information 3/27/2010 10:56:32 PM Service Control Manager None 7035 SYSTEM COMPAQ-2006 > Information 3/27/2010 10:56:32 PM Service Control Manager None 7036 N/A COMPAQ-2006 > Information 3/27/2010 10:56:32 PM Service Control Manager None 7035 SYSTEM COMPAQ-2006 > Information 3/27/2010 10:56:32 PM Service Control Manager None 7036 N/A COMPAQ-2006 > Information 3/27/2010 10:56:32 PM Service Control Manager None 7035 SYSTEM COMPAQ-2006 > Information 3/27/2010 10:56:32 PM Service Control Manager None 7036 N/A COMPAQ-2006 > Error 3/27/2010 10:56:32 PM Service Control Manager None 7026 N/A COMPAQ-2006 > Information 3/27/2010 10:54:44 PM Tcpip None 4201 N/A COMPAQ-2006 > Information 3/27/2010 10:55:03 PM eventlog None 6005 N/A COMPAQ-2006 > Information 3/27/2010 10:55:03 PM eventlog None 6009 N/A COMPAQ-2006 > Information 3/27/2010 10:36:00 PM eventlog None 6006 N/A COMPAQ-2006 > Information 3/27/2010 10:19:27 PM Service Control Manager None 7036 N/A COMPAQ-2006 > Information 3/27/2010 9:18:02 PM Service Control Manager None 7036 N/A COMPAQ-2006 > Information 3/27/2010 7:48:35 PM Service Control Manager None 7036 N/A COMPAQ-2006 > Information 3/27/2010 7:48:35 PM Service Control Manager None 7036 N/A COMPAQ-2006 > Information 3/27/2010 7:48:35 PM Service Control Manager None 7035 SYSTEM COMPAQ-2006 > Information 3/27/2010 7:48:35 PM Service Control Manager None 7036 N/A COMPAQ-2006 > Information 3/27/2010 7:48:35 PM Service Control Manager None 7036 N/A COMPAQ-2006 > |