Vino's Event Viewer v01c run on Windows 2008 in English
Report run at 26/01/2010 7:05:09 PM

Note: All dates below are in the format dd/mm/yyyy

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 26/01/2010 5:06:20 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: OUTLOOK.EXE, version: 12.0.4518.1014, time stamp: 0x4542840f Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x0565c9f0 Faulting process id: 0xb1c Faulting application start time: 0x01ca9ea02c55254d Faulting application path: C:\Program Files\Office2007\Office12\OUTLOOK.EXE Faulting module path: unknown Report Id: 1f113296-0a9d-11df-85e0-c32c9e9c04d2

Log: 'Application' Date/Time: 20/01/2010 6:57:00 PM
Type: Error Category: 101
Event: 1002 Source: Application Hang
The program NLNOTES.EXE version 0.0.0.0 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: b4  Start Time: 01ca9a008ea53e0f  Termination Time: 16  Application Path: C:\Notes\NLNOTES.EXE  Report Id: 563b82d0-05f4-11df-850e-f23e49b81cd4 

Log: 'Application' Date/Time: 20/01/2010 6:37:49 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: OUTLOOK.EXE, version: 12.0.4518.1014, time stamp: 0x4542840f Faulting module name: olmapi32.dll, version: 12.0.4518.1014, time stamp: 0x45428191 Exception code: 0xc0000005 Fault offset: 0x0002f416 Faulting process id: 0x6bc Faulting application start time: 0x01ca99fe4edbae70 Faulting application path: C:\Program Files\Office2007\Office12\OUTLOOK.EXE Faulting module path: c:\progra~1\office~1\office12\olmapi32.dll Report Id: e8b6d7b9-05f2-11df-8ab6-f160f6567cd1

Log: 'Application' Date/Time: 19/01/2010 4:17:55 PM
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: {88dc9ac2-4d8b-4fb6-93e2-2445d6583eb5}

Log: 'Application' Date/Time: 19/01/2010 3:46:54 PM
Type: Error Category: 101
Event: 1002 Source: Application Hang
The program OUTLOOK.EXE version 12.0.4518.1014 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: af8  Start Time: 01ca991d2ac16dfc  Termination Time: 62  Application Path: C:\Program Files\Office2007\Office12\OUTLOOK.EXE  Report Id:  

Log: 'Application' Date/Time: 17/01/2010 3:05:03 AM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: Fallout3.exe, version: 1.7.0.3, time stamp: 0x4a40f18b Faulting module name: Fallout3.exe, version: 1.7.0.3, time stamp: 0x4a40f18b Exception code: 0xc0000005 Fault offset: 0x006ddf7b Faulting process id: 0x1c10 Faulting application start time: 0x01ca9721022a9aa5 Faulting application path: C:\Program Files\Bethesda Softworks\Fallout 3\Fallout3.exe Faulting module path: C:\Program Files\Bethesda Softworks\Fallout 3\Fallout3.exe Report Id: 1ac58803-0315-11df-8a38-aad64cd5ffd3

Log: 'Application' Date/Time: 17/01/2010 1:50:26 AM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: Fallout3.exe, version: 1.7.0.3, time stamp: 0x4a40f18b Faulting module name: Fallout3.exe, version: 1.7.0.3, time stamp: 0x4a40f18b Exception code: 0xc0000005 Fault offset: 0x006ddf7b Faulting process id: 0x1a44 Faulting application start time: 0x01ca9717517ac126 Faulting application path: C:\Program Files\Bethesda Softworks\Fallout 3\Fallout3.exe Faulting module path: C:\Program Files\Bethesda Softworks\Fallout 3\Fallout3.exe Report Id: ae61fe78-030a-11df-8a38-aad64cd5ffd3

Log: 'Application' Date/Time: 16/01/2010 9:31:13 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: Fallout3.exe, version: 1.7.0.3, time stamp: 0x4a40f18b Faulting module name: Fallout3.exe, version: 1.7.0.3, time stamp: 0x4a40f18b Exception code: 0xc0000005 Fault offset: 0x006ddf7b Faulting process id: 0x990 Faulting application start time: 0x01ca96f305d3ee1e Faulting application path: C:\Program Files\Bethesda Softworks\Fallout 3\Fallout3.exe Faulting module path: C:\Program Files\Bethesda Softworks\Fallout 3\Fallout3.exe Report Id: 78239c7c-02e6-11df-8a4f-bf9b29620dd2

Log: 'Application' Date/Time: 16/01/2010 8:00:13 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: Fallout3.exe, version: 1.7.0.3, time stamp: 0x4a40f18b Faulting module name: Fallout3.exe, version: 1.7.0.3, time stamp: 0x4a40f18b Exception code: 0xc0000005 Fault offset: 0x006ddf7b Faulting process id: 0x9d4 Faulting application start time: 0x01ca96e6358dca91 Faulting application path: C:\Program Files\Bethesda Softworks\Fallout 3\Fallout3.exe Faulting module path: C:\Program Files\Bethesda Softworks\Fallout 3\Fallout3.exe Report Id: c1b29c8f-02d9-11df-8a4f-bf9b29620dd2

Log: 'Application' Date/Time: 16/01/2010 5:24:57 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: Fallout3.exe, version: 1.7.0.3, time stamp: 0x4a40f18b Faulting module name: Fallout3.exe, version: 1.7.0.3, time stamp: 0x4a40f18b Exception code: 0xc0000005 Fault offset: 0x006ddf7b Faulting process id: 0x89c Faulting application start time: 0x01ca96d08664b69a Faulting application path: C:\Program Files\Bethesda Softworks\Fallout 3\Fallout3.exe Faulting module path: C:\Program Files\Bethesda Softworks\Fallout 3\Fallout3.exe Report Id: 10c76f00-02c4-11df-9077-fef53e5a31cc

Log: 'Application' Date/Time: 16/01/2010 5:18:05 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: Fallout3.exe, version: 1.7.0.3, time stamp: 0x4a40f18b Faulting module name: Fallout3.exe, version: 1.7.0.3, time stamp: 0x4a40f18b Exception code: 0xc0000005 Fault offset: 0x006ddf7b Faulting process id: 0xb44 Faulting application start time: 0x01ca96ceea9b277a Faulting application path: C:\Program Files\Bethesda Softworks\Fallout 3\Fallout3.exe Faulting module path: C:\Program Files\Bethesda Softworks\Fallout 3\Fallout3.exe Report Id: 1b360d50-02c3-11df-9077-fef53e5a31cc

Log: 'Application' Date/Time: 16/01/2010 5:03:43 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: Fallout3.exe, version: 1.7.0.3, time stamp: 0x4a40f18b Faulting module name: Fallout3.exe, version: 1.7.0.3, time stamp: 0x4a40f18b Exception code: 0xc0000005 Fault offset: 0x006ddf7b Faulting process id: 0xb40 Faulting application start time: 0x01ca96cd9e47cae6 Faulting application path: C:\Program Files\Bethesda Softworks\Fallout 3\Fallout3.exe Faulting module path: C:\Program Files\Bethesda Softworks\Fallout 3\Fallout3.exe Report Id: 198e7e68-02c1-11df-9077-fef53e5a31cc

Log: 'Application' Date/Time: 16/01/2010 4:42:39 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: Fallout3.exe, version: 1.7.0.3, time stamp: 0x4a40f18b Faulting module name: Fallout3.exe, version: 1.7.0.3, time stamp: 0x4a40f18b Exception code: 0xc0000005 Fault offset: 0x006ddf7b Faulting process id: 0x1e8 Faulting application start time: 0x01ca96cabd1209e5 Faulting application path: C:\Program Files\Bethesda Softworks\Fallout 3\Fallout3.exe Faulting module path: C:\Program Files\Bethesda Softworks\Fallout 3\Fallout3.exe Report Id: 282dfe96-02be-11df-9077-fef53e5a31cc

Log: 'Application' Date/Time: 16/01/2010 7:05:14 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: {0e65acba-5f6d-4836-950c-1b4fc70f9ab4}

Log: 'Application' Date/Time: 06/01/2010 5:47:18 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: WINWORD.EXE, version: 12.0.4518.1014, time stamp: 0x45428028 Faulting module name: KERNELBASE.dll, version: 6.1.7600.16385, time stamp: 0x4a5bdaae Exception code: 0xe0000001 Fault offset: 0x00009617 Faulting process id: 0x4e0 Faulting application start time: 0x01ca8ef83b5ab79a Faulting application path: C:\Program Files\Office2007\Office12\WINWORD.EXE Faulting module path: C:\Windows\system32\KERNELBASE.dll Report Id: 883e4fa8-faeb-11de-902e-a50648bab8ce

Log: 'Application' Date/Time: 05/01/2010 12:27:23 AM
Type: Error Category: 101
Event: 1002 Source: Application Hang
The program NLNOTES.EXE version 0.0.0.0 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: f0c  Start Time: 01ca8d96ced979fd  Termination Time: 46  Application Path: C:\Notes\NLNOTES.EXE  Report Id: 14f5fc93-f991-11de-8f3b-a1b8e91eb8d1 

Log: 'Application' Date/Time: 31/12/2009 4:58:28 PM
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: {e73e08bb-4cb2-459f-9e1f-0bbae5ef2266}

Log: 'Application' Date/Time: 28/12/2009 4:30:10 PM
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: {60912bc2-b580-48a2-bfde-6d8813094fc7}

Log: 'Application' Date/Time: 26/12/2009 5:09:22 AM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: Fallout3.exe, version: 1.0.0.12, time stamp: 0x48d194b3 Faulting module name: Fallout3.exe, version: 1.0.0.12, time stamp: 0x48d194b3 Exception code: 0xc0000005 Fault offset: 0x006d8cdb Faulting process id: 0x828 Faulting application start time: 0x01ca85e9797f412b Faulting application path: C:\Program Files\Bethesda Softworks\Fallout 3\Fallout3.exe Faulting module path: C:\Program Files\Bethesda Softworks\Fallout 3\Fallout3.exe Report Id: d3f83a6c-f1dc-11de-be33-b0b5f09981d2

Log: 'Application' Date/Time: 26/12/2009 5:07:57 AM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: Fallout3.exe, version: 1.0.0.12, time stamp: 0x48d194b3 Faulting module name: Fallout3.exe, version: 1.0.0.12, time stamp: 0x48d194b3 Exception code: 0xc0000005 Fault offset: 0x006d8cdb Faulting process id: 0xdc4 Faulting application start time: 0x01ca85e93b790f84 Faulting application path: C:\Program Files\Bethesda Softworks\Fallout 3\Fallout3.exe Faulting module path: C:\Program Files\Bethesda Softworks\Fallout 3\Fallout3.exe Report Id: a12d6743-f1dc-11de-be33-b0b5f09981d2

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 23/01/2010 5:26:38 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: 30/12/2009 7:08:40 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/12/2009 7:05:12 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/12/2009 7:52: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: 15/12/2009 3:31:23 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: 08/12/2009 4:19: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: 05/12/2009 7:55:56 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: 05/12/2009 3:08:12 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: 05/12/2009 3:04:24 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: 28/11/2009 6:08: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: 15/11/2009 5:53:33 AM
Type: Critical Category: 64
Event: 10111 Source: Microsoft-Windows-DriverFrameworks-UserMode
The device Samsung YP-K3 (location Port_#0004.Hub_#0003) is offline due to a user-mode driver crash.  Windows will attempt to restart the device 5 more times.  Please contact the device manufacturer for more information about this problem.

Log: 'System' Date/Time: 15/11/2009 5:53:33 AM
Type: Critical Category: 64
Event: 10110 Source: Microsoft-Windows-DriverFrameworks-UserMode
A problem has occurred with one or more user-mode drivers and the hosting process has been terminated.  This may temporarily interrupt your ability to access the devices.

Log: 'System' Date/Time: 10/11/2009 1:16:28 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: 07/11/2009 8:56: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: 02/11/2009 7:43:40 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.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 27/01/2010 1:56:22 AM
Type: Error Category: 0
Event: 8003 Source: bowser
The master browser has received a server announcement from the computer FAMILY-PC that believes that it is the master browser for the domain on transport NetBT_Tcpip_{2545609D-EF96-4752-8D91-F18D1EAD. The master browser is stopping or an election is being forced.

Log: 'System' Date/Time: 26/01/2010 5:16:20 PM
Type: Error Category: 0
Event: 4319 Source: NetBT
A duplicate name has been detected on the TCP network.  The IP address of the computer that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state.

Log: 'System' Date/Time: 26/01/2010 4:11:57 PM
Type: Error Category: 0
Event: 4319 Source: NetBT
A duplicate name has been detected on the TCP network.  The IP address of the computer that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state.

Log: 'System' Date/Time: 25/01/2010 11:04:08 PM
Type: Error Category: 0
Event: 4319 Source: NetBT
A duplicate name has been detected on the TCP network.  The IP address of the computer that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state.

Log: 'System' Date/Time: 25/01/2010 11:04:01 PM
Type: Error Category: 0
Event: 4319 Source: NetBT
A duplicate name has been detected on the TCP network.  The IP address of the computer that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state.

Log: 'System' Date/Time: 25/01/2010 8:20:11 PM
Type: Error Category: 0
Event: 4319 Source: NetBT
A duplicate name has been detected on the TCP network.  The IP address of the computer that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state.

Log: 'System' Date/Time: 25/01/2010 4:59:18 PM
Type: Error Category: 0
Event: 4319 Source: NetBT
A duplicate name has been detected on the TCP network.  The IP address of the computer that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state.

Log: 'System' Date/Time: 25/01/2010 4:59:13 PM
Type: Error Category: 0
Event: 4319 Source: NetBT
A duplicate name has been detected on the TCP network.  The IP address of the computer that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state.

Log: 'System' Date/Time: 25/01/2010 4:59:06 PM
Type: Error Category: 0
Event: 4319 Source: NetBT
A duplicate name has been detected on the TCP network.  The IP address of the computer that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state.

Log: 'System' Date/Time: 25/01/2010 3:35:14 PM
Type: Error Category: 0
Event: 4319 Source: NetBT
A duplicate name has been detected on the TCP network.  The IP address of the computer that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state.

Log: 'System' Date/Time: 25/01/2010 3:20:19 PM
Type: Error Category: 0
Event: 4319 Source: NetBT
A duplicate name has been detected on the TCP network.  The IP address of the computer that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state.

Log: 'System' Date/Time: 25/01/2010 3:17:30 PM
Type: Error Category: 0
Event: 7011 Source: Service Control Manager
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the avg8wd service.

Log: 'System' Date/Time: 25/01/2010 2:42:14 AM
Type: Error Category: 0
Event: 8003 Source: bowser
The master browser has received a server announcement from the computer FAMILY-PC that believes that it is the master browser for the domain on transport NetBT_Tcpip_{2545609D-EF96-4752-8D91-F18D1EAD. The master browser is stopping or an election is being forced.

Log: 'System' Date/Time: 24/01/2010 9:25:26 PM
Type: Error Category: 0
Event: 8003 Source: bowser
The master browser has received a server announcement from the computer FAMILY-PC that believes that it is the master browser for the domain on transport NetBT_Tcpip_{2545609D-EF96-4752-8D91-F18D1EAD. The master browser is stopping or an election is being forced.

Log: 'System' Date/Time: 24/01/2010 4:23:17 AM
Type: Error Category: 0
Event: 8003 Source: bowser
The master browser has received a server announcement from the computer FAMILY-PC that believes that it is the master browser for the domain on transport NetBT_Tcpip_{2545609D-EF96-4752-8D91-F18D1EAD. The master browser is stopping or an election is being forced.

Log: 'System' Date/Time: 24/01/2010 3:32:38 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 avg8wd service.

Log: 'System' Date/Time: 23/01/2010 5:26:52 PM
Type: Error Category: 0
Event: 6008 Source: EventLog
The previous system shutdown at 10:23:17 AM on ?1/?23/?2010 was unexpected.

Log: 'System' Date/Time: 23/01/2010 6:21:29 AM
Type: Error Category: 0
Event: 8003 Source: bowser
The master browser has received a server announcement from the computer FAMILY-PC that believes that it is the master browser for the domain on transport NetBT_Tcpip_{2545609D-EF96-4752-8D91-F18D1EAD. The master browser is stopping or an election is being forced.

Log: 'System' Date/Time: 22/01/2010 7:02:51 PM
Type: Error Category: 0
Event: 36887 Source: Schannel
The following fatal alert was received: 40.

Log: 'System' Date/Time: 22/01/2010 7:02:51 PM
Type: Error Category: 0
Event: 36887 Source: Schannel
The following fatal alert was received: 40.