Voilà les rapports :
Je vais copier coller les 3 analyses de WhoCrashed à suivre, désolé pour le pavé.
On Mon 12/05/2014 20:24:11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051214-4882-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x4211)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF8800D1DD828, 0xFFFFF8800D1DD080, 0xFFFFF880012C3E83)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du système de fichiers NT
Bug check description: This indicates a problem occurred in the NTFS file system.
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 12/05/2014 20:24:11 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: eamonm.sys (eamonm+0x29EA6)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF8800D1DD828, 0xFFFFF8800D1DD080, 0xFFFFF880012C3E83)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\eamonm.sys
product: ESET Smart Security
company: ESET
description: Amon monitor
Bug check description: This indicates a problem occurred in the NTFS file system.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: eamonm.sys (Amon monitor, ESET).
Google query: ESET NTFS_FILE_SYSTEM
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
2 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:
eamonm.sys (Amon monitor, ESET)
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.
Read the topic general suggestions for troubleshooting system crashes for more information.
On Sat 17/05/2014 20:16:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051714-4867-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0x831E9D0, 0x2, 0x1, 0xFFFFF800030DFBC4)
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 Sat 17/05/2014 20:16:17 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: iusb3xhc.sys (iusb3xhc+0x24140)
Bugcheck code: 0xA (0x831E9D0, 0x2, 0x1, 0xFFFFF800030DFBC4)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\iusb3xhc.sys
product: USB 3.0 Device Driver
company: Intel Corporation
description: Intel® USB 3.0 eXtensible Host Controller Driver
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.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: iusb3xhc.sys (Intel® USB 3.0 eXtensible Host Controller Driver, Intel Corporation).
Google query: Intel Corporation IRQL_NOT_LESS_OR_EQUAL
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
3 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:
iusb3xhc.sys (Intel® USB 3.0 eXtensible Host Controller Driver, Intel Corporation)
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.
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.
On Mon 26/05/2014 21:14:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052614-4508-01.dmp
This was probably caused by the following module: ks.sys (ks+0x10B60)
Bugcheck code: 0xBE (0xFFFFF88004CD1B60, 0x800000020E989121, 0xFFFFF88009D4F3F0, 0xA)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\Windows\system32\drivers\ks.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel CSA Library
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
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 26/05/2014 21:14:54 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ks.sys (ks!KsPinSetPinClockTime+0x1540)
Bugcheck code: 0xBE (0xFFFFF88004CD1B60, 0x800000020E989121, 0xFFFFF88009D4F3F0, 0xA)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\Windows\system32\drivers\ks.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel CSA Library
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
4 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.
---------------
Un petit clic vaut mieux qu'une grande claque !
)
pourquoi les "informaticiens" disent que ça vient de l'alim sous-dimensionnée alors que c'est assez récent les BSOD ? (ou alors c'est depuis le début ?...) bref, c'est pas logique 
)