Ecran bleu à répétition

Question

Bonsoir,

Depuis près de deux mois j'ai des soucis d'écran bleu; j'ai un nouveau pc, MSI GE 60, j'ai fais les updates drivers, Windows, j'ai scan mon pc des virus, check mon disque et la mémoire vive, j'ai obtenu les erreur sur minidump files que je pourrais partager avec la configuration du pc.

j'ai pas les compétences techniques pour les lires; donc si quelqu'un peux m'aider à diagnostiquer le problème svp.

Merci d'avance;
Rayz

Lenox-Lewis · Answer

Bonjour.

Installer Whocrashed afin d'analyser les écrans bleus: https://www.malekal.com/tutoriel-whocrashed/

Rayz16 · Answer

Bonsoir, merci Lenox,


--------------------------------------------------------------------------------
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: RAYZPC
Windows version: Windows 10 , 10.0, build: 15063
Windows dir: C:\WINDOWS
Hardware: GE60 2PC, Micro-Star International Co., Ltd., MS-16GF
CPU: GenuineIntel Intel(R) Core(TM) i7-4700HQ CPU @ 2.40GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 17096232960 bytes total




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Sun 08/10/2017 17:40:54 your computer crashed
crash dump file: C:\WINDOWS\Minidump\100817-20375-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1855C) 
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8027102255C, 0xFFFFDE010BD76588, 0xFFFFDE010BD75DD0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32
toskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 



On Sun 08/10/2017 17:40:54 your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntfs.sys (NTFS+0x865A) 
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF8027102255C, 0xFFFFDE010BD76588, 0xFFFFDE010BD75DD0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers
tfs.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du système de fichiers NT
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
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 that cannot be identified at this time. 



On Sat 07/10/2017 18:30:39 your computer crashed
crash dump file: C:\WINDOWS\Minidump\100717-25781-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C580) 
Bugcheck code: 0xEF (0xFFFFA709CCC84640, 0x0, 0x0, 0x0)
Error: CRITICAL_PROCESS_DIED
file path: C:\WINDOWS\system32
toskrnl.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 07/10/2017 11:23:59 your computer crashed
crash dump file: C:\WINDOWS\Minidump\100717-16531-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C580) 
Bugcheck code: 0xC1 (0xFFFF9401510C0DB0, 0xFFFF9401510C086E, 0xBBC24C, 0x32)
Error: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION
file path: C:\WINDOWS\system32
toskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the driver wrote to an invalid section of the special pool.
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 that cannot be identified at this time. 



On Sat 07/10/2017 05:14:03 your computer crashed
crash dump file: C:\WINDOWS\Minidump\100717-18656-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C580) 
Bugcheck code: 0xC1 (0xFFFFF88C7F594F50, 0xFFFFF88C7F59486E, 0xBD40A8, 0x32)
Error: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION
file path: C:\WINDOWS\system32
toskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the driver wrote to an invalid section of the special pool.
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 that cannot be identified at this time. 





--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

34 crash dumps have been found and analyzed. Only 5 are included in this report. 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.

Lenox-Lewis · Answer

Je vois, il faut la version payante pour afficher le reste, mettre à jour les drivers avec Driverscloud: https://www.malekal.com/driverscloud-mettre-a-jour-ses-pilotes/

Lenox-Lewis · Answer

Il y a BlueScreenview, voici un tuto: https://forum.malekal.com/viewtopic.php?t=33290&start=

Lenox-Lewis · Answer

Appuyer sur les touches WINDOWS et X
Sur la gauche Invite de commandes (admin) ou Powershell (admin)
Dans la fenêtre d'invite, taper chkdsk  /f  /r
Répondre O(ui), l'analyse se fera au redémarrage du PC.

Rayz16 · Answer

Quelqu'un pourrait m'aider svp ! j'ai toujours le même problème et apparemment lenox n'est plus de la discussion  

Merci d'avance

Malekal_morte- · Answer

Salut,

pour voir ce qui tourne :

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.

Rayz16 · Answer

Bonjour,

tout d'abord merci d'avoir pris le soin de répondre.

Voici les liens demandés :

https://pjjoint.malekal.com/files.php?id=20171021_j9b15s107k12

https://pjjoint.malekal.com/files.php?id=FRST_20171021_l5z5s14n15z8

https://pjjoint.malekal.com/files.php?id=20171021_x10y11b9o10p8

j'espère que ça aidera.

Rayz

Malekal_morte- · Answer

Error: (10/21/2017 03:07:53 PM) (Source: Ntfs) (EventID: 55) (User: AUTORITE NT)
Description: Une défaillance a été détectée dans la structure du système de fichiers sur le volume C:.

La nature exacte de la défaillance est inconnue. Les structures de système de fichiers doivent être analysées en ligne. 
 


Fais un checkdisk en ligne de commandes.
Il faut saisir la commande suivante dans une invite de commande en administrateur :
chkdsk c: /R /F
Cela va te propose de faire l'analyse au redémarrage de Windows, accepte.


et :

Error: (10/21/2017 11:43:15 AM) (Source: DCOM) (EventID: 10016) (User: AUTORITE NT)
Description: Les paramètres d’autorisation propres à l’application n’accordent pas l’autorisation Local Activation pour l’application serveur COM avec le CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 et l’APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 au SID AUTORITE NT\Système de l’utilisateur (S-1-5-18) depuis l’adresse LocalHost (avec LRPC) s’exécutant dans le SID Non disponible du conteneur d’applications (Non disponible). Cette autorisation de sécurité peut être modifiée à l’aide de l’outil d’administration Services de composants.

Suis les instructions de cette page : https://www.malekal.com/corriger-erreur-dcom-windows-10/

Rayz16 · Answer

Bonsoir,

J'ai fais les deux Manips ! 

Maintenant faudra que je vérifie la stabilité en utilisant le pc? 

Je reste à l'écoute de tes instructions je te remercie bro !

Rayz

Malekal_morte- · Answer

Whocrashed indique le MFT est endommagé.
Donc comme dit précédemment, faut formater, la partition a l'air morte.

et en plus, tu as aussi des plantages NVIDIA. 


Sauvegarde les données importantes.

Réinstaller Windows 10 :

Suis ce tuto qui explique comment installer Windows 10 : comment installer Windows 10.
Toutes les étapes sont données de A à Z avec des conseils à la fin pour sécuriser Windows 10.

Les étapes sont en gros :

- Tu télécharges l'ISO d'installation de Windows 10 : https://www.microsoft.com/fr-fr/software-download/windows10 (d'autres méthodes de téléchargement : https://www.malekal.com/telecharger-iso-windows/ ).
- Créer le support d'installation avec Media Creation Tool
- Démarre dessus en modifiant la séquence de démarrage et indiquer la clé USB ou le DVD : Comment démarrer l'ordinateur sur clé USB
Si la clé ne fonctionne pas, tente d'en refaire une avec Rufus : comment télécharger Rufus - voir ce tuto pour les détails : comment créer une clé USB d'installation de Windows
- Laisse toi guider pour installer Windows 10.  
- Choisis personnaliser (pas mise à niveau)
- Supprime toutes les partitions principale et système, recréé la partition pour installer Windows.
- Clic sur suivant, cela va te dire qu'un Windows est déjà installé et qu'il va être déplacé.
- Suis la procédure d'installation de Windows à l'aide du tutoriel plus haut.

Une fois Windows installé, je te conseille de suivre ces conseils pour bien configurer et utiliser Windows : Conseils après réinstallation de Windows.

 
Veuillez appuyer sur une touche pour continuer la désinfection...

Rayz16 · Answer

La méthode ultime, je savais que j'allais partir sur une réinstallation, j'ai pas de disque dure externe c'est pour cela que je temporisé !

Je penses que je le ferais demain; je reviendrais probablement t'informer si celà est récurrent ou pas.

je te remercie Bro pour ton support.

Cordiales salutations, 
Rayz

Rayz16 · Answer

Voici le rapport Who crached :


--------------------------------------------------------------------------------
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: RAYZ-PC
Windows version: Windows 10 , 10.0, build: 16299
Windows dir: C:\Windows
Hardware: GE60 2PC, Micro-Star International Co., Ltd., MS-16GF
CPU: GenuineIntel Intel(R) Core(TM) i7-4700HQ CPU @ 2.40GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 17096232960 bytes total




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Mon 30/10/2017 2:43:05 AM your computer crashed
crash dump file: C:\Windows\Minidump\103017-23750-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x163960) 
Bugcheck code: 0x1A (0x41792, 0xFFFFFD0000013928, 0x20000000000000, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32
toskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
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 30/10/2017 2:43:05 AM your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0) 
Bugcheck code: 0x1A (0x41792, 0xFFFFFD0000013928, 0x20000000000000, 0x0)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred.
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.

Malekal_morte- · Answer

Tu as quoi comme périphériques branchés or clavier ou souris ?
Faudrait sinon tester une barrette de mémoire à la fois... voir si les BSOD perdurent.

Ecran bleu à répétition

14 réponses

Discussions similaires

Newsletters