Vino's Event Viewer v01c run on Windows XP in English Report run at 21/08/2011 08:39:01 AM Note: All dates below are in the format dd/mm/yyyy ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 'Application' Log - error Type ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Log: 'Application' Date/Time: 21/08/2011 08:22:10 Type: error Category: 0 Event: 3011 Source: LoadPerf Unloading the performance counter strings for service PSched (QoS Packet Scheduler) failed. The Error code is the first DWORD in Data section. Log: 'Application' Date/Time: 21/08/2011 08:22:10 Type: error Category: 0 Event: 3001 Source: LoadPerf The performance counter name string value in the registry is incorrectly formatted. The bogus string is 11014, the bogus index value is the first DWORD in Data section while the last valid index values are the second and third DWORD in Data section. Log: 'Application' Date/Time: 21/08/2011 08:18:45 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. Log: 'Application' Date/Time: 21/08/2011 07:22:25 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. Log: 'Application' Date/Time: 13/08/2011 03:33:09 Type: error Category: 0 Event: 8 Source: crypt32 Failed auto update retrieval of third-party root list sequence number from: with error: The server name or address could not be resolved Log: 'Application' Date/Time: 09/08/2011 07:17:28 Type: error Category: 2 Event: 474 Source: ESENT wuauclt (4032) The database page read from the file "C:\WINDOWS\SoftwareDistribution\DataStore\DataStore.edb" at offset 56352768 (0x00000000035be000) for 4096 (0x00001000) bytes failed verification due to a page checksum mismatch. The expected checksum was 2159551533 (0x80b8242d) and the actual checksum was 2159551501 (0x80b8240d). The read operation will fail with error -1018 (0xfffffc06). If this condition persists then please restore the database from a previous backup. Log: 'Application' Date/Time: 25/07/2011 03:22:38 Type: error Category: 0 Event: 1000 Source: Application Error Faulting application unhackme.exe, version 5.9.9.385, faulting module unhackme.exe, version 5.9.9.385, fault address 0x000c5cab. Log: 'Application' Date/Time: 21/07/2011 08:52:10 Type: error Category: 0 Event: 1000 Source: Application Error Faulting application msimn.exe, version 6.0.2900.5512, faulting module mshtml.dll, version 8.0.6001.19088, fault address 0x000a744c. Log: 'Application' Date/Time: 19/07/2011 01:14:24 Type: error Category: 0 Event: 1000 Source: Application Error Faulting application unhackme.exe, version 5.9.9.385, faulting module unhackme.exe, version 5.9.9.385, fault address 0x000c4b8b. Log: 'Application' Date/Time: 12/07/2011 04:26:08 Type: error Category: 2 Event: 474 Source: ESENT wuauclt (2136) The database page read from the file "C:\WINDOWS\SoftwareDistribution\DataStore\DataStore.edb" at offset 5935104 (0x00000000005a9000) for 4096 (0x00001000) bytes failed verification due to a page checksum mismatch. The expected checksum was 2639257178 (0x9d4fde5a) and the actual checksum was 2639257170 (0x9d4fde52). The read operation will fail with error -1018 (0xfffffc06). If this condition persists then please restore the database from a previous backup. Log: 'Application' Date/Time: 12/07/2011 06:24:37 Type: error Category: 2 Event: 474 Source: ESENT wuauclt (4004) The database page read from the file "C:\WINDOWS\SoftwareDistribution\DataStore\DataStore.edb" at offset 7000064 (0x00000000006ad000) for 4096 (0x00001000) bytes failed verification due to a page checksum mismatch. The expected checksum was 2090067448 (0x7c93e5f8) and the actual checksum was 2090067452 (0x7c93e5fc). The read operation will fail with error -1018 (0xfffffc06). If this condition persists then please restore the database from a previous backup. Log: 'Application' Date/Time: 05/07/2011 04:25:36 Type: error Category: 2 Event: 474 Source: ESENT wuauclt (1776) The database page read from the file "C:\WINDOWS\SoftwareDistribution\DataStore\DataStore.edb" at offset 1683456 (0x000000000019b000) for 4096 (0x00001000) bytes failed verification due to a page checksum mismatch. The expected checksum was 1609812161 (0x5ff3c8c1) and the actual checksum was 1609812193 (0x5ff3c8e1). The read operation will fail with error -1018 (0xfffffc06). If this condition persists then please restore the database from a previous backup. Log: 'Application' Date/Time: 29/06/2011 11:15:08 Type: error Category: 100 Event: 1000 Source: Application Error Faulting application wuauclt.exe, version 7.4.7600.226, faulting module esent.dll, version 5.1.2600.5512, fault address 0x000b55cc. Log: 'Application' Date/Time: 29/06/2011 06:13:58 Type: error Category: 2 Event: 474 Source: ESENT wuauclt (1408) The database page read from the file "C:\WINDOWS\SoftwareDistribution\DataStore\DataStore.edb" at offset 22761472 (0x00000000015b5000) for 4096 (0x00001000) bytes failed verification due to a page checksum mismatch. The expected checksum was 2975182981 (0xb155b085) and the actual checksum was 2975183009 (0xb155b0a1). The read operation will fail with error -1018 (0xfffffc06). If this condition persists then please restore the database from a previous backup. Log: 'Application' Date/Time: 23/06/2011 04:23:33 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. Log: 'Application' Date/Time: 14/06/2011 08:19:13 Type: error Category: 3 Event: 465 Source: ESENT wuauclt (768) Corruption was detected during soft recovery in logfile C:\WINDOWS\SoftwareDistribution\DataStore\Logs\edb.log. The failing checksum record is located at position END. Data not matching the log-file fill pattern first appeared in sector 98 (0x00000062). This logfile has been damaged and is unusable. Log: 'Application' Date/Time: 05/06/2011 03:12:27 Type: error Category: 0 Event: 1 Source: PC-Doctor (2560) Asapi: (03:12:27:4680)(2560) PCDExceptionTranslator - Fatal -- 278 Thread id: 2020 exception code: 3221225477 Structured Exception: EXCEPTION_ACCESS_VIOLATION Stack Trace: (end stack trace) Log: 'Application' Date/Time: 22/05/2011 09:23:17 Type: error Category: 2 Event: 474 Source: ESENT wuauclt (3872) The database page read from the file "C:\WINDOWS\SoftwareDistribution\DataStore\DataStore.edb" at offset 26300416 (0x0000000001915000) for 4096 (0x00001000) bytes failed verification due to a page checksum mismatch. The expected checksum was 2139468816 (0x7f85b410) and the actual checksum was 2139468820 (0x7f85b414). The read operation will fail with error -1018 (0xfffffc06). If this condition persists then please restore the database from a previous backup. Log: 'Application' Date/Time: 20/05/2011 04:56:09 Type: error Category: 2 Event: 474 Source: ESENT wuauclt (1084) The database page read from the file "C:\WINDOWS\SoftwareDistribution\DataStore\DataStore.edb" at offset 14139392 (0x0000000000d7c000) for 4096 (0x00001000) bytes failed verification due to a page checksum mismatch. The expected checksum was 3463940699 (0xce778a5b) and the actual checksum was 3463940691 (0xce778a53). The read operation will fail with error -1018 (0xfffffc06). If this condition persists then please restore the database from a previous backup. Log: 'Application' Date/Time: 19/05/2011 11:52:33 Type: error Category: 2 Event: 474 Source: ESENT wuauclt (4004) The database page read from the file "C:\WINDOWS\SoftwareDistribution\DataStore\DataStore.edb" at offset 40869888 (0x00000000026fa000) for 4096 (0x00001000) bytes failed verification due to a page checksum mismatch. The expected checksum was 3098430381 (0xb8ae4bad) and the actual checksum was 3098430361 (0xb8ae4b99). The read operation will fail with error -1018 (0xfffffc06). If this condition persists then please restore the database from a previous backup. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 'Application' Log - information Type ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Log: 'Application' Date/Time: 21/08/2011 08:28:32 Type: information Category: 0 Event: 0 Source: iPod Service The event description cannot be found. Log: 'Application' Date/Time: 21/08/2011 08:27:24 Type: information Category: 0 Event: 1800 Source: SecurityCenter The Windows Security Center Service has started. Log: 'Application' Date/Time: 21/08/2011 08:27:22 Type: information Category: 0 Event: 0 Source: gupdate The event description cannot be found. Log: 'Application' Date/Time: 21/08/2011 08:20:03 Type: information Category: 0 Event: 0 Source: iPod Service The event description cannot be found. Log: 'Application' Date/Time: 21/08/2011 08:18:10 Type: information Category: 0 Event: 1800 Source: SecurityCenter The Windows Security Center Service has started. Log: 'Application' Date/Time: 21/08/2011 08:18:08 Type: information Category: 0 Event: 0 Source: gupdate The event description cannot be found. Log: 'Application' Date/Time: 21/08/2011 08:12:41 Type: information Category: 0 Event: 11724 Source: MsiInstaller Product: Intel(R) PROSet for Wired Connections -- Removal completed successfully. Log: 'Application' Date/Time: 21/08/2011 08:11:54 Type: information Category: 0 Event: 0 Source: NetSvc The event description cannot be found. Log: 'Application' Date/Time: 21/08/2011 07:43:41 Type: information Category: 0 Event: 0 Source: gupdate The event description cannot be found. Log: 'Application' Date/Time: 21/08/2011 07:40:00 Type: information Category: 0 Event: 0 Source: gupdate The event description cannot be found. Log: 'Application' Date/Time: 21/08/2011 07:29:31 Type: information Category: 0 Event: 0 Source: iPod Service The event description cannot be found. Log: 'Application' Date/Time: 21/08/2011 07:28:54 Type: information Category: 0 Event: 1800 Source: SecurityCenter The Windows Security Center Service has started. Log: 'Application' Date/Time: 21/08/2011 07:28:53 Type: information Category: 0 Event: 0 Source: gupdate The event description cannot be found. Log: 'Application' Date/Time: 21/08/2011 07:24:31 Type: information Category: 0 Event: 0 Source: gusvc The event description cannot be found. Log: 'Application' Date/Time: 21/08/2011 07:23:31 Type: information Category: 0 Event: 0 Source: gusvc The event description cannot be found. Log: 'Application' Date/Time: 21/08/2011 07:23:29 Type: information Category: 0 Event: 0 Source: iPod Service The event description cannot be found. Log: 'Application' Date/Time: 21/08/2011 07:22:04 Type: information Category: 0 Event: 1800 Source: SecurityCenter The Windows Security Center Service has started. Log: 'Application' Date/Time: 21/08/2011 07:22:02 Type: information Category: 0 Event: 0 Source: gupdate The event description cannot be found. Log: 'Application' Date/Time: 20/08/2011 06:06:23 Type: information Category: 0 Event: 0 Source: iPod Service The event description cannot be found. Log: 'Application' Date/Time: 20/08/2011 06:03:50 Type: information Category: 0 Event: 1800 Source: SecurityCenter The Windows Security Center Service has started. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 'Application' Log - warning Type ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Log: 'Application' Date/Time: 21/08/2011 08:27:24 Type: warning Category: 1 Event: 32068 Source: Microsoft Fax The outgoing routing rule is not valid because it cannot find a valid device. The outgoing faxes that use this rule will not be routed. Verify that the targeted device or devices (if routed to a group of devices) is connected and installed correctly, and turned on. If routed to a group, verify that the group is configured correctly. Country/region code: '*' Area code: '*' Log: 'Application' Date/Time: 21/08/2011 08:27:24 Type: warning Category: 1 Event: 32026 Source: Microsoft Fax Fax Service failed to initialize any assigned fax devices (virtual or TAPI). No faxes can be sent or received until a fax device is installed. Log: 'Application' Date/Time: 21/08/2011 08:18:10 Type: warning Category: 1 Event: 32068 Source: Microsoft Fax The outgoing routing rule is not valid because it cannot find a valid device. The outgoing faxes that use this rule will not be routed. Verify that the targeted device or devices (if routed to a group of devices) is connected and installed correctly, and turned on. If routed to a group, verify that the group is configured correctly. Country/region code: '*' Area code: '*' Log: 'Application' Date/Time: 21/08/2011 08:18:10 Type: warning Category: 1 Event: 32026 Source: Microsoft Fax Fax Service failed to initialize any assigned fax devices (virtual or TAPI). No faxes can be sent or received until a fax device is installed. Log: 'Application' Date/Time: 21/08/2011 07:28:54 Type: warning Category: 1 Event: 32068 Source: Microsoft Fax The outgoing routing rule is not valid because it cannot find a valid device. The outgoing faxes that use this rule will not be routed. Verify that the targeted device or devices (if routed to a group of devices) is connected and installed correctly, and turned on. If routed to a group, verify that the group is configured correctly. Country/region code: '*' Area code: '*' Log: 'Application' Date/Time: 21/08/2011 07:28:54 Type: warning Category: 1 Event: 32026 Source: Microsoft Fax Fax Service failed to initialize any assigned fax devices (virtual or TAPI). No faxes can be sent or received until a fax device is installed. Log: 'Application' Date/Time: 21/08/2011 07:22:03 Type: warning Category: 1 Event: 32068 Source: Microsoft Fax The outgoing routing rule is not valid because it cannot find a valid device. The outgoing faxes that use this rule will not be routed. Verify that the targeted device or devices (if routed to a group of devices) is connected and installed correctly, and turned on. If routed to a group, verify that the group is configured correctly. Country/region code: '*' Area code: '*' Log: 'Application' Date/Time: 21/08/2011 07:22:03 Type: warning Category: 1 Event: 32026 Source: Microsoft Fax Fax Service failed to initialize any assigned fax devices (virtual or TAPI). No faxes can be sent or received until a fax device is installed. Log: 'Application' Date/Time: 20/08/2011 06:03:50 Type: warning Category: 1 Event: 32068 Source: Microsoft Fax The outgoing routing rule is not valid because it cannot find a valid device. The outgoing faxes that use this rule will not be routed. Verify that the targeted device or devices (if routed to a group of devices) is connected and installed correctly, and turned on. If routed to a group, verify that the group is configured correctly. Country/region code: '*' Area code: '*' Log: 'Application' Date/Time: 20/08/2011 06:03:50 Type: warning Category: 1 Event: 32066 Source: Microsoft Fax At least one of the devices in the outgoing routing group is not valid. Group name: '' Log: 'Application' Date/Time: 20/08/2011 06:03:50 Type: warning Category: 1 Event: 32026 Source: Microsoft Fax Fax Service failed to initialize any assigned fax devices (virtual or TAPI). No faxes can be sent or received until a fax device is installed. Log: 'Application' Date/Time: 20/08/2011 05:35:40 Type: warning Category: 1 Event: 32068 Source: Microsoft Fax The outgoing routing rule is not valid because it cannot find a valid device. The outgoing faxes that use this rule will not be routed. Verify that the targeted device or devices (if routed to a group of devices) is connected and installed correctly, and turned on. If routed to a group, verify that the group is configured correctly. Country/region code: '*' Area code: '*' Log: 'Application' Date/Time: 20/08/2011 05:35:40 Type: warning Category: 1 Event: 32066 Source: Microsoft Fax At least one of the devices in the outgoing routing group is not valid. Group name: '' Log: 'Application' Date/Time: 20/08/2011 05:35:40 Type: warning Category: 1 Event: 32026 Source: Microsoft Fax Fax Service failed to initialize any assigned fax devices (virtual or TAPI). No faxes can be sent or received until a fax device is installed. Log: 'Application' Date/Time: 20/08/2011 05:27:04 Type: warning Category: 1 Event: 32068 Source: Microsoft Fax The outgoing routing rule is not valid because it cannot find a valid device. The outgoing faxes that use this rule will not be routed. Verify that the targeted device or devices (if routed to a group of devices) is connected and installed correctly, and turned on. If routed to a group, verify that the group is configured correctly. Country/region code: '*' Area code: '*' Log: 'Application' Date/Time: 20/08/2011 05:27:04 Type: warning Category: 1 Event: 32026 Source: Microsoft Fax Fax Service failed to initialize any assigned fax devices (virtual or TAPI). No faxes can be sent or received until a fax device is installed. Log: 'Application' Date/Time: 20/08/2011 04:58:44 Type: warning Category: 1 Event: 32068 Source: Microsoft Fax The outgoing routing rule is not valid because it cannot find a valid device. The outgoing faxes that use this rule will not be routed. Verify that the targeted device or devices (if routed to a group of devices) is connected and installed correctly, and turned on. If routed to a group, verify that the group is configured correctly. Country/region code: '*' Area code: '*' Log: 'Application' Date/Time: 20/08/2011 04:58:44 Type: warning Category: 1 Event: 32026 Source: Microsoft Fax Fax Service failed to initialize any assigned fax devices (virtual or TAPI). No faxes can be sent or received until a fax device is installed. Log: 'Application' Date/Time: 20/08/2011 04:55:43 Type: warning Category: 1 Event: 32068 Source: Microsoft Fax The outgoing routing rule is not valid because it cannot find a valid device. The outgoing faxes that use this rule will not be routed. Verify that the targeted device or devices (if routed to a group of devices) is connected and installed correctly, and turned on. If routed to a group, verify that the group is configured correctly. Country/region code: '*' Area code: '*' Log: 'Application' Date/Time: 20/08/2011 04:55:43 Type: warning Category: 1 Event: 32026 Source: Microsoft Fax Fax Service failed to initialize any assigned fax devices (virtual or TAPI). No faxes can be sent or received until a fax device is installed. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 'System' Log - error Type ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Log: 'System' Date/Time: 21/08/2011 08:32:12 Type: error Category: 0 Event: 29 Source: W32Time The time provider NtpClient is configured to acquire time from one or more time sources, however none of the sources are currently accessible. No attempt to contact a source will be made for 14 minutes. NtpClient has no source of accurate time. Log: 'System' Date/Time: 21/08/2011 08:32:12 Type: error Category: 0 Event: 17 Source: W32Time Time Provider NtpClient: An error occurred during DNS lookup of the manually configured peer 'time-c.timefreq.bldrdoc.gov,0x1'. NtpClient will try the DNS lookup again in 15 minutes. The error was: A socket operation was attempted to an unreachable host. (0x80072751) Log: 'System' Date/Time: 21/08/2011 08:30:58 Type: error Category: 0 Event: 29 Source: W32Time The time provider NtpClient is configured to acquire time from one or more time sources, however none of the sources are currently accessible. No attempt to contact a source will be made for 14 minutes. NtpClient has no source of accurate time. Log: 'System' Date/Time: 21/08/2011 08:30:58 Type: error Category: 0 Event: 17 Source: W32Time Time Provider NtpClient: An error occurred during DNS lookup of the manually configured peer 'time-c.timefreq.bldrdoc.gov,0x1'. NtpClient will try the DNS lookup again in 15 minutes. The error was: A socket operation was attempted to an unreachable host. (0x80072751) Log: 'System' Date/Time: 21/08/2011 08:28:16 Type: error Category: 0 Event: 29 Source: W32Time The time provider NtpClient is configured to acquire time from one or more time sources, however none of the sources are currently accessible. No attempt to contact a source will be made for 14 minutes. NtpClient has no source of accurate time. Log: 'System' Date/Time: 21/08/2011 08:28:16 Type: error Category: 0 Event: 17 Source: W32Time Time Provider NtpClient: An error occurred during DNS lookup of the manually configured peer 'time-c.timefreq.bldrdoc.gov,0x1'. NtpClient will try the DNS lookup again in 15 minutes. The error was: A socket operation was attempted to an unreachable host. (0x80072751) Log: 'System' Date/Time: 21/08/2011 08:28:01 Type: error Category: 0 Event: 29 Source: W32Time The time provider NtpClient is configured to acquire time from one or more time sources, however none of the sources are currently accessible. No attempt to contact a source will be made for 14 minutes. NtpClient has no source of accurate time. Log: 'System' Date/Time: 21/08/2011 08:28:01 Type: error Category: 0 Event: 17 Source: W32Time Time Provider NtpClient: An error occurred during DNS lookup of the manually configured peer 'time-c.timefreq.bldrdoc.gov,0x1'. NtpClient will try the DNS lookup again in 15 minutes. The error was: A socket operation was attempted to an unreachable host. (0x80072751) Log: 'System' Date/Time: 21/08/2011 08:27:43 Type: error Category: 0 Event: 29 Source: W32Time The time provider NtpClient is configured to acquire time from one or more time sources, however none of the sources are currently accessible. No attempt to contact a source will be made for 14 minutes. NtpClient has no source of accurate time. Log: 'System' Date/Time: 21/08/2011 08:27:43 Type: error Category: 0 Event: 17 Source: W32Time Time Provider NtpClient: An error occurred during DNS lookup of the manually configured peer 'time-c.timefreq.bldrdoc.gov,0x1'. NtpClient will try the DNS lookup again in 15 minutes. The error was: A socket operation was attempted to an unreachable host. (0x80072751) Log: 'System' Date/Time: 21/08/2011 08:27:40 Type: error Category: 0 Event: 29 Source: W32Time The time provider NtpClient is configured to acquire time from one or more time sources, however none of the sources are currently accessible. No attempt to contact a source will be made for 15 minutes. NtpClient has no source of accurate time. Log: 'System' Date/Time: 21/08/2011 08:27:40 Type: error Category: 0 Event: 17 Source: W32Time Time Provider NtpClient: An error occurred during DNS lookup of the manually configured peer 'time-c.timefreq.bldrdoc.gov,0x1'. NtpClient will try the DNS lookup again in 15 minutes. The error was: A socket operation was attempted to an unreachable host. (0x80072751) Log: 'System' Date/Time: 21/08/2011 08:27:24 Type: error Category: 0 Event: 7023 Source: Service Control Manager The IPSEC Services service terminated with the following error: The authentication service is unknown. Log: 'System' Date/Time: 21/08/2011 08:27:24 Type: error Category: 0 Event: 7000 Source: Service Control Manager The Ulead Burning Helper service failed to start due to the following error: The system cannot find the file specified. Log: 'System' Date/Time: 21/08/2011 08:27:24 Type: error Category: 0 Event: 7000 Source: Service Control Manager The SupportSoft Sprocket Service (dellsupportcenter) service failed to start due to the following error: The system cannot find the file specified. Log: 'System' Date/Time: 21/08/2011 08:23:44 Type: error Category: 0 Event: 29 Source: W32Time The time provider NtpClient is configured to acquire time from one or more time sources, however none of the sources are currently accessible. No attempt to contact a source will be made for 14 minutes. NtpClient has no source of accurate time. Log: 'System' Date/Time: 21/08/2011 08:23:44 Type: error Category: 0 Event: 17 Source: W32Time Time Provider NtpClient: An error occurred during DNS lookup of the manually configured peer 'time-c.timefreq.bldrdoc.gov,0x1'. NtpClient will try the DNS lookup again in 15 minutes. The error was: A socket operation was attempted to an unreachable host. (0x80072751) Log: 'System' Date/Time: 21/08/2011 08:23:29 Type: error Category: 0 Event: 29 Source: W32Time The time provider NtpClient is configured to acquire time from one or more time sources, however none of the sources are currently accessible. No attempt to contact a source will be made for 14 minutes. NtpClient has no source of accurate time. Log: 'System' Date/Time: 21/08/2011 08:23:29 Type: error Category: 0 Event: 17 Source: W32Time Time Provider NtpClient: An error occurred during DNS lookup of the manually configured peer 'time-c.timefreq.bldrdoc.gov,0x1'. NtpClient will try the DNS lookup again in 15 minutes. The error was: A socket operation was attempted to an unreachable host. (0x80072751) Log: 'System' Date/Time: 21/08/2011 08:23:11 Type: error Category: 0 Event: 29 Source: W32Time The time provider NtpClient is configured to acquire time from one or more time sources, however none of the sources are currently accessible. No attempt to contact a source will be made for 14 minutes. NtpClient has no source of accurate time. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 'System' Log - information Type ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Log: 'System' Date/Time: 21/08/2011 08:30:55 Type: information Category: 0 Event: 4202 Source: Tcpip The system detected that network adapter Intel(R) PRO/100 VE Network Connection was disconnected from the network, and the adapter's network configuration has been released. If the network adapter was not disconnected, this may indicate that it has malfunctioned. Please contact your vendor for updated drivers. Log: 'System' Date/Time: 21/08/2011 08:28:37 Type: information Category: 0 Event: 7035 Source: Service Control Manager The IP Traffic Filter Driver service was successfully sent a start control. Log: 'System' Date/Time: 21/08/2011 08:28:35 Type: information Category: 0 Event: 7035 Source: Service Control Manager The DSproct service was successfully sent a start control. Log: 'System' Date/Time: 21/08/2011 08:28:34 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: 21/08/2011 08:28:32 Type: information Category: 0 Event: 7036 Source: Service Control Manager The iPod Service service entered the running state. Log: 'System' Date/Time: 21/08/2011 08:28:32 Type: information Category: 0 Event: 7035 Source: Service Control Manager The iPod Service service was successfully sent a start control. Log: 'System' Date/Time: 21/08/2011 08:28:26 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: 21/08/2011 08:28:26 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: 21/08/2011 08:28:21 Type: information Category: 0 Event: 7036 Source: Service Control Manager The SSDP Discovery Service service entered the running state. Log: 'System' Date/Time: 21/08/2011 08:28:20 Type: information Category: 0 Event: 7036 Source: Service Control Manager The Remote Access Connection Manager service entered the running state. Log: 'System' Date/Time: 21/08/2011 08:28:19 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: 21/08/2011 08:28:19 Type: information Category: 0 Event: 7035 Source: Service Control Manager The SSDP Discovery Service service was successfully sent a start control. Log: 'System' Date/Time: 21/08/2011 08:27:29 Type: information Category: 0 Event: 7036 Source: Service Control Manager The Fast User Switching Compatibility service entered the running state. Log: 'System' Date/Time: 21/08/2011 08:27:29 Type: information Category: 0 Event: 7035 Source: Service Control Manager The Fast User Switching Compatibility service was successfully sent a start control. Log: 'System' Date/Time: 21/08/2011 08:27:29 Type: information Category: 0 Event: 7036 Source: Service Control Manager The Terminal Services service entered the running state. Log: 'System' Date/Time: 21/08/2011 08:27:25 Type: information Category: 0 Event: 4201 Source: Tcpip The system detected that network adapter TRENDnet,... 32-bit 10/100/1000Mbps PCI ADAPTER was connected to the network, and has initiated normal operation over the network adapter. Log: 'System' Date/Time: 21/08/2011 08:27:25 Type: information Category: 0 Event: 7036 Source: Service Control Manager The Application Layer Gateway Service service entered the running state. Log: 'System' Date/Time: 21/08/2011 08:27:25 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: 21/08/2011 08:27:25 Type: information Category: 0 Event: 7036 Source: Service Control Manager The Fax service entered the stopped state. Log: 'System' Date/Time: 21/08/2011 08:27:25 Type: information Category: 0 Event: 7036 Source: Service Control Manager The Background Intelligent Transfer Service service entered the running state. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 'System' Log - warning Type ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Log: 'System' Date/Time: 21/08/2011 08:32:34 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 0014D126F372. 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: 21/08/2011 08:30:13 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 0014D126F372. 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: 21/08/2011 08:27:43 Type: warning Category: 0 Event: 1007 Source: Dhcp Your computer has automatically configured the IP address for the Network Card with network address 0014D126F372. The IP address being used is 169.254.48.122. Log: 'System' Date/Time: 21/08/2011 08:27:37 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 0014D126F372. 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: 21/08/2011 08:23:11 Type: warning Category: 0 Event: 1007 Source: Dhcp Your computer has automatically configured the IP address for the Network Card with network address 0014D126F372. The IP address being used is 169.254.48.122. Log: 'System' Date/Time: 21/08/2011 08:21:55 Type: warning Category: 0 Event: 2504 Source: Server The server could not bind to the transport \Device\NetBT_Tcpip_{67BD3B46-1652-4C22-AD6C-23A30F720E0C}. Log: 'System' Date/Time: 21/08/2011 08:21:52 Type: warning Category: 0 Event: 1007 Source: Dhcp Your computer has automatically configured the IP address for the Network Card with network address 0014D126F372. The IP address being used is 169.254.48.122. Log: 'System' Date/Time: 21/08/2011 08:20:41 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 0014D126F372. 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: 21/08/2011 08:18:02 Type: warning Category: 0 Event: 1007 Source: Dhcp Your computer has automatically configured the IP address for the Network Card with network address 0014D126F372. The IP address being used is 169.254.48.122. Log: 'System' Date/Time: 21/08/2011 08:16:11 Type: warning Category: 0 Event: 1007 Source: Dhcp Your computer has automatically configured the IP address for the Network Card with network address 0014D126F372. The IP address being used is 169.254.48.122. Log: 'System' Date/Time: 21/08/2011 07:29:04 Type: warning Category: 0 Event: 2504 Source: Server The server could not bind to the transport \Device\NetBT_Tcpip_{67BD3B46-1652-4C22-AD6C-23A30F720E0C}. Log: 'System' Date/Time: 21/08/2011 07:28:55 Type: warning Category: 0 Event: 1007 Source: Dhcp Your computer has automatically configured the IP address for the Network Card with network address 0014D126F372. The IP address being used is 169.254.48.122. Log: 'System' Date/Time: 21/08/2011 07:28:49 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 0014D126F372. 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: 21/08/2011 07:22:02 Type: warning Category: 0 Event: 1007 Source: Dhcp Your computer has automatically configured the IP address for the Network Card with network address 0014D126F372. The IP address being used is 169.254.48.122. Log: 'System' Date/Time: 21/08/2011 07:21:52 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 0014D126F372. 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: 20/08/2011 06:24:05 Type: warning Category: 0 Event: 1007 Source: Dhcp Your computer has automatically configured the IP address for the Network Card with network address 0014D126F372. The IP address being used is 169.254.48.122. Log: 'System' Date/Time: 20/08/2011 06:21:55 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 0014D126F372. 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: 20/08/2011 06:21:19 Type: warning Category: 0 Event: 1007 Source: Dhcp Your computer has automatically configured the IP address for the Network Card with network address 0014D126F372. The IP address being used is 169.254.48.122. Log: 'System' Date/Time: 20/08/2011 06:15:35 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 0014D126F372. 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: 20/08/2011 06:15:00 Type: warning Category: 0 Event: 1007 Source: Dhcp Your computer has automatically configured the IP address for the Network Card with network address 0014D126F372. The IP address being used is 169.254.48.122.