xeration

Oui, hier il n'étais pas disponible, voici le lien avec Cjoint : http://www.cjoint.com/c/FJglcX14lRw

Bonjour, Ayant des soucis avec CJoint, j'ai opté pour partage facile http://www.partage-facile.com/L042P3N2R0/maconfig_0__2_.pdf.html J'ai exécuter la partie 2 donc, le problème est toujours présent !

Bonjour, désolé pour le temps d'attente, donc voici pour les drivers, si j'ai bien compris, j'attends pour le point 2 ? http://www.cjoint.com/c/FIzmcWTksDp

Salut, Voici le ci joint : http://www.cjoint.com/c/FItsJavk72M

Bonjour, Nous avons supprimé la totalité des infections, cependant le problème n'est pas résolu :/

Voici les différents fichier : SFT : http://www.cjoint.com/c/FIpsfdQShXB Rapport 1 http://www.cjoint.com/c/FIpsfBzC6wB Rapport 2 http://www.cjoint.com/c/FIpsgUAHFzB

je fais ça dans la soirée, le comportement de la machine n'a pas changer malheureusement : long à démarrer (lorsque j'active l'option démarrage rapide dans le panneau de config, l'écran bleu réapparaît)

Voici le JRT : http://www.cjoint.com/c/FIpmbVOzOpw et voici le adw : http://www.cjoint.com/c/FIpmcCR7Tow

Bonjour, Voici le rapport de réparation : http://www.cjoint.com/c/FIpkVnNwelJ

Merci beaucoup, le sujet a été créer

Bonjour, Comme suggéré par Tonton (http://forum.zebulon.fr/blue-screen-driver-power-state-failure-t217044.html/page-2?do=findComment&comment=1813748), je poste ici pour effectuer une désinfection de mon pc Voici le lien de mon précédent post : http://forum.zebulon.fr/blue-screen-driver-power-state-failure-t217044.html/page-2 Voici le lien ZHPDIAG que j'avais fournis : http://www.cjoint.com/c/FImg3q6Xcgw Merci beaucoup pour votre aide ! Edit de Notpa : insertion du lien du sujet d'origine

Bonjour ! Voici le lien cijoint du diag : http://www.cjoint.com/c/FImg3q6Xcgw

J'ai fais toute les manips que vouss m'aviez demandé, et mon pc est toujours aussi très long au démarrage, l'écran bleu apparait toujours :'( je commence à désespérer

Merci pour la procédure, donc voici le premier fichier http://www.cjoint.com/c/FIggEAY3mJ5 et le deuxieme : http://www.cjoint.com/c/FIggFnM2UD5 J'ai bien défragmenter, mais cela n'a pas servie à grand chose :/

Tout est à jours :/

pas de solution ?

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

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

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.