Driver Power State Failure / pci.sys

Merci de ta réponse,

Je suis sous Windows 8.1

Au début, les problèmes apparaissaient lorsque je lançais des jeux. Ils apparaissent maintenant aussi à d'autres moments. J'ai déjà tenté de réinstaller le pilote de ma carte graphique.
Je n'utiles qu'une souris comme périphérique et elle ne semble pas être la source du problème.
Voici les résultats de l'analyse WhoCrashed:

--------------------------------------------------------------------------------
Welcome to WhoCrashed (HOME EDITION) v 6.01
--------------------------------------------------------------------------------

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: LAURENCE-PC
Windows version: Windows 8.1 , 6.3, build: 9600
Windows dir: C:\Windows
Hardware: G551JW, ASUSTeK COMPUTER INC.
CPU: GenuineIntel Intel(R) Core(TM) i7-4720HQ CPU @ 2.60GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 17063514112 bytes total




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dumps are enabled on your computer.

Crash dump directories:
C:\Windows
C:\Windows\Minidump

On Sun 14.10.2018 14:43:39 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+0x1402A0)
Bugcheck code: 0x9F (0x3, 0xFFFFCF80A63AA880, 0xFFFFD000CFFE2CB0, 0xFFFFCF80B444ABD0)
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 04.05.2018 21:15:44 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\050418-63250-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1552A0)
Bugcheck code: 0x9F (0x3, 0xFFFFE0002A383880, 0xFFFFD0018BFFD960, 0xFFFFE0002EDFECA0)
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 Tue 01.05.2018 21:17:02 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\050118-53734-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1552A0)
Bugcheck code: 0x9F (0x3, 0xFFFFE000293CE060, 0xFFFFD00024EBE960, 0xFFFFE0002DA247A0)
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 Mon 30.04.2018 21:43:09 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\043018-43406-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1552A0)
Bugcheck code: 0x9F (0x3, 0xFFFFE0013780B060, 0xFFFFD001210BE960, 0xFFFFE001367C1010)
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 Sun 29.04.2018 11:11:01 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\042918-43890-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1552A0)
Bugcheck code: 0x9F (0x3, 0xFFFFE000FA628880, 0xFFFFD000861F9960, 0xFFFFE000F95D2650)
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 28.04.2018 21:18:39 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\042818-30796-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1552A0)
Bugcheck code: 0x9F (0x3, 0xFFFFE000BFAD0880, 0xFFFFF801EEEC8960, 0xFFFFE000BE5D4B40)
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 27.01.2018 17:47:08 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\012718-33031-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x154EA0)
Bugcheck code: 0x9F (0x3, 0xFFFFE001CCD81880, 0xFFFFF8022B6B0960, 0xFFFFE001D1BEA7A0)
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 Mon 15.05.2017 17:46:37 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\051517-53921-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E2A0)
Bugcheck code: 0x9F (0x3, 0xFFFFE001B8380060, 0xFFFFD00196171960, 0xFFFFE001BC808010)
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 corrupt:
C:\Windows\Minidump\050918-53828-01.dmp
C:\Windows\Minidump\051517-43640-01.dmp




--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

On your computer a total of 51 crash dumps have been found. Only 10 have been analyzed. Only 8 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.