Erreur smiley triste redémarrage sous Windows 10
elliott.dero
Messages postés
5
Date d'inscription
Statut
Membre
Dernière intervention
-
elliott.dero Messages postés 5 Date d'inscription Statut Membre Dernière intervention -
elliott.dero Messages postés 5 Date d'inscription Statut Membre Dernière intervention -
Bonjour,
Je viens vers vous car mon ordinateur portable ne cesse de redémarrer avec ce fameux écran bleu au smiley triste (problème BSOD) et étant en plein rapport de stage donc grand besoin d'utilisation, cela devient très embêtant.
M'étant renseigné grâce aux différentes discussions sur le sujet j'ai essayé de regarder dans l'historique des mises à jours windows qui pourraient poser problème et je n'ai rien trouvé.
J'ai téléchargé le logiciel Whocrashed qui m'a fournit un rapport avec différents types d'erreur mais je vous avoue que je n'y comprends pas grand chose... :/
Si quelqu'un de fort aimable pouvait me venir en aide pour décoder ce rapport et m'indiquer une marche à suivre je lui en serait très reconnaissant.
Merci d'avance.
Elliott
Ci-dessous le copy-paste du rapport: (désolé pour le pavé)
System Information (local)
--------------------------------------------------------------------------------
Computer name: PC-ASUS
Windows version: Windows 10 , 10.0, build: 10586
Windows dir: C:\WINDOWS
Hardware: S300CA, ASUSTeK COMPUTER INC.
CPU: GenuineIntel Intel(R) Core(TM) i5-3317U CPU @ 1.70GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 4175122432 bytes total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Tue 21/06/2016 22:43:53 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\062216-26687-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1427A0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800206AF850, 0xFFFFD0002326A3F0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 Tue 21/06/2016 19:02:38 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\062116-97218-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1427A0)
Bugcheck code: 0xEF (0xFFFFE0013C3D1280, 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 Tue 21/06/2016 18:47:19 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\062116-43640-01.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
A third party driver was identified as the probable root cause of this system error.
Google query: CUSTOM_ERROR
On Tue 21/06/2016 18:12:38 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\062116-26234-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1427A0)
Bugcheck code: 0x7A (0x5, 0x0, 0xC000, 0xFFFFE0003EC92510)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Tue 21/06/2016 09:48:44 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\062116-76265-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1427A0)
Bugcheck code: 0xEF (0xFFFFE002040B67C0, 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 Tue 21/06/2016 09:43:00 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\062116-73000-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1427A0)
Bugcheck code: 0x7A (0x4, 0x0, 0xFFFFE0014F048700, 0x1FA84712270)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Tue 21/06/2016 08:25:50 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\062116-38140-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1427A0)
Bugcheck code: 0xC5 (0x5A266676572, 0x2, 0x0, 0xFFFFF8022FAB2850)
Error: DRIVER_CORRUPTED_EXPOOL
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 the system attempted to access invalid memory at a process IRQL that was too high.
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
7 crash dumps have been found and analyzed.
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.
Je viens vers vous car mon ordinateur portable ne cesse de redémarrer avec ce fameux écran bleu au smiley triste (problème BSOD) et étant en plein rapport de stage donc grand besoin d'utilisation, cela devient très embêtant.
M'étant renseigné grâce aux différentes discussions sur le sujet j'ai essayé de regarder dans l'historique des mises à jours windows qui pourraient poser problème et je n'ai rien trouvé.
J'ai téléchargé le logiciel Whocrashed qui m'a fournit un rapport avec différents types d'erreur mais je vous avoue que je n'y comprends pas grand chose... :/
Si quelqu'un de fort aimable pouvait me venir en aide pour décoder ce rapport et m'indiquer une marche à suivre je lui en serait très reconnaissant.
Merci d'avance.
Elliott
Ci-dessous le copy-paste du rapport: (désolé pour le pavé)
System Information (local)
--------------------------------------------------------------------------------
Computer name: PC-ASUS
Windows version: Windows 10 , 10.0, build: 10586
Windows dir: C:\WINDOWS
Hardware: S300CA, ASUSTeK COMPUTER INC.
CPU: GenuineIntel Intel(R) Core(TM) i5-3317U CPU @ 1.70GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 4175122432 bytes total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Tue 21/06/2016 22:43:53 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\062216-26687-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1427A0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800206AF850, 0xFFFFD0002326A3F0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 Tue 21/06/2016 19:02:38 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\062116-97218-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1427A0)
Bugcheck code: 0xEF (0xFFFFE0013C3D1280, 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 Tue 21/06/2016 18:47:19 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\062116-43640-01.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
A third party driver was identified as the probable root cause of this system error.
Google query: CUSTOM_ERROR
On Tue 21/06/2016 18:12:38 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\062116-26234-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1427A0)
Bugcheck code: 0x7A (0x5, 0x0, 0xC000, 0xFFFFE0003EC92510)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Tue 21/06/2016 09:48:44 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\062116-76265-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1427A0)
Bugcheck code: 0xEF (0xFFFFE002040B67C0, 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 Tue 21/06/2016 09:43:00 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\062116-73000-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1427A0)
Bugcheck code: 0x7A (0x4, 0x0, 0xFFFFE0014F048700, 0x1FA84712270)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Tue 21/06/2016 08:25:50 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\062116-38140-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1427A0)
Bugcheck code: 0xC5 (0x5A266676572, 0x2, 0x0, 0xFFFFF8022FAB2850)
Error: DRIVER_CORRUPTED_EXPOOL
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 the system attempted to access invalid memory at a process IRQL that was too high.
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
7 crash dumps have been found and analyzed.
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.
A voir également:
- Erreur smiley triste redémarrage sous Windows 10
- Clé d'activation windows 10 - Guide
- Forcer redemarrage windows - Guide
- Restauration systeme windows 10 - Guide
- Windows 10 ne démarre plus - Guide
- Windows 10 gratuit - Accueil - Mise à jour
1 réponse
Salut
grossomodo,ça parle de pilote non mis a jour et de possible infection?
alors,désinfecter et mettre a jour ^^
pour la désinfection,passe par le forum virus /sécurité,un contributeur regardera ça de plus près!
pour les maj,passe par windows update et redémarre ton pc !
c'est une mise a niveau depuis W7/8.1 ton W10?
si oui,ça m’étonne pas,une clean installe est la meilleur façon d'avoir un W10 opérationnel ^^
grossomodo,ça parle de pilote non mis a jour et de possible infection?
alors,désinfecter et mettre a jour ^^
pour la désinfection,passe par le forum virus /sécurité,un contributeur regardera ça de plus près!
pour les maj,passe par windows update et redémarre ton pc !
c'est une mise a niveau depuis W7/8.1 ton W10?
si oui,ça m’étonne pas,une clean installe est la meilleur façon d'avoir un W10 opérationnel ^^
Si je comprends bien pour une clean install je mets tout sur DD externe je formate et installe un "nouveau windows 10 tout beau tout neuf" c'est bien ça ? :)
Encore merci de ton aide.
ou passe par l option réinitialiser ,ça réinstalle (logiquement) W10 sans perte de fichiers,tu a le choix de les conserver ou pas ^^
perso,j'ai réinstallé proprement,et mon W10 tourne parfaitement (W8 d'origine)
coupe C: 100/150 GO max pour Windows et le reste D: pour tes données,tu a une option pour envoyer tout ça vers D: (ou autre) une fois W10 installé(paramètre,système,stockage)en cas de réinstallation/réparation/plantage,tu ne perd rien comme ça (sauf si le DD lâche ,bien sur)
installe la 1511 directement ,tant qu'a faire,ici,en bas de page
https://www.microsoft.com/fr-fr/software-download/techbench
voila,tu sais a peu près tout ^^