Bsod + infection

ok , merci pour tout .
Je suis entrain de faire un scandisk il trouve plein d'erreur , je verrai bien aprés.
Encore merçi à toi.

le rapport combo est propre.A présent on peut écarter le risque d'une infection.

Ton probléme vient certainement du matériel.Je te propose de poster un sujet sur le forum ccm dans la catégorie matériel/hardware.

Bonne chance......

http://www.cijoint.fr/cjlink.php?file=cj201011/cijF4nfGJh.txt

je l'ai fait en mode sans echec car sinon ca ne fonctionnait pas.

Ok

Pour verifier certains doutes fais ce qui suis.

/!\ A l'attention de ceux qui passent sur ce sujet /!\
Le logiciel qui suit n'est pas à utiliser à la légère et peut faire des dégâts s'il est mal utilisé ! Ne le faites que si un helpeur du forum qui connait bien cet outil vous l'a recommandé.

/!\ Désactive tous tes logiciels de protection (Antivirus, Antispywares) /!\

* Télécharge combofix(de sUBs) sur ton Bureau.
* Double-clique sur ComboFix.exe afin de le lancer.
* Il va te demander d'installer la console de récupération : accepte. (important en cas de problème)
/!\ Ne touche ni à la souris, ni au clavier durant le scan /!\
* Lorsque la recherche sera terminée, un rapport apparaîtra.
* Héberge le rapport C:\Combofix.txt sur le site cijoint.fr, puis copie/colle le lien fournit dans ta prochaine réponse sur le forum
#Si combofix ne veut pas se lancer renommes le en ccm.exe et éxécutes le en mode sans échec .
Tutoriel officiel de Combofix : http://www.bleepingcomputer.com/combofix/fr/comment-utiliser¬-combofix

le pc essayer de redémarrer au moment de l'erreur .
Sinon il a redémarrer une fois seul depuis le passage d'avenger.

Au moment de cette erreur 0*000000f4 te rappelle tu quelle application été active.?

Sinon depuis avenger ton pc se comporte t'il mieux.?
Le cerveau a des capacités tellement étonnantes qu'aujourd'hui pratiquement tout le monde en a un.

Logfile of The Avenger Version 2.0, (c) by Swandog46
http://swandog46.geekstogo.com

Platform: Windows Vista

*******************

Script file opened successfully.
Script file read successfully.

Backups directory opened successfully at C:\Avenger

*******************

Beginning to process script file:

Rootkit scan active.
No rootkits found!

File move operation "C:\Windows\winsxs\x86_cpu.inf_31bf3856ad364e35_6.0.6001.18000_none_5d4a5a9eef611fb3\processr.sys|C:\Windows\System32\drivers\processr.sys" completed successfully.
File move operation "C:\Windows\winsxs\x86_microsoft-windows-win32k_31bf3856ad364e35_6.0.6001.22754_none_b94b1375b3c94985\win32k.sys|C:\Windows\System32\win32k.sys" completed successfully.
File move operation "C:\Windows\winsxs\x86_microsoft-windows-os-kernel_31bf3856ad364e35_6.0.6001.18063_none_6bf282f6b4510613\ntkrnlpa.exe|C:\Windows\System32\ntkrnlpa.exe" completed successfully.

Completed script processing.

*******************

Finished! Terminate.

L'ordi ne veut plus demarrer j'ai un nouveau écran bleu code 0*000000f4 , j'en ai eu un autre je n'ai pas réussi à noter le code , et je suis obligé d'executer l'outils de diagnostique de démarrage .
L'utilitaire vient de finir de réparer le démarrage et l'ordi redémarre.

1. Télécharge http://www.geekstogo.com/forum/files/file/393-the-avenger-by-swandog46/ par Swandog46 sur ton Bureau.

* Décompresse le fichier
* avenger.exe sur le bureau

2. Copie le contenu en gras ci-dessous (CTRL+C),

Files to move:
C:\Windows\winsxs\x86_cpu.inf_31bf3856ad364e35_6.0.6001.18000_none_5d4a5a9eef611fb3\processr.sys | C:\Windows\System32\drivers\processr.sys
C:\Windows\winsxs\x86_microsoft-windows-win32k_31bf3856ad364e35_6.0.6001.22754_none_b94b1375b3c94985\win32k.sys | C:\Windows\System32\win32k.sys
C:\Windows\winsxs\x86_microsoft-windows-os-kernel_31bf3856ad364e35_6.0.6001.18063_none_6bf282f6b4510613\ntkrnlpa.exe | C:\Windows\System32\ntkrnlpa.exe

Note: Le code ci-dessus a été intentionnellement rédigé pour CET utilisateur.
si vous n'êtes pas CET utilisateur, NE PAS appliquer ces directives : elles pourraient endommager votre système.

3. Maintenant, lance The Avenger par clic droit, exécuter en tant qu'administrateur.

* Faites un clic droit sur la fenêtre sous "Input Script There":, Et choisissez Coller.A présent du dois avoir le script dans la fenétre blanche d' Avenger.
* Clique sur Exécuter
* Réponds "Yes" quand demandé.

4. The Avenger va automatiquement faire ce qui suit:

* Il va Redémarrer le système.
* Pendant le redémarrage, il apparaitra brièvement une fenêtre de commande de windows noire sur le bureau, c'est normal.
* Après le redémarrage, il crée un fichier log qui s'ouvrira, faisant apparaitre les actions exécutées par The Avenger. Ce fichier log se trouve ici : C:\avenger.txt

5. Pour finir copie/colle le contenu du ficher c:\avenger.txt dans ta prochaine réponse.

Tuto :
http://www.oxygenepc.com/forum/the-avenger-t594.html

http://www.cijoint.fr/cjlink.php?file=cj201011/cijM7uduRT.txt

http://www.cijoint.fr/cjlink.php?file=cj201011/cijBvEd78C.txt

http://www.cijoint.fr/cjlink.php?file=cj201011/cijYWZn9H6.txt

memoire vive tésté , aucune erreur

ok , pour l'instant je teste la mémoire vive avec le programme inclus dans windows en mode étendu avec 5 passes à réaliser . c'est donc trés long .
Je ferai donc ce que tu me demandes demain aprés-midi .
Merçi de ta patience.

Télécharge SEAF.exe de C_XX
http://www.teamxscript.org/too/SEAF.exe
Double-clique sur le fichier SEAF.exe.
Dans la partie calculer le checkhum marquer MD5
Dans la barre de recherche tape

processr.sys

Clique sur Lancer la recherche.
Le scan prendra quelques minutes et un fichier texte va s'ouvrir .
Héberge le rapport SEAF.txt sur le site cijoint.fr, puis copie/colle le lien fournit dans ta prochaine réponse sur le forum

Fais la méme chose avec les deux autres .

win32k.sys
et
ntkrnlpa.exe

fais un memtest86+

j'ai du mal a finir nod 32 car il plante constament

Le pense que la cause principale de tes plantages sont a cause de ta mémoire .Fais cette série de tests .
J'attends le rapport Eset Nod 32

https://www.pcastuces.com/pratique/windows/memoire_vista/page1.htm

je viens d'essayer la commande en mode administrateur sfc /scannow , mais j'ai un message d'erreur à la fin de l'analyse , comme quoi il n'a pas réussi à faire la réparation.
J'essaye aussi de passer Eset online scanner mais c'est pas facile ça reboot de temps en temps.

--------------------------------------------------------------------------------
Welcome to WhoCrashed Home Edition 2.10
--------------------------------------------------------------------------------

This program checks for drivers which have been crashing your computer.

Whenever a computer suddenly reboots without displaying any notice or blue screen of death, the first thing that is often though about is a hardware failure. In reality, on Windows most crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, most computers do not show a blue screen unless they are configured to do so. Instead these systems suddenly reboot without any notice.

This program does post-mortem crash dump analysis with the single click of a button.

To obtain technical support visit www.resplendence.com/support

To check if a newer version of this program is available, click here.

Just click the Analyze button for a comprehensible report ...

--------------------------------------------------------------------------------
Home Edition notice
--------------------------------------------------------------------------------

This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition. The professional edition of WhoCrashed also allows analysis of crashdumps on remote drives and computers on the network and offers more detailed analysis.

--------------------------------------------------------------------------------
Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sun 14/11/2010 21:28:00 your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0xA (0xC5791A06, 0xFF, 0x0, 0x82684669)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\Mini111410-07.dmp
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

On Sun 14/11/2010 21:11:57 your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0x1000008E (0x80000003, 0x8266CEE1, 0x803ECBA0, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
Dump file: C:\Windows\Minidump\Mini111410-06.dmp
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

On Sun 14/11/2010 17:00:44 your computer crashed
This was likely caused by the following module: win32k.sys
Bugcheck code: 0xD1 (0x82BC4BFE, 0x1C, 0x8, 0x82BC4BFE)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\Mini111410-05.dmp
file path: C:\Windows\system32\win32k.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

On Sun 14/11/2010 16:45:40 your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0xFC (0x8214182A, 0x6742C963, 0x803ECC20, 0x2)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
Dump file: C:\Windows\Minidump\Mini111410-04.dmp
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

On Sun 14/11/2010 14:31:04 your computer crashed
This was likely caused by the following module: win32k.sys
Bugcheck code: 0x50 (0xAB3BAE08, 0x8, 0xAB3BAE08, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Dump file: C:\Windows\Minidump\Mini111410-03.dmp
file path: C:\Windows\system32\win32k.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

On Sun 14/11/2010 14:19:39 your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0xA (0xC7B61A06, 0xFF, 0x0, 0x82693669)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\Mini111410-02.dmp
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

On Sun 14/11/2010 13:57:41 your computer crashed
This was likely caused by the following module: processr.sys
Bugcheck code: 0xA (0x20DD8005, 0xA, 0x1, 0x826AC51A)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\Mini111410-01.dmp
file path: C:\Windows\system32\drivers\processr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Processor Device Driver
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

On Sat 13/11/2010 17:02:32 your computer crashed
This was likely caused by the following module: win32k.sys
Bugcheck code: 0xD1 (0x82BC7BFE, 0x1C, 0x8, 0x82BC7BFE)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\Mini111310-05.dmp
file path: C:\Windows\system32\win32k.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

On Sat 13/11/2010 15:19:43 your computer crashed
This was likely caused by the following module: win32k.sys
Bugcheck code: 0x50 (0xFDD85408, 0x1, 0x8268BF90, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Dump file: C:\Windows\Minidump\Mini111310-04.dmp
file path: C:\Windows\system32\win32k.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

On Sat 13/11/2010 15:14:17 your computer crashed
This was likely caused by the following module: processr.sys
Bugcheck code: 0xA (0x36F, 0x1C, 0x1, 0x829C6BFE)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\Mini111310-03.dmp
file path: C:\Windows\system32\drivers\processr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Processor Device Driver
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

On Sat 13/11/2010 14:48:35 your computer crashed
This was likely caused by the following module: win32k.sys
Bugcheck code: 0xA (0xBB6FE380, 0xFF, 0x1, 0x829C37A7)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\Mini111310-02.dmp
file path: C:\Windows\system32\win32k.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

On Sat 13/11/2010 14:04:22 your computer crashed
This was likely caused by the following module: processr.sys
Bugcheck code: 0x1000008E (0xC0000005, 0x35612EE3, 0x803ECC20, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
Dump file: C:\Windows\Minidump\Mini111310-01.dmp
file path: C:\Windows\system32\drivers\processr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Processor Device Driver
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

12 crash dumps have been found and analyzed. Note that it's not always possible to state with certainty whether a reported driver is really 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.