http://speccy.pirifo...RYL4LuvO6guHn2g
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Microsoft Windows [Version 6.1.7601]
Copyright © 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32> sfc /scannow
Beginning system scan. This process will take some time.
Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection found corrupt files but was unable to fix some of th
em.
Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example
C:\Windows\Logs\CBS\CBS.log
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Vino's Event Viewer v01c run on Windows 2008 in
English
Report run at 10/04/2018 17:54:39
Note: All dates below are in the format
dd/mm/yyyy
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 09/04/2018 15:07:34
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/04/2018 12:13:31
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: 06/04/2018 13:28: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: 31/03/2018 19:19:44
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: 31/03/2018 16:22: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: 31/03/2018 15:47:29
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: 31/03/2018 13:19:18
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: 31/03/2018 12:14:57
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: 31/03/2018 11:57:33
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: 31/03/2018 10:57:47
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: 31/03/2018 10:52: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.
Log: 'System' Date/Time: 29/03/2018 15:17:45
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/03/2018 14:11:19
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/03/2018 05:52:18
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: 24/03/2018 15:22: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: 24/03/2018 14:33:17
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: 23/03/2018 05:25:22
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/03/2018 14:38:58
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: 21/03/2018 14:55:55
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting
down first. This error could be caused if the
system stopped responding, crashed, or lost
power unexpectedly.
Log: 'System' Date/Time: 18/03/2018 05:44:41
Type: Critical Category: 64
Event: 10111 Source: Microsoft-Windows-
DriverFrameworks-UserMode
The device Lenovo TAB3 7 Essential (location
Port_#0005.Hub_#0004) is offline due to a user-
mode driver crash. Windows will attempt to
restart the device 4 more times. Please contact
the device manufacturer for more information
about this problem.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 10/04/2018 16:06:21
Type: Error Category: 0
Event: 7011 Source: Service Control Manager
A timeout (30000 milliseconds) was reached while
waiting for a transaction response from the
WerSvc service.
Log: 'System' Date/Time: 10/04/2018 14:41:04
Type: Error Category: 0
Event: 36887 Source: Schannel
The following fatal alert was received: 40.
Log: 'System' Date/Time: 10/04/2018 14:41:04
Type: Error Category: 0
Event: 36887 Source: Schannel
The following fatal alert was received: 70.
Log: 'System' Date/Time: 10/04/2018 13:16:53
Type: Error Category: 0
Event: 7001 Source: Service Control Manager
The Intel® Management & Security Application
User Notification Service service depends on the
Intel® Management and Security Application
Local Management Service service which failed to
start because of the following error: The
service cannot be started, either because it is
disabled or because it has no enabled devices
associated with it.
Log: 'System' Date/Time: 10/04/2018 13:13:19
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The Origin Web Helper 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: 10/04/2018 13:13:19
Type: Error Category: 0
Event: 7009 Source: Service Control Manager
A timeout was reached (30000 milliseconds) while
waiting for the Origin Web Helper Service
service to connect.
Log: 'System' Date/Time: 09/04/2018 19:45:29
Type: Error Category: 0
Event: 7043 Source: Service Control Manager
The Windows Modules Installer service did not
shut down properly after receiving a preshutdown
control.
Log: 'System' Date/Time: 09/04/2018 17:19:35
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-
DistributedCOM
The server {752073A1-23F2-4396-85F0-
8FDB879ED0ED} did not register with DCOM within
the required timeout.
Log: 'System' Date/Time: 09/04/2018 15:11:55
Type: Error Category: 0
Event: 7001 Source: Service Control Manager
The Intel® Management & Security Application
User Notification Service service depends on the
Intel® Management and Security Application
Local Management Service service which failed to
start because of the following error: The
service cannot be started, either because it is
disabled or because it has no enabled devices
associated with it.
Log: 'System' Date/Time: 09/04/2018 15:09:25
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The Origin Web Helper 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: 09/04/2018 15:09:25
Type: Error Category: 0
Event: 7009 Source: Service Control Manager
A timeout was reached (30000 milliseconds) while
waiting for the Origin Web Helper Service
service to connect.
Log: 'System' Date/Time: 09/04/2018 15:07:57
Type: Error Category: 0
Event: 6008 Source: EventLog
The previous system shutdown at 16:03:12 on ?
09/?04/?2018 was unexpected.
Log: 'System' Date/Time: 09/04/2018 13:31:22
Type: Error Category: 0
Event: 7001 Source: Service Control Manager
The Intel® Management & Security Application
User Notification Service service depends on the
Intel® Management and Security Application
Local Management Service service which failed to
start because of the following error: The
service cannot be started, either because it is
disabled or because it has no enabled devices
associated with it.
Log: 'System' Date/Time: 09/04/2018 13:28:30
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The Origin Web Helper 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: 09/04/2018 13:28:30
Type: Error Category: 0
Event: 7009 Source: Service Control Manager
A timeout was reached (30000 milliseconds) while
waiting for the Origin Web Helper Service
service to connect.
Log: 'System' Date/Time: 09/04/2018 13:27:20
Type: Error Category: 0
Event: 6008 Source: EventLog
The previous system shutdown at 20:08:40 on ?
08/?04/?2018 was unexpected.
Log: 'System' Date/Time: 08/04/2018 19:09:26
Type: Error Category: 0
Event: 7011 Source: Service Control Manager
A timeout (30000 milliseconds) was reached while
waiting for a transaction response from the
BsMailProxy service.
Log: 'System' Date/Time: 08/04/2018 19:08:06
Type: Error Category: 0
Event: 7043 Source: Service Control Manager
The Windows Modules Installer service did not
shut down properly after receiving a preshutdown
control.
Log: 'System' Date/Time: 08/04/2018 15:56:32
Type: Error Category: 0
Event: 7031 Source: Service Control Manager
The Malwarebytes Service service terminated
unexpectedly. It has done this 1 time(s). The
following corrective action will be taken in
5000 milliseconds: Restart the service.
Log: 'System' Date/Time: 08/04/2018 12:18:27
Type: Error Category: 0
Event: 7001 Source: Service Control Manager
The Intel® Management & Security Application
User Notification Service service depends on the
Intel® Management and Security Application
Local Management Service service which failed to
start because of the following error: The
service cannot be started, either because it is
disabled or because it has no enabled devices
associated with it.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 10/04/2018 13:14:10
Type: Warning Category: 0
Event: 2511 Source: Server
The server service was unable to recreate the
share My Apps because the directory C:
\ProgramData\Bluestacks\UserData\Library\My Apps
no longer exists. Please run "net share My Apps
/delete" to delete the share, or recreate the
directory C:\ProgramData\Bluestacks\UserData
\Library\My Apps.
Log: 'System' Date/Time: 10/04/2018 13:12:47
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.
Log: 'System' Date/Time: 09/04/2018 15:09:53
Type: Warning Category: 0
Event: 2511 Source: Server
The server service was unable to recreate the
share My Apps because the directory C:
\ProgramData\Bluestacks\UserData\Library\My Apps
no longer exists. Please run "net share My Apps
/delete" to delete the share, or recreate the
directory C:\ProgramData\Bluestacks\UserData
\Library\My Apps.
Log: 'System' Date/Time: 09/04/2018 15:08:07
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.
Log: 'System' Date/Time: 09/04/2018 14:41:51
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name www.facebook.com
timed out after none of the configured DNS
servers responded.
Log: 'System' Date/Time: 09/04/2018 13:29:19
Type: Warning Category: 0
Event: 2511 Source: Server
The server service was unable to recreate the
share My Apps because the directory C:
\ProgramData\Bluestacks\UserData\Library\My Apps
no longer exists. Please run "net share My Apps
/delete" to delete the share, or recreate the
directory C:\ProgramData\Bluestacks\UserData
\Library\My Apps.
Log: 'System' Date/Time: 09/04/2018 13:27:30
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.
Log: 'System' Date/Time: 08/04/2018 12:16:23
Type: Warning Category: 0
Event: 2511 Source: Server
The server service was unable to recreate the
share My Apps because the directory C:
\ProgramData\Bluestacks\UserData\Library\My Apps
no longer exists. Please run "net share My Apps
/delete" to delete the share, or recreate the
directory C:\ProgramData\Bluestacks\UserData
\Library\My Apps.
Log: 'System' Date/Time: 08/04/2018 12:16:16
Type: Warning Category: 0
Event: 130 Source: Ntfs
The file system structure on volume C: has now
been repaired.
Log: 'System' Date/Time: 08/04/2018 12:13:52
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.
Log: 'System' Date/Time: 07/04/2018 08:24:58
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name google.com.au timed
out after none of the configured DNS servers
responded.
Log: 'System' Date/Time: 07/04/2018 05:56:46
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name keystone.mwbsys.com
timed out after none of the configured DNS
servers responded.
Log: 'System' Date/Time: 07/04/2018 05:52:39
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name bullguard.com timed
out after none of the configured DNS servers
responded.
Log: 'System' Date/Time: 07/04/2018 05:52:22
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name facebook.com timed
out after none of the configured DNS servers
responded.
Log: 'System' Date/Time: 06/04/2018 16:42:58
Type: Warning Category: 0
Event: 2511 Source: Server
The server service was unable to recreate the
share My Apps because the directory C:
\ProgramData\Bluestacks\UserData\Library\My Apps
no longer exists. Please run "net share My Apps
/delete" to delete the share, or recreate the
directory C:\ProgramData\Bluestacks\UserData
\Library\My Apps.
Log: 'System' Date/Time: 06/04/2018 13:28:46
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.
Log: 'System' Date/Time: 05/04/2018 20:04:11
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name facebook.com timed
out after none of the configured DNS servers
responded.
Log: 'System' Date/Time: 05/04/2018 18:00:12
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name bullguard.com timed
out after none of the configured DNS servers
responded.
Log: 'System' Date/Time: 05/04/2018 18:00:10
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name settings-
win.data.microsoft.com timed out after none of
the configured DNS servers responded.
Log: 'System' Date/Time: 05/04/2018 18:00:07
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name www.bullguard.com
timed out after none of the configured DNS
servers responded.