Running VEW.exe produced:
Vino's Event Viewer v01c run on Windows 2008 in English
Report run at 23/01/2011 7:36:13 PM
Note: All dates below are in the format dd/mm/yyyy
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 21/01/2011 5:42:43 AM
Type: Error Category: 101
Event: 1002 Source: Application Hang
The program ehshell.exe version 6.1.7600.16385 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel. Process ID: de8 Start Time: 01cbb9264d2b3042 Termination Time: 0 Application Path: C:\Windows\ehome\ehshell.exe Report Id:
Log: 'Application' Date/Time: 18/01/2011 4:39:33 PM
Type: Error Category: 0
Event: 35 Source: Outlook
Failed to determine if the store is in the crawl scope (error=0x8007043c).
Log: 'Application' Date/Time: 18/01/2011 4:39:33 PM
Type: Error Category: 0
Event: 34 Source: Outlook
Failed to get the Crawl Scope Manager with error=0x8007043c.
Log: 'Application' Date/Time: 18/01/2011 4:39:31 PM
Type: Error Category: 0
Event: 35 Source: Outlook
Failed to determine if the store is in the crawl scope (error=0x8007043c).
Log: 'Application' Date/Time: 18/01/2011 4:39:31 PM
Type: Error Category: 0
Event: 34 Source: Outlook
Failed to get the Crawl Scope Manager with error=0x8007043c.
Log: 'Application' Date/Time: 18/01/2011 2:00:23 AM
Type: Error Category: 0
Event: 11905 Source: MsiInstaller
Product: hppSendFaxCM1312 -- Error 1905.Module C:\Program Files (x86)\HP\HP Color LaserJet CM1312 MFP Series\HppTcComMsg.dll failed to unregister. HRESULT -2147220472. Contact your support personnel.
Log: 'Application' Date/Time: 18/01/2011 1:31:42 AM
Type: Error Category: 0
Event: 512 Source: Microsoft-Windows-CAPI2
The Cryptographic Services service failed to initialize the VSS backup "System Writer" object.
Details:
Could not query the status of the EventSystem service.
System Error:
A system shutdown is in progress. .
Log: 'Application' Date/Time: 14/01/2011 5:05:35 PM
Type: Error Category: 0
Event: 35 Source: Outlook
Failed to determine if the store is in the crawl scope (error=0x8007043c).
Log: 'Application' Date/Time: 14/01/2011 5:05:35 PM
Type: Error Category: 0
Event: 34 Source: Outlook
Failed to get the Crawl Scope Manager with error=0x8007043c.
Log: 'Application' Date/Time: 14/01/2011 5:05:35 PM
Type: Error Category: 0
Event: 35 Source: Outlook
Failed to determine if the store is in the crawl scope (error=0x8007043c).
Log: 'Application' Date/Time: 14/01/2011 5:05:35 PM
Type: Error Category: 0
Event: 34 Source: Outlook
Failed to get the Crawl Scope Manager with error=0x8007043c.
Log: 'Application' Date/Time: 14/01/2011 4:58:17 PM
Type: Error Category: 0
Event: 35 Source: Outlook
Failed to determine if the store is in the crawl scope (error=0x8007043c).
Log: 'Application' Date/Time: 14/01/2011 4:58:17 PM
Type: Error Category: 0
Event: 34 Source: Outlook
Failed to get the Crawl Scope Manager with error=0x8007043c.
Log: 'Application' Date/Time: 14/01/2011 4:58:14 PM
Type: Error Category: 0
Event: 35 Source: Outlook
Failed to determine if the store is in the crawl scope (error=0x8007043c).
Log: 'Application' Date/Time: 14/01/2011 4:58:14 PM
Type: Error Category: 0
Event: 34 Source: Outlook
Failed to get the Crawl Scope Manager with error=0x8007043c.
Log: 'Application' Date/Time: 11/01/2011 5:06:40 PM
Type: Error Category: 0
Event: 0 Source: TOSHIBA Service Station
TSS Load: could not communicate with TMachInfo service
Log: 'Application' Date/Time: 11/01/2011 3:51:33 AM
Type: Error Category: 0
Event: 8194 Source: VSS
Volume Shadow Copy Service error: Unexpected error querying for the IVssWriterCallback interface. hr = 0x80070005, Access is denied. . This is often caused by incorrect security settings in either the writer or requestor process.
Operation:
Gathering Writer Data
Context:
Writer Class Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Name: System Writer
Writer Instance ID: {ed4a0eef-0560-4bff-b7ac-b6114fe71ea0}
Log: 'Application' Date/Time: 10/01/2011 11:43:53 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: autorun.exe_Hewlett Packard StubApp, version: 1.0.0.9, time stamp: 0x4728cacb Faulting module name: ntdll.dll, version: 6.1.7600.16559, time stamp: 0x4ba9b29c Exception code: 0xc0000374 Fault offset: 0x000cdc9b Faulting process id: 0xbe0 Faulting application start time: 0x01cbb1203bd6f39e Faulting application path: D:\autorun.exe Faulting module path: C:\windows\SysWOW64\ntdll.dll Report Id: 7ad4b043-1d13-11e0-b65b-88ae1d45c284
Log: 'Application' Date/Time: 10/01/2011 11:38:29 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: autorun.exe_Hewlett Packard StubApp, version: 1.0.0.9, time stamp: 0x4728cacb Faulting module name: ntdll.dll, version: 6.1.7600.16559, time stamp: 0x4ba9b29c Exception code: 0xc0000374 Fault offset: 0x000cdc9b Faulting process id: 0x1790 Faulting application start time: 0x01cbb11f78728b1d Faulting application path: D:\autorun.exe Faulting module path: C:\windows\SysWOW64\ntdll.dll Report Id: b9d4fc62-1d12-11e0-b65b-88ae1d45c284
Log: 'Application' Date/Time: 09/01/2011 12:50:03 AM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: OUTLOOK.EXE, version: 12.0.6548.5000, time stamp: 0x4cafbeb3 Faulting module name: ntdll.dll, version: 6.1.7600.16559, time stamp: 0x4ba9b29c Exception code: 0xc0000005 Fault offset: 0x00038c19 Faulting process id: 0x141c Faulting application start time: 0x01cbaf9718f049ee Faulting application path: C:\Program Files (x86)\Microsoft Office\Office12\OUTLOOK.EXE Faulting module path: C:\windows\SysWOW64\ntdll.dll Report Id: 6447fb9e-1b8a-11e0-99c1-88ae1d45c284
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 23/01/2011 4:10:06 AM
Type: Warning Category: 0
Event: 0 Source: TOSHIBA Service Station
Skipping empty element [tsu:setup_args]
Log: 'Application' Date/Time: 23/01/2011 4:10:06 AM
Type: Warning Category: 0
Event: 0 Source: TOSHIBA Service Station
Skipping empty element [tsu:setup_args]
Log: 'Application' Date/Time: 23/01/2011 4:10:06 AM
Type: Warning Category: 0
Event: 0 Source: TOSHIBA Service Station
Skipping empty element [tsu:setup_args]
Log: 'Application' Date/Time: 23/01/2011 4:10:06 AM
Type: Warning Category: 0
Event: 0 Source: TOSHIBA Service Station
Skipping empty element [tsu:setup_args]
Log: 'Application' Date/Time: 23/01/2011 4:10:06 AM
Type: Warning Category: 0
Event: 0 Source: TOSHIBA Service Station
Skipping empty element [tsu:setup_args]
Log: 'Application' Date/Time: 23/01/2011 4:10:06 AM
Type: Warning Category: 0
Event: 0 Source: TOSHIBA Service Station
Skipping empty element [tsu:setup_args]
Log: 'Application' Date/Time: 23/01/2011 4:10:06 AM
Type: Warning Category: 0
Event: 0 Source: TOSHIBA Service Station
Skipping empty element [tsu:setup_args]
Log: 'Application' Date/Time: 23/01/2011 4:10:06 AM
Type: Warning Category: 0
Event: 0 Source: TOSHIBA Service Station
Skipping empty element [tsu:setup_args]
Log: 'Application' Date/Time: 23/01/2011 4:10:06 AM
Type: Warning Category: 0
Event: 0 Source: TOSHIBA Service Station
Skipping empty element [tsu:setup_args]
Log: 'Application' Date/Time: 23/01/2011 4:10:06 AM
Type: Warning Category: 0
Event: 0 Source: TOSHIBA Service Station
Skipping empty element [tsu:setup_args]
Log: 'Application' Date/Time: 23/01/2011 4:10:06 AM
Type: Warning Category: 0
Event: 0 Source: TOSHIBA Service Station
Skipping empty element [tsu:setup_args]
Log: 'Application' Date/Time: 23/01/2011 4:10:06 AM
Type: Warning Category: 0
Event: 0 Source: TOSHIBA Service Station
Skipping empty element [tsu:setup_args]
Log: 'Application' Date/Time: 22/01/2011 9:04:08 PM
Type: Warning Category: 0
Event: 0 Source: TOSHIBA Service Station
Skipping empty element [tsu:setup_args]
Log: 'Application' Date/Time: 22/01/2011 9:04:08 PM
Type: Warning Category: 0
Event: 0 Source: TOSHIBA Service Station
Skipping empty element [tsu:setup_args]
Log: 'Application' Date/Time: 22/01/2011 9:04:08 PM
Type: Warning Category: 0
Event: 0 Source: TOSHIBA Service Station
Skipping empty element [tsu:setup_args]
Log: 'Application' Date/Time: 22/01/2011 9:04:08 PM
Type: Warning Category: 0
Event: 0 Source: TOSHIBA Service Station
Skipping empty element [tsu:setup_args]
Log: 'Application' Date/Time: 22/01/2011 9:04:08 PM
Type: Warning Category: 0
Event: 0 Source: TOSHIBA Service Station
Skipping empty element [tsu:setup_args]
Log: 'Application' Date/Time: 22/01/2011 9:04:08 PM
Type: Warning Category: 0
Event: 0 Source: TOSHIBA Service Station
Skipping empty element [tsu:setup_args]
Log: 'Application' Date/Time: 22/01/2011 9:04:08 PM
Type: Warning Category: 0
Event: 0 Source: TOSHIBA Service Station
Skipping empty element [tsu:setup_args]
Log: 'Application' Date/Time: 22/01/2011 9:04:08 PM
Type: Warning Category: 0
Event: 0 Source: TOSHIBA Service Station
Skipping empty element [tsu:setup_args]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 22/01/2011 9:01:57 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Log: 'System' Date/Time: 22/01/2011 7:25:17 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Log: 'System' Date/Time: 22/01/2011 1:03:46 AM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Log: 'System' Date/Time: 20/01/2011 9:10:32 AM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Log: 'System' Date/Time: 19/01/2011 5:15:56 AM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Log: 'System' Date/Time: 18/01/2011 4:26:19 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Log: 'System' Date/Time: 18/01/2011 10:55:48 AM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Log: 'System' Date/Time: 18/01/2011 4:09:32 AM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Log: 'System' Date/Time: 18/01/2011 1:31:20 AM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Log: 'System' Date/Time: 17/01/2011 11:44:57 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Log: 'System' Date/Time: 17/01/2011 10:03:45 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Log: 'System' Date/Time: 17/01/2011 9:48:33 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Log: 'System' Date/Time: 17/01/2011 8:31:54 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Log: 'System' Date/Time: 17/01/2011 6:31:00 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Log: 'System' Date/Time: 17/01/2011 3:45:45 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Log: 'System' Date/Time: 16/01/2011 2:58:16 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Log: 'System' Date/Time: 16/01/2011 3:40:49 AM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Log: 'System' Date/Time: 14/01/2011 5:14:14 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Log: 'System' Date/Time: 14/01/2011 3:48:37 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Log: 'System' Date/Time: 14/01/2011 12:32:21 AM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 24/01/2011 12:08:43 AM
Type: Error Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D3DCB472-7261-43CE-924B-0704BD730D5F} and APPID {D3DCB472-7261-43CE-924B-0704BD730D5F} to the user Craig-PC\Craig SID (S-1-5-21-1913969698-936728373-2302265488-1000) from address LocalHost (Using LRPC). This security permission can be modified using the Component Services administrative tool.
Log: 'System' Date/Time: 24/01/2011 12:08:43 AM
Type: Error Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {145B4335-FE2A-4927-A040-7C35AD3180EF} and APPID {145B4335-FE2A-4927-A040-7C35AD3180EF} to the user Craig-PC\Craig SID (S-1-5-21-1913969698-936728373-2302265488-1000) from address LocalHost (Using LRPC). This security permission can be modified using the Component Services administrative tool.
Log: 'System' Date/Time: 22/01/2011 9:02:04 PM
Type: Error Category: 0
Event: 6008 Source: EventLog
The previous system shutdown at 2:45:17 PM on ?1/?22/?2011 was unexpected.
Log: 'System' Date/Time: 22/01/2011 7:25:25 PM
Type: Error Category: 0
Event: 6008 Source: EventLog
The previous system shutdown at 1:09:37 PM on ?1/?22/?2011 was unexpected.
Log: 'System' Date/Time: 22/01/2011 1:04:51 AM
Type: Error Category: 0
Event: 7011 Source: Service Control Manager
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the wlidsvc service.
Log: 'System' Date/Time: 22/01/2011 1:04:03 AM
Type: Error Category: 0
Event: 6008 Source: EventLog
The previous system shutdown at 6:56:39 PM on ?1/?21/?2011 was unexpected.
Log: 'System' Date/Time: 20/01/2011 8:03:19 PM
Type: Error Category: 0
Event: 11 Source: Disk
The driver detected a controller error on \Device\Harddisk1\DR1.
Log: 'System' Date/Time: 20/01/2011 6:09:05 PM
Type: Error Category: 0
Event: 11 Source: Disk
The driver detected a controller error on \Device\Harddisk1\DR1.
Log: 'System' Date/Time: 20/01/2011 9:12:02 AM
Type: Error Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID {C97FCC79-E628-407D-AE68-A06AD6D8B4D1} and APPID {344ED43D-D086-4961-86A6-1106F4ACAD9B} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC). This security permission can be modified using the Component Services administrative tool.
Log: 'System' Date/Time: 20/01/2011 9:10:40 AM
Type: Error Category: 0
Event: 6008 Source: EventLog
The previous system shutdown at 11:44:22 PM on ?1/?19/?2011 was unexpected.
Log: 'System' Date/Time: 19/01/2011 10:22:24 PM
Type: Error Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID {C97FCC79-E628-407D-AE68-A06AD6D8B4D1} and APPID {344ED43D-D086-4961-86A6-1106F4ACAD9B} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC). This security permission can be modified using the Component Services administrative tool.
Log: 'System' Date/Time: 19/01/2011 10:19:07 PM
Type: Error Category: 2
Event: 137 Source: Ntfs
The default transaction resource manager on volume E: encountered a non-retryable error and could not start. The data contains the error code.
Log: 'System' Date/Time: 19/01/2011 5:47:38 PM
Type: Error Category: 0
Event: 11 Source: Disk
The driver detected a controller error on \Device\Harddisk1\DR2.
Log: 'System' Date/Time: 19/01/2011 5:17:17 AM
Type: Error Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID {C97FCC79-E628-407D-AE68-A06AD6D8B4D1} and APPID {344ED43D-D086-4961-86A6-1106F4ACAD9B} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC). This security permission can be modified using the Component Services administrative tool.
Log: 'System' Date/Time: 19/01/2011 5:16:05 AM
Type: Error Category: 0
Event: 6008 Source: EventLog
The previous system shutdown at 6:32:14 PM on ?1/?18/?2011 was unexpected.
Log: 'System' Date/Time: 18/01/2011 5:19:04 PM
Type: Error Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID {C97FCC79-E628-407D-AE68-A06AD6D8B4D1} and APPID {344ED43D-D086-4961-86A6-1106F4ACAD9B} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC). This security permission can be modified using the Component Services administrative tool.
Log: 'System' Date/Time: 18/01/2011 5:17:08 PM
Type: Error Category: 0
Event: 7001 Source: Service Control Manager
The Computer Browser service depends on the Server service which failed to start because of the following error: The dependency service or group failed to start.
Log: 'System' Date/Time: 18/01/2011 5:17:08 PM
Type: Error Category: 0
Event: 7001 Source: Service Control Manager
The Computer Browser service depends on the Server service which failed to start because of the following error: The dependency service or group failed to start.
Log: 'System' Date/Time: 18/01/2011 5:17:08 PM
Type: Error Category: 0
Event: 7001 Source: Service Control Manager
The Computer Browser service depends on the Server service which failed to start because of the following error: The dependency service or group failed to start.
Log: 'System' Date/Time: 18/01/2011 5:17:08 PM
Type: Error Category: 0
Event: 7001 Source: Service Control Manager
The Computer Browser service depends on the Server service which failed to start because of the following error: The dependency service or group failed to start.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 23/01/2011 8:10:57 AM
Type: Warning Category: 0
Event: 134 Source: Microsoft-Windows-Time-Service
NtpClient was unable to set a manual peer to use as a time source because of DNS resolution error on ''. NtpClient will try again in 3473457 minutes and double the reattempt interval thereafter. The error was: The requested name is valid, but no data of the requested type was found. (0x80072AFC)
Log: 'System' Date/Time: 23/01/2011 8:10:56 AM
Type: Warning Category: 0
Event: 134 Source: Microsoft-Windows-Time-Service
NtpClient was unable to set a manual peer to use as a time source because of DNS resolution error on ''. NtpClient will try again in 3473457 minutes and double the reattempt interval thereafter. The error was: The requested name is valid, but no data of the requested type was found. (0x80072AFC)
Log: 'System' Date/Time: 23/01/2011 4:18:07 AM
Type: Warning Category: 0
Event: 1006 Source: Microsoft-Windows-DNS-Client
The client was unable to validate the following as active DNS server(s) that can service this client. The server(s) may be temporarily unavailable, or may be incorrectly configured. 192.168.1.1
Log: 'System' Date/Time: 23/01/2011 4:07:41 AM
Type: Warning Category: 0
Event: 4001 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN AutoConfig service has successfully stopped.
Log: 'System' Date/Time: 22/01/2011 1:07:24 AM
Type: Warning Category: 0
Event: 4001 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN AutoConfig service has successfully stopped.
Log: 'System' Date/Time: 20/01/2011 9:40:30 PM
Type: Warning Category: 0
Event: 51 Source: Disk
An error was detected on device \Device\Harddisk1\DR1 during a paging operation.
Log: 'System' Date/Time: 20/01/2011 9:35:35 PM
Type: Warning Category: 0
Event: 51 Source: Disk
An error was detected on device \Device\Harddisk1\DR1 during a paging operation.
Log: 'System' Date/Time: 20/01/2011 9:24:56 PM
Type: Warning Category: 0
Event: 51 Source: Disk
An error was detected on device \Device\Harddisk1\DR1 during a paging operation.
Log: 'System' Date/Time: 19/01/2011 10:20:37 PM
Type: Warning Category: 2
Event: 57 Source: Ntfs
The system failed to flush data to the transaction log. Corruption may occur.
Log: 'System' Date/Time: 19/01/2011 10:20:37 PM
Type: Warning Category: 0
Event: 51 Source: Disk
An error was detected on device \Device\Harddisk1\DR2 during a paging operation.
Log: 'System' Date/Time: 19/01/2011 10:20:37 PM
Type: Warning Category: 0
Event: 51 Source: Disk
An error was detected on device \Device\Harddisk1\DR2 during a paging operation.
Log: 'System' Date/Time: 19/01/2011 10:20:37 PM
Type: Warning Category: 0
Event: 51 Source: Disk
An error was detected on device \Device\Harddisk1\DR2 during a paging operation.
Log: 'System' Date/Time: 19/01/2011 10:20:37 PM
Type: Warning Category: 0
Event: 51 Source: Disk
An error was detected on device \Device\Harddisk1\DR2 during a paging operation.
Log: 'System' Date/Time: 19/01/2011 10:20:36 PM
Type: Warning Category: 0
Event: 51 Source: Disk
An error was detected on device \Device\Harddisk1\DR2 during a paging operation.
Log: 'System' Date/Time: 19/01/2011 10:20:32 PM
Type: Warning Category: 2
Event: 57 Source: Ntfs
The system failed to flush data to the transaction log. Corruption may occur.
Log: 'System' Date/Time: 19/01/2011 10:20:32 PM
Type: Warning Category: 0
Event: 51 Source: Disk
An error was detected on device \Device\Harddisk1\DR2 during a paging operation.
Log: 'System' Date/Time: 19/01/2011 10:20:32 PM
Type: Warning Category: 0
Event: 51 Source: Disk
An error was detected on device \Device\Harddisk1\DR2 during a paging operation.
Log: 'System' Date/Time: 19/01/2011 10:20:28 PM
Type: Warning Category: 0
Event: 51 Source: Disk
An error was detected on device \Device\Harddisk1\DR2 during a paging operation.
Log: 'System' Date/Time: 19/01/2011 10:20:27 PM
Type: Warning Category: 2
Event: 57 Source: Ntfs
The system failed to flush data to the transaction log. Corruption may occur.
Log: 'System' Date/Time: 19/01/2011 10:20:27 PM
Type: Warning Category: 0
Event: 51 Source: Disk
An error was detected on device \Device\Harddisk1\DR2 during a paging operation.