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 1 Apr 2010 12:10 Unknown wrote: > You stated after the hibernation time (2 hours) your HD light is flashing? > At that point did you open task manager and check what processes is running > and whether or not > an application is running? No, but I will next time around. What I see there most often, during these test runs, is nothing related to the user except HpBootOpt, but plenty of System and Local Service with many many 'svchost.exe', none of which are under my control. The sequence is, first desktop; then Screen Saver: then Monitor shutoff (never), then HD shutoff (20 minutes), then System Standby (25 min.) and finally hibernate (2 hours). After 2 hours or more have elapsed, the mintor is in reduced power, the power-on light is flashing, and that's all. It never goes to hibernate, which would be indicated by the power-on light turning off. > Also have you compared the services when starting to hibernate against the > services after one hour? > "William B. Lurie" <billurie(a)nospam.net> wrote in message > news:OgFHiIb0KHA.840(a)TK2MSFTNGP06.phx.gbl... >> Unknown wrote: >>> Thanks. Without sitting at your machine and observing various items I can >>> only go through the process of elimination. >>> It seems something is calling for the internet about every hour. May I >>> ask what you mean when you say Norton fixes their Boo-boos by remote >>> control? >> Sure. I go to their website and find tech support, for which one option >> is one-on-one online chat with their 'analyst'. I describe the problem, >> he (she) asks for permission to connect to my machine remotely, I give >> it, then he takes control of my cursor as tho' he was sitting in my chair, >> clicks and clacks, even downloads new upgrades software, installs, he and >> I check that he has fixed the problem, and I terminate the 'chat' session. >> The wait isn't usually long, typically 5 to 15 minutes. It's calling for >> *something* after one hour, which is why it >> doesn't reach the 2-hour hibernate, but as for calling the Internet, I >> don't know if we've proven that........ >> >>> "William B. Lurie" <billurie(a)nospam.net> wrote in message >>> news:%23AjmLjS0KHA.332(a)TK2MSFTNGP04.phx.gbl... >>>> Unknown wrote: >>>>> Can you verify the default time is still 0x00093a80 in the registry. If >>>>> it is trying to sync your clock >>>>> too often then perhaps that would prevent hibernation. Savings time >>>>> changeover >>>>> would not be affected. >>>>> "William B. Lurie" <billurie(a)nospam.net> wrote in message >>>>> news:Ok%2360vQ0KHA.6108(a)TK2MSFTNGP06.phx.gbl... >>>>>> Unknown wrote: >>>>>>> Curiosity question. Did you at any time alter the time interval for >>>>>>> when you sync your clock? >>>>>>> Check your registry at: >>>>>>> HKEY_LOCAL_MACHINE\System\currentcontrolset\services\w32Time\TimeProviders\NTPclient >>>>>>> in right pane special poll interval is a hexidecimal count in >>>>>>> seconds. >>>>>>> For one week (XP default time) it is 0x00093a80 (604800) >>>>>>> "William B. Lurie" <billurie(a)nospam.net> wrote in message >>>>>> No, I've never been there. It of course did the Savings Time >>>>>> changeover >>>>>> with no hitch at all. This problem goes back way beyond 10 days >>>>>> ago....... >>>> Just to check back with you, UNk, I checked and my >>>> setting is indeed as you showed, for SpecialPollInterval. >>>> Back to the drawing board......... >
From: Unknown on 1 Apr 2010 12:40 Do a Google search for 'power on light flashing' Lots of info there. "William B. Lurie" <billurie(a)nospam.net> wrote in message news:uLTzaXb0KHA.3500(a)TK2MSFTNGP02.phx.gbl... > Unknown wrote: >> You stated after the hibernation time (2 hours) your HD light is >> flashing? >> At that point did you open task manager and check what processes is >> running and whether or not >> an application is running? > > No, but I will next time around. What I see there most often, during > these test runs, is nothing related to the user except HpBootOpt, but > plenty of System and Local Service with many many 'svchost.exe', > none of which are under my control. > > The sequence is, first desktop; then Screen Saver: then Monitor shutoff > (never), then HD shutoff (20 minutes), then System Standby (25 min.) > and finally hibernate (2 hours). After 2 hours or more have elapsed, > the mintor is in reduced power, the power-on light is flashing, and that's > all. It never goes to hibernate, which would be indicated by > the power-on light turning off. > >> Also have you compared the services when starting to hibernate against >> the services after one hour? >> "William B. Lurie" <billurie(a)nospam.net> wrote in message >> news:OgFHiIb0KHA.840(a)TK2MSFTNGP06.phx.gbl... >>> Unknown wrote: >>>> Thanks. Without sitting at your machine and observing various items I >>>> can only go through the process of elimination. >>>> It seems something is calling for the internet about every hour. May I >>>> ask what you mean when you say Norton fixes their Boo-boos by remote >>>> control? >>> Sure. I go to their website and find tech support, for which one option >>> is one-on-one online chat with their 'analyst'. I describe the problem, >>> he (she) asks for permission to connect to my machine remotely, I give >>> it, then he takes control of my cursor as tho' he was sitting in my >>> chair, clicks and clacks, even downloads new upgrades software, >>> installs, he and I check that he has fixed the problem, and I terminate >>> the 'chat' session. The wait isn't usually long, typically 5 to 15 >>> minutes. It's calling for *something* after one hour, which is why it >>> doesn't reach the 2-hour hibernate, but as for calling the Internet, I >>> don't know if we've proven that........ >>> >>>> "William B. Lurie" <billurie(a)nospam.net> wrote in message >>>> news:%23AjmLjS0KHA.332(a)TK2MSFTNGP04.phx.gbl... >>>>> Unknown wrote: >>>>>> Can you verify the default time is still 0x00093a80 in the registry. >>>>>> If it is trying to sync your clock >>>>>> too often then perhaps that would prevent hibernation. Savings time >>>>>> changeover >>>>>> would not be affected. >>>>>> "William B. Lurie" <billurie(a)nospam.net> wrote in message >>>>>> news:Ok%2360vQ0KHA.6108(a)TK2MSFTNGP06.phx.gbl... >>>>>>> Unknown wrote: >>>>>>>> Curiosity question. Did you at any time alter the time interval for >>>>>>>> when you sync your clock? >>>>>>>> Check your registry at: >>>>>>>> HKEY_LOCAL_MACHINE\System\currentcontrolset\services\w32Time\TimeProviders\NTPclient >>>>>>>> in right pane special poll interval is a hexidecimal count in >>>>>>>> seconds. >>>>>>>> For one week (XP default time) it is 0x00093a80 (604800) >>>>>>>> "William B. Lurie" <billurie(a)nospam.net> wrote in message >>>>>>> No, I've never been there. It of course did the Savings Time >>>>>>> changeover >>>>>>> with no hitch at all. This problem goes back way beyond 10 days >>>>>>> ago....... >>>>> Just to check back with you, UNk, I checked and my >>>>> setting is indeed as you showed, for SpecialPollInterval. >>>>> Back to the drawing board......... >>
From: John John - MVP on 1 Apr 2010 13:28 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: 6:40:36 AM >>>>> User: COMPAQ-2006\Compaq_Owner >>>>> Computer: COMPAQ-2006 >>>>> Description: >>>>> DCOM got error "The service cannot be started, either because it is >>>>> disabled or because it has no enabled devices associated with it. " >>>>> attempting to start the service MDM with arguments "" in order to >>>>> run the server: >>>>> {0C0A3666-30C9-11D0-8F20-00805F2CD064} >>>>> >>>>> For more information, see Help and Support Center at >>>>> http://go.microsoft.com/fwlink/events.asp. >>>>> >>>>> Event Type: Error >>>>> Event Source: DCOM >>>>> Event Category: None >>>>> Event ID: 10005 >>>>> Date: 4/1/2010 >>>>> Time: 6:35:10 AM >>>>> User: COMPAQ-2006\Compaq_Owner >>>>> Computer: COMPAQ-2006 >>>>> Description: >>>>> DCOM got error "The service cannot be started, either because it is >>>>> disabled or because it has no enabled devices associated with it. " >>>>> attempting to start the service MDM with arguments "" in order to >>>>> run the server: >>>>> {0C0A3666-30C9-11D0-8F20-00805F2CD064} >>>>> >>>>> For more information, see Help and Support Center at >>>>> http://go.microsoft.com/fwlink/events.asp. >>>>> >>>>> Event Type: Error >>>>> Event Source: Ntfs >>>>> Event Category: Disk >>>>> Event ID: 55 >>>>> Date: 4/1/2010 >>>>> Time: 6:42:47 AM >>>>> User: N/A >>>>> Computer: COMPAQ-2006 >>>>> Description: >>>>> The file system structure on the disk is corrupt and unusable. >>>>> Please run the chkdsk utility on the volume R:. >>>>> >>>>> For more information, see Help and Support Center at >>>>> http://go.microsoft.com/fwlink/events.asp. >>>>> Data: >>>>> 0000: 0d 00 00 00 02 00 4e 00 ......N. >>>>> 0008: 02 00 00 00 37 00 04 c0 ....7..� >>>>> 0010: 00 00 00 00 32 00 00 c0 ....2..� >>>>> 0018: 00 00 00 00 00 00 00 00 ........ >>>>> 0020: 00 00 00 00 00 00 00 00 ........ >>>>> >>>>> Event Type: Error >>>>> Event Source: Service Control Manager >>>>> Event Category: None >>>>> Event ID: 7026 >>>>> Date: 4/1/2010 >>>>> Time: 6:44:25 AM >>>>> User: N/A >>>>> Computer: COMPAQ-2006 >>>>> Description: >>>>> The following boot-start or system-start driver(s) failed to load: >>>>> ftsata2 >>>>> KLIF >>>> >>>> >>>> Is that an updated and current list of started Windows services? >>> >>> Yes, John, I generate it anew every time I make one >>> of these hibernation runs, so that you can see it right >>> with the Events. >>>> >>>> You discussed about those two drivers with another poster not too >>>> long ago. >>> >>> Yes, and now I'll answer your queries: >>>> >>>> ftsata2: Do you now, or did you at any time have a Promise >>>> controller installed? >>> >>> No, I do not now, and never did. This basic HP machine came with >>> one hard drive, and cabling and slots for two more, which I >>> added. I select which drive to run by interrupting boot process >>> and telling it. >>>> >>>> KLIF: Do you now or did you at any time have Kaspersky AV software >>>> installed on the machine? >>> >>> No, I have used Norton AV steadily for at least 15 years. From >>> the days when Norton was impossible to work with, to the present, >>> where they fix boo-boos by Chat and remote control of their software. >>>> >>>> The chkdsk message... What do you have stored on volume R? >>> >>> Oh, I missed that it was referring to volume R. I have numerous >>> 'restore points' of which that volume is one. I generate these >>> every month or so, using the Save & Restore feature of Norton >>> System Works, which used to be PowerQuest Partition Magic. I >>> keep these in case I have to recreate a system as it was as of >>> an earlier date). I'll chkdsk it routinely but I think we can >>> ignore that Event. >> >> These system-start driver errors shouldn't affect the ability to >> hibernate but you can change their startup type and get rid of the >> errors if you want. You will have to change them in the registry at >> their respective subkeys in the >> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services key , set their >> Start Value to 0x3 or 0x4. 0x3 is manual start, 0x4 is disabled. >> >> Or, we can change them at the command prompt if you wish, I need the >> results of the following command before I can give you the proper >> commands to change the start type: >> >> sc query state= all >c:\sc.txt >> >> Copy and paste the contents of the generated sc.txt file to your next >> post, there will be lots of verbiage in the file, post it all. >> >> John > > I don't mess with registry unless it has to be messed with. > And if those commands and errors are innocuous, I see no need to > mess with them via command prompt. And the chkdsk request was > a blind alley, and to be sure, I deleted that 2+ year old backup > anyway. > > But what to do next? With all this time spent on the hibernate > problem, I hate to give up. Who knows, the answer may be just around > the next bend in the road. I don't see the KLIF or ftsata2 driver on the sc query list that you supplied... could be that they are on the clone but not on the production machine, or that the sc command doesn't see these as services. You can try these and see what it returns: sc query klif sc query ftsata2 We could also get the list of drivers with a different command: driverquery >c:\drivers.txt If you want to solve the problem you need to keep on investigating until you find what it is that is running or starting and that prevents hibernation, I don't know of an easy way to figure this out. Sometimes you need dogged determination to get to the bottom of some of these problems. John
From: William B. Lurie on 1 Apr 2010 14:40 John John - MVP 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: 6:40:36 AM >>>>>> User: COMPAQ-2006\Compaq_Owner >>>>>> Computer: COMPAQ-2006 >>>>>> Description: >>>>>> DCOM got error "The service cannot be started, either because it >>>>>> is disabled or because it has no enabled devices associated with >>>>>> it. " attempting to start the service MDM with arguments "" in >>>>>> order to run the server: >>>>>> {0C0A3666-30C9-11D0-8F20-00805F2CD064} >>>>>> >>>>>> For more information, see Help and Support Center at >>>>>> http://go.microsoft.com/fwlink/events.asp. >>>>>> >>>>>> Event Type: Error >>>>>> Event Source: DCOM >>>>>> Event Category: None >>>>>> Event ID: 10005 >>>>>> Date: 4/1/2010 >>>>>> Time: 6:35:10 AM >>>>>> User: COMPAQ-2006\Compaq_Owner >>>>>> Computer: COMPAQ-2006 >>>>>> Description: >>>>>> DCOM got error "The service cannot be started, either because it >>>>>> is disabled or because it has no enabled devices associated with >>>>>> it. " attempting to start the service MDM with arguments "" in >>>>>> order to run the server: >>>>>> {0C0A3666-30C9-11D0-8F20-00805F2CD064} >>>>>> >>>>>> For more information, see Help and Support Center at >>>>>> http://go.microsoft.com/fwlink/events.asp. >>>>>> >>>>>> Event Type: Error >>>>>> Event Source: Ntfs >>>>>> Event Category: Disk >>>>>> Event ID: 55 >>>>>> Date: 4/1/2010 >>>>>> Time: 6:42:47 AM >>>>>> User: N/A >>>>>> Computer: COMPAQ-2006 >>>>>> Description: >>>>>> The file system structure on the disk is corrupt and unusable. >>>>>> Please run the chkdsk utility on the volume R:. >>>>>> >>>>>> For more information, see Help and Support Center at >>>>>> http://go.microsoft.com/fwlink/events.asp. >>>>>> Data: >>>>>> 0000: 0d 00 00 00 02 00 4e 00 ......N. >>>>>> 0008: 02 00 00 00 37 00 04 c0 ....7..� >>>>>> 0010: 00 00 00 00 32 00 00 c0 ....2..� >>>>>> 0018: 00 00 00 00 00 00 00 00 ........ >>>>>> 0020: 00 00 00 00 00 00 00 00 ........ >>>>>> >>>>>> Event Type: Error >>>>>> Event Source: Service Control Manager >>>>>> Event Category: None >>>>>> Event ID: 7026 >>>>>> Date: 4/1/2010 >>>>>> Time: 6:44:25 AM >>>>>> User: N/A >>>>>> Computer: COMPAQ-2006 >>>>>> Description: >>>>>> The following boot-start or system-start driver(s) failed to load: >>>>>> ftsata2 >>>>>> KLIF >>>>> >>>>> >>>>> Is that an updated and current list of started Windows services? >>>> >>>> Yes, John, I generate it anew every time I make one >>>> of these hibernation runs, so that you can see it right >>>> with the Events. >>>>> >>>>> You discussed about those two drivers with another poster not too >>>>> long ago. >>>> >>>> Yes, and now I'll answer your queries: >>>>> >>>>> ftsata2: Do you now, or did you at any time have a Promise >>>>> controller installed? >>>> >>>> No, I do not now, and never did. This basic HP machine came with >>>> one hard drive, and cabling and slots for two more, which I >>>> added. I select which drive to run by interrupting boot process >>>> and telling it. >>>>> >>>>> KLIF: Do you now or did you at any time have Kaspersky AV software >>>>> installed on the machine? >>>> >>>> No, I have used Norton AV steadily for at least 15 years. From >>>> the days when Norton was impossible to work with, to the present, >>>> where they fix boo-boos by Chat and remote control of their software. >>>>> >>>>> The chkdsk message... What do you have stored on volume R? >>>> >>>> Oh, I missed that it was referring to volume R. I have numerous >>>> 'restore points' of which that volume is one. I generate these >>>> every month or so, using the Save & Restore feature of Norton >>>> System Works, which used to be PowerQuest Partition Magic. I >>>> keep these in case I have to recreate a system as it was as of >>>> an earlier date). I'll chkdsk it routinely but I think we can >>>> ignore that Event. >>> >>> These system-start driver errors shouldn't affect the ability to >>> hibernate but you can change their startup type and get rid of the >>> errors if you want. You will have to change them in the registry at >>> their respective subkeys in the >>> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services key , set their >>> Start Value to 0x3 or 0x4. 0x3 is manual start, 0x4 is disabled. >>> >>> Or, we can change them at the command prompt if you wish, I need the >>> results of the following command before I can give you the proper >>> commands to change the start type: >>> >>> sc query state= all >c:\sc.txt >>> >>> Copy and paste the contents of the generated sc.txt file to your next >>> post, there will be lots of verbiage in the file, post it all. >>> >>> John >> >> I don't mess with registry unless it has to be messed with. >> And if those commands and errors are innocuous, I see no need to >> mess with them via command prompt. And the chkdsk request was >> a blind alley, and to be sure, I deleted that 2+ year old backup >> anyway. >> >> But what to do next? With all this time spent on the hibernate >> problem, I hate to give up. Who knows, the answer may be just around >> the next bend in the road. > > I don't see the KLIF or ftsata2 driver on the sc query list that you > supplied... could be that they are on the clone but not on the > production machine, or that the sc command doesn't see these as > services. You can try these and see what it returns: > > sc query klif > sc query ftsata2 > They're both there, John. One of them is: SERVICE_NAME: ftsata2 TYPE : 1 KERNEL_DRIVER STATE : 1 STOPPED (NOT_STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN) WIN32_EXIT_CODE : 31 (0x1f) SERVICE_EXIT_CODE : 0 (0x0) CHECKPOINT : 0x0 WAIT_HINT : 0x0 The other one reads the same but I misplaced it.....the same except it said klif and one other change (I think TYPE -------CONTROL). > > We could also get the list of drivers with a different command: > > driverquery >c:\drivers.txt It didn't recognize that command. > > If you want to solve the problem you need to keep on investigating until > you find what it is that is running or starting and that prevents > hibernation, I don't know of an easy way to figure this out. Sometimes > you need dogged determination to get to the bottom of some of these > problems. Oh, you're right, John. We've both invested too much time and intellect in it, and I'd hate to drop it, either. But, as I said, what next? >
From: William B. Lurie on 1 Apr 2010 15:03
William B. Lurie wrote: > John John - MVP 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: 6:40:36 AM >>>>>>> User: COMPAQ-2006\Compaq_Owner >>>>>>> Computer: COMPAQ-2006 >>>>>>> Description: >>>>>>> DCOM got error "The service cannot be started, either because it >>>>>>> is disabled or because it has no enabled devices associated with >>>>>>> it. " attempting to start the service MDM with arguments "" in >>>>>>> order to run the server: >>>>>>> {0C0A3666-30C9-11D0-8F20-00805F2CD064} >>>>>>> >>>>>>> For more information, see Help and Support Center at >>>>>>> http://go.microsoft.com/fwlink/events.asp. >>>>>>> >>>>>>> Event Type: Error >>>>>>> Event Source: DCOM >>>>>>> Event Category: None >>>>>>> Event ID: 10005 >>>>>>> Date: 4/1/2010 >>>>>>> Time: 6:35:10 AM >>>>>>> User: COMPAQ-2006\Compaq_Owner >>>>>>> Computer: COMPAQ-2006 >>>>>>> Description: >>>>>>> DCOM got error "The service cannot be started, either because it >>>>>>> is disabled or because it has no enabled devices associated with >>>>>>> it. " attempting to start the service MDM with arguments "" in >>>>>>> order to run the server: >>>>>>> {0C0A3666-30C9-11D0-8F20-00805F2CD064} >>>>>>> >>>>>>> For more information, see Help and Support Center at >>>>>>> http://go.microsoft.com/fwlink/events.asp. >>>>>>> >>>>>>> Event Type: Error >>>>>>> Event Source: Ntfs >>>>>>> Event Category: Disk >>>>>>> Event ID: 55 >>>>>>> Date: 4/1/2010 >>>>>>> Time: 6:42:47 AM >>>>>>> User: N/A >>>>>>> Computer: COMPAQ-2006 >>>>>>> Description: >>>>>>> The file system structure on the disk is corrupt and unusable. >>>>>>> Please run the chkdsk utility on the volume R:. >>>>>>> >>>>>>> For more information, see Help and Support Center at >>>>>>> http://go.microsoft.com/fwlink/events.asp. >>>>>>> Data: >>>>>>> 0000: 0d 00 00 00 02 00 4e 00 ......N. >>>>>>> 0008: 02 00 00 00 37 00 04 c0 ....7..� >>>>>>> 0010: 00 00 00 00 32 00 00 c0 ....2..� >>>>>>> 0018: 00 00 00 00 00 00 00 00 ........ >>>>>>> 0020: 00 00 00 00 00 00 00 00 ........ >>>>>>> >>>>>>> Event Type: Error >>>>>>> Event Source: Service Control Manager >>>>>>> Event Category: None >>>>>>> Event ID: 7026 >>>>>>> Date: 4/1/2010 >>>>>>> Time: 6:44:25 AM >>>>>>> User: N/A >>>>>>> Computer: COMPAQ-2006 >>>>>>> Description: >>>>>>> The following boot-start or system-start driver(s) failed to load: >>>>>>> ftsata2 >>>>>>> KLIF >>>>>> >>>>>> >>>>>> Is that an updated and current list of started Windows services? >>>>> >>>>> Yes, John, I generate it anew every time I make one >>>>> of these hibernation runs, so that you can see it right >>>>> with the Events. >>>>>> >>>>>> You discussed about those two drivers with another poster not too >>>>>> long ago. >>>>> >>>>> Yes, and now I'll answer your queries: >>>>>> >>>>>> ftsata2: Do you now, or did you at any time have a Promise >>>>>> controller installed? >>>>> >>>>> No, I do not now, and never did. This basic HP machine came with >>>>> one hard drive, and cabling and slots for two more, which I >>>>> added. I select which drive to run by interrupting boot process >>>>> and telling it. >>>>>> >>>>>> KLIF: Do you now or did you at any time have Kaspersky AV >>>>>> software installed on the machine? >>>>> >>>>> No, I have used Norton AV steadily for at least 15 years. From >>>>> the days when Norton was impossible to work with, to the present, >>>>> where they fix boo-boos by Chat and remote control of their >>>>> software. >>>>>> >>>>>> The chkdsk message... What do you have stored on volume R? >>>>> >>>>> Oh, I missed that it was referring to volume R. I have numerous >>>>> 'restore points' of which that volume is one. I generate these >>>>> every month or so, using the Save & Restore feature of Norton >>>>> System Works, which used to be PowerQuest Partition Magic. I >>>>> keep these in case I have to recreate a system as it was as of >>>>> an earlier date). I'll chkdsk it routinely but I think we can >>>>> ignore that Event. >>>> >>>> These system-start driver errors shouldn't affect the ability to >>>> hibernate but you can change their startup type and get rid of the >>>> errors if you want. You will have to change them in the registry at >>>> their respective subkeys in the >>>> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services key , set their >>>> Start Value to 0x3 or 0x4. 0x3 is manual start, 0x4 is disabled. >>>> >>>> Or, we can change them at the command prompt if you wish, I need the >>>> results of the following command before I can give you the proper >>>> commands to change the start type: >>>> >>>> sc query state= all >c:\sc.txt >>>> >>>> Copy and paste the contents of the generated sc.txt file to your >>>> next post, there will be lots of verbiage in the file, post it all. >>>> >>>> John >>> >>> I don't mess with registry unless it has to be messed with. >>> And if those commands and errors are innocuous, I see no need to >>> mess with them via command prompt. And the chkdsk request was >>> a blind alley, and to be sure, I deleted that 2+ year old backup >>> anyway. >>> >>> But what to do next? With all this time spent on the hibernate >>> problem, I hate to give up. Who knows, the answer may be just around >>> the next bend in the road. >> >> I don't see the KLIF or ftsata2 driver on the sc query list that you >> supplied... could be that they are on the clone but not on the >> production machine, or that the sc command doesn't see these as >> services. You can try these and see what it returns: >> >> sc query klif >> sc query ftsata2 >> > They're both there, John. One of them is: > > > SERVICE_NAME: ftsata2 > TYPE : 1 KERNEL_DRIVER > STATE : 1 STOPPED > > (NOT_STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN) > WIN32_EXIT_CODE : 31 (0x1f) > SERVICE_EXIT_CODE : 0 (0x0) > CHECKPOINT : 0x0 > WAIT_HINT : 0x0 > The other one reads the same but I misplaced it.....the > same except it said klif and one other change > (I think TYPE -------CONTROL).xxxxxx SEE BELOW!!!! > xxxxxxxx >> >> We could also get the list of drivers with a different command: >> >> driverquery >c:\drivers.txt > > It didn't recognize that command. >> >> If you want to solve the problem you need to keep on investigating >> until you find what it is that is running or starting and that >> prevents hibernation, I don't know of an easy way to figure this out. >> Sometimes you need dogged determination to get to the bottom of some >> of these problems. > > Oh, you're right, John. We've both invested too much > time and intellect in it, and I'd hate to drop it, > either. But, as I said, what next? >> > Here's the other one.....from the Clone; both are on both drives: > > SERVICE_NAME: klif > TYPE : 2 FILE_SYSTEM_DRIVER > STATE : 1 STOPPED > (NOT_STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN) > WIN32_EXIT_CODE : 31 (0x1f) > SERVICE_EXIT_CODE : 0 (0x0) > CHECKPOINT : 0x0 > WAIT_HINT : 0x0 |