CRITICAL_PROCESS_DIED bsod

Salut,

Il faut déjà voir si cela se reproduit.

Les écrans bleus ou BSOD sont des plantages de Windows qui ne peut plus continuer à fonctionner.
Ces plantages ont plusieurs sources possibles :
- sources logiciels : plantage d'un pilote d'un périphérique comme ceux de la carte graphique, l'antivirus qui plante ou tout autre logiciel qui peut se charger "dans un bas niveau" sur Windows.
- sources matériels : problème matériels sur le disque dur, barrettes de mémoire défectueuses ou incomparabilités, etc

Il faut impérativement que tu regardes si ces plantages ont lieu à des moments particuliers, par exemple, si c'est lorsque tu lances une vidéo sur ton navigateur internet ou un jeu, il y a des chances que ce soit le pilote de la carte graphique. Il faudra alors réinstaller les pilotes de la carte graphique.
Débranche aussi tout autre périphérique que le clavier/souris (manette de jeu, webcam en USB, imprimante USB, etc), si tu as un de ces périphériques, indique le, ça peut être une source.

plus d'informations sur ces écrans bleus, sur la page suivante : https://www.malekal.com/bsod-ecran-bleu-windows/

On peut aussi utiliser WhoCrashed pour obtenir des informations sur ces plantages.
Télécharger et exécute Whocrashed : Telecharger WhoCrashed
=> Tutoriel WhoCrashed
Fais un copier/coller du contenu ici comme indiqué dans le tuto.

puis :

Suis le tutoriel FRST. ( prends le temps de lire attentivement - tout y est bien expliqué ).

Télécharge et lance le scan FRST,
Attendre la fin du scan, un message indique que l'analyse est terminée.

Trois rapports FRST seront générés :

• FRST.txt
• Shortcut.txt
• Additionnal.txt

Envoie ces 3 rapports sur le site https://pjjoint.malekal.com/ afin de les partager.
En retour donne les 3 liens pjjoint qui mènent aux rapports ici dans une nouvelle réponse afin que l'on puisse les consulter.

Ca n'a rien à voir avec des virus

Fais du ménage pour commencer
Vas dans le Panneau de configuration
puis programmes et fonctionnalités.
Désinstalle :
CCleaner
McAfee
MEGAsync (sauf si tu synchronises avec)
Orange
iCloud
QuickTime
WD Backup

Voici la correction à effectuer avec FRST. Tu peux t'aider de cette note explicative avec des captures d'écran.
Relance FRST puis sur ton clavier appuyer sur la touche CTRL + Y.
Le bloc-note va s'ouvrir, copie/colle ceci.

CreateRestorePoint:
CloseProcesses:
 R2 WsAppService; C:\Program Files (x86)\Wondershare\WAF\2.3.2.221\WsAppService.exe [459408 2017-02-10] (Wondershare) 
HKLM-x32\...\Run: [Wondershare Helper Compact.exe] => C:\Program Files (x86)\Common Files\Wondershare\Wondershare Helper Compact\WSHelper.exe [2072928 2014-10-31] (Wondershare)  Hosts:
C:\Program Files (x86)\Common Files\Wondershare
EmptyTemp:
RemoveProxy:
Reboot:

Enregistre le contenu par le menu fichier puis enregistrer.

Ferme le bloc-note, retourne sur FRST et clique sur le bouton "Corriger / Fix"
Un redémarrage sera peut-être nécessaire et automatique.
Un fichier texte apparaît, copie/colle le contenu ici dans un nouveau message.

Redémarre l'ordinateur.

Je vois que tu as CrystalDiskInfo, tous les disques sont en corrects ?

Vérifie l'état de santé de tes barettes de mémoire :
- memtest : vérifier barette de mémoire (malekal.com)
- memtest : vérifier barette de mémoire (CCM)

Nettoie les ventilateurs du processeur et carte graphique.

Merci beaucoup de votre aide,

Voici le rapport WhoCrashed : Welcome to WhoCrashed (HOME EDITION) v 6.01
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 a lot of system 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: PC-TANGUY
Windows version: Windows 10 , 10.0, build: 16299
Windows dir: C:\WINDOWS
Hardware: G750JM, ASUSTeK COMPUTER INC.
CPU: GenuineIntel Intel(R) Core(TM) i5-4200H CPU @ 2.80GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8467247104 bytes total

Crash Dump Analysis
Crash dumps are enabled on your computer. This system is not configured for complete or automatic crash dumps. For best results, configure your system to write out complete or automatic crash dumps. Select Tools->Crash Dump Configuration from the main menu to configure your system to write out complete memory dumps.

Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump

On Sat 31/03/2018 14:52:51 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\033118-44203-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x175510)
Bugcheck code: 0xEF (0xFFFFCC871C565580, 0x0, 0x0, 0x0)
Error: CRITICAL_PROCESS_DIED
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 critical system process died.
There is a possibility this problem was caused by a virus or other malware.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Sat 31/03/2018 14:37:27 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\033118-33406-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x175510)
Bugcheck code: 0xEF (0xFFFFA4854744C580, 0x0, 0x0, 0x0)
Error: CRITICAL_PROCESS_DIED
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 critical system process died.
There is a possibility this problem was caused by a virus or other malware.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Sat 31/03/2018 12:34:20 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\033118-43546-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x175510)
Bugcheck code: 0xEF (0xFFFFA602EC9E4080, 0x0, 0x0, 0x0)
Error: CRITICAL_PROCESS_DIED
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 critical system process died.
There is a possibility this problem was caused by a virus or other malware.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Sat 31/03/2018 12:24:59 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\033118-34359-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x175510)
Bugcheck code: 0xEF (0xFFFFE002F6909580, 0x0, 0x0, 0x0)
Error: CRITICAL_PROCESS_DIED
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 critical system process died.
There is a possibility this problem was caused by a virus or other malware.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Sat 31/03/2018 10:34:16 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\033118-39953-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x175510)
Bugcheck code: 0xEF (0xFFFFC98B1404F080, 0x0, 0x0, 0x0)
Error: CRITICAL_PROCESS_DIED
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 critical system process died.
There is a possibility this problem was caused by a virus or other malware.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

Conclusion
5 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.

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.

Puis voici les rapports FRST.txt, Shortcut.txt, Additionnal.txt dans l'ordre :
https://pjjoint.malekal.com/files.php?id=FRST_20180331_v9h13y13n9z6
https://pjjoint.malekal.com/files.php?id=20180331_m13g15c7c12z10
https://pjjoint.malekal.com/files.php?id=20180331_s95t12q14b12

Cordialement.

Merci,

J'ai désinstaller quelques programmes seulement j'utilise :
McAfee
MEGAsync
iCloud
WD Backup

Le fichier FRST me donne :

Résultats de correction de Farbar Recovery Scan Tool (x64) Version: 14.03.2018
Exécuté par Tanguy (01-04-2018 00:02:48) Run:1
Exécuté depuis D:\Bureau
Profils chargés: Tanguy (Profils disponibles: Tanguy)
Mode d'amorçage: Normal
==============================================

fixlist contenu:
CreateRestorePoint:
CloseProcesses:
R2 WsAppService; C:\Program Files (x86)\Wondershare\WAF\2.3.2.221\WsAppService.exe [459408 2017-02-10] (Wondershare)
HKLM-x32\...\Run: [Wondershare Helper Compact.exe] => C:\Program Files (x86)\Common Files\Wondershare\Wondershare Helper Compact\WSHelper.exe [2072928 2014-10-31] (Wondershare) Hosts:
C:\Program Files (x86)\Common Files\Wondershare
EmptyTemp:
RemoveProxy:
Reboot:

Le Point de restauration a été créé avec succès.
Processus fermé avec succès.
"HKLM\System\CurrentControlSet\Services\WsAppService" => supprimé(es) avec succès
WsAppService => service supprimé(es) avec succès
"HKLM\Software\WOW6432Node\Microsoft\Windows\CurrentVersion\Run\\Wondershare Helper Compact.exe" => supprimé(es) avec succès
C:\Program Files (x86)\Common Files\Wondershare => déplacé(es) avec succès

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

"HKU\.DEFAULT\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\Connections\\DefaultConnectionSettings" => supprimé(es) avec succès
"HKU\.DEFAULT\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\Connections\\SavedLegacySettings" => supprimé(es) avec succès
"HKU\S-1-5-21-2342091126-3007169168-3511568737-1001\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\Connections\\DefaultConnectionSettings" => supprimé(es) avec succès
"HKU\S-1-5-21-2342091126-3007169168-3511568737-1001\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\Connections\\SavedLegacySettings" => supprimé(es) avec succès

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

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

BITS transfer queue => 7888896 B
DOMStore, IE Recovery, AppCache, Feeds Cache, Thumbcache, IconCache => 286663157 B
Java, Flash, Steam htmlcache => 172255759 B
Windows/system/drivers => 19328638 B
Edge => 525754 B
Chrome => 62354051 B
Firefox => 362237655 B
Opera => 0 B

Temp, IE cache, history, cookies, recent:
Default => 0 B
Users => 0 B
ProgramData => 0 B
Public => 0 B
systemprofile => 456721 B
systemprofile32 => 0 B
LocalService => 10774 B
NetworkService => 363450 B
Tanguy => 16063927 B

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

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

Le système a dû redémarrer.

Fin de Fixlog 00:04:48

J'ai fais la vérification de la RAM avec Windows et rien à signaler.

De plus CrystalDiskInfo m'annonce que mes disques durs sont en état correct.

Cordialement.