|
XP hangs on shutdown
I am supplying extra info for assistance as to why XP has decided to hang on shutdown, leaving me with the only course of action and that is turn off at the wall. its a bit long winded bbut may be needed by those who can help.
Its been doing this for the last 2 months maximum, and as this is an area I am unsure of, any help would be appreciated. There has been no new additions in hardware or software for the last 18 months - 2 years, with exception to FF addon "NoScript" installed only 2 days ago. Advanced System Information - Error Log Date - Time Source Description Saturday, 1 October 2011 Service Control Manager The Network DDE service depends on the Network DDE DSDM service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. Saturday, 1 October 2011 Service Control Manager The ClipBook service depends on the Network DDE service which failed to start because of the following error: The dependency service or group failed to start. Saturday, 1 October 2011 Service Control Manager The Human Interface Device Access service terminated with the following error: The specified module could not be found. Sunday, 2 October 2011 Service Control Manager The Network DDE service depends on the Network DDE DSDM service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. Sunday, 2 October 2011 Service Control Manager The ClipBook service depends on the Network DDE service which failed to start because of the following error: The dependency service or group failed to start. Sunday, 2 October 2011 Service Control Manager The Human Interface Device Access service terminated with the following error: The specified module could not be found. Monday, 3 October 2011 Service Control Manager The Network DDE service depends on the Network DDE DSDM service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. Monday, 3 October 2011 Service Control Manager The ClipBook service depends on the Network DDE service which failed to start because of the following error: The dependency service or group failed to start. Monday, 3 October 2011 Service Control Manager The Human Interface Device Access service terminated with the following error: The specified module could not be found. Tuesday, 4 October 2011 Service Control Manager The Network DDE service depends on the Network DDE DSDM service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. Tuesday, 4 October 2011 Service Control Manager The ClipBook service depends on the Network DDE service which failed to start because of the following error: The dependency service or group failed to start. Tuesday, 4 October 2011 Service Control Manager The Human Interface Device Access service terminated with the following error: The specified module could not be found. Wednesday, 5 October 2011 Service Control Manager The Network DDE service depends on the Network DDE DSDM service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. Wednesday, 5 October 2011 Service Control Manager The ClipBook service depends on the Network DDE service which failed to start because of the following error: The dependency service or group failed to start. Wednesday, 5 October 2011 Service Control Manager The Human Interface Device Access service terminated with the following error: The specified module could not be found. Friday, 7 October 2011 Service Control Manager The Network DDE service depends on the Network DDE DSDM service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. Friday, 7 October 2011 Service Control Manager The ClipBook service depends on the Network DDE service which failed to start because of the following error: The dependency service or group failed to start. Friday, 7 October 2011 Service Control Manager The Human Interface Device Access service terminated with the following error: The specified module could not be found. Saturday, 8 October 2011 Service Control Manager The Network DDE service depends on the Network DDE DSDM service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. Saturday, 8 October 2011 Service Control Manager The ClipBook service depends on the Network DDE service which failed to start because of the following error: The dependency service or group failed to start. Saturday, 8 October 2011 Service Control Manager The Human Interface Device Access service terminated with the following error: The specified module could not be found. Sunday, 9 October 2011 Service Control Manager The Network DDE service depends on the Network DDE DSDM service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. Sunday, 9 October 2011 Service Control Manager Timeout (30000 milliseconds) waiting for the Kaspersky Anti-Virus Service service to connect. Sunday, 9 October 2011 Service Control Manager The Kaspersky Anti-Virus Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. Sunday, 9 October 2011 Service Control Manager The ClipBook service depends on the Network DDE service which failed to start because of the following error: The dependency service or group failed to start. Sunday, 9 October 2011 Service Control Manager The Human Interface Device Access service terminated with the following error: The specified module could not be found. Sunday, 9 October 2011 Service Control Manager The Network DDE service depends on the Network DDE DSDM service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. Sunday, 9 October 2011 Service Control Manager The ClipBook service depends on the Network DDE service which failed to start because of the following error: The dependency service or group failed to start. Sunday, 9 October 2011 Service Control Manager The Human Interface Device Access service terminated with the following error: The specified module could not be found. Monday, 10 October 2011 Service Control Manager The Network DDE service depends on the Network DDE DSDM service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. Monday, 10 October 2011 Service Control Manager The ClipBook service depends on the Network DDE service which failed to start because of the following error: The dependency service or group failed to start. Monday, 10 October 2011 Service Control Manager The Human Interface Device Access service terminated with the following error: The specified module could not be found. Monday, 10 October 2011 Service Control Manager The Network DDE service depends on the Network DDE DSDM service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. Monday, 10 October 2011 Service Control Manager The ClipBook service depends on the Network DDE service which failed to start because of the following error: The dependency service or group failed to start. Monday, 10 October 2011 Service Control Manager The Human Interface Device Access service terminated with the following error: The specified module could not be found. Tuesday, 11 October 2011 Service Control Manager The Network DDE service depends on the Network DDE DSDM service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. Tuesday, 11 October 2011 Service Control Manager The ClipBook service depends on the Network DDE service which failed to start because of the following error: The dependency service or group failed to start. Tuesday, 11 October 2011 Service Control Manager The Human Interface Device Access service terminated with the following error: The specified module could not be found. Wednesday, 12 October 2011 Service Control Manager The Network DDE service depends on the Network DDE DSDM service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. Wednesday, 12 October 2011 Service Control Manager The ClipBook service depends on the Network DDE service which failed to start because of the following error: The dependency service or group failed to start. Wednesday, 12 October 2011 Service Control Manager The Human Interface Device Access service terminated with the following error: The specified module could not be found. Wednesday, 12 October 2011 Service Control Manager The SASDIFSV service failed to start due to the following error: The system cannot find the file specified. Thursday, 13 October 2011 Service Control Manager The Network DDE service depends on the Network DDE DSDM service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. Thursday, 13 October 2011 Service Control Manager The ClipBook service depends on the Network DDE service which failed to start because of the following error: The dependency service or group failed to start. Thursday, 13 October 2011 Service Control Manager The Human Interface Device Access service terminated with the following error: The specified module could not be found. Thursday, 13 October 2011 Service Control Manager The following boot-start or system-start driver(s) failed to load: SASKUTIL Thursday, 13 October 2011 Service Control Manager The Kaspersky Anti-Virus Service service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 0 milliseconds: Restart the service. Friday, 14 October 2011 Service Control Manager The Network DDE service depends on the Network DDE DSDM service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. Friday, 14 October 2011 Service Control Manager The ClipBook service depends on the Network DDE service which failed to start because of the following error: The dependency service or group failed to start. Friday, 14 October 2011 Service Control Manager The Human Interface Device Access service terminated with the following error: The specified module could not be found. Friday, 14 October 2011 Service Control Manager The following boot-start or system-start driver(s) failed to load: SASKUTIL Saturday, 15 October 2011 Service Control Manager The Network DDE service depends on the Network DDE DSDM service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. Saturday, 15 October 2011 Service Control Manager The ClipBook service depends on the Network DDE service which failed to start because of the following error: The dependency service or group failed to start. Saturday, 15 October 2011 Service Control Manager The Human Interface Device Access service terminated with the following error: The specified module could not be found. Saturday, 15 October 2011 Service Control Manager The following boot-start or system-start driver(s) failed to load: SASKUTIL Saturday, 15 October 2011 Service Control Manager The SASKUTIL service failed to start due to the following error: The system cannot find the file specified. Saturday, 15 October 2011 Service Control Manager The SASDIFSV service failed to start due to the following error: The system cannot find the file specified. Saturday, 15 October 2011 Service Control Manager The SASKUTIL service failed to start due to the following error: The system cannot find the file specified. Saturday, 15 October 2011 Service Control Manager The SASKUTIL service failed to start due to the following error: The system cannot find the file specified. Sunday, 16 October 2011 Service Control Manager The Network DDE service depends on the Network DDE DSDM service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. Sunday, 16 October 2011 Service Control Manager Timeout (30000 milliseconds) waiting for the Kaspersky Anti-Virus Service service to connect. Sunday, 16 October 2011 Service Control Manager The Kaspersky Anti-Virus Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. Sunday, 16 October 2011 Service Control Manager The ClipBook service depends on the Network DDE service which failed to start because of the following error: The dependency service or group failed to start. Sunday, 16 October 2011 Service Control Manager The Human Interface Device Access service terminated with the following error: The specified module could not be found. Sunday, 16 October 2011 Service Control Manager The following boot-start or system-start driver(s) failed to load: SASKUTIL Monday, 17 October 2011 Service Control Manager The Network DDE service depends on the Network DDE DSDM service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. Monday, 17 October 2011 Service Control Manager The ClipBook service depends on the Network DDE service which failed to start because of the following error: The dependency service or group failed to start. Monday, 17 October 2011 Service Control Manager The Human Interface Device Access service terminated with the following error: The specified module could not be found. Monday, 17 October 2011 Service Control Manager The following boot-start or system-start driver(s) failed to load: SASKUTIL Monday, 17 October 2011 Service Control Manager The Network DDE service depends on the Network DDE DSDM service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. Monday, 17 October 2011 Service Control Manager The ClipBook service depends on the Network DDE service which failed to start because of the following error: The dependency service or group failed to start. Monday, 17 October 2011 Service Control Manager The Human Interface Device Access service terminated with the following error: The specified module could not be found. Monday, 17 October 2011 Service Control Manager The SASDIFSV service failed to start due to the following error: The system cannot find the file specified. Monday, 17 October 2011 Service Control Manager The SASDIFSV service failed to start due to the following error: The system cannot find the file specified. Monday, 17 October 2011 Service Control Manager The SASDIFSV service failed to start due to the following error: The system cannot find the file specified. Tuesday, 18 October 2011 Service Control Manager The Network DDE service depends on the Network DDE DSDM service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. Tuesday, 18 October 2011 Service Control Manager The ClipBook service depends on the Network DDE service which failed to start because of the following error: The dependency service or group failed to start. Tuesday, 18 October 2011 Service Control Manager The Human Interface Device Access service terminated with the following error: The specified module could not be found. Tuesday, 18 October 2011 Service Control Manager The following boot-start or system-start driver(s) failed to load: SASKUTIL Tuesday, 18 October 2011 Service Control Manager The SASDIFSV service failed to start due to the following error: The system cannot find the path specified. Wednesday, 19 October 2011 Service Control Manager The Network DDE service depends on the Network DDE DSDM service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. Wednesday, 19 October 2011 Service Control Manager The ClipBook service depends on the Network DDE service which failed to start because of the following error: The dependency service or group failed to start. Wednesday, 19 October 2011 Service Control Manager The Human Interface Device Access service terminated with the following error: The specified module could not be found. Wednesday, 19 October 2011 Service Control Manager The SASDIFSV service failed to start due to the following error: The system cannot find the path specified. Thursday, 20 October 2011 Service Control Manager The Network DDE service depends on the Network DDE DSDM service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. Thursday, 20 October 2011 Service Control Manager The ClipBook service depends on the Network DDE service which failed to start because of the following error: The dependency service or group failed to start. Thursday, 20 October 2011 Service Control Manager The Human Interface Device Access service terminated with the following error: The specified module could not be found. Thursday, 20 October 2011 Service Control Manager The following boot-start or system-start driver(s) failed to load: SASKUTIL Thursday, 20 October 2011 Service Control Manager The SASDIFSV service failed to start due to the following error: The system cannot find the path specified. Thursday, 20 October 2011 Service Control Manager The SASDIFSV service failed to start due to the following error: The system cannot find the path specified. Thursday, 20 October 2011 Service Control Manager The SASDIFSV service failed to start due to the following error: The system cannot find the file specified. Friday, 21 October 2011 Service Control Manager The Network DDE service depends on the Network DDE DSDM service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. Friday, 21 October 2011 Service Control Manager The ClipBook service depends on the Network DDE service which failed to start because of the following error: The dependency service or group failed to start. Friday, 21 October 2011 Service Control Manager The Human Interface Device Access service terminated with the following error: The specified module could not be found. Friday, 21 October 2011 Service Control Manager The following boot-start or system-start driver(s) failed to load: SASKUTIL Friday, 21 October 2011 Service Control Manager The SASKUTIL service failed to start due to the following error: The system cannot find the file specified. Friday, 21 October 2011 Service Control Manager The SASDIFSV service failed to start due to the following error: The system cannot find the file specified. Friday, 21 October 2011 Service Control Manager The SASKUTIL service failed to start due to the following error: The system cannot find the file specified. Friday, 21 October 2011 Service Control Manager The Network DDE service depends on the Network DDE DSDM service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. Friday, 21 October 2011 Service Control Manager The ClipBook service depends on the Network DDE service which failed to start because of the following error: The dependency service or group failed to start. Friday, 21 October 2011 Service Control Manager The Human Interface Device Access service terminated with the following error: The specified module could not be found. Friday, 21 October 2011 Service Control Manager The following boot-start or system-start driver(s) failed to load: SASKUTIL Friday, 21 October 2011 Service Control Manager The SASKUTIL service failed to start due to the following error: The system cannot find the file specified. Friday, 21 October 2011 Service Control Manager The SASDIFSV service failed to start due to the following error: The system cannot find the file specified. Friday, 21 October 2011 Service Control Manager The SASKUTIL service failed to start due to the following error: The system cannot find the file specified. Friday, 21 October 2011 Service Control Manager The SASKUTIL service failed to start due to the following error: The system cannot find the file specified. Friday, 21 October 2011 Service Control Manager The Network DDE service depends on the Network DDE DSDM service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. Friday, 21 October 2011 Service Control Manager The ClipBook service depends on the Network DDE service which failed to start because of the following error: The dependency service or group failed to start. Friday, 21 October 2011 Service Control Manager The Human Interface Device Access service terminated with the following error: The specified module could not be found. Friday, 21 October 2011 Service Control Manager The following boot-start or system-start driver(s) failed to load: SASKUTIL Friday, 21 October 2011 Service Control Manager The SASKUTIL service failed to start due to the following error: The system cannot find the file specified. Friday, 21 October 2011 Service Control Manager The SASDIFSV service failed to start due to the following error: The system cannot find the file specified. Friday, 21 October 2011 Service Control Manager The SASKUTIL service failed to start due to the following error: The system cannot find the file specified. Friday, 21 October 2011 Service Control Manager The SASKUTIL service failed to start due to the following error: The system cannot find the file specified. Saturday, 22 October 2011 Service Control Manager The Network DDE service depends on the Network DDE DSDM service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. Saturday, 22 October 2011 Service Control Manager The ClipBook service depends on the Network DDE service which failed to start because of the following error: The dependency service or group failed to start. Saturday, 22 October 2011 Service Control Manager The Human Interface Device Access service terminated with the following error: The specified module could not be found. Saturday, 22 October 2011 Service Control Manager The following boot-start or system-start driver(s) failed to load: SASKUTIL Saturday, 22 October 2011 Service Control Manager The SASKUTIL service failed to start due to the following error: The system cannot find the file specified. Saturday, 22 October 2011 Service Control Manager The SASDIFSV service failed to start due to the following error: The system cannot find the file specified. Saturday, 22 October 2011 Service Control Manager The SASKUTIL service failed to start due to the following error: The system cannot find the file specified. Saturday, 22 October 2011 Service Control Manager The SASKUTIL service failed to start due to the following error: The system cannot find the file specified. Sunday, 23 October 2011 Service Control Manager The Network DDE service depends on the Network DDE DSDM service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. Sunday, 23 October 2011 Service Control Manager The ClipBook service depends on the Network DDE service which failed to start because of the following error: The dependency service or group failed to start. Sunday, 23 October 2011 Service Control Manager The Human Interface Device Access service terminated with the following error: The specified module could not be found. Sunday, 23 October 2011 Service Control Manager The following boot-start or system-start driver(s) failed to load: SASKUTIL Sunday, 23 October 2011 Service Control Manager The Network DDE service depends on the Network DDE DSDM service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. Sunday, 23 October 2011 Service Control Manager The ClipBook service depends on the Network DDE service which failed to start because of the following error: The dependency service or group failed to start. Sunday, 23 October 2011 Service Control Manager The Human Interface Device Access service terminated with the following error: The specified module could not be found. Sunday, 23 October 2011 Service Control Manager The following boot-start or system-start driver(s) failed to load: SASKUTIL Monday, 24 October 2011 Service Control Manager The Network DDE service depends on the Network DDE DSDM service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. Monday, 24 October 2011 Service Control Manager The ClipBook service depends on the Network DDE service which failed to start because of the following error: The dependency service or group failed to start. Monday, 24 October 2011 Service Control Manager The Human Interface Device Access service terminated with the following error: The specified module could not be found. Monday, 24 October 2011 Service Control Manager The following boot-start or system-start driver(s) failed to load: SASDIFSV SASKUTIL Tuesday, 25 October 2011 Service Control Manager The Network DDE service depends on the Network DDE DSDM service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. Tuesday, 25 October 2011 Service Control Manager The ClipBook service depends on the Network DDE service which failed to start because of the following error: The dependency service or group failed to start. Tuesday, 25 October 2011 Service Control Manager The Human Interface Device Access service terminated with the following error: The specified module could not be found. Tuesday, 25 October 2011 Service Control Manager The following boot-start or system-start driver(s) failed to load: SASDIFSV SASKUTIL Wednesday, 26 October 2011 Service Control Manager The Network DDE service depends on the Network DDE DSDM service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. Wednesday, 26 October 2011 Service Control Manager The ClipBook service depends on the Network DDE service which failed to start because of the following error: The dependency service or group failed to start. Wednesday, 26 October 2011 Service Control Manager The Human Interface Device Access service terminated with the following error: The specified module could not be found. Wednesday, 26 October 2011 Service Control Manager The following boot-start or system-start driver(s) failed to load: SASDIFSV SASKUTIL Thursday, 27 October 2011 Service Control Manager The Network DDE service depends on the Network DDE DSDM service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. Thursday, 27 October 2011 Service Control Manager The ClipBook service depends on the Network DDE service which failed to start because of the following error: The dependency service or group failed to start. Thursday, 27 October 2011 Service Control Manager The Human Interface Device Access service terminated with the following error: The specified module could not be found. Thursday, 27 October 2011 Service Control Manager The following boot-start or system-start driver(s) failed to load: SASDIFSV SASKUTIL Friday, 28 October 2011 Service Control Manager The Network DDE service depends on the Network DDE DSDM service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. Friday, 28 October 2011 Service Control Manager The ClipBook service depends on the Network DDE service which failed to start because of the following error: The dependency service or group failed to start. Friday, 28 October 2011 Service Control Manager The Human Interface Device Access service terminated with the following error: The specified module could not be found. Friday, 28 October 2011 Service Control Manager The following boot-start or system-start driver(s) failed to load: SASDIFSV SASKUTIL Saturday, 29 October 2011 Service Control Manager The Network DDE service depends on the Network DDE DSDM service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. Saturday, 29 October 2011 Service Control Manager The ClipBook service depends on the Network DDE service which failed to start because of the following error: The dependency service or group failed to start. Saturday, 29 October 2011 Service Control Manager The Human Interface Device Access service terminated with the following error: The specified module could not be found. Saturday, 29 October 2011 Service Control Manager The following boot-start or system-start driver(s) failed to load: SASDIFSV SASKUTIL Sunday, 30 October 2011 Service Control Manager The Network DDE service depends on the Network DDE DSDM service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. Sunday, 30 October 2011 Service Control Manager The ClipBook service depends on the Network DDE service which failed to start because of the following error: The dependency service or group failed to start. Sunday, 30 October 2011 Service Control Manager The Human Interface Device Access service terminated with the following error: The specified module could not be found. Sunday, 30 October 2011 Service Control Manager The following boot-start or system-start driver(s) failed to load: SASDIFSV SASKUTIL Monday, 31 October 2011 Service Control Manager The Network DDE service depends on the Network DDE DSDM service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. Monday, 31 October 2011 Service Control Manager The ClipBook service depends on the Network DDE service which failed to start because of the following error: The dependency service or group failed to start. Monday, 31 October 2011 Service Control Manager The Human Interface Device Access service terminated with the following error: The specified module could not be found. Monday, 31 October 2011 Service Control Manager The following boot-start or system-start driver(s) failed to load: SASDIFSV SASKUTIL Tuesday, 1 November 2011 Service Control Manager The Network DDE service depends on the Network DDE DSDM service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. Tuesday, 1 November 2011 Service Control Manager The ClipBook service depends on the Network DDE service which failed to start because of the following error: The dependency service or group failed to start. Tuesday, 1 November 2011 Service Control Manager The Human Interface Device Access service terminated with the following error: The specified module could not be found. Tuesday, 1 November 2011 Service Control Manager The following boot-start or system-start driver(s) failed to load: SASDIFSV SASKUTIL Tuesday, 1 November 2011 Service Control Manager The SASDIFSV service failed to start due to the following error: The system cannot find the file specified. Wednesday, 2 November 2011 Service Control Manager The Network DDE service depends on the Network DDE DSDM service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. Wednesday, 2 November 2011 Service Control Manager The ClipBook service depends on the Network DDE service which failed to start because of the following error: The dependency service or group failed to start. Wednesday, 2 November 2011 Service Control Manager The Human Interface Device Access service terminated with the following error: The specified module could not be found. Wednesday, 2 November 2011 Service Control Manager The following boot-start or system-start driver(s) failed to load: SASKUTIL Wednesday, 2 November 2011 Service Control Manager The SASKUTIL service failed to start due to the following error: The system cannot find the file specified. Wednesday, 2 November 2011 Service Control Manager The SASDIFSV service failed to start due to the following error: The system cannot find the file specified. Wednesday, 2 November 2011 Service Control Manager The SASKUTIL service failed to start due to the following error: The system cannot find the file specified. Wednesday, 2 November 2011 Service Control Manager The SASKUTIL service failed to start due to the following error: The system cannot find the file specified. Thursday, 3 November 2011 Service Control Manager The Network DDE service depends on the Network DDE DSDM service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. Thursday, 3 November 2011 Service Control Manager The ClipBook service depends on the Network DDE service which failed to start because of the following error: The dependency service or group failed to start. Thursday, 3 November 2011 Service Control Manager The Human Interface Device Access service terminated with the following error: The specified module could not be found. Thursday, 3 November 2011 Service Control Manager The following boot-start or system-start driver(s) failed to load: SASKUTIL Saturday, 5 November 2011 Service Control Manager The Network DDE service depends on the Network DDE DSDM service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. Saturday, 5 November 2011 Service Control Manager The ClipBook service depends on the Network DDE service which failed to start because of the following error: The dependency service or group failed to start. Saturday, 5 November 2011 Service Control Manager The Human Interface Device Access service terminated with the following error: The specified module could not be found. Saturday, 5 November 2011 Service Control Manager The following boot-start or system-start driver(s) failed to load: SASKUTIL Sunday, 6 November 2011 Service Control Manager The Network DDE service depends on the Network DDE DSDM service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. Sunday, 6 November 2011 Service Control Manager The ClipBook service depends on the Network DDE service which failed to start because of the following error: The dependency service or group failed to start. Sunday, 6 November 2011 Service Control Manager The Human Interface Device Access service terminated with the following error: The specified module could not be found. Sunday, 6 November 2011 Service Control Manager The following boot-start or system-start driver(s) failed to load: SASDIFSV SASKUTIL Monday, 7 November 2011 Service Control Manager The Network DDE service depends on the Network DDE DSDM service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. Monday, 7 November 2011 Service Control Manager The ClipBook service depends on the Network DDE service which failed to start because of the following error: The dependency service or group failed to start. Monday, 7 November 2011 Service Control Manager The Human Interface Device Access service terminated with the following error: The specified module could not be found. Monday, 7 November 2011 Service Control Manager The following boot-start or system-start driver(s) failed to load: SASDIFSV SASKUTIL Tuesday, 8 November 2011 Service Control Manager The Network DDE service depends on the Network DDE DSDM service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. Tuesday, 8 November 2011 Service Control Manager The ClipBook service depends on the Network DDE service which failed to start because of the following error: The dependency service or group failed to start. Tuesday, 8 November 2011 Service Control Manager The Human Interface Device Access service terminated with the following error: The specified module could not be found. Tuesday, 8 November 2011 Service Control Manager The following boot-start or system-start driver(s) failed to load: SASDIFSV SASKUTIL Thursday, 10 November 2011 Service Control Manager The Network DDE service depends on the Network DDE DSDM service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. Thursday, 10 November 2011 Service Control Manager The ClipBook service depends on the Network DDE service which failed to start because of the following error: The dependency service or group failed to start. Thursday, 10 November 2011 Service Control Manager The Human Interface Device Access service terminated with the following error: The specified module could not be found. Thursday, 10 November 2011 Service Control Manager The following boot-start or system-start driver(s) failed to load: SASDIFSV SASKUTIL Friday, 11 November 2011 Service Control Manager The Network DDE service depends on the Network DDE DSDM service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. Friday, 11 November 2011 Service Control Manager The ClipBook service depends on the Network DDE service which failed to start because of the following error: The dependency service or group failed to start. Friday, 11 November 2011 Service Control Manager The Human Interface Device Access service terminated with the following error: The specified module could not be found. Friday, 11 November 2011 Service Control Manager The following boot-start or system-start driver(s) failed to load: SASDIFSV SASKUTIL Saturday, 12 November 2011 Service Control Manager The Network DDE service depends on the Network DDE DSDM service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. Saturday, 12 November 2011 Service Control Manager The ClipBook service depends on the Network DDE service which failed to start because of the following error: The dependency service or group failed to start. Saturday, 12 November 2011 Service Control Manager The Human Interface Device Access service terminated with the following error: The specified module could not be found. Saturday, 12 November 2011 Service Control Manager The following boot-start or system-start driver(s) failed to load: SASDIFSV SASKUTIL Sunday, 13 November 2011 Service Control Manager The Network DDE service depends on the Network DDE DSDM service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. Sunday, 13 November 2011 Service Control Manager The ClipBook service depends on the Network DDE service which failed to start because of the following error: The dependency service or group failed to start. Sunday, 13 November 2011 Service Control Manager The Human Interface Device Access service terminated with the following error: The specified module could not be found. Sunday, 13 November 2011 Service Control Manager The following boot-start or system-start driver(s) failed to load: SASDIFSV SASKUTIL Monday, 14 November 2011 Service Control Manager The Network DDE service depends on the Network DDE DSDM service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. Monday, 14 November 2011 Service Control Manager The ClipBook service depends on the Network DDE service which failed to start because of the following error: The dependency service or group failed to start. Monday, 14 November 2011 Service Control Manager The Human Interface Device Access service terminated with the following error: The specified module could not be found. Monday, 14 November 2011 Service Control Manager The following boot-start or system-start driver(s) failed to load: SASDIFSV SASKUTIL Monday, 14 November 2011 Service Control Manager The Network DDE service depends on the Network DDE DSDM service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. Monday, 14 November 2011 Service Control Manager The ClipBook service depends on the Network DDE service which failed to start because of the following error: The dependency service or group failed to start. Monday, 14 November 2011 Service Control Manager The Human Interface Device Access service terminated with the following error: The specified module could not be found. Monday, 14 November 2011 Service Control Manager The following boot-start or system-start driver(s) failed to load: SASDIFSV SASKUTIL Tuesday, 15 November 2011 Service Control Manager The Network DDE service depends on the Network DDE DSDM service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. Tuesday, 15 November 2011 Service Control Manager The ClipBook service depends on the Network DDE service which failed to start because of the following error: The dependency service or group failed to start. Tuesday, 15 November 2011 Service Control Manager The Human Interface Device Access service terminated with the following error: The specified module could not be found. Tuesday, 15 November 2011 Service Control Manager The following boot-start or system-start driver(s) failed to load: SASDIFSV SASKUTIL Wednesday, 16 November 2011 Service Control Manager The Network DDE service depends on the Network DDE DSDM service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. Wednesday, 16 November 2011 Service Control Manager The ClipBook service depends on the Network DDE service which failed to start because of the following error: The dependency service or group failed to start. Wednesday, 16 November 2011 Service Control Manager The Human Interface Device Access service terminated with the following error: The specified module could not be found. Wednesday, 16 November 2011 Service Control Manager The following boot-start or system-start driver(s) failed to load: SASDIFSV SASKUTIL Friday, 18 November 2011 Service Control Manager The Network DDE service depends on the Network DDE DSDM service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. |
Re: XP hangs on shutdown
INFO cont:
Friday, 18 November 2011 Service Control Manager The ClipBook service depends on the Network DDE service which failed to start because of the following error: The dependency service or group failed to start. Friday, 18 November 2011 Service Control Manager The Human Interface Device Access service terminated with the following error: The specified module could not be found. Friday, 18 November 2011 Service Control Manager The following boot-start or system-start driver(s) failed to load: SASDIFSV SASKUTIL Saturday, 19 November 2011 Service Control Manager The Network DDE service depends on the Network DDE DSDM service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. Saturday, 19 November 2011 Service Control Manager The ClipBook service depends on the Network DDE service which failed to start because of the following error: The dependency service or group failed to start. Saturday, 19 November 2011 Service Control Manager The Human Interface Device Access service terminated with the following error: The specified module could not be found. Saturday, 19 November 2011 Service Control Manager The following boot-start or system-start driver(s) failed to load: SASDIFSV SASKUTIL Sunday, 20 November 2011 Service Control Manager The Network DDE service depends on the Network DDE DSDM service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. Sunday, 20 November 2011 Service Control Manager The ClipBook service depends on the Network DDE service which failed to start because of the following error: The dependency service or group failed to start. Sunday, 20 November 2011 Service Control Manager The Human Interface Device Access service terminated with the following error: The specified module could not be found. Sunday, 20 November 2011 Service Control Manager The following boot-start or system-start driver(s) failed to load: SASDIFSV SASKUTIL Monday, 21 November 2011 Service Control Manager The Network DDE service depends on the Network DDE DSDM service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. Monday, 21 November 2011 Service Control Manager The ClipBook service depends on the Network DDE service which failed to start because of the following error: The dependency service or group failed to start. Monday, 21 November 2011 Service Control Manager The Human Interface Device Access service terminated with the following error: The specified module could not be found. Monday, 21 November 2011 Service Control Manager The following boot-start or system-start driver(s) failed to load: SASDIFSV SASKUTIL Tuesday, 22 November 2011 Service Control Manager The Network DDE service depends on the Network DDE DSDM service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. Tuesday, 22 November 2011 Service Control Manager The ClipBook service depends on the Network DDE service which failed to start because of the following error: The dependency service or group failed to start. Tuesday, 22 November 2011 Service Control Manager The Human Interface Device Access service terminated with the following error: The specified module could not be found. Tuesday, 22 November 2011 Service Control Manager The following boot-start or system-start driver(s) failed to load: SASDIFSV SASKUTIL Wednesday, 23 November 2011 Service Control Manager The Network DDE service depends on the Network DDE DSDM service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. Wednesday, 23 November 2011 Service Control Manager The ClipBook service depends on the Network DDE service which failed to start because of the following error: The dependency service or group failed to start. Wednesday, 23 November 2011 Service Control Manager The Human Interface Device Access service terminated with the following error: The specified module could not be found. Wednesday, 23 November 2011 Service Control Manager The following boot-start or system-start driver(s) failed to load: SASDIFSV SASKUTIL Thursday, 24 November 2011 Service Control Manager The Network DDE service depends on the Network DDE DSDM service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. Thursday, 24 November 2011 Service Control Manager The ClipBook service depends on the Network DDE service which failed to start because of the following error: The dependency service or group failed to start. Thursday, 24 November 2011 Service Control Manager The Human Interface Device Access service terminated with the following error: The specified module could not be found. Thursday, 24 November 2011 Service Control Manager The following boot-start or system-start driver(s) failed to load: SASDIFSV SASKUTIL Friday, 25 November 2011 Service Control Manager The Network DDE service depends on the Network DDE DSDM service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. Friday, 25 November 2011 Service Control Manager The ClipBook service depends on the Network DDE service which failed to start because of the following error: The dependency service or group failed to start. Friday, 25 November 2011 Service Control Manager The Human Interface Device Access service terminated with the following error: The specified module could not be found. Friday, 25 November 2011 Service Control Manager The following boot-start or system-start driver(s) failed to load: SASDIFSV SASKUTIL Saturday, 26 November 2011 Service Control Manager The Network DDE service depends on the Network DDE DSDM service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. Saturday, 26 November 2011 Service Control Manager The ClipBook service depends on the Network DDE service which failed to start because of the following error: The dependency service or group failed to start. Saturday, 26 November 2011 Service Control Manager The Human Interface Device Access service terminated with the following error: The specified module could not be found. Saturday, 26 November 2011 Service Control Manager The following boot-start or system-start driver(s) failed to load: SASDIFSV SASKUTIL Sunday, 27 November 2011 Service Control Manager The Network DDE service depends on the Network DDE DSDM service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. Sunday, 27 November 2011 Service Control Manager The ClipBook service depends on the Network DDE service which failed to start because of the following error: The dependency service or group failed to start. Sunday, 27 November 2011 Service Control Manager The Human Interface Device Access service terminated with the following error: The specified module could not be found. Sunday, 27 November 2011 Service Control Manager The following boot-start or system-start driver(s) failed to load: SASDIFSV SASKUTIL |
Re: XP hangs on shutdown
Sunday, 27 November 2011 Service Control Manager The Network DDE service depends on the Network DDE DSDM service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.
Sunday, 27 November 2011 Service Control Manager The ClipBook service depends on the Network DDE service which failed to start because of the following error: The dependency service or group failed to start. Sunday, 27 November 2011 Service Control Manager The Human Interface Device Access service terminated with the following error: The specified module could not be found. Sunday, 27 November 2011 Service Control Manager The following boot-start or system-start driver(s) failed to load: SASDIFSV SASKUTIL Monday, 28 November 2011 sr The System Restore filter encountered the unexpected error '0xC0000001' while processing the file '' on the volume 'HarddiskVolume1'. It has stopped monitoring the volume. Monday, 28 November 2011 Service Control Manager The Network DDE service depends on the Network DDE DSDM service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. Monday, 28 November 2011 Service Control Manager The ClipBook service depends on the Network DDE service which failed to start because of the following error: The dependency service or group failed to start. Monday, 28 November 2011 Service Control Manager The Human Interface Device Access service terminated with the following error: The specified module could not be found. Monday, 28 November 2011 Service Control Manager The following boot-start or system-start driver(s) failed to load: SASDIFSV SASKUTIL uagp35 Tuesday, 29 November 2011 Service Control Manager The Network DDE service depends on the Network DDE DSDM service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. Tuesday, 29 November 2011 Service Control Manager The ClipBook service depends on the Network DDE service which failed to start because of the following error: The dependency service or group failed to start. Tuesday, 29 November 2011 Service Control Manager The Human Interface Device Access service terminated with the following error: The specified module could not be found. Tuesday, 29 November 2011 Service Control Manager The following boot-start or system-start driver(s) failed to load: SASDIFSV SASKUTIL Wednesday, 30 November 2011 Service Control Manager The Network DDE service depends on the Network DDE DSDM service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. Wednesday, 30 November 2011 Service Control Manager The ClipBook service depends on the Network DDE service which failed to start because of the following error: The dependency service or group failed to start. Wednesday, 30 November 2011 Service Control Manager The Human Interface Device Access service terminated with the following error: The specified module could not be found. Wednesday, 30 November 2011 Service Control Manager The following boot-start or system-start driver(s) failed to load: SASDIFSV SASKUTIL Thursday, 1 December 2011 Service Control Manager The Network DDE service depends on the Network DDE DSDM service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. Thursday, 1 December 2011 Service Control Manager The ClipBook service depends on the Network DDE service which failed to start because of the following error: The dependency service or group failed to start. Thursday, 1 December 2011 Service Control Manager The Human Interface Device Access service terminated with the following error: The specified module could not be found. Thursday, 1 December 2011 Service Control Manager The following boot-start or system-start driver(s) failed to load: SASDIFSV SASKUTIL Friday, 2 December 2011 Service Control Manager The Network DDE service depends on the Network DDE DSDM service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. Friday, 2 December 2011 Service Control Manager The ClipBook service depends on the Network DDE service which failed to start because of the following error: The dependency service or group failed to start. Friday, 2 December 2011 Service Control Manager The Human Interface Device Access service terminated with the following error: The specified module could not be found. Friday, 2 December 2011 Service Control Manager The following boot-start or system-start driver(s) failed to load: SASDIFSV SASKUTIL Saturday, 3 December 2011 Service Control Manager The Network DDE service depends on the Network DDE DSDM service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. Saturday, 3 December 2011 Service Control Manager The ClipBook service depends on the Network DDE service which failed to start because of the following error: The dependency service or group failed to start. Saturday, 3 December 2011 Service Control Manager The Human Interface Device Access service terminated with the following error: The specified module could not be found. Saturday, 3 December 2011 Service Control Manager The following boot-start or system-start driver(s) failed to load: SASDIFSV SASKUTIL Saturday, 3 December 2011 Service Control Manager The Network DDE service depends on the Network DDE DSDM service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. Saturday, 3 December 2011 Service Control Manager The ClipBook service depends on the Network DDE service which failed to start because of the following error: The dependency service or group failed to start. Saturday, 3 December 2011 Service Control Manager The Human Interface Device Access service terminated with the following error: The specified module could not be found. Saturday, 3 December 2011 Service Control Manager The following boot-start or system-start driver(s) failed to load: SASDIFSV SASKUTIL Monday, 5 December 2011 Service Control Manager The Network DDE service depends on the Network DDE DSDM service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. Monday, 5 December 2011 Service Control Manager The ClipBook service depends on the Network DDE service which failed to start because of the following error: The dependency service or group failed to start. Monday, 5 December 2011 Service Control Manager The Human Interface Device Access service terminated with the following error: The specified module could not be found. Monday, 5 December 2011 Service Control Manager The following boot-start or system-start driver(s) failed to load: SASDIFSV SASKUTIL Tuesday, 6 December 2011 Service Control Manager The Network DDE service depends on the Network DDE DSDM service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. Tuesday, 6 December 2011 Service Control Manager The ClipBook service depends on the Network DDE service which failed to start because of the following error: The dependency service or group failed to start. Tuesday, 6 December 2011 Service Control Manager The Human Interface Device Access service terminated with the following error: The specified module could not be found. Tuesday, 6 December 2011 Service Control Manager The following boot-start or system-start driver(s) failed to load: SASDIFSV SASKUTIL Wednesday, 7 December 2011 Service Control Manager The Network DDE service depends on the Network DDE DSDM service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. Wednesday, 7 December 2011 Service Control Manager The ClipBook service depends on the Network DDE service which failed to start because of the following error: The dependency service or group failed to start. Wednesday, 7 December 2011 Service Control Manager The Human Interface Device Access service terminated with the following error: The specified module could not be found. Wednesday, 7 December 2011 Service Control Manager The following boot-start or system-start driver(s) failed to load: SASDIFSV SASKUTIL Thursday, 8 December 2011 Service Control Manager The Network DDE service depends on the Network DDE DSDM service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. Thursday, 8 December 2011 Service Control Manager The ClipBook service depends on the Network DDE service which failed to start because of the following error: The dependency service or group failed to start. Thursday, 8 December 2011 Service Control Manager The Human Interface Device Access service terminated with the following error: The specified module could not be found. Thursday, 8 December 2011 Service Control Manager The following boot-start or system-start driver(s) failed to load: SASDIFSV SASKUTIL Friday, 9 December 2011 Service Control Manager The Network DDE service depends on the Network DDE DSDM service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. Friday, 9 December 2011 Service Control Manager The ClipBook service depends on the Network DDE service which failed to start because of the following error: The dependency service or group failed to start. Friday, 9 December 2011 Service Control Manager The Human Interface Device Access service terminated with the following error: The specified module could not be found. Friday, 9 December 2011 Service Control Manager The following boot-start or system-start driver(s) failed to load: SASDIFSV SASKUTIL Saturday, 10 December 2011 Service Control Manager The Network DDE service depends on the Network DDE DSDM service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. Saturday, 10 December 2011 Service Control Manager The ClipBook service depends on the Network DDE service which failed to start because of the following error: The dependency service or group failed to start. Saturday, 10 December 2011 Service Control Manager The Human Interface Device Access service terminated with the following error: The specified module could not be found. Saturday, 10 December 2011 Service Control Manager The following boot-start or system-start driver(s) failed to load: SASDIFSV SASKUTIL |
Re: XP hangs on shutdown
Saturday, 10 December 2011 Service Control Manager The Network DDE service depends on the Network DDE DSDM service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.
Saturday, 10 December 2011 Service Control Manager The ClipBook service depends on the Network DDE service which failed to start because of the following error: The dependency service or group failed to start. Saturday, 10 December 2011 Service Control Manager The Human Interface Device Access service terminated with the following error: The specified module could not be found. Saturday, 10 December 2011 Service Control Manager The following boot-start or system-start driver(s) failed to load: SASDIFSV SASKUTIL Sunday, 11 December 2011 Service Control Manager The Network DDE service depends on the Network DDE DSDM service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. Sunday, 11 December 2011 Service Control Manager The ClipBook service depends on the Network DDE service which failed to start because of the following error: The dependency service or group failed to start. Sunday, 11 December 2011 Service Control Manager The Human Interface Device Access service terminated with the following error: The specified module could not be found. Sunday, 11 December 2011 Service Control Manager The following boot-start or system-start driver(s) failed to load: SASDIFSV SASKUTIL Monday, 12 December 2011 Service Control Manager The Network DDE service depends on the Network DDE DSDM service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. Monday, 12 December 2011 Service Control Manager The ClipBook service depends on the Network DDE service which failed to start because of the following error: The dependency service or group failed to start. Monday, 12 December 2011 Service Control Manager The Human Interface Device Access service terminated with the following error: The specified module could not be found. Monday, 12 December 2011 Service Control Manager The following boot-start or system-start driver(s) failed to load: SASDIFSV SASKUTIL Tuesday, 13 December 2011 Service Control Manager The Network DDE service depends on the Network DDE DSDM service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. Tuesday, 13 December 2011 Service Control Manager The ClipBook service depends on the Network DDE service which failed to start because of the following error: The dependency service or group failed to start. Tuesday, 13 December 2011 Service Control Manager The Human Interface Device Access service terminated with the following error: The specified module could not be found. Tuesday, 13 December 2011 Service Control Manager The following boot-start or system-start driver(s) failed to load: SASDIFSV SASKUTIL Wednesday, 14 December 2011 Service Control Manager The Network DDE service depends on the Network DDE DSDM service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. Wednesday, 14 December 2011 Service Control Manager The ClipBook service depends on the Network DDE service which failed to start because of the following error: The dependency service or group failed to start. Wednesday, 14 December 2011 Service Control Manager The Human Interface Device Access service terminated with the following error: The specified module could not be found. Wednesday, 14 December 2011 Service Control Manager The following boot-start or system-start driver(s) failed to load: SASDIFSV SASKUTIL Wednesday, 14 December 2011 Service Control Manager The Network DDE service depends on the Network DDE DSDM service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. Wednesday, 14 December 2011 Service Control Manager The ClipBook service depends on the Network DDE service which failed to start because of the following error: The dependency service or group failed to start. Wednesday, 14 December 2011 Service Control Manager The Human Interface Device Access service terminated with the following error: The specified module could not be found. Wednesday, 14 December 2011 Service Control Manager The following boot-start or system-start driver(s) failed to load: SASDIFSV SASKUTIL Thursday, 15 December 2011 Service Control Manager The Network DDE service depends on the Network DDE DSDM service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. Thursday, 15 December 2011 Service Control Manager The ClipBook service depends on the Network DDE service which failed to start because of the following error: The dependency service or group failed to start. Thursday, 15 December 2011 Service Control Manager The Human Interface Device Access service terminated with the following error: The specified module could not be found. Thursday, 15 December 2011 Service Control Manager The following boot-start or system-start driver(s) failed to load: SASDIFSV SASKUTIL Friday, 16 December 2011 Service Control Manager The Network DDE service depends on the Network DDE DSDM service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. Friday, 16 December 2011 Service Control Manager The ClipBook service depends on the Network DDE service which failed to start because of the following error: The dependency service or group failed to start. Friday, 16 December 2011 Service Control Manager The Human Interface Device Access service terminated with the following error: The specified module could not be found. Friday, 16 December 2011 Service Control Manager The following boot-start or system-start driver(s) failed to load: SASDIFSV SASKUTIL Saturday, 17 December 2011 Service Control Manager The Network DDE service depends on the Network DDE DSDM service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. Saturday, 17 December 2011 Service Control Manager The ClipBook service depends on the Network DDE service which failed to start because of the following error: The dependency service or group failed to start. Saturday, 17 December 2011 Service Control Manager The Human Interface Device Access service terminated with the following error: The specified module could not be found. Saturday, 17 December 2011 Service Control Manager The following boot-start or system-start driver(s) failed to load: SASDIFSV SASKUTIL Sunday, 18 December 2011 Service Control Manager The Network DDE service depends on the Network DDE DSDM service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. Sunday, 18 December 2011 Service Control Manager The ClipBook service depends on the Network DDE service which failed to start because of the following error: The dependency service or group failed to start. Sunday, 18 December 2011 Service Control Manager The Human Interface Device Access service terminated with the following error: The specified module could not be found. Sunday, 18 December 2011 Service Control Manager The following boot-start or system-start driver(s) failed to load: SASDIFSV SASKUTIL Sunday, 18 December 2011 Service Control Manager The Network DDE service depends on the Network DDE DSDM service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. Sunday, 18 December 2011 Service Control Manager The ClipBook service depends on the Network DDE service which failed to start because of the following error: The dependency service or group failed to start. Sunday, 18 December 2011 Service Control Manager The Human Interface Device Access service terminated with the following error: The specified module could not be found. Sunday, 18 December 2011 Service Control Manager The following boot-start or system-start driver(s) failed to load: SASDIFSV SASKUTIL Monday, 19 December 2011 Service Control Manager The Network DDE service depends on the Network DDE DSDM service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. Monday, 19 December 2011 Service Control Manager The ClipBook service depends on the Network DDE service which failed to start because of the following error: The dependency service or group failed to start. Monday, 19 December 2011 Service Control Manager The Human Interface Device Access service terminated with the following error: The specified module could not be found. Monday, 19 December 2011 Service Control Manager The following boot-start or system-start driver(s) failed to load: SASDIFSV SASKUTIL Tuesday, 20 December 2011 Service Control Manager The Network DDE service depends on the Network DDE DSDM service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. Tuesday, 20 December 2011 Service Control Manager The ClipBook service depends on the Network DDE service which failed to start because of the following error: The dependency service or group failed to start. Tuesday, 20 December 2011 Service Control Manager The Human Interface Device Access service terminated with the following error: The specified module could not be found. Tuesday, 20 December 2011 Service Control Manager The following boot-start or system-start driver(s) failed to load: SASDIFSV SASKUTIL Wednesday, 21 December 2011 Service Control Manager The Network DDE service depends on the Network DDE DSDM service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. Wednesday, 21 December 2011 Service Control Manager The ClipBook service depends on the Network DDE service which failed to start because of the following error: The dependency service or group failed to start. Wednesday, 21 December 2011 Service Control Manager The Human Interface Device Access service terminated with the following error: The specified module could not be found. Wednesday, 21 December 2011 Service Control Manager The following boot-start or system-start driver(s) failed to load: SASDIFSV SASKUTIL Tuesday, 8 February 2011 Applicatio n Error Faulting application explorer.exe, version 6.0.2900.5512, faulting module unknown, version 0.0.0.0, fault address 0x03c0d090. Tuesday, 8 February 2011 DrWatson The application, C:\WINDOWS\Explorer.EXE, generated an application error The error occurred on 02/08/2011 @ 16:10:49.812 The exception generated was c0000005 at address 03C0D090 () Friday, 11 March 2011 Applicatio n Error Faulting application explorer.exe, version 6.0.2900.5512, faulting module unknown, version 0.0.0.0, fault address 0x03b8d095. Friday, 11 March 2011 Applicatio n Error Faulting application drwtsn32.exe, version 5.1.2600.0, faulting module dbghelp.dll, version 5.1.2600.5512, fault address 0x0001295d. Friday, 11 March 2011 Applicatio n Hang Hanging application explorer.exe, version 6.0.2900.5512, hang module hungapp, version 0.0.0.0, hang address 0x00000000. Sunday, 10 April 2011 MsiInstall er Product: Microsoft Office 2000 Premium -- Error 1706. No valid source could be found for product Microsoft Office 2000 Premium. The Windows installer cannot continue. Sunday, 10 April 2011 MsiInstall er Product: Microsoft Office 2000 Premium -- Error 1706. No valid source could be found for product Microsoft Office 2000 Premium. The Windows installer cannot continue. Monday, 11 April 2011 Applicatio n Error Faulting application explorer.exe, version 6.0.2900.5512, faulting module unknown, version 0.0.0.0, fault address 0x034dd090. Monday, 11 April 2011 DrWatson The application, C:\WINDOWS\Explorer.EXE, generated an application error The error occurred on 04/11/2011 @ 19:35:13.734 The exception generated was c0000005 at address 034DD090 () Saturday, 16 April 2011 MsiInstall er Product: Microsoft Office 2000 Premium -- Error 1706. No valid source could be found for product Microsoft Office 2000 Premium. The Windows installer cannot continue. Saturday, 16 April 2011 MsiInstall er Product: Microsoft Office 2000 Premium -- Error 1706. No valid source could be found for product Microsoft Office 2000 Premium. The Windows installer cannot continue. Saturday, 16 April 2011 MsiInstall er Product: Microsoft Office 2000 Premium -- Error 1706. No valid source could be found for product Microsoft Office 2000 Premium. The Windows installer cannot continue. Tuesday, 26 April 2011 Applicatio n Hang Hanging application wmplayer.exe, version 11.0.5721.5262, hang module hungapp, version 0.0.0.0, hang address 0x00000000. Tuesday, 26 April 2011 Applicatio n Hang Hanging application wmplayer.exe, version 11.0.5721.5262, hang module hungapp, version 0.0.0.0, hang address 0x00000000. Sunday, 1 May 2011 Applicatio n Error Faulting application explorer.exe, version 6.0.2900.5512, faulting module lameacm.acm, version 0.9.1.0, fault address 0x0005d0a4. Tuesday, 10 May 2011 Applicatio n Error Faulting application explorer.exe, version 6.0.2900.5512, faulting module unknown, version 0.0.0.0, fault address 0x047bd090. Saturday, 14 May 2011 Applicatio n Hang Hanging application firefox.exe, version 1.9.2.4095, hang module hungapp, version 0.0.0.0, hang address 0x00000000. Saturday, 14 May 2011 Applicatio n Hang Hanging application firefox.exe, version 1.9.2.4095, hang module hungapp, version 0.0.0.0, hang address 0x00000000. Saturday, 4 June 2011 Applicatio n Hang Hanging application firefox.exe, version 1.9.2.4095, hang module hungapp, version 0.0.0.0, hang address 0x00000000. Tuesday, 14 June 2011 Applicatio n Error Faulting application explorer.exe, version 6.0.2900.5512, faulting module wininet.dll, version 6.0.2900.5512, fault address 0x00003674. Saturday, 18 June 2011 Applicatio n Hang Hanging application FreeHideIP-3.7.1.6.Setup.exe, version 0.0.0.0, hang module hungapp, version 0.0.0.0, hang address 0x00000000. Thursday, 30 June 2011 Applicatio n Error Faulting application explorer.exe, version 6.0.2900.5512, faulting module unknown, version 0.0.0.0, fault address 0x6d911043. Tuesday, 5 July 2011 Applicatio n Error Faulting application explorer.exe, version 6.0.2900.5512, faulting module wininet.dll, version 6.0.2900.5512, fault address 0x00003674. Tuesday, 5 July 2011 Applicatio n Hang Hanging application avp.exe, version 11.0.2.571, hang module hungapp, version 0.0.0.0, hang address 0x00000000. Thursday, 7 July 2011 crypt32 Failed auto update retrieval of third-party root list sequence number from: with error: The server name or address could not be resolved Thursday, 4 August 2011 Applicatio n Hang Hanging application firefox.exe, version 1.9.2.4095, hang module hungapp, version 0.0.0.0, hang address 0x00000000. Saturday, 6 August 2011 Applicatio n Error Faulting application explorer.exe, version 6.0.2900.5512, faulting module unknown, version 0.0.0.0, fault address 0x034dd090. Sunday, 7 August 2011 Applicatio n Hang Hanging application vlc.exe, version 1.1.9.0, hang module hungapp, version 0.0.0.0, hang address 0x00000000. Tuesday, 9 August 2011 Applicatio n Hang Hanging application explorer.exe, version 6.0.2900.5512, hang module hungapp, version 0.0.0.0, hang address 0x00000000. Tuesday, 9 August 2011 Applicatio n Hang Hanging application explorer.exe, version 6.0.2900.5512, hang module hungapp, version 0.0.0.0, hang address 0x00000000. Saturday, 13 August 2011 Applicatio n Error Faulting application explorer.exe, version 6.0.2900.5512, faulting module wininet.dll, version 6.0.2900.5512, fault address 0x00003674. Thursday, 18 August 2011 Applicatio n Hang Hanging application mum.exe, version 8.1.28.209, hang module hungapp, version 0.0.0.0, hang address 0x00000000. Thursday, 18 August 2011 Applicatio n Error Faulting application explorer.exe, version 6.0.2900.5512, faulting module unknown, version 0.0.0.0, fault address 0x075ad090. Saturday, 20 August 2011 Applicatio n Error Faulting application explorer.exe, version 6.0.2900.5512, faulting module wininet.dll, version 6.0.2900.5512, fault address 0x00003674. Monday, 22 August 2011 Applicatio n Error Faulting application explorer.exe, version 6.0.2900.5512, faulting module unknown, version 0.0.0.0, fault address 0x0439d090. Friday, 26 August 2011 crypt32 Failed auto update retrieval of third-party root list sequence number from: with error: The server name or address could not be resolved Saturday, 27 August 2011 Applicatio n Error Faulting application explorer.exe, version 6.0.2900.5512, faulting module wininet.dll, version 6.0.2900.5512, fault address 0x00003674. Saturday, 27 August 2011 Applicatio n Error Faulting application drwtsn32.exe, version 5.1.2600.0, faulting module dbghelp.dll, version 5.1.2600.5512, fault address 0x0001295d. Sunday, 28 August 2011 Applicatio n Error Faulting application explorer.exe, version 6.0.2900.5512, faulting module wininet.dll, version 6.0.2900.5512, fault address 0x00003674. Wednesday, 31 August 2011 Applicatio n Hang Hanging application vlc.exe, version 1.1.9.0, hang module hungapp, version 0.0.0.0, hang address 0x00000000. Friday, 2 September 2011 crypt32 Failed auto update retrieval of third-party root list sequence number from: with error: The server name or address could not be resolved Tuesday, 6 September 2011 Applicatio n Hang Hanging application mbam.exe, version 1.51.1.1076, hang module hungapp, version 0.0.0.0, hang address 0x00000000. Tuesday, 6 September 2011 Applicatio n Hang Hanging application mbam.exe, version 1.51.1.1076, hang module hungapp, version 0.0.0.0, hang address 0x00000000. Wednesday, 7 September 2011 Applicatio n Error Faulting application explorer.exe, version 6.0.2900.5512, faulting module wininet.dll, version 6.0.2900.5512, fault address 0x00003674. Wednesday, 7 September 2011 Applicatio n Error Faulting application drwtsn32.exe, version 5.1.2600.0, faulting module dbghelp.dll, version 5.1.2600.5512, fault address 0x0001295d. Saturday, 10 September 2011 Applicatio n Error Faulting application avp.exe, version 11.0.2.571, faulting module msvcr80.dll, version 8.0.50727.4053, fault address 0x0001721e. Saturday, 17 September 2011 Applicatio n Error Faulting application explorer.exe, version 6.0.2900.5512, faulting module wininet.dll, version 6.0.2900.5512, fault address 0x00003674. Saturday, 17 September 2011 crypt32 Failed auto update retrieval of third-party root list sequence number from: with error: The server name or address could not be resolved Sunday, 18 September 2011 Applicatio n Hang Hanging application MiPony.exe, version 1.4.0.0, hang module hungapp, version 0.0.0.0, hang address 0x00000000. Thursday, 22 September 2011 Applicatio n Hang Hanging application MiPony.exe, version 1.5.0.0, hang module hungapp, version 0.0.0.0, hang address 0x00000000. Sunday, 25 September 2011 Applicatio n Hang Hanging application MiPony.exe, version 1.5.0.0, hang module hungapp, version 0.0.0.0, hang address 0x00000000. Saturday, 1 October 2011 Applicatio n Hang Hanging application MiPony.exe, version 1.5.0.0, hang module hungapp, version 0.0.0.0, hang address 0x00000000. Tuesday, 4 October 2011 Applicatio n Hang Hanging application firefox.exe, version 1.9.2.4095, hang module hungapp, version 0.0.0.0, hang address 0x00000000. Sunday, 9 October 2011 crypt32 Failed auto update retrieval of third-party root list sequence number from: with error: The server name or address could not be resolved Monday, 10 October 2011 Applicatio n Hang Hanging application MailWasher.exe, version 0.0.0.0, hang module hungapp, version 0.0.0.0, hang address 0x00000000. Monday, 10 October 2011 Applicatio n Hang Hanging application MailWasher.exe, version 0.0.0.0, hang module hungapp, version 0.0.0.0, hang address 0x00000000. Monday, 10 October 2011 Applicatio n Hang Hanging application MailWasher.exe, version 0.0.0.0, hang module hungapp, version 0.0.0.0, hang address 0x00000000. Monday, 10 October 2011 Applicatio n Hang Hanging application MailWasher.exe, version 0.0.0.0, hang module hungapp, version 0.0.0.0, hang address 0x00000000. Monday, 10 October 2011 Applicatio n Hang Hanging application firefox.exe, version 1.9.2.4095, hang module hungapp, version 0.0.0.0, hang address 0x00000000. Monday, 10 October 2011 Applicatio n Hang Hanging application MailWasher.exe, version 0.0.0.0, hang module hungapp, version 0.0.0.0, hang address 0x00000000. Monday, 10 October 2011 Applicatio n Hang Hanging application MailWasher.exe, version 0.0.0.0, hang module hungapp, version 0.0.0.0, hang address 0x00000000. Monday, 10 October 2011 Applicatio n Hang Hanging application MailWasher.exe, version 0.0.0.0, hang module hungapp, version 0.0.0.0, hang address 0x00000000. Monday, 10 October 2011 Applicatio n Hang Hanging application MailWasher.exe, version 0.0.0.0, hang module hungapp, version 0.0.0.0, hang address 0x00000000. Monday, 10 October 2011 Applicatio n Hang Hanging application MailWasher.exe, version 0.0.0.0, hang module hungapp, version 0.0.0.0, hang address 0x00000000. Monday, 10 October 2011 Applicatio n Hang Hanging application MailWasher.exe, version 0.0.0.0, hang module hungapp, version 0.0.0.0, hang address 0x00000000. Monday, 10 October 2011 Applicatio n Hang Hanging application MailWasher.exe, version 0.0.0.0, hang module hungapp, version 0.0.0.0, hang address 0x00000000. Tuesday, 11 October 2011 Applicatio n Hang Hanging application IEXPLORE.EXE, version 6.0.2900.5512, hang module hungapp, version 0.0.0.0, hang address 0x00000000. Thursday, 13 October 2011 Applicatio n Error Faulting application avp.exe, version 11.0.2.571, faulting module avzkrnl.dll, version 4.34.0.7, fault address 0x000092e9. Monday, 17 October 2011 Applicatio n Hang Hanging application MiPony.exe, version 1.5.0.0, hang module hungapp, version 0.0.0.0, hang address 0x00000000. Tuesday, 18 October 2011 Applicatio n Hang Hanging application MiPony.exe, version 1.5.0.0, hang module hungapp, version 0.0.0.0, hang address 0x00000000. Wednesday, 19 October 2011 Applicatio n Hang Hanging application MiPony.exe, version 1.5.0.0, hang module hungapp, version 0.0.0.0, hang address 0x00000000. Wednesday, 19 October 2011 Applicatio n Hang Hanging application SUPERAntiSpyware.exe, version 4.47.0.1000, hang module hungapp, version 0.0.0.0, hang address 0x00000000. Wednesday, 19 October 2011 Applicatio n Hang Hanging application SUPERAntiSpyware.exe, version 4.47.0.1000, hang module hungapp, version 0.0.0.0, hang address 0x00000000. Friday, 21 October 2011 Applicatio n Error Faulting application explorer.exe, version 6.0.2900.5512, faulting module , version 0.0.0.0, fault address 0x00000000. Saturday, 22 October 2011 Applicatio n Hang Hanging application MiPony.exe, version 1.5.0.0, hang module hungapp, version 0.0.0.0, hang address 0x00000000. |
Re: XP hangs on shutdown
Tuesday, 25 October 2011 Applicatio n Hang Hanging application MiPony.exe, version 1.5.0.0, hang module hungapp, version 0.0.0.0, hang address 0x00000000.
Thursday, 3 November 2011 Applicatio n Hang Hanging application MiPony.exe, version 1.5.2.0, hang module hungapp, version 0.0.0.0, hang address 0x00000000. Sunday, 6 November 2011 Applicatio n Error Faulting application explorer.exe, version 6.0.2900.5512, faulting module unknown, version 0.0.0.0, fault address 0x0326d090. Wednesday, 9 November 2011 Applicatio n Error Faulting application explorer.exe, version 6.0.2900.5512, faulting module unknown, version 0.0.0.0, fault address 0x0331d090. Wednesday, 9 November 2011 Applicatio n Error Faulting application drwtsn32.exe, version 5.1.2600.0, faulting module dbghelp.dll, version 5.1.2600.5512, fault address 0x0001295d. Thursday, 10 November 2011 Applicatio n Hang Hanging application MiPony.exe, version 1.5.2.0, hang module hungapp, version 0.0.0.0, hang address 0x00000000. Thursday, 10 November 2011 Applicatio n Hang Hanging application IEXPLORE.EXE, version 6.0.2900.5512, hang module hungapp, version 0.0.0.0, hang address 0x00000000. Thursday, 10 November 2011 Applicatio n Hang Hanging application WINWORD.EXE, version 9.0.0.2717, hang module hungapp, version 0.0.0.0, hang address 0x00000000. Thursday, 10 November 2011 Applicatio n Hang Hanging application WINWORD.EXE, version 9.0.0.2717, hang module hungapp, version 0.0.0.0, hang address 0x00000000. Saturday, 12 November 2011 Applicatio n Hang Hanging application WINWORD.EXE, version 9.0.0.2717, hang module hungapp, version 0.0.0.0, hang address 0x00000000. Saturday, 12 November 2011 Applicatio n Hang Hanging application WINWORD.EXE, version 9.0.0.2717, hang module hungapp, version 0.0.0.0, hang address 0x00000000. Monday, 14 November 2011 Applicatio n Hang Hanging application MiPony.exe, version 1.5.2.0, hang module hungapp, version 0.0.0.0, hang address 0x00000000. Monday, 14 November 2011 Applicatio n Hang Hanging application MiPony.exe, version 1.5.2.0, hang module hungapp, version 0.0.0.0, hang address 0x00000000. Tuesday, 15 November 2011 Applicatio n Error Faulting application explorer.exe, version 6.0.2900.5512, faulting module unknown, version 0.0.0.0, fault address 0x03b6d090. Wednesday, 16 November 2011 Applicatio n Hang Hanging application MiPony.exe, version 1.5.2.0, hang module hungapp, version 0.0.0.0, hang address 0x00000000. Thursday, 17 November 2011 Applicatio n Hang Hanging application IEXPLORE.EXE, version 6.0.2900.5512, hang module hungapp, version 0.0.0.0, hang address 0x00000000. Thursday, 17 November 2011 Applicatio n Hang Hanging application IEXPLORE.EXE, version 6.0.2900.5512, hang module hungapp, version 0.0.0.0, hang address 0x00000000. Thursday, 17 November 2011 Applicatio n Hang Hanging application IEXPLORE.EXE, version 6.0.2900.5512, hang module hungapp, version 0.0.0.0, hang address 0x00000000. Thursday, 17 November 2011 Applicatio n Hang Hanging application IEXPLORE.EXE, version 6.0.2900.5512, hang module hungapp, version 0.0.0.0, hang address 0x00000000. Thursday, 17 November 2011 Applicatio n Error Faulting application explorer.exe, version 6.0.2900.5512, faulting module mp4splitter.ax, version 1.3.2116.0, fault address 0x00022390. Thursday, 17 November 2011 Applicatio n Error Faulting application drwtsn32.exe, version 5.1.2600.0, faulting module dbghelp.dll, version 5.1.2600.5512, fault address 0x0001295d. Sunday, 20 November 2011 Applicatio n Hang Hanging application firefox.exe, version 1.9.2.4095, hang module hungapp, version 0.0.0.0, hang address 0x00000000. Saturday, 26 November 2011 Applicatio n Hang Hanging application MiPony.exe, version 1.5.2.0, hang module hungapp, version 0.0.0.0, hang address 0x00000000. Saturday, 26 November 2011 Applicatio n Error Faulting application explorer.exe, version 6.0.2900.5512, faulting module unknown, version 0.0.0.0, fault address 0x0389d090. Sunday, 27 November 2011 Applicatio n Hang Hanging application IEXPLORE.EXE, version 6.0.2900.5512, hang module hungapp, version 0.0.0.0, hang address 0x00000000. Sunday, 27 November 2011 Applicatio n Hang Hanging application IEXPLORE.EXE, version 6.0.2900.5512, hang module hungapp, version 0.0.0.0, hang address 0x00000000. Sunday, 27 November 2011 Applicatio n Hang Hanging application IEXPLORE.EXE, version 6.0.2900.5512, hang module hungapp, version 0.0.0.0, hang address 0x00000000. Monday, 28 November 2011 Applicatio n Hang Hanging application MiPony.exe, version 1.5.2.0, hang module hungapp, version 0.0.0.0, hang address 0x00000000. Tuesday, 29 November 2011 Applicatio n Error Faulting application explorer.exe, version 6.0.2900.5512, faulting module unknown, version 0.0.0.0, fault address 0x0436d090. Thursday, 1 December 2011 Applicatio n Error Faulting application msimn.exe, version 6.0.2900.5512, faulting module ntdll.dll, version 5.1.2600.5512, fault address 0x0001b1fa. Thursday, 1 December 2011 Applicatio n Hang Hanging application msimn.exe, version 6.0.2900.5512, hang module hungapp, version 0.0.0.0, hang address 0x00000000. Thursday, 1 December 2011 Applicatio n Error Faulting application msimn.exe, version 6.0.2900.5512, faulting module ntdll.dll, version 5.1.2600.5512, fault address 0x0001b1fa. Thursday, 1 December 2011 Applicatio n Hang Hanging application msimn.exe, version 6.0.2900.5512, hang module hungapp, version 0.0.0.0, hang address 0x00000000. Thursday, 1 December 2011 Applicatio n Error Faulting application msimn.exe, version 6.0.2900.5512, faulting module ntdll.dll, version 5.1.2600.5512, fault address 0x0001b1fa. Thursday, 1 December 2011 Applicatio n Hang Hanging application msimn.exe, version 6.0.2900.5512, hang module hungapp, version 0.0.0.0, hang address 0x00000000. Thursday, 1 December 2011 Applicatio n Error Faulting application explorer.exe, version 6.0.2900.5512, faulting module unknown, version 0.0.0.0, fault address 0x05c8d090. Monday, 5 December 2011 Applicatio n Error Faulting application explorer.exe, version 6.0.2900.5512, faulting module unknown, version 0.0.0.0, fault address 0x0396d090. Thursday, 8 December 2011 Applicatio n Error Faulting application explorer.exe, version 6.0.2900.5512, faulting module unknown, version 0.0.0.0, fault address 0x0337d090. Thursday, 8 December 2011 Applicatio n Error Faulting application drwtsn32.exe, version 5.1.2600.0, faulting module dbghelp.dll, version 5.1.2600.5512, fault address 0x0001295d. Sunday, 11 December 2011 Applicatio n Error Faulting application explorer.exe, version 6.0.2900.5512, faulting module unknown, version 0.0.0.0, fault address 0x033ad090. Thursday, 15 December 2011 Applicatio n Hang Hanging application MiPony.exe, version 1.5.2.0, hang module hungapp, version 0.0.0.0, hang address 0x00000000. Thursday, 15 December 2011 Applicatio n Error Faulting application explorer.exe, version 6.0.2900.5512, faulting module unknown, version 0.0.0.0, fault address 0x0418d090. Saturday, 17 December 2011 Applicatio n Error Faulting application explorer.exe, version 6.0.2900.5512, faulting module unknown, version 0.0.0.0, fault address 0x034ed090. Sunday, 18 December 2011 Applicatio n Error Faulting application explorer.exe, version 6.0.2900.5512, faulting module unknown, version 0.0.0.0, fault address 0x044cd090. Sunday, 18 December 2011 Applicatio n Error Faulting application drwtsn32.exe, version 5.1.2600.0, faulting module dbghelp.dll, version 5.1.2600.5512, fault address 0x0001295d. Tuesday, 20 December 2011 Applicatio n Error Faulting application explorer.exe, version 6.0.2900.5512, faulting module unknown, version 0.0.0.0, fault address 0x034ed090. Tuesday, 20 December 2011 Applicatio n Error Faulting application drwtsn32.exe, version 5.1.2600.0, faulting module dbghelp.dll, version 5.1.2600.5512, fault address 0x0001295d. |
Re: XP hangs on shutdown
Logfile of Trend Micro HijackThis v2.0.4
Scan saved at 9:29:09 AM, on 21/12/2011 Platform: Windows XP SP3 (WinNT 5.01.2600) MSIE: Internet Explorer v6.00 SP3 (6.00.2900.5512) Boot mode: Normal Running processes: C:\WINDOWS\System32\smss.exe C:\WINDOWS\system32\winlogon.exe C:\WINDOWS\system32\services.exe C:\WINDOWS\system32\lsass.exe C:\WINDOWS\system32\svchost.exe C:\WINDOWS\System32\svchost.exe C:\WINDOWS\system32\spoolsv.exe C:\Program Files\Kaspersky Lab\Kaspersky Internet Security 2011\avp.exe C:\Program Files\Diskeeper Corporation\Diskeeper\DkService.exe C:\Program Files\Java\jre6\bin\jqs.exe C:\WINDOWS\Explorer.EXE C:\WINDOWS\system32\VTTimer.exe C:\Program Files\Unlocker\UnlockerAssistant.exe C:\Program Files\Kaspersky Lab\Kaspersky Internet Security 2011\avp.exe C:\Program Files\FireTrust\MailWasher Pro\MailWasher.exe C:\Documents and Settings\Pep n Skye\My Documents\HijackThis\HijackThis.exe R0 - HKCU\Software\Microsoft\Internet Explorer\Main,Start Page = Code:
http://google.comCode:
http://www.poony.info/R3 - URLSearchHook: (no name) - {90d46c30-9f25-4104-aea9-35c3f84477ff} - C:\Program Files\mipony-plugin\prxtbmip0.dll O2 - BHO: (no name) - AutorunsDisabled - (no file) O2 - BHO: IDM Helper - {0055C089-8582-441B-A0BF-17B458C2A3A8} - C:\Program Files\Internet Download Manager\IDMIECC.dll O2 - BHO: AcroIEHelperStub - {18DF081C-E8AD-4283-A596-FA578C2EBDC3} - C:\Program Files\Common Files\Adobe\Acrobat\ActiveX\AcroIEHelperShim.dll O2 - BHO: Conduit Engine - {30F9B915-B755-4826-820B-08FBA6BD249D} - C:\Program Files\ConduitEngine\prxConduitEngine.dll O2 - BHO: IEVkbdBHO - {59273AB4-E7D3-40F9-A1A8-6FA9CCA1862C} - C:\Program Files\Kaspersky Lab\Kaspersky Internet Security 2011\ievkbd.dll O2 - BHO: (no name) - {90d46c30-9f25-4104-aea9-35c3f84477ff} - C:\Program Files\mipony-plugin\prxtbmip0.dll O2 - BHO: Java(tm) Plug-In 2 SSV Helper - {DBC80044-A445-435b-BC74-9C25C1C588A9} - C:\Program Files\Java\jre6\bin\jp2ssv.dll O2 - BHO: link filter bho - {E33CF602-D945-461A-83F0-819F76A199F8} - C:\Program Files\Kaspersky Lab\Kaspersky Internet Security 2011\klwtbbho.dll O2 - BHO: JQSIEStartDetectorImpl - {E7E6F031-17CE-4C07-BC86-EABFE594F69C} - C:\Program Files\Java\jre6\lib\deploy\jqs\ie\jqs_plugin.dll O3 - Toolbar: Torrent-Search Toolbar - {e0c7b854-d5ce-4db6-9804-be1438603d89} - C:\Program Files\Torrent-Search\tbTorr.dll O3 - Toolbar: (no name) - {90d46c30-9f25-4104-aea9-35c3f84477ff} - C:\Program Files\mipony-plugin\prxtbmip0.dll O3 - Toolbar: Conduit Engine - {30F9B915-B755-4826-820B-08FBA6BD249D} - C:\Program Files\ConduitEngine\prxConduitEngine.dll O4 - HKLM\..\Run: [VTTimer] VTTimer.exe O4 - HKLM\..\Run: [UnlockerAssistant] "C:\Program Files\Unlocker\UnlockerAssistant.exe" O4 - HKLM\..\Run: [Adobe Reader Speed Launcher] "C:\Program Files\Adobe\Reader 9.0\Reader\Reader_sl.exe" O4 - HKLM\..\Run: [Adobe ARM] "C:\Program Files\Common Files\Adobe\ARM\1.0\AdobeARM.exe" O4 - HKLM\..\Run: [AVP] "C:\Program Files\Kaspersky Lab\Kaspersky Internet Security 2011\avp.exe" O4 - HKCU\..\Run: [SUPERAntiSpyware] C:\DOCUME~1\PEPNSK~1\LOCALS~1\Temp\RarSFX0\SUPERAn tiSpyware.exe O8 - Extra context menu item: Add to Anti-Banner - C:\Program Files\Kaspersky Lab\Kaspersky Internet Security 2011\ie_banner_deny.htm O8 - Extra context menu item: Download all links with IDM - C:\Program Files\Internet Download Manager\IEGetAll.htm O8 - Extra context menu item: Download all with Free Download Manager - file://C:\Program Files\Free Download Manager\dlall.htm O8 - Extra context menu item: Download FLV video content with IDM - C:\Program Files\Internet Download Manager\IEGetVL.htm O8 - Extra context menu item: Download selected with Free Download Manager - file://C:\Program Files\Free Download Manager\dlselected.htm O8 - Extra context menu item: Download video with Free Download Manager - file://C:\Program Files\Free Download Manager\dlfvideo.htm O8 - Extra context menu item: Download with Free Download Manager - file://C:\Program Files\Free Download Manager\dllink.htm O8 - Extra context menu item: Download with IDM - C:\Program Files\Internet Download Manager\IEExt.htm O9 - Extra button: &Virtual Keyboard - {4248FE82-7FCB-46AC-B270-339F08212110} - C:\Program Files\Kaspersky Lab\Kaspersky Internet Security 2011\klwtbbho.dll O9 - Extra button: URLs c&heck - {CCF151D8-D089-449F-A5A4-D9909053F20F} - C:\Program Files\Kaspersky Lab\Kaspersky Internet Security 2011\klwtbbho.dll O9 - Extra button: (no name) - {e2e2dd38-d088-4134-82b7-f2ba38496583} - C:\WINDOWS\Network Diagnostic\xpnetdiag.exe O9 - Extra 'Tools' menuitem: @xpsp3res.dll,-20001 - {e2e2dd38-d088-4134-82b7-f2ba38496583} - C:\WINDOWS\Network Diagnostic\xpnetdiag.exe O16 - DPF: {17492023-C23A-453E-A040-C7C580BBF700} (Windows Genuine Advantage Validation Tool) - Code:
http://go.microsoft.com/fwlink/?linkid=39204Code:
http://update.microsoft.com/windowsupdate/v6/V5Controls/en/x86/client/wuweb_site.cab?1281566243484O20 - AppInit_DLLs: C:PROGRA~1\KASPER~1\KASPER~1\mzukbd3.dll, C:\PROGR~1\KASPER~1\KASPER~1\adialhk.dll, C:\PROGRA~1\KASPER~1\KASPER~1\mzvkbd3.dll, C:\PROGRA~1\KASPER~1\KASPER~1\kloehk.dll O22 - SharedTaskScheduler: Browseui preloader - {438755C2-A8BA-11D1-B96B-00A0C90312E1} - C:\WINDOWS\system32\browseui.dll O22 - SharedTaskScheduler: Component Categories cache daemon - {8C7461EF-2B13-11d2-BE35-3078302C2030} - C:\WINDOWS\system32\browseui.dll O23 - Service: Kaspersky Anti-Virus Service (AVP) - Kaspersky Lab ZAO - C:\Program Files\Kaspersky Lab\Kaspersky Internet Security 2011\avp.exe O23 - Service: Diskeeper - Diskeeper Corporation - C:\Program Files\Diskeeper Corporation\Diskeeper\DkService.exe O23 - Service: Java Quick Starter (JavaQuickStarterService) - Sun Microsystems, Inc. - C:\Program Files\Java\jre6\bin\jqs.exe -- End of file - 6230 bytes |
Re: XP hangs on shutdown
Thank you EB. I still think XP was the best
|
Re: XP hangs on shutdown
1. Try closing everything you can in your tray (lower right corner) before you shut down and see if it still hangs.
1a. if #1 works, remove things from your startup. 2. Run a CMD shell and try shutting down with "shutdown -s -t 0" Let us know if either of those work or if you need more information, please message me and I'll add more in depth procedures here. |
Re: XP hangs on shutdown
Hi.
You must read this. Code:
http://www.theeldergeek.com/network_dde_dsdm.htmCode:
http://www.malwarebytes.org/ |
Re: XP hangs on shutdown
EB: Is this your other machine? :)
Realize if you disable DDE your programs may not be able to exchange data between them directly if you use that feature. Besides Malwarebytes, you could also try Spybot Search and Destroy to clean out ad and spyware crap. If you have a registry cleaner, you could clean out your registry and defragment it. Please let us know what you have tried thus far and if anything seems to have helped. You should consider removing things like search toolbar and Acrobat. Super anti spyware says it's in temp. hmm. What's mipony? Download manager? (this could be bad if you didn't install it) I'd kill a lot of that myself I am sure. I don't know what a lot of those things from Hijack This are so it's hard to say what else without talking to you. What is VTTimer? |
Re: XP hangs on shutdown
Do you need a registry cleaner makes this a thorough job!
Code:
http://www.eusing.com/free_registry_cleaner/registry_cleaner.htm |
Re: XP hangs on shutdown
Played around quite a bit since I posted.
Cleaned, scrubbed and nit picked my way through the PC. This is the Net machine that I use to post this, the other is my conversion PC because its built like a brick chit house, made for speed. Nothing in start up folder, I try to keep it down to a minimum or nothing. Did locate something, I did install willingly MiPony and I gave it the directive NOT to tie in with I.E. but it did. Opened I.E. as Firefox is my browser by default, and stripped that sucker as bare as a badger. MiPony had installed a toolbar into I.E. so that's gone as well as some other minor things. I don't use I.E. anyway so if it doesn't function as a browser it wont matter. Now I am getting the hang about 1 in 8 - 10 times, which is considerably better than everytime. Also discovered there is a hyperlink in the EXT HDD that hooks to I.E. but to plough through 500 plus Gb to locate the one offending problem, (I guess in jpg or similar) would take a month of Sundays. But when this one occurs it tells me that it won't safely remove the USB, so I have been using Unlocker to kill the process, and whammo its gone. I hate I.E. its worse than a virus that infiltrates everything and hates to be left out of anything. Got a friend who has a fix for I.E., but yet have to download it, but it completely removes it from the PC altogether and Firefox or the browser of your choosing, is the only one on the computer. More to check out first, but as long it doesn't kill off my O.E. as that is my main email program. I still think Xp is the best, have used Win7 and Vista, and perhaps "the new" is overwhelminng, I didn't like them. Too locked up for me and trying to sort a friend's PC who has both programs on her 2 PC's was a nightmare. Neither obeyed simple commands, not to mention how much was hidden compared to Xp. |
Re: XP hangs on shutdown
Quote:
XP was solid for sure. I fought upgrading until I got a 64bit PC. Win 7 is better for a 64 bit system. Vista was just crap, a Win 7 wannabee. Alas I agree XP is awesome, but I finally did break down and go to Win 7. I had Vista on my last laptop, it was crap in the first degree, just like Win ME was. |
Re: XP hangs on shutdown
I wouldn't touch IE either.
I've long since stopped using FireFox too. Consider trying OPERA Browser. Much faster and way more efficient. It also has most of what you need included so you don't have to find and install add ons. I realize preference is a big factor in choosing a Browser, but if you haven't tried it, maybe it's worth a look? :dunno: |
Re: XP hangs on shutdown
DMan999 the other conversion PC is 64 bit ready but I have Xp on it, can't afford to purchase win7. But as it is something I don't connect to the Net, hot rocks would probably do quite well, just have to locate a good and reliable one.
Dee Cee no problems with another browser, I only stuck with FF because of the adblock plus which is very good. On advice was told to use noscript, that lasted a week as it had so many locks on everything it was getting painful to keep adjusting the settings. Need something that doesn't require constant attention. This Net PC gives me no trouble when its running, its only when I shut down the odd occasion now compared to before. |
Re: XP hangs on shutdown
OK then.
If you are happy with it. I wasn't. OPERA has a built in ad blocking system. |
Re: XP hangs on shutdown
Quote:
I also primarily use Opera. when something requires another, I use Firefox first, then to IE last. I also have Maxthon since I read good things about it, but I can't say much about it since I don't really use it and forget it's there since I only use Opera really. |
Re: XP hangs on shutdown
In my experience. One needs to do a Clean RE-Install of any Windows OP every 12 months.
There is just too much **** that gets collected, added and corrupted in Win OS that even Windows itself cannot fix. The Hanging on Shut down can be caused by a Corrupted OS or even just having 1 bad sector on the Hard Drive. If you take a look back to how Fast you system was when you first installed it, to how "fast" (not) it is now, you will see that there is a big difference no matter how much you Prune, Defrag' or what ever you do to tidy up the system. The system just gets slower by the day. A bit like RUST. The only way to get rid of RUST is to Strip it all back to bare metal, make any repairs (bad sectors) and then re-apply the Colour. So do a HARD Reformat and then a Clean Re-install. It takes time so have all of the Programs, Keys and Required Back up files at hand first. Make sure that you have all of the Address Books, Internet Bookmark links, Email's and Passwords ---- SAVED ---- . Thats my answer to this problem. It's what I have done many times in the past (a few times to fix this type of problem). . |
| All times are GMT. The time now is 13:36. |
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.
SEO by vBSEO 3.5.2