Ecran bleu windows 10Fermé

Question

Bonjour a tous,

Je viens vers vous aujourd'hui car je suis face a un probleme.

En effet , je joue souvent en ligne et depuis un certain temps , lorsque je joue tout plante .

Je m'explique car il y 2 types de plantage.

=> le premier ou seul le jeu plante et je me retrouve sur le bureau et le jeu s"est fermé.
=> le deuxieme ( et c'est celui qui me chagrine le plus ) est que tout mon pc plante avec un écran bleu avec ce message que tout le monde connait bien "veuillez patientez nous collectons les données dues a votre erreur."

Mais en bas il y a aussi multiples codes erreurs qui ne sont pas les memes selon les plantages.

ceux qui reviennent le plus : whea uncorrectable error , SYSTEM_SERVICE_EXCEPTION (fltmgr.sys) , irql not less or equal .

J'ai mener quelques recherches sur le net avant de poster . mais aucune n'a résolu mon probleme.

J'ai penser à un probleme de mise a jour de logiciel , mais rien..
Défaillance d'une RAM , non plus..

je suis sous Windows 10 64 bits.

J'ai effectuer un memtest mais aucune erreur.
j'ai utiliser Bluescreeview , il me trouve une erreur sur ntoskrnl.exe
J'ai fait aussi un scan SPeecy voici le resultat = > http://speccy.piriform.com/results/HY0rkM7w5d47YZ0CtQoffj3

Dans l'attente d'une réponse de votre part

cordialement..


Configuration: Windows / Chrome 64.0.3282.186

Malekal_morte- · Answer

Salut,

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.

et :

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.

gu4rdian30 · Answer

bonjour , 

resultat who crashed =>

--------------------------------------------------------------------------------
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: DESKTOP-NM5S6IF
Windows version: Windows 10 , 10.0, build: 16299
Windows dir: C:\WINDOWS
Hardware: ASUSTeK COMPUTER INC., P8Z77-V LX2
CPU: GenuineIntel Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 8537444352 bytes total




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dumps are enabled on your computer. 

Crash dump directories: 
C:\WINDOWS
C:\WINDOWS\Minidump

The following dump files were found but could not be read. These files may be corrupt:
C:\WINDOWS\MEMORY.DMP




--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

One crash dump has been found and analyzed. Only 0 is included in this report. 
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. 



Rapports : 

https://pjjoint.malekal.com/files.php?id=FRST_20180307_g5r10h11g8c6

 https://pjjoint.malekal.com/files.php?id=20180307_r11p13w13c8t5

https://pjjoint.malekal.com/files.php?id=20180307_p9o10s6c11w15

j'espere que cela vous convient.



Cependant je tiens a préciser qu"hier j'ai fait un scan 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: DESKTOP-NM5S6IF
Windows version: Windows 10 , 10.0, build: 16299
Windows dir: C:\WINDOWS
Hardware: ASUSTeK COMPUTER INC., P8Z77-V LX2
CPU: GenuineIntel Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 8537444352 bytes total



Crash Dump Analysis

Crash dumps are enabled on your computer. 

Crash dump directories: 
C:\WINDOWS
C:\WINDOWS\Minidump

On Mon 05/03/2018 14:46:51 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\030518-6000-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x175430) 
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF802EF500AA3)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug. 
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out. 
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 05/03/2018 14:46:51 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!setjmpex+0x9599) 
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF802EF500AA3)
Error: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug. 
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out. 
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 05/03/2018 14:45:37 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\030518-4593-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x175430) 
Bugcheck code: 0xEF (0xFFFFB68068BE7340, 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 Sun 04/03/2018 21:24:55 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\030418-4609-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x175430) 
Bugcheck code: 0xA (0x7FF5CCC95000, 0x2, 0x0, 0xFFFFF8031F286140)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug. 
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 




Conclusion

4 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. 


entre temps j'ai supprimer pilotes clavier / souris 

cordialement

Malekal_morte- · Answer

Si tu as mis à jour tes pilotes avec Driver Cleaner, il a pu en mettre un pourri....
Faut pas utiliser ces programmes.

Désinstalle tout ça :
CCleaner
DAEMON Tools Pro
Driver Cleaner 3
ESET NOD32 Antivirus 

Evite aussi de télécharger n'importe quoi.

Antivirus Windows Defender a détecté un logiciel malveillant ou potentiellement indésirable.
Pour plus d’informations, reportez-vous aux éléments suivants :
https://www.microsoft.com/en-us/wdsi/threats/malware-encyclopedia-description?name=Trojan%3aWin32%2fTiggre!rfn&threatid=2147723625&enterprise=0
Nom : Trojan:Win32/Tiggre!rfn
ID : 2147723625
Gravité : Grave
Catégorie : Cheval de Troie
Chemin : file:_C:\Users\julien\Desktop\game.exe;webfile:_C:\Users\julien\Desktop\game.exe|about:internet|chrome.exe
Origine de la détection : Internet
Type de détection : Concret
Source de détection : Téléchargements et pièces jointes
Utilisateur : DESKTOP-NM5S6IF\julien
Nom du processus : Unknown
Version de la signature : AV: 1.261.1721.0, AS: 1.261.1721.0, NIS: 118.2.0.0
Version du moteur : AM: 1.1.14500.5, NIS: 2.1.14202.0

~~

Dans Cortana, tape invite de commandes, sur le résultat, fais un clic droit puis "Exécuter en tant qu'Administrateur"
Dans la fenêtre invite de commandes qui s'ouvre saisir chkdsk C: /F /R

Tape sur la touche entrée, il va te demander si tu veut le faire au redémarrage, tape o (oui), tape sur entrée et redémarre, au redémarrage un écran bleu va s'afficher avec "étape 1 sur 5"..., c'est normal ! Et il va rester ainsi d'étape en étape durant 1h ou 2h. C'est long mais nécessaire pour effectuer toutes les vérifications.


Vérifie déjà le disque dur : Comment vérifier la santé du disque dur
Par exemple avec CrystalDiskInfo.

gu4rdian30 · Answer

bonjour ,

J'ai télécharger certains de ces logiciels sur demande d'autres modérateurs de forum sur des sites concurrents. a qui doit on faire confiance? enfin bref.


Je vais faire en détail tout ce que tu m'as dit par contre jai 2 petits "hic":

Eset nod 32 et daemon tools pro sont des versions achetées, légalement je ve dire. sa m'embete de les supprimer . Mais si c'est indispensable pour que mon pc soit sain je le ferai.

pour le rapport chrystal : SSD 100% ok

par contre quand jouvre invité de commande en mode administrateur et que j'entre la commande il me dit ca :


(c) 2017 Microsoft Corporation. Tous droits réservés.

C:\WINDOWS\system32>chkdsk C: /F /R
Le type du système de fichiers est NTFS.
Impossible de verrouiller le lecteur en cours.

CHKDSK ne peut pas s’exécuter parce que le volume est utilisé
par un autre processus. Voulez-vous que ce volume soit
vérifié au prochain redémarrage du système ? (O/N) o

Ce volume sera vérifié au prochain redémarrage du système.

C:\WINDOWS\system32>

et il reboot normalement , il fait juste une analyse de C: qui dure 5 secondes et demarree windows normalement 


cordialement.

gu4rdian30 · Answer

re bonjour ,

je viens d'effectuer toutes les démarches et donc apres avoir lancer chkdsk C: /F /R  depuis l'invité de commande dans les options avancées.

il a bien lancer un scan etape 1 ,2 ,3 etc.. qui a pris 20 secondes 

Au final aucun probleme detecté.

Rapport chrystal : 100% ok

Ecran bleu windows 10

5 réponses

Newsletters