I already found a fix with a registry change, but here is the info requested, tell me if you found anyelse wrong
Vino's Event Viewer v01c run on Windows 7 in English
Report run at 19/12/2014 10:35:13 AM
Note: All dates below are in the format dd/mm/yyyy
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 19/12/2014 12:14:13 PM
Type: Error Category: 0
Event: 255 Source: iumsvc
The event description cannot be found.
Log: 'Application' Date/Time: 19/12/2014 12:14:07 PM
Type: Error Category: 0
Event: 255 Source: iumsvc
The event description cannot be found.
Log: 'Application' Date/Time: 19/12/2014 12:14:05 PM
Type: Error Category: 0
Event: 255 Source: iumsvc
The event description cannot be found.
Log: 'Application' Date/Time: 19/12/2014 12:14:03 PM
Type: Error Category: 0
Event: 255 Source: iumsvc
The event description cannot be found.
Log: 'Application' Date/Time: 19/12/2014 12:14:02 PM
Type: Error Category: 0
Event: 255 Source: iumsvc
The event description cannot be found.
Log: 'Application' Date/Time: 19/12/2014 12:14:02 PM
Type: Error Category: 0
Event: 255 Source: iumsvc
The event description cannot be found.
Log: 'Application' Date/Time: 19/12/2014 12:13:08 PM
Type: Error Category: 101
Event: 1002 Source: Application Hang
The program backgroundTaskHost.exe version 6.3.9600.17415 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: 12c8 Start Time: 01d01b846cced554 Termination Time: 4294967295 Application Path: C:\WINDOWS\system32\backgroundTaskHost.exe Report Id: 628bcdc2-8778-11e4-82e0-ac220baf2615 Faulting package full name: Facebook.Facebook_1.4.0.9_x64__8xx8rvfyw5nnt Faulting package-relative application ID: App
Log: 'Application' Date/Time: 19/12/2014 12:07:38 PM
Type: Error Category: 0
Event: 1008 Source: Microsoft-Windows-Perflib
The Open Procedure for service "BITS" in DLL "C:\Windows\System32\bitsperf.dll" failed. Performance data for this service will not be available. The first four bytes (DWORD) of the Data section contains the error code.
Log: 'Application' Date/Time: 19/12/2014 5:29:31 AM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: DVDFab.exe, version: 9.1.7.9, time stamp: 0x5488118f Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x2e5b1b78 Faulting process id: 0x163c Faulting application start time: 0x01d01b4cc2bf7c01 Faulting application path: C:\Program Files (x86)\DVDFab 9\DVDFab.exe Faulting module path: unknown Report Id: 01a92a75-8740-11e4-82df-ac220baf2615 Faulting package full name: Faulting package-relative application ID:
Log: 'Application' Date/Time: 19/12/2014 3:37:00 AM
Type: Error Category: 0
Event: 255 Source: iumsvc
The event description cannot be found.
Log: 'Application' Date/Time: 19/12/2014 3:36:59 AM
Type: Error Category: 0
Event: 255 Source: iumsvc
The event description cannot be found.
Log: 'Application' Date/Time: 19/12/2014 3:36:57 AM
Type: Error Category: 0
Event: 255 Source: iumsvc
The event description cannot be found.
Log: 'Application' Date/Time: 19/12/2014 3:36:57 AM
Type: Error Category: 0
Event: 255 Source: iumsvc
The event description cannot be found.
Log: 'Application' Date/Time: 19/12/2014 3:36:55 AM
Type: Error Category: 0
Event: 255 Source: iumsvc
The event description cannot be found.
Log: 'Application' Date/Time: 19/12/2014 3:36:55 AM
Type: Error Category: 0
Event: 255 Source: iumsvc
The event description cannot be found.
Log: 'Application' Date/Time: 19/12/2014 3:27:58 AM
Type: Error Category: 101
Event: 1002 Source: Application Hang
The program LiveComm.exe version 17.5.9600.20689 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: 12b4 Start Time: 01d01b3b0ff6d4ae Termination Time: 4294967295 Application Path: C:\Program Files\WindowsApps\microsoft.windowscommunicationsapps_17.5.9600.20689_x64__8wekyb3d8bbwe\LiveComm.exe Report Id: 060033f0-872f-11e4-82df-ac220baf2615 Faulting package full name: microsoft.windowscommunicationsapps_17.5.9600.20689_x64__8wekyb3d8bbwe Faulting package-relative application ID: ppleae38af2e007f4358a809ac99a64a67c1
Log: 'Application' Date/Time: 19/12/2014 3:27:56 AM
Type: Error Category: 101
Event: 1002 Source: Application Hang
The program LiveComm.exe version 17.5.9600.20689 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: 12b4 Start Time: 01d01b3b0ff6d4ae Termination Time: 4294967295 Application Path: C:\Program Files\WindowsApps\microsoft.windowscommunicationsapps_17.5.9600.20689_x64__8wekyb3d8bbwe\LiveComm.exe Report Id: 04475e1a-872f-11e4-82df-ac220baf2615 Faulting package full name: microsoft.windowscommunicationsapps_17.5.9600.20689_x64__8wekyb3d8bbwe Faulting package-relative application ID: ppleae38af2e007f4358a809ac99a64a67c1
Log: 'Application' Date/Time: 19/12/2014 3:27:56 AM
Type: Error Category: 101
Event: 1002 Source: Application Hang
The program backgroundTaskHost.exe version 6.3.9600.17415 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: 1218 Start Time: 01d01b3b0fce4cbc Termination Time: 4294967295 Application Path: C:\WINDOWS\system32\backgroundTaskHost.exe Report Id: 0445d737-872f-11e4-82df-ac220baf2615 Faulting package full name: Facebook.Facebook_1.4.0.9_x64__8xx8rvfyw5nnt Faulting package-relative application ID: App
Log: 'Application' Date/Time: 19/12/2014 2:54:06 AM
Type: Error Category: 0
Event: 255 Source: iumsvc
The event description cannot be found.
Log: 'Application' Date/Time: 19/12/2014 2:54:05 AM
Type: Error Category: 0
Event: 255 Source: iumsvc
The event description cannot be found.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Information Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 19/12/2014 1:33:54 PM
Type: Information Category: 0
Event: 0 Source: PDEngine
SMARTPlacement operation has been paused for drive C:\.
Log: 'Application' Date/Time: 19/12/2014 1:33:53 PM
Type: Information Category: 0
Event: 66 Source: PDAgent
StealthPatrol schedule suspended on drive C:\ : System activity (kernel mode CPU) .
Log: 'Application' Date/Time: 19/12/2014 1:33:27 PM
Type: Information Category: 0
Event: 0 Source: PDEngine
SMARTPlacement operation has been resumed for drive C:\.
Log: 'Application' Date/Time: 19/12/2014 1:33:27 PM
Type: Information Category: 0
Event: 67 Source: PDAgent
StealthPatrol schedule resumed on drive C:\ .
Log: 'Application' Date/Time: 19/12/2014 1:28:21 PM
Type: Information Category: 0
Event: 0 Source: PDEngine
SMARTPlacement operation has been paused for drive C:\.
Log: 'Application' Date/Time: 19/12/2014 1:28:20 PM
Type: Information Category: 0
Event: 66 Source: PDAgent
StealthPatrol schedule suspended on drive C:\ : System activity (kernel mode CPU) .
Log: 'Application' Date/Time: 19/12/2014 1:21:21 PM
Type: Information Category: 0
Event: 0 Source: PDEngine
SMARTPlacement operation has been resumed for drive C:\.
Log: 'Application' Date/Time: 19/12/2014 1:21:21 PM
Type: Information Category: 0
Event: 67 Source: PDAgent
StealthPatrol schedule resumed on drive C:\ .
Log: 'Application' Date/Time: 19/12/2014 1:16:15 PM
Type: Information Category: 0
Event: 0 Source: PDEngine
SMARTPlacement operation has been paused for drive C:\.
Log: 'Application' Date/Time: 19/12/2014 1:16:14 PM
Type: Information Category: 0
Event: 66 Source: PDAgent
StealthPatrol schedule suspended on drive C:\ : System activity (disk I/O) .
Log: 'Application' Date/Time: 19/12/2014 1:11:03 PM
Type: Information Category: 0
Event: 0 Source: PDEngine
SMARTPlacement operation has been resumed for drive C:\.
Log: 'Application' Date/Time: 19/12/2014 1:11:03 PM
Type: Information Category: 0
Event: 67 Source: PDAgent
StealthPatrol schedule resumed on drive C:\ .
Log: 'Application' Date/Time: 19/12/2014 1:05:57 PM
Type: Information Category: 0
Event: 0 Source: PDEngine
SMARTPlacement operation has been paused for drive C:\.
Log: 'Application' Date/Time: 19/12/2014 1:05:56 PM
Type: Information Category: 0
Event: 66 Source: PDAgent
StealthPatrol schedule suspended on drive C:\ : System activity (kernel mode CPU) .
Log: 'Application' Date/Time: 19/12/2014 12:51:21 PM
Type: Information Category: 0
Event: 0 Source: PDEngine
SMARTPlacement operation has been resumed for drive C:\.
Log: 'Application' Date/Time: 19/12/2014 12:51:21 PM
Type: Information Category: 0
Event: 67 Source: PDAgent
StealthPatrol schedule resumed on drive C:\ .
Log: 'Application' Date/Time: 19/12/2014 12:46:15 PM
Type: Information Category: 0
Event: 0 Source: PDEngine
SMARTPlacement operation has been paused for drive C:\.
Log: 'Application' Date/Time: 19/12/2014 12:46:14 PM
Type: Information Category: 0
Event: 66 Source: PDAgent
StealthPatrol schedule suspended on drive C:\ : System activity (kernel mode CPU) .
Log: 'Application' Date/Time: 19/12/2014 12:39:33 PM
Type: Information Category: 0
Event: 0 Source: PDEngine
SMARTPlacement operation has been resumed for drive C:\.
Log: 'Application' Date/Time: 19/12/2014 12:39:32 PM
Type: Information Category: 0
Event: 67 Source: PDAgent
StealthPatrol schedule resumed on drive C:\ .
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 19/12/2014 12:09:25 PM
Type: Warning Category: 0
Event: 1 Source: Microsoft-Windows-ApplicationExperienceInfrastructure
The application (Intel Bluetooth Wireless High Speed, from vendor Intel) has the following problem: To function properly, Intel Bluetooth Wireless High Speed must be reinstalled after you upgrade Windows.
Log: 'Application' Date/Time: 19/12/2014 12:09:12 PM
Type: Warning Category: 0
Event: 1 Source: Microsoft-Windows-ApplicationExperienceInfrastructure
The application (Outpost, from vendor Agnitum Ltd.) has the following problem: To function properly, Outpost must be reinstalled after you upgrade Windows.
Log: 'Application' Date/Time: 19/12/2014 3:36:36 AM
Type: Warning Category: 1
Event: 532 Source: ESENT
LiveComm (3648) C:\Users\Alexis\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\6b259be21302d5df\120712-0049\: A request to read from the file "C:\Users\Alexis\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\6b259be21302d5df\120712-0049\DBStore\livecomm.edb" at offset 10289152 (0x00000000009d0000) for 8192 (0x00002000) bytes has not completed for 36 second(s). This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.
Log: 'Application' Date/Time: 19/12/2014 3:36:36 AM
Type: Warning Category: 1
Event: 532 Source: ESENT
LiveComm (3648) C:\Users\Alexis\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\6b259be21302d5df\120712-0049\: A request to read from the file "C:\Users\Alexis\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\6b259be21302d5df\120712-0049\DBStore\livecomm.edb" at offset 10256384 (0x00000000009c8000) for 8192 (0x00002000) bytes has not completed for 36 second(s). This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.
Log: 'Application' Date/Time: 19/12/2014 3:36:36 AM
Type: Warning Category: 7
Event: 507 Source: ESENT
LiveComm (3648) C:\Users\Alexis\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\6b259be21302d5df\120712-0049\: A request to read from the file "C:\Users\Alexis\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\6b259be21302d5df\120712-0049\DBStore\livecomm.edb" at offset 8962048 (0x000000000088c000) for 8192 (0x00002000) bytes succeeded, but took an abnormally long time (42 seconds) to be serviced by the OS. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.
Log: 'Application' Date/Time: 19/12/2014 3:24:01 AM
Type: Warning Category: 0
Event: 1 Source: Microsoft-Windows-ApplicationExperienceInfrastructure
The application (Intel Bluetooth Wireless High Speed, from vendor Intel) has the following problem: To function properly, Intel Bluetooth Wireless High Speed must be reinstalled after you upgrade Windows.
Log: 'Application' Date/Time: 19/12/2014 3:24:00 AM
Type: Warning Category: 0
Event: 1 Source: Microsoft-Windows-ApplicationExperienceInfrastructure
The application (Outpost, from vendor Agnitum Ltd.) has the following problem: To function properly, Outpost must be reinstalled after you upgrade Windows.
Log: 'Application' Date/Time: 19/12/2014 2:49:42 AM
Type: Warning Category: 0
Event: 1 Source: Microsoft-Windows-ApplicationExperienceInfrastructure
The application (Intel Bluetooth Wireless High Speed, from vendor Intel) has the following problem: To function properly, Intel Bluetooth Wireless High Speed must be reinstalled after you upgrade Windows.
Log: 'Application' Date/Time: 19/12/2014 2:49:37 AM
Type: Warning Category: 0
Event: 1 Source: Microsoft-Windows-ApplicationExperienceInfrastructure
The application (Outpost, from vendor Agnitum Ltd.) has the following problem: To function properly, Outpost must be reinstalled after you upgrade Windows.
Log: 'Application' Date/Time: 19/12/2014 2:11:29 AM
Type: Warning Category: 7
Event: 507 Source: ESENT
LiveComm (1360) C:\Users\Alexis\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\6b259be21302d5df\120712-0049\: A request to read from the file "C:\Users\Alexis\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\6b259be21302d5df\120712-0049\DBStore\livecomm.edb" at offset 10698752 (0x0000000000a34000) for 8192 (0x00002000) bytes succeeded, but took an abnormally long time (24 seconds) to be serviced by the OS. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.
Log: 'Application' Date/Time: 19/12/2014 2:08:22 AM
Type: Warning Category: 0
Event: 1 Source: Microsoft-Windows-ApplicationExperienceInfrastructure
The application (Outpost, from vendor Agnitum Ltd.) has the following problem: To function properly, Outpost must be reinstalled after you upgrade Windows.
Log: 'Application' Date/Time: 19/12/2014 2:05:30 AM
Type: Warning Category: 0
Event: 1 Source: Microsoft-Windows-ApplicationExperienceInfrastructure
The application (Intel Bluetooth Wireless High Speed, from vendor Intel) has the following problem: To function properly, Intel Bluetooth Wireless High Speed must be reinstalled after you upgrade Windows.
Log: 'Application' Date/Time: 18/12/2014 11:42:05 AM
Type: Warning Category: 0
Event: 1 Source: Microsoft-Windows-ApplicationExperienceInfrastructure
The application (Intel Bluetooth Wireless High Speed, from vendor Intel) has the following problem: To function properly, Intel Bluetooth Wireless High Speed must be reinstalled after you upgrade Windows.
Log: 'Application' Date/Time: 18/12/2014 11:41:52 AM
Type: Warning Category: 0
Event: 1 Source: Microsoft-Windows-ApplicationExperienceInfrastructure
The application (Outpost, from vendor Agnitum Ltd.) has the following problem: To function properly, Outpost must be reinstalled after you upgrade Windows.
Log: 'Application' Date/Time: 18/12/2014 5:46:56 AM
Type: Warning Category: 0
Event: 1 Source: Microsoft-Windows-ApplicationExperienceInfrastructure
The application (Intel Bluetooth Wireless High Speed, from vendor Intel) has the following problem: To function properly, Intel Bluetooth Wireless High Speed must be reinstalled after you upgrade Windows.
Log: 'Application' Date/Time: 18/12/2014 5:46:36 AM
Type: Warning Category: 0
Event: 1 Source: Microsoft-Windows-ApplicationExperienceInfrastructure
The application (Outpost, from vendor Agnitum Ltd.) has the following problem: To function properly, Outpost must be reinstalled after you upgrade Windows.
Log: 'Application' Date/Time: 18/12/2014 5:12:31 AM
Type: Warning Category: 3
Event: 472 Source: ESENT
LiveComm (5844) C:\Users\Alexis\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\6b259be21302d5df\120712-0049\: The shadow header page of file C:\Users\Alexis\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\6b259be21302d5df\120712-0049\DBStore\livecomm.edb was damaged. The primary header page (8192 bytes) was used instead.
Log: 'Application' Date/Time: 18/12/2014 5:05:52 AM
Type: Warning Category: 0
Event: 1 Source: Microsoft-Windows-ApplicationExperienceInfrastructure
The application (Intel Bluetooth Wireless High Speed, from vendor Intel) has the following problem: To function properly, Intel Bluetooth Wireless High Speed must be reinstalled after you upgrade Windows.
Log: 'Application' Date/Time: 18/12/2014 5:05:45 AM
Type: Warning Category: 0
Event: 1 Source: Microsoft-Windows-ApplicationExperienceInfrastructure
The application (Outpost, from vendor Agnitum Ltd.) has the following problem: To function properly, Outpost must be reinstalled after you upgrade Windows.
Log: 'Application' Date/Time: 18/12/2014 2:06:47 AM
Type: Warning Category: 0
Event: 1 Source: Microsoft-Windows-ApplicationExperienceInfrastructure
The application (Outpost, from vendor Agnitum Ltd.) has the following problem: To function properly, Outpost must be reinstalled after you upgrade Windows.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 05/12/2014 11:08:04 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: 19/12/2014 12:06:38 PM
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The Apple Mobile Device 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: 19/12/2014 12:06:38 PM
Type: Error Category: 0
Event: 7009 Source: Service Control Manager
A timeout was reached (30000 milliseconds) while waiting for the Apple Mobile Device service to connect.
Log: 'System' Date/Time: 19/12/2014 3:28:09 AM
Type: Error Category: 0
Event: 7034 Source: Service Control Manager
The Soluto PCGenome Core Service service terminated unexpectedly. It has done this 1 time(s).
Log: 'System' Date/Time: 19/12/2014 2:02:43 AM
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The ASLDR Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion.
Log: 'System' Date/Time: 19/12/2014 2:02:43 AM
Type: Error Category: 0
Event: 7009 Source: Service Control Manager
A timeout was reached (30000 milliseconds) while waiting for the ASLDR Service service to connect.
Log: 'System' Date/Time: 18/12/2014 5:44:06 AM
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The Apple Mobile Device 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/12/2014 5:44:06 AM
Type: Error Category: 0
Event: 7009 Source: Service Control Manager
A timeout was reached (30000 milliseconds) while waiting for the Apple Mobile Device service to connect.
Log: 'System' Date/Time: 18/12/2014 5:07:57 AM
Type: Error Category: 0
Event: 7022 Source: Service Control Manager
The Intel® Centrino® Wireless Bluetooth® + High Speed Service service hung on starting.
Log: 'System' Date/Time: 18/12/2014 3:43:07 AM
Type: Error Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID {C2F03A33-21F5-47FA-B4BB-156362A2F239} and APPID {316CDED5-E4AE-4B15-9113-7055D84DCC97} to the user CALCU\Alexis SID (S-1-5-21-1318044153-752161398-541790769-1002) from address LocalHost (Using LRPC) running in the application container Microsoft.BingNews_3.0.4.213_x64__8wekyb3d8bbwe SID (S-1-15-2-508114518-3340871649-811464485-526616082-4258465299-1774086546-1865468257). This security permission can be modified using the Component Services administrative tool.
Log: 'System' Date/Time: 17/12/2014 3:07:55 PM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {4AA0A5C4-1B9B-4F2E-99D7-99C6AEC83474} did not register with DCOM within the required timeout.
Log: 'System' Date/Time: 17/12/2014 3:07:25 PM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {4AA0A5C4-1B9B-4F2E-99D7-99C6AEC83474} did not register with DCOM within the required timeout.
Log: 'System' Date/Time: 17/12/2014 3:07:25 PM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {4AA0A5C4-1B9B-4F2E-99D7-99C6AEC83474} did not register with DCOM within the required timeout.
Log: 'System' Date/Time: 17/12/2014 7:15:45 AM
Type: Error Category: 0
Event: 7023 Source: Service Control Manager
The Superfetch service terminated with the following error: The service has not been started.
Log: 'System' Date/Time: 17/12/2014 7:15:43 AM
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The Software Protection service failed to start due to the following error: The service did not start due to a logon failure.
Log: 'System' Date/Time: 17/12/2014 7:15:43 AM
Type: Error Category: 0
Event: 7038 Source: Service Control Manager
The sppsvc service was unable to log on as NT AUTHORITY\NetworkService with the currently configured password due to the following error: The security account manager (SAM) or local security authority (LSA) server was in the wrong state to perform the security operation. To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC).
Log: 'System' Date/Time: 17/12/2014 2:20:16 AM
Type: Error Category: 1
Event: 20 Source: Microsoft-Windows-WindowsUpdateClient
Installation Failure: Windows failed to install the following update with error 0x80070005: Update for Windows 8.1 for x64-based Systems (KB2976978).
Log: 'System' Date/Time: 17/12/2014 2:12:25 AM
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The Apple Mobile Device 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: 17/12/2014 2:12:25 AM
Type: Error Category: 0
Event: 7009 Source: Service Control Manager
A timeout was reached (30000 milliseconds) while waiting for the Apple Mobile Device service to connect.
Log: 'System' Date/Time: 16/12/2014 2:45:07 AM
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The Apple Mobile Device 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: 16/12/2014 2:45:07 AM
Type: Error Category: 0
Event: 7009 Source: Service Control Manager
A timeout was reached (30000 milliseconds) while waiting for the Apple Mobile Device service to connect.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Information Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 19/12/2014 1:33:49 PM
Type: Information Category: 0
Event: 7040 Source: Service Control Manager
The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start.
Log: 'System' Date/Time: 19/12/2014 1:18:22 PM
Type: Information Category: 0
Event: 7040 Source: Service Control Manager
The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start.
Log: 'System' Date/Time: 19/12/2014 12:35:35 PM
Type: Information Category: 10
Event: 12 Source: Microsoft-Windows-UserModePowerService
Process C:\Windows\System32\WinSAT.exe (process ID:5500) reset policy scheme from {8C5E7FDA-E8BF-4A96-9A85-A6E23A8C635C} to {A1841308-3541-4FAB-BC81-F71556F20B4A}
Log: 'System' Date/Time: 19/12/2014 12:35:28 PM
Type: Information Category: 10
Event: 12 Source: Microsoft-Windows-UserModePowerService
Process C:\Windows\System32\WinSAT.exe (process ID:5500) reset policy scheme from {A1841308-3541-4FAB-BC81-F71556F20B4A} to {8C5E7FDA-E8BF-4A96-9A85-A6E23A8C635C}
Log: 'System' Date/Time: 19/12/2014 12:21:41 PM
Type: Information Category: 1
Event: 19 Source: Microsoft-Windows-WindowsUpdateClient
Installation Successful: Windows successfully installed the following update: MAGIX.MusicMakerJam
Log: 'System' Date/Time: 19/12/2014 12:19:26 PM
Type: Information Category: 1
Event: 43 Source: Microsoft-Windows-WindowsUpdateClient
Installation Started: Windows has started installing the following update: MAGIX.MusicMakerJam
Log: 'System' Date/Time: 19/12/2014 12:18:28 PM
Type: Information Category: 2
Event: 17 Source: Microsoft-Windows-WindowsUpdateClient
Installation Ready: The following updates are downloaded and ready for installation:
- MAGIX.MusicMakerJam
Log: 'System' Date/Time: 19/12/2014 12:15:48 PM
Type: Information Category: 0
Event: 7040 Source: Service Control Manager
The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start.
Log: 'System' Date/Time: 19/12/2014 12:10:46 PM
Type: Information Category: 0
Event: 14206 Source: Microsoft-Windows-WMPNSS-Service
Media server 'CALCU:
alexis_arenas@hotmail.com:' was successfully initialized and is sharing media with network media devices.
Log: 'System' Date/Time: 19/12/2014 12:10:43 PM
Type: Information Category: 0
Event: 14204 Source: Microsoft-Windows-WMPNSS-Service
Service 'WMPNetworkSvc' started.
Log: 'System' Date/Time: 19/12/2014 12:07:43 PM
Type: Information Category: 0
Event: 16 Source: Microsoft-Windows-Kernel-General
The access history in hive \??\C:\Users\Alexis\AppData\Local\Microsoft\Windows\UsrClass.dat was cleared updating 21502 keys and creating 2037 modified pages.
Log: 'System' Date/Time: 19/12/2014 12:07:43 PM
Type: Information Category: 0
Event: 16 Source: Microsoft-Windows-Kernel-General
The access history in hive \??\C:\Users\Alexis\ntuser.dat was cleared updating 9785 keys and creating 753 modified pages.
Log: 'System' Date/Time: 19/12/2014 12:07:43 PM
Type: Information Category: 1101
Event: 7001 Source: Microsoft-Windows-Winlogon
User Logon Notification for Customer Experience Improvement Program
Log: 'System' Date/Time: 19/12/2014 12:07:23 PM
Type: Information Category: 0
Event: 7026 Source: Service Control Manager
The following boot-start or system-start driver(s) did not load: dam
Log: 'System' Date/Time: 19/12/2014 12:06:48 PM
Type: Information Category: 10
Event: 12 Source: Microsoft-Windows-UserModePowerService
Process C:\Windows\System32\DptfPolicyConfigTDPService.exe (process ID:2316) reset policy scheme from {A1841308-3541-4FAB-BC81-F71556F20B4A} to {A1841308-3541-4FAB-BC81-F71556F20B4A}
Log: 'System' Date/Time: 19/12/2014 12:06:48 PM
Type: Information Category: 10
Event: 12 Source: Microsoft-Windows-UserModePowerService
Process C:\Windows\System32\DptfParticipantProcessorService.exe (process ID:2284) reset policy scheme from {A1841308-3541-4FAB-BC81-F71556F20B4A} to {A1841308-3541-4FAB-BC81-F71556F20B4A}
Log: 'System' Date/Time: 19/12/2014 12:06:47 PM
Type: Information Category: 0
Event: 6 Source: Microsoft-Windows-FilterManager
File System Filter 'avckf' (6.1, ?2014?-?05?-?08T09:48:18.000000000Z) has successfully loaded and registered with Filter Manager.
Log: 'System' Date/Time: 19/12/2014 12:06:07 PM
Type: Information Category: 0
Event: 10001 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN Extensibility Module has successfully started. Module Path: C:\WINDOWS\System32\IWMSSvc.dll
Log: 'System' Date/Time: 19/12/2014 12:05:56 PM
Type: Information Category: 0
Event: 4000 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN AutoConfig service has successfully started.
Log: 'System' Date/Time: 19/12/2014 12:05:55 PM
Type: Information Category: 4
Event: 51046 Source: Microsoft-Windows-DHCPv6-Client
DHCPv6 client service is started
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 19/12/2014 12:06:45 PM
Type: Warning Category: 7
Event: 37 Source: Microsoft-Windows-Kernel-Processor-Power
The speed of processor 3 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 71 seconds since the last report.
Log: 'System' Date/Time: 19/12/2014 12:06:45 PM
Type: Warning Category: 7
Event: 37 Source: Microsoft-Windows-Kernel-Processor-Power
The speed of processor 2 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 71 seconds since the last report.
Log: 'System' Date/Time: 19/12/2014 12:06:45 PM
Type: Warning Category: 7
Event: 37 Source: Microsoft-Windows-Kernel-Processor-Power
The speed of processor 0 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 71 seconds since the last report.
Log: 'System' Date/Time: 19/12/2014 12:06:45 PM
Type: Warning Category: 7
Event: 37 Source: Microsoft-Windows-Kernel-Processor-Power
The speed of processor 1 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 71 seconds since the last report.
Log: 'System' Date/Time: 19/12/2014 12:05:50 PM
Type: Warning Category: 0
Event: 11 Source: Microsoft-Windows-Wininit
Custom dynamic link libraries are being loaded for every application. The system administrator should review the list of libraries to ensure they are related to trusted applications. Please visit
Working with the AppInit_DLLs registry value for more information.
Log: 'System' Date/Time: 19/12/2014 12:05:39 PM
Type: Warning Category: 0
Event: 264 Source: Win32k
A multi-touch device reported inconsistent contact information.
Log: 'System' Date/Time: 19/12/2014 6:15:48 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 'time.windows.com,0x9'. NtpClient will try again in 15 minutes and double the reattempt interval thereafter. The error was: No such host is known. (0x80072AF9)
Log: 'System' Date/Time: 19/12/2014 6:15:48 AM
Type: Warning Category: 0
Event: 10002 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN Extensibility Module has stopped. Module Path: C:\WINDOWS\System32\IWMSSvc.dll
Log: 'System' Date/Time: 19/12/2014 5:30:57 AM
Type: Warning Category: 1014
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name tracker.openbittorrent.com timed out after none of the configured DNS servers responded.
Log: 'System' Date/Time: 19/12/2014 3:21:22 AM
Type: Warning Category: 7
Event: 37 Source: Microsoft-Windows-Kernel-Processor-Power
The speed of processor 1 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 71 seconds since the last report.
Log: 'System' Date/Time: 19/12/2014 3:21:22 AM
Type: Warning Category: 7
Event: 37 Source: Microsoft-Windows-Kernel-Processor-Power
The speed of processor 3 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 71 seconds since the last report.
Log: 'System' Date/Time: 19/12/2014 3:21:22 AM
Type: Warning Category: 7
Event: 37 Source: Microsoft-Windows-Kernel-Processor-Power
The speed of processor 2 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 71 seconds since the last report.
Log: 'System' Date/Time: 19/12/2014 3:21:22 AM
Type: Warning Category: 7
Event: 37 Source: Microsoft-Windows-Kernel-Processor-Power
The speed of processor 0 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 71 seconds since the last report.
Log: 'System' Date/Time: 19/12/2014 3:20:27 AM
Type: Warning Category: 0
Event: 11 Source: Microsoft-Windows-Wininit
Custom dynamic link libraries are being loaded for every application. The system administrator should review the list of libraries to ensure they are related to trusted applications. Please visit
Working with the AppInit_DLLs registry value for more information.
Log: 'System' Date/Time: 19/12/2014 3:20:16 AM
Type: Warning Category: 0
Event: 264 Source: Win32k
A multi-touch device reported inconsistent contact information.
Log: 'System' Date/Time: 19/12/2014 3:19:41 AM
Type: Warning Category: 0
Event: 10002 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN Extensibility Module has stopped. Module Path: C:\WINDOWS\System32\IWMSSvc.dll
Log: 'System' Date/Time: 19/12/2014 2:46:03 AM
Type: Warning Category: 7
Event: 37 Source: Microsoft-Windows-Kernel-Processor-Power
The speed of processor 3 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 71 seconds since the last report.
Log: 'System' Date/Time: 19/12/2014 2:46:03 AM
Type: Warning Category: 7
Event: 37 Source: Microsoft-Windows-Kernel-Processor-Power
The speed of processor 2 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 71 seconds since the last report.
Log: 'System' Date/Time: 19/12/2014 2:46:03 AM
Type: Warning Category: 7
Event: 37 Source: Microsoft-Windows-Kernel-Processor-Power
The speed of processor 1 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 71 seconds since the last report.
Log: 'System' Date/Time: 19/12/2014 2:46:03 AM
Type: Warning Category: 7
Event: 37 Source: Microsoft-Windows-Kernel-Processor-Power
The speed of processor 0 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 71 seconds since the last report.
