PC très lent et blue screen

routman54 · le 17 Sep 2011 21:08

Bonsoir,
J'ai un jeune voisin qui a un Compaq CQ 5109 FR / VC889 AA-ABF qui est vraiment très lent et qui fait des blues screen dès que l'on essaie de tèlècharger ou rester trop longtemps sur le Net .
Je l'ai mis en dèmarrage sèlectif , mais je ne gagne pas grand choses , et bien sur j'ai pensè virus.
J'ai passè Rogue Killer :

Code: Tout sélectionner: RogueKiller V5.3.4 [30/08/2011] par Tigzy contact sur http://www.sur-la-toile.com mail: tigzyRK<at>gmail<dot>com Remontees: http://www.sur-la-toile.com/discussion-193725-1-BRogueKillerD-Remontees.html Systeme d'exploitation: Windows Vista (6.0.6002 Service Pack 2) 32 bits version Demarrage : Mode normal Utilisateur: pc [Droits d'admin] Mode: Recherche -- Date : 17/09/2011 14:18:50 Processus malicieux: 1 [SUSP PATH] autoupdater.exe -- c:\users\pc\appdata\roaming\pctuto\updatepctuto\autoupdater.exe -> KILLED [TermProc] Entrees de registre: 5 [SUSP PATH] HKLM\[...]\RunOnce : autoupdater (C:\Users\pc\AppData\Roaming\PCtuto\UpdatePCTuto\autoupdater.exe -runonce) -> FOUND [HJ] HKLM\[...]\NewStartPanel : {59031a47-3f72-44a7-89c5-5595fe6b30ee} (1) -> FOUND [HJ] HKLM\[...]\NewStartPanel : {20D04FE0-3AEA-1069-A2D8-08002B30309D} (1) -> FOUND [HJ] HKCU\[...]\ClassicStartMenu : {645FF040-5081-101B-9F08-00AA002F954E} (1) -> FOUND [HJ] HKCU\[...]\NewStartPanel : {645FF040-5081-101B-9F08-00AA002F954E} (1) -> FOUND Fichiers / Dossiers particuliers: [FOLDER] plugs : c:\users\pc\appdata\roaming\adobe\plugs --> FOUND Fichier HOSTS: 127.0.0.1 localhost ::1 localhost Termine : << RKreport[1].txt >> RKreport[1].txt

suite :

Code: Tout sélectionner: RogueKiller V5.3.4 [30/08/2011] par Tigzy contact sur http://www.sur-la-toile.com mail: tigzyRK<at>gmail<dot>com Remontees: http://www.sur-la-toile.com/discussion-193725-1-BRogueKillerD-Remontees.html Systeme d'exploitation: Windows Vista (6.0.6002 Service Pack 2) 32 bits version Demarrage : Mode normal Utilisateur: pc [Droits d'admin] Mode: Suppression -- Date : 17/09/2011 14:19:48 Processus malicieux: 0 Entrees de registre: 5 [SUSP PATH] HKLM\[...]\RunOnce : autoupdater (C:\Users\pc\AppData\Roaming\PCtuto\UpdatePCTuto\autoupdater.exe -runonce) -> DELETED [HJ] HKLM\[...]\NewStartPanel : {59031a47-3f72-44a7-89c5-5595fe6b30ee} (1) -> REPLACED (0) [HJ] HKLM\[...]\NewStartPanel : {20D04FE0-3AEA-1069-A2D8-08002B30309D} (1) -> REPLACED (0) [HJ] HKCU\[...]\ClassicStartMenu : {645FF040-5081-101B-9F08-00AA002F954E} (1) -> REPLACED (0) [HJ] HKCU\[...]\NewStartPanel : {645FF040-5081-101B-9F08-00AA002F954E} (1) -> REPLACED (0) Fichiers / Dossiers particuliers: [FILE] KB1242364038.exe : c:\users\pc\appdata\roaming\adobe\plugs\KB1242364038.exe --> REMOVED [FOLDER] plugs : c:\users\pc\appdata\roaming\adobe\plugs --> REMOVED Fichier HOSTS: 127.0.0.1 localhost ::1 localhost Termine : << RKreport[2].txt >> RKreport[1].txt ; RKreport[2].txt

.
Ensuite je lui ai passè un coup de MBAM qui m'a trouvè 72 éléments infectieux , mis en quarantaine . Je n'ai malheureusement pas rèussi a vous mettre le rapport mis sur ma clè en Woks et moi je ne l'ai pas et je n'ai pas rèussi à le transformer. Pareit pour Wocrashed qui m'a trouvè près de 80 blue screen mais bizarement les dèfaillances ne sont pratiquement jamais les mêmes.Je suis assez limitè car je télécharge les utilitaires sur une clè et je vais chez lui , alors si je pouvais au moins rètablir correctement le Net ce serait le pied et j'opèrerai directement depuis son ordinateur.
Chose un peu bizzare aussi quand il fait des jeux en ligne ça ne coupe pas ?
J'ai aussi à ma disposition un CD de Reagato XPE mais son ordi est sous Vista et l'OTL du CD n'a pas voulu passer.
En vous remerciant par avance.
Dany

Skynet · le 18 Sep 2011 06:21

Bonjour!

Ouff les BSOD, ce n'est pas joli. Les virus peuvent les causer, mais comme ce PC est vieux, s'il m'était donné de le vérifier personnellement, je commencerais par un test du CPU, de la mémoire et du disque dur étant donné que ce n'est pas très long et que ça règle beaucoup de questions si on constate des défectuosités. Pour le processeur et la mémoire, l'UBCD est parfait car il contient CPU Burn In et Memtest. Pour le disque dur, comme Windows démarre, HDTunes peut te montrer l'état SMART du disque dur. Comment utiliser ces outils est bien expliqué en images à ce lien : http://****

Sinon si le problème est uniquement lié à l'infection au virus, personnellement sur de nombreuses années, l'outil qui s'est avéré être efficace en toute circonstance est Kaspersky Rescue Disk, car son taux de détection est excellent et puisqu'il travaille tandis que Windows est arrêté, les virus ne peuvent résister ou se cacher.
http://support.kaspersky.com/viruses/rescuedisk
http://****

Laissez-moi savoir si trouvez quelque chose ou si la situation s'améliore.

routman54 · le 18 Sep 2011 09:27

Bonjour,
Merci de te pencher sur ce cas . pour les tes : Rams , HDD, CPU , l'utilitaire de HP ne trouve rien . c'est pour celà que je soupconne un virus quelconque bien planquè.
J'ai tèlèchargè Kapersky rescue disk ainsi que removal tools 2011 et dès que j'ai un instant je retourne chez lui voir. Mais le dimanche comme tout le monde on a plein de choses à faire et des invitès de surcroit..
Je te tiens au courant et j'essaie dee repiquer mes rapports loupès.
A ++++

bernard53 · le 18 Sep 2011 10:55

Bonjour a tous

Les blues screen même avec un pc âgé peuvent être causés par des virus.

J'ai aussi à ma disposition un CD de Reagato XPE mais son ordi est sous Vista

Il est compatible Vista mais de cette façon.

Code: Tout sélectionner: ** si le systeme d'exploitation est Vista ou Seven tu peux avoir ce message : "RunScanner Error - Target is not windows 2000 or later", il faut donc aller et sélectionner jusqu'au dossier c:\windows dans l'arborescence en dessous de local disk (c:)

N'hésite pas à mettre le rapport.

routman54 · le 18 Sep 2011 11:12

Bonjour bernard,
Je suis allè rècupèrerWocrashed :

Code: Tout sélectionner: System Information (local) computer name: PC-DE-PC windows version: Windows Vista Service Pack 2, 6.0, build: 6002 windows dir: C:\Windows CPU: AuthenticAMD AMD Sempron(tm) Processor LE-1250 AMD586, level: 15 1 logical processors, active mask: 1 RAM: 2010923008 total VM: 2147352576, free: 1951723520 Crash Dump Analysis Crash dump directory: C:\Windows\Minidump Crash dumps are enabled on your computer. On Sun 18/09/2011 06:23:40 GMT your computer crashed crash dump file: C:\Windows\Minidump\Mini091811-01.dmp This was probably caused by the following module: usbport.sys (USBPORT+0x1025) Bugcheck code: 0xFE (0x6, 0xFFFFFFFF8DDF19B8, 0x66725045, 0x0) Error: BUGCODE_USB_DRIVER file path: C:\Windows\system32\drivers\usbport.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: USB 1.1 & 2.0 Port Driver Bug check description: This indicates that an error has occurred in a Universal Serial Bus (USB) driver. The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time. On Sun 18/09/2011 06:23:40 GMT your computer crashed crash dump file: C:\Windows\memory.dmp This was probably caused by the following module: usbport.sys (USBPORT+0x1025) Bugcheck code: 0xFE (0x6, 0xFFFFFFFF8DDF19B8, 0x66725045, 0x0) Error: BUGCODE_USB_DRIVER file path: C:\Windows\system32\drivers\usbport.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: USB 1.1 & 2.0 Port Driver Bug check description: This indicates that an error has occurred in a Universal Serial Bus (USB) driver. The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time. On Sat 17/09/2011 18:10:59 GMT your computer crashed crash dump file: C:\Windows\Minidump\Mini091711-23.dmp This was probably caused by the following module: ntfs.sys (Ntfs+0x19FFF) Bugcheck code: 0x24 (0x1904AA, 0xFFFFFFFFA05FD5C8, 0xFFFFFFFFA05FD2C4, 0xFFFFFFFF82CBC917) Error: NTFS_FILE_SYSTEM file path: C:\Windows\system32\drivers\ntfs.sys product: Système d'exploitation Microsoft® Windows® company: Microsoft Corporation description: Pilote du système de fichiers NT Bug check description: This indicates a problem occurred in the NTFS file system. The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time. On Sat 17/09/2011 16:23:02 GMT your computer crashed crash dump file: C:\Windows\Minidump\Mini091711-22.dmp This was probably caused by the following module: ntkrnlpa.exe (nt+0x98379) Bugcheck code: 0xBE (0xFFFFFFFF9C159D16, 0x52E4121, 0xFFFFFFFF88F1BC4C, 0xA) Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY file path: C:\Windows\system32\ntkrnlpa.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This is issued if a driver attempts to write to a read-only memory segment. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. On Sat 17/09/2011 14:54:20 GMT your computer crashed crash dump file: C:\Windows\Minidump\Mini091711-21.dmp This was probably caused by the following module: aswtdi.sys (aswTdi+0xA51) Bugcheck code: 0x19 (0x20, 0xFFFFFFFF8D7D3950, 0xFFFFFFFF8D7D41C0, 0x90ED6C5) Error: BAD_POOL_HEADER file path: C:\Windows\system32\drivers\aswtdi.sys product: avast! Antivirus System company: AVAST Software description: avast! TDI Filter Driver Bug check description: This indicates that a pool header is corrupt. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: aswtdi.sys (avast! TDI Filter Driver, AVAST Software). Google query: aswtdi.sys AVAST Software BAD_POOL_HEADER On Sat 17/09/2011 14:51:18 GMT your computer crashed crash dump file: C:\Windows\Minidump\Mini091711-20.dmp This was probably caused by the following module: aswsp.sys (aswSP+0xD239) Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFFFFF82E24C37, 0xFFFFFFFF8A87B92C, 0xFFFFFFFF8A87B628) Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M file path: C:\Windows\system32\drivers\aswsp.sys product: avast! Antivirus System company: AVAST Software description: avast! self protection module Bug check description: This indicates that a system thread generated an exception which the error handler did not catch. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: aswsp.sys (avast! self protection module, AVAST Software). Google query: aswsp.sys AVAST Software SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M On Sat 17/09/2011 14:22:36 GMT your computer crashed crash dump file: C:\Windows\Minidump\Mini091711-19.dmp This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x2DC1D1) Bugcheck code: 0xD1 (0xFFFFFFFFE5744086, 0x8, 0x8, 0xFFFFFFFFE5744086) Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL file path: C:\Windows\system32\drivers\nvlddmkm.sys product: NVIDIA Compatible Windows Vista Kernel Mode Driver, Version 182.14 company: NVIDIA Corporation description: NVIDIA Compatible Windows Vista Kernel Mode Driver, Version 182.14 Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Compatible Windows Vista Kernel Mode Driver, Version 182.14 , NVIDIA Corporation). Google query: nvlddmkm.sys NVIDIA Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL On Sat 17/09/2011 14:19:03 GMT your computer crashed crash dump file: C:\Windows\Minidump\Mini091711-18.dmp This was probably caused by the following module: ntkrnlpa.exe (nt+0xB25BF) Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82CC55BF, 0xFFFFFFFFA307975C, 0x0) Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M file path: C:\Windows\system32\ntkrnlpa.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. On Sat 17/09/2011 14:12:08 GMT your computer crashed crash dump file: C:\Windows\Minidump\Mini091711-17.dmp This was probably caused by the following module: fltmgr.sys (fltmgr+0x9385) Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82CBD90D, 0xFFFFFFFF81A7D848, 0x0) Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M file path: C:\Windows\system32\drivers\fltmgr.sys product: Système d'exploitation Microsoft® Windows® company: Microsoft Corporation description: Gestionnaire de filtres de système de fichiers Microsoft Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time. On Sat 17/09/2011 13:36:16 GMT your computer crashed crash dump file: C:\Windows\Minidump\Mini091711-16.dmp This was probably caused by the following module: classpnp.sys (CLASSPNP+0x47F2) Bugcheck code: 0xD1 (0x28A8A83, 0x2, 0x8, 0x28A8A83) Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL file path: C:\Windows\system32\drivers\classpnp.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: SCSI Class System Dll Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time. On Sat 17/09/2011 13:31:47 GMT your computer crashed crash dump file: C:\Windows\Minidump\Mini091711-15.dmp This was probably caused by the following module: hal.dll (hal+0x3FF9) Bugcheck code: 0xA (0xFFFFFFFFE6DD0DC4, 0x2, 0x1, 0xFFFFFFFF82FC5FF9) Error: IRQL_NOT_LESS_OR_EQUAL file path: C:\Windows\system32\hal.dll product: Microsoft® Windows® Operating System company: Microsoft Corporation description: Hardware Abstraction Layer DLL Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time. On Sat 17/09/2011 13:17:19 GMT your computer crashed crash dump file: C:\Windows\Minidump\Mini091711-14.dmp This was probably caused by the following module: ntfs.sys (Ntfs+0x7FF37) Bugcheck code: 0xA (0x67BB0846, 0x2, 0x0, 0xFFFFFFFF82C71114) Error: IRQL_NOT_LESS_OR_EQUAL file path: C:\Windows\system32\drivers\ntfs.sys product: Système d'exploitation Microsoft® Windows® company: Microsoft Corporation description: Pilote du système de fichiers NT Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time. On Sat 17/09/2011 13:10:22 GMT your computer crashed crash dump file: C:\Windows\Minidump\Mini091711-13.dmp This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x2C4362) Bugcheck code: 0x50 (0xFFFFFFFFE74FD06F, 0x0, 0xFFFFFFFF8C2C8362, 0x2) Error: PAGE_FAULT_IN_NONPAGED_AREA file path: C:\Windows\system32\drivers\nvlddmkm.sys product: NVIDIA Compatible Windows Vista Kernel Mode Driver, Version 182.14 company: NVIDIA Corporation description: NVIDIA Compatible Windows Vista Kernel Mode Driver, Version 182.14 Bug check description: This indicates that invalid system memory has been referenced. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Compatible Windows Vista Kernel Mode Driver, Version 182.14 , NVIDIA Corporation). Google query: nvlddmkm.sys NVIDIA Corporation PAGE_FAULT_IN_NONPAGED_AREA On Sat 17/09/2011 12:57:43 GMT your computer crashed crash dump file: C:\Windows\Minidump\Mini091711-12.dmp This was probably caused by the following module: aswsp.sys (aswSP+0x811D) Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82E48D5C, 0xFFFFFFFFAC3DA960, 0x0) Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M file path: C:\Windows\system32\drivers\aswsp.sys product: avast! Antivirus System company: AVAST Software description: avast! self protection module Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: aswsp.sys (avast! self protection module, AVAST Software). Google query: aswsp.sys AVAST Software KERNEL_MODE_EXCEPTION_NOT_HANDLED_M On Sat 17/09/2011 12:53:14 GMT your computer crashed crash dump file: C:\Windows\Minidump\Mini091711-11.dmp This was probably caused by the following module: usbport.sys (USBPORT+0x1025) Bugcheck code: 0xFE (0x6, 0xFFFFFFFF8DA59B00, 0x66725045, 0x0) Error: BUGCODE_USB_DRIVER file path: C:\Windows\system32\drivers\usbport.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: USB 1.1 & 2.0 Port Driver Bug check description: This indicates that an error has occurred in a Universal Serial Bus (USB) driver. The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time. Conclusion 83 crash dumps have been found and analyzed. Only 15 are included in this report. 6 third party drivers have been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers: nvlddmkm.sys (NVIDIA Compatible Windows Vista Kernel Mode Driver, Version 182.14 , NVIDIA Corporation) bewgu.sys (Adaptateur WiFi Driver, BeWAN systems) aswsp.sys (avast! self protection module, AVAST Software) aswtdi.sys (avast! TDI Filter Driver, AVAST Software) symtdi.sys symefa.sys If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems. Read the topic general suggestions for troubleshooting system crashes for more information. Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

Ainsi que Mbam :

Code: Tout sélectionner: Malwarebytes' Anti-Malware 1.51.2.1300 www.malwarebytes.org Version de la base de données: 7733 Windows 6.0.6002 Service Pack 2 Internet Explorer 9.0.8112.16421 17/09/2011 16:01:44 mbam-log-2011-09-17 (16-01-44).txt Type d'examen: Examen rapide Elément(s) analysé(s): 168843 Temps écoulé: 8 minute(s), 56 seconde(s) Processus mémoire infecté(s): 0 Module(s) mémoire infecté(s): 0 Clé(s) du Registre infectée(s): 37 Valeur(s) du Registre infectée(s): 1 Elément(s) de données du Registre infecté(s): 0 Dossier(s) infecté(s): 13 Fichier(s) infecté(s): 21 Processus mémoire infecté(s): (Aucun élément nuisible détecté) Module(s) mémoire infecté(s): (Aucun élément nuisible détecté) Clé(s) du Registre infectée(s): HKEY_CLASSES_ROOT\CLSID\{147A976F-EEE1-4377-8EA7-4716E4CDD239} (Adware.MyWebSearch) -> Quarantined and deleted successfully. HKEY_CLASSES_ROOT\CLSID\{1602F07D-8BF3-4c08-BDD6-DDDB1C48AEDC} (Adware.ClickPotato) -> Quarantined and deleted successfully. HKEY_CLASSES_ROOT\TypeLib\{C55CA95C-324B-451c-B2D2-6E895AA75FEC} (Adware.ClickPotato) -> Quarantined and deleted successfully. HKEY_CLASSES_ROOT\Interface\{30B15818-E110-4527-9C05-46ACE5A3460D} (Adware.ClickPotato) -> Quarantined and deleted successfully. HKEY_CLASSES_ROOT\ClickPotatoLiteAX.info.1 (Adware.ClickPotato) -> Quarantined and deleted successfully. HKEY_CLASSES_ROOT\ClickPotatoLiteAX.info (Adware.ClickPotato) -> Quarantined and deleted successfully. HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Ext\Stats\{1602F07D-8BF3-4C08-BDD6-DDDB1C48AEDC} (Adware.ClickPotato) -> Quarantined and deleted successfully. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Ext\PreApproved\{1602F07D-8BF3-4C08-BDD6-DDDB1C48AEDC} (Adware.ClickPotato) -> Quarantined and deleted successfully. HKEY_CLASSES_ROOT\CLSID\{AC6D819E-AA8F-4418-A3BB-D165C1B18BB5} (Adware.ClickPotato) -> Quarantined and deleted successfully. HKEY_CLASSES_ROOT\ClickPotatoLiteAX.UserProfiles.1 (Adware.ClickPotato) -> Quarantined and deleted successfully. HKEY_CLASSES_ROOT\ClickPotatoLiteAX.UserProfiles (Adware.ClickPotato) -> Quarantined and deleted successfully. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Ext\PreApproved\{AC6D819E-AA8F-4418-A3BB-D165C1B18BB5} (Adware.ClickPotato) -> Quarantined and deleted successfully. HKEY_CLASSES_ROOT\Typelib\{B035BA6B-57CD-4F72-B545-65BE465FCAF6} (Adware.ShoppingReport2) -> Quarantined and deleted successfully. HKEY_CLASSES_ROOT\Typelib\{D44FD6F0-9746-484E-B5C4-C66688393872} (Adware.ShoppingReport2) -> Quarantined and deleted successfully. HKEY_CLASSES_ROOT\Interface\{0EB3F101-224A-4B2B-9E5B-DF720857529C} (Adware.ShoppingReport2) -> Quarantined and deleted successfully. HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Ext\Stats\{BDEA95CF-F0E6-41E0-BD3D-B00F39A4E939} (Adware.ShoppingReport2) -> Quarantined and deleted successfully. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\Low Rights\ElevationPolicy\{A078F691-9C07-4AF2-BF43-35E79EECF8B7} (Adware.Softomate) -> Quarantined and deleted successfully. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Ext\PreApproved\{69725738-CD68-4f36-8D02-8C43722EE5DA} (Adware.Hotbar) -> Quarantined and deleted successfully. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Ext\PreApproved\{B58926D6-CFB0-45D2-9C28-4B5A0F0368AE} (Adware.ClickPotato) -> Quarantined and deleted successfully. HKEY_CLASSES_ROOT\MenuButtonIE.ButtonIE (Adware.ClickPotato) -> Quarantined and deleted successfully. HKEY_CLASSES_ROOT\MenuButtonIE.ButtonIE.1 (Adware.ClickPotato) -> Quarantined and deleted successfully. HKEY_CLASSES_ROOT\ShoppingReport2.HbAx (Adware.ShopperReports) -> Quarantined and deleted successfully. HKEY_CLASSES_ROOT\ShoppingReport2.HbAx.1 (Adware.ShopperReports) -> Quarantined and deleted successfully. HKEY_CLASSES_ROOT\ShoppingReport2.HbInfoBand (Adware.ShopperReports) -> Quarantined and deleted successfully. HKEY_CLASSES_ROOT\ShoppingReport2.HbInfoBand.1 (Adware.ShopperReports) -> Quarantined and deleted successfully. HKEY_CLASSES_ROOT\ShoppingReport2.IEButton (Adware.ShopperReports) -> Quarantined and deleted successfully. HKEY_CLASSES_ROOT\ShoppingReport2.IEButton.1 (Adware.ShopperReports) -> Quarantined and deleted successfully. HKEY_CLASSES_ROOT\ShoppingReport2.IEButtonA (Adware.ShopperReports) -> Quarantined and deleted successfully. HKEY_CLASSES_ROOT\ShoppingReport2.IEButtonA.1 (Adware.ShopperReports) -> Quarantined and deleted successfully. HKEY_CLASSES_ROOT\ShoppingReport2.RprtCtrl (Adware.ShopperReports) -> Quarantined and deleted successfully. HKEY_CLASSES_ROOT\ShoppingReport2.RprtCtrl.1 (Adware.ShopperReports) -> Quarantined and deleted successfully. HKEY_CLASSES_ROOT\AppID\MenuButtonIE.DLL (Adware.ClickPotato) -> Quarantined and deleted successfully. HKEY_CURRENT_USER\Software\clickpotatolitesa (Adware.ClickPotato) -> Quarantined and deleted successfully. HKEY_CURRENT_USER\Software\ShoppingReport2 (Adware.ShoppingReport2) -> Quarantined and deleted successfully. HKEY_LOCAL_MACHINE\SOFTWARE\ClickPotatoLite (Adware.ClickPotato) -> Quarantined and deleted successfully. HKEY_LOCAL_MACHINE\SOFTWARE\ShoppingReport2 (Adware.ShoppingReport2) -> Quarantined and deleted successfully. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ShoppingReport2 (Adware.Hotbar) -> Quarantined and deleted successfully. Valeur(s) du Registre infectée(s): HKEY_LOCAL_MACHINE\SOFTWARE\Mozilla\Firefox\extensions\ClickPotatoLite@ClickPotatoLite.com (Adware.ClickPotato) -> Value: ClickPotatoLite@ClickPotatoLite.com -> Quarantined and deleted successfully. Elément(s) de données du Registre infecté(s): (Aucun élément nuisible détecté) Dossier(s) infecté(s): c:\programdata\2aca5cc3-0f83-453d-a079-1076fe1a8b65 (Adware.Seekmo) -> Quarantined and deleted successfully. c:\programdata\clickpotatolitesa (Adware.ClickPotato) -> Quarantined and deleted successfully. c:\Users\pc\AppData\Roaming\clickpotatolite (Adware.ClickPotato) -> Delete on reboot. c:\program files\clickpotatolite (Adware.ClickPotato) -> Quarantined and deleted successfully. c:\program files\clickpotatolite\bin (Adware.ClickPotato) -> Quarantined and deleted successfully. c:\program files\clickpotatolite\bin\10.0.668.0 (Adware.ClickPotato) -> Quarantined and deleted successfully. c:\program files\clickpotatolite\bin\10.0.668.0\firefox (Adware.ClickPotato) -> Quarantined and deleted successfully. c:\program files\clickpotatolite\bin\10.0.668.0\firefox\extensions (Adware.ClickPotato) -> Quarantined and deleted successfully. c:\program files\clickpotatolite\bin\10.0.668.0\firefox\extensions\plugins (Adware.ClickPotato) -> Quarantined and deleted successfully. c:\program files\shoppingreport2 (Adware.ShoppingReport2) -> Quarantined and deleted successfully. c:\program files\shoppingreport2\Bin (Adware.ShoppingReport2) -> Quarantined and deleted successfully. c:\program files\shoppingreport2\Bin\2.7.34 (Adware.ShoppingReport2) -> Quarantined and deleted successfully. c:\programdata\microsoft\Windows\start menu\Programs\clickpotato (Adware.ClickPotato) -> Quarantined and deleted successfully. Fichier(s) infecté(s): c:\Users\pc\AppData\Local\Temp\ptu7514_tmp.exe (PUP.Casino) -> Not selected for removal. c:\Users\pc\AppData\Local\Temp\ptubb7_tmp.exe (PUP.Casino) -> Not selected for removal. c:\Users\pc\AppData\Local\Temp\cra3652.tmp (PUP.Casino.Gen) -> Not selected for removal. c:\Users\pc\AppData\Local\Temp\saiC674.exe (Adware.ScanQuery) -> Quarantined and deleted successfully. c:\Users\pc\AppData\Local\Temp\install\Keygen.exe (RiskWare.Tool.CK) -> Quarantined and deleted successfully. c:\Users\pc\AppData\Local\Temp\is-1AGTC.tmp\PCTuto\inst.exe (Adware.Agent) -> Quarantined and deleted successfully. c:\Users\pc\AppData\Local\Temp\wz0145\Keygen.exe (RiskWare.Tool.CK) -> Quarantined and deleted successfully. c:\Users\pc\setupcasino_3534.exe (PUP.Casino) -> Not selected for removal. c:\Users\pc\AppData\Local\Temp\0.9251963112672461.exe (Exploit.Drop.2) -> Quarantined and deleted successfully. c:\programdata\clickpotatolitesa\clickpotatolitesa.dat (Adware.ClickPotato) -> Quarantined and deleted successfully. c:\programdata\clickpotatolitesa\clickpotatolitesaabout.mht (Adware.ClickPotato) -> Quarantined and deleted successfully. c:\programdata\clickpotatolitesa\clickpotatolitesaau.dat (Adware.ClickPotato) -> Quarantined and deleted successfully. c:\programdata\clickpotatolitesa\clickpotatolitesaeula.mht (Adware.ClickPotato) -> Quarantined and deleted successfully. c:\programdata\clickpotatolitesa\clickpotatolitesa_kyf_update.dat (Adware.ClickPotato) -> Quarantined and deleted successfully. c:\program files\clickpotatolite\bin\10.0.668.0\launchhelp.dll (Adware.ClickPotato) -> Quarantined and deleted successfully. c:\program files\clickpotatolite\bin\10.0.668.0\firefox\extensions\install.rdf (Adware.ClickPotato) -> Quarantined and deleted successfully. c:\program files\clickpotatolite\bin\10.0.668.0\firefox\extensions\plugins\npclntax_clickpotatolitesa.dll (Adware.ClickPotato) -> Quarantined and deleted successfully. c:\program files\shoppingreport2\Uninst.exe (Adware.ShoppingReport2) -> Quarantined and deleted successfully. c:\programdata\microsoft\Windows\start menu\Programs\clickpotato\About Us.lnk (Adware.ClickPotato) -> Quarantined and deleted successfully. c:\programdata\microsoft\Windows\start menu\Programs\clickpotato\clickpotato customer support.lnk (Adware.ClickPotato) -> Quarantined and deleted successfully. c:\programdata\microsoft\Windows\start menu\Programs\clickpotato\clickpotato uninstall instructions.lnk (Adware.ClickPotato) -> Quarantined and deleted successfully. .

.
Pour aujourd'hui , je pense que c'est tout ce que je pourrai faire, normalement j'ai l'après midi chargè mais je suis en vacances donc quelques jours pour trouver.
Encore merci.
J'ai fait un passage avec remove tools 2011 de Kapersky qui ne m'a rien trouvè.

bernard53 · le 18 Sep 2011 15:19

OK pour les rapports :wink:

il semble qu'Avast et ta carte graphique sont en partie en cause.

Pour Avast je pense qu'une bonne désinstallation peux résoudre cela et pour ta carte graphique une mise à jour.

soit ici: http://www.nvidia.fr/Download/index.aspx?lang=fr

ou la. http://www.touslesdrivers.com/index.php?v_page=29

oxmosys · le 18 Sep 2011 15:35

bernard53 a raison, tu as une erreur 'DRIVER_IRQL_NOT_LESS_OR_EQUAL' avec ta carte graphique, c'est très parlant.

routman54 · le 18 Sep 2011 20:13

Bonsoir,
Après que je lui ai laissè un message sur son tel. ,mon jeune voisin a dèsinstallè Avast mais comme il n'arrivait toujours pas à télécharger, il a lancer la restauration d'usine . On verra ce que ça dit demain, j'ai peur que celà ne rèsolve le problème. C'est pour celà que je prèfère prendre le "malade" à la maison quand c'est possible, au moins moi j'ai de la patience.
Merci à tous deux et je vous tiens au jus.

oxmosys · le 18 Sep 2011 21:16

La restauration de l'usine devrait corriger tout problème qui n'est pas matériel car elle ramène l'ordinateur au même stade que lorsqu'il a été acheté. Par contre.. bon maintenant c'est fait alors c'est trop tard, mais il faut faire gaffe avec la restauration car tout dépendant de la technologie utilisée par le constructeur de l'ordinateur pour restaurer les données, les documents et tout le reste peuvent être écrasés (effacés) durant la restauration.. En tout cas bonne chance :-)

routman54 · le 19 Sep 2011 20:44

Bonsoir
Après sa rèinstallation d'usine mon voisin a dit que a buggait encore et il s'est rachetè un autre ordinateur. J'ai rècupèrer l'ancien , sans rien lui faire il fonctionne , là il fait ses mises à jours.Chez lui il marchait par Wifi sur une Box SFR , il était obligè de le rèinitialiser à chaque fois et il refusait les mises à jours . Chercher l'erreur. Il fera le bonheur de quelqu'un de moins pressè
Merci quand même du coup de main.

bernard53 · le 19 Sep 2011 20:46

Au moins tu as récupérer un pc :lol:

oxmosys · le 19 Sep 2011 20:56

Héhé.. ok bah voilà!

Ask to Old Man · le 20 Sep 2011 08:42

[HS]

bonjour Dany,

Si tu continue comme ça, tu vas pouvoir faire marchand ambulant de PC durant tes livraisons... :lol:

[/HS)

routman54 · le 20 Sep 2011 20:17

[hs]
Mon brave Atom si je devais les revendre avec les heures que je passe dessus je serai pas beaucoup payè de l'heure , les offrir et donner un peu de joie ça me paie plus , celui ci ira à quelqu'un qui fêtera son anniversaire d'ici peu ,j'y rajouterai un écran un clavier et le tour est jouè.
Bonne soirèe.
[hs]

Ask to Old Man · le 20 Sep 2011 20:47

Ce n'était bien sur qu'une plaisanterie!! Perso, les quelques rares vieilles bécanes ou
pièces dispo chez moi,ont finit par faire le bonheur d'assoc' de quartier & leur cyber café.

PC très lent et blue screen

PC très lent et blue screen

Re: PC très lent et blue screen

Re: PC très lent et blue screen

Re: PC très lent et blue screen

Re: PC très lent et blue screen

Re: PC très lent et blue screen

Re: PC très lent et blue screen

Re: PC très lent et blue screen

Re: PC très lent et blue screen

Re: PC très lent et blue screen

Re: PC très lent et blue screen

Re: PC très lent et blue screen

Re: PC très lent et blue screen

Re: PC très lent et blue screen

Sujets similaires

Qui est en ligne