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 1 Apr 2010 15:41 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). 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. >> We could also get the list of drivers with a different command: >> >> driverquery >c:\drivers.txt > > It didn't recognize that command. Another utility that is included in XP Pro but not in XP Home... >> 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? Make sure that you don't have a 3D screen saver running. Disconnect the network cable and see if things change, maybe something from 'outside' is keeping the machine alive. See what shows up in the Event Log, if there is nothing to be found in the Event Log start investigating the Loaded Modules. John
From: William B. Lurie on 1 Apr 2010 18:06 John John - MVP wrote: > 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). > > 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. > Okay, I'll try those. > > >>> We could also get the list of drivers with a different command: >>> >>> driverquery >c:\drivers.txt >> >> It didn't recognize that command. > > Another utility that is included in XP Pro but not in XP Home... > > >>> 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? > > Make sure that you don't have a 3D screen saver running. Only screen saver is garden variety generic via Start>>Display>>Screen Saver that came with XP. > > Disconnect the network cable and see if things change, maybe something > from 'outside' is keeping the machine alive. I was testing that way for a while, didn't show any improvement (then). > > See what shows up in the Event Log, if there is nothing to be found in > the Event Log start investigating the Loaded Modules. By Loaded Modules, I assume you mean everything that shows in the Task Manager list, including about 15 executables that are not user-generated...... SvcHosts, for example. I don't think I'm up to doing that, but I have the other items above to look into. May I digress with an adaptation of a prayer? Lord, give me the strength to change what I can change. And the grace to accept what I cannot change. And the wisdom to know the difference between the two. Bill > > John
From: William B. Lurie on 1 Apr 2010 18:21 (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. > >>> We could also get the list of drivers with a different command: >>> >>> driverquery >c:\drivers.txt >> >> It didn't recognize that command. > > Another utility that is included in XP Pro but not in XP Home... > > >>> 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? > > Make sure that you don't have a 3D screen saver running. > > Disconnect the network cable and see if things change, maybe something > from 'outside' is keeping the machine alive. 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). > > See what shows up in the Event Log, if there is nothing to be found in > the Event Log start investigating the Loaded Modules. > > John
From: John John - MVP on 1 Apr 2010 19:39 William B. Lurie wrote: >> Make sure that you don't have a 3D screen saver running. > > Only screen saver is garden variety generic via Start>>Display>>Screen > Saver that came with XP. Even if they are the "garden variety" that came with XP they could still be at fault. You have to positively eliminate possible causes, disable screen savers(set to None) and see if things change. >> Disconnect the network cable and see if things change, maybe something >> from 'outside' is keeping the machine alive. > > I was testing that way for a while, didn't show any improvement (then). >> >> See what shows up in the Event Log, if there is nothing to be found in >> the Event Log start investigating the Loaded Modules. > > By Loaded Modules, I assume you mean everything that shows > in the Task Manager list, including about 15 executables > that are not user-generated...... SvcHosts, for example. > I don't think I'm up to doing that, but I have the other > items above to look into. > > May I digress with an adaptation of a prayer? > Lord, give me the strength to change what I can change. > And the grace to accept what I cannot change. > And the wisdom to know the difference between the two. Amen. John
From: John John - MVP on 1 Apr 2010 20:01
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 |