Zurück   Trojaner-Board > Malware entfernen > Plagegeister aller Art und deren Bekämpfung

Plagegeister aller Art und deren Bekämpfung: Broken.OpenCommand Virus gefunden-Rechner ist extrem langsam geworden

Windows 7 Wenn Du nicht sicher bist, ob Du dir Malware oder Trojaner eingefangen hast, erstelle hier ein Thema. Ein Experte wird sich mit weiteren Anweisungen melden und Dir helfen die Malware zu entfernen oder Unerwünschte Software zu deinstallieren bzw. zu löschen. Bitte schildere dein Problem so genau wie möglich. Sollte es ein Trojaner oder Viren Problem sein wird ein Experte Dir bei der Beseitigug der Infektion helfen.

 
Alt 11.07.2014, 17:21   #29
funcopter
 
Broken.OpenCommand Virus gefunden-Rechner ist extrem langsam geworden - Standard

Broken.OpenCommand Virus gefunden-Rechner ist extrem langsam geworden



Hallo Schrauber,

das Seatool hat nicht funktioniert.
Ich habe mir das GSmartControl runtergeladen und drüber laufen lassen.
Ich hoffe das war jetzt nicht falsch.
Die erste Festplatte hat 1760 Fehler im Laufe von 12244 Betriebsstunden gezählt und die zweite 61246 im Laufe von 54096 Stunden.
Ob ein aktueller Fehler da drauf ist kann ich aus derm Log nicht sehen.
Vielleicht siehst Du da ja was.
Hier die zugehörigen Logs:

Gruß
Funcopter
Complete error log:

SMART Error Log Version: 1
ATA Error Count: 1760 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 1760 occurred at disk power-on lifetime: 12244 hours (510 days + 4 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
84 51 00 5f 00 00 e0 Error: ICRC, ABRT at LBA = 0x0000005f = 95

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c8 00 7f 5f 00 00 e0 00 00:01:34.647 READ DMA
c8 00 7f 5f 00 00 e0 00 00:01:34.194 READ DMA
10 00 ff 00 00 00 e0 00 00:01:34.194 RECALIBRATE [OBS-4]
c8 00 7f 5f 00 00 e0 00 00:01:33.759 READ DMA
c8 00 7f 5f 00 00 e0 00 00:01:33.264 READ DMA

Error 1759 occurred at disk power-on lifetime: 12244 hours (510 days + 4 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
84 51 00 5f 00 00 e0 Error: ICRC, ABRT at LBA = 0x0000005f = 95

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c8 00 7f 5f 00 00 e0 00 00:01:34.194 READ DMA
10 00 ff 00 00 00 e0 00 00:01:34.194 RECALIBRATE [OBS-4]
c8 00 7f 5f 00 00 e0 00 00:01:33.759 READ DMA
c8 00 7f 5f 00 00 e0 00 00:01:33.264 READ DMA
c8 00 01 3f 00 00 e0 00 00:01:33.263 READ DMA

Error 1758 occurred at disk power-on lifetime: 12244 hours (510 days + 4 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
84 51 00 5f 00 00 e0 Error: ICRC, ABRT at LBA = 0x0000005f = 95

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c8 00 7f 5f 00 00 e0 00 00:01:33.759 READ DMA
c8 00 7f 5f 00 00 e0 00 00:01:33.264 READ DMA
c8 00 01 3f 00 00 e0 00 00:01:33.263 READ DMA
c8 00 01 25 0d cb e2 00 00:01:32.545 READ DMA
c8 00 01 00 00 00 e0 00 00:01:32.545 READ DMA

Error 1757 occurred at disk power-on lifetime: 12244 hours (510 days + 4 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
84 51 00 5f 00 00 e0 Error: ICRC, ABRT at LBA = 0x0000005f = 95

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c8 00 7f 5f 00 00 e0 00 00:01:33.264 READ DMA
c8 00 01 3f 00 00 e0 00 00:01:33.263 READ DMA
c8 00 01 25 0d cb e2 00 00:01:32.545 READ DMA
c8 00 01 00 00 00 e0 00 00:01:32.545 READ DMA
c8 00 01 00 00 00 e0 00 00:01:32.545 READ DMA

Error 1756 occurred at disk power-on lifetime: 7622 hours (317 days + 14 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
84 51 00 c7 00 00 e0 Error: ICRC, ABRT at LBA = 0x000000c7 = 199

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c8 00 08 c7 00 00 e0 00 00:00:32.113 READ DMA
c8 00 08 bf 00 00 e0 00 00:00:32.113 READ DMA
c8 00 08 b7 00 00 e0 00 00:00:32.113 READ DMA
c8 00 08 af 00 00 e0 00 00:00:32.112 READ DMA
c8 00 08 a7 00 00 e0 00 00:00:32.112 READ DMA


Complete error log:

SMART Error Log Version: 1
Warning: ATA error count 61246 inconsistent with error log pointer 5
ATA Error Count: 61246 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 61246 occurred at disk power-on lifetime: 54096 hours (2254 days + 0 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
04 51 01 01 00 00 a0 Error: ABRT

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
a1 00 01 01 00 00 a0 00 35d+17:42:08.640 IDENTIFY PACKET DEVICE
c8 00 08 77 a5 34 e1 00 29d+16:53:44.320 READ DMA
08 00 01 01 00 00 a0 00 35d+17:42:08.640 DEVICE RESET
00 00 01 01 00 00 00 00 40d+09:28:39.680 NOP [Abort queued commands]
e0 00 00 00 00 00 a0 00 29d+16:53:44.320 STANDBY IMMEDIATE

Error 61245 occurred at disk power-on lifetime: 54096 hours (2254 days + 0 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
04 51 01 01 00 00 a0

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
08 00 01 01 00 00 a0 00 35d+17:42:08.640 DEVICE RESET
00 00 01 01 00 00 00 00 40d+09:28:39.680 NOP [Abort queued commands]
e0 00 00 00 00 00 a0 00 29d+16:53:44.320 STANDBY IMMEDIATE
c8 00 40 91 a7 2c e1 00 29d+16:53:44.320 READ DMA
c8 00 08 77 a5 34 e1 00 29d+16:53:44.320 READ DMA

Error 61244 occurred at disk power-on lifetime: 53584 hours (2232 days + 16 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
04 51 01 01 00 00 a0 Error: ABRT

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
a1 00 01 01 00 00 a0 00 35d+17:42:08.640 IDENTIFY PACKET DEVICE
c8 00 08 47 31 e3 e0 00 34d+08:01:57.760 READ DMA
08 00 01 01 00 00 a0 00 35d+17:42:08.640 DEVICE RESET
00 00 01 01 00 00 00 00 40d+09:28:39.680 NOP [Abort queued commands]
e0 00 00 00 00 00 a0 00 34d+08:01:57.760 STANDBY IMMEDIATE

Error 61243 occurred at disk power-on lifetime: 53584 hours (2232 days + 16 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
04 51 01 01 00 00 a0

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
08 00 01 01 00 00 a0 00 35d+17:42:08.640 DEVICE RESET
00 00 01 01 00 00 00 00 40d+09:28:39.680 NOP [Abort queued commands]
e0 00 00 00 00 00 a0 00 34d+08:01:57.760 STANDBY IMMEDIATE
c8 00 08 97 36 8f e0 00 34d+08:01:57.760 READ DMA
c8 00 08 47 31 e3 e0 00 34d+08:01:57.760 READ DMA

Error 61242 occurred at disk power-on lifetime: 53072 hours (2211 days + 8 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
04 51 01 01 00 00 a0 Error: ABRT

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
a1 00 01 01 00 00 a0 00 35d+17:42:08.640 IDENTIFY PACKET DEVICE
08 00 01 01 00 00 a0 00 35d+17:42:08.640 DEVICE RESET
00 00 01 01 00 00 00 00 40d+09:28:39.680 NOP [Abort queued commands]
e0 00 00 00 00 00 a0 00 48d+03:54:28.480 STANDBY IMMEDIATE
c8 00 08 af 40 00 e1 00 48d+03:54:28.480 READ DMA

 

Themen zu Broken.OpenCommand Virus gefunden-Rechner ist extrem langsam geworden
brauche, broken.opencommand, dauert, eingefangen, gefangen, gelöscht, geschwindigkeit, glaskugel, langsam, malwarebytes, permanent, plagegeist, problem, pup.optional.babylon.a, quarantäne, rechner, schonmal, verschiebt, virus, win32/toolbar.conduit




Ähnliche Themen: Broken.OpenCommand Virus gefunden-Rechner ist extrem langsam geworden


  1. Broken.OpenCommand
    Plagegeister aller Art und deren Bekämpfung - 12.05.2015 (32)
  2. Mein Pc ist plötzlich extrem Langsam geworden!
    Alles rund um Windows - 17.02.2015 (7)
  3. Virus? Internetabbrüche, rechner extrem langsam windows8.1
    Plagegeister aller Art und deren Bekämpfung - 25.11.2014 (3)
  4. Alter Vista Laptop ist extrem Langsam geworden
    Plagegeister aller Art und deren Bekämpfung - 17.10.2014 (3)
  5. Internet extrem langsam geworden
    Plagegeister aller Art und deren Bekämpfung - 04.01.2014 (9)
  6. HKCR\regfile\shell\open\command| (Broken.OpenCommand)
    Plagegeister aller Art und deren Bekämpfung - 08.11.2012 (2)
  7. Broken.OpenCommand: Keine Wiederherstellungspunkte, löschen einiger Dateien nicht möglich.
    Log-Analyse und Auswertung - 06.06.2012 (15)
  8. PC auf einmal extrem langsam geworden
    Plagegeister aller Art und deren Bekämpfung - 17.05.2012 (1)
  9. Broken.OpenCommand Virus
    Plagegeister aller Art und deren Bekämpfung - 29.03.2012 (37)
  10. Broken.OpenCommand Malwarebytes fund
    Log-Analyse und Auswertung - 08.02.2012 (8)
  11. Laptop plötzlich sehr langsam, vor allem Video Streams, MBAW meldet broken.opencommand
    Log-Analyse und Auswertung - 24.11.2011 (25)
  12. Pc über Nacht extrem langsam geworden
    Log-Analyse und Auswertung - 24.10.2010 (4)
  13. Internet extrem langsam geworden
    Log-Analyse und Auswertung - 27.08.2010 (5)
  14. Notebook extrem langsam geworden
    Plagegeister aller Art und deren Bekämpfung - 29.03.2010 (0)
  15. Sound verzerrt, Rechner extrem langsam: Virus???
    Log-Analyse und Auswertung - 17.05.2009 (0)
  16. PC extrem langsam geworden (seit 1woche)
    Log-Analyse und Auswertung - 07.11.2008 (14)
  17. Bitte HJT Log-File überprüfen; PC ist extrem langsam geworden!!!
    Log-Analyse und Auswertung - 12.09.2007 (4)

Zum Thema Broken.OpenCommand Virus gefunden-Rechner ist extrem langsam geworden - Hallo Schrauber, das Seatool hat nicht funktioniert. Ich habe mir das GSmartControl runtergeladen und drüber laufen lassen. Ich hoffe das war jetzt nicht falsch. Die erste Festplatte hat 1760 Fehler - Broken.OpenCommand Virus gefunden-Rechner ist extrem langsam geworden...

Alle Zeitangaben in WEZ +1. Es ist jetzt 21:36 Uhr.


Copyright ©2000-2025, Trojaner-Board
Archiv
Du betrachtest: Broken.OpenCommand Virus gefunden-Rechner ist extrem langsam geworden auf Trojaner-Board

Search Engine Optimization by vBSEO ©2011, Crawlability, Inc.