Aller au contenu


Blue Screen Driver Power State Failure


  • Veuillez vous connecter pour répondre
28 réponses à ce sujet

#1 xeration

xeration
  • Invités

Posté 21 août 2016 - 01:00

Bonjour,


Depuis quelque jours j'ai le problème de l'écran bleu et l'erreur driver power state failure :

Le pc plante, reboote, l'écran bleu survient pendant 5 minute, le pc reboote charge pendant 5-10 minutes puis tout remarche.
Le problème c'est que le problème survient à chaque démarrage ou sortie de veille prolonger, j'ai essayer d'enlever la veille prolonger mais rien n'y fait 
J'ai suivis pas mal de tuto jusqu’à formater mon PC à l'état d'usine, mais rien ne change.

Quelqu'un pourrait-il me venir en aide ?


  • 0

PUBLICITÉ

    Annonces Google

#2 Tonton

Tonton

    Modérateur

  • Modérateur [Tonton]
  • 19 098 messages

Posté 24 août 2016 - 10:34

Bonjour xeration,

Lance WhoCrashed (http://forums.cnetfr...vec-whocrashed/) et poste le log correspondant, stp.

Pense également à t'inscrire sur Zébulon : c'est gratuit.

@+,
Tonton


  • 0

#3 xeration

xeration

    Junior Member

  • Membres
  • 19 messages

Posté 26 août 2016 - 07:46

Bonjour,

 

Merci de votre réponse, voici les logs de whocrashed :

 

Crash Dump Analysis

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Tue 23/08/2016 06:18:41 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\082316-269312-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E2A0)
Bugcheck code: 0x9F (0x3, 0xFFFFE000BF968880, 0xFFFFD001B67F8960, 0xFFFFE000C4DF8540)
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 Tue 23/08/2016 06:18:41 GMT 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, 0xFFFFE000BF968880, 0xFFFFD001B67F8960, 0xFFFFE000C4DF8540)
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 Mon 22/08/2016 05:01:23 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\082216-598250-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E2A0)
Bugcheck code: 0x9F (0x3, 0xFFFFE00078FE9060, 0xFFFFD000A6BF8960, 0xFFFFE0007E7F2BF0)
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 Thu 11/08/2016 14:26:25 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\082116-273312-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E2A0)
Bugcheck code: 0x9F (0x3, 0xFFFFE001F0F59060, 0xFFFFD00193DF8960, 0xFFFFE001F2999010)
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 Thu 11/08/2016 13:51:58 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\081116-276187-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E2A0)
Bugcheck code: 0x9F (0x3, 0xFFFFE00075557060, 0xFFFFD001F67E1960, 0xFFFFE000778D25C0)
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 Thu 11/08/2016 08:41:46 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\081116-273250-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E2A0)
Bugcheck code: 0x9F (0x3, 0xFFFFE000517D57C0, 0xFFFFF800F1034960, 0xFFFFE00053B01B40)
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

6 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. 


  • 0

#4 Tonton

Tonton

    Modérateur

  • Modérateur [Tonton]
  • 19 098 messages

Posté 26 août 2016 - 03:02

Bonjour xeration,
 
Je te conseille de réparer Windows 8 sans perte de données : http://www.chantal11...rte-de-donnees/

@+,
Tonton


  • 0

#5 xeration

xeration

    Junior Member

  • Membres
  • 19 messages

Posté 28 août 2016 - 09:30

Bonjour,

 

J'ai suivis la procédure, maheureusement, le problème persiste :(


  • 0

#6 pear

pear

    Devil Member !

  • Equipe Sécurité
  • 27 259 messages

Posté 28 août 2016 - 11:04

Essayez ceci:

 

 

la commande DISM , ne fonctionne pas sous windows vista
elle ne fonctionne qu'a partir de windows 8
lancer l'outil Dism.exe, en procédant comme suit:
    Cliquez sur les touches Windows+X, et choisissez Invite de commandes (admin).
    Dans l'invite de commandes, tapez les lignes suivantes une par une et validez par Entrée.
    DISM.exe /Online /Cleanup-image /Scanhealth
    DISM.exe /Online /Cleanup-image /Restorehealth
    Remarque: Cette manipulation prend une quinzaine de minutes, patientez jusqu'à la fin de l'exécution.
  

  • 0

#7 xeration

xeration

    Junior Member

  • Membres
  • 19 messages

Posté 29 août 2016 - 01:38

Bonjour,

 

Suite au commande que vous m'aviez indiquer, le problème reste inchanger :(

 

j'ai pu lire sur internet qu'il fallait que je désactive une option d'alimentation du PC (celle qui fait que l'ordinateur s'allume plus vite) en désactivant cette option (qui est recommandé d'activer) je n'est plus le message, mais l'ordinateur met beaucoup de temps à s'allumer


  • 0

#8 xeration

xeration

    Junior Member

  • Membres
  • 19 messages

Posté 03 septembre 2016 - 01:40

pas de solution ?


  • 0

#9 pear

pear

    Devil Member !

  • Equipe Sécurité
  • 27 259 messages

Posté 03 septembre 2016 - 02:23

Vérfiez si un driver, graphique par exemple, ne serait pas à mettre à jour


  • 0

#10 xeration

xeration

    Junior Member

  • Membres
  • 19 messages

Posté 04 septembre 2016 - 08:45

Tout est à jours :/


  • 0









Sujets similaires :     x