Bad pool header écran bleu

Salut, merci pour ta rapidité !

Voici le premier rapport :


--------------------------------------------------------------------------------
Welcome to WhoCrashed (HOME EDITION) v 5.54
--------------------------------------------------------------------------------

This program checks for drivers which have been crashing your computer. If your computer has displayed a blue (or black) screen of death, suddenly rebooted or shut down then this program might help you find the root cause of the problem and a solution.

Whenever a computer suddenly reboots without displaying any notice or blue (or black) screen of death, the first thing that is often thought 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, many computers do not show a blue or black screen unless they are configured for this. Instead these systems suddenly reboot without any notice.

This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. It will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems.

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

Click here to check if you have the latest version or if an update is available.

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 of WhoCrashed which allows you to perform more thorough and detailed analysis. It also offers a range of additional features such as remote analysis on remote directories and remote computers on the network.

Please note that this version of WhoCrashed is not licensed for use by professional support engineers.

Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.


--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------

Computer name: PROPRIETAIREPC
Windows version: Windows 7 Service Pack 1, 6.1, build: 7601
Windows dir: C:\Windows
Hardware: Satellite L655, TOSHIBA, Portable PC
CPU: GenuineIntel Intel(R) Core(TM) i5 CPU M 460 @ 2.53GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 4151148544 bytes total




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Mon 07/08/2017 13:55:52 your computer crashed
crash dump file: C:\Windows\Minidump\080717-24804-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70E40)
Bugcheck code: 0x19 (0x20, 0xFFFFFA8007F4CC00, 0xFFFFFA8007F4CC20, 0x402001A)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 07/08/2017 13:55:52 your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: aswsp.sys (aswSP+0xB92F)
Bugcheck code: 0x19 (0x20, 0xFFFFFA8007F4CC00, 0xFFFFFA8007F4CC20, 0x402001A)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\aswsp.sys
product: avast! Antivirus
company: AVAST Software
description: avast! self protection module
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. This problem might also be caused because of overheating (thermal issue).
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: AVAST Software BAD_POOL_HEADER



On Mon 07/08/2017 11:27:21 your computer crashed
crash dump file: C:\Windows\Minidump\080717-23649-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70E40)
Bugcheck code: 0x19 (0x20, 0xFFFFFA8007EEAC00, 0xFFFFFA8007EEAC20, 0x402000C)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 04/08/2017 17:37:25 your computer crashed
crash dump file: C:\Windows\Minidump\080717-26910-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70E40)
Bugcheck code: 0x19 (0x20, 0xFFFFFA8007E02490, 0xFFFFFA8007E024B0, 0x402000C)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 03/08/2017 23:19:05 your computer crashed
crash dump file: C:\Windows\Minidump\080417-23774-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70E40)
Bugcheck code: 0x19 (0x20, 0xFFFFFA8008219280, 0xFFFFFA80082192A0, 0x4020008)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.





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

9 crash dumps have been found and analyzed. Only 5 are included in this report. A third party driver has 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:

aswsp.sys (avast! self protection module, AVAST Software)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by 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 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.

Et les trois suivants :

FRST : https://pjjoint.malekal.com/files.php?id=FRST_20170808_g12z11x14e6l10

Shortcut : https://pjjoint.malekal.com/files.php?id=20170808_v11p8r14d9d13

Addition : https://pjjoint.malekal.com/files.php?id=20170808_r7c14i6f6k6

Voilà le dernier rapport :

Résultats de correction de Farbar Recovery Scan Tool (x64) Version: 03-08-2016
Exécuté par Proprietaire (2017-08-08 18:39:37) Run:1
Exécuté depuis C:\Users\Proprietaire\Desktop
Profils chargés: Proprietaire (Profils disponibles: Proprietaire)
Mode d'amorçage: Safe Mode (with Networking)
==============================================

fixlist contenu:

CreateRestorePoint:
CloseProcesses:
2017-08-07 13:57 - 2017-08-07 13:58 - 00275152 _____ C:\Windows\Minidump\080717-24804-01.dmp
2017-08-07 12:38 - 2017-08-07 12:38 - 00000000 ____D C:\Program Files (x86)\mtJyu7dYEpUK
2017-08-07 12:37 - 2017-08-07 13:55 - 00000000 ____D C:\Program Files (x86)\AdBlocker
2017-08-07 12:37 - 2017-08-07 12:37 - 00021180 ____H C:\Windows\Tasks\{040E0F47-0B0B-790B-0A11-0905057E117A}.job
2017-08-07 12:35 - 2017-08-07 12:35 - 00020932 ____H C:\Windows\Tasks\{790E0B47-0D7E-090B-0E11-0D087F0F1104}.job
2017-08-07 12:22 - 2017-08-07 12:32 - 00000000 ____D C:\Program Files\GKOZNAYK25
2017-08-07 12:22 - 2017-08-07 12:27 - 00000000 ____D C:\Program Files\IKHPF14VKY
2017-08-07 12:22 - 2017-08-07 12:22 - 00000000 ____D C:\Users\Proprietaire\AppData\Roaming\uypxpkvx1t5
2017-08-07 12:22 - 2017-08-07 12:22 - 00000000 ____D C:\Users\Proprietaire\AppData\Roaming\dpexuhxjkfs
2017-08-07 12:21 - 2017-08-07 12:21 - 00000000 ____D C:\Users\Proprietaire\AppData\Roaming\ls13abtjq5m
2017-08-07 12:20 - 2017-08-07 12:20 - 00000000 ____D C:\Windows\Azart
2017-08-07 11:55 - 2017-08-07 11:56 - 01069267 _____ C:\Users\Proprietaire\Desktop\Advanced_SystemCare_Ultimate_10_Crack_Key.zip
2017-08-03 22:43 - 2017-08-03 22:44 - 00000000 ____D C:\Users\Proprietaire\AppData\LocalLow\IObit
2017-08-03 22:43 - 2017-08-03 22:43 - 00000000 ____D C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Advanced SystemCare Ultimate
2017-08-03 22:43 - 2017-08-03 22:43 - 00000000 ____D C:\ProgramData\{D76294E6-03B8-4971-AF2E-3F846161A690}
2017-08-03 22:43 - 2017-08-03 22:43 - 00000000 ____D C:\ProgramData\{ACBCD40A-42A8-4FF9-BD42-ABCD14998CBA}
2017-08-03 22:44 - 2017-08-03 22:44 - 00000000 ____D C:\Windows\Tasks\ImCleanDisabled
2017-08-03 22:44 - 2017-08-03 22:44 - 00000000 ____D C:\ProgramData\ProductData
2017-08-03 22:44 - 2017-08-03 22:44 - 00000000 ____D C:\ProgramData\BDLogging
2017-08-03 22:44 - 2016-11-02 19:11 - 00520032 _____ (BitDefender S.R.L.) C:\Windows\system32\Drivers\trufos.sys
2017-08-03 11:20 - 2017-08-03 11:23 - 00002531 _____ C:\Ad-Report-CLEAN[1].txt
2017-08-03 10:57 - 2017-08-03 11:02 - 00002059 _____ C:\Ad-Report-SCAN[1].txt
2017-08-03 10:56 - 2017-08-03 11:23 - 00000000 ____D C:\Ad-Remover
2017-08-03 10:56 - 2017-08-03 10:56 - 01344041 _____ (C_XX) C:\Users\Proprietaire\Downloads\ad-remover_ad_remover_2010_2.0.0.0_anglais_313780.exe
2017-08-03 10:53 - 2017-08-03 11:12 - 00000000 ____D C:\Program Files (x86)\AdBlock Master
2017-08-03 10:53 - 2017-08-03 10:53 - 00118720 _____ C:\Users\Proprietaire\AppData\Local\GDIPFONTCACHEV1.DAT
2017-08-03 10:13 - 2017-08-03 10:13 - 00000000 ____D C:\ProgramData\{B96EB44A-7860-4F13-BC9A-0A73CA5F11C2}
Task: {553DF0BA-256A-460F-A09C-A617699B3479} - \TaskUserUpdate_wp -> Pas de fichier <==== ATTENTION
Task: {647D9AB1-BC49-44C2-AF1A-B26265949B27} - System32\Tasks\{01E3F0B5-74CC-4A7D-980E-5CBAC4353688} => pcalua.exe -a "C:\Program Files (x86)\Pricora 12.0\Uninstall.exe" -c /fcp=1

S2 AdBlockerService; C:\Program Files (x86)\AdBlocker\AdBlockerService.exe [110080 2017-04-11] (Star Line) [Fichier non signé]
EmptyTemp:
RemoveProxy:
Reboot:

Erreur: Un point de restauration ne peut être créé qu'en mode normal.
Processus fermé avec succès.
C:\Windows\Minidump\080717-24804-01.dmp => déplacé(es) avec succès
C:\Program Files (x86)\mtJyu7dYEpUK => déplacé(es) avec succès
C:\Program Files (x86)\AdBlocker => déplacé(es) avec succès
C:\Windows\Tasks\{040E0F47-0B0B-790B-0A11-0905057E117A}.job => déplacé(es) avec succès
C:\Windows\Tasks\{790E0B47-0D7E-090B-0E11-0D087F0F1104}.job => déplacé(es) avec succès
C:\Program Files\GKOZNAYK25 => déplacé(es) avec succès
C:\Program Files\IKHPF14VKY => déplacé(es) avec succès
C:\Users\Proprietaire\AppData\Roaming\uypxpkvx1t5 => déplacé(es) avec succès
C:\Users\Proprietaire\AppData\Roaming\dpexuhxjkfs => déplacé(es) avec succès
C:\Users\Proprietaire\AppData\Roaming\ls13abtjq5m => déplacé(es) avec succès
C:\Windows\Azart => déplacé(es) avec succès
C:\Users\Proprietaire\Desktop\Advanced_SystemCare_Ultimate_10_Crack_Key.zip => déplacé(es) avec succès
C:\Users\Proprietaire\AppData\LocalLow\IObit => déplacé(es) avec succès
"C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Advanced SystemCare Ultimate" => non trouvé(e).
C:\ProgramData\{D76294E6-03B8-4971-AF2E-3F846161A690} => déplacé(es) avec succès
C:\ProgramData\{ACBCD40A-42A8-4FF9-BD42-ABCD14998CBA} => déplacé(es) avec succès
C:\Windows\Tasks\ImCleanDisabled => déplacé(es) avec succès
C:\ProgramData\ProductData => déplacé(es) avec succès
C:\ProgramData\BDLogging => déplacé(es) avec succès
"C:\Windows\system32\Drivers\trufos.sys" => non trouvé(e).
C:\Ad-Report-CLEAN[1].txt => déplacé(es) avec succès
C:\Ad-Report-SCAN[1].txt => déplacé(es) avec succès
C:\Ad-Remover => déplacé(es) avec succès
C:\Users\Proprietaire\Downloads\ad-remover_ad_remover_2010_2.0.0.0_anglais_313780.exe => déplacé(es) avec succès
C:\Program Files (x86)\AdBlock Master => déplacé(es) avec succès
C:\Users\Proprietaire\AppData\Local\GDIPFONTCACHEV1.DAT => déplacé(es) avec succès
C:\ProgramData\{B96EB44A-7860-4F13-BC9A-0A73CA5F11C2} => déplacé(es) avec succès
"HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Logon\{553DF0BA-256A-460F-A09C-A617699B3479}" => clé supprimé(es) avec succès
"HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Tasks\{553DF0BA-256A-460F-A09C-A617699B3479}" => clé supprimé(es) avec succès
HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Tree\TaskUserUpdate_wp => clé non trouvé(e).
"HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Plain\{647D9AB1-BC49-44C2-AF1A-B26265949B27}" => clé supprimé(es) avec succès
"HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Tasks\{647D9AB1-BC49-44C2-AF1A-B26265949B27}" => clé supprimé(es) avec succès
C:\Windows\System32\Tasks\{01E3F0B5-74CC-4A7D-980E-5CBAC4353688} => déplacé(es) avec succès
"HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Tree\{01E3F0B5-74CC-4A7D-980E-5CBAC4353688}" => clé supprimé(es) avec succès
AdBlockerService => service supprimé(es) avec succès

========= RemoveProxy: =========

"HKLM\SOFTWARE\Policies\Microsoft\Internet Explorer" => clé supprimé(es) avec succès
HKU\.DEFAULT\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\Connections\\DefaultConnectionSettings => valeur supprimé(es) avec succès
HKU\.DEFAULT\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\Connections\\SavedLegacySettings => valeur supprimé(es) avec succès
HKU\S-1-5-21-2770342242-2561543545-836076102-1000\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\Connections\\DefaultConnectionSettings => valeur supprimé(es) avec succès
HKU\S-1-5-21-2770342242-2561543545-836076102-1000\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\Connections\\SavedLegacySettings => valeur supprimé(es) avec succès


========= Fin de RemoveProxy: =========


=========== EmptyTemp: ==========

BITS transfer queue => 8388608 B
DOMStore, IE Recovery, AppCache, Feeds Cache, Thumbcache, IconCache => 19639815 B
Java, Flash, Steam htmlcache => 1050 B
Windows/system/drivers => 24681645 B
Edge => 0 B
Chrome => 18155862 B
Firefox => 95320890 B
Opera => 0 B

Temp, IE cache, history, cookies, recent:
Default => 66228 B
Public => 0 B
ProgramData => 0 B
systemprofile => 46704617 B
systemprofile32 => 1413745 B
LocalService => 132244 B
NetworkService => 75712 B
Proprietaire => 116861613 B

RecycleBin => 0 B
EmptyTemp: => 316.1 MB données temporaires supprimées.

================================


Le système a dû redémarrer.

Fin de Fixlog 18:39:55

Toujours rien après la dernière analyse de Malwarebytes, je perds espoir haha. Je sais pas si tu en a besoin mais voici le rapport :

Malwarebytes Anti-Malware
www.malwarebytes.org

Date de l'analyse: 15/08/2017
Heure de l'analyse: 01:22
Fichier journal: rapport.txt
Administrateur: Oui

Version: 2.2.0.1024
Base de données de programmes malveillants: v2017.08.14.08
Base de données de rootkits: v2017.08.02.01
Licence: Gratuit
Protection contre les programmes malveillants: Désactivé
Protection contre les sites Web malveillants: Désactivé
Autoprotection: Désactivé

Système d'exploitation: Windows 7 Service Pack 1
Processeur: x64
Système de fichiers: NTFS
Utilisateur: Proprietaire

Type d'analyse: Analyse des menaces
Résultat: Terminé
Objets analysés: 272725
Temps écoulé: 17 min, 24 s

Mémoire: Activé
Démarrage: Activé
Système de fichiers: Activé
Archives: Activé
Rootkits: Désactivé
Heuristique: Activé
PUP: Avertir
PUM: Activé

Processus: 0
(Aucun élément malveillant détecté)

Modules: 0
(Aucun élément malveillant détecté)

Clés du Registre: 1
PUP.Optional.PSScriptLoad.ACMB3, HKU\S-1-5-21-2770342242-2561543545-836076102-1000\CONSOLE\%SYSTEMROOT%_SYSTEM32_SVCHOST.EXE, , [b68a7b1232771e18689827c545bb9a66],

Valeurs du Registre: 1
PUP.Optional.PSScriptLoad.ACMB3, HKU\S-1-5-21-2770342242-2561543545-836076102-1000\CONSOLE\%SYSTEMROOT%_SYSTEM32_SVCHOST.EXE|WindowPosition, 201329664, , [b68a7b1232771e18689827c545bb9a66]

Données du Registre: 0
(Aucun élément malveillant détecté)

Dossiers: 0
(Aucun élément malveillant détecté)

Fichiers: 0
(Aucun élément malveillant détecté)

Secteurs physiques: 0
(Aucun élément malveillant détecté)


(end)

Non c'est toujours pareil, écrans bleus dès le démarrage... :( d'autres idées ?

C'est bon merci beaucoup plus de problèmes ! Tu me conseillerai plutôt quoi comme antivirus du coup ? :)