Ecran bleu avec différents messages, même en mode sans échec

On Fri 27/06/2014 20:06:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini062714-01.dmp
This was probably caused by the following module: aswsp.sys (aswSP+0x1A414)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF834BC372, 0xFFFFFFFFAEDDA860, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\aswsp.sys
product: avast! Antivirus
company: AVAST Software
description: avast! self protection module
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
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: aswsp.sys (avast! self protection module, AVAST Software).
Google query: AVAST Software KERNEL_MODE_EXCEPTION_NOT_HANDLED_M



On Fri 27/06/2014 20:06:18 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: aswsp.sys (aswSP+0x1A414)
Bugcheck code: 0x8E (0xFFFFFFFFC0000005, 0xFFFFFFFF834BC372, 0xFFFFFFFFAEDDA860, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\aswsp.sys
product: avast! Antivirus
company: AVAST Software
description: avast! self protection module
Bug check description: This bug check indicates that a kernel-mode application generated an exception that the error handler did not catch.
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: aswsp.sys (avast! self protection module, AVAST Software).
Google query: AVAST Software KERNEL_MODE_EXCEPTION_NOT_HANDLED



On Thu 26/06/2014 20:27:16 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini062614-02.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
A third party driver was identified as the probable root cause of this system error.
Google query: CUSTOM_ERROR



On Thu 26/06/2014 20:27:16 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini062614-03.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xCD9BD)
Bugcheck code: 0xC2 (0x7, 0x110B, 0x2070208, 0xFFFFFFFFA6E1ABA8)
Error: BAD_POOL_CALLER
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the current thread is making a bad pool request.
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 26/06/2014 20:14:41 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini062614-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x4DECD)
Bugcheck code: 0xA (0xFFFFFFFFC00D55C0, 0x2, 0x0, 0xFFFFFFFF834F6934)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.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.