Écran bleu ntoskrnl.exe disant driver power state failure

Bonjour,
j'ai mon portable depuis environ 2 ans, et depuis environ le moi de janvier il fait à quelques reprises des écrans bleu je voudrais savoir comment l'arranger. Il est toujours branché mais la batterie a été retiré, elle est remise seulement lorsque je débranche mon portable..ce qui arrive rarement.


voici mes configurations de pc:
vindows 7 64bit
intel core i5-460m
4g de ram
intel(r) hd graphics mémoire de 1696 mo


voici le rapport Who Crashed:

computer name: MARIE
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\windows
Hardware: FR700/FX700, Micro-Star International Co., Ltd., MS-1751
CPU: GenuineIntel Intel(R) Core(TM) i5 CPU M 460 @ 2.53GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 4074831872 total
VM: 2147352576, free: 1955803136




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

Crash dump directory: C:\windows\Minidump

Crash dumps are enabled on your computer.

On Tue 2014-04-01 11:28:05 GMT your computer crashed
crash dump file: C:\windows\Minidump\040114-17269-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x9F (0x3, 0xFFFFFA8004906A10, 0xFFFFF80000B9C518, 0xFFFFFA8007820C10)
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 2014-04-01 11:28:05 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, 0xFFFFFA8004906A10, 0xFFFFF80000B9C518, 0xFFFFFA8007820C10)
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 Wed 2014-03-26 15:01:07 GMT your computer crashed
crash dump file: C:\windows\Minidump\032614-22698-01.dmp
This was probably caused by the following module: afd.sys (afd+0x243A)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF880040EE43A, 0xFFFFF880084FAA50, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\windows\system32\drivers\afd.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Ancillary Function Driver for WinSock
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Mon 2014-01-20 13:01:06 GMT your computer crashed
crash dump file: C:\windows\Minidump\012014-18579-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x9F (0x3, 0xFFFFFA800490E060, 0xFFFFF80000B9C518, 0xFFFFFA80073F4890)
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 Fri 2014-01-10 18:15:51 GMT your computer crashed
crash dump file: C:\windows\Minidump\011014-20404-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x9F (0x3, 0xFFFFFA800490BA10, 0xFFFFF80000B9C518, 0xFFFFFA8006D9E730)
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 Fri 2013-12-20 01:54:01 GMT your computer crashed
crash dump file: C:\windows\Minidump\122213-23556-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x9F (0x3, 0xFFFFFA8003BAD700, 0xFFFFF80004D20518, 0xFFFFFA80077EC940)
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 actually 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.