Écran bleu messages d'erreur
trocme95
Messages postés
1520
Statut
Membre
-
fabul Messages postés 42094 Date d'inscription Statut Modérateur Dernière intervention -
fabul Messages postés 42094 Date d'inscription Statut Modérateur Dernière intervention -
Bonjour, j'ai mon pc qui plante sous windows 10. J'ai fait des recherches en vain sur youtube. J'ai pris des photos mais je ne parviens pas à vous les montrer en utilisant le logo pour insérer une photo. donc comment, en 1er, dois-je procéder pour inclure des photos s'il vous plait?
En vous remerciant.
En vous remerciant.
Configuration: Windows / Chrome 99.0.4844.74
A voir également:
- Écran bleu messages d'erreur
- Écran bleu - Guide
- Dupliquer ecran - Guide
- Capture d'écran ipad - Guide
- Ecran d'accueil iphone - Guide
- Comment récupérer les messages supprimés sur whatsapp - Guide
44 réponses
- 1
- 2
- 3
Suivant
Résumé de la discussion
Un PC sous Windows 10 plante fréquemment et l'utilisateur souhaite savoir comment inclure des photos dans le message d'aide afin de mieux décrire le problème et les tentatives de résolution. Pour résoudre ces plantages, plusieurs répondants recommandent de mettre à jour tous les pilotes via Touslesdrivers ou DriversCloud et de se méfier des outils comme IOBit Driver Booster Free qui ajoutent des tâches planifiées. En cas de persistance, d'autres suggèrent d'utiliser Autoruns pour désactiver ces tâches planifiées et d'envisager une mise à jour des pilotes restants ou une réinstallation Windows si nécessaire. Une piste évoquée concerne l'analyse de dumps et l'identification d'un fichier problématique comme ntoskrnl.exe, mais elle apporte une information utile sur la source possible des plantages.
Le site du fabricant, (Mais ça peut être obsolète)
Tu peux essayer (Sans garanties) IOBit Driver booster Free
Mais le désinstaller après ou supprimer ses tâches planifiées qu'il ajoute si tu sais comment. (J'utilise Autoruns)
Touslesdrivers : Mes Drivers
https://fichiers2.touslesdrivers.com/Mes_Drivers_3.0.4.exe
Et DriversCloud
https://www.driverscloud.com/fr/demarrer
Tu peux essayer (Sans garanties) IOBit Driver booster Free
Mais le désinstaller après ou supprimer ses tâches planifiées qu'il ajoute si tu sais comment. (J'utilise Autoruns)
Touslesdrivers : Mes Drivers
https://fichiers2.touslesdrivers.com/Mes_Drivers_3.0.4.exe
Et DriversCloud
https://www.driverscloud.com/fr/demarrer
jeannets
Messages postés
28374
Date d'inscription
Statut
Contributeur
Dernière intervention
Ambassadeur
6 599
Bonjour,
Pour mettre des photos, il faut cliquer sur le symbole du paysage montagne, le 1er à droite en haut de ta réponse...
Si ça ne marche pas, tu le mets sur le site cjoint.com et nous colle le lien ici.
Ton fichier photo JPG doit etre sur ton ordinateur et ne pas etre trop volumineux.
mais ton écran bleu, c'est un blocage de windows... marque et modèle du PC et son âge
Pour mettre des photos, il faut cliquer sur le symbole du paysage montagne, le 1er à droite en haut de ta réponse...
Si ça ne marche pas, tu le mets sur le site cjoint.com et nous colle le lien ici.
Ton fichier photo JPG doit etre sur ton ordinateur et ne pas etre trop volumineux.
mais ton écran bleu, c'est un blocage de windows... marque et modèle du PC et son âge
Salut,
Pour analyser les crashdumps d'écran bleus, il faut utiliser un programme comme WhoCrashed Free Home Edition
https://www.commentcamarche.net/telecharger/utilitaires/23795-whocrashed-free-home-edition/
Les rapports se copient en texte.
Pour analyser les crashdumps d'écran bleus, il faut utiliser un programme comme WhoCrashed Free Home Edition
https://www.commentcamarche.net/telecharger/utilitaires/23795-whocrashed-free-home-edition/
Les rapports se copient en texte.
Merci tous deux d'abord je réponds à Jeannets:
https://cjoint.com/c/LCsw6krWmUS
https://cjoint.com/c/LCsxahfhcuS
https://cjoint.com/c/LCsxaUk5zES
Le pc est un hp pavillon, 14 ans d'age environ
https://cjoint.com/c/LCsw6krWmUS
https://cjoint.com/c/LCsxahfhcuS
https://cjoint.com/c/LCsxaUk5zES
Le pc est un hp pavillon, 14 ans d'age environ
Vous n’avez pas trouvé la réponse que vous recherchez ?
Posez votre question
jeannets
Messages postés
28374
Date d'inscription
Statut
Contributeur
Dernière intervention
Ambassadeur
6 599
bon, c'est mieux, tu réussi ainsi à mettre des images, même si ce n'est pas le chemin du forum..!
Pour ton écran bleu, c'est une anomalie de fonctionnement de windows... Comme le dit @fabul, tu peux en savoir un peu plus avec le logiciel WhoCrashed...tu peux le faire pour avoir son diagnostic..
Mais au vue de tes images, ton sujet a déja été évoqué sur ce forum, ici:
https://www.commentcamarche.net/informatique/windows/25143-ecran-bleu-windows-bsod-explications-solutions/
je t'invite donc à le parcourir.. et, pas à pas, faire une purification de ton PC... mettre à jour... désinstaller ce qui n'est pas utile avec "RevoUninstaller" https://www.commentcamarche.net/telecharger/utilitaires/19405-revo-uninstaller/ sans oublier le scan en mode avancé.
Ton PC, est il une tour ou un portable..?? car au dela de "Pavilion" il doit y avoir un N° de modèle..?? voir en dessous.
Si le disque est d'origine, il pourrait aussi cacher des défauts.....?? mais ce sera pour plus tard.
Pour ton écran bleu, c'est une anomalie de fonctionnement de windows... Comme le dit @fabul, tu peux en savoir un peu plus avec le logiciel WhoCrashed...tu peux le faire pour avoir son diagnostic..
Mais au vue de tes images, ton sujet a déja été évoqué sur ce forum, ici:
https://www.commentcamarche.net/informatique/windows/25143-ecran-bleu-windows-bsod-explications-solutions/
je t'invite donc à le parcourir.. et, pas à pas, faire une purification de ton PC... mettre à jour... désinstaller ce qui n'est pas utile avec "RevoUninstaller" https://www.commentcamarche.net/telecharger/utilitaires/19405-revo-uninstaller/ sans oublier le scan en mode avancé.
Ton PC, est il une tour ou un portable..?? car au dela de "Pavilion" il doit y avoir un N° de modèle..?? voir en dessous.
Si le disque est d'origine, il pourrait aussi cacher des défauts.....?? mais ce sera pour plus tard.
Il doit y avoir plusieurs réponses..Selon tous les Fichiers de blocage qui sont en mémoire depuis longtemps... C'est surtout le dernier ou les deux ou trois derniers qui sont important pour nous. Tu devrais y voir le message d'erreur ecrit en majuscule, je crois... tu peux le copier, même en Anglais et le coller ici...
Sinon, le corps du texte doit etre le même pour tous..
Il faut cliquer sur "Analyse" pour que ça marche...ensuite faire défiler la page vers le bas; c'est là que se trouve les résultats..
Sinon, le corps du texte doit etre le même pour tous..
Il faut cliquer sur "Analyse" pour que ça marche...ensuite faire défiler la page vers le bas; c'est là que se trouve les résultats..
Bonjour et merci. Voilà le copier-coller:
On Fri 18/03/2022 20:16:44 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\031822-48281-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F72E0)
Bugcheck code: 0x9F (0x3, 0xFFFFDD8E56BC0060, 0xFFFFF8026186E950, 0xFFFFDD8E5A743010)
Error: DRIVER_POWER_STATE_FAILURE
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 driver is in an inconsistent or invalid power state. A device object has been blocking an IRP for too long a time.
This is 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 Fri 18/03/2022 19:53:43 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\031822-46765-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F72E0)
Bugcheck code: 0x9F (0x3, 0xFFFF8481E83F2060, 0xFFFFF80516675BA0, 0xFFFF8481F0316010)
Error: DRIVER_POWER_STATE_FAILURE
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 driver is in an inconsistent or invalid power state. A device object has been blocking an IRP for too long a time.
This is 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 Fri 18/03/2022 12:21:12 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\031822-47718-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F72E0)
Bugcheck code: 0x9F (0x3, 0xFFFFD90B3CA78060, 0xFFFFF80612A75BA0, 0xFFFFD90B463AC010)
Error: DRIVER_POWER_STATE_FAILURE
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 driver is in an inconsistent or invalid power state. A device object has been blocking an IRP for too long a time.
This is 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.
The following dump files were found but could not be read. These files may be corrupted:
C:\WINDOWS\Minidump\031822-38312-01.dmp
On Fri 18/03/2022 20:16:44 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\031822-48281-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F72E0)
Bugcheck code: 0x9F (0x3, 0xFFFFDD8E56BC0060, 0xFFFFF8026186E950, 0xFFFFDD8E5A743010)
Error: DRIVER_POWER_STATE_FAILURE
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 driver is in an inconsistent or invalid power state. A device object has been blocking an IRP for too long a time.
This is 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 Fri 18/03/2022 19:53:43 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\031822-46765-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F72E0)
Bugcheck code: 0x9F (0x3, 0xFFFF8481E83F2060, 0xFFFFF80516675BA0, 0xFFFF8481F0316010)
Error: DRIVER_POWER_STATE_FAILURE
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 driver is in an inconsistent or invalid power state. A device object has been blocking an IRP for too long a time.
This is 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 Fri 18/03/2022 12:21:12 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\031822-47718-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F72E0)
Bugcheck code: 0x9F (0x3, 0xFFFFD90B3CA78060, 0xFFFFF80612A75BA0, 0xFFFFD90B463AC010)
Error: DRIVER_POWER_STATE_FAILURE
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 driver is in an inconsistent or invalid power state. A device object has been blocking an IRP for too long a time.
This is 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.
The following dump files were found but could not be read. These files may be corrupted:
C:\WINDOWS\Minidump\031822-38312-01.dmp
Un dump file n'a pu être lu, corrompu, ça aurait peut être aidé parce que les autres données ne pointent que vers un fichier Microsoft, ntoskrnl.exe et pas vers un driver autre, qui nous aurait aidé à savoir quel driver réinstaller.
À ta place je mettrais à jour tous les drivers (Pilotes) possibles.
À ta place je mettrais à jour tous les drivers (Pilotes) possibles.
Merci beaucoup. Je viens de rallumer le pc et il ne présente pas de panne. Mais j'ai peur que le problème resurvienne. Qu'en pensez vous ? En vous remerciant.
Je remarque que le son ne fonctionne pas. Le nom de ma carte son est M-AUDIO Fast track ultra. Dois-je la remplacer ou peut-on faire un réglage ?
jeannets
Messages postés
28374
Date d'inscription
Statut
Contributeur
Dernière intervention
Ambassadeur
6 599
Il faut faire tout ce qui est indiqué dans mon POST N°4 précédent surtout la lecture du lien CCM
La panne bleue reviendra certainement... C'est comme une maison de 1810, ça ne sert à rien de refaire les étagères alors que tous les murs doivent etre consolidés etc..etc.. ici, c'est windows en entier qui est à retaper...Donc ne tarde pas à attaquer tout ce qui est préconisé.
La panne bleue reviendra certainement... C'est comme une maison de 1810, ça ne sert à rien de refaire les étagères alors que tous les murs doivent etre consolidés etc..etc.. ici, c'est windows en entier qui est à retaper...Donc ne tarde pas à attaquer tout ce qui est préconisé.
jeannets
Messages postés
28374
Date d'inscription
Statut
Contributeur
Dernière intervention
Ambassadeur
6 599
OK, il te présente toutes les applications installées qu'il a trouvé...Tu clic droit sur l'une d'elle que tu veux désinstaller, et valide en cliquant sur "Désinstaller"... lorsqu'il a fini, tu coche "Avancé" puis sur SCAN il va chercher tous les résidus...et tu valide sur supprimer Tout doit etre coché et ce par deux fois.
Ensuite tu recommence sur une autre appli.... C'est ça l'usage utile de RevoUninstaller
Ensuite tu recommence sur une autre appli.... C'est ça l'usage utile de RevoUninstaller
il y en a environ 35. Je ne sais lesquelles choisir ? D'autant plus qu'ils y en a de windows. Merci.
jeannets
Messages postés
28374
Date d'inscription
Statut
Contributeur
Dernière intervention
Ambassadeur
6 599
Ça, c'est toi qui le sais. Les windows, il faut les laisser si c'est bien Windows... Sinon, le but n'est pas de supprimer pour le plaisir de supprimer...C'est de supprimer ce qui n'est pas indispensable... ou que tu ne te souviens pas les avoir installé toi même...ou des noms qui ne te disent rien...bref, ce qui est louche/suspect...
Pour ma part, j'en ai 274, alors ne sois pas effrayé avec tes 35, ils sont peut etre légitimes et c'est autre chose qui produit tes écrans bleus...As-tu fait le diagnostique avec le logiciel "WhoCrashed", ce serait intéressant de savoir ce qu'il à trouvé..??, surtout quand on cherche..!
Sur RevoUninstaller, tu as aussi un nettoyeur dans les menus du haut, c'est la deuxième case... Il te propose de nettoyer plusieurs rubrique de ton PC, suivant tes choix ou besoins, c'est aussi un autre points que tu pourrais utiliser...
Voici un Tuto sur ce logiciel https://www.logicielgratuit-tuto.com/nettoyage/revo-uninstaller/
et voici la vidéo https://www.youtube.com/watch?v=wlDzAQSs-tQ
Voila un peu d'occupation pour améliorer ton PC... Au point de vue Logiciel et espérer ne plus avoir d'écran bleu...
Pour ma part, j'en ai 274, alors ne sois pas effrayé avec tes 35, ils sont peut etre légitimes et c'est autre chose qui produit tes écrans bleus...As-tu fait le diagnostique avec le logiciel "WhoCrashed", ce serait intéressant de savoir ce qu'il à trouvé..??, surtout quand on cherche..!
Sur RevoUninstaller, tu as aussi un nettoyeur dans les menus du haut, c'est la deuxième case... Il te propose de nettoyer plusieurs rubrique de ton PC, suivant tes choix ou besoins, c'est aussi un autre points que tu pourrais utiliser...
Voici un Tuto sur ce logiciel https://www.logicielgratuit-tuto.com/nettoyage/revo-uninstaller/
et voici la vidéo https://www.youtube.com/watch?v=wlDzAQSs-tQ
Voila un peu d'occupation pour améliorer ton PC... Au point de vue Logiciel et espérer ne plus avoir d'écran bleu...
j'avais fait peut etre une erreur dans le copier-coller que j'ai posté hier. J'ai relancé l'analyse et voici les derniers (chronologiquement en partant du haut cette fois).
Crash dumps are enabled on your computer.
Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump
On Sat 19/03/2022 12:41:22 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\031922-47546-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F72E0)
Bugcheck code: 0x9F (0x3, 0xFFFFB98D48604060, 0xFFFFF80175E6E950, 0xFFFFB98D4E4F24B0)
Error: DRIVER_POWER_STATE_FAILURE
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 driver is in an inconsistent or invalid power state. A device object has been blocking an IRP for too long a time.
This is 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 19/03/2022 12:41:22 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!MmTrimAllSystemPagableMemory+0x28907)
Bugcheck code: 0x9F (0x3, 0xFFFFB98D48604060, 0xFFFFF80175E6E950, 0xFFFFB98D4E4F24B0)
Error: DRIVER_POWER_STATE_FAILURE
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state. A device object has been blocking an IRP for too long a time.
This is 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 Fri 18/03/2022 21:21:50 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\031822-63906-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F72E0)
Bugcheck code: 0x9F (0x3, 0xFFFFA38460DA0060, 0xFFFFE0086C429950, 0xFFFFA38464FC7980)
Error: DRIVER_POWER_STATE_FAILURE
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 driver is in an inconsistent or invalid power state. A device object has been blocking an IRP for too long a time.
This is 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.
Crash dumps are enabled on your computer.
Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump
On Sat 19/03/2022 12:41:22 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\031922-47546-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F72E0)
Bugcheck code: 0x9F (0x3, 0xFFFFB98D48604060, 0xFFFFF80175E6E950, 0xFFFFB98D4E4F24B0)
Error: DRIVER_POWER_STATE_FAILURE
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 driver is in an inconsistent or invalid power state. A device object has been blocking an IRP for too long a time.
This is 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 19/03/2022 12:41:22 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!MmTrimAllSystemPagableMemory+0x28907)
Bugcheck code: 0x9F (0x3, 0xFFFFB98D48604060, 0xFFFFF80175E6E950, 0xFFFFB98D4E4F24B0)
Error: DRIVER_POWER_STATE_FAILURE
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state. A device object has been blocking an IRP for too long a time.
This is 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 Fri 18/03/2022 21:21:50 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\031822-63906-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F72E0)
Bugcheck code: 0x9F (0x3, 0xFFFFA38460DA0060, 0xFFFFE0086C429950, 0xFFFFA38464FC7980)
Error: DRIVER_POWER_STATE_FAILURE
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 driver is in an inconsistent or invalid power state. A device object has been blocking an IRP for too long a time.
This is 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.
Il faudrait tous les avoir, parce que les derniers ne disent rien qui me parle.
Juste ntoskrnl.exe qui est le Kernel, le cœur de Windows
Il nous manque des données sur ce qui fait planter le kernel
Juste ntoskrnl.exe qui est le Kernel, le cœur de Windows
Il nous manque des données sur ce qui fait planter le kernel
Crash Dump Analysis
--------------------------------------------------------------------------------
Welcome to WhoCrashed (Home Edition) v 6.70
--------------------------------------------------------------------------------
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: HP
Windows version: Windows 10, 10.0, version 2009, build: 19042
Windows dir: C:\WINDOWS
Hardware: WE277AA-ABF p6352fr, HP-Pavilion, PEGATRON CORPORATION, EVANS
CPU: GenuineIntel Pentium(R) Dual-Core CPU E5300 @ 2.60GHz 8664, level: 6
2 logical processors, active mask: 3
RAM: 4294168576 bytes (4,0GB)
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dumps are enabled on your computer.
Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump
On Sat 19/03/2022 12:41:22 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\031922-47546-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F72E0)
Bugcheck code: 0x9F (0x3, 0xFFFFB98D48604060, 0xFFFFF80175E6E950, 0xFFFFB98D4E4F24B0)
Error: DRIVER_POWER_STATE_FAILURE
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 driver is in an inconsistent or invalid power state. A device object has been blocking an IRP for too long a time.
This is 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 19/03/2022 12:41:22 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!MmTrimAllSystemPagableMemory+0x28907)
Bugcheck code: 0x9F (0x3, 0xFFFFB98D48604060, 0xFFFFF80175E6E950, 0xFFFFB98D4E4F24B0)
Error: DRIVER_POWER_STATE_FAILURE
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state. A device object has been blocking an IRP for too long a time.
This is 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 Fri 18/03/2022 21:21:50 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\031822-63906-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F72E0)
Bugcheck code: 0x9F (0x3, 0xFFFFA38460DA0060, 0xFFFFE0086C429950, 0xFFFFA38464FC7980)
Error: DRIVER_POWER_STATE_FAILURE
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 driver is in an inconsistent or invalid power state. A device object has been blocking an IRP for too long a time.
This is 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 Fri 18/03/2022 21:04:37 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\031822-44312-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F72E0)
Bugcheck code: 0x9F (0x3, 0xFFFFAE0971986060, 0xFFFFF8021C06E950, 0xFFFFAE09771575E0)
Error: DRIVER_POWER_STATE_FAILURE
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 driver is in an inconsistent or invalid power state. A device object has been blocking an IRP for too long a time.
This is 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 Fri 18/03/2022 20:56:53 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\031822-45515-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F72E0)
Bugcheck code: 0x9F (0x3, 0xFFFF9C810302A060, 0xFFFFF80485875BA0, 0xFFFF9C8103DC6010)
Error: DRIVER_POWER_STATE_FAILURE
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 driver is in an inconsistent or invalid power state. A device object has been blocking an IRP for too long a time.
This is 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 Fri 18/03/2022 20:40:48 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\031822-52859-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F72E0)
Bugcheck code: 0x9F (0x3, 0xFFFFCA09200E0060, 0xFFFFF58AA9A29950, 0xFFFFCA092044D010)
Error: DRIVER_POWER_STATE_FAILURE
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 driver is in an inconsistent or invalid power state. A device object has been blocking an IRP for too long a time.
This is 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 Fri 18/03/2022 20:16:44 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\031822-48281-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F72E0)
Bugcheck code: 0x9F (0x3, 0xFFFFDD8E56BC0060, 0xFFFFF8026186E950, 0xFFFFDD8E5A743010)
Error: DRIVER_POWER_STATE_FAILURE
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 driver is in an inconsistent or invalid power state. A device object has been blocking an IRP for too long a time.
This is 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 Fri 18/03/2022 19:53:43 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\031822-46765-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F72E0)
Bugcheck code: 0x9F (0x3, 0xFFFF8481E83F2060, 0xFFFFF80516675BA0, 0xFFFF8481F0316010)
Error: DRIVER_POWER_STATE_FAILURE
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 driver is in an inconsistent or invalid power state. A device object has been blocking an IRP for too long a time.
This is 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 Fri 18/03/2022 12:21:12 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\031822-47718-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F72E0)
Bugcheck code: 0x9F (0x3, 0xFFFFD90B3CA78060, 0xFFFFF80612A75BA0, 0xFFFFD90B463AC010)
Error: DRIVER_POWER_STATE_FAILURE
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 driver is in an inconsistent or invalid power state. A device object has been blocking an IRP for too long a time.
This is 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.
The following dump files were found but could not be read. These files may be corrupted:
C:\WINDOWS\Minidump\031822-38312-01.dmp
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
On your computer a total of 53 crash dumps have been found. Only 10 have been analyzed. Only 9 are included in this report. If dump files are found and they could not be analuzed, it means they are corrupted. Because crash dumps are an emergency measure it is not uncommon for this to happen, however often it points to a problem in the storage stack. It is suggested that you run CHKDSK on your system drive to check your drive for errors.
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.
--------------------------------------------------------------------------------
Welcome to WhoCrashed (Home Edition) v 6.70
--------------------------------------------------------------------------------
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: HP
Windows version: Windows 10, 10.0, version 2009, build: 19042
Windows dir: C:\WINDOWS
Hardware: WE277AA-ABF p6352fr, HP-Pavilion, PEGATRON CORPORATION, EVANS
CPU: GenuineIntel Pentium(R) Dual-Core CPU E5300 @ 2.60GHz 8664, level: 6
2 logical processors, active mask: 3
RAM: 4294168576 bytes (4,0GB)
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dumps are enabled on your computer.
Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump
On Sat 19/03/2022 12:41:22 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\031922-47546-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F72E0)
Bugcheck code: 0x9F (0x3, 0xFFFFB98D48604060, 0xFFFFF80175E6E950, 0xFFFFB98D4E4F24B0)
Error: DRIVER_POWER_STATE_FAILURE
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 driver is in an inconsistent or invalid power state. A device object has been blocking an IRP for too long a time.
This is 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 19/03/2022 12:41:22 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!MmTrimAllSystemPagableMemory+0x28907)
Bugcheck code: 0x9F (0x3, 0xFFFFB98D48604060, 0xFFFFF80175E6E950, 0xFFFFB98D4E4F24B0)
Error: DRIVER_POWER_STATE_FAILURE
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state. A device object has been blocking an IRP for too long a time.
This is 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 Fri 18/03/2022 21:21:50 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\031822-63906-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F72E0)
Bugcheck code: 0x9F (0x3, 0xFFFFA38460DA0060, 0xFFFFE0086C429950, 0xFFFFA38464FC7980)
Error: DRIVER_POWER_STATE_FAILURE
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 driver is in an inconsistent or invalid power state. A device object has been blocking an IRP for too long a time.
This is 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 Fri 18/03/2022 21:04:37 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\031822-44312-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F72E0)
Bugcheck code: 0x9F (0x3, 0xFFFFAE0971986060, 0xFFFFF8021C06E950, 0xFFFFAE09771575E0)
Error: DRIVER_POWER_STATE_FAILURE
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 driver is in an inconsistent or invalid power state. A device object has been blocking an IRP for too long a time.
This is 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 Fri 18/03/2022 20:56:53 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\031822-45515-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F72E0)
Bugcheck code: 0x9F (0x3, 0xFFFF9C810302A060, 0xFFFFF80485875BA0, 0xFFFF9C8103DC6010)
Error: DRIVER_POWER_STATE_FAILURE
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 driver is in an inconsistent or invalid power state. A device object has been blocking an IRP for too long a time.
This is 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 Fri 18/03/2022 20:40:48 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\031822-52859-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F72E0)
Bugcheck code: 0x9F (0x3, 0xFFFFCA09200E0060, 0xFFFFF58AA9A29950, 0xFFFFCA092044D010)
Error: DRIVER_POWER_STATE_FAILURE
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 driver is in an inconsistent or invalid power state. A device object has been blocking an IRP for too long a time.
This is 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 Fri 18/03/2022 20:16:44 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\031822-48281-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F72E0)
Bugcheck code: 0x9F (0x3, 0xFFFFDD8E56BC0060, 0xFFFFF8026186E950, 0xFFFFDD8E5A743010)
Error: DRIVER_POWER_STATE_FAILURE
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 driver is in an inconsistent or invalid power state. A device object has been blocking an IRP for too long a time.
This is 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 Fri 18/03/2022 19:53:43 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\031822-46765-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F72E0)
Bugcheck code: 0x9F (0x3, 0xFFFF8481E83F2060, 0xFFFFF80516675BA0, 0xFFFF8481F0316010)
Error: DRIVER_POWER_STATE_FAILURE
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 driver is in an inconsistent or invalid power state. A device object has been blocking an IRP for too long a time.
This is 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 Fri 18/03/2022 12:21:12 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\031822-47718-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F72E0)
Bugcheck code: 0x9F (0x3, 0xFFFFD90B3CA78060, 0xFFFFF80612A75BA0, 0xFFFFD90B463AC010)
Error: DRIVER_POWER_STATE_FAILURE
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 driver is in an inconsistent or invalid power state. A device object has been blocking an IRP for too long a time.
This is 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.
The following dump files were found but could not be read. These files may be corrupted:
C:\WINDOWS\Minidump\031822-38312-01.dmp
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
On your computer a total of 53 crash dumps have been found. Only 10 have been analyzed. Only 9 are included in this report. If dump files are found and they could not be analuzed, it means they are corrupted. Because crash dumps are an emergency measure it is not uncommon for this to happen, however often it points to a problem in the storage stack. It is suggested that you run CHKDSK on your system drive to check your drive for errors.
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.
La seule chose qui reste à faite c'est installer tous les drivers possibles.
https://forums.commentcamarche.net/forum/affich-37551707-ecran-bleu-messages-d-erreur#17
Ou encore réinstaller Windows, mais c'est peut être trop.
https://forums.commentcamarche.net/forum/affich-37551707-ecran-bleu-messages-d-erreur#17
Ou encore réinstaller Windows, mais c'est peut être trop.
- 1
- 2
- 3
Suivant
Il ajoute des tâches planifiées dans Windows pour démarrer automatiquement, mais entre toi et moi, quand est ce qu'on a besoin de ça ???
Tu peux les décocher dans la section Scheduled Tasks de Autoruns 13.98
https://filehippo.com/fr/download_autoruns/13.98/?ex=BB-2188.0