écran bleu intempestif, comment rectifier ?
35Matt35
Messages postés
16
Date d'inscription
Statut
Membre
Dernière intervention
-
jumulka Messages postés 12157 Date d'inscription Statut Membre Dernière intervention -
jumulka Messages postés 12157 Date d'inscription Statut Membre Dernière intervention -
bonsoir,
je ne sais pas si je suis au bon endroit, alors pardonnez-moi par avance si ce n'est pas le cas...
Fréquemment, mon pc (un Asus i3 sous Win10) me jette un bel écran bleu avec un smiley tout dégueu qui me dit que mon pc a commis une erreur. Mon pc redémarre ensuite normalement (quoi qu'il met de plus en plus de temps pour le faire)
Je ne sais trop que faire...
Merci d'avance pour vos conseils.
je ne sais pas si je suis au bon endroit, alors pardonnez-moi par avance si ce n'est pas le cas...
Fréquemment, mon pc (un Asus i3 sous Win10) me jette un bel écran bleu avec un smiley tout dégueu qui me dit que mon pc a commis une erreur. Mon pc redémarre ensuite normalement (quoi qu'il met de plus en plus de temps pour le faire)
Je ne sais trop que faire...
Merci d'avance pour vos conseils.
A voir également:
- écran bleu intempestif, comment rectifier ?
- Supprimer rond bleu whatsapp - Guide
- Double ecran - Guide
- Écran bleu - Guide
- Capture d'écran whatsapp - Accueil - Messagerie instantanée
- Retourner ecran pc - Guide
3 réponses
Bonsoir,
Est-ce un pc portable (j'imagine que oui) ?
essaye de mettre à jour des drivers depuis le site Asus pour ton pc (il faut vérifier le modèle)
et regarde ici : https://forums.commentcamarche.net/forum/affich-4608196-ecran-bleu-driver-power-state-failure
ça pourrait t'aider.
Cordialement.
Est-ce un pc portable (j'imagine que oui) ?
essaye de mettre à jour des drivers depuis le site Asus pour ton pc (il faut vérifier le modèle)
et regarde ici : https://forums.commentcamarche.net/forum/affich-4608196-ecran-bleu-driver-power-state-failure
ça pourrait t'aider.
Cordialement.
bonsoir,
il s'agit bien d'un ordinateur portable.
Les pilotes, tous ceux que j'ai pu tester, sont à jour et mis à jour automatiquement.
le problème survient indépendamment des réglages de périodes de veille sur secteur/batterie (paramètres affichage/alim).
J'ai remarqué que cela se produit souvent lorsque plusieurs applis tournent (ex : office + chrome + musique). Mais parfois cela se produit aussi à la reprise d'une mise en veille.
il s'agit bien d'un ordinateur portable.
Les pilotes, tous ceux que j'ai pu tester, sont à jour et mis à jour automatiquement.
le problème survient indépendamment des réglages de périodes de veille sur secteur/batterie (paramètres affichage/alim).
J'ai remarqué que cela se produit souvent lorsque plusieurs applis tournent (ex : office + chrome + musique). Mais parfois cela se produit aussi à la reprise d'une mise en veille.
Salut, si tu parles de mise à jour Windows update il met pas tout à jour...
Essayes d'aller sur le site constructeur tu choisis ton modèle de pc et tu mets à jour tout ce que tu peux (Bios, chipset, audio, graphique ect...).
Mais ça ressemble à un soucis de RAM si plusieurs appli le font planter ET à la reprise de veille ça plante aussi...
Dans un premier temps fais ce que je t'ai dit et ensuite test de stresser l'ordi en lançant beaucoup d'applis. Mais essayes aussi de voir le liens que je t'ai donné plus haut !
La solution s'y trouve peut-être dans un des commentaires.
Cordialement.
Essayes d'aller sur le site constructeur tu choisis ton modèle de pc et tu mets à jour tout ce que tu peux (Bios, chipset, audio, graphique ect...).
Mais ça ressemble à un soucis de RAM si plusieurs appli le font planter ET à la reprise de veille ça plante aussi...
Dans un premier temps fais ce que je t'ai dit et ensuite test de stresser l'ordi en lançant beaucoup d'applis. Mais essayes aussi de voir le liens que je t'ai donné plus haut !
La solution s'y trouve peut-être dans un des commentaires.
Cordialement.
télécharge whocrashed, tu fait analyse puis tu vas dans dump, tu aura le crash et le fichier mis en cause
bonjour,
Voici ce qui en ressort :
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Mon 02/01/2017 05:04:27 your computer crashed
crash dump file: C:\WINDOWS\Minidump\010217-34718-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0xA (0xFFFFDCF7E8CA2988, 0x2, 0x0, 0xFFFFF80307125185)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 01/01/2017 23:25:51 your computer crashed
crash dump file: C:\WINDOWS\Minidump\010117-29875-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0x9F (0x3, 0xFFFFA48C5B323640, 0xFFFFE081F53B2960, 0xFFFFA48C548D9480)
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.
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 01/01/2017 18:26:53 your computer crashed
crash dump file: C:\WINDOWS\Minidump\010117-34687-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0x9F (0x3, 0xFFFFAB01DB09C060, 0xFFFF8481EE7B2960, 0xFFFFAB01DFC4D750)
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.
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 01/01/2017 18:26:53 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: 0x9F (0x3, 0xFFFFAB01DB09C060, 0xFFFF8481EE7B2960, 0xFFFFAB01DFC4D750)
Error: DRIVER_POWER_STATE_FAILURE
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
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 Fri 30/12/2016 21:19:14 your computer crashed
crash dump file: C:\WINDOWS\Minidump\123016-35562-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0x9F (0x3, 0xFFFF9B86FC88FBA0, 0xFFFFF8012A064960, 0xFFFF9B86F73AB1F0)
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.
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
--------------------------------------------------------------------------------
11 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.
Voici ce qui en ressort :
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Mon 02/01/2017 05:04:27 your computer crashed
crash dump file: C:\WINDOWS\Minidump\010217-34718-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0xA (0xFFFFDCF7E8CA2988, 0x2, 0x0, 0xFFFFF80307125185)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 01/01/2017 23:25:51 your computer crashed
crash dump file: C:\WINDOWS\Minidump\010117-29875-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0x9F (0x3, 0xFFFFA48C5B323640, 0xFFFFE081F53B2960, 0xFFFFA48C548D9480)
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.
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 01/01/2017 18:26:53 your computer crashed
crash dump file: C:\WINDOWS\Minidump\010117-34687-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0x9F (0x3, 0xFFFFAB01DB09C060, 0xFFFF8481EE7B2960, 0xFFFFAB01DFC4D750)
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.
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 01/01/2017 18:26:53 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: 0x9F (0x3, 0xFFFFAB01DB09C060, 0xFFFF8481EE7B2960, 0xFFFFAB01DFC4D750)
Error: DRIVER_POWER_STATE_FAILURE
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
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 Fri 30/12/2016 21:19:14 your computer crashed
crash dump file: C:\WINDOWS\Minidump\123016-35562-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0x9F (0x3, 0xFFFF9B86FC88FBA0, 0xFFFFF8012A064960, 0xFFFF9B86F73AB1F0)
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.
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
--------------------------------------------------------------------------------
11 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.
sur le dernier écran bleu, j'ai pu lire :
DRIVER POWER STATE FAILURE