Vino's Event Viewer v01c run on Windows 7 in English Report run at 03/05/2018 4:54:49 PM Note: All dates below are in the format dd/mm/yyyy ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 'System' Log - Critical Type ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Log: 'System' Date/Time: 03/05/2018 8:57:49 PM Type: Critical Category: 63 Event: 41 Source: Microsoft-Windows-Kernel-Power The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. Log: 'System' Date/Time: 03/05/2018 8:49:34 PM Type: Critical Category: 63 Event: 41 Source: Microsoft-Windows-Kernel-Power The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. Log: 'System' Date/Time: 03/05/2018 8:46:36 PM Type: Critical Category: 63 Event: 41 Source: Microsoft-Windows-Kernel-Power The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. Log: 'System' Date/Time: 03/05/2018 2:52:48 AM Type: Critical Category: 63 Event: 41 Source: Microsoft-Windows-Kernel-Power The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. Log: 'System' Date/Time: 03/05/2018 2:47:26 AM Type: Critical Category: 63 Event: 41 Source: Microsoft-Windows-Kernel-Power The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. Log: 'System' Date/Time: 02/05/2018 11:00:25 PM Type: Critical Category: 63 Event: 41 Source: Microsoft-Windows-Kernel-Power The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. Log: 'System' Date/Time: 02/05/2018 10:49:23 PM Type: Critical Category: 63 Event: 41 Source: Microsoft-Windows-Kernel-Power The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. Log: 'System' Date/Time: 30/04/2018 4:51:45 AM Type: Critical Category: 63 Event: 41 Source: Microsoft-Windows-Kernel-Power The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. Log: 'System' Date/Time: 30/04/2018 4:45:59 AM Type: Critical Category: 63 Event: 41 Source: Microsoft-Windows-Kernel-Power The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. Log: 'System' Date/Time: 29/04/2018 10:51:24 PM Type: Critical Category: 63 Event: 41 Source: Microsoft-Windows-Kernel-Power The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. Log: 'System' Date/Time: 28/04/2018 4:35:56 AM Type: Critical Category: 63 Event: 41 Source: Microsoft-Windows-Kernel-Power The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. Log: 'System' Date/Time: 28/04/2018 4:22:00 AM Type: Critical Category: 63 Event: 41 Source: Microsoft-Windows-Kernel-Power The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. Log: 'System' Date/Time: 28/04/2018 4:19:11 AM Type: Critical Category: 63 Event: 41 Source: Microsoft-Windows-Kernel-Power The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. Log: 'System' Date/Time: 28/04/2018 4:15:28 AM Type: Critical Category: 63 Event: 41 Source: Microsoft-Windows-Kernel-Power The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. Log: 'System' Date/Time: 25/04/2018 2:08:17 AM Type: Critical Category: 63 Event: 41 Source: Microsoft-Windows-Kernel-Power The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. Log: 'System' Date/Time: 25/04/2018 2:05:50 AM Type: Critical Category: 63 Event: 41 Source: Microsoft-Windows-Kernel-Power The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. Log: 'System' Date/Time: 25/04/2018 2:02:23 AM Type: Critical Category: 63 Event: 41 Source: Microsoft-Windows-Kernel-Power The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. Log: 'System' Date/Time: 24/04/2018 12:51:12 AM Type: Critical Category: 63 Event: 41 Source: Microsoft-Windows-Kernel-Power The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. Log: 'System' Date/Time: 22/04/2018 11:28:51 PM Type: Critical Category: 63 Event: 41 Source: Microsoft-Windows-Kernel-Power The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. Log: 'System' Date/Time: 22/04/2018 1:45:46 AM Type: Critical Category: 63 Event: 41 Source: Microsoft-Windows-Kernel-Power The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 'System' Log - Error Type ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Log: 'System' Date/Time: 03/05/2018 9:23:58 PM Type: Error Category: 0 Event: 10016 Source: Microsoft-Windows-DistributedCOM The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. Log: 'System' Date/Time: 03/05/2018 9:13:58 PM Type: Error Category: 0 Event: 10016 Source: Microsoft-Windows-DistributedCOM The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. Log: 'System' Date/Time: 03/05/2018 9:03:51 PM Type: Error Category: 0 Event: 10016 Source: Microsoft-Windows-DistributedCOM The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. Log: 'System' Date/Time: 03/05/2018 9:00:49 PM Type: Error Category: 0 Event: 10016 Source: Microsoft-Windows-DistributedCOM The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user LAPTOP-COKEBKSL\Sam5776 SID (S-1-5-21-3750826685-671608555-4107877556-1001) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. Log: 'System' Date/Time: 03/05/2018 8:59:06 PM Type: Error Category: 0 Event: 10016 Source: Microsoft-Windows-DistributedCOM The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. Log: 'System' Date/Time: 03/05/2018 8:59:06 PM Type: Error Category: 0 Event: 10016 Source: Microsoft-Windows-DistributedCOM The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. Log: 'System' Date/Time: 03/05/2018 8:59:06 PM Type: Error Category: 0 Event: 10016 Source: Microsoft-Windows-DistributedCOM The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. Log: 'System' Date/Time: 03/05/2018 8:59:06 PM Type: Error Category: 0 Event: 10016 Source: Microsoft-Windows-DistributedCOM The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. Log: 'System' Date/Time: 03/05/2018 8:59:06 PM Type: Error Category: 0 Event: 10016 Source: Microsoft-Windows-DistributedCOM The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. Log: 'System' Date/Time: 03/05/2018 8:59:06 PM Type: Error Category: 0 Event: 10016 Source: Microsoft-Windows-DistributedCOM The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. Log: 'System' Date/Time: 03/05/2018 8:58:13 PM Type: Error Category: 0 Event: 16953 Source: Microsoft-Windows-Directory-Services-SAM The password notification DLL "C:\Program Files\TrueKey\McAfeeTrueKeyPasswordFilter" failed to load with error 126. Please verify that the notification DLL path defined in the registry, HKLM\System\CurrentControlSet\Control\Lsa\Notification Packages, refers to a correct and absolute path (:\\.) and not a relative or invalid path. If the DLL path is correct, please validate that any supporting files are located in the same directory, and that the system account has read access to both the DLL path and any supporting files. Contact the provider of the notification DLL for additional support. Further details can be found on the web at http://go.microsoft.com/fwlink/?LinkId=245898. Log: 'System' Date/Time: 03/05/2018 8:57:49 PM Type: Error Category: 0 Event: 46 Source: volmgr Crash dump initialization failed! Log: 'System' Date/Time: 03/05/2018 8:58:14 PM Type: Error Category: 0 Event: 6008 Source: EventLog The previous system shutdown at 3:57:07 PM on ?5/?3/?2018 was unexpected. Log: 'System' Date/Time: 03/05/2018 8:49:59 PM Type: Error Category: 0 Event: 16953 Source: Microsoft-Windows-Directory-Services-SAM The password notification DLL "C:\Program Files\TrueKey\McAfeeTrueKeyPasswordFilter" failed to load with error 126. Please verify that the notification DLL path defined in the registry, HKLM\System\CurrentControlSet\Control\Lsa\Notification Packages, refers to a correct and absolute path (:\\.) and not a relative or invalid path. If the DLL path is correct, please validate that any supporting files are located in the same directory, and that the system account has read access to both the DLL path and any supporting files. Contact the provider of the notification DLL for additional support. Further details can be found on the web at http://go.microsoft.com/fwlink/?LinkId=245898. Log: 'System' Date/Time: 03/05/2018 8:50:00 PM Type: Error Category: 0 Event: 6008 Source: EventLog The previous system shutdown at 3:47:01 PM on ?5/?3/?2018 was unexpected. Log: 'System' Date/Time: 03/05/2018 8:47:00 PM Type: Error Category: 0 Event: 16953 Source: Microsoft-Windows-Directory-Services-SAM The password notification DLL "C:\Program Files\TrueKey\McAfeeTrueKeyPasswordFilter" failed to load with error 126. Please verify that the notification DLL path defined in the registry, HKLM\System\CurrentControlSet\Control\Lsa\Notification Packages, refers to a correct and absolute path (:\\.) and not a relative or invalid path. If the DLL path is correct, please validate that any supporting files are located in the same directory, and that the system account has read access to both the DLL path and any supporting files. Contact the provider of the notification DLL for additional support. Further details can be found on the web at http://go.microsoft.com/fwlink/?LinkId=245898. Log: 'System' Date/Time: 03/05/2018 5:27:47 AM Type: Error Category: 0 Event: 10016 Source: Microsoft-Windows-DistributedCOM The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. Log: 'System' Date/Time: 03/05/2018 3:19:04 AM Type: Error Category: 0 Event: 10016 Source: Microsoft-Windows-DistributedCOM The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. Log: 'System' Date/Time: 03/05/2018 3:09:04 AM Type: Error Category: 0 Event: 10016 Source: Microsoft-Windows-DistributedCOM The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. Log: 'System' Date/Time: 03/05/2018 3:01:05 AM Type: Error Category: 0 Event: 7022 Source: Service Control Manager The Downloaded Maps Manager service hung on starting. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 'System' Log - Warning Type ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Log: 'System' Date/Time: 03/05/2018 9:00:05 PM Type: Warning Category: 0 Event: 15301 Source: Microsoft-Windows-HttpEvent SSL Certificate Settings created by an admin process for endpoint : 0.0.0.0:28380 . Log: 'System' Date/Time: 03/05/2018 9:00:04 PM Type: Warning Category: 0 Event: 15300 Source: Microsoft-Windows-HttpEvent SSL Certificate Settings deleted for endpoint : 0.0.0.0:28380 . Log: 'System' Date/Time: 03/05/2018 8:59:20 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: 03/05/2018 8:59:20 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: 03/05/2018 8:59:20 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: 03/05/2018 8:59:20 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: 03/05/2018 8:58:54 PM Type: Warning Category: 1014 Event: 1014 Source: Microsoft-Windows-DNS-Client Name resolution for the name wpad timed out after none of the configured DNS servers responded. Log: 'System' Date/Time: 03/05/2018 8:58:54 PM Type: Warning Category: 0 Event: 2 Source: HidBth Bluetooth HID device either went out of range or became unresponsive. Log: 'System' Date/Time: 03/05/2018 8:58:49 PM Type: Warning Category: 1014 Event: 1014 Source: Microsoft-Windows-DNS-Client Name resolution for the name wpad timed out after none of the configured DNS servers responded. Log: 'System' Date/Time: 03/05/2018 8:58:10 PM Type: Warning Category: 0 Event: 34 Source: BTHUSB The local adapter does not support an important Low Energy controller state to support peripheral mode. The minimum required supported state mask is 0x491f7fffff, got 0x1fffffff. Low Energy peripheral role functionality will not be available. Log: 'System' Date/Time: 03/05/2018 8:51:06 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: 03/05/2018 8:51:06 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: 03/05/2018 8:51:06 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: 03/05/2018 8:51:06 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: 03/05/2018 8:50:47 PM Type: Warning Category: 0 Event: 15301 Source: Microsoft-Windows-HttpEvent SSL Certificate Settings created by an admin process for endpoint : 0.0.0.0:28380 . Log: 'System' Date/Time: 03/05/2018 8:50:47 PM Type: Warning Category: 0 Event: 15300 Source: Microsoft-Windows-HttpEvent SSL Certificate Settings deleted for endpoint : 0.0.0.0:28380 . Log: 'System' Date/Time: 03/05/2018 8:50:39 PM Type: Warning Category: 0 Event: 2 Source: HidBth Bluetooth HID device either went out of range or became unresponsive. Log: 'System' Date/Time: 03/05/2018 8:49:57 PM Type: Warning Category: 0 Event: 34 Source: BTHUSB The local adapter does not support an important Low Energy controller state to support peripheral mode. The minimum required supported state mask is 0x491f7fffff, got 0x1fffffff. Low Energy peripheral role functionality will not be available. Log: 'System' Date/Time: 03/05/2018 8:49:55 PM Type: Warning Category: 212 Event: 219 Source: Microsoft-Windows-Kernel-PnP The driver \Driver\WUDFRd failed to load for the device {55BC022C-955B-4D87-A88D-D3E68CBEB2F4}\CT_27B961DB-3057-49BB-BD0D-ACA9FD8FF697\4&2e41a53b&0&38. Log: 'System' Date/Time: 03/05/2018 8:48:07 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.