Toko
Members-
Posts
12 -
Joined
-
Last visited
Reputation
0 NeutralRecent Profile Visitors
The recent visitors block is disabled and is not being shown to other users.
-
Taskbar icons keeps refreshing randomly
Toko replied to Toko's topic in Resolved Malware Removal Logs
Okay then, thank you so much for your help. -
Toko started following AdvancedSetup
-
Taskbar icons keeps refreshing randomly
Toko replied to Toko's topic in Resolved Malware Removal Logs
Still nothing Fixlog.txt -
Taskbar icons keeps refreshing randomly
Toko replied to Toko's topic in Resolved Malware Removal Logs
Fixlog.txt -
Taskbar icons keeps refreshing randomly
Toko replied to Toko's topic in Resolved Malware Removal Logs
Still the same thing.... Thanks for your reply. -
Taskbar icons keeps refreshing randomly
Toko replied to Toko's topic in Resolved Malware Removal Logs
Fixlog.txt -
Taskbar icons keeps refreshing randomly
Toko replied to Toko's topic in Resolved Malware Removal Logs
Report MB 1.txt AdwCleaner[C00].txt FRST.txt Addition.txt -
Hello, Every so often the desktop and taskbar will refresh, it happens randomly anytime. Addition.txt FRST.txt
-
Vino's Event Viewer v01c run on Windows 2008 in English Report run at 20/01/2018 2:58:26 Note: All dates below are in the format dd/mm/yyyy ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 'Application' Log - Critical Type ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 'Application' Log - Error Type ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Log: 'Application' Date/Time: 19/01/2018 21:33:55 Type: Error Category: 0 Event: 10 Source: Microsoft-Windows-WMI Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected. Log: 'Application' Date/Time: 19/01/2018 20:28:47 Type: Error Category: 0 Event: 10 Source: Microsoft-Windows-WMI Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected. Log: 'Application' Date/Time: 19/01/2018 20:07:07 Type: Error Category: 0 Event: 10 Source: Microsoft-Windows-WMI Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected. Log: 'Application' Date/Time: 19/01/2018 20:02:42 Type: Error Category: 0 Event: 10 Source: Microsoft-Windows-WMI Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected. Log: 'Application' Date/Time: 19/01/2018 19:38:15 Type: Error Category: 0 Event: 10 Source: Microsoft-Windows-WMI Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected. Log: 'Application' Date/Time: 19/01/2018 19:24:53 Type: Error Category: 0 Event: 10 Source: Microsoft-Windows-WMI Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected. Log: 'Application' Date/Time: 19/01/2018 19:01:37 Type: Error Category: 0 Event: 10 Source: Microsoft-Windows-WMI Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected. Log: 'Application' Date/Time: 19/01/2018 13:53:53 Type: Error Category: 0 Event: 10 Source: Microsoft-Windows-WMI Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected. Log: 'Application' Date/Time: 19/01/2018 13:14:50 Type: Error Category: 0 Event: 10 Source: Microsoft-Windows-WMI Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected. Log: 'Application' Date/Time: 19/01/2018 13:05:55 Type: Error Category: 0 Event: 10 Source: Microsoft-Windows-WMI Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected. Log: 'Application' Date/Time: 19/01/2018 13:02:38 Type: Error Category: 0 Event: 10 Source: Microsoft-Windows-WMI Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected. Log: 'Application' Date/Time: 19/01/2018 3:15:44 Type: Error Category: 0 Event: 10 Source: Microsoft-Windows-WMI Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected. Log: 'Application' Date/Time: 18/01/2018 21:34:54 Type: Error Category: 0 Event: 10 Source: Microsoft-Windows-WMI Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected. Log: 'Application' Date/Time: 18/01/2018 1:04:19 Type: Error Category: 0 Event: 10 Source: Microsoft-Windows-WMI Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected. Log: 'Application' Date/Time: 18/01/2018 0:36:22 Type: Error Category: 0 Event: 10 Source: Microsoft-Windows-WMI Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 'System' Log - Critical Type ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Log: 'System' Date/Time: 19/01/2018 21:32:08 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/01/2018 21:23:35 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/01/2018 20:26:54 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/01/2018 20:05: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: 19/01/2018 20:00: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: 19/01/2018 19:36:21 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/01/2018 19:23:00 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/01/2018 18:59: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: 19/01/2018 3:13:51 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/01/2018 1:02: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: 18/01/2018 0:34: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: 17/01/2018 21:25:46 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: 17/01/2018 21:09: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: 16/01/2018 1:33:11 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/01/2018 1:21: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. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 'System' Log - Error Type ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Log: 'System' Date/Time: 19/01/2018 21:57:36 Type: Error Category: 0 Event: 36887 Source: Schannel The following fatal alert was received: 70. Log: 'System' Date/Time: 19/01/2018 21:57:36 Type: Error Category: 0 Event: 36887 Source: Schannel The following fatal alert was received: 70. Log: 'System' Date/Time: 19/01/2018 21:23:41 Type: Error Category: 0 Event: 6008 Source: EventLog The previous system shutdown at 1:22:54 AM on ?1/?20/?2018 was unexpected. Log: 'System' Date/Time: 19/01/2018 20:26:59 Type: Error Category: 0 Event: 6008 Source: EventLog The previous system shutdown at 12:25:14 AM on ?1/?20/?2018 was unexpected. Log: 'System' Date/Time: 19/01/2018 20:05:19 Type: Error Category: 0 Event: 6008 Source: EventLog The previous system shutdown at 12:03:48 AM on ?1/?20/?2018 was unexpected. Log: 'System' Date/Time: 19/01/2018 20:00:54 Type: Error Category: 0 Event: 6008 Source: EventLog The previous system shutdown at 11:59:21 PM on ?1/?19/?2018 was unexpected. Log: 'System' Date/Time: 19/01/2018 19:36:29 Type: Error Category: 0 Event: 6008 Source: EventLog The previous system shutdown at 11:35:00 PM on ?1/?19/?2018 was unexpected. Log: 'System' Date/Time: 19/01/2018 19:23:07 Type: Error Category: 0 Event: 6008 Source: EventLog The previous system shutdown at 11:21:45 PM on ?1/?19/?2018 was unexpected. Log: 'System' Date/Time: 19/01/2018 18:59:53 Type: Error Category: 0 Event: 6008 Source: EventLog The previous system shutdown at 10:58:24 PM on ?1/?19/?2018 was unexpected. Log: 'System' Date/Time: 19/01/2018 14:31:17 Type: Error Category: 0 Event: 36887 Source: Schannel The following fatal alert was received: 70. Log: 'System' Date/Time: 19/01/2018 14:31:17 Type: Error Category: 0 Event: 36887 Source: Schannel The following fatal alert was received: 70. Log: 'System' Date/Time: 19/01/2018 13:51:20 Type: Error Category: 0 Event: 10010 Source: Microsoft-Windows-DistributedCOM The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. Log: 'System' Date/Time: 19/01/2018 3:13:55 Type: Error Category: 0 Event: 6008 Source: EventLog The previous system shutdown at 7:12:59 AM on ?1/?19/?2018 was unexpected. Log: 'System' Date/Time: 18/01/2018 1:02:31 Type: Error Category: 0 Event: 6008 Source: EventLog The previous system shutdown at 5:00:29 AM on ?1/?18/?2018 was unexpected. Log: 'System' Date/Time: 18/01/2018 0:34:34 Type: Error Category: 0 Event: 6008 Source: EventLog The previous system shutdown at 4:32:52 AM on ?1/?18/?2018 was unexpected.
-
Okay sorry about that. Malwarebytes www.malwarebytes.com -Log Details- Scan Date: 1/20/18 Scan Time: 1:48 AM Log File: 7e0e5bce-fd62-11e7-bafe-00252246b7e5.json Administrator: Yes -Software Information- Version: 3.3.1.2183 Components Version: 1.0.262 Update Package Version: 1.0.3735 License: Trial -System Information- OS: Windows 7 Service Pack 1 CPU: x64 File System: NTFS User: User-PC\User -Scan Summary- Scan Type: Threat Scan Result: Completed Objects Scanned: 223716 Threats Detected: 0 (No malicious items detected) Threats Quarantined: 0 (No malicious items detected) Time Elapsed: 5 min, 29 sec -Scan Options- Memory: Enabled Startup: Enabled Filesystem: Enabled Archives: Enabled Rootkits: Enabled Heuristics: Enabled PUP: Detect PUM: Detect -Scan Details- Process: 0 (No malicious items detected) Module: 0 (No malicious items detected) Registry Key: 0 (No malicious items detected) Registry Value: 0 (No malicious items detected) Registry Data: 0 (No malicious items detected) Data Stream: 0 (No malicious items detected) Folder: 0 (No malicious items detected) File: 0 (No malicious items detected) Physical Sector: 0 (No malicious items detected) (end) # AdwCleaner 7.0.7.0 - Logfile created on Fri Jan 19 21:57:37 2018 # Updated on 2018/18/01 by Malwarebytes # Database: 01-16-2018.1 # Running on Windows 7 Home Premium (X64) # Mode: scan # Support: https://www.malwarebytes.com/support ***** [ Services ] ***** No malicious services found. ***** [ Folders ] ***** No malicious folders found. ***** [ Files ] ***** No malicious files found. ***** [ DLL ] ***** No malicious DLLs found. ***** [ WMI ] ***** No malicious WMI found. ***** [ Shortcuts ] ***** No malicious shortcuts found. ***** [ Tasks ] ***** No malicious tasks found. ***** [ Registry ] ***** No malicious registry entries found. ***** [ Firefox (and derivatives) ] ***** No malicious Firefox entries. ***** [ Chromium (and derivatives) ] ***** No malicious Chromium entries. ************************* ########## EOF - C:\AdwCleaner\AdwCleaner[S0].txt ########## ------------------------------------- Microsoft Windows Malicious Software Removal Tool v5.56, January 2018 (build 5.56.14443.1) Started On Sat Jan 20 01:59:03 2018 Engine: 1.1.14405.2 Signatures: 1.259.631.0 Run Mode: Interactive Graphical Mode Results Summary: ---------------- No infection found. Microsoft Windows Malicious Software Removal Tool Finished On Sat Jan 20 02:01:36 2018 Return code: 0 (0x0)
-
There we go. https://mega.nz/#!DwlSHKSa!nguXyC80dAEpBYAawculeEneADLkFGe7eKOA0vhYDNQ https://mega.nz/#!fh8w3ZhJ!oxg3hqQUHoHusLocF8OwDfmh-YarI7bq4OZfLPnPELY https://mega.nz/#!GxMVhLhB!CwDFqWU_og06Jfm_sKaMg6wGQsnMv5mEgtA-6TqlSKc
-
Yes ofc i trust them. The Georgia Tbilisi Magticom Ltd are an Internet Service Provider.
-
Hello there, sometimes pc freezes and after that i have to restart the computer. There is not any of the Blue Screen of Death. Addition.txt FRST.txt