Vino's Event Viewer v01c run on Windows 7 in English
Report run at 19/09/2014 19:59:52
Note: All dates below are in the format dd/mm/yyyy
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 19/09/2014 09:56:53
Type: Error Category: 101
Event: 1002 Source: Application Hang
The program wwahost.exe version 6.3.9600.17031 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: 11c4 Start Time: 01cfd2bc22eb5a3e Termination Time: 46 Application Path: C:\Windows\system32\wwahost.exe Report Id: 451d316b-3fe3-11e4-974e-88124e8553f4 Faulting package full name: B-sideSoftware.Tweetium_2.9.2.263_x86__eq7kkbyjh4j3c Faulting package-relative application ID: App
Log: 'Application' Date/Time: 19/09/2014 09:56:51
Type: Error Category: 101
Event: 1002 Source: Application Hang
The program iexplore.exe version 11.0.9600.17278 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: 8f4 Start Time: 01cfd0d77b85924e Termination Time: 78 Application Path: C:\Program Files\Internet Explorer\iexplore.exe Report Id: 4513a7f5-3fe3-11e4-974e-88124e8553f4 Faulting package full name: Faulting package-relative application ID:
Log: 'Application' Date/Time: 19/09/2014 08:33:14
Type: Error Category: 101
Event: 1002 Source: Application Hang
The program backgroundTaskHost.exe version 6.3.9600.16384 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: 1cac Start Time: 01cfd3e3484dcb93 Termination Time: 4294967295 Application Path: C:\Windows\system32\backgroundTaskHost.exe Report Id: 95574d7e-3fd7-11e4-974e-88124e8553f4 Faulting package full name: Facebook.Facebook_1.4.0.9_x86__8xx8rvfyw5nnt Faulting package-relative application ID: App
Log: 'Application' Date/Time: 19/09/2014 08:03:29
Type: Error Category: 101
Event: 1002 Source: Application Hang
The program backgroundTaskHost.exe version 6.3.9600.16384 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: 1f74 Start Time: 01cfd3df17634853 Termination Time: 4294967295 Application Path: C:\Windows\system32\backgroundTaskHost.exe Report Id: 6463418f-3fd3-11e4-974e-88124e8553f4 Faulting package full name: Facebook.Facebook_1.4.0.9_x86__8xx8rvfyw5nnt Faulting package-relative application ID: App
Log: 'Application' Date/Time: 19/09/2014 05:03:33
Type: Error Category: 101
Event: 1002 Source: Application Hang
The program backgroundTaskHost.exe version 6.3.9600.16384 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: 25f4 Start Time: 01cfd3c5f20c762a Termination Time: 4294967295 Application Path: C:\Windows\system32\backgroundTaskHost.exe Report Id: 3f0c6f5e-3fba-11e4-974e-88124e8553f4 Faulting package full name: Facebook.Facebook_1.4.0.9_x86__8xx8rvfyw5nnt Faulting package-relative application ID: App
Log: 'Application' Date/Time: 19/09/2014 02:03:10
Type: Error Category: 101
Event: 1002 Source: Application Hang
The program backgroundTaskHost.exe version 6.3.9600.16384 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: 250c Start Time: 01cfd3accca5ae6b Termination Time: 4294967295 Application Path: C:\Windows\system32\backgroundTaskHost.exe Report Id: 19b35707-3fa1-11e4-974e-88124e8553f4 Faulting package full name: Facebook.Facebook_1.4.0.9_x86__8xx8rvfyw5nnt Faulting package-relative application ID: App
Log: 'Application' Date/Time: 19/09/2014 01:22:21
Type: Error Category: 101
Event: 1002 Source: Application Hang
The program LiveComm.exe version 17.5.9600.20605 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: 1590 Start Time: 01cfd33eb83fecf6 Termination Time: 4294967295 Application Path: C:\Program Files\WindowsApps\microsoft.windowscommunicationsapps_17.5.9600.20605_x86__8wekyb3d8bbwe\LiveComm.exe Report Id: 5364082e-3f9b-11e4-974e-88124e8553f4 Faulting package full name: microsoft.windowscommunicationsapps_17.5.9600.20605_x86__8wekyb3d8bbwe Faulting package-relative application ID: ppleae38af2e007f4358a809ac99a64a67c1
Log: 'Application' Date/Time: 19/09/2014 01:18:17
Type: Error Category: 101
Event: 1002 Source: Application Hang
The program backgroundTaskHost.exe version 6.3.9600.16384 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: 240c Start Time: 01cfd3a68339fd8d Termination Time: 4294967295 Application Path: C:\Windows\system32\backgroundTaskHost.exe Report Id: d03c5456-3f9a-11e4-974e-88124e8553f4 Faulting package full name: Facebook.Facebook_1.4.0.9_x86__8xx8rvfyw5nnt Faulting package-relative application ID: App
Log: 'Application' Date/Time: 19/09/2014 01:03:14
Type: Error Category: 101
Event: 1002 Source: Application Hang
The program backgroundTaskHost.exe version 6.3.9600.16384 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: 2390 Start Time: 01cfd3a46ad7ba0f Termination Time: 4294967295 Application Path: C:\Windows\system32\backgroundTaskHost.exe Report Id: b93d684a-3f98-11e4-974e-88124e8553f4 Faulting package full name: Facebook.Facebook_1.4.0.9_x86__8xx8rvfyw5nnt Faulting package-relative application ID: App
Log: 'Application' Date/Time: 19/09/2014 00:33:17
Type: Error Category: 101
Event: 1002 Source: Application Hang
The program backgroundTaskHost.exe version 6.3.9600.16384 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: 218c Start Time: 01cfd3a039f1fb7b Termination Time: 4294967295 Application Path: C:\Windows\system32\backgroundTaskHost.exe Report Id: 88d85562-3f94-11e4-974e-88124e8553f4 Faulting package full name: Facebook.Facebook_1.4.0.9_x86__8xx8rvfyw5nnt Faulting package-relative application ID: App
Log: 'Application' Date/Time: 18/09/2014 23:28:31
Type: Error Category: 0
Event: 33 Source: SideBySide
Activation context generation failed for "C:\Program Files\EPSON Software\Download Navigator\EPSDNLMW64.EXE". Dependent Assembly Microsoft.Windows.Common-Controls,language="*",processorArchitecture="amd64",publicKeyToken="6595b64144ccf1df",type="win32",version="6.0.0.0" could not be found. Please use sxstrace.exe for detailed diagnosis.
Log: 'Application' Date/Time: 18/09/2014 23:27:26
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: skydrive.exe, version: 6.3.9600.17278, time stamp: 0x53eea066 Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0x00000000 Fault offset: 0x00000000 Faulting process id: 0xa34 Faulting application start time: 0x01cfd398109aa7ef Faulting application path: C:\Windows\System32\skydrive.exe Faulting module path: unknown Report Id: 5944ad03-3f8b-11e4-974e-88124e8553f4 Faulting package full name: Faulting package-relative application ID:
Log: 'Application' Date/Time: 18/09/2014 23:27:07
Type: Error Category: 0
Event: 8211 Source: System Restore
The scheduled restore point could not be created. Additional information: (0x80042308).
Log: 'Application' Date/Time: 18/09/2014 23:27:07
Type: Error Category: 0
Event: 8193 Source: System Restore
Failed to create restore point (Process = C:\Windows\system32\srtasks.exe ExecuteScheduledSPPCreation; Description = Scheduled Checkpoint; Error = 0x80042308).
Log: 'Application' Date/Time: 18/09/2014 23:27:07
Type: Error Category: 0
Event: 12305 Source: VSS
Volume Shadow Copy Service error: Volume/disk not connected or not found. Error context: DeviceIoControl([URL="file://\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1"]\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1[/URL] - 000001E4,0x00560034,009299B8,0,00926560,4096,[0]).
Operation:
Processing PostFinalCommitSnapshots
Context:
Execution Context: System Provider
Log: 'Application' Date/Time: 18/09/2014 05:58:48
Type: Error Category: 101
Event: 1002 Source: Application Hang
The program backgroundTaskHost.exe version 6.3.9600.16384 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: c10 Start Time: 01cfd30344d5f459 Termination Time: 4294967295 Application Path: C:\Windows\system32\backgroundTaskHost.exe Report Id: da35ce9a-3ef8-11e4-974e-88124e8553f4 Faulting package full name: Facebook.Facebook_1.4.0.9_x86__8xx8rvfyw5nnt Faulting package-relative application ID: App
Log: 'Application' Date/Time: 17/09/2014 11:33:43
Type: Error Category: 101
Event: 1002 Source: Application Hang
The program backgroundTaskHost.exe version 6.3.9600.16384 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: 60c Start Time: 01cfd26a27e82808 Termination Time: 4294967295 Application Path: C:\Windows\system32\backgroundTaskHost.exe Report Id: 78fa3923-3e5e-11e4-974e-88124e8553f4 Faulting package full name: Facebook.Facebook_1.4.0.9_x86__8xx8rvfyw5nnt Faulting package-relative application ID: App
Log: 'Application' Date/Time: 17/09/2014 11:25:58
Type: Error Category: 0
Event: 1008 Source: Microsoft-Windows-CEIP
A problem prevented Customer Experience Improvement Program data from being sent to Microsoft, (Error 80070005).
Log: 'Application' Date/Time: 17/09/2014 11:22:45
Type: Error Category: 101
Event: 1002 Source: Application Hang
The program LiveComm.exe version 17.5.9600.20605 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: 27e8 Start Time: 01cfd2629be5bcbb Termination Time: 4294967295 Application Path: C:\Program Files\WindowsApps\microsoft.windowscommunicationsapps_17.5.9600.20605_x86__8wekyb3d8bbwe\LiveComm.exe Report Id: f1bdf21a-3e5c-11e4-974e-88124e8553f4 Faulting package full name: microsoft.windowscommunicationsapps_17.5.9600.20605_x86__8wekyb3d8bbwe Faulting package-relative application ID: ppleae38af2e007f4358a809ac99a64a67c1
Log: 'Application' Date/Time: 17/09/2014 10:25:09
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: skydrive.exe, version: 6.3.9600.17278, time stamp: 0x53eea066 Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0x00000000 Fault offset: 0x00000000 Faulting process id: 0xedc Faulting application start time: 0x01cfd261a2c8ae57 Faulting application path: C:\Windows\System32\skydrive.exe Faulting module path: unknown Report Id: e60e3102-3e54-11e4-974e-88124e8553f4 Faulting package full name: Faulting package-relative application ID:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Information Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 19/09/2014 09:56:59
Type: Information Category: 0
Event: 1001 Source: Windows Error Reporting
Fault bucket 98866580737, type 5 Event Name: MoAppHang Response: Not available Cab Id: 98864935617 Problem signature: P1: B-sideSoftware.Tweetium_2.9.2.263_x86__eq7kkbyjh4j3c P2: praid:App P3: 6.3.9600.17031 P4: 53085904 P5: 4669 P6: 16912384 P7: P8: P9: P10: Attached files: C:\Users\Mark\AppData\Local\Temp\WER72E4.tmp.appcompat.txt C:\Users\Mark\AppData\Local\Temp\WER7314.tmp.version.xml C:\Users\Mark\AppData\Local\Temp\WER7344.tmp.WERInternalMetadata.xml triagedump.dmp C:\Users\Mark\AppData\Local\Temp\WER85C4.tmp.xml C:\Users\Mark\AppData\Local\Temp\WER85D5.tmp.WERDataCollectionFailure.txt These files may be available here: C:\Users\Mark\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppHang_B-sideSoftware.T_187460f1fa696cbbc6e2e28892211f63aba6f826_846337bc_cab_0f989c94 Analysis symbol: Rechecking for solution: 0 Report Id: 451d316b-3fe3-11e4-974e-88124e8553f4 Report Status: 8 Hashed bucket: 37d462a9df57fda52faf25a71dcf6b19
Log: 'Application' Date/Time: 19/09/2014 09:56:51
Type: Information Category: 0
Event: 1001 Source: Windows Error Reporting
Fault bucket 94592662808, type 5 Event Name: AppHangB1 Response: Not available Cab Id: 0 Problem signature: P1: iexplore.exe P2: 11.0.9600.17278 P3: 53eea0c3 P4: 7886 P5: 16912384 P6: P7: P8: P9: P10: Attached files: C:\Users\Mark\AppData\Local\Temp\WER72C5.tmp.appcompat.txt C:\Users\Mark\AppData\Local\Temp\WER743D.tmp.version.xml C:\Users\Mark\AppData\Local\Temp\WER746D.tmp.WERInternalMetadata.xml These files may be available here: C:\Users\Mark\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppHang_iexplore.exe_63d6f1b79d734d4c835499b33640ec6a67aedb0_82a313f7_039c7b02 Analysis symbol: Rechecking for solution: 0 Report Id: 4513a7f5-3fe3-11e4-974e-88124e8553f4 Report Status: 0 Hashed bucket: ddb8b5189f3a960e843be6d79359f1c0
Log: 'Application' Date/Time: 19/09/2014 09:56:34
Type: Information Category: 1
Event: 326 Source: ESENT
svchost (9244) Instance: The database engine attached a database (1, C:\ProgramData\Microsoft\Windows\AppRepository\PackageRepository.edb). (Time=0 seconds) Internal Timing Sequence: [1] 0.000, [2] 0.000, [3] 0.016, [4] 0.000, [5] 0.000, [6] 0.000, [7] 0.015, [8] 0.000, [9] 0.000, [10] 0.000, [11] 0.000, [12] 0.000. Saved Cache: 1 0
Log: 'Application' Date/Time: 19/09/2014 09:56:34
Type: Information Category: 1
Event: 105 Source: ESENT
svchost (9244) Instance: The database engine started a new instance (0). (Time=0 seconds) Internal Timing Sequence: [1] 0.000, [2] 0.000, [3] 0.000, [4] 0.016, [5] 0.000, [6] 0.000, [7] 0.000, [8] 0.000, [9] 0.000, [10] 0.000.
Log: 'Application' Date/Time: 19/09/2014 09:56:34
Type: Information Category: 1
Event: 102 Source: ESENT
svchost (9244) Instance: The database engine (6.03.9600.0000) is starting a new instance (0).
Log: 'Application' Date/Time: 19/09/2014 09:41:37
Type: Information Category: 0
Event: 0 Source: DellDigitalDelivery
PowerEvent handled successfully by the service.
Log: 'Application' Date/Time: 19/09/2014 09:34:03
Type: Information Category: 0
Event: 903 Source: Microsoft-Windows-Security-SPP
The Software Protection service has stopped.
Log: 'Application' Date/Time: 19/09/2014 09:34:03
Type: Information Category: 0
Event: 16384 Source: Microsoft-Windows-Security-SPP
Successfully scheduled Software Protection service for re-start at 2114-08-26T09:34:03Z. Reason: RulesEngine.
Log: 'Application' Date/Time: 19/09/2014 09:33:33
Type: Information Category: 0
Event: 902 Source: Microsoft-Windows-Security-SPP
The Software Protection service has started. 6.3.9600.16497
Log: 'Application' Date/Time: 19/09/2014 09:33:33
Type: Information Category: 0
Event: 1003 Source: Microsoft-Windows-Security-SPP
The Software Protection service has completed licensing status check. Application Id=55c92734-d682-4d71-983e-d6ec3f16059f Licensing Status=
1: 0cdc4d08-6df6-4eb4-b5b4-a373c3e351e7, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)(?)(?)])(1 )(2 )]
2: 625cc89b-693d-45c4-9967-123877fc41e4, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)(?)(?)])(1 )(2 )]
3: 9a8645c4-8908-49bb-8eec-6671a533b17a, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)(?)(?)])(1 )(2 )]
4: 9e263fcf-ef40-428c-8aa1-40e09e2994db, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)(?)(?)])(1 )(2 )]
5: 9e4b231b-3e45-41f4-967f-c914f178b6ac, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)(?)(?)])(1 )(2 )]
6: b080aea2-e6c5-4b22-838e-fa4a21c931e3, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)(?)(?)])(1 )(2 )]
7: bbc56067-37f8-49dd-87b2-a418a9ba130a, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)(?)(?)])(1 )(2 )]
8: bf4b3af6-c071-496d-bfcc-5f0dc12c7798, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)(?)(?)])(1 )(2 )]
9: c752c2e0-7c17-4af4-bba6-6f8aa1e698bc, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)(?)(?)])(1 )(2 )]
10: c7c00280-b24d-4e82-89ca-4f1288eb1d9e, 1, 1 [(0 [0x00000000, 1, 0], [(?)( 1 0x00000000)(?)( 2 0x00000000 0 0 msft:rm/algorithm/hwid/4.0 0x00000000 0)(?)(?)( 10 0x00000000 msft:rm/algorithm/flags/1.0)(?)])(1 )(2 )]
11: fe1c3238-432a-43a1-8e25-97e7d1ef10f3, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)(?)(?)])(1 )(2 )]
12: 4a8149bb-7d61-49f4-8822-82c7bf88d64b, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)(?)(?)])(1 )(2 )]
Log: 'Application' Date/Time: 19/09/2014 09:33:32
Type: Information Category: 0
Event: 1066 Source: Microsoft-Windows-Security-SPP
Initialization status for service objects. C:\Windows\system32\sppwinob.dll, msft:spp/windowsfunctionality/agent/7.0, 0x00000000, 0x00000000
C:\Windows\system32\sppobjs.dll, msft:rm/algorithm/inherited/1.0, 0x00000000, 0x00000000
C:\Windows\system32\sppobjs.dll, msft:rm/algorithm/phone/1.0, 0x00000000, 0x00000000
C:\Windows\system32\sppobjs.dll, msft:rm/algorithm/pkey/detect, 0x00000000, 0x00000000
C:\Windows\system32\sppobjs.dll, msft:spp/ActionScheduler/1.0, 0x00000000, 0x00000000
C:\Windows\system32\sppobjs.dll, msft:spp/TaskScheduler/1.0, 0x00000000, 0x00000000
C:\Windows\system32\sppobjs.dll, msft:spp/statecollector/pkey, 0x00000000, 0x00000000
C:\Windows\system32\sppobjs.dll, msft:spp/volume/services/kms/1.0, 0x00000000, 0x00000000
C:\Windows\system32\sppobjs.dll, msft:spp/volume/services/kms/activationinfo/1.0, 0x00000000, 0x00000000
Log: 'Application' Date/Time: 19/09/2014 09:33:32
Type: Information Category: 0
Event: 900 Source: Microsoft-Windows-Security-SPP
The Software Protection service is starting. Parameters:caller=svchost.exe
Log: 'Application' Date/Time: 19/09/2014 09:23:54
Type: Information Category: 0
Event: 903 Source: Microsoft-Windows-Security-SPP
The Software Protection service has stopped.
Log: 'Application' Date/Time: 19/09/2014 09:23:54
Type: Information Category: 0
Event: 16384 Source: Microsoft-Windows-Security-SPP
Successfully scheduled Software Protection service for re-start at 2114-08-26T09:23:54Z. Reason: RulesEngine.
Log: 'Application' Date/Time: 19/09/2014 09:23:24
Type: Information Category: 0
Event: 902 Source: Microsoft-Windows-Security-SPP
The Software Protection service has started. 6.3.9600.16497
Log: 'Application' Date/Time: 19/09/2014 09:23:24
Type: Information Category: 0
Event: 1003 Source: Microsoft-Windows-Security-SPP
The Software Protection service has completed licensing status check. Application Id=55c92734-d682-4d71-983e-d6ec3f16059f Licensing Status=
1: 0cdc4d08-6df6-4eb4-b5b4-a373c3e351e7, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)(?)(?)])(1 )(2 )]
2: 625cc89b-693d-45c4-9967-123877fc41e4, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)(?)(?)])(1 )(2 )]
3: 9a8645c4-8908-49bb-8eec-6671a533b17a, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)(?)(?)])(1 )(2 )]
4: 9e263fcf-ef40-428c-8aa1-40e09e2994db, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)(?)(?)])(1 )(2 )]
5: 9e4b231b-3e45-41f4-967f-c914f178b6ac, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)(?)(?)])(1 )(2 )]
6: b080aea2-e6c5-4b22-838e-fa4a21c931e3, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)(?)(?)])(1 )(2 )]
7: bbc56067-37f8-49dd-87b2-a418a9ba130a, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)(?)(?)])(1 )(2 )]
8: bf4b3af6-c071-496d-bfcc-5f0dc12c7798, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)(?)(?)])(1 )(2 )]
9: c752c2e0-7c17-4af4-bba6-6f8aa1e698bc, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)(?)(?)])(1 )(2 )]
10: c7c00280-b24d-4e82-89ca-4f1288eb1d9e, 1, 1 [(0 [0x00000000, 1, 0], [(?)( 1 0x00000000)(?)( 2 0x00000000 0 0 msft:rm/algorithm/hwid/4.0 0x00000000 0)(?)(?)( 10 0x00000000 msft:rm/algorithm/flags/1.0)(?)])(1 )(2 )]
11: fe1c3238-432a-43a1-8e25-97e7d1ef10f3, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)(?)(?)])(1 )(2 )]
12: 4a8149bb-7d61-49f4-8822-82c7bf88d64b, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)(?)(?)])(1 )(2 )]
Log: 'Application' Date/Time: 19/09/2014 09:23:24
Type: Information Category: 0
Event: 1066 Source: Microsoft-Windows-Security-SPP
Initialization status for service objects. C:\Windows\system32\sppwinob.dll, msft:spp/windowsfunctionality/agent/7.0, 0x00000000, 0x00000000
C:\Windows\system32\sppobjs.dll, msft:rm/algorithm/inherited/1.0, 0x00000000, 0x00000000
C:\Windows\system32\sppobjs.dll, msft:rm/algorithm/phone/1.0, 0x00000000, 0x00000000
C:\Windows\system32\sppobjs.dll, msft:rm/algorithm/pkey/detect, 0x00000000, 0x00000000
C:\Windows\system32\sppobjs.dll, msft:spp/ActionScheduler/1.0, 0x00000000, 0x00000000
C:\Windows\system32\sppobjs.dll, msft:spp/TaskScheduler/1.0, 0x00000000, 0x00000000
C:\Windows\system32\sppobjs.dll, msft:spp/statecollector/pkey, 0x00000000, 0x00000000
C:\Windows\system32\sppobjs.dll, msft:spp/volume/services/kms/1.0, 0x00000000, 0x00000000
C:\Windows\system32\sppobjs.dll, msft:spp/volume/services/kms/activationinfo/1.0, 0x00000000, 0x00000000
Log: 'Application' Date/Time: 19/09/2014 09:23:23
Type: Information Category: 0
Event: 900 Source: Microsoft-Windows-Security-SPP
The Software Protection service is starting. Parameters:caller=svchost.exe
Log: 'Application' Date/Time: 19/09/2014 09:13:46
Type: Information Category: 0
Event: 903 Source: Microsoft-Windows-Security-SPP
The Software Protection service has stopped.
Log: 'Application' Date/Time: 19/09/2014 09:13:46
Type: Information Category: 0
Event: 16384 Source: Microsoft-Windows-Security-SPP
Successfully scheduled Software Protection service for re-start at 2114-08-26T09:13:46Z. Reason: RulesEngine.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 18/09/2014 23:15:04
Type: Warning Category: 3
Event: 10023 Source: Microsoft-Windows-Search
The protocol host process 8712 did not respond and is being forcibly terminated {filter host process 9768}.
Log: 'Application' Date/Time: 15/09/2014 12:47:00
Type: Warning Category: 3
Event: 10023 Source: Microsoft-Windows-Search
The protocol host process 704 did not respond and is being forcibly terminated {filter host process 6108}.
Log: 'Application' Date/Time: 15/09/2014 11:23:43
Type: Warning Category: 0
Event: 10010 Source: Microsoft-Windows-RestartManager
Application 'C:\Program Files\Dell Update\DellUpTray.exe' (pid 3792) cannot be restarted - Application SID does not match Conductor SID..
Log: 'Application' Date/Time: 15/09/2014 11:23:43
Type: Warning Category: 0
Event: 10010 Source: Microsoft-Windows-RestartManager
Application 'C:\Program Files\Dell Update\DellUpTray.exe' (pid 3792) cannot be restarted - Application SID does not match Conductor SID..
Log: 'Application' Date/Time: 15/09/2014 11:23:42
Type: Warning Category: 0
Event: 10010 Source: Microsoft-Windows-RestartManager
Application 'C:\Program Files\Dell Update\DellUpTray.exe' (pid 3792) cannot be restarted - Application SID does not match Conductor SID..
Log: 'Application' Date/Time: 15/09/2014 11:23:42
Type: Warning Category: 0
Event: 10010 Source: Microsoft-Windows-RestartManager
Application 'C:\Program Files\Dell Update\DellUpTray.exe' (pid 3792) cannot be restarted - Application SID does not match Conductor SID..
Log: 'Application' Date/Time: 15/09/2014 02:15:34
Type: Warning Category: 3
Event: 10023 Source: Microsoft-Windows-Search
The protocol host process 6248 did not respond and is being forcibly terminated {filter host process 9096}.
Log: 'Application' Date/Time: 14/09/2014 01:37:05
Type: Warning Category: 0
Event: 10010 Source: Microsoft-Windows-RestartManager
Application 'C:\Windows\ImmersiveControlPanel\SystemSettings.exe' (pid 5736) cannot be restarted - Application SID does not match Conductor SID..
Log: 'Application' Date/Time: 14/09/2014 01:37:05
Type: Warning Category: 0
Event: 10010 Source: Microsoft-Windows-RestartManager
Application 'C:\Windows\explorer.exe' (pid 1512) cannot be restarted - Application SID does not match Conductor SID..
Log: 'Application' Date/Time: 14/09/2014 00:08:26
Type: Warning Category: 0
Event: 10010 Source: Microsoft-Windows-RestartManager
Application 'C:\Windows\explorer.exe' (pid 1512) cannot be restarted - Application SID does not match Conductor SID..
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 10/09/2014 15:46:26
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/09/2014 20:50:43
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/09/2014 18:13:56
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/09/2014 14:01:12
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: 27/08/2014 09:50:14
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: 25/08/2014 23:34:38
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/08/2014 07:52:15
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: 11/08/2014 07:38:01
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/07/2014 11:43:37
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/07/2014 12:47:24
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: 01/07/2014 10:38:28
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: 26/06/2014 11:57:25
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/06/2014 02:03:48
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/06/2014 10:11:37
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: 01/06/2014 11:28:02
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: 18/09/2014 23:27:07
Type: Error Category: 0
Event: 36 Source: volsnap
The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit.
Log: 'System' Date/Time: 18/09/2014 17:06:10
Type: Error Category: 0
Event: 10005 Source: Microsoft-Windows-DistributedCOM
DCOM got error "1053" attempting to start the service gupdate with arguments "/comsvc" in order to run the server: {4EB61BAC-A3B6-4760-9581-655041EF4D69}
Log: 'System' Date/Time: 18/09/2014 17:06:10
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The Google Update Service (gupdate) 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: 18/09/2014 17:06:10
Type: Error Category: 0
Event: 7009 Source: Service Control Manager
A timeout was reached (30000 milliseconds) while waiting for the Google Update Service (gupdate) service to connect.
Log: 'System' Date/Time: 18/09/2014 16:06:31
Type: Error Category: 0
Event: 10005 Source: Microsoft-Windows-DistributedCOM
DCOM got error "1053" attempting to start the service gupdate with arguments "/comsvc" in order to run the server: {4EB61BAC-A3B6-4760-9581-655041EF4D69}
Log: 'System' Date/Time: 18/09/2014 16:06:31
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The Google Update Service (gupdate) 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: 18/09/2014 16:06:31
Type: Error Category: 0
Event: 7009 Source: Service Control Manager
A timeout was reached (30000 milliseconds) while waiting for the Google Update Service (gupdate) service to connect.
Log: 'System' Date/Time: 18/09/2014 15:06:52
Type: Error Category: 0
Event: 10005 Source: Microsoft-Windows-DistributedCOM
DCOM got error "1053" attempting to start the service gupdate with arguments "/comsvc" in order to run the server: {4EB61BAC-A3B6-4760-9581-655041EF4D69}
Log: 'System' Date/Time: 18/09/2014 15:06:52
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The Google Update Service (gupdate) 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: 18/09/2014 15:06:52
Type: Error Category: 0
Event: 7009 Source: Service Control Manager
A timeout was reached (30000 milliseconds) while waiting for the Google Update Service (gupdate) service to connect.
Log: 'System' Date/Time: 18/09/2014 13:06:43
Type: Error Category: 0
Event: 10005 Source: Microsoft-Windows-DistributedCOM
DCOM got error "1053" attempting to start the service gupdate with arguments "/comsvc" in order to run the server: {4EB61BAC-A3B6-4760-9581-655041EF4D69}
Log: 'System' Date/Time: 18/09/2014 13:06:43
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The Google Update Service (gupdate) 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: 18/09/2014 13:06:43
Type: Error Category: 0
Event: 7009 Source: Service Control Manager
A timeout was reached (30000 milliseconds) while waiting for the Google Update Service (gupdate) service to connect.
Log: 'System' Date/Time: 18/09/2014 12:06:44
Type: Error Category: 0
Event: 10005 Source: Microsoft-Windows-DistributedCOM
DCOM got error "1053" attempting to start the service gupdate with arguments "/comsvc" in order to run the server: {4EB61BAC-A3B6-4760-9581-655041EF4D69}
Log: 'System' Date/Time: 18/09/2014 12:06:44
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The Google Update Service (gupdate) 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: 18/09/2014 12:06:44
Type: Error Category: 0
Event: 7009 Source: Service Control Manager
A timeout was reached (30000 milliseconds) while waiting for the Google Update Service (gupdate) service to connect.
Log: 'System' Date/Time: 18/09/2014 02:05:38
Type: Error Category: 0
Event: 10005 Source: Microsoft-Windows-DistributedCOM
DCOM got error "1053" attempting to start the service gupdate with arguments "/comsvc" in order to run the server: {4EB61BAC-A3B6-4760-9581-655041EF4D69}
Log: 'System' Date/Time: 18/09/2014 02:05:38
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The Google Update Service (gupdate) 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: 18/09/2014 02:05:38
Type: Error Category: 0
Event: 7009 Source: Service Control Manager
A timeout was reached (30000 milliseconds) while waiting for the Google Update Service (gupdate) service to connect.
Log: 'System' Date/Time: 17/09/2014 21:03:34
Type: Error Category: 0
Event: 8003 Source: bowser
The master browser has received a server announcement from the computer HPSERVER8 that believes that it is the master browser for the domain on transport NetBT_Tcpip_{6291DF19-B966-4754-AE45-032F97E4. The master browser is stopping or an election is being forced.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Information Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 19/09/2014 10:46:28
Type: Information Category: 157
Event: 506 Source: Microsoft-Windows-Kernel-Power
The system is entering connected standby Reason: Idle Timeout.
Log: 'System' Date/Time: 19/09/2014 10:40:49
Type: Information Category: 158
Event: 507 Source: Microsoft-Windows-Kernel-Power
The system is exiting connected standby Reason: Power Button.
Log: 'System' Date/Time: 19/09/2014 10:26:42
Type: Information Category: 157
Event: 506 Source: Microsoft-Windows-Kernel-Power
The system is entering connected standby Reason: Idle Timeout.
Log: 'System' Date/Time: 19/09/2014 10:18:57
Type: Information Category: 158
Event: 507 Source: Microsoft-Windows-Kernel-Power
The system is exiting connected standby Reason: Power Button.
Log: 'System' Date/Time: 19/09/2014 10:03:53
Type: Information Category: 157
Event: 506 Source: Microsoft-Windows-Kernel-Power
The system is entering connected standby Reason: Power Button.
Log: 'System' Date/Time: 19/09/2014 09:56:34
Type: Information Category: 158
Event: 507 Source: Microsoft-Windows-Kernel-Power
The system is exiting connected standby Reason: Power Button.
Log: 'System' Date/Time: 19/09/2014 09:42:15
Type: Information Category: 157
Event: 506 Source: Microsoft-Windows-Kernel-Power
The system is entering connected standby Reason: Idle Timeout.
Log: 'System' Date/Time: 19/09/2014 09:41:38
Type: Information Category: 158
Event: 507 Source: Microsoft-Windows-Kernel-Power
The system is exiting connected standby Reason: AC/DC Display Burst.
Log: 'System' Date/Time: 19/09/2014 02:00:00
Type: Information Category: 0
Event: 6013 Source: EventLog
The system uptime is 311944 seconds.
Log: 'System' Date/Time: 18/09/2014 23:34:53
Type: Information Category: 0
Event: 7045 Source: Service Control Manager
A service was installed in the system. Service Name: MpKsl787f047e Service File Name: C:\ProgramData\Microsoft\Windows Defender\Definition Updates\{3045EB67-77A5-4D50-84FA-96A826E74041}\MpKsl787f047e.sys Service Type: kernel mode driver Service Start Type: system start Service Account:
Log: 'System' Date/Time: 18/09/2014 23:34:39
Type: Information Category: 0
Event: 7045 Source: Service Control Manager
A service was installed in the system. Service Name: Nal Service Service File Name: C:\Windows\system32\Drivers\iqvw32.sys Service Type: kernel mode driver Service Start Type: demand start Service Account:
Log: 'System' Date/Time: 18/09/2014 23:32:43
Type: Information Category: 2
Event: 17 Source: Microsoft-Windows-WindowsUpdateClient
Installation Ready: The following updates are downloaded and ready for installation. To install the updates, an administrator should log on to this computer and Windows will prompt with further instructions:
- Microsoft.BingSports
Log: 'System' Date/Time: 18/09/2014 23:28:12
Type: Information Category: 0
Event: 26 Source: Application Popup
Application popup: Windows - Delayed Write Failed : Exception Processing Message 0xc0000222 Parameters 0x753E4248 0x753E4248 0x753E4248 0x753E4248
Log: 'System' Date/Time: 18/09/2014 23:27:55
Type: Information Category: 0
Event: 26 Source: Application Popup
Application popup: Windows - Delayed Write Failed : Exception Processing Message 0xc0000222 Parameters 0x753E4248 0x753E4248 0x753E4248 0x753E4248
Log: 'System' Date/Time: 18/09/2014 23:27:00
Type: Information Category: 0
Event: 98 Source: Microsoft-Windows-Ntfs
Volume OS (\Device\HarddiskVolumeShadowCopy1) is healthy. No action is needed.
Log: 'System' Date/Time: 18/09/2014 23:25:59
Type: Information Category: 157
Event: 506 Source: Microsoft-Windows-Kernel-Power
The system is entering connected standby Reason: Idle Timeout.
Log: 'System' Date/Time: 18/09/2014 23:25:53
Type: Information Category: 158
Event: 507 Source: Microsoft-Windows-Kernel-Power
The system is exiting connected standby Reason: AC/DC Display Burst.
Log: 'System' Date/Time: 18/09/2014 22:59:05
Type: Information Category: 157
Event: 506 Source: Microsoft-Windows-Kernel-Power
The system is entering connected standby Reason: Power Button.
Log: 'System' Date/Time: 18/09/2014 22:51:00
Type: Information Category: 158
Event: 507 Source: Microsoft-Windows-Kernel-Power
The system is exiting connected standby Reason: Power Button.
Log: 'System' Date/Time: 18/09/2014 21:34:21
Type: Information Category: 1
Event: 19 Source: Microsoft-Windows-WindowsUpdateClient
Installation Successful: Windows successfully installed the following update: Definition Update for Windows Defender - KB2267602 (Definition 1.185.346.0)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 18/09/2014 23:28:12
Type: Warning Category: 0
Event: 50 Source: Ntfs
{Delayed Write Failed} Windows was unable to save all the data for the file \Extend\$UsnJrnl:$J:$DATA. 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: 18/09/2014 23:27:55
Type: Warning Category: 0
Event: 50 Source: Ntfs
{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: 18/09/2014 23:27:55
Type: Warning Category: 0
Event: 50 Source: Ntfs
{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: 18/09/2014 23:27:55
Type: Warning Category: 0
Event: 50 Source: Ntfs
{Delayed Write Failed} Windows was unable to save all the data for the file \$Mft::$BITMAP. 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: 18/09/2014 23:27:32
Type: Warning Category: 0
Event: 50 Source: Ntfs
{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: 18/09/2014 23:27:26
Type: Warning Category: 0
Event: 50 Source: Ntfs
{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: 18/09/2014 23:27:15
Type: Warning Category: 0
Event: 50 Source: Ntfs
{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: 18/09/2014 23:27:07
Type: Warning Category: 0
Event: 140 Source: Microsoft-Windows-Ntfs
The system failed to flush data to the transaction log. Corruption may occur in VolumeId: OS, DeviceName: \Device\HarddiskVolumeShadowCopy1. (A device which does not exist was specified.)
Log: 'System' Date/Time: 18/09/2014 23:27:07
Type: Warning Category: 0
Event: 140 Source: Microsoft-Windows-Ntfs
The system failed to flush data to the transaction log. Corruption may occur in VolumeId: OS, DeviceName: \Device\HarddiskVolumeShadowCopy1. (A device which does not exist was specified.)
Log: 'System' Date/Time: 18/09/2014 23:27:07
Type: Warning Category: 0
Event: 140 Source: Microsoft-Windows-Ntfs
The system failed to flush data to the transaction log. Corruption may occur in VolumeId: OS, DeviceName: \Device\HarddiskVolumeShadowCopy1. (A device which does not exist was specified.)
Log: 'System' Date/Time: 18/09/2014 23:27:07
Type: Warning Category: 0
Event: 140 Source: Microsoft-Windows-Ntfs
The system failed to flush data to the transaction log. Corruption may occur in VolumeId: OS, DeviceName: \Device\HarddiskVolumeShadowCopy1. (A device which does not exist was specified.)
Log: 'System' Date/Time: 18/09/2014 23:27:07
Type: Warning Category: 0
Event: 140 Source: Microsoft-Windows-Ntfs
The system failed to flush data to the transaction log. Corruption may occur in VolumeId: OS, DeviceName: \Device\HarddiskVolumeShadowCopy1. (A device which does not exist was specified.)
Log: 'System' Date/Time: 18/09/2014 23:27:07
Type: Warning Category: 0
Event: 140 Source: Microsoft-Windows-Ntfs
The system failed to flush data to the transaction log. Corruption may occur in VolumeId: OS, DeviceName: \Device\HarddiskVolumeShadowCopy1. (A device which does not exist was specified.)
Log: 'System' Date/Time: 18/09/2014 22:53:34
Type: Warning Category: 0
Event: 4230 Source: Tcpip
TCP/IP has chosen to restrict the congestion window for several connections due to a network condition. This could be related to a problem in the TCP global or supplemental configuration and will cause degraded throughput.
Log: 'System' Date/Time: 17/09/2014 21:10:47
Type: Warning Category: 0
Event: 4230 Source: Tcpip
TCP/IP has chosen to restrict the congestion window for several connections due to a network condition. This could be related to a problem in the TCP global or supplemental configuration and will cause degraded throughput.
Log: 'System' Date/Time: 17/09/2014 14:03:31
Type: Warning Category: 0
Event: 8021 Source: BROWSER
The browser service was unable to retrieve a list of servers from the browser master [URL="file://\\HPSERVER8"]\\HPSERVER8[/URL] on the network \Device\NetBT_Tcpip_{6291DF19-B966-4754-AE45-032F97E4EDAC}. Browser master: [URL="file://\\HPSERVER8"]\\HPSERVER8[/URL] Network: \Device\NetBT_Tcpip_{6291DF19-B966-4754-AE45-032F97E4EDAC} This event may be caused by a temporary loss of network connectivity. If this message appears again, verify that the server is still connected to the network. The return code is in the Data text box.
Log: 'System' Date/Time: 17/09/2014 11:31:46
Type: Warning Category: 0
Event: 16002 Source: AFD
Closing a UDP socket with local port number 65051 in process 1172 is taking longer than expected. The local port number may not be available until the close operation is completed. This happens typically due to misbehaving network drivers. Ensure latest updates are installed for Windows and any third-party networking software including NIC drivers, firewalls, or other security products.
Log: 'System' Date/Time: 17/09/2014 11:31:46
Type: Warning Category: 0
Event: 16002 Source: AFD
Closing a UDP socket with local port number 55155 in process 1172 is taking longer than expected. The local port number may not be available until the close operation is completed. This happens typically due to misbehaving network drivers. Ensure latest updates are installed for Windows and any third-party networking software including NIC drivers, firewalls, or other security products.
Log: 'System' Date/Time: 17/09/2014 11:31:43
Type: Warning Category: 0
Event: 16002 Source: AFD
Closing a UDP socket with local port number 54928 in process 1172 is taking longer than expected. The local port number may not be available until the close operation is completed. This happens typically due to misbehaving network drivers. Ensure latest updates are installed for Windows and any third-party networking software including NIC drivers, firewalls, or other security products.
Log: 'System' Date/Time: 17/09/2014 11:31:43
Type: Warning Category: 0
Event: 16002 Source: AFD
Closing a UDP socket with local port number 63946 in process 1172 is taking longer than expected. The local port number may not be available until the close operation is completed. This happens typically due to misbehaving network drivers. Ensure latest updates are installed for Windows and any third-party networking software including NIC drivers, firewalls, or other security products.
