Vino's Event Viewer v01c run on Windows XP in English Report run at 28/10/2010 9:04:18 AM Note: All dates below are in the format dd/mm/yyyy ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 'Application' Log - error Type ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Log: 'Application' Date/Time: 25/10/2010 3:54:37 PM Type: error Category: 101 Event: 1002 Source: Application Hang Hanging application EXCEL.EXE, version 12.0.6545.5000, hang module hungapp, version 0.0.0.0, hang address 0x00000000. Log: 'Application' Date/Time: 24/10/2010 8:33:08 PM Type: error Category: 100 Event: 1000 Source: Application Error Faulting application Mats_Run.devices.exe, version 0.0.0.0, faulting module msvcrt.dll, version 7.0.2600.5512, fault address 0x00036fa3. Log: 'Application' Date/Time: 24/10/2010 8:32:36 PM Type: error Category: 100 Event: 1000 Source: Application Error Faulting application svchost.exe, version 5.1.2600.5512, faulting module ntdll.dll, version 5.1.2600.5755, fault address 0x00023845. Log: 'Application' Date/Time: 24/10/2010 2:30:07 PM Type: error Category: 50 Event: 4609 Source: EventSystem The COM+ Event System detected a bad return code during its internal processing. HRESULT was 800706BA from line 44 of d:\comxp_sp3\com\com1x\src\events\tier1\eventsystemobj.cpp. Please contact Microsoft Product Support Services to report this error. Log: 'Application' Date/Time: 24/10/2010 2:05:56 PM Type: error Category: 0 Event: 1001 Source: Application Error Fault bucket 1271752061. Log: 'Application' Date/Time: 24/10/2010 2:05:19 PM Type: error Category: 100 Event: 1000 Source: Application Error Faulting application svchost.exe, version 5.1.2600.5512, faulting module ntdll.dll, version 5.1.2600.5755, fault address 0x00023845. Log: 'Application' Date/Time: 24/10/2010 9:36:35 AM Type: error Category: 0 Event: 1001 Source: Application Error Fault bucket 1271752061. Log: 'Application' Date/Time: 24/10/2010 9:36:21 AM Type: error Category: 100 Event: 1000 Source: Application Error Faulting application svchost.exe, version 5.1.2600.5512, faulting module ntdll.dll, version 5.1.2600.5755, fault address 0x00023845. Log: 'Application' Date/Time: 22/10/2010 8:30:53 PM Type: error Category: 100 Event: 1000 Source: Application Error Faulting application svchost.exe, version 5.1.2600.5512, faulting module ntdll.dll, version 5.1.2600.5755, fault address 0x00023845. Log: 'Application' Date/Time: 22/10/2010 3:20:17 PM Type: error Category: 100 Event: 1000 Source: Application Error Faulting application svchost.exe, version 5.1.2600.5512, faulting module ntdll.dll, version 5.1.2600.5755, fault address 0x00023845. Log: 'Application' Date/Time: 21/10/2010 10:53:24 PM Type: error Category: 100 Event: 1000 Source: Application Error Faulting application svchost.exe, version 5.1.2600.5512, faulting module ntdll.dll, version 5.1.2600.5755, fault address 0x00023845. Log: 'Application' Date/Time: 21/10/2010 5:35:11 PM Type: error Category: 100 Event: 1000 Source: Application Error Faulting application svchost.exe, version 5.1.2600.5512, faulting module ntdll.dll, version 5.1.2600.5755, fault address 0x00023845. Log: 'Application' Date/Time: 17/10/2010 5:55:16 PM Type: error Category: 0 Event: 1000 Source: Application Error Faulting application plugin-container.exe, version 1.9.2.3909, faulting module ntdll.dll, version 5.1.2600.5755, fault address 0x0000100b. Log: 'Application' Date/Time: 17/10/2010 5:55:05 PM Type: error Category: 101 Event: 1002 Source: Application Hang Hanging application firefox.exe, version 1.9.2.3909, hang module hungapp, version 0.0.0.0, hang address 0x00000000. Log: 'Application' Date/Time: 17/10/2010 2:56:32 PM Type: error Category: 0 Event: 11 Source: crypt32 Failed extract of third-party root list from auto update cab at: with error: The data is invalid. Log: 'Application' Date/Time: 17/10/2010 2:41:45 PM Type: error Category: 101 Event: 1002 Source: Application Hang Hanging application sas.exe, version 9.13000.16592.24715, hang module hungapp, version 0.0.0.0, hang address 0x00000000. Log: 'Application' Date/Time: 17/10/2010 11:38:18 AM Type: error Category: 0 Event: 1000 Source: Application Error Faulting application acrobat.exe, version 7.0.8.218, faulting module acrobat.dll, version 7.1.0.649, fault address 0x0023e906. Log: 'Application' Date/Time: 17/10/2010 11:38:10 AM Type: error Category: 0 Event: 1000 Source: Application Error Faulting application acrobat.exe, version 7.0.8.218, faulting module acrobat.dll, version 7.1.0.649, fault address 0x0023e906. Log: 'Application' Date/Time: 15/10/2010 7:34:25 PM Type: error Category: 0 Event: 8 Source: crypt32 Failed auto update retrieval of third-party root list sequence number from: with error: The specified server cannot perform the requested operation. Log: 'Application' Date/Time: 15/10/2010 7:34:25 PM Type: error Category: 0 Event: 8 Source: crypt32 Failed auto update retrieval of third-party root list sequence number from: with error: This operation returned because the timeout period expired. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 'Application' Log - information Type ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Log: 'Application' Date/Time: 28/10/2010 9:04:14 AM Type: information Category: 1 Event: 101 Source: Automatic LiveUpdate Scheduler Information Level: success Rolling back the schedule; execution will occur at approximately 9:09 AM. Log: 'Application' Date/Time: 28/10/2010 9:01:22 AM Type: information Category: 0 Event: 0 Source: LiveUpdate Notice Service The event description cannot be found. Log: 'Application' Date/Time: 28/10/2010 8:59:49 AM Type: information Category: 9 Event: 103 Source: VMware View The VMware View System Service is starting Log: 'Application' Date/Time: 28/10/2010 8:59:49 AM Type: information Category: 0 Event: 1800 Source: SecurityCenter The Windows Security Center Service has started. Log: 'Application' Date/Time: 28/10/2010 8:59:49 AM Type: information Category: 9 Event: 103 Source: VMware View WSNM: serviceRun [08:59:48.984] Log: 'Application' Date/Time: 28/10/2010 8:59:49 AM Type: information Category: 9 Event: 103 Source: VMware View WSNM: main [08:59:48.984] Log: 'Application' Date/Time: 28/10/2010 8:59:49 AM Type: information Category: 9 Event: 103 Source: VMware View Program 'wsnm - VDM Framework Node Manager' started, version=3.1.1 build-175957, pid=3040, buildtype=release Log: 'Application' Date/Time: 28/10/2010 8:59:48 AM Type: information Category: 0 Event: 0 Source: ThinkVantage Registry Monitor Service The event description cannot be found. Log: 'Application' Date/Time: 28/10/2010 8:59:17 AM Type: information Category: 0 Event: 0 Source: RoxLiveShare9 The event description cannot be found. Log: 'Application' Date/Time: 28/10/2010 8:59:17 AM Type: information Category: 0 Event: 0 Source: RoxLiveShare9 The event description cannot be found. Log: 'Application' Date/Time: 28/10/2010 8:59:17 AM Type: information Category: 0 Event: 0 Source: Roxio Upnp Server 9 The event description cannot be found. Log: 'Application' Date/Time: 28/10/2010 8:59:17 AM Type: information Category: 0 Event: 0 Source: Roxio Upnp Server 9 The event description cannot be found. Log: 'Application' Date/Time: 28/10/2010 8:59:17 AM Type: information Category: 0 Event: 0 Source: RegSrvc The event description cannot be found. Log: 'Application' Date/Time: 28/10/2010 8:59:17 AM Type: information Category: 0 Event: 0 Source: LiveUpdate Notice Service The event description cannot be found. Log: 'Application' Date/Time: 28/10/2010 8:59:17 AM Type: information Category: 0 Event: 0 Source: IviRegMgr The event description cannot be found. Log: 'Application' Date/Time: 28/10/2010 8:59:16 AM Type: information Category: 0 Event: 2 Source: Diskeeper The Diskeeper Control Center has been started. Diskeeper service started Log: 'Application' Date/Time: 28/10/2010 8:59:16 AM Type: information Category: 0 Event: 0 Source: EvtEng The event description cannot be found. Log: 'Application' Date/Time: 28/10/2010 8:59:14 AM Type: information Category: 1 Event: 101 Source: Automatic LiveUpdate Scheduler Information Level: success Rolling back the schedule; execution will occur at approximately 9:04 AM. Log: 'Application' Date/Time: 28/10/2010 8:59:14 AM Type: information Category: 1 Event: 101 Source: Automatic LiveUpdate Scheduler Information Level: success Service started. Log: 'Application' Date/Time: 28/10/2010 8:59:12 AM Type: information Category: 0 Event: 0 Source: btwdins The event description cannot be found. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 'Application' Log - warning Type ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Log: 'Application' Date/Time: 28/10/2010 8:30:50 AM Type: warning Category: 0 Event: 1517 Source: Userenv Windows saved user JOSH\Joshua Spizman registry while an application or service was still using the registry during log off. The memory used by the user's registry has not been freed. The registry will be unloaded when it is no longer in use. This is often caused by services running as a user account, try configuring the services to run in either the LocalService or NetworkService account. Log: 'Application' Date/Time: 25/10/2010 10:47:36 PM Type: warning Category: 0 Event: 1517 Source: Userenv Windows saved user JOSH\Joshua Spizman registry while an application or service was still using the registry during log off. The memory used by the user's registry has not been freed. The registry will be unloaded when it is no longer in use. This is often caused by services running as a user account, try configuring the services to run in either the LocalService or NetworkService account. Log: 'Application' Date/Time: 25/10/2010 7:51:48 PM Type: warning Category: 0 Event: 1517 Source: Userenv Windows saved user JOSH\Joshua Spizman registry while an application or service was still using the registry during log off. The memory used by the user's registry has not been freed. The registry will be unloaded when it is no longer in use. This is often caused by services running as a user account, try configuring the services to run in either the LocalService or NetworkService account. Log: 'Application' Date/Time: 25/10/2010 3:05:44 PM Type: warning Category: 0 Event: 1517 Source: Userenv Windows saved user JOSH\Joshua Spizman registry while an application or service was still using the registry during log off. The memory used by the user's registry has not been freed. The registry will be unloaded when it is no longer in use. This is often caused by services running as a user account, try configuring the services to run in either the LocalService or NetworkService account. Log: 'Application' Date/Time: 24/10/2010 11:25:39 PM Type: warning Category: 0 Event: 1517 Source: Userenv Windows saved user JOSH\Joshua Spizman registry while an application or service was still using the registry during log off. The memory used by the user's registry has not been freed. The registry will be unloaded when it is no longer in use. This is often caused by services running as a user account, try configuring the services to run in either the LocalService or NetworkService account. Log: 'Application' Date/Time: 24/10/2010 10:58:06 PM Type: warning Category: 0 Event: 1517 Source: Userenv Windows saved user JOSH\Joshua Spizman registry while an application or service was still using the registry during log off. The memory used by the user's registry has not been freed. The registry will be unloaded when it is no longer in use. This is often caused by services running as a user account, try configuring the services to run in either the LocalService or NetworkService account. Log: 'Application' Date/Time: 24/10/2010 8:37:38 PM Type: warning Category: 0 Event: 1517 Source: Userenv Windows saved user JOSH\Joshua Spizman registry while an application or service was still using the registry during log off. The memory used by the user's registry has not been freed. The registry will be unloaded when it is no longer in use. This is often caused by services running as a user account, try configuring the services to run in either the LocalService or NetworkService account. Log: 'Application' Date/Time: 24/10/2010 3:32:12 PM Type: warning Category: 0 Event: 1517 Source: Userenv Windows saved user JOSH\Joshua Spizman registry while an application or service was still using the registry during log off. The memory used by the user's registry has not been freed. The registry will be unloaded when it is no longer in use. This is often caused by services running as a user account, try configuring the services to run in either the LocalService or NetworkService account. Log: 'Application' Date/Time: 24/10/2010 2:30:39 PM Type: warning Category: 0 Event: 1517 Source: Userenv Windows saved user JOSH\Joshua Spizman registry while an application or service was still using the registry during log off. The memory used by the user's registry has not been freed. The registry will be unloaded when it is no longer in use. This is often caused by services running as a user account, try configuring the services to run in either the LocalService or NetworkService account. Log: 'Application' Date/Time: 24/10/2010 1:48:50 PM Type: warning Category: 0 Event: 1517 Source: Userenv Windows saved user JOSH\Joshua Spizman registry while an application or service was still using the registry during log off. The memory used by the user's registry has not been freed. The registry will be unloaded when it is no longer in use. This is often caused by services running as a user account, try configuring the services to run in either the LocalService or NetworkService account. Log: 'Application' Date/Time: 24/10/2010 12:59:20 PM Type: warning Category: 0 Event: 1517 Source: Userenv Windows saved user JOSH\Joshua Spizman registry while an application or service was still using the registry during log off. The memory used by the user's registry has not been freed. The registry will be unloaded when it is no longer in use. This is often caused by services running as a user account, try configuring the services to run in either the LocalService or NetworkService account. Log: 'Application' Date/Time: 24/10/2010 9:54:53 AM Type: warning Category: 0 Event: 1517 Source: Userenv Windows saved user JOSH\Joshua Spizman registry while an application or service was still using the registry during log off. The memory used by the user's registry has not been freed. The registry will be unloaded when it is no longer in use. This is often caused by services running as a user account, try configuring the services to run in either the LocalService or NetworkService account. Log: 'Application' Date/Time: 24/10/2010 9:07:18 AM Type: warning Category: 0 Event: 1517 Source: Userenv Windows saved user JOSH\Joshua Spizman registry while an application or service was still using the registry during log off. The memory used by the user's registry has not been freed. The registry will be unloaded when it is no longer in use. This is often caused by services running as a user account, try configuring the services to run in either the LocalService or NetworkService account. Log: 'Application' Date/Time: 24/10/2010 9:00:25 AM Type: warning Category: 0 Event: 1517 Source: Userenv Windows saved user JOSH\Joshua Spizman registry while an application or service was still using the registry during log off. The memory used by the user's registry has not been freed. The registry will be unloaded when it is no longer in use. This is often caused by services running as a user account, try configuring the services to run in either the LocalService or NetworkService account. Log: 'Application' Date/Time: 22/10/2010 2:34:22 PM Type: warning Category: 0 Event: 1517 Source: Userenv Windows saved user JOSH\Joshua Spizman registry while an application or service was still using the registry during log off. The memory used by the user's registry has not been freed. The registry will be unloaded when it is no longer in use. This is often caused by services running as a user account, try configuring the services to run in either the LocalService or NetworkService account. Log: 'Application' Date/Time: 21/10/2010 11:17:37 PM Type: warning Category: 0 Event: 1517 Source: Userenv Windows saved user JOSH\Joshua Spizman registry while an application or service was still using the registry during log off. The memory used by the user's registry has not been freed. The registry will be unloaded when it is no longer in use. This is often caused by services running as a user account, try configuring the services to run in either the LocalService or NetworkService account. Log: 'Application' Date/Time: 20/10/2010 4:09:29 PM Type: warning Category: 0 Event: 1517 Source: Userenv Windows saved user JOSH\Joshua Spizman registry while an application or service was still using the registry during log off. The memory used by the user's registry has not been freed. The registry will be unloaded when it is no longer in use. This is often caused by services running as a user account, try configuring the services to run in either the LocalService or NetworkService account. Log: 'Application' Date/Time: 20/10/2010 4:03:34 PM Type: warning Category: 0 Event: 1517 Source: Userenv Windows saved user JOSH\Joshua Spizman registry while an application or service was still using the registry during log off. The memory used by the user's registry has not been freed. The registry will be unloaded when it is no longer in use. This is often caused by services running as a user account, try configuring the services to run in either the LocalService or NetworkService account. Log: 'Application' Date/Time: 19/10/2010 10:36:19 PM Type: warning Category: 0 Event: 1517 Source: Userenv Windows saved user JOSH\Joshua Spizman registry while an application or service was still using the registry during log off. The memory used by the user's registry has not been freed. The registry will be unloaded when it is no longer in use. This is often caused by services running as a user account, try configuring the services to run in either the LocalService or NetworkService account. Log: 'Application' Date/Time: 19/10/2010 11:37:28 AM Type: warning Category: 0 Event: 1517 Source: Userenv Windows saved user JOSH\Joshua Spizman registry while an application or service was still using the registry during log off. The memory used by the user's registry has not been freed. The registry will be unloaded when it is no longer in use. This is often caused by services running as a user account, try configuring the services to run in either the LocalService or NetworkService account. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 'System' Log - error Type ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Log: 'System' Date/Time: 28/10/2010 9:02:10 AM Type: error Category: 102 Event: 1003 Source: System Error Error code 10000050, parameter1 ba570000, parameter2 00000001, parameter3 804f4bbe, parameter4 00000000. Log: 'System' Date/Time: 28/10/2010 9:01:52 AM Type: error Category: 102 Event: 1003 Source: System Error Error code 1000007e, parameter1 c0000005, parameter2 8b5171c4, parameter3 ba56fb04, parameter4 ba56f800. Log: 'System' Date/Time: 28/10/2010 8:59:49 AM Type: error Category: 0 Event: 7000 Source: Service Control Manager The Access Connections Main 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. Log: 'System' Date/Time: 28/10/2010 8:59:49 AM Type: error Category: 0 Event: 7009 Source: Service Control Manager Timeout (30000 milliseconds) waiting for the Access Connections Main Service service to connect. Log: 'System' Date/Time: 28/10/2010 8:59:49 AM Type: error Category: 0 Event: 7009 Source: Service Control Manager Timeout (30000 milliseconds) waiting for the Roxio Hard Drive Watcher 9 service to connect. Log: 'System' Date/Time: 28/10/2010 8:54:31 AM Type: error Category: 0 Event: 7000 Source: Service Control Manager The Access Connections Main 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. Log: 'System' Date/Time: 28/10/2010 8:54:31 AM Type: error Category: 0 Event: 7009 Source: Service Control Manager Timeout (30000 milliseconds) waiting for the Access Connections Main Service service to connect. Log: 'System' Date/Time: 28/10/2010 8:54:31 AM Type: error Category: 0 Event: 7009 Source: Service Control Manager Timeout (30000 milliseconds) waiting for the Roxio Hard Drive Watcher 9 service to connect. Log: 'System' Date/Time: 27/10/2010 11:09:17 PM Type: error Category: 102 Event: 1003 Source: System Error Error code 1000007e, parameter1 c0000005, parameter2 8b5101c4, parameter3 ba56fb04, parameter4 ba56f800. Log: 'System' Date/Time: 27/10/2010 11:09:14 PM Type: error Category: 102 Event: 1003 Source: System Error Error code 10000050, parameter1 ba570000, parameter2 00000001, parameter3 804f4bbe, parameter4 00000000. Log: 'System' Date/Time: 27/10/2010 11:08:45 PM Type: error Category: 6 Event: 16 Source: Windows Update Agent Unable to Connect: Windows is unable to connect to the automatic updates service and therefore cannot download and install updates according to the set schedule. Windows will continue to try to establish a connection. Log: 'System' Date/Time: 27/10/2010 11:07:36 PM Type: error Category: 0 Event: 7000 Source: Service Control Manager The Access Connections Main 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. Log: 'System' Date/Time: 27/10/2010 11:07:36 PM Type: error Category: 0 Event: 7009 Source: Service Control Manager Timeout (30000 milliseconds) waiting for the Access Connections Main Service service to connect. Log: 'System' Date/Time: 27/10/2010 11:07:36 PM Type: error Category: 0 Event: 7009 Source: Service Control Manager Timeout (30000 milliseconds) waiting for the Roxio Hard Drive Watcher 9 service to connect. Log: 'System' Date/Time: 27/10/2010 11:05:41 PM Type: error Category: 0 Event: 7000 Source: Service Control Manager The Access Connections Main 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. Log: 'System' Date/Time: 27/10/2010 11:05:41 PM Type: error Category: 0 Event: 7009 Source: Service Control Manager Timeout (30000 milliseconds) waiting for the Access Connections Main Service service to connect. Log: 'System' Date/Time: 27/10/2010 11:05:41 PM Type: error Category: 0 Event: 7009 Source: Service Control Manager Timeout (30000 milliseconds) waiting for the Roxio Hard Drive Watcher 9 service to connect. Log: 'System' Date/Time: 27/10/2010 9:31:26 PM Type: error Category: 0 Event: 7022 Source: Service Control Manager The Automatic Updates service hung on starting. Log: 'System' Date/Time: 27/10/2010 9:29:19 PM Type: error Category: 0 Event: 7000 Source: Service Control Manager The Access Connections Main 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. Log: 'System' Date/Time: 27/10/2010 9:29:19 PM Type: error Category: 0 Event: 7009 Source: Service Control Manager Timeout (30000 milliseconds) waiting for the Access Connections Main Service service to connect. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 'System' Log - information Type ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Log: 'System' Date/Time: 28/10/2010 9:04:20 AM Type: information Category: 0 Event: 7036 Source: Service Control Manager The LiveUpdate service entered the stopped state. Log: 'System' Date/Time: 28/10/2010 9:04:14 AM Type: information Category: 0 Event: 7036 Source: Service Control Manager The LiveUpdate service entered the running state. Log: 'System' Date/Time: 28/10/2010 9:04:14 AM Type: information Category: 0 Event: 7035 Source: Service Control Manager The LiveUpdate service was successfully sent a start control. Log: 'System' Date/Time: 28/10/2010 9:01:26 AM Type: information Category: 0 Event: 7036 Source: Service Control Manager The IMAPI CD-Burning COM Service service entered the stopped state. Log: 'System' Date/Time: 28/10/2010 9:01:20 AM Type: information Category: 0 Event: 7036 Source: Service Control Manager The IMAPI CD-Burning COM Service service entered the running state. Log: 'System' Date/Time: 28/10/2010 9:01:20 AM Type: information Category: 0 Event: 7035 Source: Service Control Manager The IMAPI CD-Burning COM Service service was successfully sent a start control. Log: 'System' Date/Time: 28/10/2010 9:01:11 AM Type: information Category: 0 Event: 7036 Source: Service Control Manager The Remote Access Connection Manager service entered the running state. Log: 'System' Date/Time: 28/10/2010 9:01:08 AM Type: information Category: 0 Event: 7035 Source: Service Control Manager The Remote Access Connection Manager service was successfully sent a start control. Log: 'System' Date/Time: 28/10/2010 9:01:08 AM Type: information Category: 0 Event: 7036 Source: Service Control Manager The Telephony service entered the running state. Log: 'System' Date/Time: 28/10/2010 9:00:50 AM Type: information Category: 0 Event: 7035 Source: Service Control Manager The WAM service was successfully sent a start control. Log: 'System' Date/Time: 28/10/2010 9:00:06 AM Type: information Category: 0 Event: 7036 Source: Service Control Manager The Computer Browser service entered the stopped state. Log: 'System' Date/Time: 28/10/2010 9:00:06 AM Type: information Category: 0 Event: 7036 Source: Service Control Manager The Application Layer Gateway Service service entered the running state. Log: 'System' Date/Time: 28/10/2010 9:00:06 AM Type: information Category: 0 Event: 7036 Source: Service Control Manager The Terminal Services service entered the running state. Log: 'System' Date/Time: 28/10/2010 9:00:06 AM Type: information Category: 0 Event: 7035 Source: Service Control Manager The Terminal Services service was successfully sent a start control. Log: 'System' Date/Time: 28/10/2010 9:00:06 AM Type: information Category: 0 Event: 7035 Source: Service Control Manager The Application Layer Gateway Service service was successfully sent a start control. Log: 'System' Date/Time: 28/10/2010 9:00:05 AM Type: information Category: 0 Event: 7036 Source: Service Control Manager The Network Location Awareness (NLA) service entered the running state. Log: 'System' Date/Time: 28/10/2010 9:00:05 AM Type: information Category: 0 Event: 7035 Source: Service Control Manager The Network Location Awareness (NLA) service was successfully sent a start control. Log: 'System' Date/Time: 28/10/2010 8:59:48 AM Type: information Category: 0 Event: 14204 Source: WMPNetworkSvc Service 'WMPNetworkSvc' started. Log: 'System' Date/Time: 28/10/2010 8:59:23 AM Type: information Category: 0 Event: 33 Source: e1express Intel(R) 82566MM Gigabit Network Connection Link has been established: 100Mbps full duplex. Log: 'System' Date/Time: 28/10/2010 8:59:23 AM Type: information Category: 0 Event: 31 Source: e1express Intel(R) 82566MM Gigabit Network Connection :Spanning Tree Protocol has been detected on the device your network connection is attached to. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 'System' Log - warning Type ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Log: 'System' Date/Time: 27/10/2010 11:16:06 PM Type: warning Category: 0 Event: 27 Source: e1express Intel(R) 82566MM Gigabit Network Connection Link has been disconnected. Log: 'System' Date/Time: 27/10/2010 11:15:32 PM Type: warning Category: 0 Event: 27 Source: e1express Intel(R) 82566MM Gigabit Network Connection Link has been disconnected. Log: 'System' Date/Time: 26/10/2010 8:22:24 AM Type: warning Category: 0 Event: 256 Source: PlugPlayManager Timed out sending notification of device interface change to window of "SAS window" Log: 'System' Date/Time: 26/10/2010 8:21:53 AM Type: warning Category: 0 Event: 50 Source: Fastfat {Delayed Write Failed} Windows was unable to save all the data for the file . The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere. Log: 'System' Date/Time: 25/10/2010 2:05:49 PM Type: warning Category: 0 Event: 263 Source: PlugPlayManager The service "TVT Scheduler" may not have unregistered for device event notifications before it was stopped. Log: 'System' Date/Time: 25/10/2010 1:36:40 PM Type: warning Category: 0 Event: 263 Source: PlugPlayManager The service "TVT Backup Service" may not have unregistered for device event notifications before it was stopped. Log: 'System' Date/Time: 24/10/2010 11:00:44 PM Type: warning Category: 0 Event: 1007 Source: Dhcp Your computer has automatically configured the IP address for the Network Card with network address 001DE04BA0B9. The IP address being used is 169.254.53.54. Log: 'System' Date/Time: 24/10/2010 10:59:35 PM Type: warning Category: 0 Event: 1003 Source: Dhcp Your computer was not able to renew its address from the network (from the DHCP Server) for the Network Card with network address 001DE04BA0B9. The following error occurred: The operation was canceled by the user. . Your computer will continue to try and obtain an address on its own from the network address (DHCP) server. Log: 'System' Date/Time: 24/10/2010 10:28:41 PM Type: warning Category: 0 Event: 1003 Source: Dhcp Your computer was not able to renew its address from the network (from the DHCP Server) for the Network Card with network address 001DE04BA0B9. The following error occurred: The semaphore timeout period has expired. . Your computer will continue to try and obtain an address on its own from the network address (DHCP) server. Log: 'System' Date/Time: 24/10/2010 8:32:45 PM Type: warning Category: 0 Event: 4226 Source: Tcpip TCP/IP has reached the security limit imposed on the number of concurrent TCP connect attempts. Log: 'System' Date/Time: 24/10/2010 8:23:44 PM Type: warning Category: 0 Event: 1007 Source: Dhcp Your computer has automatically configured the IP address for the Network Card with network address 001DE04BA0B9. The IP address being used is 169.254.53.54. Log: 'System' Date/Time: 24/10/2010 8:20:49 PM Type: warning Category: 0 Event: 1003 Source: Dhcp Your computer was not able to renew its address from the network (from the DHCP Server) for the Network Card with network address 001DE04BA0B9. The following error occurred: The semaphore timeout period has expired. . Your computer will continue to try and obtain an address on its own from the network address (DHCP) server. Log: 'System' Date/Time: 24/10/2010 8:01:12 PM Type: warning Category: 0 Event: 3033 Source: MRxSmb The redirector was unable to register the address for transport NetBT_Tcpip_{2744CC89-9216-41A2-AE06-CFC for the following reason: . Transport has been taken offline. Log: 'System' Date/Time: 24/10/2010 7:59:39 PM Type: warning Category: 0 Event: 1003 Source: Dhcp Your computer was not able to renew its address from the network (from the DHCP Server) for the Network Card with network address 001DE04BA0B9. The following error occurred: The semaphore timeout period has expired. . Your computer will continue to try and obtain an address on its own from the network address (DHCP) server. Log: 'System' Date/Time: 24/10/2010 7:59:04 PM Type: warning Category: 0 Event: 3033 Source: MRxSmb The redirector was unable to register the address for transport NetBT_Tcpip_{2F6434C2-7631-4681-81F5-5F8 for the following reason: . Transport has been taken offline. Log: 'System' Date/Time: 24/10/2010 7:59:01 PM Type: warning Category: 0 Event: 1003 Source: Dhcp Your computer was not able to renew its address from the network (from the DHCP Server) for the Network Card with network address 001DE04BA0B9. The following error occurred: The semaphore timeout period has expired. . Your computer will continue to try and obtain an address on its own from the network address (DHCP) server. Log: 'System' Date/Time: 24/10/2010 7:58:37 PM Type: warning Category: 0 Event: 3033 Source: MRxSmb The redirector was unable to register the address for transport NetBT_Tcpip_{2744CC89-9216-41A2-AE06-CFC for the following reason: . Transport has been taken offline. Log: 'System' Date/Time: 24/10/2010 7:50:49 PM Type: warning Category: 0 Event: 1003 Source: Dhcp Your computer was not able to renew its address from the network (from the DHCP Server) for the Network Card with network address 001DE04BA0B9. The following error occurred: The semaphore timeout period has expired. . Your computer will continue to try and obtain an address on its own from the network address (DHCP) server. Log: 'System' Date/Time: 24/10/2010 7:48:25 PM Type: warning Category: 0 Event: 1003 Source: Dhcp Your computer was not able to renew its address from the network (from the DHCP Server) for the Network Card with network address 001DE04BA0B9. The following error occurred: The semaphore timeout period has expired. . Your computer will continue to try and obtain an address on its own from the network address (DHCP) server. Log: 'System' Date/Time: 24/10/2010 7:45:29 PM Type: warning Category: 0 Event: 1003 Source: Dhcp Your computer was not able to renew its address from the network (from the DHCP Server) for the Network Card with network address 001DE04BA0B9. The following error occurred: The semaphore timeout period has expired. . Your computer will continue to try and obtain an address on its own from the network address (DHCP) server.